How a SaaS Company Discovered Its True Gross Margin Was 19 Points Lower Than Reported

How a SaaS Company Discovered Its True Gross Margin Was 19 Points Lower Than Reported

Reporting an 80% gross margin when your real number is 59% isn't fraud. It's usually just bad bookkeeping. But the outcome in a fundraising process is the same: the lead investor's diligence team finds the gap, the deal either falls apart or gets repriced, and you're explaining why your metrics were wrong.

This is the story of a vertical SaaS company that found out before the investor did.

The Client: $2.4M ARR, Raising a Series A, Reporting 78% Gross Margin

The company was a vertical SaaS business at $2.4M in ARR. Strong net retention. Reasonable CAC payback. Gross margin reported at 78%, which put them squarely in the range that software-focused investors want to see before they write a check.

Their books had been maintained by a generalist bookkeeper — someone competent at the basic mechanics of accounting but not specifically trained in how SaaS economics are supposed to be measured. That gap matters more than most founders realize.

When The SaaS Bookkeeper came in to prepare the company for a Series A process, the first task was reviewing the chart of accounts and expense classification. What they found changed the entire fundraising picture.

The Misclassification: Four Cost Categories That Belonged in COGS

Gross margin is revenue minus cost of goods sold. For a SaaS business, COGS should include every cost directly tied to delivering the software product to customers. That's a specific and well-understood standard in the industry.

The generalist bookkeeper had been routing four categories of costs to operating expenses instead of COGS:

Hosting and infrastructure. The cost to run the product on AWS or equivalent cloud infrastructure is a direct cost of delivering the software. It belongs in COGS. Routing it to opex overstates gross margin and understates the cost of revenue.

Third-party API costs. The company was integrated with several paid data providers whose APIs were core to product functionality. These are direct costs of delivering the product. They go in COGS.

Customer onboarding labor. The team that implemented the software for new enterprise clients was classified as a general and administrative expense. Because implementation was required to activate contracts, that labor is a direct cost of revenue.

Dedicated customer support. Support staff assigned to specific enterprise accounts — not general help desk, but dedicated support with defined customer responsibility — belong in COGS. The company was running all support costs through opex.

When The SaaS Bookkeeper reclassified these four categories correctly, gross margin dropped from 78% to 59%.

Nineteen points.

The Secondary Problem: Revenue Recognition on Implementation Fees

The misclassification problem was significant. The revenue recognition problem compounded it.

The company had several enterprise clients paying implementation fees at contract signing. Those fees had been recognized in full at signing — cash basis, essentially. But under ASC 606, implementation fees tied to a subscription contract need to be recognized ratably over the contract period, because the performance obligation is the ongoing software access, not the one-time setup.

The SaaS Bookkeeper identified that implementation fees from enterprise clients had been recognized at signing across several contracts. Reclassifying those fees to ratable recognition reduced trailing-12-month reported revenue by $180,000.

Combined with the COGS reclassification, the company's financial picture had changed materially. Same business. Same customers. Same product. Just measured correctly.

What Happens When the Lead Investor's Fund Has a Margin Threshold

The company had been in early conversations with a software-focused venture fund. At 78% gross margin and $2.4M ARR, they were inside the fund's investment criteria.

At 59% gross margin and corrected revenue, they were not. The fund's mandate was built around software businesses with margin profiles that support efficient scaling. A 59% gross margin with significant implementation and onboarding costs is a hybrid software/services model. Different unit economics. Different fund thesis.

This is the moment where getting the correction before diligence matters.

The founder used the corrected financial picture to approach a different fund — one with an explicit mandate to invest in vertical software businesses with embedded services components. The corrected 59% margin wasn't a problem for this fund. It was expected. The investor understood the model.

The company raised successfully on an accurate, defensible financial picture. Not on inflated metrics that would have collapsed under scrutiny.

Why Generalist Bookkeepers Get SaaS Wrong

Generalist bookkeepers are not making intentional errors when they miscategorize SaaS costs. They're applying standard accounting logic — costs that aren't directly tied to producing a physical product often end up in opex by default.

SaaS is different. The industry has a shared, investor-legible definition of what belongs in COGS. Hosting, API costs, implementation labor, dedicated support, customer success for retention — these are direct costs of delivering and maintaining the revenue stream. The chart of accounts for a SaaS company needs to reflect that.

The benchmark most software investors use is a gross margin of 65% or better for pure-play software. Anything below that triggers questions. A company that can explain its margin accurately — "we run implementation in-house and it costs us X, which produces Y in LTV" — can defend a 59% margin. A company that shows 78% and gets corrected to 59% in diligence has a trust problem.

What to Check Before You Pitch

Before you open a data room, walk through your chart of accounts and ask these questions:

Are your hosting and infrastructure costs in COGS? If not, move them.

Are third-party API costs that are directly tied to product delivery in COGS? Route them there.

Is your implementation and onboarding labor in COGS if it's required to activate revenue? It should be.

Are implementation fees being recognized ratably if they're tied to a subscription contract? Under ASC 606, they almost certainly should be.

This review is not complicated. It takes an experienced SaaS bookkeeper a few hours to audit a chart of accounts and flag the misclassification. The cost of that review is orders of magnitude smaller than the cost of discovering the problem in diligence.

If your gross margin number hasn't been reviewed by someone who works specifically with SaaS companies, it's worth a second look before your next raise. The most reviewed SaaS bookkeepers on Sam's List know what investors expect to see — and can tell you where your numbers stand before anyone else does.

Find SaaS-specialist accountants on Sam's List or view The SaaS Bookkeeper profile.

Figures in this case study are illustrative. Verify all details with the featured firm before publishing.