--- name: building-board-revenue-reporting description: >- Builds the board revenue package: an ARR bridge, cohort retention, efficiency metrics, pipeline and capacity health, and the CRO narrative explaining a miss or a beat. Use when the user says "board deck", "board revenue slides", "board package", "prep for the board meeting", "ARR bridge", "NRR slide", "CAC payback", "Rule of 40", "efficiency metrics for the board", "how do I explain the miss to the board", "investor update revenue section", or asks which revenue metrics belong in front of directors. Use it whenever the task is assembling or reviewing revenue reporting for a board or investors, even if the user does not say "board". Do NOT use for running the internal weekly forecast call (see running-forecast-calls), designing quotas or commission plans (see designing-sales-compensation), building a new revenue leader's onboarding plan (see planning-cro-first-90-days), or defining a single SaaS metric formula in isolation (see modeling-saas-revenue-metrics). metadata: version: "1.0" --- # Building board revenue reporting Assemble the revenue section of one board package: ARR bridge, retention, efficiency, pipeline and capacity health, and the written narrative on variance to plan. Financial statements, cash and runway modeling, and the internal weekly forecast call are out of scope. Note on sourcing: the board-pack structure and dashboard mechanics below come from a vendor framework, and its illustrative figures are worked examples rather than benchmarks. Retention, efficiency, and coverage benchmarks come from named studies and are cited individually. ## Workflow Copy this checklist into your reply and tick items as you complete them: ``` - [ ] 1. Run the data-foundation gate - [ ] 2. Build the ARR bridge and tie it to Finance - [ ] 3. Build cohort retention (NRR and GRR) and benchmark it - [ ] 4. Compute efficiency metrics against segment thresholds - [ ] 5. Build pipeline health and capacity sections - [ ] 6. Write the narrative: context, risks, asks - [ ] 7. Validate the pack against the tie-out gate; fix and re-run ``` **1. Run the data-foundation gate first.** Do not build a slide before these hold, because a number a director can break in one question costs more credibility than a missing slide ([Weflow](https://www.weflow.ai/blog/revops-board-reporting-framework-best-practices)): - One source of truth across CRM, BI, and Finance. - A version-controlled metrics glossary for ARR, NRR, CAC payback, coverage, forecast categories, and productivity, recording when and why each formula changed. - Ownership per metric mapped to CRM field, BI model, Finance source, and the named person who signs off. - Stage definitions, exit criteria, forecast categories, and close-date rules enforced; required fields validated for segment, geo, product line, campaign source, forecast category. - Finance tie-outs agreed for booked ARR, churn, and expansion logic. **2. Build the ARR bridge.** Opening ARR + new logo + expansion − contraction − churn = closing ARR, with each component reconciled to the Finance figure before the pack is drafted. Show a five-quarter rolling view on every trended metric, because five quarters shows sequential movement, the same quarter last year, and seasonality in one frame ([Weflow](https://www.weflow.ai/blog/revops-board-reporting-framework-best-practices)). Report new logo and expansion separately from the start; expansion has its own conversion pattern and cycle length and must be modeled separately ([Clari](https://www.clari.com/blog/sales-forecasting-methods/)). **3. Build cohort retention.** Use the dollar-based cohort definition, not an account-based one: NRR is the current-period MRR from only those customers who were customers in the same period one year earlier, divided by their total MRR in that earlier period, including upsell, cross-sell, and price increases. GRR is the same calculation excluding upsell, cross-sell, and price increases, computed by capping each customer's later-period MRR at its prior-period MRR; churn is 1 − GRR ([SaaS Capital](https://www.saas-capital.com/wp-content/uploads/2025/09/RB32WS1-2025-B2B-SaaS-Retention-Benchmarks.pdf)). Benchmark against ACV band, not company age or industry, because similar price points imply similar org design and support model ([SaaS Capital](https://www.saas-capital.com/wp-content/uploads/2025/09/RB32WS1-2025-B2B-SaaS-Retention-Benchmarks.pdf)). Private B2B SaaS medians: NRR 101%, GRR 91%, with GRR of at least 90% stated as the floor for parity with peers. Median NRR by ACV band: under $12K 98%; $12–25K 103%; $25–50K 102%; $50–100K 104%; $100–250K 102%; above $250K 106% ([SaaS Capital](https://www.saas-capital.com/wp-content/uploads/2025/09/RB32WS1-2025-B2B-SaaS-Retention-Benchmarks.pdf)). Pair retention with growth, because that is the link a board cares about. Median growth by NRR band: under 90% NRR grows 15%; 90–100% grows 16%; 100–110% grows 21%; 110–120% grows 30%; 120–130% grows 38%; above 130% grows 50%, against a population median growth of 24%. Moving from the 100–110% band to 110–120% is worth roughly 9 percentage points of growth, and GRR shows little direct correlation with growth — treat it as table stakes ([SaaS Capital](https://www.saas-capital.com/wp-content/uploads/2025/09/RB32WS1-2025-B2B-SaaS-Retention-Benchmarks.pdf)). **4. Compute efficiency metrics.** Report CAC payback against the segment threshold rather than a single company target: under 12 months for SMB focus, under 18 for mid-market, under 24 for enterprise, measured on gross-margin-adjusted ARR and including sales, marketing, and the customer-success expense tied to renewal, upsell, and cross-sell ([Bessemer](https://www.bvp.com/atlas/scaling-to-100-million)). Add the unit-economics read: 1× CLTV/CAC is breakeven, invest at 3× or above, keep experimenting well below 3×, and stop acquiring incremental customers when CAC exceeds CLTV ([Bessemer](https://www.bvp.com/atlas/scaling-to-100-million)). Choose the efficiency headline by stage, and name the choice on the slide: | Situation | Metric to lead with | |---|---| | Above $25M ARR | Efficiency score = FCF margin of ARR + ARR YoY growth; 40%+ is the stated bar, and the BVP Nasdaq Emerging Cloud Index average sits closer to 50% ([Bessemer](https://www.bvp.com/atlas/scaling-to-100-million)) | | Growth composition contested | Rule of X = (growth × multiplier) + FCF margin, at roughly 2× for private companies; it explains valuation better than Rule of 40, R² 62% versus 50% ([Bessemer](https://www.bvp.com/atlas/the-rule-of-x)) | | Early stage, growing above 125% and burning above 75% | Burn multiple, where roughly 1×–1.5× is attractive; Rule of X does not apply cleanly here ([Bessemer](https://www.bvp.com/atlas/the-rule-of-x)) | | Public-comparable S&M efficiency question | Magic number = (current-quarter GAAP revenue − prior-quarter GAAP revenue) × 4 ÷ prior-quarter S&M; below 0.75 inefficient, 0.75–1.0 moderate, above 1.0 very efficient ([Wall Street Prep](https://www.wallstreetprep.com/knowledge/saas-magic-number/)) | Below $25M ARR, efficiency score is noisy on a small revenue base and should be shown with that caveat stated ([Bessemer](https://www.bvp.com/atlas/scaling-to-100-million)). **5. Build pipeline health and capacity.** Report coverage as required coverage = 1 ÷ trailing win rate, not a fixed 3×, and show weighted coverage alongside raw ([Clari](https://www.clari.com/blog/pipeline-coverage-best-practices/)). Purge before reporting: a team showing 4× coverage with 30% stale pipeline holds 2.8× qualified coverage, and deals aged beyond 2× the average cycle length should be discounted or removed ([Clari](https://www.clari.com/blog/pipeline-coverage-best-practices/)). The capacity section carries planned versus actual hires, ramping rep count, full-productivity timelines, attrition, manager coverage against the common 1:6 span threshold, and attainment segmented by tenure (ramping versus fully ramped), region, segment, manager, and business type. Compare modeled ramp time to actual ramp time every quarter and quantify the revenue effect of the gap, because unacknowledged ramp slippage is the most common source of a plan that was already unachievable when it was approved ([Weflow](https://www.weflow.ai/blog/revops-board-reporting-framework-best-practices)). **6. Write the narrative.** Curate five to seven metrics and for each show the trend, explain the root cause, and draft the narrative line; the recommended set is ARR, NRR, pipeline coverage, forecast versus actuals, CAC payback, quota attainment split by ramp status, and ramp-time actuals ([Weflow](https://www.weflow.ai/blog/revops-board-reporting-framework-best-practices)). Structure the discussion as Context (what changed in revenue, pipeline, productivity, retention), Risks (which early-warning signals matter and what drives them), and Asks (where leadership needs board input, approval, or alignment). The goal is decisions made, not slides reviewed ([Weflow](https://www.weflow.ai/blog/revops-board-reporting-framework-best-practices)). Pair every lagging metric with the leading indicator that explains it, which is what converts a miss slide into a diagnosis ([Weflow](https://www.weflow.ai/blog/revops-board-reporting-framework-best-practices)): | Lagging | Leading | |---|---| | ARR attainment | Pipeline creation, coverage, stage conversion, ASP trend | | NRR | Usage depth, executive engagement, renewal sentiment, churn-risk accounts | | Forecast accuracy | Deal momentum, stage aging, activity completeness, manager inspection quality | | CAC payback | Hiring velocity, ramp-time actuals, attainment by ramp status | | Margin | Pricing and discounting trend by segment, region, deal size | On a miss, this step is high-freedom on wording and low-freedom on structure: name the mechanism, quantify it, state what was done and when the fix shows up in the numbers. A miss narrative with no quantified mechanism reads as a lack of instrumentation regardless of how well written it is. **7. Validate the pack, then loop.** Run this gate and fix every failure before the pack circulates: ``` - ARR bridge components each tie to the Finance figure (state variance if any) - NRR and GRR computed on the same cohort window and both disclosed - Every metric matches the glossary formula; any changed formula is footnoted - Five-quarter view present on every trended metric - Coverage figure is post-purge and states the win rate used - Activity completeness above 95% on accounts feeding pipeline claims - Exactly 5-7 headline metrics; every one has a named root cause and a narrative line - Every "Ask" names a decision, an owner, and a date ``` Re-run the gate after fixing. Only circulate when it passes, because a single untied number moves the meeting from strategy to reconciliation. ## At-risk signals to surface in the risk section Report these with the action already taken, not as observations ([Weflow](https://www.weflow.ai/blog/revops-board-reporting-framework-best-practices)): | Signal | Action to report | |---|---| | Close date pushed more than once in 30 days | Stage validity reviewed, buyer timeline confirmed, inflated Commit classifications stripped | | No next step on a late-stage opportunity | Manager inspection triggered, next-step field completion required | | Buyer engagement dropping across meetings and email replies | Momentum risk flagged, multithreading or executive outreach pushed | | Activity capture incomplete on key accounts | Sync logic audited, completeness restored, forecast confidence reassessed | | Forecast category not matching stage or evidence | Hygiene rules enforced, manager roll-ups recalibrated | ## Output format Use this exact section order; keep it stable across board cycles so directors can compare packs quarter over quarter. Content inside each section is yours to adapt. ``` ## Revenue review — **1. Headline** Closing ARR $X (plan $X, variance ±X%) | NRR N% | GRR N% | CAC payback N mo | Coverage N.Nx **2. ARR bridge (five-quarter)** | Quarter | Opening | New logo | Expansion | Contraction | Churn | Closing | **3. Retention** NRR by ACV band vs benchmark | GRR vs 90% floor | top 5 churn/contraction accounts and cause **4. Efficiency** CAC payback vs segment threshold | efficiency metric led with, and why | CLTV/CAC **5. Pipeline health** Coverage (raw and weighted) | required coverage = 1 / win rate | stale purged $ | creation by segment **6. Capacity** Planned vs actual hires | ramping count | attainment by ramp status | modeled vs actual ramp, revenue effect $ **7. Narrative** Context: Risks: Asks: ``` ## Gotchas - Compute NRR and GRR on the same cohort window and disclose both. GRR cannot exceed 100% by construction; a GRR above 100% in a draft pack means upsell leaked into the gross calculation ([SaaS Capital](https://www.saas-capital.com/wp-content/uploads/2025/09/RB32WS1-2025-B2B-SaaS-Retention-Benchmarks.pdf)). - In every ACV band except above $250K, at least a quarter of companies are contracting, and the 25th-to-75th percentile spread is widest in the $12–25K band ([SaaS Capital](https://www.saas-capital.com/wp-content/uploads/2025/09/RB32WS1-2025-B2B-SaaS-Retention-Benchmarks.pdf)). Show your percentile position within your band rather than a distance from the overall 101% median, which flatters low-ACV businesses and punishes high-ACV ones. - Growth decays predictably. ARR growth retains roughly 70% year over year in the private cloud market and about 80% for the public cloud index ([Bessemer](https://www.bvp.com/atlas/scaling-to-100-million)). A plan assuming flat growth rate is asserting an above-market outcome, and a board will read it that way; state the growth-endurance assumption explicitly. - A single metric never establishes health. Magic number in particular must be read alongside gross margin and churn, because it ignores nothing about retention quality ([Wall Street Prep](https://www.wallstreetprep.com/knowledge/saas-magic-number/)). Gross margin averages 65–70% across maturity levels, so a magic number computed on unusually low-margin revenue overstates efficiency ([Bessemer](https://www.bvp.com/atlas/scaling-to-100-million)). - The vendor board framework's illustrative figures — coverage 3.4× falling to 2.8×, $2.1M slipped from stage 4, attainment 68% falling to 61%, modeled ramp 6 months versus actual 8 — are worked examples, not benchmarks ([Weflow](https://www.weflow.ai/blog/revops-board-reporting-framework-best-practices)). Never present them as industry comparison figures. - Review the early-warning dashboard weekly, not in the week before the board meeting ([Weflow](https://www.weflow.ai/blog/revops-board-reporting-framework-best-practices)). Signals discovered during pack assembly are already too old to act on, and the pack then documents a problem instead of a response. - Attainment reported as a team average hides the distribution. Two reps at 140% and eight at 50% produce a 68% team average while 80% of the team is missing badly ([RevenueLab](https://www.revenuelab.fyi/blog/sales-capacity-planning)). Report attainment split by ramp status and show the median, not the mean. - Reporting an unweighted coverage ratio invites a board to conclude the quarter is covered when it is not; weighted coverage is the more honest signal and should be the number in the headline ([Clari](https://www.clari.com/blog/pipeline-coverage-best-practices/)).