RevOps for MSPs: Managed Agreements, MRR from Sold to Billed, Renewals and Agreement Margin
RevOps for MSPs explained: how managed agreements are priced and billed, MRR from sold to billed, which system owns each record, and agreement margin.
A managed service provider reviews the agreement it renews next month and finds nothing wrong with it. The users the client added were billed, and the monthly recurring revenue in the CRM matches the invoice to the dollar. The PSA shows a margin above the one the agreement was sold at, and its effective rate per technician hour is the highest in the book. Counted in full, the agreement has lost nine points of margin, because the client's devices grew faster than its users and the price counts users.
This article sets out revenue operations for a managed service provider as an operating model, independent of any software product. It starts with the agreement and its pricing unit, then follows monthly recurring revenue from sold to billed, the lifecycle and its handoffs, quarterly business reviews and renewals, and the system that owns each record. A definition of agreement margin is tested on sample data, followed by the metrics, a procedure, costs, symptoms, common questions and the limits of the evidence.
The finding can be checked in any MSP's records. An agreement's revenue follows only the unit it is priced on, while its cost follows users, devices and hours together, so its margin moves with whichever driver the price does not count. A PSA's contract profitability, as Autotask documents it, costs an agreement from the unit costs of the services it bills and the time charged to it, so an unbilled driver is held at the ratio assumed when the unit cost was set. The count of that driver sits in the RMM or the client's directory and its price in vendor bills, so no reconciliation of billing can find the loss: the invoice is correct.
Revenue operations, as the firm's foundations paper defines it, keeps objectives, records, measures, systems and decisions traceable to one another across acquisition, retention and expansion. A managed service provider (MSP), in the definition published by CISA and its partner agencies, delivers, operates or manages ICT services for customers under a contractual arrangement such as a service level agreement. Remote monitoring and management (RMM) software is what the same agencies describe MSPs using for endpoint monitoring, network management and remote support. A professional services automation (PSA) system records tickets, technician time, agreements and invoices. An agreement is the recurring contract a client is under, and agreement margin is its billed recurring revenue less the hours delivered under it at a loaded labour cost and the cost of every user and device it covers.
Managed Agreements: Pricing Units, Project Work and Committed Costs
An MSP sells a standing obligation whose price is fixed before the work it covers is known. Among Autotask's contract types, the recurring service contract generates a billing item at a regular interval as a fixed amount per unit, such as a PC or a software licence, and suits billing regardless of the amount of work performed. The cost of consumption therefore sits with the provider.
Three pricing bases follow, and each counts one driver of cost. An agreement priced per user bills users, one priced per device bills devices, and a flat agreement bills neither. Cost follows every driver at once: technician hours with users and their devices, per-user services with the user count, and per-device tools with the device count. Datto RMM, for example, consumes a licence for each server, desktop and laptop running its agent and for each managed network device, printer and ESXi host.
Project work runs beside the agreement on its own terms, from the onboarding project sold with it to later refreshes and migrations. Under a fixed price contract, Autotask notes, the provider completes the tasks for one price regardless of the labour and materials costs incurred. The nearest peer-reviewed evidence concerns software projects rather than managed services: across 93 offshore projects at one vendor, the analysis of Gopal and colleagues suggests that contract choice significantly determined project profit.
Resold licences add a cost committed on terms the agreement may not match. Under Microsoft's new commerce rules, the licences on a subscription can be decreased only within the first seven days after they were added, and after that not until the cancellation window at renewal. An agreement letting a client remove users monthly, resting on annual-term licences, leaves each removed user's licence cost with the provider until that renewal.
MRR from Sold to Billed
Monthly recurring revenue (MRR) passes through four states between signature and cash, each held by a different record. MRR sold is set at signature in the CRM, where HubSpot, for example, calculates a deal's monthly recurring revenue from its recurring line items and ignores the Amount property. MRR contracted but not yet billed covers onboarding. MRR billed is set by the PSA, whose copy of the agreement changes whenever the service desk adds or removes units, and MRR collected is set in accounting when the invoice is paid.
After onboarding, units added, units removed and cancellations move billed MRR away from sold. Where the PSA is amended and the CRM is not, the two diverge while their totals stay close, because additions offset reductions. The arithmetic, and a reconciliation by agreement that finds the gap, are set out in the guide to the best CRM for MSP businesses. A reconciled bridge proves that revenue is recorded alike in both systems, and says nothing about cost.
The Client Lifecycle and Its Four Handoffs
The lifecycle runs from enquiry to renewal and then loops, since each renewal prices the same agreement again. An assessment of the client's estate leads to a proposal, a signed agreement and an onboarding project. Service then runs monthly, as RMM alerts and client requests become tickets, technicians record time against them and the service desk amends units as the client changes.
Sales hands the onboarding project a signed agreement, with its pricing basis, unit counts and the assumptions its price was built on: devices per user or users per device, and expected hours. In a PSA-native stack Autotask's Won Opportunity Wizard closes the opportunity and manages the handoff to delivery in one database. The handoff fails when the assumptions stay in a pricing spreadsheet, leaving the first review nothing to compare against.
The onboarding project hands the service desk a mapped estate. In Autotask a ticket takes its contract from its device first, then from the organisation's default service desk contract, then from the parent organisation's default (Autotask contract application). The handoff fails when discovered devices are left unmapped, so their alert tickets bill through a default contract or through none.
The service desk hands finance time and amendments. Time bills through the ticket's contract unless its role or work type is excluded, in which case Autotask bills the entry at Admin role rates outside the contract. The handoff fails when project work is logged on agreement tickets or agreement work on project tasks, moving cost between contracts whose profitability finance will read.
Finance hands account management the agreement's economics, and this return carries the finding. Billed revenue and time sit in the PSA, devices in the RMM, users in the client's directory and unit prices in vendor bills, and only a join of all four gives the margin the review and the renewal need.
Quarterly Business Reviews, Renewals and Expansion
A quarterly business review (QBR) is a scheduled meeting at which provider and client review the agreement's service record. Its material comes from delivery: tickets, hours and service level attainment from the PSA, and the age and health of the device estate from the RMM. Its output is commercial, whether a refresh project, an added service, or a change of price or scope proposed ahead of renewal.
A project becomes a separate fixed price or time and materials contract, while an added service changes the agreement's units and MRR in the PSA, and both begin as opportunities in the CRM. The renewal then turns margin into a price through one of three levers, a higher unit price, a pricing basis that counts the driver which grew, or a narrower scope, and choosing between them needs margin broken down by driver.
Records in the PSA, the RMM, the CRM and Accounting
The PSA is the agreement of record. ConnectWise states that agreement tie-back keeps all work billable and accounted for, and that its agreements track the hours clients use against their contracts. An Autotask recurring service contract carries services and bundles, each with a unit price and, optionally, a unit cost and a vendor.
The RMM holds the device estate. Datto RMM devices appear in Autotask as configuration items, and on the Endpoint Management Configuration Item Mapping page each can be assigned a billing contract and, for recurring service contracts, a service or bundle (Datto RMM and Autotask). Monitor alerts create tickets in designated queues.
The CRM holds what happens before an agreement exists and before each renewal: leads, opportunities, quotes, the pricing basis as sold, renewal opportunities and QBR outcomes. A general CRM can also model the agreement: Salesforce's service contracts represent warranties, subscriptions and service level agreements, while HubSpot needs a custom object, available on Enterprise subscriptions, whose design is set out in the MSP service agreement object. Accounting holds invoices, cash, payroll and the vendor bills for every tool and licence.
| Record | System of record and owner | What the agreement review needs |
|---|---|---|
| RecordLead, opportunity, quote and pricing basis as sold | System of record and ownerCRM; sales | What the agreement review needsPrice, units and the assumptions behind them |
| RecordAgreement: services, units, price and term | System of record and ownerPSA; service delivery | What the agreement review needsBilled units and MRR by month |
| RecordOnboarding and later projects | System of record and ownerPSA; project team | What the agreement review needsProject fees and hours, by agreement |
| RecordTickets and time entries | System of record and ownerPSA; service desk | What the agreement review needsHours on the agreement |
| RecordManaged devices and alerts | System of record and ownerRMM; service desk | What the agreement review needsDevice count by client, by month |
| RecordUsers and licence terms | System of record and ownerClient directory and licensing portal; service desk | What the agreement review needsUser count by client, and each licence's term |
| RecordInvoices, cash, payroll and vendor bills | System of record and ownerAccounting; finance | What the agreement review needsMRR collected, loaded labour cost, unit prices of tools and licences |
| RecordQBR outcomes, renewal and expansion opportunities | System of record and ownerCRM; account management | What the agreement review needsAgreement margin, by driver |
Agreement Margin and the Records It Joins
Agreement margin is billed recurring revenue less three costs: hours delivered at a loaded labour cost, users covered at the per-user cost of their services, and devices covered at the per-device cost of the tools that manage them. Effective rate, monthly revenue divided by hours delivered, ranks agreements by the price of labour and leaves out every other cost.
The PSA computes a margin of its own. Autotask's recurring service contracts carry a built-in profitability monitor that tracks time charged to the contract at each resource's internal rate, and profitability includes the unit cost set on each service. That cost is counted in the service's own units, which are the units billed. On an agreement priced per user and carrying no device service, devices enter only through the user service's unit cost, fixed at an assumed number of devices per user, so the PSA's margin stays put when the device count rises.
The repair is to count every driver, billed or not. Autotask's billing rules count active contacts or devices on a chosen date to set a billing product's units for the next monthly period, which offers one route; a monthly join of RMM device counts and directory user counts to vendor prices offers another. On either route the result has to reach the CRM, where the renewal is priced.
Agreement Margin on Sample Data
The figures below are sample data for an invented MSP and describe no client. A year ago it signed three agreements with three clients of identical size, each at $5,000 a month priced to a 30.0 percent margin, on three different bases. The sample costs a loaded technician hour at $80, the per-device stack of RMM agent, endpoint protection and backup at $14 a device a month, and per-user services at $10 a user. Resold licences are billed on their own lines and left out.
| Measure | A, per user | B, per device | C, flat |
|---|---|---|---|
| MeasurePrice | A, per user$125 a user | B, per device$100 a device | C, flat$5,000 a month |
| MeasureUsers and devices at signature | A, per user40 and 50 | B, per device40 and 50 | C, flat40 and 50 |
| MeasureExpected hours a month | A, per user30 | B, per device30 | C, flat30 |
| MeasureMRR sold | A, per user$5,000 | B, per device$5,000 | C, flat$5,000 |
| MeasureExpected tools and labour | A, per user$1,100 and $2,400 | B, per device$1,100 and $2,400 | C, flat$1,100 and $2,400 |
| MeasureMargin as priced | A, per user30.0% | B, per device30.0% | C, flat30.0% |
| MeasureUnit cost set on the PSA service | A, per user$27.50 a user, assuming 1.25 devices per user | B, per device$22.00 a device, assuming 0.8 users per device | C, flat$1,100 a month, assuming 40 users and 50 devices |
At signature each agreement's tools cost 40 × $10 + 50 × $14 = $1,100 and its labour 30 × $80 = $2,400, leaving $1,500 of $5,000. Twelve months later the three clients have grown in different directions.
| Measure | A, per user | B, per device | C, flat |
|---|---|---|---|
| MeasureUsers | A, per user44, billed | B, per device50 | C, flat46 |
| MeasureDevices, from the RMM | A, per user96 | B, per device55, billed | C, flat60 |
| MeasureHours on the agreement | A, per user32 | B, per device34 | C, flat38 |
| MeasureMRR billed, matching the CRM | A, per user$5,500 | B, per device$5,500 | C, flat$5,000 |
| MeasureEffective rate per hour | A, per user$171.88 | B, per device$161.76 | C, flat$131.58 |
| MeasureMargin in the PSA, at the unit cost set | A, per user$1,730, or 31.5% | B, per device$1,570, or 28.5% | C, flat$860, or 17.2% |
| MeasureTool cost with every unit counted | A, per user$1,784 | B, per device$1,270 | C, flat$1,300 |
| MeasureAgreement margin, every unit counted | A, per user$1,156, or 21.0% | B, per device$1,510, or 27.5% | C, flat$660, or 13.2% |
Every check on revenue passes: the users added to A and the devices added to B were amended in the PSA and written back to the CRM, so neither a reconciliation nor a check of billed-unit drift finds anything.
The PSA's own figures put A first. Its effective rate is $5,500 ÷ 32 = $171.88 an hour, the highest of the three, and its PSA margin is $5,500 − 44 × $27.50 − 32 × $80 = $1,730, or 31.5 percent, above the 30.0 percent it was sold at, so on those figures A would renew unchanged.
Counted, A has lost nine points. Its user price assumes 44 × 1.25 = 55 devices and the RMM manages 96, so (96 − 55) × $14 = $574 a month of tool cost reaches accounting without reaching the agreement, and its margin is $1,156, or 21.0 percent. B's gap is (50 − 44) × $10 = $60, and C, priced on neither driver, carries (46 − 40) × $10 + (60 − 50) × $14 = $200.
Across the book the PSA reports $4,160 of margin on $16,000 of MRR, or 26.0 percent, against a counted $3,326, or 20.8 percent. The $834 difference is tool cost the vendor bills carry and the agreements do not: $4,354 billed for the month against $3,520 allocated through the unit costs set in the PSA.
Restoring each agreement's 30.0 percent needs monthly revenue of its counted cost divided by 0.7: $4,344 ÷ 0.7 = $6,205.71 for A, 12.8 percent above its current $5,500; $3,990 ÷ 0.7 = $5,700.00 for B, 3.6 percent above; and $4,340 ÷ 0.7 = $6,200.00 for C, 24.0 percent above. For A the alternative is to change what the price counts, with a per-device component or a device allowance per user.
The sample is one invented year and forecasts nothing, and a client offered a changed pricing basis may leave. It shows that the PSA's margin and the counted margin can disagree about which agreement needs repricing, while every check that reads revenue alone passes.
MSP Revenue Operations Metrics
Revenue measures read the CRM and the PSA; measures of units and cost also need the RMM, the directory and accounting.
| Metric | Definition | Records it reads |
|---|---|---|
| MetricMRR sold | DefinitionRecurring value signed in the period, at signature | Records it readsCRM |
| MetricContracted MRR not yet billed | DefinitionSigned recurring value whose billing has not started | Records it readsCRM, PSA |
| MetricDays to first invoice | DefinitionDays from signature to the first recurring invoice | Records it readsCRM, PSA |
| MetricMRR billed | DefinitionRecurring value invoiced in the month, after amendments | Records it readsPSA |
| MetricGross MRR retention | DefinitionStarting MRR less reductions and cancellations, over starting MRR | Records it readsPSA |
| MetricExpansion | DefinitionMRR added to existing agreements, plus project fees sold to existing clients | Records it readsPSA, CRM |
| MetricEffective rate | DefinitionMRR billed over hours on the agreement | Records it readsPSA |
| MetricBilled-unit drift | DefinitionUnits in use less units billed, for the unit the agreement is priced on | Records it readsPSA, RMM or directory |
| MetricUnbilled-driver ratio | DefinitionDevices per billed user, or users per billed device, against the ratio priced | Records it readsPSA, RMM, directory |
| MetricAgreement margin | DefinitionMRR billed less hours at loaded cost and every user and device at vendor cost | Records it readsPSA, RMM, directory, accounting |
Agreement Margin Procedure
- List every system holding a record of a client, agreement, device, user, ticket, time entry, invoice or vendor bill, and the function that owns it.
- Record on every signed agreement its pricing basis, billed units, and the assumptions its price was built on: devices per user or users per device, and expected hours.
- Map every managed device in the RMM to its client's agreement, so alert tickets and device counts resolve to one contract.
- Classify each tool and service by its cost driver, per device, per user or fixed, and take each unit price from the vendor bills.
- Agree the loaded cost of a technician hour with finance, and revise it when payroll changes.
- Each month, compute agreement margin from MRR billed and hours in the PSA, devices in the RMM, users in the directory and the prices from step 4, and write it, with its gap to the PSA's margin, to the agreement's CRM record before each QBR and renewal.
- Verify on one month. The tool and licence costs allocated across all agreements, plus the provider's own devices and any committed minimum, equal the vendor bills; the hours allocated equal the hours on agreement tickets in the PSA; and MRR billed per agreement equals the invoice. A failed equality names the input that broke.
This model configured in one CRM beside a PSA, with the agreement and the site as records of their own, is the subject of the walkthrough of HubSpot for MSPs.
Costs and Returns for a Managed Service Provider
The firm publishing this page is a HubSpot Solutions Partner that implements CRM systems for MSPs and sells this work, an interest to weigh in what follows.
The model buys renewal prices set on the full cost of each agreement, including a changed pricing basis where a client no longer fits the unit it pays for. It costs a complete device-to-agreement mapping, a classification of every tool by cost driver, a loaded labour cost agreed with finance, and a monthly join that someone owns. The join is the weak point, since the finance team posting vendor bills gains nothing from allocating them to agreements that account management reads.
The case is strongest for an MSP with per-user or flat agreements across clients whose device estates differ, and with per-device tools in its stack, since each condition widens the gap the sample measures. It is weakest where every agreement is priced per device and no per-user services are resold, so the billed unit already carries the tool costs, and for a provider with a handful of agreements whose owner reads the RMM and the vendor bills directly.
Symptoms in Agreement Economics and Their Sources
Tool spend in accounting rises faster than MRR while every agreement's margin in the PSA holds steady. Devices were added under per-user and flat agreements, and their cost reached the vendor bills without reaching any agreement; step 6 allocates it.
Alert tickets bill through a client's default contract, or through none. Devices discovered at onboarding were never mapped to the agreement, so contract precedence fell through to the organisation's default; step 3 maps them.
Licence cost stays in the books after a client reduces its users. The licences were bought on an annual term that allowed reductions only in the seven days after they were added, while the agreement allowed monthly reductions, so the licence term belongs beside the agreement's terms at renewal.
Frequently Asked Questions
For a managed service provider, what does revenue operations mean?
It means governing the records that carry a client from enquiry through proposal, agreement, onboarding, monthly service and QBRs to renewal and expansion. That covers which system owns each record, what crosses each handoff, and how MRR and agreement margin are defined, so that every system agrees on one client's economics.
Does an MSP need revenue operations?
It needs the discipline where agreements are priced on one unit while cost follows several, where projects and resold licences sit beside recurring work, and where a sales team prices agreements that a service desk delivers. An owner who prices, delivers and bills every agreement personally holds the join in one head, and a monthly comparison of device and user counts against billed units may be enough.
RevOps and service delivery management: how do the two differ?
Service delivery management runs the service itself, and ISO/IEC 20000-1 specifies requirements for a service management system covering the planning, design, transition, delivery and improvement of services. Revenue operations governs the commercial record around that service: the price, the units billed, the renewal and the margin. The two meet at the agreement, where delivery produces the hours, tickets and service levels that revenue operations carries into the renewal price.
Limits of This Page and Its Evidence
This page covers the commercial record of an MSP from enquiry to renewal, and leaves out service level design, security operations, tool selection and revenue recognition. Product behaviour is as documented by Autotask, Datto RMM, ConnectWise, Microsoft, Salesforce and HubSpot in September 2026. ConnectWise's product documentation requires a partner sign-in, so its statements rest on public product pages, and the ISO/IEC 20000-1 abstract was read through an Internet Archive capture of iso.org dated 3 September 2026, because the site refuses automated requests.
The evidence has two limits. No published study located for this page measures whether an operating model of this kind changes margins or retention at MSPs, and the direct research reviewed in the firm's history of revenue operations is recent and small. The sample MSP is invented, so it shows that the two margins can disagree, not how often or by how much, and its tool and service costs are sample figures rather than vendor prices.
Revenue Operations for MSPs in Summary
An MSP prices a standing agreement on one unit, per user, per device or flat, and serves it at a cost that follows users, devices and hours together. Its recurring revenue passes from sold in the CRM to billed in the PSA to collected in accounting, while devices live in the RMM and tool prices arrive as vendor bills.
Revenue operations for MSPs assigns each record to one system, states what crosses the handoffs from sales to onboarding to the service desk to finance, and defines each metric by the records it reads. The renewal needs agreement margin with every unit counted, billed or not. On the sample data the PSA reports agreement A at 31.5 percent, above the 30.0 percent it was sold at, while counting its 96 devices puts it at 21.0 percent: an agreement the PSA's figures would have renewed unchanged.