A useful account plan starts with what can be observed. Review the services in scope, open risks, recurring support themes, planned business changes and recommendations that the client has previously deferred. Compare that record with the standard your MSP believes the client needs. The difference is the opportunity map.
The map should distinguish between urgent remediation, sensible improvement and optional optimisation. That prevents every gap from being presented with the same weight. It also lets an account manager explain why a recommendation matters now, what happens if it waits and which decision is needed from the client.
- Repeated tickets that point to an underlying configuration, capacity or training problem.
- New sites, employees, applications or regulatory obligations that change the client’s requirements.
- Services delivered outside the agreement because the current scope no longer reflects reality.
- Security, continuity or lifecycle recommendations that remain open without a recorded decision.
- Different standards across similar client environments, where one account has fallen behind the MSP’s current baseline.
Expansion becomes inconsistent when responsibility is shared vaguely between sales, service and technical teams. Name one commercial owner for each account. That person does not need to produce every technical recommendation, but they should maintain the account plan, organise review meetings and make sure agreed actions move forward.
Support the owner with a simple cadence:
- Review account evidence before each client meeting.
- Select a small number of recommendations that deserve discussion.
- Record the client’s decision, timing and reason.
- Assign the next action to a named person.
- Revisit deferred items when the agreed trigger arrives.
Clients are more likely to engage when recommendations form a coherent sequence. Group work into immediate risks, near-term capability improvements and longer-term plans. Explain the outcome of each stage in plain business language, including any operational disruption or dependency.
Avoid combining every possible improvement into one oversized proposal. A staged roadmap helps the client prioritise, protects the credibility of the advice and creates a visible route from discussion to delivery. Over time, this also gives the MSP a clearer expansion pipeline based on documented needs rather than optimistic assumptions.
Reviewing won and lost expansion work improves the method. Record which evidence opened the conversation, which objection delayed it and whether the delivered outcome matched the original case. Feed those lessons back into account plans and future reviews.
