Strong technology rarely sells itself
Plenty of MSPs are built on genuinely excellent delivery and still cannot get into the AI conversation. The constraint is not the technology.
There is a comfortable belief in this industry that if the technical work is good enough, the commercial results follow. It is comfortable because it is half true, and because it rewards the thing most MSP owners are naturally best at.
It held up reasonably well when the buyer was technical. It does not hold up now. A business can be excellent at delivery and still never be in the room where the decision is made.
If you have watched a customer commission an AI programme you could have delivered better than whoever won it, you have already met this problem. It was not decided on capability. It was decided before capability was discussed.
One is built. One is usually improvised.
Deliberately built, over years
Certifications, tooling, process, escalation paths, a service desk that works. Real investment, made consciously, reviewed regularly. Most MSPs can describe this half of their business in detail and are justifiably proud of it.
Strong, and getting stronger.
Assembled from what worked
Positioning that emerged rather than was chosen. Offers described differently by every person who sells them. Pricing set by what the last customer accepted. A route to market that is mostly referral and renewal.
Improvised, and rarely reviewed.
Neither half is optional. Only one of them usually got built on purpose.
The constraint is rarely the technology. It is the model around it.
When growth stalls, the instinct is to add capability. Another certification, another vendor badge, another workload in the portfolio. It feels productive, it is measurable, and it is the thing the business already knows how to do.
It rarely moves the number. If the market cannot say what you are for, if your offers are described differently in every conversation, or if your pricing reflects what the last customer would accept rather than what the change is worth — no amount of additional capability fixes that. You are strengthening the half that was never the problem.
Four things a commercial model needs before it scales.
None of them is marketing. All of them are decisions the leadership team has to make and then hold.
A position you actually chose
Sharp enough to exclude somebody
- Most MSP positioning describes the whole market and therefore says nothing. If it does not rule anyone out, it is not a position — it is a description.
A route to the executive conversation
Not just to the IT manager
- A repeatable way of reaching the people who decide, in the installed base as much as in new accounts. That is where the AI decisions are being made.
Offers with a shape and a price
That somebody else can sell
- Defined scope, known price, consistent delivery pattern. If every engagement is scoped from scratch, the business cannot grow past the people who can scope it.
Proof a CFO will accept
A case, not a demonstration
- What changes in the business, what it is worth, and over what period. Technical proof convinces the technical buyer, who is no longer the one signing.
Four things worth remembering.
- Excellent delivery is necessary and not sufficient. It has never been sufficient; it just used to be closer.
- Growth usually stalls in the commercial model, not the technology — and the commercial half is the one that was never built deliberately.
- Adding capability when the commercial model is the constraint strengthens the half that was already strong.
- A model that scales needs a chosen position, a route to the executive conversation, offers with a price, and proof a CFO will accept.
The same argument applies to software vendors, for the same reasons — if that is you, start here instead.
Which half of your business is actually constrained?
A Growth Review is a structured conversation with you and your leadership team: where your AI practice is constrained, whether it is the technical half or the commercial one, and what removing that constraint is worth. Ninety minutes, no cost, and an honest answer — including when the answer is that you do not need us.
Win the business case before you win the build.