Finance & RevOps
Board-ready ARR, NRR, and reconciliation. Lineage finance can defend without a data ticket.
Department · Finance
From three revenue numbers to
one certified close.
Controllers, FP&A, and the board share formulas, lineage, and owners. Not Slack archaeology the night before review.
Overview
Finance cannot close on three versions of the same number.
Product analytics, billing, and the board pack disagree because trial, convert, and ARR are defined in three tools. Reconciliation becomes a Monday tax. Audit becomes a reconstruction project.
Company Brain gives Finance a certified close path on the stack you already run. Formulas have named owners. Lineage sits on every figure. Exceptions have people, not a queue. The pack is a cut of the same objects the close team already trusts.
IT still owns the warehouse. Finance owns the number. Metroflow is the layer that keeps those two stories from drifting apart.
- Controllers and accounting ops running month-end
- FP&A building forecasts on the same grain as actuals
- RevOps defending ARR and NRR in the QBR
- Audit and the audit committee walking a number back to source
Days, not weeksClose from one board instead of twelve exports
One ARRSame ID in Looker, the deck, and chat
Audit-readyColumn, join, and filter on every figure
Company Brain
What Company Brain is, and how it helps Finance.
Company Brain is the cited layer above billing, warehouse, and BI. It does not replace the ledger. It makes every figure walkable: formula, owner, lineage, and exception.
Finance stops reconciling three extracts before every review. The close, the forecast, and the board pack cut from the same objects.
- Ask how NRR is calculated and get the formula, exclusions, and FX with citations.
- A 2% delta opens the spec, not a war room.
- Audit walks a number back to source without a reconstruction project.
- Agents only answer from certified metrics. They do not invent a column.
Use cases
Go from conflicting books to one trusted close
Month-end
End the Monday reconciliation tax
GL, billing, product analytics, and the warehouse sit in one context. Variances surface with owners. The close pack is a view, not a rebuild the night before the meeting.
- Certify ARR and NRR once, with a named owner and lineage from events to warehouse models.
- Company Brain answers why convert dropped from governed context, not three private dashboards.
- Unmatched, late, and material items sit on a board with a person and a due date.
Audit-ready numbers
Every slide traces to a certified KPI
When finance flags a 2% delta, you open the spec. You do not open a war room. The pack is the same objects the close already signed.
- Reconciliation alerts when a model or definition drifts.
- Exportable lineage for auditors and the audit committee.
- No rebuild in slides the night before the board.
No ticket required
Ask in plain language. Get cited proof.
Walk through how net revenue retention is calculated: formula, exclusions, FX. Citations travel with the answer.
- Same certified ID in Looker, the board deck, and chat.
- Rogue explores get deprecated instead of argued forever.
- Thin context is said out loud. The assistant does not invent a column.
FP&A
Scenarios that do not fight last close
Drivers sit on the same grain as actuals. A scenario is a named assumption, not a second workbook. Variance is explained, not argued.
- Shared grain across actuals and scenarios.
- Named assumptions with a change trail.
- Variance that Finance and Product can both walk.
Control
Policy as named rules, not Slack folklore
Recognition, allocation, and cutoff live as versioned rules. When policy changes, the graph records who and when.
- Versioned policy on the objects Finance already uses.
- Named allocations with owners.
- A change trail the auditor can walk.
AP / AR
Payables and receivables with the same truth
Aging, disputes, and cash forecast share definitions. Collections and treasury stop arguing about which extract is current.
- Shared aging and dispute trail.
- Cash forecast from one grain.
- Exceptions with named owners on the board.
How it lands
One brain. Shared by finance and the stack.
On your stack
Billing, warehouse, and BI stay put
Metroflow sits above Stripe, Snowflake, dbt, and Looker. Metadata only. Row data stays in your network.
- Connect sources you already run. No rip-and-replace.
- Name the grain: account, entity, period, cost center.
- Document one close path end to end.
Governed change
Definition changes leave an audit trail
Finance signs off. Product cannot silently ship a new revenue explore. Owners, versions, and deprecation sit on every KPI.
- Certify ARR, NRR, and the board pack IDs.
- Pre-merge impact when dbt models feeding the close change.
- Rogue explores retired or flagged.
Cited, not guessed
WBR and close without a data ticket
Company Brain separates pipeline delay from definition drift in minutes. Answers include catalog and lineage citations.
- Close board is the work, not a screenshot of the work.
- No write access until you approve it.
- Audit pack is a cut of the same objects.
Run
Every close starts from proof
Freshness, volume, and schema sit on the same objects people already use. Alert the owner, not the whole company.
- Stale close inputs surface before standup.
- Policy versions stay visible after the person who wrote them leaves.
- New entities inherit the same grain, not a new religion.
Resources
Finance resources
Preview a playbook in the browser, download it, or read the two pieces written for this page.
Playbooks
Exec + Finance + Product
One board narrative. Product, finance, and leadership stop bringing three books to the same meeting.