A 41,775-row dataset audited line-by-line.
A founder needed to know whether the margin claims in his deck would survive being asked to show his work. The honest answer required forty-one thousand rows of it.
41,775
rows audited
line-by-line, no sampling
36
columns reconciled
each tied to a documented formula
3
discrepancies caught pre-meeting
before CFO contact
4 wks
to defendable
from kickoff to closing the meeting
— The Brief
A pricing thesis was built on top of a targeting dataset that nobody had actually walked the entire length of. The CFO conversation was four weeks out. The downside of being wrong was not "smaller deal."
— Diagnosis
The dataset was clean enough to sell against and dirty enough to embarrass with. A line-by-line forensic was the only acceptable answer, with every metric in every artifact reproducible from a single command.
— How I Read It
First-person · operator's note
My first read was that the founder didn't need a flashier report — he needed to walk into a CFO meeting against arithmetic, not narrative. So the work wasn't to make the numbers prettier; it was to make every number reproducible from the source CSV with one command. I froze the canonical file and hashed it on day one so any later disagreement could be resolved by re-running, not re-arguing. That discipline cost me speed in week one and bought me certainty in week four. When three discrepancies surfaced against the deck, I didn't soften them — I documented them. Founders defend numbers they can derive themselves; that's the only kind worth charging against.
— Process
- 01Week 1
Freeze
Canonical CSV named, hashed, frozen. Every later number derives from it.
- 02Week 1–2
Walk
Line-by-line through 41,775 rows. Outliers, defaults, and gaps tagged.
- 03Week 3
Reconcile
Every figure in the deck cross-checked against the forensic. Three corrections.
- 04Week 4
Document
Founder-grade documentation written so the operator can defend each number alone.
— The Build
01 · Single source of truth
One canonical CSV named, hashed, and frozen. Every downstream document derived its numbers from it via documented formulas.
The CFO walked into the meeting against arithmetic, not narrative.
02 · Cross-sheet reconciliation
Every figure that appeared in the deck cross-checked against the forensic. Three discrepancies found and fixed before the meeting.
03 · Founder-grade documentation
A second-pass documentation set written for a developer reader — so the operator could defend each number without me in the room.
"Forty-one thousand seven hundred seventy-five rows defended in a single meeting window."
— Artifacts Delivered
- 01Forensic audit (PDF + working spreadsheet)
- 02Single source-of-truth CSV (frozen + hashed)
- 03Margin reconciliation document
- 04Compensation methodology document
— Outcome
The CFO conversation closed inside the original meeting window. The number that mattered survived first contact with scrutiny — because the work to defend it had already been done.
— Receipts
- ✓CFO conversation closed inside the booked window
- 0numbers walked back post-meeting
- 1×command reproduces every metric — still does