GoDo Platform
Workflows Provable Deployment FAQ For law firms
Book a working session
Common Ledger · For venture funds — the quarterly close & the annual audit

One ledger for your entire fund. Every number provable.

Not another portfolio dashboard. Common Ledger collects the quarter from your portfolio companies' email replies, extracts every figure with its verbatim source attached, runs your valuation policy through the preference stack, and assembles the LP update, the Schedule of Investments handoff, and the audit binder — from one tamper-evident record. It flags a gap instead of inventing a number.

Book a 20-minute working session See it on sample data
AI proposes. Your team signs.
Common Ledger — Q2 2026 close
TAMPER-EVIDENT LEDGER · SEQ 4,812
Collection — 24 of 31 companies in
Arcadia Robotics✓ income stmt · balance sheet · cap table
Meadow Healthnudged Tue — week 3 of chase
Quill AIsilent ×2 — escalated to partner
Ferrous Systems✓ raised — SPA + new cap table filed
Attachments pulled from founder replies, matched to company and quarter, filed, and ticked off — no hand-downloading, no drag-and-drop into Drive.
Evidence drawer — every figure
Q2 revenue — $1.24M
Source: income statement, p.2, "Total revenue" · proposed by extraction · verified by HD · ledger #4,812
Fair value — held at last round
Policy: priced round 14 months ago, inside the 18-month window · waterfall through the preference stack, rebuildable on demand · awaiting second approver
No source, no figure. Blanks stay blank.
The quarter, today

One person's inbox holds the fund's financial record.

A month after quarter-end, someone on your team emails thirty portfolio companies, chases the silent ones, downloads the attachments, files them into folders, and re-keys the numbers into a workbook. Then, at year-end, the auditors ask where each number came from — and whether it changed.

The collection is a chase
Request emails, weekly follow-ups, escalations, attachment archaeology — weeks of one operator's quarter, every quarter. And it all stops when that person is out.
Valuations live in spreadsheets with no provenance
The waterfall is a formula in a workbook. Which cell of which cap table fed it is tribal knowledge. When a founder re-sends a corrected cap table, nothing flags what just went stale.
Audit season is re-authorship
Auditors rebuild the waterfalls independently and ask "where did this come from, and has it changed?" Answering means re-deriving a year of work from folders and email threads.
What it runs

From founder reply to audit binder — one record, six workflows.

Each one writes to the same structured record: one entry per company per quarter, every figure with a source pointer, every action on the ledger.

★ 01 · Collection & chase
The quarter collects itself
Per-company requests for exactly the documents that apply — financials for everyone, SPAs and cap tables only for companies that raised. Weekly nudges for the silent, escalation to a partner after the chase runs its course. A shared status grid replaces the tracking spreadsheet.
02 · Inbox ingestion
Reaches into the inbox so nobody has to
Connect the inbox once. Attachments on founder replies are matched to the right company and quarter, filed, and ticked off the collection grid automatically. A login-free upload portal covers teammates and fund admins who'd rather drop files than forward email.
03 · Extraction with provenance
Every figure arrives with its source attached
Income statements, balance sheets, and cap tables become structured figures — revenue, cash, share counts — each stamped with the verbatim place it came from, queued for one-click human verification. The product never displays a number it didn't truly derive.
04 · Valuation & waterfall
Your policy, computed — not guessed
Each company routes down your valuation policy tree — held at zero, at cost, at last round inside the window, or on comps — then the waterfall distributes through the preference stack to your per-share position. Deterministic code: rerun it and get the same answer. A human signs every mark.
05 · LP updates, SOI & handoff
Reporting assembled from the verified record
Per-fund LP update drafts, LP-call prep, and a structured Schedule of Investments handoff for your fund administrator — generated from figures that already carry their sources, instead of re-keyed into yet another document.
06 · The audit binder
Year-end becomes assembly, not authorship
The binder self-assembles: every figure, its source document, who verified it, who approved it, and the ledger proof that none of it was silently edited. What used to be a quarter of reconstruction becomes an export.
Provable by construction

An auditor can rebuild every number. Nobody can quietly rewrite one.

These aren't policies in a handbook. They're properties of the software — the same "private, provable" architecture GoDo builds for law firms, applied to fund reporting.

Hash-chain audit ledger
Every consequential action is appended to a per-firm hash chain with a monotonic sequence. "Has this changed since Q2?" always has a provable answer — rows can't be edited after the fact, including by admins.
Provenance to the line
Every figure stores the verbatim source it came from — down to the statement line or spreadsheet cell. "Where did this number come from?" is one click, not an afternoon.
Four-eyes by construction
Sign-offs and deletions require a distinct second approver. The software will not let one person — or the AI — complete them alone. Not a policy. A precondition.
Deterministic engines
Waterfalls and the valuation policy tree are computed code, not model output. The AI extracts and drafts; it holds no verify or sign authority. AI proposes. Your team signs.
Who it serves

Built for the whole reporting chain.

The same record serves everyone who touches the quarter — which is exactly why it pays for itself.

GPs & CFOs
The quarter closes in days instead of weeks, without hiring for it. LP questions get answered from the record, not from memory. The audit stops consuming Q4.
Fund admins & outsourced CFOs
A structured, SOI-ready handoff instead of email archaeology — and one system that runs the same close across every fund client you serve.
Auditors
Test against a provable record: sample and verify instead of reconstruct. Sources attached, approvals attributed, a hash chain that answers "has this changed?" on its own.
LPs
Updates that arrive on time, marks that trace to source documents, and an audit that goes quietly. Confidence in the numbers is the product.
On who pays: quarterly reporting and audit tooling commonly sits with fund expenses under the LPA rather than the management company's P&L — ask your fund counsel where Common Ledger belongs for your fund.
Where it runs

Cloud tenant when you want speed. Sovereign when the data can't leave.

Cloud. Your firm gets an isolated tenant — organization scope is set by the session, by construction, so no request can read or write across firms. Email access rides GoDo's already-approved Google connection layer; Google tokens live there, never inside the app.

Sovereign. The same product runs on hardware your firm owns, with local models and a per-install member whitelist. Cap tables, LP lists, and fund financials never leave the building — and are never pasted into a third-party cloud AI to "check a number." It's a configuration switch, not a rebuild: start in the cloud and move on-prem when the fund's posture demands it.

Secured by GoDo. Common Ledger is built and operated on the GoDo platform — the same private, provable architecture behind our work for law firms handling confidential VC and corporate matters.

Deployment facts
ModesIsolated cloud tenant · sovereign on-prem
Tenant isolationOrg-scoped by construction
Google accessVia GoDo's approved connection layer
AI authorityProposes only — no verify/sign power
Audit ledgerAppend-only hash chain, per firm
ApprovalsDistinct second approver, enforced
BackupsEncrypted, restore-verified
Economics

Priced against the close, not per seat.

Weigh it against what the quarter costs today: weeks of an operator's time chasing and re-keying, audit-prep re-derivation at year-end, and the back-and-forth your fund administrator bills for. Flat monthly pricing per firm, covering every fund — no per-seat licenses, no usage uplift. Most firms start with a pilot quarter on one fund, run alongside their current process, and switch when the binder proves itself.

Benchmark: a fraction of one ops hire — before counting the audit-prep bill.
Talk through your quarter →
FAQ

Straight answers.

Does the AI make valuation calls?

No. The valuation policy tree and the waterfall are deterministic code — rerun them and get the same answer. The AI extracts figures and drafts documents; it holds no verify or sign authority. A human verifies every figure, and sign-offs require a distinct second approver. AI proposes. Your team signs.

Where does our data live?

In cloud mode, in your firm's isolated tenant — organization scope comes from the session, by construction, so nothing reads or writes across firms. In sovereign mode, on hardware your firm owns, with local models and a per-install member whitelist. Google tokens live in GoDo's approved connection layer, never inside the app. Your data is not used to train models.

A founder re-sends a corrected cap table. What happens?

It's matched to the company and quarter and filed like any other arrival, and the figures derived from the old version are flagged for re-verification. The ledger records the change — who accepted it and when. Nothing is silently overwritten, which is exactly what your auditor will ask about.

Does it replace our fund administrator or auditor?

No — it feeds them. Your fund administrator gets a structured, SOI-ready handoff instead of a folder of PDFs; your auditor gets a binder and a rebuildable record instead of a reconstruction project. What it replaces is the chase spreadsheet, the inbox archaeology, and the re-keying in between.

What does onboarding look like?

Minutes, not a data-migration project. The setup wizard pre-fills your portfolio from public data, takes a spreadsheet import for the rest, and connects the inbox. Your first close runs with us alongside — on your real quarter, next to your current process, so nothing is at risk while it earns your trust.

We're a fund administrator / outsourced CFO. Is this for us?

Yes — arguably most of all. You run the same collection, extraction, and close across many fund clients; Common Ledger runs it as one system with a provable record per fund. Talk to us about multi-fund deployment.

Bring your worst quarter-close story.

Walk us through how your team collects, values, and reports today — and what last audit season cost you. We'll show you the same quarter running on Common Ledger, on sample data, in twenty minutes.

Book a 20-minute working session See it on sample data
No credit card. Set up in minutes. Secured by GoDo.
GoDo Platform
Workflows Provable Deployment FAQ GoDo for law firms
© 2026 GoDo Platform. All rights reserved.