Founding pilot
A paid pilot,against a baseline you own.
In this category, buyers are asked to run an unpaid pilot with no defined endpoint, no measured baseline, and no exit, then handed a result calculated inside the vendor's own black box. This page states the founding pilot's published terms so none of that is a question by the time you sign.
Paid from day one. Scoped to one workflow. Measured against numbers your organization already has. Closed on a fixed 180-day schedule, with a stated exit if the results do not hold.
01 · What a pilot is
One organization. One workflow. One owner.
A founding pilot is not a proof of concept and not an open-ended trial. It is a defined engagement, seven terms, all fixed before work starts.
- One organization
- The pilot runs inside one organization, on its own systems and its own policies. Nothing in the terms below is shared across a cohort.
- One workflow
- A single named workflow, scoped and frozen for the length of the pilot. A wider scope is a new pilot, not a change to this one.
- One owner
- A single named decision owner on the organization’s side, accountable for every regulated decision the pilot touches.
- One honest source path
- Evidence is drawn from the organization’s real source systems for the length of the pilot, not a demo environment built to look clean.
- One complete Work Activation loop
- A governed Work Activation runs end to end at least once: the whole loop, not a slice of it.
- A defined baseline
- Measured before the pilot starts, in the organization’s own numbers, then frozen so the pilot’s result has something honest to compare against.
- Named support and decision owners
- A named Rōvn contact and a named organization approver, both on record for the length of the term.
02 · The value equation
The organization supplies its own baseline.
Pilot value is not a vendor estimate. It is added up from the organization's own operating numbers, the same way a finance team would add them.
Pilot value is measured as the sum of
- administrative chase hours × loaded labor cost
- blocked clinician-days × organization-validated daily contribution
- credentialing and enrollment denials and write-offs
- avoidable temporary, overtime, or premium coverage cost
- repeated verification and implementation cost
Rōvn does not promise a savings percentage or a dollar result before a pilot establishes the baseline and measures the result.
Dated industry benchmarks may frame the size of the problem, attributed on the page where they appear; they are never printed here as Rōvn's own claimed outcome. No modeled calculation is presented as an operating result.
03 · The schedule and the terms
180 days, on a fixed schedule.
Four stations, one rule, a fixed acceptance date. Then five published bands, each scoped to a different amount of operated work, no vendor call required to see a number.
Days 1 to 90
Prove readiness against a frozen cohort and a measured baseline.
Days 91 to 180
Prove the contracted workflows, on your roster, at your sites.
Acceptance
By day 165, on the terms fixed at day one.
Production
Begins day 181, at the band your scope has earned.
| Pilot band | Year-one investment | What it covers |
|---|---|---|
| Foundation | $20,000 | One site, the core governed roster, readiness alone |
| Growth | $30,000 | Multiple sites, one organization, readiness plus renewals |
| Scale | $45,000 | Delegated workflows across the organization’s full roster |
| Enterprise | $75,000 | Full delegated operations, every site, every workflow in scope |
| Network | $100,000 to $175,000 | Multiple organizations under one governed network |
04 · What each side brings
You bring the roster. Rōvn brings the work.
Neither side is guessing what the other owes. Both columns below are fixed in the same terms sheet your pilot signs.
You bring
- One rosterThe clinicians already in scope for this pilot, no new hiring required to start.
- One workflowThe single process you want proven, named at the start and held for the term.
- A named decision ownerOne person on your side, accountable for every regulated call the pilot touches.
- Your own baselineMeasured going in, in your own numbers, not estimated after the fact.
Rōvn brings
- The operated work, receiptedChase, evidence gathering, monitoring, and drafting, every step logged to a receipt.
- Named human gatesOn every regulated decision, nothing regulated moves without your named owner’s signature.
Underneath both columns, agents do the chase: they query sources, open cases on items nearing expiration, gather and reconcile evidence, and draft what a human needs to see, around the clock, receipted at every step. Every regulated decision in this pilot, on either side, stays with a named person. Nothing here is decided by software.
05 · What would make us stop
The kill criterion, published as a pilot term.
This is not a marketing line. It is printed here because it is falsifiable, and because a pilot that could never fail to prove its case would not be worth running.
If the second governed Work Activation is not materially faster and cheaper than the first, the network thesis is wrong.
The pilot is built to test that sentence, not to avoid testing it. If it fails, the honest next step is to say so, not to relabel the measurement.
06 · Start the pilot
Bring one roster. Read the terms first.
One conversation, one destination: scope, baseline, and the fixed 180-day schedule get set before anything starts.
No signature is asked for on that call. It exists so the terms on this page are the terms you actually get.