Say an agreement covers 20 users and 20 devices, using the model's 20-seat client size for illustration. Under its per seat pricing rule, the billed count is the larger count, so 20 seats. At the model's $225 monthly seat fee, that is 20 times $225, or $4,500 a month.
That calculation assumes the agreement defines which users and devices are covered and when they are counted. Change that population or the counting date and the invoice can change. Write those rules beside the formula before asking billing to reproduce it.
A seat is the unit billed for the managed service. The MSP Outpost model defines its count as the larger of covered users or devices, not the sum. A device inventory and a billed seat count are related records; they are not interchangeable labels.
Put the Rule in the Agreement
The model favors a flat monthly fee with scope and exclusions stated plainly. For seat-based billing, that includes the unit, its price, and the method for updating the quantity. The person approving the agreement should be able to explain the calculation from those terms.
A starting definition to adapt is: The managed-service seat count is the greater of the covered-user count and covered-device count established under this agreement. The monthly managed-service fee is that seat count multiplied by the agreed seat rate, subject to the agreement's stated minimum and adjustment terms.
Then define the covered populations. Don't leave users and devices as words everyone is expected to interpret alike. List the categories included, categories charged separately, and responsibilities outside scope.
If the current agreement uses another method, treat the change as a commercial decision. Check the existing terms and agree the revised scope and counting rule before applying it. A new spreadsheet formula doesn't amend an agreement.
Separate People, Accounts, and Devices
For the user record, state which people count and how additions and departures are recognized. Decide how the agreement handles temporary staff, external workers, and people whose support is outside your responsibility. Give the client a way to identify the covered population without requiring them to interpret a raw directory export.
Keep service and shared accounts visible without automatically equating each account to a separate person. The counting rule should say how those records are treated. Licensing may still use a different unit, which needs its own reconciliation.
For devices, name the categories included in the managed-seat definition. Identify whether workstations, servers, shared terminals, or other equipment are included or separately priced. Those choices belong in the scope, not in a billing clerk's guess about an unfamiliar asset.
Record how you treat spares, retired equipment, and devices still under management during a transition. A powered-off asset isn't automatically outside your service responsibility. Use the agreed inclusion rule and retain the evidence behind its status.
Use the Larger Count Without Adding It Twice
The calculation can be expressed as seats equal the maximum of the covered-user count and the covered-device count. Maximum means whichever count is higher; when the counts are equal, use that same count once. Don't add the two populations together.
| Count Relationship | Seats Under the Model Rule | What Billing Needs |
|---|---|---|
| Covered users exceed covered devices | Covered-user count | Reconciled user and device records for the agreed period |
| Covered devices exceed covered users | Covered-device count | Reconciled device and user records for the agreed period |
| Counts are equal | Either equal count, used once | Evidence that both populations use the agreed scope |
| A category is outside the seat scope | Apply its separate agreed treatment | Recorded exclusion or separate charge, without duplicate inclusion |
In the illustrative account, both counts are 20, so the larger count remains 20. Adding them would incorrectly produce 40 seats under this definition. The $4,500 monthly calculation depends on the 20-seat result and the agreed $225 rate.
The model uses one endpoint per seat for its staffing and tool calculations because the seat definition already takes the larger count. That is a modeling assumption. It doesn't establish the actual relationship between people and devices at every client or replace your asset record.
Set the Counting Date and Change Method
Write down the point in the billing process at which the covered populations are measured. State how approved additions, departures, and corrections affect the current or following invoice. Use the method agreed with the client rather than selecting whichever snapshot gives the preferred fee.
Keep a dated source record for the user population and the device population. Have the service owner confirm coverage before billing applies the formula. If information is missing, assign an owner to resolve it instead of silently changing the scope.
Apply the same method when the count falls. Identify the date service responsibility ends and any separate supplier commitments that remain. A managed-service count change doesn't itself establish whether a resold license commitment can change on the same date.
Tas Gray, in a practitioner commercial-design account, describes choosing monthly upstream licensing commitments to support flexibility in his per-user service. That is his arrangement, not a rule for every license. Check your own supplier terms alongside the client agreement.
Give Billing a Reconciliation It Can Show
Keep the previous quantity, additions, removals, current user count, current device count, and billed result together. Link changes to an authorized request or a verified coverage record. The invoice explanation should lead back to that reconciliation.
I'd show the client the relevant change in plain language: the populations used, the larger count, the seat rate, and the effective period. Keep unrelated product lines separate. That lets a disputed count be checked without reopening the whole pricing structure.
When the client disagrees, identify whether the issue is an asset record, a covered person, an effective date, or the agreed definition itself. Correct the record or resolve the commercial question with the responsible owner. Avoid applying an unexplained credit that leaves the same disagreement embedded in the next invoice.
A rough estimate can start a discussion. It cannot reconcile an invoice. Preserve the approved source records and the calculation so another person can reproduce the charge.
Assign the Rule Before the Next Invoice
The account owner agrees the definition and explains changes to the client. The service owner maintains the coverage records. Billing applies the count and checks the reconciliation, while the person approving exceptions records the decision and its effect on future invoices.
Use a recent account to test the process. Rebuild the covered-user and covered-device counts for the agreed period, take the larger, and multiply it by the seat rate. Resolve the first difference between that result and the invoice before extending the method across the book.
A clear definition won't guarantee that no invoice is challenged. It gives both sides the same calculation to inspect, with an agreed scope and an effective date. That is the part your MSP can put in place before the bill goes out.
mspoutpost.com/articles/per-seat-pricing-needs-a-definition-your-invoice-can-defend
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.