← Back to articles

SaaS Benchmarks by Vertical: B2B, Vertical SaaS, AI-Native, and Developer Tools

The most common mistake founders make is comparing themselves to horizontal SaaS benchmarks when their business operates in a distinct vertical. A developer tool at 50% gross margin looks broken against horizontal SaaS (70%+) until you understand infrastructure, API, and compute costs baked into dev tools. A vertical SaaS at 1.2x annual growth looks slow until you understand competitive moats and switching costs in niche markets. This guide maps benchmarks across six categories, revealing what investors actually expect in each vertical.

B2B Horizontal SaaS: The Competitive Gauntlet

Horizontal SaaS (CRM, project management, accounting software serving all industries) is the most competitive category. Switching costs are low (limited integrations, data portability), buyer behavior is similar across segments, and TAM is enormous, attracting numerous competitors.

Expected benchmarks: Series A ARR £1M to £3M, 2.5x to 3x growth, NRR 90% to 100%, CAC payback 12 to 18 months, gross margin 75%+. Series B looks for £10M to £20M ARR, 1.8x to 2.5x growth, NRR 100% to 110%, burn multiple under 1.5.

Why these benchmarks? Because horizontal SaaS must scale customer acquisition aggressively to combat churn and competition. Customer success investments must be efficient (often via product and automation, not high-touch). Expansion revenue is moderate (20% to 35% of new ARR) because customers adopt features gradually, not dramatically.

Examples: Slack (100% to 110% NRR in growth stage), Stripe (exceptional NRR driven by expansion), Notion (viral adoption enabling high growth). These companies achieve horizontal SaaS benchmarks by excelling at product-led growth and viral expansion.

Vertical SaaS: Deep Embedding and Higher Multiples

Vertical SaaS targets a specific industry or function; accounting for accountants, HR software for restaurants, practice management for veterinarians. Switching costs are high (industry-specific workflows, integrations to industry tools, training sunk cost), moats are defensible (deep knowledge of vertical dynamics), and competition is lower.

Expected benchmarks: Series A ARR £1M to £4M, 1.5x to 2.5x growth (lower than horizontal due to smaller TAM per vertical), NRR 100% to 115%, CAC payback 15 to 24 months (longer due to complex implementation), gross margin 75%+, monthly churn 0.25% to 0.75% (lower due to switching costs).

Series B looks for £8M to £20M ARR, NRR 110%+, burn multiple under 1.5, clear expansion revenue (40% to 60% of new ARR) driven by customers buying additional vertical-specific modules.

Vertical SaaS trades lower growth for higher defensibility. A company at £10M ARR growing 1.5x annually with 112% NRR and 0.3% monthly churn is more valuable (venture-scale) than a horizontal SaaS at £10M growing 2.5x annually with 98% NRR and 3% monthly churn. The vertical SaaS survives downturns; the horizontal SaaS must perpetually acquire.

Developer Tools and Infrastructure SaaS: The Efficiency Paradox

Developer tools (Stripe, Twilio, GitHub, PagerDuty) and infrastructure SaaS (Datadog, CockroachDB) show the highest NRR (130% to 150%) but lowest CAC absolute spend. Why? Developers self-serve (low CAC), adopt products rapidly (fast time-to-value), and expand usage as they build more features (natural consumption growth).

Expected benchmarks: Series A ARR £2M to £8M, 2.5x to 3.5x growth (developers adopt fast, viral loops common), NRR 110% to 130%, CAC payback 6 to 12 months (developers close as self-serve, low friction), gross margin 75% to 90%, monthly churn 1% to 2% (developers commit via integrations).

Series B looks for £10M to £30M ARR, 2x to 3x growth, NRR 120% to 150%, burn multiple 0.8x to 1.3x (exceptional unit economics), expansion revenue 50%+ of new ARR.

The catch: developer tools face extreme competition (low switching costs if alternative exists), and pricing is often usage-based (margin sensitive to efficiency). Profitability requires operational excellence; burn multiples must be tight.

AI-Native SaaS: New Economics, Evolving Benchmarks

AI-native SaaS companies (companies built on LLM, computer vision, or other models as the core value proposition) are still establishing benchmarks as of 2026. However, several patterns are visible. First, gross margins are typically 50% to 70% (compared to 75%+ for traditional SaaS) due to inference cost pressures; every API call to an LLM provider incurs real-time cost. Second, CAC is moderate (£500 to £5,000 per customer typically) due to evolving product-market fit; AI product adoption is slowing as hype gives way to pragmatism. Third, churn is higher than traditional SaaS (2% to 5% monthly) as users test features, find they don't meet needs, and move to alternatives.

Expected benchmarks: Series A ARR £500k to £2M (still early-stage), 1.5x to 2.5x growth, NRR 80% to 110% (highly variable; some AI companies achieve 120%+ NRR, others struggle with churn), gross margin 50% to 70%, CAC payback 12 to 24 months.

Series B looks for £5M to £15M ARR, 1.5x to 2x growth, NRR trending to 100%+, gross margin improving toward 70%+ (as inference costs decrease and volumes increase), defensibility story essential (why AI moats are defensible in your category).

The key differentiator for AI-native SaaS: defensibility. Pure inference cost moat (just calling an LLM cheaply) is temporary. Sustainable AI-native companies have defensible data, unique models, or workflow integration advantages. Investors scrutinise this carefully.

Fintech SaaS: Complexity as Competitive Advantage

Fintech SaaS (payments, lending, treasury, expense management for businesses) combines high regulatory barriers (defensibility) with complex sales processes (long cycles, high CAC). ACV is typically very high (£50k to £500k+ for B2B fintech).

Expected benchmarks: Series A ARR £2M to £6M, 1.5x to 2.5x growth (complex sales slow acquisition), NRR 90% to 105% (expansion exists as customers grow balance sheets, but switching costs are high and churn is low even without expansion), CAC payback 18 to 36 months (long sales cycles, high-touch implementation), gross margin 75%+.

Series B looks for £12M to £30M ARR, 1.3x to 2x growth, NRR 100% to 110%, burn multiple 1.3x to 1.8x (fintech often tolerates higher burn due to high ACV economics), monthly churn 0.5% to 1.5% (regulatory switching costs create stickiness).

Fintech SAC (Sales and Acquisition Cost) is high because compliance, integrations, and deployment require dedicated resources. However, LTV (Lifetime Value) is equally high due to regulatory moat and account stickiness. The LTV: CAC ratio might be 5:1 or 6:1 (excellent), justifying aggressive CAC investment.

Consumer SaaS: Growth Through Virality, Margins Through Scale

Consumer SaaS (Slack for consumers, WhatsApp payments, TikTok creator tools) must drive adoption through viral mechanisms because traditional marketing ROI doesn't work at consumer CAC. Churn is high because switching costs are minimal and competitor alternatives are one click away.

Expected benchmarks: Early-stage (pre-Series A), monthly churn 5% to 15%, NRR 80% to 100% (expansion from subscriptions or premium tiers), CAC near £0 or £1 to £5 (viral growth), gross margin 60% to 80%.

Series A for consumer SaaS is rare and requires exceptional metrics: viral coefficient above 1.0 (each user invites more than one new user), DAU (daily active user) retention 50%+, month-one retention 30%+. If you've achieved this, Series A investors believe your path to network effects and scale.

Consumer SaaS typically requires larger rounds and longer to monetisation than B2B SaaS. A consumer app at 50M users and 5% monthly churn is more valuable than a B2B SaaS at £20M ARR and 2% monthly churn, despite vastly different monetisation stages.

Vertical SaaS Within Fintech, Healthtech, Legaltech: Nested Categories

Some categories combine traits of multiple verticals. Healthtech (medical practice management, patient engagement, health insurance software) combines fintech's regulatory complexity with vertical SaaS's industry-specific defensibility. Legaltech (practice management, contract analysis, legal research for law firms) combines vertical SaaS's deep embedding with complexity and long sales cycles.

Expected benchmarks for these nested categories: blend fintech and vertical SaaS. Healthtech: £1M to £5M Series A ARR, 1.5x to 2.5x growth, 95% to 110% NRR, 18 to 30 month CAC payback. Legaltech: similar pattern, with slightly higher CAC and longer payback due to legal industry conservatism.

Positioning Your Metrics Against Vertical Benchmarks

In fundraising, always position metrics against vertical benchmarks, not horizontal SaaS defaults. "Our vertical SaaS company at £6M ARR growing 1.6x annually with 108% NRR and 0.4% monthly churn compares favourably to vertical SaaS peers, despite appearing slow against horizontal SaaS." Show your investor the right comparison set.

Additionally, explain why your vertical has different characteristics. "Our developer tool has 60% gross margin (below horizontal SaaS 75% benchmark) because we incur significant compute costs per API call, but this is standard in our category and our gross margin improves with scale as infrastructure efficiency increases." Investors who understand your vertical will accept this explanation; those unfamiliar will question it. Address proactively.

Key Takeaways

• Horizontal B2B SaaS: high growth (2.5x to 3x), high CAC, lower NRR (95% to 105%); competition drives acquisition intensity
• Vertical SaaS: lower growth (1.5x to 2.5x), high defensibility, 100% to 115% NRR; switching costs create moat
• Developer tools: highest NRR (120% to 150%), viral adoption, lowest CAC; efficiency and competition are core risks
• AI-native SaaS: evolving benchmarks, 50% to 70% gross margin (inference costs), variable NRR; defensibility essential
• Fintech SaaS: high ACV, long sales cycles, 18 to 36 month CAC payback, high LTV; regulatory moat drives defensibility
• Consumer SaaS: viral growth required, 5% to 15% monthly churn, nearly £0 CAC; requires exceptional retention metrics for Series A
• Always compare metrics to vertical benchmarks, not horizontal SaaS defaults; context matters as much as numbers

Frequently Asked Questions

Our developer tool has 65% gross margin, below the 75% benchmark. Is this a red flag? Not necessarily. Some developer tools (those with high infrastructure costs) naturally have lower gross margins. As your volume scales, infrastructure unit costs decrease and gross margin typically improves. Show investors your roadmap for gross margin improvement and track it quarterly. If gross margin is declining, that's a red flag.

Our vertical SaaS grows at 1.2x annually but our NRR is 115%. Is this enough for Series A? Growth is on the lower side for Series A, but exceptional NRR and retention metrics might compensate. Show: (1) why growth is slowing (market penetration, not product-market fit failure); (2) total ARR and path to £8M+ (the Series B target); (3) cohort retention curves proving retention is durable. Some investors bet on vertical SaaS defensibility over growth rate.

How do we benchmark against AI-native SaaS peers when benchmarks are still developing? Transparency matters most. Show your gross margin, monthly churn, NRR, and CAC payback. Compare to the most similar AI-native companies you can find (similar models, market). Explain deviations: "Our inference costs are £500k monthly on £2M revenue (25% COGS) due to high model quality; competitors with lower quality achieve 35% COGS. We're trading margin for defensibility." Investors will respect this explanation if you're tracking the trade-off intentionally.

Our fintech SaaS has 36-month CAC payback but 6x LTV: CAC ratio. Is this venture-scale? Potentially yes, but verify the inputs. If ACV is £100k, LTV is £600k, and payback is 36 months, that's excellent. However, ensure churn assumptions are conservative (actual monthly churn, not optimistic projections) and that you're excluding high-touch customer success costs from the LTV calculation. If LTV: CAC is genuinely 6x, most investors will back you despite long payback.