Your Services Revenue Is Not SaaS Growth. It Is a Margin Trap.
Professional services can unlock early enterprise sales, but they are not software growth. Benchmarkit: median subscription margin is 81%, professional services margin is 30%, and services above 15–20% of revenue can pull total margin below 77%. The metrics founders need before calling every dollar SaaS revenue.
Your Services Revenue Is Not SaaS Growth. It Is a Margin Trap.
Many founders call every pound or dollar of revenue “SaaS revenue.” It makes the ARR chart look bigger. It helps the growth story. It may even win the deal.
But if the revenue requires people to configure, build, train, customise, migrate, or repeatedly rescue the customer, it is not software growth in the same way. It is services revenue. And when founders mix the two, they can build a company that looks like SaaS on a slide but behaves like a consultancy in the bank account.
This is not an argument against professional services. Services can speed up onboarding, reveal customer needs, fund early learning, and unlock enterprise sales. The trap starts when services become the hidden answer to a product that is hard to deploy, hard to adopt, or too customised to repeat.
The Margin Gap Is Not Small
Benchmarkit’s 2025 B2B SaaS Performance Metrics show a sharp split between revenue types. The median total-revenue gross margin was 77%. Subscription revenue margin was 81%. Professional-services margin was only 30% [1].
That is not a bookkeeping detail. It changes how much cash is left to fund product development, sales, support, and profit. A business that adds more low-margin services can report rising revenue while becoming less able to invest in the software engine it claims to be building.
Benchmarkit reports that professional services represent roughly 15% of revenue at the median. It warns that when services exceed 15–20% of total revenue, and/or service gross margin falls below 30%, total gross margin is likely to drop below the 77% median [1].
If every new customer requires a new project, you have not solved the product problem. You have moved it into delivery.
Why Revenue Mix Changes the Company You Are Building
The 2026 Aleph × Benchmarkit report, using full-year 2025 data from 342 SaaS and AI-native companies, found a median 80% software gross margin but only 76% total-revenue gross margin [2]. That four-point gap is the drag from services and other lower-margin revenue.
The stronger end of the market is even clearer. Top-quartile software businesses reached 86%+ gross margin. Bottom-quartile companies were at 50% [2]. That is a 36-point spread in how much of each revenue dollar remains after direct delivery costs.
Scale matters, but only if the company is actually productising delivery. Software gross margin rises from 72% at sub-$5 million ARR to 86% at $50–100 million ARR — a 14-point increase [2]. If a founder keeps adding custom work as revenue rises, that operating leverage never arrives.
The Comparison Every Founder Should Run
| Revenue type | Median gross margin | What scales | Core risk |
|---|---|---|---|
| Subscription software | 80–81% | The product, infrastructure, and customer base | Hosting, support, and AI compute costs |
| Professional services | 30% | Headcount and billable hours | Custom work dilutes total margin |
| Usage-only SaaS | 62% | Customer usage and retention | Infrastructure and compute cost rises with usage |
| Blended SaaS revenue | 76–77% | Only if service work becomes repeatable | The mix hides a delivery problem |
Sources: Benchmarkit 2025 B2B SaaS Performance Metrics and Aleph × Benchmarkit 2026 SaaS & AI Performance Benchmarks [1] [2].
The Consultancy With a Login Screen
There is a simple test. Remove the implementation team from the plan. Does the customer still get value in a predictable time frame? Can a new customer use the same onboarding, configuration, and playbook as the last ten customers? Can your gross margin improve as you add customers?
If the answer is no, the business may be valuable. It may have happy customers. It may have a healthy services practice. But it should not be managed or valued as a pure software company. Pretending otherwise creates bad hiring plans, bad pricing, and bad forecasts.
The SaaS CFO explains why this matters in the P&L. Subscription revenue, services revenue, and their direct costs must be separated. A blended gross-margin number can hide a strong 90% recurring margin behind weak or even negative services economics [3].
What Strong Founders Do Instead
Zee’s view is blunt: founders should treat every repeated service task as product research with an expiry date. If customers repeatedly pay for the same implementation, integration, report, or workflow, make a decision. Productise it, price it properly as a premium service, or stop offering it.
Strong founders track three numbers separately each month: subscription gross margin, services gross margin, and total gross margin. They do not let services disappear inside ARR. They measure time-to-value, deployment hours per customer, and the share of onboarding that can happen without a human.
They also avoid the false choice between “no services” and “unlimited services.” The right model is often narrow, high-value, time-boxed services that move the customer toward self-sufficiency. The wrong model is an open-ended promise that makes every new logo a new delivery business.
Revenue is not automatically good revenue. In SaaS, the best revenue makes the next customer easier to serve. The worst revenue makes the next customer require another project manager.
Frequently Asked Questions
Is professional-services revenue bad for a SaaS company?
No. It can accelerate onboarding, support enterprise deployments, and reveal what should be productised. It becomes a risk when it is open-ended, low-margin, or required for every customer to achieve value.
What is a good SaaS gross margin?
The Aleph × Benchmarkit 2026 report, based on full-year 2025 data, reports an 80% median software gross margin and 76% median blended total-revenue gross margin. Top-quartile software companies clear 86% [2].
What professional-services percentage is too high for SaaS?
Benchmarkit reports a median near 15% of total revenue and warns that services exceeding 15–20% of revenue and/or services margin below 30% is likely to pull total margin below the 77% median [1]. The right threshold still depends on business model and customer value.
Why should services revenue and subscription revenue be reported separately?
They have different delivery costs and margins. Separating them prevents high-margin recurring software economics from being hidden by lower-margin custom work, or vice versa [3].
How can a founder reduce services dependence?
Measure which service tasks repeat, turn repeatable work into product features or templates, set clear implementation scopes, charge for genuinely bespoke work, and track deployment hours and time-to-value by customer segment.
Does usage-based SaaS have lower gross margin?
Often, yes. The Aleph × Benchmarkit benchmark reported a 62% median for usage-only models because infrastructure and compute costs rise with usage. That model can still be attractive if retention and expansion justify the margin trade-off [2].