Assume the US model's 20 covered seats at $225 a seat each month. Multiply 20 x $225 and the managed-service fee is $4,500 a month. Put that calculation beside the scope in your managed services agreement. If the covered environment or service commitment changes, this sum alone can't set the fee.
A flat fee is a recurring price for agreed service, rather than a balance of prepaid hours. The model's B4 calls for plain wording about what it includes and what costs extra. I'd put that wording on a scope page the client and service desk can both use after signing.
Make the Billing Unit Clear
A covered seat is the unit that prices the managed service. The model takes the greater of covered users or devices, rather than adding them together. Point to the maintained coverage record and state how changes to that record are approved.
The example's calculation prices the managed-service line. It doesn't price separately resold licenses or equipment. Show separate recurring product charges and the resulting recurring total before asking the client to accept the price.
Keep the service description attached to that basis. Say which environment the team supports and what work the recurring fee funds. Everything IT isn't a description the technician can use to decide whether a request fits.
Don't turn the page into a list of tool logos. Explain the work and the limits needed to make it precise. The client needs to understand the service action, rather than infer it from a product name.
Use the Page to Answer Actual Scope Questions
Populate the proposed page structure below from the service you've costed and agreed. Have the named owners check it before it goes to the client. The fields identify decisions to write down, rather than declaring a universal bundle for every MSP.
| Scope Page Field | What to Write | Who Checks It |
|---|---|---|
| Recurring Price | The managed-service calculation, separate recurring charges, and total. | Finance lead |
| Covered Environment | The supported systems and reference to the maintained coverage record. | Account owner |
| Included Work | The actions funded by the recurring fee and the relevant limits. | Service owner |
| Support Availability | The actual support window and request route, with the response commitment distinguished from restoration. | Service desk lead |
| Separate Work | The work that needs another scope and approved price. | Project lead |
| Client Cooperation | The access or decisions the service requires from the client. | Account owner |
| Extra-Spend Approval | The authorized client contact and how approval is recorded. | Finance lead |
| Version and Questions | The agreed version and the person who resolves conflicting service descriptions. | Account owner |
Use a reference to a detailed estate record when the full inventory would overwhelm the page. Check that the desk can find the current record from that reference. A short summary doesn't help if it points to a list nobody maintains.
Write each inclusion as work your team can identify. A hypothetical monitoring description might say the team monitors covered endpoints and handles alerts within the agreed scope. It still needs the actual coverage and handling commitment before it belongs in an agreement.
Have the service owner check that the description matches delivery. If sales and the desk interpret the wording differently, settle that difference now. Don't leave the client to choose between competing explanations after a fault.
Explain How a Separate Request Gets Priced
An exclusion needs a route to an answer. If a requested migration falls into project work, have the project lead establish the scope before promising delivery. Give the desk a named person to ask when the classification is unclear.
The US model's blended project selling rate is $185 an hour. For a quote using that basis, the labor calculation is agreed billable hours x $185. The rate doesn't tell you the hours, and the quote still needs a defined result.
Keep that labor line distinguishable from separately quoted products or third-party work. Show the amount or agreed pricing method before the client authorizes it. Record how a later scope change receives approval instead of treating the first estimate as permission for every extra charge.
A rule of thumb can't authorize an invoice. Finance needs the accepted price and scope with the authorized contact's decision. Send an incomplete record back to the account owner rather than treating a remembered conversation as settled billing.
Let the Technician Route the Commercial Decision
A tech shouldn't be negotiating price while diagnosing a fault. Let them identify the work and send the scope question to the service owner. Have the account owner explain the proposed treatment to the client, including the price where extra work is needed.
Erick Simpson recommends checking an unusual request for the expertise it needs and the support work it creates. He suggests exception approval and considering a suitable partner. Keep that as his practitioner advice, rather than permission to accept any unfamiliar system for an extra fee.
If the exception is approved, state whether it is temporary or continuing. Put its limits where the desk can find them. An agreement to implement something doesn't establish the ongoing support commitment for it.
For an urgent request, follow the authorization route actually agreed with that client. Confirm what action is permitted and how the charge will be handled. Don't let urgency write an extra service promise into a ticket note.
Rebuild the Invoice and Test the Scope
Have finance calculate the recurring invoice from the scope page. In the opening example, the managed-service calculation remains $4,500. A combined total with separately priced licenses needs their agreed amounts before anyone can state the full recurring bill.
Keep that check numerical. The finance lead should be able to trace each recurring line to its basis and approved treatment. An explanation that only the salesperson can reproduce isn't ready for the billing handoff.
Then test the wording against an actual included request and a request that required separate approval. Ask the desk to locate the answer using the written record. If the answer depends on a private conversation, have the account owner confirm and record the agreed meaning.
Ask the client contact how they would request work outside the fee. That checks whether the approval route is usable; it doesn't guarantee an end to scope disputes. Correct the unclear instruction while the relevant people are reviewing it.
Have the people responsible for the agreement check the summary alongside the full terms. Resolve conflicting descriptions before issuing it. The page should communicate the actual commitment rather than create a second version of it.
Update the Description When the Service Changes
When an approved change affects recurring work, update the description and billing record together. Have the account owner explain the change through the agreed client process. Don't quietly convert an exclusion into another recurring line.
Keep the accepted version available to the desk. Record who resolves questions when another service record disagrees with it. Otherwise the same request can receive a different answer depending on which document the technician happens to open.
Start with the next agreement your team will use. Have delivery check every service promise and finance rebuild the price from its stated basis. Take the page to the client when both teams can reach the same work and billing decision from the written record.
mspoutpost.com/articles/managed-services-agreement-make-the-flat-fee-clear
Written by Graham Whitfield
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.