Agency-SaaS hybrids run a structurally different runway model than pure SaaS. A bootstrapped business with $30K/month in services revenue and $8K/month in SaaS MRR has very different runway dynamics than a pure $38K MRR SaaS — the services revenue is project-based, time-bounded, and concentration-prone, while the SaaS MRR is recurring and structurally compoundable. Most founders running this model conflate the two in their runway math, which produces a number that's either too optimistic (services treated as recurring) or too pessimistic (SaaS treated as project-volatile). This guide walks through how to actually calculate runway in a hybrid model, the cost structure that makes the dual revenue stream work, and the transition point where the business should commit to one model or the other.
Cost structure
Hybrid agency-SaaS cost structure typically allocates 25-35% to delivery (services execution — usually 1-3 senior contractors or employees doing the actual client work), 25-35% to engineering (SaaS product development), 10-15% to sales and account management (services revenue requires active relationship management; SaaS has lower-touch acquisition), 10-15% to overhead and tooling, and the rest to founder salary. The two cost lines hybrid founders most often miscalculate: delivery capacity (services revenue requires headcount that scales linearly with revenue, unlike SaaS) and SaaS engineering opportunity cost (founder time spent on services delivery is time not spent on SaaS product, which creates a structural ceiling on SaaS growth that's invisible in monthly P&L).
MRR and ARR norms
Hybrid model MRR norms split between two revenue streams: services revenue at $10-50K/month per active client (usually 3-8 concurrent clients for a 2-person team), SaaS MRR layered on top at $1-10K/month per SaaS customer (usually $5-30K total SaaS MRR while services dominates). The natural transition point is when SaaS MRR exceeds services revenue — at that point the founder should commit to one model. Most hybrid founders never make this transition because services revenue is the immediate cash flow and SaaS is the slower compound; the result is a 3-5 year stall where neither business reaches scale.
Operator-grade runway target
12-18 (services-funded) or 18-24 (transition-stage) months
Pure services businesses run on shorter runway (12 months) because revenue is more immediate and adjustable — losing a client doesn't shorten runway 18 months in the future. Hybrid models in the transition phase (where SaaS is growing past services) need longer runway (18-24 months) because the SaaS growth phase requires consistent product investment that services revenue subsidizes. The trap: hybrid founders running services-grade short runway when they should be running SaaS-grade long runway because they're trying to compound a SaaS business.
Agency / Consultancy Hybrid benchmarks (2026)
| Metric | Operator-grade band |
|---|---|
| Services revenue concentration (top client) | <30% of services revenue |
| SaaS MRR percentage of total revenue (early) | 10-30% |
| SaaS MRR percentage at transition | 50%+ |
| Median monthly SaaS-side churn | 3-6% |
| Operator-grade runway (transition phase) | 18-24 months |
Run the math
Model your Agency / Consultancy Hybrid runway in 60 seconds
Drop in your cash, MRR, monthly burn, growth rate, and planned hires. The calculator projects 24 months under both current trajectory and the after-hire scenario, flags the danger zone, and exports to PDF for the investor update.
Open the Runway Calculator →Frequently Asked Questions
Should I combine services revenue with SaaS MRR for runway math?
Compute runway against each separately, then sum. Services revenue should produce a 'services-only runway' (cash + services receivables ÷ services-dedicated burn) and SaaS MRR should produce a 'SaaS-only runway' (cash + SaaS MRR ÷ SaaS-dedicated burn). The combined view is the operating runway, but separating them surfaces the dependency: a hybrid with 12-month services runway and 30-month SaaS runway is structurally a services business; the inverse profile is structurally a SaaS business that happens to do services.
When should a hybrid agency-SaaS founder commit to one model?
When SaaS MRR exceeds services revenue and SaaS growth rate exceeds 8% MoM, the structural case for committing to SaaS is established. When services revenue is growing faster than SaaS and SaaS retention is stagnant, the business is structurally a services business with a SaaS sidecar — committing to services and shutting down SaaS development frees up engineering capacity that increases services capacity. Most founders hold the hybrid model too long, hoping SaaS will accelerate without dedicated investment; the data rarely supports that hope.
How does services revenue affect SaaS valuation?
Services revenue typically values at 1-2x annual revenue (project-based, lower predictability), while SaaS MRR values at 5-10x ARR or higher. A hybrid business with $300K services revenue and $150K SaaS ARR ($12.5K MRR) values at roughly $300-600K (services) + $750K-1.5M (SaaS) = $1.05-2.1M. Pure SaaS at the same total revenue ($450K ARR) values at $2.25-4.5M. The valuation gap is a structural reason to transition to pure SaaS when growth math supports it.
Can services revenue make SaaS unit economics look better than they are?
Yes, materially. Founder time spent on services delivery is time not spent on SaaS engineering. If that time were valued at full cost ($100-200K/year for a senior founder), the SaaS side's true CAC, engineering cost, and gross margin would all look worse. Hybrid founders who exclude founder time from SaaS-side cost calculations report SaaS unit economics that don't survive a switch to a pure-SaaS team. Honest unit economics requires charging the SaaS side for proportional founder time.
Companion tools for Agency / Consultancy Hybrid
Runway is the cash-window metric. Pair it with the MRR Health Snapshot to grade recurring-revenue durability under your agency / consultancy hybrid retention profile, the Cohort Visualizer to validate retention curves by signup cohort, the CAC Payback Calculator to confirm acquisition pays back inside your runway window, and the Fundability Scorecard to map your numbers against the investor stage band that fits your sector.
Runway guides for other SaaS sectors
Related reading
- The SaaS Runway Playbook for Bootstrapped Founders — the 18-month target and three runway scenarios every operator should model.
- How to Calculate SaaS Runway in 4 Inputs — formula walkthrough with worked example.
- Burn Multiple for Bootstrapped SaaS — why bootstrapped founders should target <1.0x instead of the venture <2.0x bar.
- MRR vs ARR for bootstrapped founders — which metric to lead with at each stage.