A growing contract can still dilute the business
A recurring agreement creates predictability only when the obligations attached to it are understood. Extra users, poorly documented systems, repeated exceptions and informal promises can expand the delivery commitment without expanding the fee. Growth then increases workload faster than economic contribution.
The Service Leadership announcement published in June 2026 reports strong 2025 performance, including at least 19% adjusted EBITDA for its best-in-class IT solution provider cohort. That is a useful signal of what a defined group achieved. It is not a universal MSP margin, a gross-margin target or evidence that adding revenue automatically produces the same result.
Source context: ConnectWise / Service Leadership. See source dates and limitations below.
Reconcile the measures before comparing them
Monthly recurring revenue describes a revenue pattern. Service gross margin deducts the costs classified as direct service delivery. Customer contribution can include additional account-specific costs such as unusually intensive account management. Operating profit then reflects the wider business cost base. Adjusted EBITDA introduces its own exclusions and adjustments. Comparing these labels without their definitions creates false precision.
For an internal review, write down the allocation policy and use it consistently. Decide how delivery labour, shared licences, onboarding, after-hours cover and service management are assigned. An imperfect but stable definition that supports operational decisions is more useful than a flattering percentage that changes with the allocation method.
Follow the work behind the invoice
Take an illustrative customer paying £5,000 per month. If £4,500 is consumed by allocated delivery labour, licences and agreed account-level support costs, £500 remains before the rest of the firm’s overheads. That 10% contribution is not EBITDA. A further £400 of recurring exception work would leave only £100 on the same basis.
The appropriate response is not automatically a price increase. The account may need a defined remediation project, a revised service boundary, standardised technology or a different support model. Some exceptions are deliberately funded investments in a valuable relationship. Make that choice visible instead of allowing accidental subsidy.
Choose the next unit of growth
Review acquisition, expansion and retention separately. New customers carry selling and onboarding costs. Expansion can be attractive where delivery is repeatable, but a new service may introduce another operating model. Retention protects recurring revenue, although retaining an unsustainable contract without changing its scope can preserve the wrong economics.
A practical management review starts with accounts that combine low contribution and high service effort. Then examine which services produce repeatable delivery and which customer characteristics predict exceptions. Use that evidence to refine the ideal customer, onboarding policy and sales qualification. The aim is growth that the operating model can absorb.
Make the management review explain change
A useful monthly review connects a change in contribution to something the team can act on. Separate customer additions, departures, price changes, service expansion and changes in delivery effort. If revenue rises while contribution falls, the explanation could be onboarding, an altered customer mix or recurring exceptions. Each requires a different response. A single margin percentage cannot reveal which one occurred.
For new agreements, record the expected onboarding effort and compare it with the work performed. Decide which setup work is charged, which is an explicit investment and which belongs in a remediation project. The distinction helps sales and delivery avoid treating an unusually difficult start as the normal cost of every future customer.
For established accounts, look for persistent scope drift. A new site, an unsupported application or a changed working pattern can alter delivery demand without a formal request to change the contract. Review the service boundary with the customer and explain the operational consequence. Good scope management should make the agreement clearer for both parties, not turn every interaction into a dispute.
Use this review to select one improvement with an accountable owner and a date to inspect the result. That might be better qualification, a revised onboarding checklist or removal of a recurring technical exception. Measure the contribution and service effect together so that an apparent cost improvement does not conceal deteriorating customer experience.
Implications for technology vendors
A vendor proposition becomes more credible when it explains implementation effort, continuing support and the customer outcome an MSP can sell. A product discount addresses only one part of the partner’s economics. Evidence of a manageable service burden can be more useful than a large theoretical margin calculated before labour and exceptions.
A framework for the next decision
| Measure | What it helps explain | What it does not prove |
|---|---|---|
| Recurring revenue | Continuity of contracted billing | Quality of the underlying contribution |
| Service gross margin | Direct delivery economics | Profit after the whole cost base |
| Customer contribution | Account-level economics on a declared basis | Comparable EBITDA across businesses |
| Retention and concentration | Exposure to lost or dominant accounts | That every retained contract is profitable |
This is commercial analysis, not accountancy advice or a profitability benchmark. The worked customer is illustrative. The cited release reports a defined cohort and prior-year performance; its full methodology should be consulted before direct comparisons.
Sources & further reading
Explore the MSP programme
Connect practical analysis with peer exchange, relevant events and commercial insight.