Mostly on whether your product makes their managed service easier to run and easier to sell. A UK MSP looks at how it fits the stack it already supports, whether it can manage many customers from one place, how it bills, whether there is room to build a service around it, and whether the vendor will turn up when a deal or a problem needs help. A strong product on its own is rarely enough. A vendor that makes the MSP's service simpler usually is.
By John Bates, founder of AXQ
Over five years on the distributor side I sat in a lot of meetings where a software vendor pitched a managed service provider. The ones that went well rarely led with features. They led with how the product would fit the way the MSP already runs its customers.
Here is what MSPs tend to weigh. Every MSP is different, so treat this as a starting point and ask them what matters most.
Step by step
Five questions an MSP asks.
Does it fit the stack we already run?
An MSP makes money by running many customers the same way. Every new vendor means new training, new tooling and new support calls, so the first question is whether your product fits alongside the platforms and tools it already manages.
If your product replaces something they already run, say so plainly and show what the switch costs them in time. They will be working it out anyway.
Can we manage many customers from one place?
MSPs want one console where they can see every customer, deploy to them, report on them and fix problems without logging in and out of separate accounts.
A product built for a single in-house IT team can be good and still be hard for an MSP to run at scale. If yours has a multi-customer view, lead with it.
How does it bill, and through whom?
Most MSPs sell monthly services, so they look for monthly billing that can move up and down with each customer, and an ordering route they already use, often a distributor or a cloud marketplace.
Long upfront commitments sit awkwardly with monthly contracts. If you need to sell differently, explain how the MSP avoids carrying the gap. For the distributor question, see do you need a UK distributor.
Can we build a service around it?
Margin and recurring revenue matter, but so does room for the MSP's own work: onboarding, monitoring, reporting and support it can charge for as part of its service.
A product that leaves nothing for the MSP to do is a resale, not a managed service. Show where their service sits around yours.
Will the vendor turn up?
MSPs have usually been signed by vendors who then disappeared. They want a named person, technical help in UK hours, help on the first deals and a clear rule on who owns the customer, written down before anything is registered.
What happens after signing is what they remember. See what the first 30 days with a new UK partner should look like.
The first conversation
What helps, and what puts them off.
What usually helps:
- Starting from a problem their customers already have, not from your feature list.
- Showing how your product is run day to day across many customers.
- Being clear, in writing, on how they order, how they are billed and who owns the customer.
- Offering help on the first named customer, not a generic enablement plan.
What tends to put them off:
- A product demo with no story about the service around it.
- Billing terms that do not match how they sell.
- A partner portal and no person.
- Any sign you will sell direct to their customers behind them.
Most of this is about trust more than terms. An MSP puts its own name on every customer it runs your product for, so it is choosing a vendor it can stand behind.
What usually goes wrong
Three patterns come up again and again.
Pitching the product, not the service
The vendor shows features to people who are thinking about margin, workload and their customers. Start from the service the MSP could sell, and the features follow.
Signing too many at once
A long list of MSPs signs, none gets real attention, and none sells. Start with a few chosen for fit. See how to recruit your first channel partners in the UK.
Leaving them alone after signing
The agreement is signed and the vendor moves on to the next one. See the partner programme that signs but doesn't sell.
The short version
Fit, one console, monthly billing, a service, a person.
UK MSPs choose vendors that make their own service easier to run and sell. Show how you fit what they already manage, how they bill and order, where their service sits, and who on your side will help with the first customers. If you are still deciding whether MSPs are the right first partner type, try the partner type picker, and for the wider order of decisions, read UK market entry strategy for US software companies.
John Bates, founder of AXQ. Five years at TD SYNNEX (via IQBlade, acquired), leading partner go-to-market programmes for AWS, Cisco, Google, Microsoft and Nvidia across EMEA.