Financials

Investor KPI Dashboard Spec

AI Diligence Console

Rōvn Investor KPI Dashboard: Definitions & Target Framework

Date: 2026-05-14 Audience: Pre-seed and Series A investors Cadence: Monthly, sent first business day of following month

Status, PRE-LAUNCH. Rōvn has zero paying customers, zero signed LOIs, zero revenue, zero ARR, and zero paid pilots. This document is not a report of actuals. It is a KPI specification: it defines every metric the monthly investor update will track and states the target values for the funded period. Every "actual" column will read 0 / n/a until the relevant milestone is reached post-funding. Numbers below labeled TARGET are planning goals, not commitments and not results.

1. Dashboard Structure

Once the company is operating, the monthly investor update is a single-page dashboard with three bands:

+===========================================================================+
| TOP BAND  (financial health, what investors look at first)              |
| ARR  ·  ARR growth  ·  Cash  ·  Runway  ·  Burn                          |
+---------------------------------------------------------------------------+
| MIDDLE BAND  (commercial momentum, sales pipeline)                       |
| Design partners signed/pending/declined  ·  Facility logos                |
+---------------------------------------------------------------------------+
| BOTTOM BAND  (product & moat, Rōvn-proprietary metrics)                 |
| Source authority adapter status                                          |
| Cached query count                                                       |
| AI receipt count                                                         |
| Audit chain block height                                                 |
+===========================================================================+

Until launch, every band reports 0 / n/a for actuals and shows the target framework below.

2. Top Band: Financial Health

Metric	Definition	Source	Current Actual	Funded-Period Target
ARR	Run-rate annualized recurring revenue at end of period	P&L sheet, REVENUE_BUILD	$0 (pre-launch)	First paid design partner → first non-zero ARR
ARR growth (MoM)	Month-over-month % change in ARR	Computed from ARR history	n/a, no ARR history	Track once ARR > $0
Cash on hand	Bank balance + AR aging	Bank balance + AR aging	Per close statement	≥ 12 months runway maintained
Runway	Cash ÷ 12-mo avg net burn	Cash / net burn	n/a until burn baseline set	≥ 12 months
Net burn (mo)	P&L expense − P&L revenue	P&L	Per close statement	Within 110% of plan

Heuristic alerts (auto-flagged once metrics go live): - ARR growth MoM < 5% → flag yellow - Runway < 12 months → flag yellow - Runway < 6 months → flag red, board call needed - Burn > 110% of planned → flag yellow

Pre-launch note: There is no ARR figure to report. The top band will display ARR: $0 (pre-launch) until the first paid design partner activates.

3. Middle Band: Commercial Momentum

Pipeline funnel: definitions and targets

There are no actuals to report yet. The funnel below defines each stage and states the funded-period target the team will build toward. All "Current Actual" entries are 0.

Stage	Definition	Funded-Period TARGET
Conversations	Facility decision-maker contacted, discovery scheduled	Build qualified top-of-funnel
Discovery calls	Completed needs-assessment call	Convert conversations at a healthy rate
Design partner LOIs	Non-binding intent to run a design-partner engagement	3-5 design partners over Months 0-6
Paid Pilots	Facility on a $12K 90-day Pilot (one-time, pilot-to-production)	Convert design partners to paid Pilots
Paid Core/Operator	Facility on paid Core ($10,000/mo · $120K ACV) or Operator ($20,000/mo · $240K ACV) tier, typically a converted Pilot	Pilot → Core/Operator conversion at day 90
Paid Platform	Enterprise Platform contract ($1M+)	Platform motion is a Y3+ target
Declined / Lost	Opportunity closed-lost; root cause logged	Track and root-cause every loss

Logo list (showcase): pre-launch

There are no customer logos. No facility has been named, signed, piloted, or onboarded. This section will populate only with facilities that have an actual signed agreement, once they exist. Until then it reads:

Facility	Tier	MRR	Status	Use case
none, pre-launch	-	-	-	-

Worker funnel (supply side): definitions and targets

No workers have registered. All actuals are 0.

Metric	Definition	Current Actual	M12 TARGET
Total Passport workers	Workers with a created Passport profile	0	2,000
Active workers (credentials current)	Workers with at least one current credential	0	1,000
Active conversion %	Active ÷ total Passport workers	n/a	50%
Credentials verified	Distinct credentials verified via Rōvn	0	5,000
Verifications via cache	Verifications served from cached replay	0	1,500

4. Bottom Band: Product & Moat Metrics

These are the Rōvn-proprietary metrics that no other healthcare-staffing comp tracks. They are the moat narrative for investors. All counts below are targets / definitions, actuals are 0 pre-launch and will be populated from production once live.

Source authority adapter status

Adapter coverage is a real, buildable product surface. The table below states the target coverage for the funded period. Status reflects build/integration state, not customer usage.

Source	Target Status	Target Coverage	Notes
NPDB	LIVE adapter	RN / MD	Primary-source verification
Nursys e-Notify	LIVE adapter	RN / LPN	Continuous license monitoring
Persona (identity)	LIVE adapter	Identity	IAL2 identity verification
Checkr (background)	LIVE adapter	Background	Per-pull billing
OIG exclusion list	LIVE adapter	Exclusions	Daily refresh
State BON adapters	PARTIAL	Expanding	Adding states each quarter
Specialty cert sources	PARTIAL	Expanding	ANCC, AACN, BLS in scope

Investor takeaway: Adapter coverage is the moat. More adapters = more verification scenarios served first-party = more cache density. Adapter build status is reported honestly; customer-usage counts remain 0 until launch.

Cached query count

Metric	Definition	Current Actual	Target
Total cached responses	Source responses stored for replay	0	Grows with verification volume
Cache hit rate	Cached replays ÷ total verification requests	n/a	70% by Y5
Estimated cost saved	Pass-through fees avoided via cache	$0	Tracks cache hit rate

Investor takeaway: Cache hit rate trajectory tells the gross-margin story. Goal: 70% by Y5.

AI receipt count

Metric	Definition	Current Actual	Target
Total ai_runs receipts	AI actions logged with a structured receipt	0	Grows with platform activity
Receipts with full source citation	% of receipts citing every source used	n/a	100% (non-negotiable)
Customer-visible decisions backed by receipt	% of surfaced AI outputs with a receipt	n/a	100% (non-negotiable)

Investor takeaway: 100% receipt coverage is the design standard. This is the trust positioning.

Audit chain block height

Metric	Definition	Current Actual	Target
audit_log block height	Append-only audit chain entry count	0	Grows with platform activity
Hash chain integrity check	Periodic chain-integrity verification result	n/a	PASS every check
Last anchored to S3 Glacier	Date of last cold-storage anchor	n/a	Monthly anchor

Investor takeaway: Append-only audit chain is the compliance moat. Once live, block-height growth is a customer-activity proxy.

5. Optional Add-On Bands

If the investor base asks for more depth, add these once the metrics exist:

Hospital Portal usage

Metric	Definition	Current Actual	Target
Active hospital users (logins/mo)	Distinct facility users logging in monthly	0	Grows with paid logos
Average decisions per session	Verification/credentialing actions per session	n/a	Track once live
Time-to-verification (median)	Median hours from request to verified result	n/a	Beat 14-day industry baseline

Verified API usage

Metric	Definition	Current Actual	Target
API customers (paying)	Distinct paying API accounts	0	Build paid API base post-launch
Verifications/month	API verification calls per month	0	Grows with API adoption
API revenue (monthly run-rate)	Monthly API recurring + usage revenue	$0	Track once API customers exist

API customer identities will always be anonymized in investor reporting for HIPAA-aligned handling.

6. Narrative Section (Above Dashboard)

The dashboard is the bottom of the update. Above it, once the company is operating:

Section 1: Wins (5 bullets max): real, dated wins only (e.g. design partner signed, adapter shipped, hire made, SOC 2 audit milestone). No win is reported before it has actually happened.

Section 2: Losses / Misses (3 bullets max): closed-lost opportunities with root cause, slipped timelines, supply-side shortfalls vs target.

Section 3: Asks: specific intros, beta testers, advisor gaps.

7. Dashboard Build Plan

Phase	Tool	Owner	Timeline
Month 0-3	Manual (Notion + Excel)	Founder	Manual updates
Month 4-6	Airtable + Looker Studio	Founder + ops hire	Auto-pulled from prod
Month 7-12	Internal admin dashboard	Eng	Live from `/api/metrics` endpoint
Month 12+	Investor portal (read-only)	Eng	Time-series + drill-down

The /api/metrics endpoint should expose ARR, runway, pipeline, and moat metrics in a clean JSON format that drives both the investor update and the internal team dashboard.

8. Investor Update Email Template

Subject: Rōvn [Month] Update: [headline status], Cash $X.XM, [headline win]

Hi all,

Quick highlights this month:

WINS:
- ...

MISSES:
- ...

ASKS:
- ...

DASHBOARD: [link to one-page PDF]

Giles

Keep email under 200 words. Dashboard is the data; email is the narrative. Pre-launch updates state pre-launch status plainly, no invented traction.

9. Quarterly Deep Dives

Once per quarter, after the relevant metrics exist, add to the regular monthly update: - Cohort retention chart: NRR/GRR by cohort - Cache hit-rate trajectory: compounding moat - Pipeline conversion funnel: sales efficiency - Burn multiple trend: capital efficiency

These are separate quarterly "investor reports," not part of the monthly update.

10. Risks Communication Protocol

The dashboard should never hide bad news. Specifically: - Runway dropping below 12 months → red flag on dashboard + email subject line - Lost design partner → "Misses" section, root cause analysis - Adapter coverage stalls → flag in product band

Investor trust at this stage is built on honesty, not heroics. That includes reporting pre-launch status honestly: zero customers, zero ARR, zero LOIs, zero paid pilots until those numbers genuinely change.

Note: Confirm with lead investors what additional metrics they want in their monthly update (varies by investor).

End of dashboard spec.

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 Bedrock under BAA · Anthropic Claude (Haiku 4.5) under BAA · zero-data-retention posture · no PHI in prompts.