VC portfolio monitoring tools were built for fund administration — capital calls, valuations, LP reporting. They're good at tracking the investment. They're not designed to track the SaaS operating engine underneath it. When your portfolio is 80%+ SaaS, that gap isn't a minor inconvenience — it's the difference between catching a retention problem in March and discovering it in the Q2 board deck. This article maps the current tool landscape, identifies where it falls short for SaaS-heavy portfolios, and lays out what a SaaS-native monitoring approach looks like.
What tools do VCs use to monitor SaaS portfolio companies?
The current landscape (Visible, Carta, Standard Metrics, Affinity)
Most VC portfolio monitoring today runs through a handful of platforms: Visible, Carta, Standard Metrics, and Affinity. Each covers a different slice of the problem. Visible automates data collection from portcos via quarterly request templates. Carta tracks cap tables and fund administration. Standard Metrics connects to accounting systems and pulls financials. Affinity manages deal flow and relationship intelligence.
All four are designed primarily for collectingdata from portfolio companies. Founders fill out a form, upload a spreadsheet, or grant read access to their accounting tool. The data arrives quarterly, sometimes monthly. It's self-reported, self-calculated, and rarely verified against the billing system that generated the revenue in the first place.
The gap isn't that these tools are bad — they're excellent at fund administration and relationship management. The gap is that none of them are designed to verifythe operating metrics they collect. A founder reports 15% net revenue retention growth. Is that calculated from subscription events, or estimated from a revenue delta? Does it include annual contracts normalized to monthly, or just monthly charges? The tool doesn't know, and neither does the portfolio manager reviewing the report.
| Feature | Visible | Carta | Standard Metrics | Affinity |
|---|---|---|---|---|
| Automated data collection | ||||
| Cap table / fund admin | ||||
| Billing-verified MRR | ||||
| NRR / GRR calculation | ||||
| Cohort retention curves | ||||
| Daily data refresh | ||||
| Cross-portco benchmarks | ||||
| Relationship / deal CRM |
The SaaS-native monitoring gap
Fund admin tools vs operating metrics tools
Fund administration tools answer questions about the fund: how much capital is deployed, what's the current mark, what does the return profile look like at exit. Operating metrics tools answer questions about the company: is MRR growing, are customers retaining, is the unit economics engine healthy. These are fundamentally different categories, but VCs routinely conflate them because the same quarterly data collection covers both.
A quarterly request template asks for MRR, ARR, headcount, burn rate, and cash runway. That data feeds the fund admin view (mark the portfolio) and the operating view (assess company health) simultaneously. The problem is cadence and verification. Fund marks can tolerate quarterly data with a 30-day lag. Operating metrics lose diagnostic value at quarterly resolution — a churn spike in month one is invisible until the quarter closes.
What VCs with majority-SaaS portfolios actually need
A VC with 15–25 SaaS portcos needs a different layer than fund admin. They need MRR composition per portco — not just the top-line number, but the waterfall showing new, expansion, contraction, and churn. They need net and gross retention calculated from subscription events, not estimated from revenue deltas. They need efficiency metrics — LTV:CAC, burn multiple, CAC payback — derived from actual billing and spend data.
Most importantly, they need these metrics calculated consistently across every portco. When Portco A reports 110% NRR and Portco B reports 105%, the comparison is meaningless unless both numbers use the same definition, the same cohort window, and the same treatment of annual contracts. Consistent taxonomy is the prerequisite for portfolio-level analysis, and self-reported data almost never delivers it.
SaaS metrics VCs should monitor per portco
Revenue growth and quality (MRR, NRR, expansion share)
MRR is the starting point, but it needs decomposition. Total MRR growing 5% month-over-month can mask very different engines: one portco might be growing through new logos with minimal expansion, while another is expanding aggressively into its base with flat new-logo acquisition. The risk profiles are different, and the interventions are different.
Net MRR retention is the single metric that tells a VC whether a portco's existing customer base is growing or shrinking on its own. Above 110%, the portco grows from its base alone — new sales are additive. Below 95%, the portco is running on a treadmill, acquiring new customers just to backfill decay. Expansion share — expansion revenue as a percentage of beginning-of-period MRR — isolates the upsell engine from the retention story.
Net MRR Retention
Revenue retained from existing customers including expansion, contraction, and churn.
Retention signals (churn rate, GRR, cohort decay)
Customer churn rate is the clearest product-market fit signal in a VC's toolkit. Monthly logo churn above 3% in a B2B SaaS portco is a structural problem — the company is losing more than a third of its customers annually. Below 1.5%, the product has stickiness. Between those bounds, context matters: segment mix, contract length, and ACV all affect what "normal" looks like.
Customer Churn Rate
Percentage of customers lost in a given period — the clearest signal of product-market fit.
Gross revenue retention strips out expansion to show pure contraction and churn. A portco with 120% NRR and 82% GRR has a strong upsell motion masking a serious retention problem. When expansion slows — as it does in market downturns — the GRR number becomes the revenue trajectory. VCs who only track NRR miss this until it's too late.
Cohort retention curves matter more than aggregate numbers for portfolio evaluation. A portco's aggregate NRR might be 108%, but if the last three cohorts retain at 94% while legacy cohorts retain at 118%, the aggregate is a lagging indicator. Cohort curves surface degradation 6–12 months before it appears in the top-line number.
Efficiency indicators (LTV:CAC, burn multiple)
LTV:CAC is the unit economics gate for portfolio-level capital allocation. A portco with 5:1 LTV:CAC has room to accelerate growth — the VC should be asking why they aren't spending more. A portco with 1.8:1 needs efficiency work before additional capital makes sense. The ratio drives follow-on investment decisions, but only if it's calculated from real acquisition costs and verified retention-based lifetime value.
Burn multiple — net burn divided by net new ARR — captures efficiency at the company level. Below 1.5x is efficient growth. Above 3x means the portco is spending more than $3 for every $1 of new ARR, which is only sustainable with significant runway. For VCs managing reserve allocation across 15+ portcos, burn multiple is the fastest triage metric: it answers "is this company using our capital efficiently?" in a single number.
From self-reported data to verified metrics
The biggest gap in VC monitoring isn't tools — it's data quality. Self-reported metrics arrive with implicit assumptions baked in. One portco calculates MRR including annual contracts on an accrual basis. Another uses cash-basis monthly charges. A third includes setup fees. All three report a number called "MRR," but they're measuring different things. When those numbers sit side by side in a portfolio dashboard, the comparison is fiction.
Verified metrics start at the billing system. When MRR is calculated from actual subscription events in Stripe — invoices, charges, refunds, subscription changes — the definition is enforced by the data source, not the reporter. Every portco's MRR is calculated the same way: from the same event types, with the same normalization logic for annual and quarterly contracts, using the same treatment of trials, discounts, and prorations.
This isn't about distrust. Founders aren't misrepresenting their metrics intentionally — they're calculating them differently because there is no universal standard. Billing-system verification removes the ambiguity. The number is the number, derived from the same source and the same logic for every portco in the portfolio.
LP reporting from verified portfolio data
Quarterly LP updates backed by billing data
LP updates typically include a portfolio summary with key metrics per portco: ARR, growth rate, burn, and a qualitative assessment. When those metrics are verified from billing data, the GP can present them with confidence — no caveats about self-reporting methodology, no asterisks about definition inconsistencies. The numbers are the numbers.
A billing-verified portfolio view also enables trend reporting that LPs increasingly expect. Rather than a point-in-time snapshot, the update can show 12-month NRR trajectories, cohort retention curves, and efficiency trends per portco. That level of detail signals operational depth to LPs and differentiates the fund in a competitive fundraising environment.
The cadence benefit compounds. With daily-refresh data, the quarterly LP report is a snapshot of a continuously updated view — not a scramble to collect, reconcile, and format data from 20 portcos in the two weeks before the report is due. The report assembly time drops from days to hours because the data is already normalized, current, and comparable.
How North Metric works for VC portfolio monitoring
North Metric connects directly to each portfolio company's Stripe account and calculates every SaaS metric from billing events. MRR, NRR, GRR, LTV:CAC, churn by type, cohort retention — all derived from the same subscription data, using the same definitions across every portco. No spreadsheets, no quarterly data requests, no definition mismatches between companies.
For VC portfolio managers, this means a single dashboard across all portfolio companies with daily-refresh data. When a portco's net retention dips below the portfolio median, it surfaces the next day — not in the next quarterly update. When a pricing change at another portco lifts expansion revenue, the effect is visible within the billing cycle.
Stage-matched benchmarks contextualize every portco's metrics against industry percentiles. A portco at the 30th percentile for gross retention isn't just "below target" — it's quantifiably behind its peers, with a trend line showing whether the gap is closing. That precision turns portfolio reviews from qualitative discussions into data-driven triage.
Fund admin tools track the investment. North Metric tracks the recurring revenue engine that drives the investment's value — verified, normalized, and refreshed daily across every company in the portfolio.