The boardroom problem
The commercial update is encouraging: bookings are ahead, the pipeline is larger, and the team wants to hire. Then finance presents a weaker gross margin and a tighter cash forecast. Both accounts may be accurate. They describe different parts of the business, often over different periods.
The board's task is to reconcile those accounts before approving the next commitment. A contract signature does not establish delivery profitability. Recognized revenue does not establish collection. A larger customer can bring more support, implementation work, customization, or consumption costs than the sales model assumed. Growth can expose an operating problem faster than it solves one.
Orca's operating lens connects four questions: What is the quality of the revenue? How does profit convert into cash? What return will the next investment earn? How durable are those economics? The answer should lead to a decision, an owner, and a date.
Start with one set of definitions
Ask the CFO and CRO or CGO to reconcile the same customer population and reporting period. Separate bookings, recurring revenue, recognized revenue, billed revenue, and collected cash. Document whether contract values include implementation fees, variable usage, discounts, or options that have not been exercised. A pipeline total should not be compared with a recognized-revenue target as though they were interchangeable.
Then agree which costs sit in gross profit and keep the classification consistent. If support labor moves below the line, the reported margin can improve without the business becoming more efficient. Finance should reconcile the operating view to the ledger, identify allocation assumptions, and show the effect of any classification changes. The commercial team should validate contract terms and the delivery promises behind the forecast.
Separate mix from deterioration
Consider an illustrative company with $10 million of revenue and a 70% gross margin: it generates $7 million of gross profit. Revenue then rises to $12 million while gross margin falls to 55%. Gross profit is now $6.6 million. The business has added $2 million of revenue and lost $400,000 of gross profit before operating expenses.
That result alone does not tell you what to cut. A shift toward lower-margin implementation work could explain the decline even if subscription delivery remains healthy. Alternatively, the same customers may now require more delivery hours, more compute, or deeper discounts. Build a bridge that separates price, customer and service mix, volume, unit cost, and accounting changes. Assign each variance once so the bridge does not double count it.
Use customer cohorts and service lines to find the source. Review newly sold work separately from the existing book. Identify whether the problem begins at the quote, the handoff, delivery, renewal, or collection. Show both gross-profit dollars and margin percentage: a percentage improvement can coexist with a shrinking profit pool.
For software, connect usage to the contract
Review hosting, model inference, support, onboarding, and third-party costs at the level available in your systems. Compare the revenue earned from a customer or product tier with its attributable delivery costs. Make shared-cost allocations visible rather than presenting estimates as measured precision.
If heavier usage raises cost without raising revenue, review included allowances, overage pricing, packaging, and renewal terms. Engineering owns the technical efficiency work; finance validates the unit economics; the commercial leader owns the customer and pricing response. An AI feature should be assessed on its delivery economics and customer value before its adoption rate becomes the basis for a hiring plan.
For professional services, test the sold assumptions
Compare quoted hours, actual hours, realized fees, write-offs, and the fully burdened cost of delivery. A highly utilized team can still lose margin when senior staff perform work priced for junior capacity, fixed-fee projects overrun, or unapproved scope becomes habitual. Utilization alone cannot establish engagement profitability.
Review the weakest engagements with the delivery and commercial leaders together. Agree whether to re-scope, reprice at renewal, change staffing, improve the workflow, or exit when contract terms permit. Protect valuable client relationships while making the economics explicit. Across-the-board cuts can remove the capacity needed to deliver profitable work and create a second problem.
Turn disagreement into a 30-day operating plan
In the first week, finance reconciles the revenue definitions and margin bridge; commercial and delivery leaders confirm the underlying terms and activity. In week two, those leaders select a small number of pricing, delivery, or collection interventions and estimate their gross-profit and cash effects separately. Cash timing matters: a repricing proposal does not fund payroll until it is agreed, billed, and collected.
During weeks three and four, track the interventions against a baseline. Record the owner, expected effect, evidence required, decision date, and any customer or retention risk. Present a base case, a credible downside, and the assumptions that would cause management to stop or expand the intervention. The CEO resolves cross-functional tradeoffs; the board approves changes within its reserved authority.
Keep the growth ambition, but make its funding conditions explicit. The strongest board discussion ends with a shared account of what is happening, what management will change, and what evidence will justify the next dollar of investment.
The next board pack
| Owner | Action | Timing and evidence |
|---|---|---|
| Finance | Reconcile bookings to recognized revenue and cash; build the margin bridge. | Within 7 days: Ledger tie-out and one agreed definition sheet |
| CRO / CGO | Review discounting, packaging, customer mix and promises in new deals. | Within 14 days: Deal-level economics and approved exceptions |
| Delivery / technology | Validate delivery hours or usage costs; test the largest leakage point. | Within 21 days: Measured unit cost and customer impact |
| CEO / board | Choose what to fund, change or stop using profit and cash scenarios. | By day 30: Decision log, accountable owner and review date |
Curated reading
These readings were reviewed for this issue. The applications are Orca’s independent interpretation; the publishers do not endorse Orca.
How to Correctly Calculate your SaaS Gross Profit Margin
The SaaS CFO / Ben MurrayRead for revenue-stream margins and consistent cost classification. Orca application: isolate the source of erosion before changing the operating plan.
Cloud Infrastructure Is Now a Finance Problem
The SaaS CFO / Ben MurrayRead for the link between technical consumption and financial control. Orca application: give finance and engineering a shared cost-to-serve view.
The Burn Multiple
Bottom Up / David SacksRead for capital efficiency: net burn divided by net new ARR. Orca application: assess the funding required for growth. This venture SaaS measure is not a universal margin benchmark.
Levels of PMF
First RoundRead for the relationship between demand, customer satisfaction and efficiency. Orca application: match spending commitments to evidence about the company's stage. The Paths to PMF collection was also reviewed.
Vertical Integrators: Part IV
Not Boring / Packy McCormickRead for a broader view of unit economics and execution risk. Orca application: evaluate the whole delivery system before assuming scale will repair margins. Its industry examples are not SaaS benchmarks.
Also reviewed: First Round’s Paths to PMF collection. Source review: October 26, 2026.
Put the thinking to work
Orca connects financial leadership, operating discipline, and accountable execution. Book a conversation about the decisions ahead.
Get the PDF — name and email required ↗All examples are hypothetical, not forecasts or actual client results. General information, not individualized legal, tax, accounting or investment advice. © 2026 Orca Operating Partners. All rights reserved in Orca-owned materials. Third-party rights remain with their owners. Permitted use and licensing. Permissions: support@orcaoperatingpartners.com.