MSP Agreement Profitability: Measure It With PSA Data

Why agreement profitability is hard to see

Most MSPs know which clients feel profitable. Fewer can prove it from the data.

A client may pay a large monthly agreement and still drain margin through noisy endpoints, unmanaged expectations, recurring escalations, underpriced onsite work, or missed billing adjustments. Another client may look small on revenue but generate clean margin because ticket volume is predictable and the environment is well standardized.

That is why MSP agreement profitability should not be measured from agreement revenue alone. It requires a joined view of service desk work, billing, vendors, and client commitments.

The goal is not to create a finance spreadsheet that nobody uses. The goal is to give owners, service managers, and dispatchers a reliable operating view: which agreements are healthy, which are drifting, and what action would improve the margin.

Start with a simple profitability model

At the agreement level, the basic model is straightforward:

Agreement revenue minus direct service cost minus tool and vendor cost equals gross profit.

Gross profit divided by agreement revenue gives the gross margin percentage.

The difficulty is deciding what belongs in each category and making sure the data is complete enough to trust.

For most MSPs, the agreement-level view should include:

• Monthly recurring agreement revenue
• Covered labor hours from service tickets
• Effective labor cost by technician or role
• Escalation and after-hours premiums
• Tooling costs tied to users, devices, mailboxes, backups, security, or licensing
• Vendor costs and pass-through items
• Projects or change requests incorrectly absorbed into the agreement
• Billing leakage from missing additions, stale counts, or unbilled services

You do not need perfect cost accounting on day one. You do need a consistent model that improves over time. A directionally correct profitability view reviewed every month is more useful than a perfect quarterly report that arrives too late to change behavior.

Use service desk data to measure labor consumption

Labor is usually the largest variable in MSP agreement profitability. The service desk shows how much of the agreement is being consumed and why.

The first step is mapping tickets to the right client, agreement, work type, and service category. If tickets are inconsistently classified, margin reporting becomes guesswork. Password resets, endpoint issues, security alerts, vendor coordination, onsite work, and after-hours incidents should not all land in one generic support bucket.

For each agreement, track these service desk metrics:

• Total ticket count by month
• Total hours and average minutes per ticket
• Hours per user, endpoint, server, or site
• Reactive versus proactive work
• First-touch resolution rate
• Escalation rate
• Reopened tickets
• After-hours and emergency work
• Onsite visits
• Tickets caused by the same asset, vendor, or recurring issue

A client with high ticket count but low average handling time may need better self-service, training, or automation. A client with low ticket count but high escalated hours may have complex infrastructure or poor documentation. Those are different margin problems.

This is where classification quality matters. Tools like autonomous tickets can help normalize intake, routing, and summaries so profitability reporting is based on cleaner operational data instead of whatever a busy dispatcher had time to enter.

Convert ticket time into cost

Ticket hours only become profitability data when they are translated into cost.

Many MSPs start with a blended loaded labor rate. For example, if the service team costs $85 per productive hour, multiply agreement-covered ticket hours by $85. This gives a useful first view.

A more mature model uses labor cost by role or technician level:

• Tier 1 help desk hours
• Tier 2 or escalation hours
• Project engineer hours absorbed into support
• Service manager or vCIO time included in the agreement
• After-hours support at a higher cost rate

This helps explain why two clients with the same number of support hours may have very different margins. Ten hours of Tier 1 work is not the same as ten hours of senior engineering time.

It also helps service managers spot operational improvements. If a client consumes too much senior labor for routine work, the issue may be documentation, training, access rights, standardization, or poor triage. If senior labor is truly required, the agreement price or scope may need to change.

Tie billing data to what is actually being supported

The second half of MSP agreement profitability is billing accuracy. Even well-priced agreements lose margin when the client footprint grows but billing does not keep up.

Common leakage points include:

• New users not added to the agreement
• Retired users still billed by vendors but not charged to the client
• Security tools deployed but not included on the invoice
• Backup, EDR, email security, or SaaS licenses out of sync
• Agreement quantities updated manually and inconsistently
• Vendor price increases not reflected in client billing
• Pass-through items treated as included support

A monthly agreement profitability review should compare what is billed against what is present in the environment and what appears on vendor invoices. Corei's billing and vendor auditing is built for this kind of mismatch detection, especially where small per-seat differences compound across many clients.

For example, a client may be billed for 82 managed users while identity data shows 91 active users and the security vendor bills for 94 seats. That is not just a billing cleanup issue. It changes the real margin of the agreement.

Separate covered, billable, and out-of-scope work

Profitability analysis depends on knowing which work should be included in the agreement and which work should be billed separately.

Service teams often absorb small out-of-scope tasks because it is faster than stopping to clarify billing. Over time, that behavior trains clients to expect project work, vendor management, moves, changes, application consulting, and onsite labor inside the fixed fee.

Your PSA data should make these distinctions visible:

• Covered support under the agreement
• Billable support outside the agreement
• Project work
• Procurement or licensing work
• Vendor-caused incidents
• Client training or adoption issues
• Security incident response
• Warranty or hardware replacement work

The point is not to argue over every 15-minute task. The point is to see patterns. If a client consistently receives 12 extra hours per month outside the agreed scope, you have a pricing, scope, or expectation issue.

Clear classification also helps dispatchers make better real-time decisions. When the ticket shows the client agreement, scope, recent ticket history, and known commitments in one place, it is easier to route work correctly and avoid accidental margin erosion. Corei's client command center is designed to give that context without making the dispatcher open five screens.

Build dashboards that answer operating questions

Agreement profitability reporting should not be limited to a static monthly finance export. Service leaders need dashboards that connect profitability to the behavior causing it.

Useful agreement views include:

• Gross margin by client and agreement
• Margin trend over 3, 6, and 12 months
• Labor hours versus included or expected hours
• Ticket volume per supported user or endpoint
• Top clients by unbilled labor
• Top clients by escalation hours
• Tool cost variance by client
• Agreements below target margin
• Clients with increasing support consumption before renewal

The best dashboards let you move from the number to the reason. If a client dropped from 52 percent to 36 percent margin, the next question is why. Was it more tickets, higher-level labor, stale billing counts, vendor cost increases, an incident, or project work being handled as support?

Corei's dashboards and reports are intended to connect those layers so a service manager can act on the variance instead of exporting data and rebuilding the story manually.

Review profitability by cohort, not just by client

Client-level analysis is essential, but cohorts show whether the underlying offer is healthy.

Group agreements by attributes such as:

• Per-user agreements
• Per-device agreements
• Co-managed IT
• Security bundle tier
• Industry vertical
• Client size
• Onsite requirement
• Legacy versus current pricing model
• Standardized versus non-standardized stack

This helps answer strategic questions. Are smaller clients below target margin because of fixed overhead? Are legacy agreements underpriced compared with current packaging? Are clients with certain line-of-business applications consuming more senior engineering time? Does one security bundle carry vendor costs that have outpaced pricing?

Cohort reporting also makes renewals easier. Instead of treating each renewal as a negotiation from scratch, you can show how that client compares with similar clients and what needs to change to keep service sustainable.

Use profitability data in QBRs and renewals

Agreement profitability data is not only for internal use. It can support better client conversations when framed properly.

Clients do not need to see your margin calculations. They do benefit from understanding service patterns, recurring issues, aging equipment, user training needs, and risk areas that drive support volume.

For example, a QBR can show that 28 percent of tickets came from the same aging workstation group, or that after-hours incidents rose after a new application rollout. That creates a business case for standardization, replacement, training, or scope changes.

Corei's QBR insights can help assemble client review material from operational data, so profitability improvements are tied to service outcomes rather than presented as a price increase with no context.

Watch for common measurement mistakes

Several mistakes can make agreement profitability reporting misleading.

First, do not ignore missing time entries. If technicians routinely under-enter time, profitable clients may only look profitable because labor is invisible. Improve time capture before making major pricing decisions.

Second, do not treat all labor as equal. A flat average rate is acceptable to start, but escalation-heavy clients need to be identified.

Third, do not evaluate one unusual month in isolation. Security incidents, migrations, onboarding, and vendor outages can distort results. Use rolling trends and annotate major events.

Fourth, do not separate profitability from service quality. A client can be profitable because they are underserved. Include SLA performance, backlog, CSAT, and recurring issue data so margin does not become the only operating goal.

Finally, do not let reporting become a finance-only exercise. Dispatchers, service managers, account managers, and owners all influence agreement profitability. The data should be visible enough to change daily decisions.

Practical takeaway

To measure MSP agreement profitability, start with a repeatable monthly process:

1. Pull agreement revenue by client.
2. Match all covered ticket time to the agreement.
3. Convert labor time into cost using a blended or role-based rate.
4. Add tool, license, and vendor costs by client.
5. Compare billed quantities against supported users, devices, and vendor invoices.
6. Separate covered work from billable or out-of-scope work.
7. Review margin trends and the operational drivers behind them.
8. Decide one corrective action per low-margin agreement.

Corrective actions may include a billing cleanup, scope clarification, automation, documentation work, user training, standardization project, vendor review, or renewal price adjustment.

If you already run ConnectWise Manage and want better profitability visibility without a rip-and-replace project, Corei can run on top of it through the ConnectWise integration. Many MSPs start by improving reporting, ticket intelligence, and billing audit workflows before deciding whether to change the system of record.

The most important step is to stop treating agreement profitability as an annual pricing exercise. It is an operating metric. When service desk and billing data are connected, margin problems become visible early enough to fix them.