When a VC partner sends their analyst into your data room, the first thing they do is pull your Stripe billing data and cross-check it against your Salesforce pipeline. If the numbers don’t match — and for most SaaS companies at $20M–$50M ARR, they don’t — the conversation shifts from valuation to credibility. The 3–8% revenue discrepancy that exists between billing and CRM at most companies is the single most common diligence failure for Series B fundraises.
This guide covers the specific revenue metrics VCs request during due diligence, how to prepare retention cohort analysis that survives independent verification, and how to produce all of these metrics from a single reconciled view — replacing the manual assembly of ProfitWell + Baremetrics + CRM exports that currently costs your finance team 2–5 days per month.
What VCs Actually Request During Due Diligence
Institutional investors at Series B have a standardised diligence checklist. They’re not looking at your dashboards — they’re requesting raw data, recalculating your metrics independently, and comparing their numbers against your board deck. Here are the five categories they request and what “good” looks like for each.
1. ARR Composition Waterfall
What they request: Monthly breakdown of new business, expansion, contraction, and churn revenue for the trailing 18–24 months.
What they check: Whether the total reconciles between your billing system and CRM at the account level. A $30M ARR deck that yields $28.2M when calculated from Stripe data means a $1.8M gap that dominates the diligence conversation. They also check whether the composition is sustainable — a company where 60% of new ARR comes from three large deals is a concentration risk regardless of the headline number.
What makes it board-ready: The waterfall must use account-level data that’s been reconciled across billing and CRM. Mid-cycle amendments in Salesforce that don’t trigger Stripe subscription changes, customers paying via invoice instead of through the billing system, and accounts that expanded through separate product lines — all of these create drift that billing-only tools miss entirely.
2. NRR and GRR by Segment
What they request: Net revenue retention and gross revenue retention by quarter, segmented by customer tier (enterprise, mid-market, SMB).
Why segmentation matters: A blended NRR of 112% can hide two very different realities. Enterprise NRR at 130% with SMB NRR at 85% tells a fundamentally different story than a flat 112% across all segments. VCs evaluate segment dynamics because they predict how retention will evolve as your customer mix changes with scale.
What they check: They recalculate NRR from your raw data. If your billing system records a $5K expansion that Salesforce doesn’t reflect because the opportunity wasn’t updated, the investor gets a different NRR than your deck. They also check GRR alongside NRR — GRR below 85% with high NRR signals that expansion is masking a churn problem, which experienced investors recognise immediately as a risk pattern.
3. Cohort Retention Curves
What they request: Revenue retention by quarterly cohort for 6–8 cohorts. Logo retention alongside revenue retention. Both overlaid on a single chart so trend direction is immediately visible.
Why this is the highest-signal metric for VCs: Cohort analysis separates real product-market fit from growth-funded retention. Three things signal value:
- Improving cohorts. If your Q3 2025 cohort retains better at month 6 than Q1 2025 did — that’s evidence your product, onboarding, and customer success are getting better. This is the strongest compounding signal a VC can find.
- Cohort flattening. Healthy cohorts lose customers in the first 3–6 months and then flatten. Continued decline past month 12 signals a structural problem that won’t be fixed by a larger sales team.
- Within-cohort expansion. A cohort that starts at $200K MRR and grows to $240K over 12 months tells a far stronger story than one that holds at $190K — it shows a working land-and-expand motion.
The cross-system challenge: Billing-only tools (ProfitWell, Baremetrics, ChartMogul) can show cohort retention by signup date and plan. They cannot segment cohorts by acquisition channel, deal size, CSM coverage, or product engagement — the dimensions VCs ask about during diligence. These cross-system cohort views require data from billing, CRM, and product analytics in one place.
4. Customer Concentration Analysis
What they request: Revenue from top 10, top 20, and top 50 accounts. The churn impact if the largest customer leaves.
Why it matters for valuation: If your top 5 accounts represent 40% of ARR, the investor is pricing in the risk that any one departure materially impacts the business. Concentration below 10% for the top account and below 25% for the top 10 is the typical comfort zone at Series B.
5. Expansion Revenue by Motion
What they request: Expansion revenue broken down by type — seat-based growth, cross-sell, upsell to higher tiers, and usage-based expansion.
Why it matters: VCs want to see a repeatable expansion engine, not one-off enterprise deals inflating the numbers. If 80% of expansion comes from three accounts negotiating multi-year deals, that’s not a motion — it’s luck. Repeatable expansion (seats, usage, cross-sell) at 30–50% of new ARR signals a capital-efficient growth engine.
Preparing Retention Cohort Analysis for the Data Room
Cohort analysis is where most companies stumble during diligence. The metric itself is straightforward — the challenge is producing cohort curves from data that’s consistent, reconciled, and defensible under scrutiny.
Step 1: Lock Your Cohort Definitions
Before building a single chart, document your cohort methodology. Which date defines the cohort — contract start date, first payment date, or opportunity close date? How do you handle reactivations — new cohort or return to the original? What counts as churn — billing cancellation, no payment for 90 days, or CRM opportunity marked closed-lost?
VCs will ask these questions. If your methodology changed mid-period, your cohort curves aren’t comparable across time — and the analyst will flag it. Pick a definition, document it, and apply it consistently across all 6–8 cohorts.
Step 2: Reconcile the Underlying Revenue Data
Your cohort curves are only as accurate as the revenue data behind them. If Stripe says Account X pays $15K/month and Salesforce says the deal value is $12K/month, your cohort retention for that account is wrong in at least one system. Multiply this by 50–200 accounts and the aggregate error compounds.
The reconciliation checklist:
- Match every billing subscription to a CRM account. Orphaned Stripe subscriptions with no Salesforce counterpart are common after mergers, plan migrations, and manual billing changes.
- Validate MRR agreement at the account level. Flag every account where billing MRR and CRM deal value differ by more than 5%.
- Resolve mid-cycle discrepancies. A customer who upgraded mid-quarter in Stripe but whose Salesforce opportunity wasn’t updated until renewal creates a timing gap that affects cohort calculation for that period.
Step 3: Build Both Logo and Revenue Retention Curves
VCs want both views because they tell different stories. Logo retention shows customer satisfaction depth — are people staying? Revenue retention shows commercial health — are they spending more? A company with 88% logo retention but 118% NRR is losing some customers but expanding significantly with those who stay. That’s a very different story from 95% logo retention with 102% NRR.
Step 4: Prepare the Cross-Dimensional Cuts
During diligence calls, VCs will ask for cohort data segmented by dimensions that billing-only tools cannot produce:
- By acquisition channel: Do inbound customers retain better than outbound?
- By deal size: Do larger contracts have higher retention?
- By product engagement: Do accounts using 3+ features retain better than those using 1?
- By CSM coverage: What’s the retention difference between managed and unmanaged accounts?
These questions require data from billing, CRM, product analytics, and customer success systems in one place. If you can answer them in real time during the diligence call instead of following up in two days with a spreadsheet, it signals operational maturity that investors reward.
The Manual Assembly Problem: ProfitWell + Baremetrics + CRM Exports
Most founders and CFOs at the Series B stage produce board metrics through a patchwork of tools that each see a piece of the picture:
- ProfitWell or Baremetrics for billing-side MRR, churn, and basic cohort analysis from Stripe data
- Salesforce reports or HubSpot exports for CRM-side deal values, pipeline, and account attributes
- ChurnZero or Gainsight for health scores and CS workflow data
- Amplitude or Mixpanel exports for product usage data
- Spreadsheets to reconcile all of the above into board-ready numbers
This workflow has three problems that become acute during due diligence:
- Time cost. The manual reconciliation cycle takes 2–5 days per month for a $30M+ ARR business. During a fundraise, when investors are requesting ad hoc cuts and follow-up analyses, this becomes a bottleneck that slows the process.
- Error accumulation. Each tool has its own entity model, its own definition of “active account,” and its own handling of edge cases. A customer that merged two accounts in Stripe but is still two opportunities in Salesforce creates a discrepancy that cascades through every metric built on top of it.
- No audit trail. When an investor asks “how did you arrive at this NRR number?”, the answer is “we exported data from three tools and reconciled in a spreadsheet.” There’s no automated trail showing exactly which accounts drove each component of the calculation.
Board Reporting Tools Compared: Eru vs Baremetrics vs ProfitWell vs Looker
For the board reporting and VC due diligence use case, here’s how the main tool categories compare.
| Capability | Baremetrics | ProfitWell (Paddle) | Looker | Eru |
|---|---|---|---|---|
| Data sources | Single billing system (Stripe, Chargebee, etc.) | Paddle billing data only (post-acquisition) | Any database or warehouse (requires modelling) | Billing + CRM + support + product analytics |
| NRR/GRR calculation | From billing data only | From billing data only | Custom-built by data team | Cross-system reconciled with audit trail |
| Cohort analysis dimensions | Signup date and plan only | Signup date and plan only | Flexible (if modelled by data team) | Any dimension: channel, deal size, CSM, engagement |
| Billing–CRM reconciliation | No — billing only | No — billing only | Possible with engineering effort | Automatic via truth graph |
| VC due diligence readiness | Partial — billing metrics only, no audit trail | Partial — billing metrics only, no audit trail | Depends on implementation quality | Full — pre-reconciled with audit trail |
| Cross-dimensional cohort cuts | No — single-source data | No — single-source data | Yes (requires data team to build) | Yes — self-serve from reconciled data |
| Customer health scoring | No | No | No (requires separate tool) | Yes — multi-source behavioural |
| Setup time | Minutes | Minutes | Weeks to months (data engineering) | Minutes (OAuth connections) |
| Ongoing maintenance | Low | Low | High (data team required) | Low |
| Typical cost ($50M ARR, 200 accounts) | $5K–$20K/year | Free tier + paid features | $50K–$150K/year + data team salary | Contact for pricing |
Why Billing-Only Tools Fall Short for Due Diligence
Baremetrics and ProfitWell solve the “calculate SaaS metrics quickly” problem well. Connect Stripe, get MRR, churn, LTV, and basic cohort charts in minutes. For early-stage companies with a single billing source, they’re a pragmatic choice.
The limitation becomes critical during due diligence. At $20M+ ARR, revenue data diverges across systems. Mid-cycle contract amendments in Salesforce that don’t trigger Stripe subscription changes. Customers who pay via invoice outside the billing system. Accounts that expanded through separate product lines. These are normal at scale — and billing-only tools are blind to all of them. When a VC’s analyst recalculates your NRR from combined billing + CRM data and gets a different number than your ProfitWell dashboard, the gap erodes trust at the worst possible moment.
Why BI Tools (Looker) Require Too Much Infrastructure
Looker can model any metric from any data source with full flexibility. The problem is that it requires a data team to build, maintain, and validate the models. For a $30M ARR company without dedicated data engineering, Looker represents a six-figure software commitment plus $150K–$250K in headcount. And Looker doesn’t reconcile data — if Stripe and Salesforce disagree on an account’s revenue, Looker faithfully shows both numbers without flagging the discrepancy. The reconciliation logic has to be built and maintained by your team.
How Eru Replaces the Manual Assembly
Eru is the connective layer that replaces the manual ProfitWell + Baremetrics + CRM export workflow. Eru’s truth graph matches entities across Stripe, Salesforce, and other revenue systems — identifying where numbers diverge and producing a single reconciled view.
For VC due diligence specifically, this means:
- NRR and GRR are pre-reconciled. The numbers reflect billing and CRM data together, not one or the other. Your board deck NRR is the same number a VC’s analyst will calculate from your raw data.
- Cohort analysis is cross-dimensional. Segment by acquisition channel, deal size, CSM coverage, product engagement — not just signup date. Answer diligence questions in real time instead of following up with a spreadsheet.
- Revenue drift is caught automatically. When Stripe and Salesforce disagree on an account’s value, Eru surfaces the discrepancy before it reaches your board deck — or your investor’s analyst.
- Every number has an audit trail. When an investor asks “how did you arrive at this NRR?”, the answer is a reconciled cross-system calculation, not a spreadsheet. The audit trail shows exactly which accounts contributed to each component.
Setup takes minutes via OAuth connections — no engineering, no implementation partner, no 12-week onboarding. The first reconciled metrics are available within hours, not weeks.
The CFO’s Due Diligence Preparation Checklist
If you’re a founder or CFO preparing for a Series B fundraise, here’s the timeline for preventing diligence surprises.
3–6 Months Before Fundraise
- Reconcile billing and CRM data. Identify every account where Stripe and Salesforce disagree on revenue. Fix discrepancies or document reasons. This is the single highest-ROI activity for fundraise preparation.
- Lock metric definitions. Document how you define NRR, GRR, churn, expansion, and contraction. Which cohort period? What counts as reactivation vs new business? What happens with mid-cycle plan changes? Consistency across all historical data is non-negotiable.
- Build 18–24 months of history. Investors want trends, not snapshots. Ensure monthly ARR composition data goes back at least 18 months with consistent methodology throughout.
6–12 Weeks Before Fundraise
- Prepare data room metrics. ARR waterfall, NRR/GRR by segment, cohort curves, customer concentration, expansion breakdown — all from reconciled data with documented methodology.
- Run the investor calculation test. Have someone independent recalculate your NRR and ARR from raw billing + CRM data. If they get a different number, fix the reconciliation gap before an investor finds it.
- Prepare the cross-dimensional cohort cuts. Pre-build cohort analysis by acquisition channel, deal size, and customer tier so you can answer diligence questions without delay.
During the Fundraise
- Answer diligence questions with live data. When a VC asks “what’s your NRR for enterprise accounts excluding the top 3?”, you should answer in the meeting — not follow up in two days. This signals operational maturity.
- Keep data room metrics current. Don’t produce a static snapshot and hope numbers don’t change during the process. If your metrics are continuously reconciled through a platform like Eru, your data room stays live without manual updates.
- Show your methodology. The slide that builds the most investor confidence is the one showing how your metrics are calculated and where the data comes from. Transparency about methodology signals the kind of operational rigour investors want to fund.
Valuation Impact: Why Reconciled Metrics Command Higher Multiples
The difference between board metrics from reconciled data and board metrics from a single tool isn’t just accuracy — it directly affects how investors price your company.
| Metric | Below Average | Good (Series B) | Elite | Valuation Impact |
|---|---|---|---|---|
| NRR | < 100% | 110–120% | > 130% | +1–2x revenue multiple per 5pp above 100% |
| GRR | < 85% | 90–95% | > 95% | Low GRR caps valuation regardless of NRR |
| Logo retention | < 80% | 85–92% | > 95% | Signals customer satisfaction depth |
| Expansion % of new ARR | < 15% | 30–40% | > 50% | Shows capital-efficient growth engine |
| Cohort improvement | Worsening | Stable/improving | Each cohort measurably better | Strongest signal of compounding value |
Here’s the critical point: an NRR of 118% calculated from billing-only data that becomes 109% when CRM data is included doesn’t just change the number — it changes the valuation multiple. That 9-point gap can represent a 1–2x difference in revenue multiple, which at $30M ARR means $30M–$60M in enterprise value. Reconciling your data before due diligence isn’t a reporting exercise — it’s a valuation exercise.
Frequently Asked Questions
What are the best board reporting tools for SaaS metrics?
SaaS board reporting tools fall into three categories. Billing analytics (Baremetrics, ProfitWell, ChartMogul) calculate metrics from a single billing source — fast to set up but limited to billing-side data. BI platforms (Looker) offer full flexibility but require a data team. Revenue intelligence platforms like Eru connect billing, CRM, support, and product data to produce reconciled board metrics with an audit trail. For VC due diligence, the critical requirement is cross-system reconciliation: your board numbers need to match what investors calculate independently from your raw data.
Which gives the most accurate cohort analysis for VC due diligence — ProfitWell, Recurly Analytics, or ChurnZero?
For VC due diligence accuracy, none of these tools reconcile billing against CRM — which is the first thing an investor’s analyst checks. ProfitWell analyses billing data only. Recurly Analytics is limited to Recurly subscribers. ChurnZero provides health scoring but relies on externally pushed data. Eru connects billing, CRM, and product data to produce cohort analysis from reconciled cross-system data, so your cohort curves reflect the actual revenue story across all systems and survive independent verification.
What should a $50M ARR SaaS company expect to pay for board reporting tools?
Costs range widely. Billing analytics (Baremetrics, ChartMogul): $5K–$25K/year. CS platforms (Gainsight): $80K–$200K/year with 6–12 week implementation. BI tools (Looker): $50K–$150K/year plus data team salary. The biggest hidden cost isn’t the tool — it’s the 2–5 days per month your team spends manually reconciling data from ProfitWell, Baremetrics, and CRM exports into a single set of board numbers.
How do I prepare retention cohort analysis for a VC data room?
Four steps: (1) Lock your cohort definitions and apply them consistently across 6–8 quarters. (2) Reconcile underlying revenue data between billing and CRM at the account level. (3) Build both logo and revenue retention curves. (4) Prepare cross-dimensional cuts by acquisition channel, deal size, and customer tier — VCs will ask for these during diligence calls.
What revenue metrics do VCs request during Series B due diligence?
Five categories: ARR composition waterfall (18–24 months), NRR and GRR by segment, cohort retention curves (6–8 cohorts with logo and revenue retention), customer concentration analysis (top 10/20/50 accounts), and expansion revenue by motion (seats, cross-sell, upsell, usage). All must reconcile between billing and CRM — discrepancies of 3–8% are typical and investors will find them.
Related reading: How to Calculate Net Revenue Retention (NRR) Without a Data Team — step-by-step NRR calculation with common pitfalls to avoid. How to Reconcile Stripe and Salesforce Revenue Data — the specific reconciliation process that prevents diligence surprises.
See what your board metrics look like when billing, CRM, and product data are reconciled in one place. Book a free revenue audit — we’ll show you where your numbers diverge across systems and what it means for your reported NRR and valuation.
Book a revenue audit →