Project Attach Rate: The MRR Benchmark Most MSPs Get Wrong

"MRR is king" is the closest thing the MSP industry has to a founding creed, and for good reason. Recurring revenue compounds, smooths cash flow, and drives valuation. But there is a second number that separates well-run MSPs from the pack, and almost nobody tracks it as a managed metric: how much project revenue every dollar of MRR generates.

Call it the project attach rate. It is the clearest single indicator of whether your account management function is actually working - and most MSPs either do not measure it at all, or anchor on a benchmark that is really just the floor.

The Benchmark Is a Band, Not a Point

The number you will hear most often in peer groups is 30%: for every dollar of MRR, expect roughly thirty cents in project services revenue. That figure comes straight from the classic best-practice revenue split of 75% recurring and 25% non-recurring, which works out to $0.33 of NRR per MRR dollar.

The 30% figure is not wrong. It is just the conservative edge of the real range. Industry benchmark data tells a wider story. Datto's Global MSP Benchmark, drawing on more than 1,900 MSPs, puts the median recurring revenue share at 62% of total revenue - which means the typical MSP is actually generating about $0.61 of non-recurring revenue for every MRR dollar. And the average MSP still derives 25% to 40% of total revenue from project and break-fix work.

Put those together and the honest benchmark is a band:

$0.33 per MRR dollar - the disciplined floor

The 75/25 split. An MSP at this level with a structured review cadence is harvesting steadily without letting projects distort the business. Below this line, something is broken in opportunity identification.

$0.50 per MRR dollar - strong, review-driven harvest

This is what a mature TBR and EBR cadence produces: lifecycle refresh projects, security remediation, compliance work, and cloud migrations surfaced quarter after quarter from a documented roadmap.

$0.65 and above - the danger zone

Past this point the MSP is not harvesting projects from a recurring base. It is a project shop with a managed services side hustle. Revenue gets lumpy, staffing gets volatile, and valuation suffers.

Why the Ceiling Matters as Much as the Floor

Most content about project revenue treats it as pure upside: identify more needs, sell more projects, everyone wins. That is only half the story. The other half is what project dependency does to the value of the business.

Buyers and private equity firms discount non-recurring revenue heavily. A dollar of project revenue is commonly valued at 0.5x to 1x, while a dollar of managed services MRR is valued at 4x to 6x. The widely cited benchmark for unlocking premium multiples is recurring revenue above 70% of total. MSPs with 70% or higher MRR share have traded at meaningfully higher earnings multiples than peers below 50% MRR share at the same revenue size.

So the goal is not to maximize the attach rate. The goal is to hold it inside the band where project revenue is strong enough to prove the roadmap is converting, but never so large that it erodes the recurring ratio that makes the business valuable. Overshooting the ceiling is just as much a management failure as undershooting the floor.

Not All NRR Dollars Are Equal

Two MSPs can post the identical attach rate and be in completely different businesses.

The first harvests project revenue through a structured review cadence. Every Technology Business Review walks the lifecycle roadmap. Every Executive Business Review presents documented Red and Yellow risk items with a remediation plan and a budget number attached. Projects are forecast two to four quarters out, priced deliberately, and staffed on a plan. That NRR dollar is predictable, high margin, and repeatable.

The second gets the same dollar reactively: break-fix escalations, emergency replacements after something fails, projects scoped in a panic. Same ratio on the income statement, but unpredictable delivery, compressed margin, and zero strategic credit with the client.

The attach rate only becomes a health signal when you also track where the dollar came from. Review-sourced NRR is a Green indicator. Reactive NRR at the same volume is a Yellow one, because it means the roadmap is not doing the work.

Scoring It: The Project Attach Rate Metric

Here is how the metric is defined and scored inside the vCIO Framework, using the same Red, Yellow, Green model that runs through all 14 modules:

Project Attach Rate = trailing 12-month NRR divided by trailing 12-month MRR, calculated per client.

Green: $0.35 to $0.50 per MRR dollar. The roadmap is converting. Reviews are surfacing work, projects are being positioned and closed, and the recurring base still dominates the relationship.

Yellow: below $0.25. The account is under-harvested. Either reviews are not happening on cadence, the roadmap has no budget-attached items, or opportunities are being identified but never positioned. This is the most common state in unmanaged books of business - and it is where the invisible revenue leak lives.

Red: above $0.65. One of two problems is present. Either the client relationship is project-dependent, which is a churn and forecasting risk, or the managed agreement is underpriced and project work is quietly backfilling a margin gap that belongs in the recurring contract. Both need a pricing and scope review, not a celebration.

Calculating this per client rather than only at the company level is what makes it actionable. A healthy blended number can hide a book where a handful of Tier A accounts generate all the project work while the rest of the base sits untouched.

Expected Attach by Client Tier

Attach expectations should also flex by tier. Tier A (Always Engaged) accounts carry the deepest review cadence and the most active roadmaps, so they should reliably sit in the Green band and often at its top edge. Tier B (Betterment Focused) accounts should trend toward Green as their improvement plans convert to funded projects. Tier C (Core Consistent) accounts will naturally run lighter - a Tier C client at $0.25 may be perfectly healthy, provided lifecycle basics are current and no Red risk items are aging on the register.

That tier-adjusted view keeps the metric fair. It stops account managers from being penalized for a stable Tier C book, and it stops a flashy Tier A project pipeline from masking neglect everywhere else.

A Worked Example

Take an MSP billing $200,000 per month in MRR, or $2.4M annually in recurring revenue. The band math:

Floor ($0.33): roughly $792,000 per year in project revenue, about $66,000 per month.
Strong harvest ($0.50): $1.2M per year, about $100,000 per month.
Ceiling ($0.65): $1.56M per year. Above this, the recurring share of total revenue drops below the 70% valuation threshold and the business profile starts to change.

If that MSP is seeing $30,000 a month in project work - a $0.15 attach rate - the clients have not stopped having needs. The needs are simply going unidentified, unpositioned, or unconverted. On a $2.4M recurring base, the gap between $0.15 and the bottom of the Green band is more than $400,000 a year in revenue the MSP is already positioned to win.

The Attach Rate Is an Output, Not a Sales Target

The mistake is treating the attach rate as a quota - pushing account managers to "sell more projects" into accounts. That produces exactly the low-quality, reactive NRR dollar described above, and clients can smell it.

The attach rate is an output of an operating system. When reviews happen on cadence, when every environment has a scored risk register, when the lifecycle roadmap has budget numbers attached, and when the client sees the same Red, Yellow, Green picture the MSP sees, project revenue follows as a natural consequence of the client acting on their own documented priorities. The MSP never has to pitch. The roadmap does the selling.

Frequently Asked Questions

How do you calculate project attach rate?

Divide trailing 12-month non-recurring revenue by trailing 12-month recurring revenue, per client. Use a trailing 12-month window rather than a quarter - a single large project lands unevenly and a quarterly view will swing a healthy account into Red or Green on timing alone. Calculate it per client first and blend upward. The company-level number is useful for reporting, but the per-client number is the one that tells an account manager where to look.

Does hardware and license resale count toward the attach rate?

Track it separately. Pass-through hardware and license renewals inflate the ratio without saying anything about whether the roadmap is converting - an account can post a strong attach rate on a single refresh order while every Red risk item on its register sits untouched. The metric is meant to measure advisory conversion, so the cleanest version counts project services revenue: remediation work, migrations, lifecycle refresh labor, and compliance projects. If resale margin is a material part of the business, score it as its own line rather than letting it distort this one.

How long should it take to move an under-harvested account into the Green band?

Plan on two review cycles. The first Technology Business Review surfaces the gaps and puts budget numbers against them; the client needs time with those numbers; the second review is where deferred items get approved. On a quarterly cadence that is roughly six months from the first structured review to a measurable shift in the ratio. An account that has never had a documented roadmap will not move on the first meeting, and treating that first meeting as a failure is how MSPs abandon the cadence right before it starts working.

Should project attach rate be tied to account manager compensation?

Not as a quota. Compensating on the ratio itself recreates the reactive, low-quality revenue described above, because the fastest way to move the number is to push projects into accounts that did not ask for them. Compensate on the inputs that produce it instead: reviews completed on cadence, roadmaps maintained with budget attached, and Red and Yellow risk items dispositioned into either a funded remediation project or a signed risk acceptance. Manage those and the ratio follows. Manage the ratio and you get the behavior the metric was designed to detect.

That is the difference between a benchmark you hope to hit and a metric you manage. The framework builds the mechanism: a TBR structure that surfaces the work, a client health score that flags under-harvested accounts, and an expansion playbook for the revenue already sitting in your base. Measure the attach rate per client, score it Red, Yellow, Green, and manage the accounts - and the ratio takes care of itself.