Revenue Model: Three Cases, Stated Honestly
Updated: 2026-07-22, aligned to Rōvn master canon generation 8 (effective 2026-07-21). Contracted revenue today: zero. Rōvn is pre-launch, with zero paying customers and zero signed pilots as verified facts. Nothing on this page is traction.
1. Why the prior three-case model is withdrawn
The dated May 2026 Bear / Base / Bull model that previously lived on this page was built on an internal multi-tier price ladder that has since been retired. Its dollar curves, logo counts, blended ACVs, and the exit math derived from them are withdrawn as investor-facing forecasts. The workbook remains downloadable in 02.9 Financial Model as a labeled historical artifact only, until the rebuilt model on the current pricing unit passes founder and board review.
What replaced the ladder is deliberately simpler:
- Exactly one public price: Readiness at $2,500 per month. Everything above it is governed and quoted.
- One billable unit: active monitored lives (persons). Work Relationships and Work Activations are cost and telemetry sub-units, never the invoice driver.
- Reuse never raises price within a band.
2. Model discipline (what any Rōvn forecast must satisfy)
Per canon, every forecast requires:
- base, downside, and upside cases;
- explicit facility, worker, relationship, and Work Activation assumptions;
- source-cost and implementation sensitivity;
- no double counting of subscription and transaction revenue;
- a clear distinction between contracted, pipeline, target, and hypothetical revenue;
- a cash runway and hiring trigger tied to milestones.
Today every line of every case is hypothetical: contracted revenue is zero and pipeline is early. Any number an investor sees before a signed agreement exists is a target, not a commitment and not a result.
3. Where revenue can come from
- Readiness subscriptions (the entry).
- Operator subscriptions.
- Monitored-lives tiers.
- Implementation packages.
- Enterprise platform contracts.
- Authorized API and embed access (READ).
- Receipt and audit exports.
- Delegated credentialing, only after the applicable certification and agreements exist.
- Future worker premium, only for additive features that never degrade the free Passport.
Revenue never comes from placement fees, commissions, success or finder fees, selling worker data, per-reuse penalties, hidden steering, or a facility-facing worker reliability score. See 02.2 Pricing and Packaging.
4. The one public arithmetic anchor
The only revenue arithmetic this room publishes is derived from the one public price:
| Anchor | Arithmetic | Status |
|---|---|---|
| One Readiness customer | $2,500 per month = $30,000 annualized | List-price arithmetic, not a forecast and not a contract |
| Everything above Readiness | Quoted per organization against monitored lives | Governed; no public dollar figures until board-approved |
5. Case definitions (assumption sets, no dollar totals yet)
The rebuilt model publishes dollar curves only after founder and board approval. What is fixed now is what each case must assume, explicitly:
| Case | Core assumptions |
|---|---|
| Downside | One cluster only. Readiness subscriptions without Operator expansion. No delegation partner signed in the window. Slow source activation; higher manual exception cost; implementation payback longer than planned. |
| Base | The locked GTM triangle lands: one anchor paying organization, one delegation-capable partner signed in parallel, one agency or contingency bench depositing the same clinician pool. Readiness converts to Operator inside the first cluster. Monitored lives grow with facility density; second-Work-Activation cost falls measurably. |
| Upside | Multi-cluster density plus delegated reuse: the CVO clock matures into signed delegation, READ and API access begin producing platform revenue, and cross-organization reuse compounds retention and expansion. |
6. What to watch instead of a hockey stick
Until real revenue exists, the leading indicators are operational, and they are defined precisely in 02.6 KPI Definitions and 02.7 the KPI Dashboard spec:
- first paying Readiness customer, and density rising in that cluster;
- active monitored lives under management;
- Passport claim and liveness rates on the first deposited roster (targets: 40 percent claimed, 25 percent active trailing 90 days);
- time and cost of the first Work Activation versus the second (the falsifiable network test);
- zero-rework Work Activation rate, the North Star compass, once instrumented in the first pilot;
- implementation payback and coordinator hours displaced, measured against the facility's own baseline.
All figures anywhere in this section are projections or targets. Rōvn will not present a target as a result, and any current-state claim carries its evidence date.