Contract value in it support and the per-user pricing trap

3 days ago
3 min read

Introduction

Managed IT support is usually priced per user per month, which is easy to quote and easy for a client to compare. It is also a poor description of the cost, because two businesses with the same headcount can generate completely different volumes of work depending on their systems, their age of hardware and how their staff behave.

The result is a book where some contracts are profitable, some are quietly subsidised, and nobody knows which until somebody looks at ticket volumes against contract value.

Raising average contract value is partly about pricing structure and mostly about which services sit inside the agreement. Both are within your control.

1. Contract value in it support should reflect complexity, not just headcount

Users are a proxy, and a rough one.

Measure tickets per client against contract value

Monthly ticket count and time spent, divided by what the client pays. The variation across a book is usually dramatic. Run it for a quarter rather than a month.

Load the price for genuine complexity

Legacy systems, multiple sites, unsupported software, unusual applications. These generate work and should carry a premium rather than an apology. Say what the premium is for so it does not read as arbitrary.

2. Move from break-fix to contracted

Reactive work is the worst business in the trade.

Price the contract against predictable cost

A monthly agreement smooths revenue and lets you plan capacity. Break-fix means feast, famine and no predictability for either side. Clients prefer the certainty too.

Make the contract cover prevention

Patching, monitoring, backup verification and hardware refresh reduce the tickets you have to absorb. The incentives align once the contract is monthly. Fewer tickets becomes good for both of you.

3. Build the security and compliance lines properly

This is where contract value has genuinely moved.

Price security as its own service

Endpoint protection, email filtering, multi-factor rollout, awareness training, backup testing. These are distinct deliverables, not favours. Quote them as line items with their own value.

Charge for the documentation clients need

Asset registers, policies and evidence for insurance or client audits. Businesses increasingly must have these and cannot produce them alone. Insurers and larger customers now ask for them.

4. Get the projects out of the contract

Project work absorbed into a support agreement destroys the margin.

Define what the contract excludes

Migrations, office moves, new installs, upgrades. State these as project work at the outset. Put the list in the agreement itself.

Quote projects separately and properly

A migration is weeks of planned work. Bundling it into a monthly fee means doing it for nothing. Scope it, price it and schedule it like any other project.

5. Review the book annually and act

Contracts drift out of alignment with reality every year.

Reprice the loss-making contracts

Some clients are consuming several times what they pay. Present the ticket data and adjust, or part company. The data makes the conversation factual rather than awkward.

Watch client growth and shrinkage

Headcount changes and nobody tells you. Check the licence counts against the contract. An annual true-up on user numbers recovers revenue you are already delivering. Put the review date in the contract.

Conclusion

Measure monthly tickets and time spent against contract value for every client, because per-user pricing hides the fact that some agreements consume several times what they pay while others are highly profitable.

Load the price for legacy systems, multiple sites and unsupported software rather than absorbing them, move clients from break-fix to monthly agreements that cover prevention so the incentives align, price security and compliance documentation as the distinct deliverables they now are, define clearly what the contract excludes and quote migrations and installs as separate projects, and review the whole book annually — repricing the loss-makers and truing up user numbers that changed without anybody telling you.