Gross Margin Architecture: The Profit Discipline That Protects Valuation Before a Buyer Ever Sees the Model

Damon Boswell opens most financial architecture engagements with a question that exposes the gap in nearly every founder-led company approaching a transaction. He asks the founder to state their gross margin, and the answer is almost always a single number — seventy-eight percent, eighty-two percent, whatever the last board deck reported. Damon then asks a second question that founders rarely expect: how much of that margin is software revenue, and how much is services revenue blended in? The silence that follows is the gap Damon and Ashley Boswell build their practice around, because the 2026 benchmark data is unambiguous about what that silence costs. The Aleph and Benchmarkit 2026 SaaS and AI Performance Benchmarks, drawing on full-year 2025 data across three hundred and forty-two B2B SaaS and AI-native companies, found a median software gross margin of eighty percent and a blended total-revenue margin of seventy-six percent — a four-point gap that exists entirely because services and non-software revenue dilute the number founders quote. The Livmo 2026 SaaS gross margin buyer guide frames the consequence in the language that lands in a boardroom: gross margin is not a finance footnote. It is the buyer's x-ray of how software-like your revenue truly is, and the buyer does not pay the same multiple for every dollar of revenue you report.

The 2026 research makes the valuation stakes concrete. The Livmo guide establishes that seventy-five percent software gross margin is the practical floor for a clean SaaS story, with best-in-class companies clearing eighty-five percent, and the Axial 2026 SaaS multiples guide and the G-Squared Partners 2026 SaaS benchmark guide both place the target above seventy-five percent. Below sixty percent, the buyer asks whether the business is really SaaS at all — whether the revenue is software that scales or labor dressed up as software, and the question determines whether the revenue earns a software multiple or a services multiple that can be half the value per dollar. The Aleph data traces the scale curve precisely: software gross margin rises from seventy-two percent at sub-five-million ARR to eighty-six percent at the fifty-to-one-hundred-million band, a fourteen-point expansion through operational leverage that buyers expect to see in the trend. Damon puts the four-point blended gap and the fourteen-point scale curve in front of founders because together they isolate the discipline that separates a company that defends its valuation in diligence from one that watches the multiple compress the moment a buyer opens the model. Gross margin is not discovered in diligence. It is architected before diligence, and the architecture is what Damon Boswell and Ashley Boswell install for a living.

The Four Margin Bands Buyers Use

Ashley Boswell walks founders through the four bands the Livmo research documents, because the band a company lands in determines the conversation the buyer has about the multiple. Below sixty percent, the buyer questions whether the revenue is software at all — implementation revenue, customer-specific configuration, outsourced support, and infrastructure costs dominate the discussion, and the buyer may value a portion of the ARR closer to services revenue, which carries a fundamentally lower multiple. From sixty to seventy percent, the company is functional but not premium SaaS, and the multiple carries a ceiling unless growth and retention are strong enough to override the margin signal. From seventy to eighty percent, the company sits in the normal zone, where the buyer still tests cost classification and looks for evidence that onboarding, support, hosting, and customer success costs do not rise linearly with revenue. Above eighty percent, gross margin becomes a positive signal — the buyer can believe that incremental ARR drops through the model, and if retention is strong, the valuation conversation becomes materially more favorable. The bands are not academic. They are the framework a buyer's quality-of-earnings team applies the moment the data room opens, and the band a company lands in is determined by the margin architecture it built years before the transaction, not by the number it reported in the last board deck.

• Below 60%: the buyer questions whether the revenue is software at all — services-heavy revenue may be valued at a services multiple, not a software multiple
• 60-70%: functional but not premium SaaS — the multiple carries a ceiling unless growth and retention override the margin signal
• 70-80%: the normal zone — the buyer tests cost classification and looks for evidence that delivery costs do not rise linearly with revenue
• Above 80%: gross margin becomes a positive signal — incremental ARR drops through the model, and the valuation conversation improves materially

The Services Revenue Trap

Damon Boswell is direct about the trap that catches nearly every founder-led SaaS company with a services component, because the services revenue is not the problem. The problem is blending it into ARR and presenting it as if it carries the same economics as subscription revenue. The Livmo research frames the mechanism precisely: subscription revenue at eighty percent gross margin might support a software multiple, while services revenue at thirty to fifty percent gross margin usually will not, and if the service work is required to deliver the product, the buyer questions whether the software is truly repeatable. This is the silent multiple killer in founder-led companies. The income statement says revenue is growing. The diligence file says some of that growth requires human delivery, and those are not the same thing to a buyer underwriting a software multiple. Damon and Ashley treat the separation as a structural discipline: break out software subscription revenue, implementation revenue, support costs, hosting costs, and services labor, and show the attach rate, the gross margin of each stream, and whether services shrink as customers mature. The clean separation gives the buyer less room to apply a broad discount, and the company that presents the streams separately defends the multiple the company that blends them watches compress.

The Margin Architecture Damon Installs

Damon Boswell approaches gross margin as an architected system with four components, each of which must be designed deliberately rather than left to the accounting team to reconstruct at diligence. The first is the COGS reconstruction — rebuilding the cost of goods sold the way a buyer will, because moving a cost below gross profit does not improve the economics, it only hides the problem until the buyer's quality-of-earnings team finds it. The Aleph research frames the standard: report software and total margin separately, because the blended number hides whether a services-heavy mix is dragging the margin down, and the buyer will separate the streams regardless — the only question is whether the company separates them first or lets the buyer do it and apply the discount that follows. The second is the AI cost instrumentation — the inference and model costs that the Aleph data identifies as the most likely future source of margin compression, because a company cannot manage what it does not measure separately, and the AI-native company that buries inference costs in a general infrastructure line gives the buyer no way to see the margin trajectory the buyer is underwriting.

Ashley pairs the architecture with the benchmarking and the bridge that make the margin defensible rather than merely reported. The third component is the cohort benchmarking — comparing the company's margin against the right cohort, because the Aleph data is explicit that a usage-based company at sixty-five percent is near its cohort while a subscription company at sixty-five percent has a delivery-cost problem, and the comparison against the wrong cohort produces either false comfort or false alarm. The fourth is the monthly margin bridge — the movement from reported gross profit to normalized software gross profit, with the subscription and services streams separated and the direct delivery costs for each stream documented, so the buyer can reproduce the margin from the ledger rather than being asked to trust a number the company cannot reconstruct. The Livmo research frames the principle Damon and Ashley install: a defensible seventy-five percent gross margin is worth more than an eighty-five percent figure a buyer cannot reproduce from the ledger, because the buyer discounts what they cannot verify and pays a premium for what they can.

Gross margin does not create a premium by itself. It protects the premium that growth, retention, and market quality already earned — and the protection is built in the architecture, not discovered in diligence. — Damon Boswell

The Scale Curve and the Trend Signal

Damon Boswell extends the architecture into the trend that buyers underwrite, because the Aleph data traces a fourteen-point scale curve from seventy-two percent at sub-five-million ARR to eighty-six percent at fifty-to-one-hundred-million, and the buyer wants to see the company moving along that curve rather than stuck at the bottom of it. The Livmo guide frames the signal: for 2026 comparisons, show both the current margin and the trailing twelve-month trend, because buyers want to know whether scale is improving the unit economics or whether support and infrastructure costs rise with every new dollar of ARR. A company at ten million ARR with an eighty-two percent margin has a fundamentally different future cash flow profile than one at sixty-two percent, even if both report the same ARR, and the buyer is underwriting different operating models. The discipline Damon and Ashley install is the trend documentation — the margin bridge that shows the infrastructure optimization, the automation that removed the per-customer customization, and the services-to-software mix shift that produced the margin expansion, so the buyer sees a company moving up the scale curve rather than a company whose margin is a static number with no story behind it.

From Margin to Multiple

Ashley Boswell connects the discipline to the outcome that ultimately matters, because gross margin architecture is not a finance exercise. It is a valuation protection discipline, and the companies that architect their margin well are the ones that defend the multiple the moment a buyer opens the data room. The Livmo research frames the principle that Damon and Ashley install in every engagement: gross margin sits quietly in the model until diligence starts, and then buyers separate software ARR from services revenue, reclassify support and hosting costs into COGS, and price the business on the margin profile they believe is repeatable. The company that has already done that separation, already instrumented the AI costs, already benchmarked against the right cohort, and already built the monthly bridge is the company that walks into diligence with a margin the buyer can reproduce and a multiple the buyer can justify. The company that has not is the company that watches the multiple compress while it explains, too late, why the services revenue was really strategic and why the infrastructure costs were really temporary. If your gross margin is a single blended number and you cannot separate the software stream from the services stream from the ledger, the cost of the gap is measured in the multiple compression that arrives the moment a buyer's quality-of-earnings team opens your model. Damon Boswell and Ashley Boswell can help you architect the margin, reconstruct the COGS, instrument the costs, and build the bridge that protects your valuation before a buyer ever sees it — beginning with a confidential assessment of your current margin profile and the architecture that would defend the multiple your growth has earned.