What do most companies build vs. what boards actually need? Most SaaS companies build static spreadsheet models reconciled quarterly with top-line ARR only — no decomposition, no cohort analysis, and no diligence defensibility. Boards and buyers need automated daily refresh from source systems, full ARR waterfalls with segment decomposition, vintage retention analysis, and numbers that are defensible in M&A diligence.

What Most Teams Build

Walk into any PE-backed SaaS company between $50M and $500M in ARR and you will find some version of the same reporting infrastructure. It was built by a capable analyst, it works well enough for internal conversations, and it breaks every time the board asks a question the model was not designed to answer. Here is what that typically looks like.

1. Static Spreadsheet Reconciled Quarterly

The most common ARR model in mid-market SaaS is a spreadsheet — usually Excel, sometimes Google Sheets — maintained by one or two people in finance. It gets reconciled quarterly, which means for three months out of every four, the numbers are stale. Between reconciliation cycles, the business is making decisions based on data that may no longer reflect reality. New bookings, mid-quarter churn, and expansion deals all accumulate in a backlog that only gets resolved when someone manually updates the model before the next board meeting.

2. Top-Line ARR Only, No Decomposition

Most internal models report a single ARR number — sometimes broken out by new vs. existing, but rarely decomposed further. There is no segmentation by product line, customer cohort, geography, or deal size. This means the business can answer “what is our ARR?” but cannot answer “where is our ARR growing fastest?” or “which segments are contracting?” Boards and buyers always ask the second and third questions. Without decomposition, every answer requires a manual deep dive.

3. Manual Data Pulls from 3+ Systems

To build the quarterly reconciliation, someone has to pull data from Salesforce (or HubSpot), the billing system (Stripe, Zuora, or Chargebee), the ERP (NetSuite or Sage), and sometimes the product database for usage data. Each system has its own customer identifiers, its own hierarchy, and its own definition of what constitutes an “account.” Reconciling across these systems is manual, error-prone, and time-consuming. It is also the single biggest bottleneck in the entire reporting process.

4. One Analyst Owns the Whole Model

In most organizations, one person — sometimes two — understands how the ARR model works. They built it, they maintain it, and they are the only ones who can explain its logic when the board asks questions. This creates concentration risk that goes beyond operational inconvenience. When that person goes on vacation, changes roles, or leaves the company, the reporting infrastructure goes with them. The model is not documented, not version-controlled, and not transferable.

5. Breaks Every Board Cycle

Every quarter, the same pattern repeats. The board meeting is two weeks away. Finance scrambles to update the model. Someone discovers that the Salesforce data does not match billing. A product launch introduced a new SKU that the model does not account for. The reconciliation takes twice as long as expected. The final board deck is assembled in the last 48 hours, and the team spends more time formatting slides than analyzing what the numbers actually mean. This is not a failure of effort — it is a failure of infrastructure.

What Boards Actually Need

Board members and PE operating partners are not asking for better spreadsheets. They are asking for a fundamentally different level of reporting — one that reflects how sophisticated investors evaluate SaaS businesses. Here is what that standard looks like.

1. Automated Daily Refresh from Source Systems

Board-grade reporting starts with data that is current. Not quarterly-current, but daily-current. When a customer churns on Tuesday, the ARR model should reflect it by Wednesday morning. When expansion revenue closes, it should appear in the waterfall that day. This requires automated pipelines that pull from CRM, billing, and ERP systems on a daily cadence, reconcile the data programmatically, and update the reporting layer without human intervention. The goal is not real-time vanity metrics — it is eliminating the quarterly scramble entirely.

2. Full ARR Waterfall with Segment Decomposition

A board-ready ARR waterfall shows beginning ARR, new logo ARR, expansion ARR, contraction ARR, and churn ARR — and breaks each category down by segment. That means decomposition by product line, customer size tier, geography, industry vertical, and sales motion. This level of granularity allows boards to see where growth is concentrated, where retention is weakest, and where the business has structural risks that top-line numbers obscure.

3. Cohort Retention, NRR, GRR by Vintage

Aggregate retention metrics hide as much as they reveal. A 110% net retention rate looks strong until you discover that one large customer expansion is masking broad-based contraction across the rest of the base. Vintage-level analysis — tracking each cohort from their starting quarter through subsequent periods — reveals the true retention behavior of the business. It shows whether newer cohorts retain better or worse than older ones, whether NRR is improving or declining over time, and whether GRR is stable or deteriorating. This is the standard that sophisticated buyers and investors expect.

4. Defensible in M&A Diligence

When a buyer conducts quality of earnings analysis on an ARR business, they rebuild the ARR model from source data. If your internal model cannot be traced back to individual transactions in CRM and billing, the diligence team will build their own version — and the discrepancies between their numbers and yours will become negotiating leverage against you. Board-grade reporting is diligence-grade reporting. Every number should be auditable, every classification decision should be documented, and every assumption should be defensible.

5. AI-Ready for Agents and Copilots

The next generation of board reporting is conversational. Instead of waiting for an analyst to build a custom view, board members and operating partners should be able to ask questions in natural language: “Show me NRR by cohort for the enterprise segment over the last eight quarters.” “Which product line has the highest expansion rate?” “What is the contraction trend for customers acquired in 2024?” This requires data that is structured, governed, and accessible to AI agents — not locked in a spreadsheet that only one person understands.

The Gap Is Not Technical — It Is Structural

“The biggest challenges are not technical. They are knowing the reporting and operating implications of every decision you make in the model.” — CFO, $100M B2B SaaS

This quote captures the core problem. The gap between what most companies build and what boards actually need is not a gap in tools or technology. Every mid-market SaaS company has access to Power BI, Tableau, dbt, Snowflake, and a dozen other platforms that could theoretically produce board-grade output. The gap is in expertise.

Building an ARR waterfall is straightforward. Building one where every classification decision — how you handle multi-product customers, co-termed renewals, mid-quarter upgrades, partial churn, and reactivations — matches what a diligence team would produce is not. That requires deep experience across dozens of SaaS businesses, an understanding of how PE firms and buyers evaluate these metrics, and the judgment to know which decisions matter and which do not.

Most finance teams have never been through a sell-side diligence process. They have never had their ARR model challenged by a buyer’s quality of earnings team. They have never seen the difference between a model that survives diligence and one that creates a purchase price adjustment. This is not a criticism of those teams — it is a recognition that this is specialized knowledge that comes from repeated exposure to transactions, not from building one model at one company.

The structural nature of the gap also explains why throwing more technology at the problem does not solve it. A company can migrate from spreadsheets to a modern data stack and still produce output that is not board-ready, because the issue was never the tooling. The issue is the domain expertise required to make the right classification decisions, present the data in the format boards expect, and ensure the output is defensible when someone challenges it.

How Pacer AI Closes the Gap

Pacer AI is an AI-native consulting firm built specifically to close this gap. Founded by ex-PwC M&A advisors with experience across $25B+ in SaaS transactions, Pacer combines deep domain expertise with an enterprise data transformation platform to deliver what boards actually need — not what most teams build.

The approach is direct:

  • Unified customer data cube built from your CRM, billing, and ERP systems — reconciled programmatically, not manually
  • Full ARR waterfall reporting with segment decomposition by product, cohort, geography, and customer tier
  • Vintage retention analysis showing NRR, GRR, and cohort behavior over time
  • Diligence-grade documentation ensuring every number is traceable and every classification decision is defensible
  • AI agent access for natural-language queries against your customer data, delivered through Power BI and Excel
  • Daily automated refresh — not a one-time deliverable, but a continuously updated platform

The result: 30 minutes to board-ready, not 30 hours. Updated daily for the pace of operations, not quarterly for the pace of reporting. Learn more about how this works on our ARR Snowball solution page.

Next Steps

If your current board reporting process involves a quarterly scramble, a single-owner spreadsheet, or numbers you would not want a diligence team to examine closely, it is time to close the gap. Schedule a 30-minute conversation and we will show you what board-grade ARR reporting looks like with your own data.

Get a Sample Board Package