Section 1
The five challenges at a glance
Importing a software metric into a service business creates predictable failure modes, and most of them stem from forgetting the rule's provenance. Feld's original post was explicit about scope: the 40% rule applied to SaaS companies at scale, around $50 million in revenue, with recurring contracts and software gross margins (Feld, 2015). McKinsey's subsequent analysis of more than 200 software companies between 2011 and 2021 found firms exceeded Rule of 40 performance only 16% of the time, meaning the benchmark is aspirational even in its native habitat (McKinsey, 2021). Bessemer went further and argued equal weighting is itself wrong for valuation purposes, since public markets weight growth two to three times more heavily than free-cash-flow margin, the basis of their replacement metric, Rule of X (Bessemer, 2023). Meanwhile the service-business reality is sobering: SPI Research's 2025 Professional Services Maturity Benchmark, an industry vendor study, recorded billable utilization at 68.9% and EBITDA margins at 9.8%, the lowest in over a decade (SPI Research, 2025). Applying a 40% bar built on 80% gross margins to firms earning 9.8% EBITDA without adjustment produces despair, not discipline. The table maps the five challenges in adapting the rule honestly.
Section 2
Challenge one: get the provenance right before using the rule
Citation hygiene matters here because the Rule of 40's authority is often overstated. The rule was not invented by Brad Feld, and he never claimed it was. In his February 3, 2015 post, Feld wrote that he was at a board meeting and heard a late-stage investor describe his firm's 40% rule for a healthy software company; Feld relayed it, specifying it applied to SaaS companies at scale, assume at least $50 million in revenue (Feld, 2015). Fred Wilson of Union Square Ventures, who was at the same meeting, published his own post within days (Wilson, 2015), and the heuristic spread through the SaaS ecosystem from there. The empirical validation came later. McKinsey's analysis found that investors consistently reward companies at or above the Rule of 40 with higher enterprise-value-to-revenue multiples, top-quartile performers commanding nearly triple the multiples of bottom-quartile firms, while only about one-third of software companies achieve the benchmark at all, and sustained performance is rarer still: in a sample of more than 200 software companies from 2011 to 2021, firms exceeded the threshold only 16% of the time (McKinsey, 2021). Why does provenance matter for an agency owner? Because the rule is a valuation heuristic validated on recurring-revenue software economics, and every adaptation choice that follows depends on respecting what the evidence does and does not cover.
Section 3
Challenge two: the margin structure problem
The 40 in Rule of 40 is not arbitrary, but it is contextual. A SaaS business typically runs 75-85% gross margins, so a dollar of revenue growth carries enormous incremental profit potential; the 40% bar implicitly prices that structure. Service businesses run materially different physics. Gross margins for agencies and consultancies typically land between 50% and 65% after honest allocation of delivery labor, and SPI Research's 2025 benchmark, vendor data drawn from hundreds of professional services firms, shows the sector averaging 9.8% EBITDA margins with billable utilization of 68.9%, both at decade lows (SPI Research, 2025). The same study found leading firms target utilization between 70% and 80%, the zone where margin and sustainability coexist. Mechanically copying a 40% combined target onto this margin structure forces one of two distortions: firms chase growth they cannot deliver profitably, or they inflate margin short-term by cutting the delivery quality that retention depends on. The defensible adaptation is to rebuild the threshold from the margin base up. If best-in-class SaaS clears 40 on an 80% gross margin base, the equivalent discipline on a 60% gross margin base sits closer to 30, and a service firm combining, say, 20% annual growth with 15% EBITDA margin (a 35 score) is performing at a level comparable to a Rule of 40 software company. The bar must be honest about the business it measures, or operators will rationally ignore it.
Section 4
Challenge three: definitions and weighting decide whether the number means anything
Feld devoted a third of his original post to a warning that is routinely skipped: profit is harder to define than growth, and the rule's usefulness collapses if the definition floats. He preferred EBITDA as the baseline, back-tested against operating income, net income, and cash flow (Feld, 2015). For owner-operated service firms the definitional traps are worse. Owner compensation blended into profit, pass-through media or printing spend inflating revenue, and unbilled founder labor all distort both sides of the equation. The clean construction: revenue net of pass-throughs; growth measured year over year on that net figure; profit as EBITDA after normalizing owner salary to market rate. The second decision is weighting. Bessemer's research on public cloud companies found growth is worth roughly two to three times as much as free-cash-flow margin in valuation terms, leading them to propose Rule of X, growth times a multiplier, plus FCF margin, as a successor for at-scale companies (Bessemer, 2023). Their related efficiency-score framework targets growth-plus-margin of about 70% at $25-50M ARR and 50% beyond $100M (Bessemer, 2023), demonstrating that even within software the threshold flexes by stage. For service firms the practical translation is asymmetric tolerance: a point of durable, retention-backed growth is worth more than a point of margin squeezed from delivery, because growth compounds and squeezed margin usually reverts. Whichever construction you choose, freeze it, the metric's power is in its consistency across quarters, not its sophistication.
Section 5
Innovative solutions
Forward-thinking service operators are not just adapting the Rule of 40, they are extending it into instruments software companies never needed. The first innovation is the service-line Rule of 40: computing growth-plus-margin per offer rather than for the firm overall. A firm scoring 32 in aggregate often hides a 55-scoring productized offer subsidizing a 12-scoring legacy service; the disaggregated view tells you where to invest and what to prune, echoing Bain's finding that sustained value creators concentrate on a focused, profitable core (Bain, 2001). The second is the utilization-adjusted score: pairing the Rule of 40 with SPI's utilization benchmarks, because in services, margin is largely a derivative of utilization, firms below the 70-80% utilization zone (SPI Research, 2025) should treat utilization repair as the highest-leverage margin intervention available. The third is AI-augmented delivery margin: applying AI to proposal generation, reporting, research, and quality assurance directly raises the margin half of the score without headcount cuts, consistent with EY's finding that CEOs now demand measurable ROI from AI deployment (EY, 2026). The fourth is using the score as buyer-facing language: acquirers of agencies increasingly run efficient-growth math in diligence, and a founder who presents three years of a consistently constructed growth-plus-EBITDA score, with definitions documented, signals operating maturity that directly supports valuation, the same mechanism McKinsey documented in public-market multiples (McKinsey, 2021).
Section 6
Solution framework
The LeverageOS adaptation, the Service Rule of 40, runs in four steps. Step one: construct the inputs. Net revenue excludes pass-through spend; growth is trailing-twelve-month versus prior twelve; profit is EBITDA with owner compensation normalized to market. Document the definitions once and never move them, Feld's original warning about definitional drift (Feld, 2015) is the most common failure we see. Step two: calibrate the threshold to your gross margin. As a working rule: gross margin above 70%, hold the bar at 40; 55-70%, use 35; 45-55%, use 30. This preserves the rule's discipline while respecting the margin physics that McKinsey's software sample takes for granted (McKinsey, 2021). Step three: weight asymmetrically when making trade-offs. Following Bessemer's evidence that growth carries two to three times the valuation weight of margin (Bessemer, 2023), prefer moves that add durable growth over moves that add equivalent margin, unless you are below your margin floor, defined as the EBITDA level that funds working capital and one bad quarter. Step four: review quarterly at the service-line level and annually at the firm level, pairing the score with utilization (target the 70-80% zone per SPI Research, 2025) and net revenue retention. The framework's purpose is not to hit a magic number; it is to make every growth-versus-margin argument inside the firm resolvable with arithmetic instead of opinion.
Section 7
Evidence-based action plan
Week one: compute your baseline. Pull trailing-twelve-month net revenue growth and normalized EBITDA margin; add them. Most owner-operated service firms land between 15 and 35 on first honest measurement, below their calibrated bar but within repair distance. Weeks two and three: disaggregate by service line. Allocate delivery labor at loaded cost; identify your highest and lowest scoring offers. Month two: attack utilization first if you are below 70%, since SPI's decade-low sector data (SPI Research, 2025) shows utilization is the dominant controllable margin lever, recover it through better scoping, capacity planning, and pruning chronically discounted work. Month three: deploy one AI-assisted delivery improvement with measured before-and-after hours per engagement, targeting the margin side per EY's ROI-first doctrine (EY, 2026). Months four through six: rebalance the portfolio, scale the top-scoring service line with a defined acquisition budget, fix or exit the bottom one, and reprice anything whose score sits below your bar purely due to legacy rates. Quarter three onward: institutionalize the metric in monthly leadership reviews and in your annual planning, presenting growth and margin as one number with documented definitions. Within four quarters, the typical pattern is a 5-10 point score improvement, and, more durably, a leadership team that argues about evidence rather than anecdotes, which is the actual lesson the software industry's Rule of 40 decade left behind (Feld, 2015; McKinsey, 2021). For adjacent evidence in this pillar, see [Small Teams, Big Output: The Evidence on Revenue-per-Employee Leverage and the AI-Lean Operating Model](/blog/growth-small-teams-revenue-per-employee-ai-lean) and [Unit Economics That Survive Diligence: CAC and LTV Discipline for Agencies and Service Firms](/blog/growth-unit-economics-cac-ltv-diligence).