Board KPI Catalog — Defined, Sourced, Benchmarked

The single past-period observed burn — gross and net — that anchors the forecast-scenario matrix. The "we just lived through this" baseline against which conservative / most-likely / best-case forecasts are projected. Differs from `finance.gross_burn_rate` and `finance.net_burn_rate` in being explicitly a point-in-time historical anchor with both components paired in one object, rather than the standalone monthly KPI values. Common pitfall: anchoring forecasts off a single month with a known one-off (large bill, prepayment received) bakes a distortion into all scenarios — pick a representative period or document the adjustment.

FX-aware enumeration of the company's bank, brokerage, and money-market accounts — each with bank name, account type, restricted flag, currency, balance, as-of date, and notes. The underlying data source for `finance.total_cash_in_bank`, `finance.total_restricted_cash`, `finance.total_unrestricted_cash`, and the FX conversion that turns multi-currency holdings into a single reporting-currency number. Common pitfall: a single forgotten account (often a legacy operational account or a money-market sweep) silently misstates the total — boards should ask for a checklist reconciliation against the prior board pack each cycle. Best practice: include account-number last-4 (not full numbers, for security) and the FX rate used per non-functional-currency account.

Forecast burn-rate matrix across three scenarios — conservative (defensive cost plan, slow revenue), mostLikely (current best-estimate), bestCase (aggressive investment with strong revenue) — with gross + net burn for each. Bound to the ScenarioBurnRateMatrix widget alongside the historical `finance.burn_rate_actual` anchor. The board reads this to understand what range of cash trajectories the company is planning for and which one management has chosen as the base case. Common pitfall: the three scenarios cluster tightly (all within ±10% of each other) — that's not three scenarios, it's one scenario with rounding error. Real scenarios should reflect meaningfully different operating decisions and produce visibly different runways.

Signed cash effect of period-over-period changes in current assets — accounts receivable, prepaid expenses, deposits, and other short-term assets. Positive when assets are converting back to cash (AR collections, prepaid expenses being consumed); negative when assets are growing and absorbing cash (AR balance up, new prepayments made). Half of the `finance.net_working_capital_adjustment` rollup. Common pitfall: a one-off enterprise prepayment to a vendor (e.g. 12-month infra commit) shows up here as a large negative without the P&L showing the cost yet — flag it explicitly so the board does not read deterioration where there is none.

Signed cash effect of period-over-period changes in current liabilities — accounts payable, accrued payroll/taxes/bonuses, deferred revenue from customer prepayments, and other short-term liabilities. Positive when liabilities grow and absorb less cash than the matched expense suggests (e.g. AP balance growing means vendor cash payments lag); negative when liabilities are being paid down faster than they accrue. Deferred revenue is the most powerful component in SaaS — a large annual prepayment received increases deferred revenue and supplies cash now against expense recognized later. Common pitfall: a board reading this as straight cash improvement misses that deferred revenue must still be earned out, and a stretched AP balance signals supplier strain. Best practice: footnote large components (deferred revenue, accrued bonus) separately.

Narrative listing of the key inputs the forecast rests on — growth-rate assumptions, churn assumptions, hiring plan, FX rates, expected timing of large bookings, planned price changes, capitalized-vs-expensed R&D treatment, etc. Without this field, the board cannot tell whether a forecast change reflects a real-world update or a quietly changed assumption. Common pitfall: assumptions are written once at planning and never updated when the underlying reality shifts — track explicitly which assumption changed each quarter and why. Best practice (per "Venture Deals" by Feld & Mendelson, and standard board-pack guidance): every material variance vs. forecast should be traceable to either an executed plan or a changed assumption.

Material risks that could break the forecast or the cash position — customer concentration, contract renewal risk in the next 2 quarters, debt-covenant proximity, FX exposure on multi-currency revenue/cost mix, payment-processor concentration, audit/tax adjustments under review, regulatory changes affecting revenue recognition. Distinct from `risk_factors` at the operations level — this is explicitly financial. Common pitfall: this field becomes boilerplate ("market risk, execution risk") instead of naming the specific risks the board can act on this quarter. Best practice (per the standard board-pack guidance reflected in NVCA Model Investor Rights Agreement information-rights conventions): name the top 3–5 risks with a probability/impact note and a current mitigation status.

Executive narrative on what the latest forecast says and how it has changed since prior reporting — which scenarios were considered, which was picked as "most likely" and why, what changed since last quarter, and what would push the forecast into a different scenario. Pairs with `finance.burn_rate_scenarios` (the numeric scenarios) to provide the qualitative "why" beside the quantitative "what". Common pitfall: this becomes a restatement of the numbers rather than commentary — every paragraph should add interpretation the numbers do not by themselves convey (drivers, decisions taken, decisions deferred).

Average monthly cash outflow before any inflows are netted off — essentially the company's monthly cost base in cash terms. Tracked alongside net burn because net burn alone can mask a structural problem when revenue is masking high cost. The board reads gross burn to understand the absolute cost commitment (mostly payroll, infra, COGS, sales spend) regardless of revenue mix. Common pitfall: founders often optimize the net burn narrative ("we cut burn 30%") via a one-time inflow without addressing the gross-burn cost base — the next quarter without that inflow re-exposes the underlying spend. Always present gross and net side-by-side.

Average monthly net cash outflow over the reporting period — total cash spent minus total cash collected, divided by the number of months in the period. The headline survival number for venture-backed startups: it pairs with `finance.total_cash_in_bank` to produce runway, and pairs with revenue growth to produce the Bessemer "burn multiple". Common pitfall: net burn is volatile — large quarterly bills (annual SaaS renewals, employer-tax true-ups), enterprise prepayments, and FX swings can mask the underlying trend. Smoothing over a trailing 3-month average is standard board practice. Equally important: do not silently include one-off cash events (acquisitions, settlements, large prepayments received) without flagging them — boards prefer a "core burn" and "headline burn" pair when the period is noisy.

Signed net effect on cash of changes in current assets and current liabilities — receivables coming in (positive), payables going out (negative), prepaid expenses (negative when paid, positive when burned down), and accrued liabilities (positive when accrued, negative when settled). The rollup of `finance.current_asset_adjustments` and `finance.current_liability_adjustments`. Common pitfall: at early stage this is dominated by payroll-cycle noise and is near zero — once the company adds enterprise contracts with annual prepayments or 60-day net terms, this can swing 1–3 months of burn either direction. Becomes material at Series A+; ignored before that.

Unrestricted cash adjusted for near-term working-capital effects — i.e. the cash that is actually deployable after accounting for receivables coming in, payables going out, and accrued obligations crystallizing in the next reporting period. More conservative than `finance.total_unrestricted_cash` because it nets out the cash a healthy AR/AP cycle is already promising or claiming. The board reads this as the "real" cash position when working capital is material to the business (typical at Series A+, when AR/AP cycles get sizeable). Common pitfall: at early stage AR is small and AP is mostly payroll/SaaS, so this collapses to unrestricted cash — once enterprise deals or 60-day net terms appear, the gap widens fast.

Cash on the balance sheet that is not available for general operating use because it is contractually pledged or held for a specific purpose — typical examples include landlord lease-deposit escrows, customer-funds collateral, security deposits backing letters of credit, payment-processor reserves, and debt-covenant minimum-balance requirements. Per IFRS and US GAAP balance-sheet presentation, restricted cash must be disclosed separately from unrestricted cash; the board should treat this number as removed from runway. Common pitfall: payment-processor "reserve" balances and large customer-deposit floats are often missed when reporting unrestricted cash, inflating apparent runway.

Estimated number of months the company can operate at the current net burn before unrestricted cash reaches zero, holding everything else constant. The single most consequential survival input for venture-backed companies — it sets the urgency of every fundraising, hiring, and cost decision. Common pitfall: runway is often quoted off `finance.total_cash_in_bank` and a single-month spot-burn instead of operationally-available cash and a 3-month-trailing burn — the result is a runway that looks 2–4 months longer than it actually is when working capital tightens. Boards should ask which cash and which burn went into the calculation.

Sum of all bank account balances at the reporting cut-off, expressed in a single reporting currency after FX conversion. This is the gross top-of-house cash number — it does not net out restrictions, near-term liabilities, or commitments. The board reads this as the absolute denominator for runway and as a checksum against the cap table (capital raised − cumulative net burn ≈ cash). Common pitfall: founders sometimes report a USD figure that silently includes ILS/EUR accounts at stale FX rates — always reconcile against the bank-accounts list (per FX-aware MultiCurrencyAccountList) and tag the rate date.

Sum of cash actually received from operating activities for the period — customer collections (subscription, services, transactional revenue), refunds claimed back from vendors, and any operating tax credits. Excludes financing activities (debt draws, equity proceeds) and investing activities (asset sales, investment income). This is the numerator-side of the net-burn equation, and the cash-basis counterpart to recognized revenue on the P&L. Common pitfall: companies sometimes book annual SaaS prepayments here as a single-month inflow, masking the underlying monthly run-rate — split lumpy items out or smooth over a trailing 3 months.

Sum of cash actually paid for operating activities for the period — payroll and benefits, employer taxes, vendor payments (infra, tooling, contractors), sales and marketing spend, rent, professional services, refunds issued. Excludes financing activities (debt repayment, dividend payments) and investing activities (acquisitions, capex). Direct input to gross burn. Common pitfall: capitalized R&D and long-term capex sometimes get bucketed here; if so they distort gross burn. Keep this strictly operating-cash and surface investing/financing outflows separately so the board can see "ongoing cost base" vs. "discretionary capital deployment".

Cash that the company can freely deploy for any operational purpose — total bank balances minus any contractually restricted balances. This is the input most boards actually want when judging runway, because it strips out escrows, security deposits, and processor reserves that cannot be spent on payroll or vendors. The distinction matters more as the company adds enterprise contracts (deposit obligations), debt facilities (covenant balances), and payment processing volume (rolling reserves). Common pitfall: at early stage, restricted cash is often near zero so teams equate this with `finance.total_cash_in_bank` — track them separately from day one to avoid surprise reclassifications later.

Itemized list of working-capital adjustments with explicit sign-prefix driving the additive-vs-subtractive multiplier — e.g. "+ AR collected: $250k", "− Prepaid infra: $80k", "+ Deferred revenue: $600k". The line-item basis for `finance.net_working_capital_adjustment` and its child KPIs (current_asset_adjustments, current_liability_adjustments). The signed-prefix UI convention prevents the most common working-capital reporting bug — sign-flips that double-count or invert the cash effect. Common pitfall: lumping unrelated items into a single "other working capital" line loses the diagnostic value; break out the top 3–5 components.

Annual Recurring Revenue — the value of all recurring subscription revenue normalized to a one-year run-rate as of the period close. The headline operating metric for a subscription business; every growth and efficiency ratio (NRR, GRR, magic number, CAC payback, Rule of 40) is calibrated against it. Excludes one-time fees, professional services, and non-contractual usage. Common pitfall: confusing ARR (contracted recurring) with revenue (recognized) or with CARR (contracted incl. not-yet-live) — the SMSB standard draws sharp lines between them, and boards expect the same discipline. The KpiVarianceTable widget surfaces forecast / actual / variance / status / future-forecast columns against the same field.

Average annualized contract value across new-customer deals signed during the period (ACV). Defines where the company plays on the SaaS deal-size spectrum and dictates the operating model — high-ACV businesses tolerate longer sales cycles and direct sales motions; low-ACV businesses must run product-led or inside-sales motions to keep CAC payback short. Common pitfall: blending new and expansion ACV obscures the new-logo deal-size trend that boards actually want to see. Anchored to KBCM/Sapphire SaaS Survey 2024 §Average Contract Value for cross-company benchmarking.

Mean dollar value across active pipeline opportunities (Pipeline Value / Pipeline Deal Count). Distinct from sales.avg_contract_value (ACV) which measures closed-won deals — average_deal_size is forward-looking pipeline-shape, ACV is realized output. Common pitfall: a few oversized deals materially skew the average — always inspect median_deal_size alongside; a large gap between average and median signals a few mega-deals that drive most of the projected number, which concentrates pipeline risk.

Average number of days from opportunity creation to closed-won status — measured only on won deals (lost deals are tracked separately). The motion-velocity metric — directly determines how much pipeline coverage is needed, how quickly investment in new reps pays back, and how feedback loops on packaging or pricing experiments compound. Common pitfall: blending segment cycles (SMB and Enterprise often differ 5–10×) into a single average hides material trend signals — segment-cut the metric where deal-volume permits.

Total fully-loaded S&M spend in the period divided by the dollars of new CARR generated in the period (new-customer + expansion CARR combined). Per the SMSB standard, the headline efficiency ratio for the full sales-and-marketing motion — answers "how many cents do we spend on S&M to add one dollar of contracted ARR." Common pitfall: blending without separately reporting New CAC Ratio and Expansion CAC Ratio hides which side of the motion is driving efficiency — for a healthy SaaS company expansion CAC is usually 3–5× cheaper per dollar than new-logo CAC.

Total value of signed contracts that have not yet been recognized as revenue — future revenue locked into the books. Equivalent to "remaining performance obligation" (RPO) in public-SaaS disclosures, though private companies often track only the in-period portion. Board reads this as the visibility horizon: a healthy backlog means recognized revenue is largely already-sold and not dependent on Q-end heroics. Common pitfall: confusing backlog with pipeline — backlog is contractually committed, pipeline is unsigned opportunity. Surface the two on the same dashboard but never sum them.

Total dollar value of all signed contracts that have not yet been recognized as revenue — the visibility window into future revenue at a point in time. Closely related to sales.bookings_backlog; this entry serves as the FlowSubform `start` slot for the per-period bookings-backlog flow (open + new bookings − recognized − cancellations = close). Common pitfall: omitting cancellations from the flow leaves a phantom backlog that overstates future revenue visibility — every backlog flow needs an explicit cancellation line even when zero.

Number of months required for the gross profit generated from a new customer's ARR to recover the fully-loaded S&M spend used to acquire them. The single most decision-useful efficiency metric at the board level — it directly connects acquisition cost, ACV, and gross margin into one "how long until we break even on this customer" answer. Per the SMSB standard, the calculation must use gross-margin-adjusted ARR in the denominator (not raw ARR) to be cross-company comparable. Common pitfall: using raw ARR understates payback by ~25–30 percentage points and breaks comparability with peer benchmarks.

Contracted Annual Recurring Revenue — recognized MRR × 12 plus the annualized value of contracts that are signed but not yet live (i.e. implementation, ramp, deferred-start). Per the SMSB standard, CARR sits between ARR (live only) and pipeline (unsigned) on the revenue-certainty spectrum: contractually committed but not yet delivered. Boards reading CARR > ARR gap can quantify the in-flight implementation backlog and the leading indicator of next-period ARR. Common pitfall: counting verbal commitments or LOIs as CARR — only signed contracts qualify under the SMSB definition.

Annualized recurring revenue lost during the period from customers who fully cancelled — terminating their contract or letting it lapse without renewal. The "leak" line of the ARR waterfall and the denominator of Gross Revenue Retention. Distinct from Downgrade ARR (sales.downgrades) which captures contractions where the customer stays. Common pitfall: lumping mid-term cancellations with non-renewals masks two very different retention failures — surface them separately when material. The KpiVarianceTable widget tracks period forecast vs actual; a widening miss against forecast is the earliest signal of a retention problem.

Narrative read on competitive dynamics affecting the sales motion — material wins / losses to specific competitors, observed pricing or packaging moves in the market, new entrants, M&A in the competitive set. Boards use this surface to bring outside intelligence (their other portfolio companies, advisors) to bear on the competitive picture. Common pitfall: listing competitor names without quantifying how often they show up in deal cycles — a "Competitor X is being aggressive" entry without "we saw them in 8 of 20 active deals last quarter, up from 3 of 18" is too vague to act on.

Fully-loaded sales-and-marketing (S&M) expense incurred to acquire one new customer during the period. Per the SMSB standard, the CAC numerator includes salaries + commissions + benefits + travel + marketing programs + tooling — i.e. all S&M costs, not just direct-attribution paid acquisition. The denominator is new logos, not deals. Common pitfall: omitting fully-loaded comp (especially BDR/SDR base salary and CS-team cost-of-sale where they participate in expansion) understates CAC and inflates every downstream efficiency metric. The board cares about CAC alongside CAC Payback and the CAC Ratio family — single-number CAC is a building block, not a verdict.

Count of opportunities that transitioned to closed-lost during the period — the volume side of pipeline disqualification. The other half of the win rate denominator; without tracking it explicitly you cannot compute or benchmark win rate. Common pitfall: stale "open" deals that should be marked lost are left open, inflating pipeline value while suppressing the lost count — a hygiene problem that compounds because next-period coverage looks fine while win rates silently degrade. Every CRM hygiene policy should specify a max-age before deals auto-flag for lost-or-update review.

Total dollar value of opportunities closed-lost during the period — the opportunity-cost view on the pipeline motion. Useful for sizing the "what we missed" gap and prioritizing post-mortem efforts on the highest-value losses. Common pitfall: post-mortems on small lost deals waste time relative to insight; tier the post-mortem cadence by value (e.g. every loss above the 80th-percentile deal size gets a written debrief). Boards expect the largest 2–3 losses to be explained explicitly in commentary.

Count of opportunities that reached closed-won status during the period — the volume side of the period's sales output. Paired with closed_won_value gives the period's average won-deal size, a critical mix-shift indicator. Common pitfall: counting opportunity stage transitions rather than discrete deal closes (re-opened deals inflate the count). Boards read the trend over 4+ quarters to detect motion-volume stability — sharp drops while pipeline holds usually mean late-stage conversion has broken.

Total dollar value of all opportunities closed-won during the period — the period's realized bookings from the pipeline motion. Reconciles to (sales.new_business + sales.expansion) when split by deal type. Common pitfall: reporting TCV (total contract value) here when the rest of the dashboard uses ACV — pick one and apply it consistently across closed_won_value, weighted_forecast, and pipeline_value, or the dashboard math stops reconciling.

Annualized recurring revenue lost from existing customers who reduced spend mid-term or at renewal (seat reductions, tier downgrades, removed modules) — without leaving entirely. The "contraction" line of the ARR waterfall, distinct from full churn. Often a more sensitive leading indicator than churn because customers tend to contract before they cancel. Common pitfall: lumping downgrades into churn obscures the early-warning signal — boards looking only at logo churn miss the slow-bleed pattern. Surfaces in the KpiVarianceTable widget alongside expansion and churn so the net-retention math is auditable.

Annualized recurring revenue added during the period from existing customers — through upsell (more seats / higher tier), cross-sell (additional products), or price increases. The "farm" line of the ARR waterfall. Boards read this as the leading indicator that product-market fit has translated into product-account fit and that the post-sale motion is creating compound growth. Common pitfall: classifying contractual price-step-ups (CPI escalators baked into the original contract) as expansion overstates new selling motion. Expansion CAC Ratio and Net Revenue Retention are derived from this number.

Fully-loaded S&M plus Customer Success expense attributable to expansion divided by expansion CARR generated in the period. Per SMSB, the efficiency read on the upsell / cross-sell / land-and-expand motion. Distinct from the new-logo CAC ratio because the cost base often includes CSMs whose primary metric is retention but whose secondary metric is expansion — boards expect to see that allocation called out. Common pitfall: excluding CS comp entirely understates the true cost of expansion; including all of CS overstates it. The SMSB standard prescribes a documented allocation rule (typically tied to expansion-quota OTE share).

Recognized revenue minus cost of goods sold (COGS), divided by recognized revenue, expressed as a percentage. The single best read on whether the business model can ever generate operating leverage — a low gross margin caps every downstream efficiency metric (CAC payback, LTV/CAC, Rule of 40). For SaaS, COGS includes hosting, third-party software, customer support, and customer-success cost-of-service. Common pitfall: omitting customer success from COGS inflates the margin and breaks comparability with peer benchmarks. Anchored to KBCM/Sapphire SaaS Survey 2024 §Gross Margin.

Year-over-year percentage growth in ARR (or recognized revenue, if explicitly anchored) — comparing the current period to the equivalent period 12 months prior. The single most-watched investor metric and the largest single driver of SaaS valuation multiples. Common pitfall: comparing to the prior quarter (QoQ) and reporting it as "growth rate" — boards and investors mean YoY unless explicitly noted otherwise. Anchored to KBCM/Sapphire SaaS Survey 2024 §YoY ARR Growth for cross-company benchmarking.

Median dollar value across active pipeline opportunities — the typical deal in the pipeline, robust against the few-big-deals skew that distorts the average. The honest read on the "core motion" deal-size; if the team is winning a few oversized deals but the median is shrinking, the underlying motion is degrading even though the topline numbers look fine. Common pitfall: omitting median in dashboards in favor of just the average lets concentration risk hide. A best-practice board pack always shows both.

Annualized recurring revenue booked from net-new logos (first-time customers) during the period. This is the "hunt" line of the ARR waterfall — the output of the new-customer acquisition motion, distinct from expansion (existing-customer upsell) and from churn / downgrades. Common pitfall: counting renewals or expansion deals as new business inflates the new-logo conversion engine and hides a stalled acquisition motion. The KpiVarianceTable widget shows period forecast vs actual; downstream views compare it to S&M spend to derive new-business CAC and CAC payback.

S&M expense attributable to new-customer acquisition divided by the new-customer CARR generated in the period. Per SMSB, the cleanest read on the new-logo acquisition engine's efficiency — strips out the expansion motion which has materially different unit economics. Common pitfall: failing to split AE comp time correctly between new and expansion activities — when the same AE owns both motions, an allocation rule (often the % of OTE tied to new-vs-expansion quota) is required and must be applied consistently quarter-over-quarter.

Count of net-new logo customers signed during the period (a customer is a discrete buying entity — typically an account, not a seat). Paired with sales.new_business gives Average Selling Price (ASP) — a primary input to ICP / segment-fit conversations. Early-stage boards read the logo count as a sanity check on top-of-funnel and PMF before ARR-density grows enough to matter. Common pitfall: counting expansion deals or new contracts from existing customers as "new" inflates the acquisition signal — the count must match the same "first-time customer" criterion as New Business ARR.

Total dollar value of new opportunities entering the pipeline during the period — the top-of-funnel inflow line in the pipeline flow. The single best read on the marketing-and-SDR engine's output. Common pitfall: counting inflated, un-qualified opportunities (e.g. every demo request) overstates the engine's output; restrict to opportunities that pass a defined qualification stage (typically SQL or higher) before counting. Boards expect this number to track forward quota — a quarter's top-of-funnel should be ~1× the same quarter's quota for a normal sales-cycle business.

Total pipeline value at the start of the period — the baseline against which the period's pipeline flow (+ new opportunities − won − lost = closing) reconciles. Equal to the prior period's closing pipeline by construction. Surfaces in sales.pipeline_flow as the `start` slot. Common pitfall: restating opening pipeline to retroactively "clean up" stale deals masks the hygiene problem rather than addressing it; cleanup should happen via explicit "old-deal scrub" lines in the flow, not by editing the opening baseline.

Narrative documenting the key assumptions underlying the pipeline forecast — conversion rates by stage, expected sales-cycle length, segment-mix expectations, and any deal-specific dependencies (e.g. "we assume Acme renews their POC by end of month and signs the upgrade in Q3"). Common pitfall: leaving assumptions implicit makes the forecast non-falsifiable — if you don't list the assumptions, you can't identify which one broke when the forecast misses. Renders side-by-side with sales.pipeline_risk_factors in the TwoColumnTextarea widget (sales.pipeline_context_notes container).

Container handle for the side-by-side contextual notes — pairs sales.pipeline_assumptions (left slot) with sales.pipeline_risk_factors (right slot) in the TwoColumnTextarea widget. Visually positions the "what we're assuming" narrative directly next to the "what could break those assumptions" narrative, forcing the team to write them in concert (rather than as two independent surfaces that drift apart over quarters). Common pitfall: writing assumptions without their corresponding risks (or vice versa) means the forecast is incomplete — every assumption should pair to a risk factor that captures the failure mode.

Total number of active opportunities in the pipeline (open stages only — excludes closed-won and closed-lost). The volume side of pipeline coverage; paired with pipeline_value gives the average deal size and the deal-count vs deal-size ratio that characterizes the motion shape. Common pitfall: counting non-bona-fide opportunities (orphaned trials, demo requests that never converted to a real evaluation) inflates the number — apply a stage-floor cutoff (e.g. SQL or higher) so the count reflects committed evaluation activity.

Container handle for the additive / subtractive pipeline-flow bridge — reconciles opening pipeline to closing pipeline through the period's adds, wins, and losses (opening + new_opps − closed_won − closed_lost = closing) with dual count + value columns. Renders via the FlowSubform widget. The audit trail of the pipeline motion — without this, period-over-period pipeline changes are unexplained. Common pitfall: a "scrub" line (deals reclassified from open to lost mid-period) is needed to keep the math reconciling when CRM hygiene happens; without it the flow appears not to balance and trust in the underlying numbers erodes.

Container handle for the field-array of key in-flight deals — each entry tracks deal name, current stage, dollar value, and confidence/commit status. Renders via the CollapsibleFormItemCardGallery widget (a reused gallery pattern shared with HR keyHires / keyOpenings). The "named deals the board should know about" surface — typically the top 5–10 deals by value or strategic importance. Common pitfall: a static list that doesn't reflect the current quarter — these should be refreshed each period to reflect actual top-of-mind deals, not carried forward from prior packs.

Container handle for the addable per-quarter forecast rows — each row tracks quarter, totalPipelineValue, weightedPipelineValue, expectedCloses (committed forecast), and dealCount. Rendered via the AddableQuarterlyForecastTable widget. Provides the multi-quarter forward visibility view the board reviews to validate the next 2–4 quarters of revenue, not just the current quarter. Common pitfall: filling in only the current quarter and treating future quarters as "we'll figure it out" — multi-quarter forecasting forces honest top-of-funnel planning for the periods beyond the immediate one.

Narrative listing the material risks to pipeline conversion or deal timing — specific deal slips, segment headwinds, budget freezes, competitive entry, ICP-fit misses on late-stage deals. Distinct from sales.key_concerns (which covers the whole sales motion) — this is specifically about the forecast / pipeline conversion math. Common pitfall: vague risks ("market is choppy") aren't actionable; a useful entry quantifies the at-risk dollar amount and names specific deals or segments. Renders side-by-side with sales.pipeline_assumptions in the TwoColumnTextarea widget.

Container handle for the per-stage pipeline metrics grid — for each pipeline stage (qualification, discovery, evaluation, proposal, negotiation, closing) tracks dealCount, totalValue, closingProbability, winRateFromStage, and avgTimeToClose. The most diagnostic surface in the pipeline view: where deals are bunching, which stage is the bottleneck, where conversion math is breaking. Rendered via the StageMetricsGrid widget seeded from PipelineStageValues. Common pitfall: trusting unchanged stage probabilities even as the deal mix shifts — re-calibrate the per-stage close rates quarterly against actuals or the weighted forecast drifts unreliably.

Sum of the dollar value of all active deals currently in the sales pipeline — unweighted (raw deal-value sum, not probability-weighted). Boards read this as the top-of-funnel sufficiency check: if pipeline coverage (pipeline value / forecast) drops below the historic conversion-rate-implied threshold, the forecast is at risk. Common pitfall: confusing pipeline value with weighted forecast — the unweighted number always exceeds the weighted, often by 3–5× depending on the stage mix. Always report both and the implied conversion ratio.

The team's expected closed-won dollars for the current quarter — usually a sales-leader judgment call informed by weighted forecast but adjusted for deal-by-deal commit confidence. Distinct from weighted_forecast (which is mechanical, stage × probability). Boards read both: a quarterly_forecast materially below weighted_forecast means the team has explicit negative judgment on specific big deals; above it means they're calling deals stronger than the stage probabilities suggest. Common pitfall: anchoring the call to plan rather than reality — boards quickly learn to discount "we will hit plan" forecasts and reward calibrated commit-vs-actual track records.

Total revenue recognized under the company's accounting standard (ASC 606 / IFRS 15) during the period — distinct from billings (what was invoiced) and from ARR (an annualized run-rate snapshot). The income-statement top line and the basis for GAAP reporting. Common pitfall: confusing recognized revenue with ARR — for a company with mid-year contract starts, ARR exit will exceed recognized revenue for that year; the gap shrinks as the cohort matures. Boards reviewing a recognition-heavy investor pack should always see ARR alongside revenue to avoid mis-pricing growth.

Container handle for the three-section quarter-over-quarter compare object that tracks average days-to-close trend (lastQuarter / thisQuarter / improvement). Renders via the QuarterToQuarterImprovementGrid widget with three slots. The "is the motion getting faster or slower" diagnostic — cycle length trend is one of the most reliable leading indicators of ICP fit and packaging quality. Common pitfall: comparing without controlling for deal-size mix — if up-market mix is shifting, a flat cycle is actually an improvement (because up-market cycles are inherently longer). Note the mix context in commentary if material.

Forward-looking narrative naming the next-period (typically next-quarter) sales priorities — segment bets, pipeline-coverage actions, hiring focuses, enablement themes, ICP refinements. The "what we're changing or doubling-down on" surface, complementing strategic_context (which is past-tense) and key_concerns (which is present-tense). Common pitfall: listing too many focus areas (3 is the practical maximum a team can actually execute against; 7+ means everything is a priority, i.e. nothing is). Boards use this to track promise-vs-delivery quarter over quarter.

Free-text narrative of the critical issues, pipeline risks, or blockers in the sales motion that require board attention this period. Distinct from sales.pipeline_risk_factors (which is forecast-specific) — this is the full-stack sales-org concerns list including hiring, comp, churn-cluster patterns, large-deal slippage, and competitive losses. Common pitfall: under-reporting concerns because the team wants to show progress — boards explicitly invite this surface so they can help, and a board pack with no concerns surfaces is itself a yellow flag (either the team is hiding something or not introspecting deeply enough).

Executive-summary narrative for the sales section of the board pack — the CRO/CEO's one-screen synthesis of overall sales performance, market dynamics, and the story behind the quarter's numbers. Categorical state derived from operational reporting — no calculation. Renders via ExecutiveCommentary widget as multi-section tabbed prose with per-section word counts. Common pitfall: writing it as a numbers-recap repeats what the KPI table already shows; the goal is the connective tissue — why the numbers moved, what changed in the market, what the next 90 days look like. Boards read this first when scanning the deck.

Opening ARR at the beginning of the period — the baseline against which the period's ARR waterfall (new + expansion − downgrades − churn) reconciles to ending ARR. Equal to the prior period's closing ARR by construction. The FlowSubform widget binds starting_arr as the `start` slot of the ARR-bridge flow, and the ending position is computed as start + Σ(deltas). Common pitfall: restating starting_arr mid-period to "fix" a prior-period reporting error breaks the period-over-period audit trail; corrections should land as a separate restatement note, not by editing the opening balance.

Total pipeline value with each deal multiplied by its stage-based close probability — the canonical probabilistic forecast number. More forecasting-useful than raw pipeline value because it accounts for the conversion-likelihood mix across stages (early-stage deals weighted ~10–25%, mid-stage ~40–60%, late-stage ~70–90%). Common pitfall: using globally-flat probabilities (e.g. always 50%) instead of stage-specific calibrated ones — a reliable weighted forecast requires the stage probabilities to be back-tested against actual close rates from prior periods.

Percentage of closed opportunities that resulted in closed-won (vs closed-lost) during the period. The single best read on bottom-of-funnel execution and the most direct input to pipeline-coverage math (required coverage = 1 / win rate). Common pitfall: computing win rate without disqualifying "no decision" outcomes inflates losses and depresses the rate artificially; the SaaS norm is to either bucket no-decisions separately or track a two-rate view (raw win rate vs ICP-fit win rate excluding no-decisions). Stage-segment cuts (SMB vs Enterprise) usually differ 2×–4× and should be reported separately when volume permits.

Share of total ARR flagged as at-risk for churn or contraction — the proportional view that complements the absolute `arr_at_risk` dollar figure. Computed as `arr_at_risk ÷ total ARR`. The board reads this as the worst-case-near-term-NRR-impact ceiling: if every at-risk account actually churned in-period, NRR would drop by roughly this percentage (before expansion offset). Common pitfall: the "at-risk" definition is internal and varies by company — a 12% percent_arr_at_risk under a conservative flagging rule is a very different signal than 12% under an aggressive rule. Document the flag rule and hold it constant.

Period-over-period percent change in Average Contract Value (mean ARR per active customer logo). A rising ACV trend signals pricing power, successful tier upgrades, or a mix-shift toward larger customers; a falling ACV trend signals seat compression, discounting pressure, or a mix-shift toward smaller customers. The board reads this alongside `total_customers` and `customers.net_revenue_retention` to disambiguate which lever is moving — logo growth vs. expansion vs. price. Common pitfall: ACV mix-shifts (a wave of new SMB logos at low ACV) can drag the average down even when existing-customer ACV is rising — segment-cut ACV is more diagnostic than the blended number.

Sum of ARR from customers flagged "at-risk" by the customer-success team — typically driven by usage decline, low health score, executive turnover at the customer, missed milestones, or explicit churn intent. The board reads this as the worst-case near-term churn exposure if no intervention happens. Common pitfall: the "at-risk" definition drifts across CSMs and quarters; standardize the criteria (e.g. health score below threshold OR 30-day usage drop > X% OR cancellation request received) and version-control the playbook so the absolute number is comparable period-over-period. Pair with `percent_arr_at_risk` for the proportional read.

Named at-risk accounts, root-cause analysis of why they're at risk, and the mitigation plan in flight. Pairs with the quantitative `arr_at_risk` and `percent_arr_at_risk` and gives the board the names + the playbook. Common pitfall: listing the at-risk accounts without the diagnosis or the plan — the board reader needs to see what the team is doing about it, not just what the team is worried about. Also: avoid using this surface as a generic "things are bad" venting forum — keep it account-specific and action-specific.

Active programs the CS / Product / Sales team is running to improve customer health, NPS, retention, or expansion — onboarding revamps, health-score model updates, success-plan rollouts, expansion playbooks, advocacy programs, executive-business-review cadence changes. The board reads this as the "what are we doing about it" companion to the metric pages and the at-risk narrative. Common pitfall: listing initiatives without owner, target metric movement, or checkpoint date — the board cannot follow up on vague programs.

Count of customer logos that ended their subscription/contract during the period. Includes voluntary cancellations and non-renewals. Some companies separately track downgrade-to-zero as churn — be explicit about whether downgrades that drop ARR to $0 count as churn (typical: yes) vs. material contraction that keeps ARR > 0 (typical: tracked under contraction, not churn). The board reads this as the raw count behind `logo_churn_rate`; the percentage tells you the rate, the absolute count tells you the volume of CS pain. Common pitfall: counting customers that re-activate (sometimes called "boomerang" or resurrection) — settle the rule (typical: count each cancellation event, do not net resurrection).

Identified upsell, cross-sell, and seat-expansion opportunities inside the existing customer base, with deal size and timing where known. This is the qualitative narrative behind the expansion component of NRR — what the CS / Sales team sees in the pipeline that has not yet converted. The board reads this as forward-looking signal on whether NRR will trend up or down next quarter. Common pitfall: confusing "opportunities" (real conversations with named accounts) with "addressable upside" (theoretical TAM uplift) — keep this field anchored in actual pipeline.

Recurring revenue retained from the cohort of customers present at the start of the period, excluding expansion — so the metric captures only churn and contraction. Per the SaaS Metrics Standards Board (SMSB) GRR standard. GRR is bounded at 100% (cannot exceed it) and reads as the "no-defense-against-churn" floor on retention. The board reads GRR alongside NRR (`customers.net_revenue_retention`) — the gap between them is the expansion contribution. Common pitfall: treating GRR and NRR as substitutes — they answer fundamentally different questions, and a healthy NRR with sliding GRR signals churn masked by upsell.

Share of customer logos lost during the period — the inverse of logo retention. Numerator is logos that churned during the period; denominator is logos present at period start. Per the KBCM/Sapphire Private SaaS Company Survey definition (treated as the de-facto private-SaaS reporting convention). The board reads this as the simplest churn signal — independent of revenue-weighting. Common pitfall: confusing annualized vs. period-rate (monthly churn × 12 ≠ annualized churn for a compounding base) — be explicit about the time window and annualization method.

Share of customer logos retained from the prior period, counted by logo (not by revenue). Per the SaaS Metrics Standards Board (SMSB) Logo Retention standard: numerator is logos present at both period start and period end; denominator is logos present at period start. New logos acquired during the period are excluded from both. The board reads this as a "stickiness" signal independent of ACV: high logo retention with weak NRR points to flat/contracting expansion; weak logo retention with strong NRR points to high concentration risk. Common pitfall: conflating logo retention with revenue retention — they answer different questions and routinely diverge.

Recurring revenue retained from the cohort of customers present at the start of the period, including expansion (upsell, cross-sell, price increases) and net of churn and contraction — but excluding revenue from net-new logos acquired in-period. Per the SaaS Metrics Standards Board (SMSB) NRR standard. NRR above 100% means the cohort grew faster than it lost — a hallmark of strong product-led expansion. The board reads NRR alongside GRR (`customers.gross_revenue_retention`) to separate the "keep + expand" signal from the "just keep" signal. Common pitfall: mixing GAAP revenue and ARR in numerator vs. denominator, or letting net-new logo revenue leak in — both inflate the number; SMSB is explicit that the cohort is closed at period start.

Net Promoter Score — % of survey respondents who are promoters (score 9–10) minus % detractors (0–6), passives (7–8) excluded. Per the original NPS methodology (Reichheld, Bain & Company, 2003). The score ranges from −100 to +100. The board reads NPS as one read on product-market fit and word-of-mouth potential, not as a precise customer-loyalty measurement — the methodology is well-known for being sensitive to sample bias, response rate, and survey timing. Common pitfall: comparing NPS across companies without normalizing for industry — B2B SaaS NPS distributions sit much higher than consumer-app NPS, and the absolute number means little without a peer cohort.

Period-over-period change in NPS score — the trajectory signal that matters more than any single absolute score. A 5-point swing between adjacent quarters is usually more informative than a "good" or "bad" absolute label, because the methodology's noise floor is high enough that absolute comparisons across companies (or even across quarters with different sample sizes) are unreliable. The board reads this to spot deterioration early — a persistent multi-quarter decline is one of the leading indicators of pending churn. Common pitfall: comparing periods with very different sample sizes or response rates — a "decline" from 45 to 35 means very different things at n=30 vs. n=300.

Free-form commentary from the CS / Sales leadership on retention trends, cohort behavior, and underlying drivers of loyalty (or its absence). Pairs with the quantitative retention KPIs (NRR, GRR, logo retention) and gives the board the "why" behind the numbers — which cohorts are strong, which are weak, what feature engagement correlates with retention, what onboarding changes are landing. Common pitfall: filler prose that restates the numbers without adding causal insight — a board reader should learn something here they could not infer from the metrics page alone.

Share of total ARR contributed by the top N customers — typically top 5 or top 10. Measures revenue concentration risk: a high concentration means losing one big customer would materially dent ARR. The board reads this alongside `arr_at_risk` and the customer list to gauge how much of the company's future is tied to a handful of accounts. Common pitfall: hiding parent-account aggregation — if three "customers" are subsidiaries of the same parent, true concentration is higher than the count-by-logo view shows; settle parent-rollup rules and document them in `customer_definition_note`.

Count of active paying customer logos at the end of the period. "Active" means the customer has a live paid subscription or contract on the reporting date — not trial, not cancelled, not zero-revenue. The board reads this alongside ARR to triangulate whether growth is logo-driven (more customers at similar ACV) or expansion-driven (existing customers paying more). Common pitfall: definitions of "customer" drift over time as the company sells to subsidiaries, parent accounts, or self-serve users — settle the counting unit (parent vs. account vs. seat) and document it in `customer_definition_note` so cross-period comparisons stay honest.

Breakdown of engineering capacity across new features, maintenance, and tech debt — typically reported as a three-way split summing to 100%. The execution-level view of where engineering hours are actually going (vs. `innovation_capacity_pct` which is a single percentage for new-capabilities work, and vs. `offensive_roadmap_pct` which is a roadmap-classification percentage). Common pitfall: capacity allocation reported in plan rather than actuals. The plan can say 60% new features but the actuals can be 30% new features and 50% support work — the gap is the operating signal. Boards should require both planned and actual splits, at least quarterly.

Percentage of customer churn (logo or ARR, define explicitly) where the primary stated reason is product or quality problems — bugs, performance, missing core functionality, reliability incidents. Distinguishes product-driven churn from pricing-driven, competitor-driven, or use-case-fit-driven churn. Common pitfall: relying on free-text exit-survey reasons. Customers commonly cite "price" when the underlying issue was reliability or missing features — boards should require both the customer-stated reason and the CSM/Account-Manager-assigned root cause, and watch the gap. The Pendo "Product-Led Growth Benchmark" and similar product-analytics publishers cover product-driven churn qualitatively, not as published numeric ranges.

Percentage of committed deliverables shipped on or before the originally-promised date within a measurement window (typically a quarter). Surfaces whether the engineering organization can be trusted to hit commitments the company makes externally — to customers in contracts, to the board in quarterly plans, to GTM teams sequencing launches. Common pitfall: gaming. Teams over-deliver by under-promising (predictability climbs while velocity drops) or move the goalposts (re-baseline mid-quarter so "on-time" stays high). Boards should ask for "predictability against original commitment", not "against current plan", and pair with throughput trends.

Percentage of the planned roadmap (typically next 1–2 quarters) allocated to offensive bets — net-new capabilities, market expansion, differentiation moats, new monetization. The "what proportion of the plan is about winning" view. Common pitfall: counting "improvements to existing features" as offensive when the change is really table-stakes parity work. Boards should expect a McKinsey-style horizon framing (Horizon 1 = core, Horizon 2 = adjacent, Horizon 3 = transformational) or an equivalent classification, and apply it consistently. Per the original McKinsey "Three Horizons" framing (Baghai/Coley/White, "The Alchemy of Growth", 1999), a healthy portfolio funds all three — over-indexing on any one is a strategic risk.

Percentage of R&D capacity (typically measured in engineering-weeks or story points over a quarter) allocated to net-new capabilities, as opposed to maintenance, bug fixes, internal tooling, or customer-support engineering. The "available bandwidth for offense" view. Common pitfall: confusing innovation capacity (input — how much team-time is available for new work) with `offensive_roadmap_pct` (output — what proportion of the planned roadmap is growth-oriented). A team can have 60% innovation capacity allocated entirely to defensive work if the roadmap demands it. Boards should look at both together.

Container handle for the field-array of strategic product initiatives committed for the current quarter / half — each entry tracks the initiative name, status (on-track / at-risk / blocked / shipped / cut), owner, target date, and a one-line explanation or mitigation plan. The structured, per-initiative companion to the `product.key_initiatives_status` narrative: the narrative gives the execution-pulse story, this gallery makes each initiative individually trackable with its own owner and status. Renders via the CollapsibleFormItemCardGallery widget (the reused gallery pattern shared with sales pipeline deals and HR key hires / openings). Common pitfall: every initiative defaults to "on-track" until two weeks before its deadline — require an explicit at-risk state with a mitigation plan, not a re-label at the deadline.

Stoplight-plus-narrative status of the strategic product initiatives committed for the current quarter / half — each initiative ideally tagged on-track / at-risk / blocked / shipped, with a one-line explanation. The execution-pulse view that connects strategy intent to delivery reality. Common pitfall: every initiative defaults to "on track" until two weeks before the deadline, then turns red — a board that only sees binary green-or-red status without intermediate "at-risk" signaling is being managed reactively. Pair with `delivery_predictability` to detect this pattern; require at-risk initiatives to surface a mitigation plan, not just a label.

Container handle for the field-array of products in the portfolio — each entry tracks the product name, its portfolio classification (e.g. growth engine / cash cow / innovation bet / sunset candidate, or Horizon 1/2/3), ARR contribution, investment thesis, and lifecycle stage. The structured, per-product companion to the `product.portfolio_strategy` narrative: the narrative tells the story, this gallery makes each product line individually visible and trackable. Renders via the CollapsibleFormItemCardGallery widget (the reused gallery pattern shared with sales pipeline deals and HR key hires / openings). Common pitfall: a portfolio gallery that lists products without an explicit classification or investment thesis per item — that is an inventory, not a portfolio.

Narrative overview of the product portfolio — which products are growth engines, which are cash cows, which are innovation bets, and which are candidates for sunset. The CEO/CPO articulation of "what game each product line is playing." Frequently structured along the McKinsey Three Horizons framing or the classic BCG growth-share matrix (stars / cash cows / question marks / dogs — per Bruce Henderson's "The Product Portfolio", 1970). Common pitfall: the portfolio narrative does not name horizons, life-cycle stages, or sunset candidates — a portfolio described entirely as "growth engines" is not a portfolio strategy, it is a wishlist. Boards should push for explicit classification of every material product.

Ratio of net-new ARR generated in a period to R&D spend in the same period — answers "how much revenue does each R&D dollar produce?" Distinct from sales-efficiency metrics (Magic Number, CAC payback) which measure sales/marketing productivity. Common pitfall: R&D-driven ARR (new capabilities, expansion features) shows up on a 2–4 quarter lag after the spend — single-period ratios mis-state the relationship. Boards should look at trailing-twelve-month R&D efficiency, not month-over-month, and pair with `innovation_capacity_pct` to understand whether the spend is on growth bets or maintenance.

Total monthly cash outflow on research and development — fully-loaded engineering, product, and design payroll plus tooling, infrastructure dedicated to product development, contractors, and direct R&D vendor spend. The "input" side of R&D efficiency. Common pitfall: companies report base-payroll R&D and exclude the loaded cost (benefits, stock comp at cash-cost basis, allocated rent, dev tooling), under-reporting true R&D burn by 25–40%. Boards should always ask whether the number is base-payroll, fully-loaded, or GAAP R&D expense — they tell different stories. The KBCM/Sapphire SaaS Survey reports R&D as a percentage of revenue for its company panel — use that as the benchmarking lens.

Percentage of the planned roadmap allocated to defensive work — platform reliability, security/compliance, scalability rearchitecture, table-stakes parity with competitors, customer-retention features. The complement of `offensive_roadmap_pct`. Common pitfall: defensive work is chronically under-funded (less visible to customers, harder to demo) until a quality-churn or scalability event forces a reactive surge. Boards should treat sustained zero or near-zero defensive allocation in a maturing product as a leading indicator of future quality issues — per the standard product-management argument (Marty Cagan and similar product-leadership writing), a healthy roadmap pays both growth and platform-health rent.

Months of system capacity remaining at the current growth rate before the platform requires major (not incremental) infrastructure investment — typically driven by the binding bottleneck (database, message bus, single-tenant compute ceiling, regional capacity, or compliance-driven re-architecture). Surfaces the "scale runway" alongside the financial runway. Common pitfall: a single number hides which bottleneck binds. Boards should require the bottleneck to be named ("database shard hot-spot binds at ~150K accounts at current growth, ~4 months out"), not just the headline months — a named bottleneck makes the investment decision concrete.

Percentage of total ARR contributed by the single largest product line. Diversification-risk indicator at the product level (parallel to customer-concentration risk at the GTM level). Common pitfall: concentration risk is dismissed when the dominant product is performing well — but a one-product company is a one-feature-decision-away from existential risk. Boards should track this number alongside the portfolio narrative; sustained 70%+ concentration in a maturing company should pair with a documented diversification thesis or an explicit decision to remain a single-product company. Frames analogous to customer-concentration discussions in venture diligence (NfX / Bessemer founder essays cover the customer-side; the product-side analogue follows the same logic).

Headcount of engineers (software, infrastructure, security, data, ML) in the R&D organization, typically including full-time employees plus contractors at a defined FTE-equivalence factor. The "capacity input" side of all R&D ratios. Common pitfall: definition drift. Some companies include only software engineers, others include product managers and designers, others include all of R&D plus QA, plus support engineers. Boards should anchor the definition once and hold it stable — otherwise quarter-over-quarter comparisons are noise. Pair with `rd_monthly_spend` to derive fully-loaded cost-per-engineer.

Percentage of customers (weighted by ARR) actively using a defined set of strategic features within a measurement window. The "ARR-weighted" framing matters: a feature used by 30% of customers covering 70% of ARR is a different signal than 30% of customers covering 5% of ARR. Common pitfall: defining adoption as "ever used" rather than "actively using" (returning use in the measurement window) — the first metric only goes up and tells the board nothing. Boards should require an active-use definition (e.g. used in 2 of the last 4 weeks) and a per-feature breakdown for the strategic feature set.

Board-approved end-of-period headcount target. The contractual reference point against which `hr.total_headcount` and `hr.open_positions` are read — drift means either hiring under plan (typically a growth concern) or over plan (typically a burn-discipline concern). Common pitfall: silent in-year adjustments — boards approve a number, the CEO informally expands or contracts to it, and the variance never gets reconciled. Best practice is to treat changes to this number as board-action items, recorded in `hr.board_actions`.

Annual Recurring Revenue divided by total FTE-equivalent workforce — the canonical SaaS workforce-productivity ratio anchored to the SaaS Capital Annual Survey methodology (revenue per employee benchmarks). A high-signal denominator for "are we over- or under-staffed for our revenue scale?" Common pitfall: choosing different ARR conventions (ending vs average, GAAP-reconciled vs raw) without locking in a board-level standard. Best practice is to pair this with `sales.arr` so the numerator is unambiguous and to disclose whether contractors are included in the FTE denominator.

Count of employees actively flagged as flight risk by managers, based on engagement signals (skip-level surveys, manager 1:1s, counter-offer activity, tenure-curve risk). A leading indicator that complements the lagging `hr.voluntary_exits` number. Common pitfall: stale flags that never get cleared — at-risk lists tend to drift toward "every senior IC ever" without manager discipline. Best practice is a quarterly refresh with explicit add/remove notes and an action attached to each flag.

Mean elapsed days between requisition opening (approved and posted) and offer acceptance, averaged across requisitions filled in the period. The headline recruiting-velocity KPI commonly tracked in the SHRM Talent Acquisition Benchmarking Report. Common pitfall: choosing between time-to-fill (req-opened to offer-accepted) and time-to-hire (first-applicant to offer-accepted) without locking the convention — the two can differ by weeks. Best practice is to standardize on time-to-fill (the SHRM benchmark convention) and document any deviation.

Field-array of per-department rows — department name, leader status (resolved against `hr.leader_status`), and headcount metrics with stable-count auto-calc — rendered as a drag-sortable table grouped by department. Common pitfall: department boundaries drift over time (Eng+R&D merging, GTM splitting into Sales/Marketing/CS) — when boundaries change, prior-period comparisons need an explicit reconciliation note. This KPI is structural, not numeric — no formula applies.

Derived triple — effective FTE, cost-per-FTE, and annualized payroll — computed from `hr.payroll_run_rate` + `hr.total_contractors` and a contractor-to-FTE conversion factor. Lets the board see capacity in normalized terms even when the staffing mix shifts. Common pitfall: choosing a contractor-to-FTE factor without explicit board agreement — some companies use 1.0 (1 contractor = 1 FTE for capacity), others use 0.8 (account for ramp / partial-engagement), others use cost-equivalent ratios. Lock the convention.

Forward-looking narrative on next-period hiring priorities — target roles, sequence, sourcing strategy, and any unusual asks (executive search, specialized recruiter spend, location flexibility shifts). Anchors the board's understanding of where capacity is heading and what approvals or help are needed. Common pitfall: a stale plan that gets copy-pasted across quarters — the hiring plan should evolve with strategy shifts. Best practice is to lead with the 2–3 highest-priority hires and their justification, then a brief on backfills and bench-builds.

Explicit list of HR items requiring board attention, approval, or decision in this meeting — executive comp changes, headcount-budget changes, equity-pool top-ups, employment-policy approvals, and any items needing a board resolution. Common pitfall: burying decisions inside other narrative sections — boards consistently miss requests that are not explicitly tagged as "decision required." Best practice is to label each item as approval-required vs awareness-only and give a one-line ask.

Stacked commentary editor with per-section icon and live word count, hosting the four canonical HR narrative slots (talent highlights, talent challenges, hiring plan, retention initiatives) under a single base path — each section persists under `<basePath>.<sectionKey>`. The composite container for the narrative side of the HR scorecard, paired with `hr.departments` and `hr.risk_items` for the structured side. Common pitfall: writing each section in isolation — strong commentary cross-references the numbers ("voluntary turnover up 4 points QoQ, here is what we are doing").

Structured field-array of board-attention items, each with type / department / action / narrative quartet (problem / impact / proposal / ask). Chip color follows boardActionNeeded: approval=red, assistance=yellow, awareness=blue. The structured-table version of `hr.board_actions` — preferred when the board has adopted the formal risk-item pattern. Common pitfall: drift toward vague "we are working on it" entries — strong items name a specific action with a date.

Annualized rate of company-initiated separations as a percentage of average headcount. Complement to `hr.voluntary_turnover_rate`; together they form the total turnover picture per the Mercer US Turnover Survey methodology. Common pitfall: lumping one-time RIFs into the steady-state rate, which makes the trend unreadable. Best practice is to report steady-state involuntary turnover and call out any RIF events separately in `hr.board_actions` with the headcount delta.

Field-array of notable individual hires that warrant board-level visibility — typically C-1 executives, director-level functional leaders, and strategic specialist hires. Per-item shape: name, level, role, start status, days-to-fill. Rendered via the T2 collapsible-card gallery pattern. Structural, not numeric — formula does not apply. Common pitfall: listing every hire instead of the strategic few — boards lose signal quickly when this section turns into a directory.

Field-array of priority open roles the board should be aware of and may be able to accelerate — typically C-1 executives, hard-to-fill specialists, and any role open >60 days. Per-item shape: title, department, level, urgency, owner. Rendered via the T2 collapsible-card gallery pattern. Structural, not numeric. Common pitfall: padding the list with every open req — boards add the most value on the 3–8 strategic openings, not on backfilling the next IC.

Tri-state leader status (permanent / interim / vacant) for each board-tracked department. Permanent shows name+title; interim shows the covering person; vacant shows the gap explicitly. The single most board-relevant org-design signal — an extended interim or vacant status in a strategic function is almost always a board-level concern. Common pitfall: leaving "interim" indefinitely as a way to avoid the search-and-hire conversation — boards should set a maximum interim duration and treat overruns as board-action items. Structural KPI; no formula.

Net change in employee headcount during the period — new hires minus (voluntary exits + terminations). The bottom-line growth-or-contraction number on the HR scorecard. Common pitfall: reporting net change without showing the gross-in / gross-out components — boards can't diagnose a flat net number caused by 5 hires and 5 exits the same way they'd diagnose a flat number from zero on each side. Best practice is to surface the four components (new hires, voluntary exits, terminations, net change) together.

Count of employees whose first day fell within the reporting period. The growth-input side of the headcount equation, paired with `hr.voluntary_exits` and `hr.terminations` on the loss side. Common pitfall: counting accepted offers vs actual start dates — these can diverge by weeks (notice period) or fall through entirely (offer rescind, candidate ghosting). The board number should be actual starts, not signed offers; pipeline movement belongs in `hr.hiring_plan` narrative.

Count of board-approved roles that are currently posted and unfilled (requisition open, offer not yet accepted). The leading-edge indicator for upcoming hiring capacity demand. Common pitfall: "approved" drift — roles that were verbally green-lit but never went through the approval gate get counted here, inflating the number. The board number should match the approved headcount budget; everything else belongs in narrative as "pipeline ideas."

Monthly fully-loaded payroll cost as a percentage of `finance.gross_burn_rate`. Tells the board what share of cash outflow funds people vs everything else (infra, GTM spend, professional services, facilities). Common pitfall: comparing this ratio across companies without normalizing for stage and capex intensity — a pure-software seed company will run very payroll-heavy; a hardware-or-bio company will not. Best practice is to read this in conjunction with the burn-rate trend, not in isolation.

Annualized fully-loaded payroll cost based on current employee compensation — wages plus employer-paid taxes, benefits, and typical equity refresh allocation. Used as the dominant input into `hr.payroll_as_pct_of_burn` and the projection for `hr.fte_metrics`. Common pitfall: reporting base-salary-only and missing employer payroll taxes, benefits, and bonus accrual — this can understate true cost by 15–30%. Document the loading convention (typically wages × 1.20–1.30 for US fully-loaded) and apply consistently.

Count of employees currently on a formal Performance Improvement Plan (PIP) or equivalent performance-bar process. Leading indicator for `hr.terminations` — most PIPs that do not resolve with measurable improvement convert to involuntary exits within one quarter. Common pitfall: confusing PIPs with informal coaching — only employees on a written, time-bound plan with defined exit criteria should be counted here. Informal "we need to talk" relationships belong in the at-risk count, not this number.

Narrative on the programs and actions in flight to retain key talent and reduce voluntary turnover — refresh grants, comp-band adjustments, manager training, career-pathing programs, and similar. The response side of the `hr.at_risk_count` and `hr.voluntary_turnover_rate` story. Common pitfall: listing perks (snacks, swag) instead of actions tied to retention drivers. Best practice is to name the initiative, the at-risk population it targets, and the leading-indicator metric you'll watch.

Narrative on key hiring difficulties, attrition concerns, comp-market pressure, and market-driven talent risks that the board should weigh in on or be aware of. The "watch this" companion to `hr.talent_highlights`. Common pitfall: sanitizing this section to avoid uncomfortable conversations — but talent challenges are precisely where boards add the most value (warm intros, comp benchmarking, executive search). Best practice is to name the specific role, team, or risk and the ask explicitly.

Free-form narrative on notable hires, promotions, internal moves, and other positive organizational developments the board should be aware of. The "good news" companion to `hr.talent_challenges`. Common pitfall: listing every internal move and burying the genuinely important signals (key executive hires, strategic team-build milestones). Best practice is 3–5 bulleted items per period, each tied to a board-relevant outcome or risk-it-mitigates rather than a generic celebration.

Count of company-initiated employee separations during the period — performance-management exits, layoffs, redundancies, and for-cause terminations. The numerator of `hr.involuntary_turnover_rate` and the inverse of `hr.voluntary_exits` on the attrition page. Common pitfall: bundling layoff events (often one-time, board-known) with normal performance-management churn (steady-state, manager-driven). Best practice is to break out layoffs in `hr.talent_challenges` narrative and reserve this number for the recurring stream.

Count of active 1099 contractors, consultants, agencies-of-record, and similar non-employee labor at period end. Tracked separately from `hr.total_headcount` because the cost structure, retention dynamics, and classification risk are different. Common pitfall: under-counting agencies that bill on a project basis without per-head visibility — these often slip out of HR systems and surface only in finance AP detail. A contractor-to-FTE ratio above ~30% sustained typically warrants a classification audit and a deliberate "build vs rent" board conversation.

Total number of employees (W-2 / direct-employment equivalents) across all departments at period end. The base denominator for nearly every other HR ratio — turnover rate, revenue per FTE, payroll as % of burn — so getting the snapshot date and the FTE-vs-headcount convention right matters. Common pitfall: mixing headcount (people) with FTE (capacity) — they diverge whenever part-time, contractor, or shared-services arrangements exist. Document the convention (typically "FTE-equivalent, employees only, end-of-period") at the board level once and apply consistently.

Count of employees who resigned during the period (initiated by employee, not the company). The numerator of the `hr.voluntary_turnover_rate` calculation and the headline "are we losing people" number boards anchor on. Common pitfall: ambiguous "mutually agreed" exits — companies sometimes log managed-out exits as voluntary to keep the visible number low. Define the test: if the employee initiated the conversation and there was no formal performance trigger, it is voluntary; otherwise log as termination.

Voluntary exits over a trailing period, expressed as an annualized percentage of average headcount — the headline attrition number on the HR scorecard. Anchored to the Mercer US Turnover Survey methodology (Mercer reports voluntary vs involuntary turnover annually). Common pitfall: comparing a single quarter's annualized rate against an annual benchmark — short-window annualization is noisy. Best practice is trailing-12-months for benchmark comparison and trailing-3 or trailing-6 for trend reads. Per #1426: stage-specific industry norms here are folk-wisdom unless tied to a specific Mercer or comparable published cut.

Capital that investors have agreed to invest — including both soft commitments (verbal / handshake / IOI) and hard commitments (signed term sheet or executed subscription docs). Treat this as the round-progress odometer. Common pitfall: soft commitments are notoriously squishy — every published fundraising postmortem (per First Round Review and Bessemer founder essays) warns that founders over-count soft commits. Board-best-practice is to track soft vs hard separately or to define a haircut convention (e.g. 50% of soft) at the start of the round.

Percentage of founders' fully-diluted ownership that is given up in the new round, including any pre-close option-pool top-up (the "option pool shuffle" — option-pool expansion taken in the pre-money dilutes existing holders rather than new investors). Common pitfall: founders often quote the "investor dilution" (new money / post-money) and forget the option-pool top-up component. The Carta State of Private Markets quarterly reports publish stage-typical dilution ranges that boards should use as a sanity check.

Explicit assumptions underlying the fundraising plan: valuation expectation, lead-investor probability, time-to-close, post-close runway, and what changes if any assumption breaks. Common pitfall: assumptions are made implicitly and only surface in the postmortem. Boards should require this section to be reviewed each update — a board update where assumptions never change suggests they are not being tested, not that they are correct.

Named risks that could prevent the round from closing as targeted — market conditions (general venture sentiment, sector-specific freeze), investor-side risk (anchor investor wobble, partner-meeting drop-off), company-side risk (a metric trending wrong direction, customer concentration concern surfaced in diligence), and timing risk (runway versus close date). Common pitfall: optimistic CEOs under-report risk factors. Boards should expect at least 2–3 named risks even in a healthy round — "no risks" is itself a risk signal.

Free-text narrative covering the planned fundraising approach for the current round: target investor types (lead profile, co-investors), timing, sequencing of the conversation, use of proceeds, milestones the round will get the company to, and the alternative scenarios if the primary plan slips. This is the "what is the CEO actually doing" section of the fundraising update. Common pitfall: strategy that does not name a target lead investor profile or use-of-proceeds milestone is not strategy — it is intent. Boards should push for specificity here.

Count of distinct investors actively engaged in the current round — defined as taken a first meeting and not yet declined or fully committed. Effectively a fundraising-funnel "qualified leads" number. Common pitfall: rosy pipelines that include investors who ghosted weeks ago — best practice (echoed across NfX, First Round Review, and Bessemer founder essays) is to age-out any investor with no contact in 14+ days. Track separately from total intros taken and from hard commitments to make the conversion math legible.

Container handle for the field-array of named fundraising milestones the board should track to the close — each entry tracks milestone name, type (e.g. term-sheet signing, IC presentation, close), target date, status (upcoming / in-progress / completed / at-risk), responsible party, and notes. The "what has to happen, by when, and who owns it" surface that turns the round narrative into a tracked plan. Renders via the CollapsibleFormItemCardGallery widget (the reused gallery pattern shared with sales pipeline deals and HR key hires / openings). Common pitfall: milestones carried forward from prior packs without status updates — these should be refreshed each period so the board sees real progress, not a stale wishlist.

Floor — the smallest amount of committed capital required to legally close the round (often set in the subscription agreement) or the strategically smallest amount management would accept before re-pricing or pausing. Common pitfall: a `target_raise` of $10M and a `minimum_close_amount` of $4M tells a very different story than a target of $10M and a minimum of $9M — boards should always see both. Per common practice (NVCA Model Documents allow flexibility here), the minimum is typically 50–75% of target at seed, 70–90% at A+.

The lowest pre-money valuation management would accept to close the current round — the valuation walk-away floor. Distinct from the precise NVCA-defined `pre_money_valuation` (the single negotiated point that actually prices the round): this is the bottom of the acceptable band the team set going in. Common pitfall: teams anchor only on a target valuation and have no pre-agreed floor, so in a soft market they negotiate against themselves with no board-sanctioned line. Pair with `fundraising.target_valuation` to give the board the band, and read both against stage-relative ranges from quarterly Carta / PitchBook reports.

Total principal value of SAFEs and convertible notes outstanding that have not yet converted to equity. These convert at the next priced round, typically at a discount or valuation cap (per the standard Y Combinator SAFE templates and the National Venture Capital Association convertible-note model). Common pitfall: a SAFE stack quietly accumulating between rounds can convert into 15–25% dilution at the next priced round, surprising founders who modeled "we only sold 10% in this priced round" math. Boards should always see the fully-diluted cap table including SAFE conversion.

Calendar date by which the round is expected to close (final wires received, definitive documents signed). Compared against `finance.runway_months` to detect a fundraising-against-the-clock situation. Common pitfall: planned close dates routinely slip 30–90 days in practice (collected founder postmortems on First Round Review) — boards should ask for both an "expected" and a "no-deal" date and watch the gap to actual runway exhaustion.

Company valuation immediately after the new round closes, including the new capital raised — the canonical "valuation" number quoted in TechCrunch headlines. Per NVCA Model Documents, post-money = pre-money + new money raised. Common pitfall: post-money math gets messy with SAFEs — modern post-money SAFEs (the YC 2018+ form, per the Y Combinator SAFE primer) fix dilution at the SAFE's valuation cap regardless of subsequent priced-round pricing, so the board should always reconcile the headline post-money against the fully-diluted cap table.

Company valuation negotiated with investors immediately before the new round closes — the denominator for the new investors' ownership math. Per the NVCA Model Documents, pre-money = post-money − new money raised. Common pitfall: when convertible instruments (SAFEs, notes) are outstanding, the "headline" pre-money the CEO quotes and the effective pre-money after conversion can differ materially — the board should always ask for both. Equally important: option-pool top-ups taken pre-close come out of the pre-money share count, diluting founders not investors (the "option pool shuffle").

Progress of the round expressed as committed capital divided by target. Read alongside `round_status` and elapsed-time-in-round to detect stalls. Common pitfall: percentage progress is misleading when measured against a shifting `target_raise` — when management lowers the target mid-round, the percentage jumps without any new commitments arriving. The board should always be told when this is a target revision vs. a real progress event.

Current phase of the active fundraising round on a coarse state machine (e.g. not-started, in-progress, term-sheet, closing, closed). The board reads this to know which playbook applies — pipeline-building, diligence, closing, or post-close communications. Common pitfall: the field drifts when a round stalls or pivots, so treat each phase change as a board-update trigger. The PhasePlaybook widget binds to this enum and surfaces the appropriate phase guidance read-only beside the editor.

Target gross capital the company intends to raise in the currently active round (the "ask"). This is the headline number the CEO walks investors through and the board uses to sanity-check dilution and runway implications. Note the distinction from `total_round_size` (which can include third-party participation beyond the company-led ask) and from `minimum_close_amount` (the floor at which the round can close). Common pitfall: the target is updated mid-process when investor demand or strategy shifts — every change deserves a board note.

The pre-money valuation the current round is being run to land — the valuation "ask" that anchors the pitch and the dilution math management is targeting. Distinct from `pre_money_valuation` (the precise NVCA-defined price the round actually closes at, known only once a term sheet is signed): this is the aim, set going in. The board reads the target alongside `fundraising.minimum_valuation` as a valuation BAND — the two together tell a very different story than a single point. Common pitfall: a target valuation set on 2021-vintage multiples in a compressed market; always sanity-check against current stage-relative ranges from quarterly Carta / PitchBook / SaaS Capital reports.

Cumulative gross equity capital raised across all prior rounds (and the current round in-progress). Treated as historical context — investors and board members look at this to gauge capital efficiency (capital raised vs. ARR achieved). Common pitfall: includes all equity but typically excludes convertible debt that has not converted, venture debt principal, and grants — be explicit about what is and is not included when the number is presented. Capital efficiency benchmarks (per KBCM, SaaS Capital, and Bessemer State-of-the-Cloud) compare `total_capital_raised` to current ARR — e.g. "$30M raised, $10M ARR" is efficient at A but lean at B+.

Cash that has actually been wired and cleared the company's bank account from investors in the current round. This is the cash-in-the-bank version of `committed_amount`. Common pitfall: commitments do not pay the bills — wiring can lag commitments by weeks to months for the second / third closes, and a committed-but-not-received delta of $5M+ can quietly extend the runway forecast incorrectly. Reconcile this against `finance.total_cash_in_bank` increases each period.

Total new capital being raised in the current round across all participants — the lead, follow-on investors, employee/strategic allocations, and any side-letter pieces. This is the figure that goes into the post-money math. Common pitfall: companies sometimes confuse `total_round_size` with `target_raise` — the round size is final and used in valuation math, while the target is what management is aiming for and can move during the raise. Boards should expect a specific breakdown by investor when this number is reported.

Undrawn capacity remaining on existing venture debt facilities. Optionality the company can call on quickly without re-pricing. Common pitfall: availability is conditional — most facilities require continued covenant compliance, and an available line can be pulled or frozen by the lender if cash, ARR, or other covenants slip (per the Bessemer venture-debt content and Battery Ventures primer). The board should treat `venture_debt_available` as a soft commitment, not a hard one, until drawn.

Stoplight state of the venture-debt facility covenants — typically minimum-cash, minimum-ARR or revenue, maximum-burn, customer-concentration, and material-adverse-change clauses (per the standard Bessemer / Battery Ventures venture-debt primers). A covenant trip can freeze the draw line, accelerate repayment, or both. Common pitfall: covenants are not always actively monitored between board meetings — drift between an internal forecast and a covenant threshold can cross the line silently. Boards should require monthly covenant headroom reporting when material debt is drawn.

Principal currently drawn from venture debt facilities (e.g. Silicon Valley Bank, Hercules Capital, Trinity Capital, Western Alliance, Bridge Bank facilities). Venture debt typically extends runway 6–12 months alongside the equity round — used well, it dilution-efficiently bridges to the next equity event; used poorly, it concentrates default risk into a single covenant covenant trip. Common pitfall: drawn debt creates interest expense and a repayment schedule that compresses runway in 18–24 months even though it extends runway today (per the Battery Ventures venture-debt primer and the Bessemer "venture debt playbook" series).

Composite SaaS health score that sums the company's revenue growth rate and a profitability proxy (commonly EBITDA margin or free-cash-flow margin) into a single percentage. Originally articulated by Brad Feld in 2015 and codified by the SaaS Metrics Standards Board, the rule frames the growth-vs-profitability tradeoff: a company growing at 60% with a −20% margin scores 40, equal to a company growing at 20% with a +20% margin. The board reads it to sanity-check whether growth is being bought at unhealthy burn or whether margin discipline is constraining growth too far. Common pitfall: which profitability proxy is used materially changes the score (FCF margin is the strictest, EBITDA more flattering, "operating margin" inconsistently defined), so pick one and disclose it next to the number.