SaaS Unit Economics Case Studies: Five Real Businesses, Their Numbers, and What Worked

Why Real Numbers Matter More Than Benchmarks

Benchmarks are useful until they're not. When investors say "Series A SaaS should have 60-70% gross margins" or "CAC payback should be 12-18 months," they're describing the median. Successful outliers look completely different. This is why reading five real case studies matters more than memorising benchmark ranges. You'll see that some companies optimised for churn early (trading CAC for retention), others for expansion revenue (accepting low gross margins to gain land-and-expand), and others for market positioning (raising prices aggressively and accepting lower growth). Each path led to success, but they looked wildly different in year two.

Case Study 1: SMB HR SaaS From Seed to Series A

Background: HRIS software for 10-100 person companies. Founded 2021, raised £500k Seed in 2022, £3.5M Series A in 2024.

Year One (Post-Seed): The company operated at breakneck acquisition speed. Monthly churn was 4.2%, CAC was £2,400, ARPU was £250/month. LTV was £7,143 (ARPU × 12 × (1 ÷ 0.042)). LTV:CAC was 2.97:1, below the 3:1 comfort threshold. But the company wasn't optimising LTV; they were optimising for proof of product-market fit through usage breadth. They signed customers in real estate, healthcare, manufacturing, and retail. The product wasn't sticky to any one vertical. This was intentional. They wanted to prove broad appeal before narrowing.

Year Two (Series A Raise): The company pivoted. Instead of chasing breadth, they focused on verticalisation. They picked healthcare (easiest compliance story), built vertical-specific features (compliance checklists, provider credentialing workflows), and repositioned marketing. Monthly churn fell from 4.2% to 2.4%. CAC stayed at £2,400 (they'd shifted to partner channels and earned media in healthcare). ARPU increased to £350/month as they upsold vertical features and expanded seat count. New LTV: £17,500. New LTV:CAC: 7.3:1.

The difference: investing heavily in churn reduction (product improvements, vertical-specific onboarding, dedicated customer success for top 20 customers) before trying to scale acquisition. By the time they raised Series A, they had clear evidence that a health-focused message with vertical features reduced churn 40% and improved expansion 30%. That narrative unlocked Series A at 7x ARR valuation.

Post-Series A: The company is now at £4.2M ARR with 1.8% monthly churn, £3,100 CAC, £420 ARPU. They're expanding into adjacent verticals (financial services, legal) using the healthcare playbook. The key lesson: churn improvement is more valuable than CAC reduction at early stage.

Case Study 2: Mid-Market Security SaaS at Series A

Background: Cloud access control platform for enterprise IT. Founded 2020, £1.2M Seed, £6.5M Series A in 2023. Currently £12M ARR.

The unusual metric here is NRR. At Series A close, this company had 117% net revenue retention. That's expansion revenue exceeding churn and contraction. Most SaaS companies are fighting to hit 110% NRR; this company was three years old and already there.

Why? The product had two expansion paths that worked simultaneously. First, customers expanded seat count as they added headcount (automatic expansion). Second, customers bought adjacent modules (identity governance, conditional access) as they got comfortable. The company optimised for adoption of module 1, then module 2, sequentially. By year three, their top 40% of customers were using 3+ modules. These customers had LTV of £180k (£15k ARPU × 12 years, accounting for 0.8% monthly churn). Their single-module customers had LTV of £60k. The mix shift toward multi-module customers directly drove NRR expansion.

The unit economics were: CAC £8,500, ARPU £850 year one, growing to £1,200 by year three on existing customers. Payback was 10 months initially. But because they won large customers with long buying cycles, payback was actually fine; the pain was in sales cycle length (6 months) not payback period.

What worked: obsessive focus on module adoption metrics. They tracked which customers used which modules, when they adopted (day 1, day 30, day 90), and who never activated. They built playbooks to drive activation before upselling. This product-driven expansion approach meant expansion revenue grew 40% year-over-year even as new customer acquisition stayed flat. That's how they hit 117% NRR.

The lesson: expansion revenue compounds faster than acquisition at mid-market. A company with 100% NRR growing ARR 10% annually from new customers can grow 15-20% annually if they shift focus to expansion. This company chose expansion focus early and it paid off.

Case Study 3: Developer Tools PLG Company

Background: API infrastructure tool with product-led growth model. Founded 2019, reached £2M ARR by 2023 with minimal paid acquisition.

PLG companies have inverted unit economics: CAC is near zero (customers sign up, try the product, and buy without sales involvement), but LTV is challenged because churn is high (3-5% monthly is common for low-price SMB products). This company had a different problem: they had found a massive SMB market (developers building internal tools), but their ARPU was stuck at £180/year. At 3% monthly churn, that's LTV of £6,000. The company was profitable on a unit basis, but margins were thin and growth was capped by market size.

They faced a choice: stay SMB focused and grow 50-80% annually organically, or attempt to move upmarket to enterprise where ARPU could be 5-10x higher. They chose to move upmarket but keep PLG motion intact. That meant building enterprise features (SSO, advanced analytics, API quotas, audit logs) without hiring enterprise sales.

The transition took 18 months. They launched an enterprise tier at £12k annually (vs £180 SMB). Enterprise churn was 0.5% monthly, LTV per enterprise customer was £288k. Growth initially dropped to 40% as they invested in enterprise features instead of SMB breadth. But by month 18, 20% of ARR came from enterprise customers, growing at 140% annually. The blended growth rate was back to 75-80%.

What worked: staying technical and not hiring enterprise sales. The founder insisted that enterprise customers could buy without sales calls, and they proved it. Most moved from SMB to Enterprise tier organically. The key was building features that made the value difference clear (audit logs for compliance, better API quotas for scale). They're now at £8M ARR, 35% enterprise mix, and raising Series B at strong unit economics.

The lesson: PLG companies can move upmarket without losing their magic if they focus on product justification for premium tiers, not sales justification. ARPA expansion drives growth more than churn reduction.

Case Study 4: Professional Services SaaS With High COGS

Background: Consulting engagement management platform (CRM for consultancies). Founded 2018, £500k ARR at Series A with 51% gross margin (unusually low for SaaS).

The company's business had embedded services COGS: implementation, training, ongoing support. Every customer required 40 hours of implementation and 4 hours/month of support. At £6,000 ARPU and 70% of revenue going to implementation and support labour, gross margin was 30%. Including contractor costs for customers larger than £10k ARPU, gross margin fell to 51%. Investors were concerned because 51% margins don't support expensive sales teams or substantial R&D.

The company built a 18-month productisation roadmap. They broke their implementation process into replicable templates, built certification programmes for partners instead of doing implementation in-house, and created tiered onboarding (lite for SMB, standard for mid-market, custom for enterprise). They also built self-service knowledge base and built in-product workflows to reduce ongoing support needs.

Results after 18 months: implementation costs fell from 40 hours per customer to 12 hours per SMB customer, 20 hours for mid-market. Support moved from 4 hours/month average to 2 hours/month. Gross margin improved from 51% to 71%. They also expanded ARPU from £6k to £9.5k as customers landed deeper (selling to more departments). New LTV at improved metrics: £19,800 (£9,500 × 24 months, accounting for 0.6% monthly churn) vs previous £14,400.

What worked: obsessing on labour leverage. Every feature decision was evaluated on whether it reduced customer success labour per £1 ARR. By year four, this company had the margins of a pure-software SaaS (71%) but the stickiness of a services business (0.6% churn). They're now raising Series B at 7x ARR because investors can see a path to 75%+ margins and sustainable growth rates.

Case Study 5: Enterprise Vertical SaaS in Healthcare

Background: Hospital inventory management SaaS. Founded 2015, raised Series B at £2M ARR in 2022, now £18M ARR.

This company has unusual metrics because they picked a defensible vertical with long buying cycles. CAC is £28k (24-month sales cycle through hospital procurement). ARPU is £40k (hospitals have 5-10 year contract lives). Monthly churn is 0.4% (hospitals don't switch inventory systems). Payback period is 25 months, longer than most venture-backed SaaS, but acceptable given 10+ year customer lifetime.

At Series B (£2M ARR), investors knew payback was 25+ months. But they also knew that repeat revenue from existing customers would drive growth without corresponding sales investment. LTV: £1.2M+ (£40k × 12 × (1 ÷ 0.004)), making LTV:CAC over 40:1. The math works because customer lifetime is so long that even slow payback is acceptable.

The series B was raised at 11x ARR valuation (unusually high for a £2M ARR company, but explained by LTV:CAC ratio and predictable revenue). The company is now at £18M ARR, growing 40% annually from expansion revenue (upselling additional features like supply chain analytics) rather than new customer acquisition (which they've slowed because it's capital-intensive).

What worked: choosing a market where you can tolerate 25+ month payback because customer lifetime is extraordinarily long. Most venture-backed SaaS cannot do this; hospitals can because their procurement cycles and contract terms are long. The lesson: unit economics are relative to customer lifetime. A 3-year LTV customer needs 12-month payback. A 10-year LTV customer can tolerate 25-month payback.

The Common Pattern Across All Five

Five companies, five different paths, but one common pattern: each company identified a single unit economics lever that was most broken, fixed it ruthlessly, then rotated to the next lever. The HR SaaS company fixed churn. The security company fixed expansion revenue. The PLG company fixed ARPU. The services SaaS fixed gross margin. The healthcare company leveraged customer lifetime.

They did not try to optimise everything simultaneously. They did not chase benchmarks. They diagnosed which lever was most constraining their fundraising narrative or growth runway, built a roadmap to fix it, and executed. By the time they raised the next round, that lever had moved from a concern to a strength, and they could move focus to the next constraint.

This is how real unit economics improvement works. It's sequential, not parallel. It's diagnosis before action. It's measurement-driven, not intuition-driven. These five companies all followed that pattern regardless of business model, market size, or customer profile.

Related Reading

For foundational unit economics concepts, read the SaaS Unit Economics Bible. For expansion revenue mechanics, explore SaaS LTV and Churn Rate Dynamics. For gross margin strategies, see SaaS Gross Margin Expansion.

Key Takeaways

• Real unit economics are messier than benchmarks; successful companies optimise one lever at a time
• Churn improvement (from 4.2% to 1.8% monthly) can improve LTV:CAC more than CAC reduction alone
• Expansion revenue matters: 117% NRR is a stronger signal than low churn alone
• PLG companies can move upmarket (ARPA from £180 to £12k) by building product-driven premium tiers
• Gross margin improvement (51% to 71%) unlocks growth by freeing capital for sales and R&D
• Customer lifetime determines acceptable payback; 10-year customers can tolerate 25-month payback
• The pattern is diagnosis, single-lever focus, execution, then rotation to next constraint