Financial Outlook#

We built this page as a summarized read of our financial model. It covers the three questions investors most often start with: how we plan to spend a Seed round, how the team is expected to grow, and where revenue comes from as EMOS scales.

A detailed financial model (revenue build, per-quarter cash flow, unit economics, cohort assumptions) is available on request. See the note at the bottom of the page.

Use of Funds#

We are raising €6M to fund an 18-month runway starting November 2026 (through April 2028) delivering the first stable release of EMOS along the milestones on our product roadmap — the unified open-source release of EMOS, zero-touch enterprise onboarding, expanded hardware support, and the first wave of paid OEM and enterprise deployments.

Team Growth#

The hiring plan mirrors the two commercial waves in our go-to-market strategy: a first ramp in 2027 focused on integration and reference deployments, and a second ramp in 2028-2029 aligned with the marketplace launch and OEM scale-up.

Core R&D grows from 0 → 11 FTE by Q4 2029 — senior software engineers on Kompass and EmbodiedAgents in 2027, applied Physical AI engineers as VLA-based manipulation matures. This is the bench that keeps the core stack moving.
Deployment Engineers are the largest single bucket in the early years, ramping to 10 FTE by Q4 2029 — applied engineers who bring EMOS to specific OEM hardware and customer sites (HAL plugins, recipe development, on-site enablement). This is the bucket that makes “deployable in days” real for OEMs and integrators.
Go-to-Market (Sales & Biz Dev) starts in Q4 2026 and reaches 6 FTE by Q4 2029 — direct sales and business development into humanoid OEMs (China + EU) and integrator accounts.

Total planned headcount excluding founders reaches 27 FTE by Q4 2029. A rolling internship channel (2 per intake, twice a year) runs alongside these roles as the pipeline into full-time conversions — not shown separately on the chart.

Revenue Model#

EMOS revenue rests on three complementary streams, each aligned with a distinct actor in the robotics value chain. This blend is intentional — no single line dominates in the outer years, which means the plan does not depend on the marketplace inflection alone.

Licences & Support — Per-robot licences sold to end-users (directly or through integrators like Skysmart and M20), and pre-installed by OEM partners under revenue-share (DeepRobotics signed, humanoid OEMs in the MoU pipeline). Support tiers layered on top for enterprise buyers. This is the largest and most predictable stream once fleets deploy.
Services — Paid integration engagements — largely with OEMs and system integrators bringing new hardware into EMOS, plus a smaller share of custom recipe development for anchor enterprise customers (ESA Security Solutions is the reference). We keep this stream deliberately capped to avoid the “custom-project” trap that has held the wider robotics-software market back.
Marketplace — The EMOS Registry monetization engine launches from Q3 2027 onwards. Third-party recipe developers publish Apps to the registry, EMOS keeps a platform fee. This is the highest-leverage stream and the reason the 2029 line steps up sharply.

The trajectory assumes conservative attach rates on OEM-shipped fleets, no new large enterprise deals beyond the currently-visible pipeline, and marketplace GMV ramping only after the trust-and-safety framework is live.

Detailed Financial Model#

The full model — quarterly P&L, cash flow, headcount plan, unit economics per stream, and the underlying assumptions sheet — is available on request.

Request the detailed model

Please reach out to us at haroon@automatikarobotics.com and we will share the full Excel model along with a walk-through call.