Agency-SaaS hybrid MRR health math is the most distorted of any SaaS category because services revenue commingled with SaaS subscription revenue inflates every health metric in ways that don't survive a transition to pure SaaS. A bootstrapped hybrid with $25K/month services and $8K SaaS MRR reporting a 'blended Quick Ratio of 6' is typically running a SaaS-side Quick Ratio of 1.5-2 once services revenue is decoupled. The same inflation affects NRR (services-client expansion gets counted as SaaS expansion), gross churn (services revenue stickiness masks SaaS churn), and Quick Ratio (services-side new revenue gets counted in the SaaS numerator). This guide walks through how to decompose hybrid MRR health honestly, why the SaaS-side health profile depends on which underlying SaaS segment the product fits, and the A-grade thresholds that apply once revenue is unbundled.
Churn profile
Agency-SaaS hybrid churn is bimodal. Services revenue churn behaves like consulting (project-based revenue with high renewal risk at engagement end, 20-40% annual customer churn). SaaS subscription churn behaves like the underlying SaaS segment the product fits — if the SaaS product targets B2B SMB, expect 3-5% monthly SaaS churn; if it targets vertical workflows, expect 1.5-3% monthly. Bootstrapped hybrid founders frequently report 'blended churn of 8% annually' that combines the two — math that obscures the much higher services-side churn and the SaaS-side churn that determines long-term durability. Honest reporting requires separate churn computation for each revenue stream. NRR runs similarly bimodal: services NRR depends on engagement renewal patterns (60-90% typical); SaaS NRR depends on segment (100-115% for SaaS-side, before services-conversion expansion is layered in).
Expansion engine
Hybrid agency-SaaS expansion runs through three structural mechanics: services-to-SaaS conversion (existing services clients adopt the SaaS product as part of an engagement, contributing $200-2,000/month per converted client — the highest-velocity expansion lever in early-stage hybrids), services engagement renewal and scope expansion (clients on existing engagements expanding scope or signing new engagements, contributing services revenue that shouldn't be counted in SaaS NRR), and SaaS-side organic expansion through the same mechanics as the underlying SaaS segment (seat adds, tier upgrades, module attaches). The trap: hybrid founders frequently load services-to-SaaS conversion into 'SaaS expansion' rather than treating it as new SaaS customer acquisition, which inflates SaaS-side NRR to apparent 140-180% — numbers that don't survive a transition to pure SaaS.
A-grade health targets
A-grade: SaaS-side Quick Ratio matches underlying segment, services-to-SaaS conversion >15%, blended reporting prohibited
Hybrid agency-SaaS A-grade thresholds anchor on the SaaS-side performance against the segment the product fits, not a hybrid-specific benchmark. If the SaaS product is B2B SMB, SaaS-side Quick Ratio should match B2B SMB targets (3-5); if it's vertical workflow, SaaS-side Quick Ratio should match vertical SaaS (2-4). Services-to-SaaS conversion above 15% of active services clients within 6 months indicates the conversion engine is functioning. Blended reporting — combining services and SaaS revenue into single Quick Ratio, NRR, churn — is prohibited at operator-grade because it inflates apparent health beyond what the SaaS side can sustain without services subsidy. The honest health diagnosis requires unbundled reporting.
Agency / Consultancy Hybrid MRR health benchmarks (2026)
| Metric | Operator-grade band |
|---|---|
| SaaS-side gross churn (depends on segment) | Match underlying SaaS segment |
| Services-to-SaaS conversion rate (active clients) | >15% in 6 months |
| Services revenue churn (annual) | 20-40% |
| SaaS-side Quick Ratio (against segment baseline) | Match underlying SaaS segment |
| Blended reporting (commingled services + SaaS) | Prohibited at operator-grade |
Run the math
Grade your Agency / Consultancy Hybrid MRR health in 60 seconds
Drop in your current MRR, new MRR, expansion MRR, and churned MRR. The snapshot returns Quick Ratio, NRR, gross churn, and an A-F durability grade calibrated to your sector, flags which lever is dragging the grade down, and exports to PDF.
Open the MRR Health Snapshot →Frequently Asked Questions
Why does commingling services and SaaS revenue inflate Quick Ratio?
Services revenue is project-based and lumpy; SaaS revenue is recurring and predictable. Adding services revenue to the SaaS Quick Ratio numerator inflates the apparent new-revenue figure because services contracts often add $5-20K of one-time revenue in a single month — which then disappears from the next month without churning in the SaaS sense. The math: a hybrid with $8K SaaS MRR and a $15K services contract signed in January reports 'new MRR of $23K' if commingled, vs $8K SaaS new MRR plus $15K services revenue separately reported. The commingled view inflates Quick Ratio by 2-3x and produces forecasting that breaks once services revenue cycles out.
How should hybrids compute SaaS-side NRR separately?
Cohort the SaaS-side customer base separately from services clients, measure cohort starting SaaS MRR, then measure same-cohort ending SaaS MRR 12 months later. A customer that pays $500/month SaaS subscription and $3,000/month for ongoing services counts in the SaaS NRR cohort at $500 starting MRR and is measured 12 months later at their then-current SaaS MRR — services revenue stays out of the NRR computation. This produces a SaaS-side NRR that matches the underlying segment's normal range (100-115%). Most bootstrapped hybrid founders find this exercise reveals SaaS-side NRR 30-50 percentage points lower than the commingled figure.
When does a hybrid have enough SaaS revenue to report on SaaS-side metrics alone?
When SaaS MRR exceeds 40-50% of total monthly recurring revenue. Below 40%, the SaaS side is too small to produce statistically meaningful NRR cohorts and the metrics swing widely month to month based on individual customer behavior. Between 40-60%, SaaS-side metrics become reliable but should still be reported alongside services-side metrics. Above 60%, the business has crossed into SaaS-primary territory and external benchmarking should anchor on SaaS-side metrics with services as a separate revenue line. Bootstrapped hybrid founders reporting SaaS-side metrics from a 15% SaaS-revenue-share business are producing numbers that are too noisy to act on.
Should services-to-SaaS conversion show up in SaaS NRR or new MRR?
New MRR. A services client adopting the SaaS product is a new SaaS customer entering the SaaS cohort — they were not in the SaaS revenue base before adoption. Counting their initial SaaS MRR as expansion within the existing SaaS cohort inflates NRR and produces unrealistic durability metrics. Operator-grade method: services-to-SaaS conversion contributes to new SaaS MRR for the conversion month, and the converted customer then enters the next cohort's NRR measurement as part of the starting base for that cohort. This treatment produces honest SaaS-side unit economics that survive a transition to pure SaaS.
Companion tools for Agency / Consultancy Hybrid
MRR health is the recurring-revenue durability metric. Pair it with the Runway Calculator to confirm the cash window supports the implied growth trajectory, the Cohort Visualizer to validate that agency / consultancy hybrid retention curves match the durability profile, the CAC Payback Calculator to verify acquisition spend fits inside the customer lifetime the churn profile produces, and the Fundability Scorecard to map your durability grade against the investor stage band that fits your sector.
MRR health guides for other SaaS sectors
Related reading
- SaaS Churn Rate by Segment — the churn profile that anchors MRR health math.
- Compounding Churn — how small churn deltas compound into durability gaps over 24 months.
- MRR vs ARR for bootstrapped founders — which recurring-revenue metric to anchor health reporting on.
- The SaaS Runway Playbook for Bootstrapped Founders — how MRR health feeds the runway model.