# VARIANCE NARRATIVE — Q2 | B2B SaaS Company **Prepared for: Board of Directors** --- ## 1. DATA SUMMARY | Line Item | Actual | Budget | Variance ($) | Variance (%) | Prior Year | YoY Change (%) | |-----------|--------|--------|--------------|--------------|------------|----------------| | Revenue | $4.20M | $3.80M | +$0.40M | **+10.5%** | Not provided | Not provided | | COGS | $1.90M | $1.70M | +$0.20M | **+11.8%** ⚠️ | Not provided | Not provided | | Gross Profit | $2.30M | $2.10M | +$0.20M | **+9.5%** | Not provided | Not provided | | Gross Margin % | 54.8% | 55.3% | –0.5 pts | **–0.9%** | Not provided | Not provided | | OpEx | $2.80M | $2.50M | +$0.30M | **+12.0%** ⚠️ | Not provided | Not provided | | EBITDA | –$0.50M | –$0.40M | –$0.10M | **–25.0%** ⚠️ | Not provided | Not provided | > **Data Flags:** > - Prior year and YoY figures were not provided. Board comparisons are limited to budget variance only. > - Revenue outperformance (+$0.40M) did not drop through to EBITDA — cost growth outpaced revenue growth on both COGS and OpEx lines. This divergence warrants driver-level scrutiny. > - All three cost lines exceeded budget, suggesting a broad spending pattern rather than an isolated line item issue. --- ## 2. KEY VARIANCE DRIVERS **Materiality threshold applied:** >5% deviation OR >$50K absolute. All four P&L lines meet this threshold. --- ### Revenue: +$400K / +10.5% Favorable | Driver | Assessment | Quantification | Controllable? | Persistence | |--------|-----------|---------------|---------------|-------------| | **Volume** — New enterprise logos from Q1 product launch driving incremental ARR | Primary driver | Data suggests majority of $400K upside | Partially Controllable | Recurring if pipeline converts | | **Timing** — Possible Q2 pull-forward of deals originally budgeted for Q3 | Secondary consideration | Cannot quantify without pipeline data | Partially Controllable | One-Time risk | | **Price/Mix** — Enterprise segment typically carries higher ACV than SMB | Possible contributor | Cannot quantify without segment data ⚠️ | Controllable | Recurring | > **Flag:** Without segment-level or ARR waterfall data, it is not possible to confirm whether revenue upside is structural (new logos, expansion) or temporal (timing). Management should clarify in the Q&A. --- ### COGS: +$200K / +11.8% Unfavorable | Driver | Assessment | Quantification | Controllable? | Persistence | |--------|-----------|---------------|---------------|-------------| | **Volume** — Higher revenue base directly drives hosting, infrastructure, and support costs | Primary driver | Proportional to revenue growth; COGS grew 11.8% vs. revenue 10.5% — slight overage | Partially Controllable | Recurring | | **Mix** — Enterprise customers often require higher-touch onboarding, dedicated infrastructure, or implementation services | Secondary driver | Cannot quantify without segment data ⚠️ | Partially Controllable | Recurring if enterprise mix increases | | **One-Time** — Possible infrastructure scaling costs associated with product launch | Possible contributor | Unknown without detail | Controllable | One-Time | > **Notable Signal:** COGS grew 11.8% on 10.5% revenue growth, compressing gross margin by 50 basis points (55.3% → 54.8%). In a SaaS business, this direction of travel — even mildly — warrants monitoring. The data suggests the company is not yet achieving COGS leverage at this growth rate. --- ### OpEx: +$300K / +12.0% Unfavorable | Driver | Assessment | Quantification | Controllable? | Persistence | |--------|-----------|---------------|---------------|-------------| | **Headcount** — Series B companies at this stage typically deploy capital into Sales, Marketing, and Engineering post-raise | Likely primary driver | Cannot confirm without headcount data ⚠️ | Controllable | Recurring | | **Go-To-Market Investment** — Accelerated pipeline development following product launch | Probable contributor | Cannot quantify without department breakout ⚠️ | Controllable | Partially Recurring | | **One-Time Launch Costs** — Marketing events, external consultants, or tooling | Possible contributor | Unknown | Controllable | One-Time | > **Flag:** At 12.0% OpEx overrun on a –$500K EBITDA base, the board should request a department-level breakout to distinguish investment spend (intentional, forward-looking) from run-rate overruns (execution gap). These carry very different strategic implications. --- ### Top 3 Root Causes Across the P&L: 1. **Enterprise pipeline acceleration** (revenue driver — favorable, but cost implications not yet fully absorbed) 2. **COGS and infrastructure scaling ahead of revenue leverage** (margin compression signal) 3. **OpEx investment outpacing budget** (investment vs. overrun classification is critical and unresolved with available data) --- ## 3. NARRATIVE COMMENTARY ### Section A: Revenue & Top Line Q2 revenue of $4.2M exceeded budget by $400K, or 10.5%, reflecting what the data suggests is meaningful commercial momentum following the Q1 product launch. The enterprise pipeline acceleration cited in the company's operating context appears to be translating into closed revenue, which is a strategically significant development for a Series B business seeking to demonstrate repeatable go-to-market execution. However, the board should note that without an ARR waterfall, net revenue retention figures, or new logo count, it is not possible to confirm the quality or durability of this outperformance. Key questions for management: What portion of the $400K upside is new ARR vs. expansion vs. professional services? Were any deals pulled forward from Q3, and if so, what is the pipeline coverage for the back half? Is the enterprise ACV trending in line with the business case underpinning the Series B? The revenue beat is genuinely positive. The Board's task is to distinguish whether it represents a step-change in commercial velocity or a favorable quarter with timing tailwinds. --- ### Section B: Gross Margin & COGS Gross profit of $2.30M exceeded budget in absolute terms (+$200K), but gross margin contracted by approximately 50 basis points relative to budget (54.8% vs. 55.3%). In a SaaS context, this is a directional concern rather than an alarm — but it represents a reversal of the leverage trajectory a Series B company would typically be expected to demonstrate. COGS overran budget by $200K (11.8%), growing slightly faster than revenue (10.5%). The most plausible explanation is that enterprise customers — who drove the revenue upside — carry higher unit-level delivery costs, whether through dedicated infrastructure, onboarding resources, or premium support commitments. If this is the case, the gross margin impact is partially structural and will persist as long as enterprise mix increases. Management should be prepared to articulate the gross margin roadmap: At what scale does the enterprise motion become accretive to blended margin? Are there infrastructure efficiency initiatives in flight? The board should not be satisfied with a 50 bps miss without a credible path back to margin expansion. --- ### Section C: Operating Expenses OpEx of $2.80M exceeded budget by $300K, or 12.0% — the largest percentage overrun in the P&L and the primary driver of EBITDA underperformance. At 120 employees and a Series B stage, the company is almost certainly deploying capital into headcount and go-to-market capacity. The question is whether this overrun was planned, sanctioned, and value-generating, or whether it reflects execution friction. Without a department-level breakout, the board cannot distinguish between: - **Investment spend:** Accelerated hiring into Sales/Marketing ahead of an enterprise sales motion that was proving out faster than modeled — a positive signal that merits increasing the budget, not cutting costs. - **Run-rate overruns:** Spending in excess of plan without corresponding business case — a governance and forecasting concern. The board should request a functional breakout of the $300K variance before the end of this meeting. The appropriate response to these two scenarios is diametrically opposite. --- ### Section D: EBITDA / Operating Income EBITDA of –$500K represented a $100K miss against the –$400K budget, a 25% unfavorable variance at the bottom line. The drop-through math is instructive: the company generated $400K of revenue upside but delivered $100K of incremental EBITDA loss — meaning $500K of cost growth outpaced the revenue beat entirely. This negative operating leverage — where a 10.5% revenue outperformance produces a worse EBITDA outcome — is the central strategic tension in Q2 results. It is not unusual for a growth-stage SaaS company investing aggressively, but it requires a clear management narrative: Are we intentionally trading EBITDA for growth, and does the pipeline and ARR data validate that trade? The fixed/variable cost structure will become increasingly important to monitor. If a meaningful portion of OpEx overrun is headcount-driven (largely fixed in the near term), EBITDA improvement in H2 will depend heavily on revenue acceleration rather than cost normalization. --- ## 4. FORWARD-LOOKING BRIDGE Based on Q2 results, the implied full-year revenue run-rate is approximately **$16.8M** (Q2 actual of $4.2M annualized), compared to a full-year budget that, assuming an even $3.8M quarterly budget, would imply approximately **$15.2M** — a favorable variance of roughly **+10.5%**, assuming current trends continue. However, the implied full-year EBITDA picture is more cautious. At the Q2 run-rate of –$500K per quarter, annualized EBITDA burn would be approximately **–$2.0M**, against a budgeted –$1.6M — an unfavorable variance of approximately **–$400K**, or 25%. **Variances expected to persist:** - Revenue outperformance is likely to continue *if* enterprise pipeline conversion holds, though the board should monitor Q3 pipeline coverage closely for deal timing risk. - COGS margin pressure is likely to persist or modestly worsen as enterprise mix grows, absent deliberate infrastructure efficiency actions. - OpEx overage trajectory depends entirely on whether the $300K Q2 overrun is investment-driven (likely to continue) or one-time (likely to normalize). This is unresolved without further data. **Known factors affecting H2 comparisons:** - Continued enterprise pipeline build following product launch may sustain revenue upside. - Headcount investments made in Q1–Q2 will generate full-period cost in H2, potentially widening the OpEx variance before any leverage materializes. - No product launch events, restructuring charges, or other one-time items were indicated in the context provided. > *Based on current Q2 trends and assuming continuation of enterprise pipeline momentum, the implied full-year revenue is approximately $16.8M vs. budget of ~$15.2M — a favorable variance of +10.5% — while full-year EBITDA is tracking toward approximately –$2.0M vs. budget of ~–$1.6M, an unfavorable variance of approximately 25%. These estimates are directional and should be reconciled against management's internal forecast before being relied upon.* --- ## 5. EXECUTIVE HEADLINES > *For CFO to read aloud — Q2 Board Opening* - **Revenue exceeded budget by $400K (+10.5%), with enterprise pipeline momentum from the Q1 product launch as the primary driver.** - **Gross profit grew in absolute terms, but margin compressed 50 basis points — COGS is scaling slightly faster than revenue.** - **EBITDA missed budget by $100K despite the revenue beat, as $500K in combined cost overruns fully offset top-line outperformance.** - **OpEx ran $300K over budget; the Board needs a functional breakdown to determine whether this reflects intentional investment or execution overrun.** - **If enterprise conversion rates hold, full-year revenue could track approximately 10% above budget — but EBITDA improvement will require cost discipline in H2.** --- ## 6. RISK FLAGS ### 🔴 Flag 1: Negative Operating Leverage at Current Growth Rate **Signal:** Revenue grew 10.5% above budget; EBITDA worsened by 25%. Cost growth is outpacing revenue growth across both COGS and OpEx simultaneously. **Risk:** If this pattern persists, the company will consume cash faster than modeled, potentially compressing the Series B runway and affecting the timing of the next financing. **Recommended Action:** CFO to present a detailed Q3 cost forecast with scenario analysis against three revenue outcomes. Board should establish an EBITDA floor or cash runway covenant for internal governance. --- ### 🟡 Flag 2: Gross Margin Compression — Early Stage but Directionally Concerning **Signal:** COGS overran budget by 11.8% on 10.5% revenue growth. Gross margin slipped 50 bps vs. budget. **Risk:** In SaaS, gross margin is a structural indicator of unit economics quality. Sustained compression — even at modest levels — will affect future valuation multiples and investor narrative at Series C. **Recommended Action:** Management to present a gross margin bridge by Q3 board meeting, distinguishing enterprise mix effect from infrastructure inefficiency. Assign ownership of a gross margin improvement initiative. --- ### 🟡 Flag 3: Revenue Quality Unconfirmed — Timing Risk in Pipeline **Signal:** Revenue beat is material (+$400K) but the data does not distinguish between new ARR, expansion, pull-forward, or professional services. **Risk:** If a portion of Q2 upside is timing-driven (deals pulled from Q3), H2 revenue could disappoint against a now-elevated implied run-rate, creating a credibility issue with investors ahead of Series C. **Recommended Action:** ARR waterfall and pipeline coverage report to be included as a standing board package item. Specifically flag Q3 pipeline coverage ratio vs. implied Q3 budget. --- ### 🟠 Flag 4: OpEx Classification Gap — Investment vs. Overrun Unresolved **Signal:** $300K OpEx variance with no functional detail provided. **Risk:** The board cannot currently distinguish between value-creating investment spend and uncontrolled cost growth. This is a governance gap at a stage where capital discipline directly affects runway. **Recommended Action:** Immediate request for department-level P&L with headcount reconciliation. CFO to provide variance-by-category at this meeting or within five business days. --- ### 🟢 Flag 5: Data Completeness — Prior Year Figures Absent **Signal:** No prior year actuals were provided, limiting the analysis to budget variance only. **Risk:** Without YoY context, it is not possible to assess whether current performance represents an acceleration or deceleration of underlying business trends. **Recommended Action:** Ensure prior year actuals are included in all future board packages. A two-year trend view is standard for growth-stage companies approaching a Series C narrative. --- *This analysis is based solely on the financial data provided and does not constitute an audit opinion or investment recommendation. Forward-looking statements are directional estimates based on available data and should be reconciled against management's internal forecasts and Board-approved financial plan before being relied upon for decision-making.*