Don't force one definition on every founder. Store each company's number as reported, with its label and source, then map it to a short list of portfolio-wide fields (revenue run-rate, net burn, cash, runway) using a written rule per company. Compare on the mapped fields and keep the raw number one click away.
This one kept coming up on my calls over the last two weeks, from fund finance leads, platform heads and a former fund administrator. The setup is always similar. One company reports GMV, one reports contracted ARR, one reports monthly revenue times twelve, and a consumer app reports daily actives. Someone then needs a single table for the quarterly review or the LP letter, and the table quietly lies (usually in the row nobody looks at twice).
Why this keeps coming up
A seed or Series A portfolio isn't uniform. Marketplaces, SaaS, hardware and consumer companies each run on a different number, and founders report the number they run on. That's healthy. You'd worry about a marketplace founder who didn't track GMV.
The trouble starts when the fund needs one view. Two things usually go wrong:
- Forced definitions. The fund sends every founder the same form with "ARR" on it. A marketplace founder types in annualized GMV, because that's the closest thing they have. Now the column mixes take-rate revenue with gross volume, and the portfolio average means nothing.
- Silent rewrites. Someone on the ops team "fixes" the number in a spreadsheet, turning GMV into an estimated net revenue. The original figure is gone, and so is the reasoning. Six months later nobody can say where the revenue number came from, including the auditor.
Public companies have the same problem with their own KPIs, and regulators have a view on it. The SEC's 2020 guidance on key metrics in MD&A expects a company to define each metric clearly, explain how it's calculated and, when the method changes, explain the change and consider recasting earlier periods. A fund isn't held to that standard for its internal review. But it's a good bar to borrow, because LPs increasingly ask the same questions. ILPA's portfolio company template, first built in 2019 to make portfolio metric disclosure to LPs consistent, is being revised now, and definitions are a big part of the work.
Step 1: Keep the number exactly as reported
Before you compare anything, store what the founder actually sent. For each value, keep:
- the number and its unit
- the founder's own label ("ARR", "GMV", "net revenue")
- the period it covers, and whether it's a monthly, quarterly or annualized figure
- the currency
- a link to the email, deck or model it came from
This is the step most teams skip, and it's the one that saves you later. If the raw value lives next to its source, any comparison you build on top can be checked and redone. If it doesn't, every number in your portfolio table is somebody's memory. (Provenance is the boring part, and it's the part that holds everything else up.)
Step 2: Pick a short common layer
Then decide what every company maps to. Keep it short, because every field you add is a field you'll chase founders for.
Which metrics should every portfolio company map to?
Keep the common layer small: cash on hand, net monthly burn, runway in months, a revenue run-rate, and headcount. Those five cover most portfolio reviews and LP reports, and almost every company can produce them. Leave each company's own headline metric (GMV, DAUs, contracted ARR) beside them, starred, without trying to force it into a shared column.
A table like this works for most early-stage funds:
| Common field | What it means | Typical sources it maps from |
|---|---|---|
| Cash on hand | Bank balance at period end | Balance sheet, update email, board deck |
| Net monthly burn | Operating cash out minus operating cash in, per month (excludes new funding) | Cash flow, "burn" line in an update |
| Runway (months) | Cash on hand divided by net monthly burn | Calculated from the two above, or founder-stated |
| Revenue run-rate | Recognized revenue for the latest month × 12 | Monthly revenue, MRR, recognized ARR |
| Headcount | Full-time employees at period end | Update email, HR export, LinkedIn as a last resort |
Cash, burn and runway compare well across almost any company, which is why they're the first thing most funds look at in a downturn. Revenue run-rate is the hard one. For a marketplace, map it from net revenue (take rate times GMV), not GMV itself, and keep GMV as the company's starred headline metric.
Don't try to map DAUs, pipeline or units shipped into a revenue field. Some companies don't have a comparable revenue number yet, and that's an honest blank, not a gap to fill with a guess.
Step 3: Write a mapping rule per company
For each company, write one short line per common field that says how you get from what they report to what you compare. For example:
- "Revenue run-rate = monthly net revenue × 12. Founder reports GMV and take rate separately; we use net revenue."
- "Revenue run-rate = recognized ARR from the board deck. Founder's 'contracted ARR' includes signed-but-not-live deals and is kept as the headline metric only."
- "Net burn = founder-stated burn. They report net, confirmed in the Q2 board deck."
Put the rule next to the company, not in a separate memo nobody opens. When the number looks odd next quarter, the rule tells you whether the number moved or the method did.
Two habits make this hold up:
- Derive, don't overwrite. The mapped value is a calculation on top of the raw value. If the founder's number changes, the mapped one changes with it.
- Label what's calculated. A runway you computed from cash and burn isn't the same as a runway the founder told you. Mark the difference in the table, so nobody tells an LP "the founder says 14 months" when it was your arithmetic.
What do you do when a company changes how it calculates a metric?
Treat it as a new series, not a correction. Keep the old numbers under the old rule, start the new ones under the new rule, and write a one-line note where they meet. If the founder can restate a few past periods under the new rule, store those as well, so the trend line compares like with like.
This happens more than people expect. A company moves from contracted to live ARR after a board conversation, or starts reporting net revenue instead of gross. If you just overwrite the history, the chart shows a company that shrank overnight. Keep both, and the conversation in the portfolio review is about the business, not about a broken spreadsheet.
How should you handle companies that report in different currencies?
Store every value in the currency the company reported it in, and convert only for comparison. Convert balances such as cash at the rate on the period-end date and flows such as revenue and burn at the average rate for the period, which is how IAS 21 handles translation. Keep the rate and its date next to the converted number.
The reason to keep the local value is that currency moves can look like operating changes. A European company whose revenue is flat in euros can look like it grew or shrank in dollars. When you see a jump, check the local-currency series first.
What this looks like in practice
The quarterly table ends up with two layers. The top layer is the common fields, which you can sort, filter and roll up across the whole portfolio: who has under 12 months of runway, who's burning faster than last quarter. The second layer is each company's own headline metric, starred, with its trend, which is what the partner on the board actually cares about.
Software can take on the extraction. It can pull numbers out of updates and decks, keep each one's label and source, and flag values that are missing, stale or out of range (that's the part Cura's metrics layer does). Writing and applying the mapping rules, and spotting a definition change, is still work for the fund team. And AI still misreads gross burn as net burn and bookings as revenue often enough that a person should confirm any mapped number before it goes to an LP. Let the model draft the mapping; a human signs it off.
You won't get one perfect definition of revenue across forty companies, and you don't need one. You need a table where every number says what it is, where it came from and how it got there.
Sources
- Commission Guidance on Management's Discussion and Analysis of Financial Condition and Results of Operations (Release 33-10751), U.S. Securities and Exchange Commission
- ILPA Portfolio Company Template v2.0, ILPA
- Portfolio Company Metrics Template, ILPA
- IAS 21 The Effects of Changes in Foreign Exchange Rates, IFRS Foundation