In this article 8 sections
If you keep losing pitches to MSPs charging less than you, your prospect probably can’t tell you apart. They’re picking on price because price is the only visible difference.
Why the price gap is rarely what you’re losing on
When two MSP proposals land on a finance director’s desk and one is 30% cheaper, the cheaper one wins by default. That’s the only outcome where the FD doesn’t have to do work to justify the spend. Your 30% is invisible because the value sitting behind it is invisible.
The prospect is making a risk decision dressed up as a price decision. They use price as a rough proxy because they’ve got nothing better to compare with.
Their underlying question is: what happens to my Friday afternoon when this MSP screws something up? They want to feel that risk is low.
This is why “we’re more thorough” or “we have better engineers” doesn’t move the needle. Every MSP says that. The prospect mentally averages all the claims and falls back to price as the tiebreaker.
The play is to give them something else to compare. Specifically: the things that the cheaper MSP almost certainly can’t show, but a prospect would want before signing a 3-year contract.
The 3 proof plays that beat the cheaper MSP
Play 1: Walk in with your own audit score
Most MSPs open a pitch with their service catalogue. The catalogue says nothing about quality. Replace it with a 1-page summary of what you’d score against a recognised framework if an external auditor walked in tomorrow. Pick the framework your prospect already cares about: Cyber Essentials Plus, ISO 27001, NIS2 or NCSC CAF 4.0.
What this looks like in practice. A printable page that says: “Against the 14 CAF 4.0 principles, here is where we are achieved, where we are partially achieved, and what we are doing about the rest.”
Why this works: it tells the prospect 3 things at once. You know how you’re doing. You’re honest about gaps. You hold yourself to an external standard. The cheaper MSP can’t match this because they’ve never run the exercise.
How to build it: take the framework’s published controls, score yourself truthfully, redact anything client-specific, print one page per framework. A few hours of work, useful for every pitch from now on.
(Assurix independently assesses 59 controls and publishes the result on a link a prospect can open before the pitch. Live measures such as SLA response and patching refresh every six hours.)
Play 2: Hand the prospect 3 questions to ask the other MSP
The hardest pitch to win is the one where you’re not in the room when the decision happens. The way to influence that conversation is to give the prospect questions that expose differences they hadn’t thought to ask about. Phrase them so the cheaper MSP can’t bluff.
Three questions that almost always work
-
Show me 3 months of patching evidence on a current client account, redacted. Most MSPs say they patch promptly. Few can pull a clean report on demand.
-
Walk me through your last incident response. Don’t tell me what you’d do, tell me what you did do, what time it happened, who you escalated to, when the client got a written summary.
-
Who checks your controls between audits, and where can I see today’s result? “We’re committed to quality” is the answer of an MSP that has nothing to show.
Print these on a card you leave behind after meeting 1. Frame it as “questions worth asking any MSP you’re evaluating, including us”. The cheaper MSP either can’t answer these well or has to spend the next meeting recovering. You’ve moved the conversation onto your turf.
Play 3: Make your proof transferable so it works without you in the room
MSPs lose deals between meetings. Meeting 1 goes well. Then the prospect talks to procurement, the FD, the board, an IT-savvy friend. Your case gets retold by someone who heard it once. Most of the nuance gets lost.
The fix is something the prospect can pull up themselves and forward. Options that work, in order of build effort:
A 1-page proof summary as a PDF. Includes your audit scores, named third-party verifications, recent independent client testimonials with deal sizes redacted. Send it as a follow-up the same day as meeting 1. Easy.
An online proof page or trustmark profile the prospect can browse. Higher build cost, but the prospect can show their colleagues without you.
A short Loom (3 min max) walking through your proof, hosted at a private URL the prospect can share internally. Cheap, surprisingly effective. The prospect’s CFO doesn’t take meetings. They will watch a 3-minute video.
(Assurix gives you the second option: a link that shows every control Assurix assesses and whether it passes. Prospects can open it and share it internally. Assurix builds and hosts it.)
Down to the last two for a 70-user deal, Sereno walked the prospect through its live results and won against a rival holding ISO 27001 and SOC 2. Not the cheapest quote. Little Big Tech’s prospect signed the day after one meeting, once Nick had explained Assurix, the standard and how Little Big Tech is held to it.
Pick whichever you can build by Friday. The point is to put a copy of your differentiation in the prospect’s hands so the conversation continues when you’re not in the room.
What this looks like in a deal
Picture an MSP at the final round on a 24-user professional services client. It is £1,800/month more expensive than the incumbent. The prospect says price is the issue.
It sends the prospect a 1-page proof summary by email the same day. The summary shows its Cyber Essentials Plus certificate, its average time to resolve against SLA across all clients (3.1 hours, against a 4-hour SLA), and a quote from a client of similar size saying they’d switched from the same incumbent.
Two days later the prospect comes back asking why the cheaper MSP can’t produce the same proof. The MSP doesn’t have to defend its price. The prospect does the work. The deal closes at full rate.
The £1,800/month gap looks enormous when it is the only data point. It looks irrelevant once the prospect has 2 MSPs to compare and only one of them is showing real numbers.
When to walk away instead of fighting on price
Some prospects are not yours to win, no matter how good your proof is. The honest move is to qualify out early so you don’t burn cycles on deals that close at margins you’ll regret.
Three signals that the deal isn’t worth defending:
The prospect’s first criterion in qualifying conversations is “cheapest possible”. They’ll restate it whenever the conversation moves. They’re shopping on price, full stop.
The prospect can’t articulate any cost of failure. When you ask “what would it cost you if your IT was down for a day?” and they say “oh, not much”, they don’t have the pain that justifies a premium MSP.
The decision-maker isn’t in the room and won’t be. If you’re being filtered through a procurement lead optimising for the lowest viable bid, you can win a 1-year contract but you’ll lose the margin.
Walking away is harder than discounting, especially in a quiet month. MSPs that grow margin say no to the wrong deals.
What to do if you’ve already lost the deal (or think you have)
If the prospect went silent after pricing or told you they’ve gone with someone else, the deal isn’t necessarily dead. Some “we’ve gone with the cheaper option” decisions get reopened when the cheaper option underperforms.
Position yourself for that reopening:
Send a courteous email accepting the decision. Don’t argue. Make it clear you’d be happy to revisit if circumstances change.
Add the prospect to a quarterly check-in cadence. One short, useful email every 90 days. Industry update, a piece of MSP-related news, a free resource. No sales pitch. You’re staying top of mind for when they need an alternative.
Keep notes from your original pitch. When they call back, you want to pick up where you left off, not start cold.
Wins from this re-engagement pattern can be slow to arrive.
The proposal anti-pattern (and what to do instead)
Most MSP proposals open with: about us, our team, our values, then services and price. The opening pages are skim-fodder. The price is what gets remembered.
Restructure the proposal so the reader’s eye lands on the differentiating evidence first:
Page 1: where you stand against the frameworks this client cares about. Your Cyber Essentials Plus and ISO 27001 certificates with their dates, and your CAF 4.0 self-assessment.
Page 2: 3-month operational record. Tickets resolved by category, average time to resolve, percentage of issues caught by monitoring before user-impact.
Page 3: independent verifications. Cyber Essentials Plus and ISO 27001, trustmarks, client testimonials with verifiable names and roles.
Page 4: scope of services for this client. Standard.
Page 5: price. The page they were going to flip to anyway, but now framed by 4 pages of proof.
The prospect still sees the price. They just see it inside a context where the difference is justified.
This week: the plays as a checklist
The plays and the proposal structure above, as actions for this week.
DO:
Score your MSP against the Premium MSP Differentiation Checklist. It gives you a proposal line for each of its 7 proof points. Put the strongest one in tomorrow’s follow-up.
Write the 3 questions card. Send it as a follow-up to meeting 1.
Reorder your proposal template per the structure above. Apply to the next 3 proposals.
Audit your last 5 lost deals. How many were about price, and how many were about proof?
DON’T:
Discount before the prospect asks twice. The first “you’re expensive” is a test, not a final position.
Send price by email before a conversation. Once price is in the inbox, the negotiation is happening without you.
Open the proposal with about-us pages. The price is what gets remembered, not your team photo.
Match the cheaper MSP on rate. You’ll discount permanently because the client benchmarks you annually.
The point of all of this
The cheaper MSP wins when there’s nothing else for the prospect to compare. Your job is to give them something else. An audit score. A trustmark. A 1-page proof summary. 3 questions they can ask anyone. Whatever it takes to make the difference visible before the price is the only thing they remember.
You can build all of this yourself. Or hold a Trustmark: 59 controls independently assessed, live measures such as SLA response and patching refreshed every six hours, and a public suspension if a failure is left unfixed for 30 days. The prospect can check it without you.
