The team and the ramp

Fund the build. Scale the sell.

Two things about this plan are not optional. A software company is built by software engineers, so the seed funds the engineering build. And the entire return lives in the scaling, so the model cannot stop at 50 physicians. The full-scale team of 108 people is lean for the revenue it runs. Here is the math on all three.

The product is the code. The return is the scale. REV.health is an AI-native EMR plus integrated RCM: 10 modules, FHIR-native, and the full 2026-2027 compliance stack (USCDI v3, SMART, Da Vinci prior-auth, TEFCA, NCPDP). That is a software product. The engineers are not overhead on top of it. They are it. And a product that serves 50 physicians is a $2.4M business that returns less than the seed. The same product across 866 providers is $50.9M ARR and returns 25.4x.

A software company needs software developers

The build is real engineering: an ambient scribe that produces structured, coded encounters, a FHIR-native data model, payer prior-auth (Da Vinci CRD / DTR / PAS), e-prescribing (NCPDP SCRIPT), national exchange (TEFCA), and ONC certification. None of that ships without a senior engineering core, and it is the seed's primary job to fund that core through the build.

Engineering core

4 → 10

senior team, never rolls off. The smallest line on the roster, and the most essential.

ARR per employee at scale

~$471K

$50.9M ARR / 108 people. Lean for a SaaS plus RCM-services business.

Loaded eng salary

$200K

fully loaded, in the model

A software company with no software developers has nothing to sell. The engineering line is the one place the plan spends ahead of revenue on purpose, because the product has to exist before anyone pays for it.

You cannot stop at 50 physicians

Every provider on the platform pays a blended ~$4,898 per month (SaaS subscription plus the RCM share of collections). That number is the same whether there are 50 providers or 866. The difference is the count, and the count is the whole return.

Stop at 50 physicians

~$2.9M ARR

0.88x the seed at a 6x exit (a loss), 1.47x even at 10x. Does not return the round.

Scale to 866 providers

$50.9M ARR

15.3x at the 6x floor, 25.4x at a 10x exit. The plan.

Same product, both cases

~346

practices at full scale (866 providers, ~0.3% of US PCPs). Runway, not a share grab.

A 50-physician outcome is a lifestyle clinic-software shop. It cannot pay back a $4M seed, let alone deliver a venture return. The model is built to scale because the only version that works is the one that does.

The arc: build, then sell

One sequence, two phases. Spend the first year building a stable product with the engineering core. Then turn on the go-to-market and scale it. The captive network channel carries about 85% of growth, so the external sales team stays small.

flowchart LR
  A["Phase 1 · Build
~12 months
engineering-heavy
$0 revenue by design"] --> B["Stable product
10 modules · FHIR-native
2026-27 compliance shipped"]
  B --> C["Phase 2 · Sell & scale
captive networks + lean external sales
ramp to 866 providers"]
  C --> D["$50.9M ARR
25.4x at a 10x exit"]

This is the ramp-up you asked about. The only thing that ramps down is the cost to serve each provider: AI drives the RCM workload per physician lower every year even as the absolute team grows.

The staffing is right-sized, and it ramps

Here is the team at full scale (month 72), by function. Engineering is a small senior core. The operations lines (RCM, support, implementation, clinical) scale with the installed base, but the per-physician FTE stays tiny because the AI does the repetitive work. Most growth is captive — Empower and partner networks feed it, so the external sales team only works the ~15% we don't already own: a lean team of account execs (~14 at scale) on network-level deals.

Function	FTE at full scale	How it scales
Engineering / DevOps	10	Senior core, never rolls off. Grows slowly (4 to 10 over six years). This is the product.
RCM operations	46	~0.053 FTE per physician, and falling each year with AI. A labor-heavy legacy shop needs several times this.
Customer support	21	~0.024 FTE per physician. Scales with the installed base.
Implementation	4	~0.005 FTE per physician. Onboards each new practice.
Clinical / quality	6	~0.007 FTE per physician. Documentation and coding quality.
Sales (account execs)	14	The lean external motion that wins the ~15% non-captive slice — account execs on network-level deals, not a retail/cold-call org.
Executive & G&A	7	Leadership plus general & administrative operations.
Total	108	$50.9M ARR, about $471K of ARR per employee.

The employee-by-employee roster, with start dates, is already in the model on the Personnel and Hiring-Plan tabs, built bottom-up month by month.
108 is lean, not outsized. At ~$471K ARR per head, this is efficient for a business that bundles software with RCM services. A pure billing shop at this revenue runs far more people.
If a role is missing, it gets added, not cut. If the plan needs more engineers or ops staff than the current roster carries, that is a signal to add positions and grow into them, never to shrink the ambition to fit a smaller team.

Sources: REV.health saasRcm $4M operating model (Personnel, Hiring-Plan, Provider-Ramp, P&L tabs); headcount is the bottom-up build behind corp SWB and cost-to-serve. Revenue and return figures are the model's base case.

Fund the build. Scale the sell. The engineering core is the smallest line and the one worth funding first, because without it there is no product. The scale is the whole return, because 50 physicians does not pay back the seed and 866 returns 25.4x. And 108 people for $50.9M ARR is a lean team, not an outsized one. That is the business.