MSP Backup Attach Rate: Measure and Grow It
MSP backup attach rate shows how many managed clients buy backup from your firm. A simple formula is: clients with the defined backup service ÷ eligible managed clients × 100. The result gives you a starting point for finding gaps, reviewing offers, and building recurring revenue without guessing.
Key points
- MSP backup attach rate measures the share of eligible managed clients that purchase a defined backup service.
- Start with an account list that includes every eligible managed client.
- The denominator should include accounts that match your own service and eligibility rules.
- An attach event occurs when an eligible managed client starts a paid backup service that meets your written scope.
The number only helps if your team uses one clear definition. Decide which clients count, what qualifies as backup, and whether the measure covers every protected system or only the client account. Then report the same measure over time.
This guide covers measurement, pricing, software comparison, client reviews, recovery checks, and practical ways to grow backup revenue across an MSP client base.
What does MSP backup attach rate measure?
MSP backup attach rate measures the share of eligible managed clients that purchase a defined backup service. If 24 of 40 eligible clients buy that service, the rate is 60 percent. The numbers in that example are illustrative, not a benchmark or industry result.
The measure is an account-level view. It does not show whether every server, laptop, workload, or data set is protected. A client may have a backup contract while one important server remains outside the policy. Pair the account rate with a coverage review.
Use a written definition such as:
Attach rate = managed client accounts with an active paid backup service divided by all eligible managed client accounts.
Your policy should answer four points:
- Which accounts are eligible?
- What makes a service active?
- Does a trial count?
- Does one protected workload qualify, or must the full agreed scope be covered?
A clear rule prevents sales, service, and finance from reporting different numbers. It also makes a monthly review easier to trust.
How do you calculate the rate correctly?
Start with an account list that includes every eligible managed client. Mark whether each account has an active backup service under your written definition. Divide the number with the service by the eligible total, then multiply by 100. Record the date, source, and rules used.
A small worksheet can include:
| Field | Purpose |
|---|---|
| Client name | Identifies the account |
| Eligible | Shows whether the account belongs in the denominator |
| Backup status | Shows active, absent, pending, or unclear |
| Protected scope | Lists the systems or data covered |
| Monthly charge | Supports revenue review |
| Review date | Shows when the record was checked |
Suppose a fictional MSP has 50 eligible accounts. Thirty have the defined paid backup service. The attach rate is 30 ÷ 50 × 100, or 60 percent. If five accounts have an unclear status, do not quietly place them in either group. Resolve the records first or report the uncertainty beside the result.
A second measure can show service depth. Count protected workloads or data sources, then compare them with the workloads the client has agreed to protect. That figure answers a different question from attach rate. Keep both measures separate.
Which accounts belong in the denominator?
The denominator should include accounts that match your own service and eligibility rules. Many MSPs choose active managed clients with a current agreement. Others exclude accounts that have declined backup in writing, lack a supported environment, or receive only a limited service. The rule must be written and applied consistently.
Do not remove a difficult account simply because it has no backup service. Removing uncovered accounts makes the percentage look better while hiding a sales or risk discussion. Exclude an account only when it fails a documented eligibility rule.
Review these edge cases:
- A new client still in onboarding.
- A client with a dormant agreement.
- A client that buys backup from another provider.
- A client with a partial backup package.
- A client with no supported server or workload.
Your operations and finance teams should agree on the answer before reporting begins. Store the reason for each exclusion. A short note is enough, such as “outside managed scope” or “service not active.”
The denominator can change as your client base changes. Keep the same date range, account rules, and service definition each time you report the rate. Put changes in a note so a later reader can explain a rise or fall.
How should an MSP define a backup attach event?
An attach event occurs when an eligible managed client starts a paid backup service that meets your written scope. The event should have a clear start date, package, protected systems, price, and owner. A quote alone is not an attach event. Neither is a sales promise without an active service record.
A useful process moves through four states:
- Identified: the account lacks the defined service or has an unclear record.
- Reviewed: the team confirms systems, data, recovery needs, and current gaps.
- Proposed: the client receives a clear offer and scope.
- Active: the service is sold, configured, monitored, and recorded.
The active state needs a service check. A signed order with no configured backup should not be treated as complete. A configured job with no billing record needs review too.
Assign one owner for data quality. That person does not need to sell every opportunity. The role is to keep the account list, service records, and reporting rules aligned.
What should you compare in MSP backup software?
Compare software by the work your team must perform and the recovery result the client needs. Price matters, but a low license cost can lose its appeal if setup, monitoring, storage, support, or recovery work adds hidden labor.
Build a comparison sheet with these fields:
- Supported operating systems and workloads.
- Server and endpoint coverage.
- Cloud storage location and limits.
- Retention controls.
- Encryption and access controls.
- Alerts and failed-job reporting.
- Restore methods.
- Recovery testing workflow.
- Multi-client management.
- Billing or reporting support.
- Vendor support channels.
- Migration and exit terms.
Ask the vendor to show common tasks. Can a technician find a failed job quickly? Can the team see which client systems are outside policy? Can a user restore one file without restoring a full server? Can the MSP record a recovery test?
A feature list is not proof of fit. Match each feature to a service promise. If your offer promises monitored server backup, the platform must support the server types in your client base and give technicians a practical way to confirm job status.
How much does MSP backup software pricing affect profit?
MSP backup software pricing affects profit through license cost, storage, setup time, monitoring, support, recovery work, and account management. Review the full service cost per client, not only the vendor charge. A package that appears cheap can produce weak margins if technicians spend too much time correcting failed jobs.
Create a cost model for each package:
Monthly service cost = vendor fees + storage fees + expected labor + recovery labor allowance + other direct costs.
Then compare that cost with the client price. The difference is gross profit before broader business expenses. Keep software cost and client price in separate columns. That makes discounting easier to review.
A fictional example can show the method. Suppose a package sells for $500 per month. Direct software, storage, and labor costs total $300. The gross profit is $200, before other expenses. Those figures are placeholders, not a market price or recommended margin.
Run the model for small, medium, and large data sets. Include a server that grows over time. Check whether storage charges rise faster than the client price. If they do, set a review point in the agreement or price the package around a defined scope.
Profit is also affected by service design. An unlimited promise may create unknown storage and recovery work. A tightly defined package is easier to quote and manage.
How should you review MSP cloud backup pricing?
Review cloud backup pricing as a bundle of capacity, retention, transfer, recovery, support, and labor costs. Ask what the vendor bills by: device, workload, storage volume, protected capacity, transfer, or another unit. Then map that unit to how you sell the service.
Cloud storage can grow even when the client count stays flat. A client may add files, servers, retention days, or backup copies. Your review should compare source data with stored backup data and check the billing record against the agreed scope.
Use a monthly review with these questions:
- Did protected capacity change?
- Did retention change?
- Did the client add a server or workload?
- Did recovery work create extra labor?
- Did a failed job require technician time?
- Does the current price still cover direct costs?
Do not leave an old package in place after a client adds servers or data. Discuss the scope change and update the service record. Clear pricing protects the client relationship and gives your team a sound basis for margin decisions.
How can an MSP software comparison support a better offer?
An MSP software comparison should end with a service choice, not a long list of tools. Select the platform that fits your client environments, technician workflow, recovery needs, vendor support, and cost model. A tool that looks strong in a demo may still create friction in daily operations.
Score each option against your actual requirements. Use a simple scale such as pass, needs review, or does not fit. Add a note for every uncertain answer. Ask vendors to confirm claims in writing before you base a client promise on them.
Test a normal job and a failed job. Check setup, alerts, storage changes, file recovery, full-system recovery, and reporting. Let the technician who will manage the service take part in the test. Their feedback may reveal labor that a sales demo hides.
The comparison should also cover transition work. List the time needed to move existing clients, train staff, update agreements, and retire old tools. Those tasks affect profit even if the new license price looks attractive.
Choose one standard package first. Add exceptions only when the client environment requires them. Too many packages make quoting, billing, and support harder to control.
How do backup reviews help MSPs find revenue?
A backup review gives the MSP a reason to discuss client systems, data, storage, recovery, and service scope. It can reveal an account with no backup, a partial policy, an old package, or a mismatch between protected systems and business needs. Each finding needs a clear client discussion rather than a fear-based pitch.
Start with the account record. Confirm the managed services in scope, current backup status, protected workloads, retention rules, storage use, failed jobs, and recent recovery tests. Mark missing information as unknown. Unknown data is a review task, not proof that the client is unprotected.
The conversation can follow this path:
- Explain what the current service covers.
- Show what sits outside that scope.
- Ask what systems the client needs to restore first.
- Present a priced option with defined work.
- Record the decision and next action.
A client may decline. Record the decision and any agreed review date. A clear decline is easier to manage than an informal “not now” that disappears from the CRM.
Do not promise recovery outcomes that the selected service has not been designed and tested to support. Use the vendor’s documented capabilities and your own service scope. Recovery planning should match the client’s systems and priorities.
How can you grow backup revenue without adding ad spend?
An MSP can look for backup revenue inside its current account base before buying new traffic. Review active clients, dormant CRM contacts, old proposals, and accounts with partial coverage. The goal is a useful service conversation, not a mass message with unsupported risk claims.
Rank opportunities by evidence:
- No defined backup service.
- Backup exists but the scope is unclear.
- A server or workload sits outside policy.
- Storage or retention has changed.
- A prior proposal was never decided.
- The client has a new system or business need.
Give each account one next action and one owner. The action might be a record check, technical review, proposal, or follow-up call. Set a date. A list without ownership does not create progress.
Scrye Tech provides growth systems for US managed IT providers. Its 30-day Client Revenue Sprint helps MSPs identify and pursue revenue opportunities among active clients and dormant CRM contacts without starting with ad spend. Scrye Tech also offers a broader growth system covering demand capture, prospect qualification, nurturing, closing, expansion, and retention.
Use a service review as the reason for contact. Avoid pressure. Show the current scope, explain the gap, and let the client decide whether the proposed protection fits.
What should you report besides attach rate?
Attach rate is one measure. A useful operating view also shows coverage, revenue, cost, profit, service quality, and sales movement. These measures answer different questions, so do not merge them into one score.
Track account coverage: how many clients have the defined service. Track scope coverage: how much of each client’s agreed workload sits inside the policy. Track recurring revenue: what the backup service bills each month. Track direct cost and gross profit: what remains after direct delivery costs.
Add operating checks. Review failed jobs, unresolved alerts, recovery tests, storage growth, package changes, and open proposals. Use a date range for each report. A monthly view may suit one MSP, while a weekly service review may suit another.
Keep revenue beside account count. A higher attach rate does not always mean more revenue if new packages are small or discounts are heavy. Keep profit beside revenue too. Growth that requires too much labor can weaken the service.
A short report can show:
| Measure | Question answered |
|---|---|
| Attach rate | How many eligible accounts buy the service? |
| Scope coverage | Which agreed systems are protected? |
| Recurring revenue | What does the service bill? |
| Gross profit | What remains after direct costs? |
| Open opportunities | Which accounts need a next action? |
| Recovery checks | Has the team tested the service? |
Review changes with the people who own sales, service, and finance. One number rarely explains the reason for movement.
What can go wrong with backup attach reporting?
Reporting fails when teams count different accounts, mix quotes with active services, or ignore partial coverage. A dashboard can look precise while the underlying records remain unclear. Fix the process before debating small changes in the percentage.
Common problems include:
- A client is counted twice after a company name changes.
- A trial is counted as paid service.
- A former client stays in the denominator.
- A partial backup package is treated as full coverage.
- Storage fees are omitted from the cost model.
- Failed jobs are hidden by a broad “active” status.
Use one account ID across CRM, billing, and service tools. Give each status a definition. Review a sample of records manually. The purpose is not to create perfect paperwork. It is to make the number useful for a business decision.
A low rate is not automatically a failure. It may show that your offer does not fit some client environments, that the sales process lacks a review step, or that your records are incomplete. Find the cause before changing the product.
A higher rate is not automatically success either. Check service scope, delivery cost, recovery readiness, and client understanding. Protection should be real, recorded, and supportable.
A practical 30-day plan for improving the measure
Use the first week to define eligibility, active status, protected scope, and report dates. Export the client list. Remove duplicates. Mark unclear accounts for review. Do not change the historical number without recording the reason.
Use the second week for technical and commercial review. Confirm which workloads each client has, what the current service covers, and what direct costs the MSP pays. Flag accounts with no service, partial scope, old pricing, or missing records.
Use the third week for client conversations. Start with accounts where the gap is clear and the service fit is strong. Give technicians and account managers a short talk track. Ask permission to review the client’s current recovery needs.
Use the fourth week to send proposals, record decisions, and clean up the service data. Mark wins, declines, pending reviews, and unknown cases. Report the result with the same formula used at the start.
A simple plan works best when each account has a next step. Do not chase the percentage alone. Improve the quality of the service record, the clarity of the offer, and the link between protection and client needs.
FAQ
Is a higher backup attach rate always better?
No. A higher rate helps only when the service is correctly scoped, delivered, billed, and profitable. Check workload coverage, failed jobs, recovery testing, direct costs, and client understanding alongside the account percentage.
Should a client with one protected server count as attached?
Use the rule in your service definition. If your policy requires full agreed coverage, one protected server does not qualify. If your service sells a defined single-server package, it may qualify. Record the scope so the number remains clear.
Should free trials count in the rate?
Usually, a free trial should remain separate from paid attach rate. Create a trial status and report it beside active paid services. Counting trials as paid accounts can make sales progress and recurring revenue appear higher than they are.
How often should an MSP review backup pricing?
Review pricing when storage, retention, workloads, vendor fees, or service labor changes. A regular review also helps catch old packages. Use the same cost fields each time so the team can see whether the service still supports its price.
What should an MSP do if a client declines backup?
Record the decision, the date, the scope discussed, and the next review point. Do not remove the client from the eligible account list unless the account fails a documented rule. A clear record supports a later conversation without creating pressure.
How is cloud backup different from local backup for reporting?
The reporting formula can stay the same if both services meet your defined backup event. The cost and scope review must account for storage, transfer, retention, recovery method, support, and technician work. Keep the service types separate in the cost model when their delivery differs.
What is the first step in improving backup adoption?
Define the measure before contacting clients. Write the eligibility rule, active-service rule, protected scope, and reporting date. Then audit the account list. Clean data gives the team a sound starting point for client reviews and proposals.
