Mostly on whether your product makes their security service stronger without adding work. A UK MSSP looks at whether it feeds the tools its analysts already use, whether it runs across many customers at once, whether it gives the MSSP something new to sell, how it bills, and whether the vendor will be there when an incident or a deal needs help. Good detection on its own is rarely enough. A vendor that makes the MSSP's service stronger and simpler to run usually is.
By John Bates, founder of AXQ
Over five years on the distributor side, security programmes included, I sat in a lot of meetings where a vendor pitched a managed security provider. The ones that went well started with the provider's analysts and customers, not with the product.
Here is what MSSPs tend to weigh. Every provider is different, so treat this as a starting point and ask them what matters most.
Step by step
Five questions an MSSP asks.
Does it make our analysts' day better or worse?
An MSSP's biggest cost is analyst time. Another console, another stream of alerts or another login makes the service harder to run, so the first question is whether your product feeds the tools their security operations centre already uses, and whether it cuts noise rather than adding to it.
If it needs its own screen, say why it earns one, and show what an analyst does with it in a normal shift.
Can we run it across all our customers?
MSSPs look after many customers at once. They want one place to set policy, see every customer, investigate and report, with each customer's data kept separate.
A product built for one in-house security team can be strong and still be hard for an MSSP to run at scale. If yours is built for many customers, lead with it.
Does it give us something new to sell?
An MSSP adds a vendor when it helps them offer a service they could not offer before, or makes an existing one clearly better: faster detection, wider coverage, clearer reporting for a board, or evidence for an audit.
A product that only replaces something they already run is a harder conversation. Show the service it makes possible and which of their customers would buy it.
How does it bill, and through whom?
Most managed security is sold monthly, so MSSPs look for billing that moves 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 MSSP avoids carrying the gap. For the distributor question, see do you need a UK distributor.
Will the vendor be there when it matters?
Security has bad days. MSSPs want to know who answers during an incident, whether technical support covers UK hours, where customer data is held, and the rule on who owns the customer, written down before anything is registered.
What happens on the first bad day 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 the threats and questions their customers already bring them, not from your feature list.
- Showing how an analyst uses your product across several customers in a normal shift.
- Being clear, in writing, on data handling, ordering, billing and who owns the customer.
- Offering help on a first named customer, including a joint look at the results.
What tends to put them off:
- Detection claims with no story about the service around them.
- Another console that does not connect to the tools they already run.
- Billing terms that do not match how they sell.
- Any sign you will sell direct to their customers behind them.
Most of this is about trust more than terms. An MSSP puts its name on the security of every customer it runs your product for, so it is choosing a vendor it can stand behind when something goes wrong.
What usually goes wrong
Three patterns come up again and again.
Leading with detection, not the service
The vendor shows what it catches to people thinking about analyst time, margin and their customers. Start from the service the MSSP could sell, and the detection story follows.
Signing too many at once
A long list of providers 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.
Treating an MSSP like a reseller
An MSSP runs your product every day; a reseller sells it and moves on. Terms, training and support built for resale leave the MSSP doing the hard part alone. See how UK MSPs choose software vendors.
The short version
Less noise, many customers, a new service, monthly billing, a person.
UK MSSPs choose security vendors that make their own service stronger and easier to run. Show how you fit the tools their analysts already use, how you work across many customers, what new service you make possible, how they order and bill, and who on your side will be there on the first bad day. If you are still deciding which partner type to start with, 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.