Diligence notice·Working state of Rōvn as of 2026-07-09 · Pre-launch by designSee 09 for receipts →
AI Diligence Console
Drag the sliders to model how the $5M seedRound sizeFundraise plan · 2026-07 · $5M seed opens November 2026 into YC Demo Day (December 3); terms shared on request once counsel confirms the offering exemption (see 02.1 Use of Funds) deploys across engineering, GTM, compliance, and advisory. Headcount, runway, and milestones recompute live. The starting allocation matches 02.1 Use of Funds.
This is a scenario tool, not a commitment.
We are raising a $5M seed round, opening November 2026 into YC Demo Day on December 3. The round is sized to fund the team through the 18-to-24-month NCQA-CVO certification clock. Terms are shared on request once counsel confirms the offering exemption. Until the round closes, the company runs at a lean pre-seed burn of about $58K per month. Default sliders match the planned $5M allocation; Reset returns to the plan. Operating-cost assumptions (loaded $/headcount, vendor burn, cloud spend) are the same as the 02.9 3-case model.
$5,000,000total raise
, monthly burn
, runway (months)
, peak headcount
46%$2,300,000
22%$1,100,000
14%$700,000
8%$400,000
10%$500,000
Allocations: 100%
What the raise is built on: the six provables
The seed opens on proof, not promises. Six checkable provables anchor the round:
Verification integrity closed in production: the record-stage bypass fixed and source-receipt binding live, independently verified
One delegation-capable partner signed (the grant that makes verify-once legally reusable)
Founding Chief Credentialing and Compliance Officer (CCCO) landed
First paying Readiness customer live, with reuse density rising in that cluster
NCQA-CVO certification clock started from real pilot verifications
Worker-liveness targets hit on the first deposited roster: 40% of passports claimed, 25% active in the trailing 90 days
The round itself is sized to fund the team through the 18-to-24-month NCQA-CVO certification clock.
Full Bear / Base / Bull scenarios with revenue build, headcount plan, and DCF live in the 3-case operating model (XLSX).
Ask the AI agent about this section, the raise, compliance posture, or any cross-document question. Grounded in Rōvn's deep context, with on-page source citations.
AI queries route through AWS BedrockAI provider chain07.3 AI Architecture · AWS Bedrock under BAA → Anthropic Claude Haiku 4.5 under BAA → Rōvn ECS under BAA · Anthropic Claude (Haiku 4.5)Model identity07.3 AI Architecture · Haiku 4.5 chosen for cost + latency + BAA chain under BAA · zero-data-retention posture · no PHI in prompts.