Section 1
The deal you lost by getting cheaper
A 60-seat wholesale distributor. Two locations, an aging on-premise ERP that runs order entry, a warehouse team that starts scanning at 6am. Their current provider is mediocre in a familiar way: tickets sit, the account manager changed twice last year, patching is inconsistent. The owner told you all of this himself in the first meeting, unprompted. You quote 2,400 a month against the 2,900 they pay now. Tighter response commitments, a real backup and recovery posture, a named technical lead. On every line you compare well, and you are 500 a month cheaper. He goes quiet for eleven days. When you follow up he says the number is higher than they budgeted, which is odd, because it is lower than what they currently spend. You do what most owners do: you waive the onboarding fee and take the monthly to 2,100. Now you are 800 a month cheaper than the incumbent and the deal still dies. In February you find out they renewed with the same provider at 2,900. Read that sequence again. He was never comparing 2,400 to 2,900. He was comparing a system that is annoying but currently running against two weeks in which the ERP might not come up on a Monday morning and the warehouse cannot ship. Your discount moved the only variable that was not in dispute. It did not touch the one that was. This is the pattern that eats MSP margin quietly. The objection you answer is the one you were given. The objection that decides is the one nobody says.
Section 2
What 'too expensive' is actually pricing
The useful lens here comes from prospect theory, which is a formal way of describing how people actually evaluate a change rather than how a spreadsheet would. Two parts of it matter for you. First, people judge outcomes against a reference point, not in absolute terms. Your prospect's reference point is not an empty state. It is their current setup, working today, with all its faults already absorbed and normalised. Anything better than that reads as a gain. Anything worse reads as a loss. Second, losses loom larger than gains. This is loss aversion, and the rough working rule is that a loss is felt roughly twice as heavily as a gain of the same size. It is not a character flaw and it is not irrational. It is how the decision gets weighted. Now run your proposal through that. Faster response times, better patching, a cleaner backup regime: those are gains, they are probabilistic, they arrive slowly, and they get counted at a discount. Three days of broken order entry, staff standing around, an angry customer call from the largest account: that is a loss, it is vivid, it arrives immediately, and it gets counted at a premium. There is a second term in the equation your quote does not touch at all. The gains belong to the company. The loss, if it happens, belongs to the person who signed. Nobody at that distributor gets promoted because tickets close faster. Somebody gets remembered for the week the warehouse could not ship. So when your price drops from 2,400 to 2,100 you have improved the smaller, discounted, corporate side of the ledger and left the larger, amplified, personal side untouched. The arithmetic gets better and the decision does not move. That is not stubbornness on their part. You optimised the wrong variable.
Section 3
A discount is a cheap signal, and cheap signals make buyers more nervous
There is a second reason discounting underperforms, and it is worse than neutral. It often increases the perceived risk. Think in terms of signals. A signal only carries information when it is costly to fake. Anyone can claim a 15-minute response time on a website. The claim is free, so it tells a buyer nothing, which is why every MSP homepage in your market reads the same and none of them are believed. A signal that costs the sender something is the only kind that separates you. A discount costs you real money, but from the buyer's chair it is close to free to produce. You produced it in a single phone call, with no conditions, in under a minute. So the buyer's brain does what it should: it asks what the discount reveals. There are two available readings, and both hurt you. The first is that the original number was padded. If 2,400 could become 2,100 in one call, then 2,400 was never a real number, and if the price was flexible then the scope probably is too. That is a competence signal, and it is negative. The second is that you needed the deal. A provider who needed this deal is a provider with capacity problems, or churn, or a thin bench. For a buyer already worried about a migration, 'they were eager' is not reassuring. Compare that to a commitment that is expensive and specific: a named engineer who is on site for the two cutover mornings, a parallel-run period where the old mail flow stays live, 20 percent of the first three months' fee held back against a written go-live checklist. Those are costly. You cannot offer them casually to everyone, which is exactly why they carry information. A discount says you want the deal. A costly commitment says you expect to survive the migration.
Section 4
Diagnosing the objection: six questions, in order
You cannot treat an objection you have not identified. Three different things hide behind 'too expensive': a genuine budget constraint, transition risk, and internal politics. They need different responses, and guessing costs you either the deal or the margin. Ask these in this order, in a call, not in an email. 1. 'If the monthly were identical to what you pay today, would you make the move this quarter?' This is the splitter. A yes means price was never the blocker and you can stop discounting immediately. A hesitation, a qualifier, or a change of subject means you are looking at risk or politics. 2. 'Is there a number that is already approved, and a number that would need someone else to sign off?' This separates a real budget ceiling from a soft preference. A real ceiling has a name attached to it and a date. A soft one does not. 3. 'Walk me through the last time you changed providers here. What happened?' History is the single best predictor of how much fear is in the room. An owner who lived through a bad cutover in 2019 is not buying managed services, he is buying an assurance that 2019 does not repeat. 4. 'What is the one system that absolutely cannot be down on a Tuesday morning?' This converts a vague dread into a named, addressable object. Once he says 'order entry' you have something you can build a commitment around. 5. 'If this went badly in week one, who hears about it first, and who is standing in front of that conversation?' This is the blame question. Ask it plainly. The answer tells you whose personal exposure you are actually negotiating against. 6. 'What would have to be in writing for you to be comfortable starting?' You are asking the buyer to specify the costly signal he needs. Most will tell you, and it is almost never a lower price.
Section 5
Three objections, three different plays
Once you know which one you have, the response is not a matter of taste. If it is a genuine budget constraint, reduce scope, not price. This is the case where discounting is closest to defensible, and it is worth being honest about that: when a buyer has a hard approved ceiling and your service genuinely costs less to deliver at their site than at your average site, a lower number is a fair number, not a concession. What you must not do is keep the same scope at a lower price, because you have then taught the buyer that your pricing is a negotiation and you will re-run that negotiation at every renewal. Move a tier down, remove on-site hours, lengthen the response window, and say out loud what is coming out. If your tiers cannot support that conversation, the problem is upstream in how you built them, and the fix is structural rather than tactical. We worked through that structure in https://bizgrowthaxel.com/blog/how-to-price-managed-services-so-buyers-self-select/ . If it is transition risk, stop selling the steady state and start selling the move. The buyer has already conceded that your ongoing service is better. Nothing you add to that column changes the decision. Rebuild the proposal so the first four pages are the migration itself: a dated cutover plan, what runs in parallel and for how long, the named person who is physically present, the rollback trigger and who is authorised to pull it, and one reference call with a client whose migration hit a problem and how you handled it. That last one is uncomfortable and it is the most persuasive item on the list, because a clean reference is a signal any provider can produce. If it is internal politics, none of the above helps, and you need a different motion entirely: arm your champion with material written for the person who is actually blocking, and get access to that person or accept that the deal is not yours to win from outside the building.
Section 6
The commitments that cost you something, and what each one actually costs you
Risk-reducing commitments work because they are expensive. That means you have to price them, cap them, and be willing to walk when a buyer wants all of them on a deal that cannot carry them. Here is the honest cost of the common ones. A named engineer on site for cutover mornings costs you scheduling flexibility and usually two days of billable capacity, and it creates a key-person dependency you now have to manage. Cap it at the specific dates. Do not let it become an expectation for the life of the contract. A parallel-run period, where the old system stays live alongside the new one, costs licence overlap, engineer attention split across two environments, and a longer window in which something can break. It is the single most reassuring item you can offer and it is genuinely expensive. Charge for it or shorten it, but do not pretend it is free. A written rollback plan costs pre-cutover documentation time, which is unglamorous work that nobody wants to schedule. It is also the item that most often does not exist in MSP proposals, which is why writing one separates you. Fee at risk, where a portion of the first months' fees is contingent on a written go-live checklist, costs you cash-flow certainty and forces you to define done precisely. Only offer it if your delivery is actually consistent. If it is not, this clause will find out. One rule sits above all of these. Never offer a commitment you cannot operationally keep. A promise you break in month two is not a costly signal, it is a fraudulent one, and it detonates into churn and a reference you can never use. If your delivery cannot support these commitments yet, the growth problem is in operations, not in sales, and it is worth being clear-eyed about the order of work. That sequencing is the substance of what we do with MSPs at https://bizgrowthaxel.com/msp/ .
Section 7
Where this flips, and what the model cannot see
There is a case where this entire approach backfires, and you need to spot it inside the first ten minutes. If a prospect has just been burned catastrophically, the polarity reverses. A ransomware event the incumbent handled badly. A provider who stopped answering. An MSP that got acquired and whose service collapsed. In that situation the reference point has already moved. Staying is now the risky option and moving is the safe one. Loss aversion has not switched off, it has switched sides, and it is now working for you. Run your careful reassurance script into that room and you will lose to someone less qualified. Your parallel-run period sounds like hesitation. Your phased plan sounds slow. Your risk language sounds like you have not grasped how bad it already is. This buyer wants decisiveness, a start date this week, and someone who will take control on Monday. The correct move is to compress, commit, and lead. Give them fewer options and a shorter runway. The tell is simple: listen for whether they describe the current provider in the past tense or in the present tense. The blind spot is different and you should hold it seriously. This lens reads an individual buyer's psychology, and it goes blind inside larger organisations where procurement is political. Above roughly 75 to 100 seats, or anywhere with a CFO and an internal IT manager, 'too expensive' may be a proxy for something you cannot see from outside: an internal IT lead whose scope shrinks if you win, a finance director with a prior relationship, a group-level consolidation mandate already decided. No amount of migration reassurance touches any of that. The symptoms are recognisable. The objection changes shape between calls. Your champion stops forwarding your material. A new stakeholder appears late with a fresh concern. When you see those, stop refining the proposal and start trying to reach the room where the decision is actually being argued.
Section 8
The fitness test
This approach is not right for every MSP, and applying it from the wrong operational position will cost you. You are ready for this if you can hold your price through at least one round of silence without your cash position dictating the answer. If you have a delivery process consistent enough that a written cutover plan and a rollback trigger are documentation of what you already do, not aspirations. If you can name an engineer for a specific date two weeks out and know that commitment will survive contact with your ticket queue. If you have at least one client who will speak honestly on a reference call, including about something that went wrong. And if your pipeline has enough volume that you can afford to disqualify a buyer whose only real objection is a ceiling you cannot profitably meet. You are not ready if this month's payroll depends on the deal in front of you, because every costly commitment you make under that pressure is one you will be tempted to break. If your onboarding differs materially from technician to technician, because you cannot signal a process you do not have. If you have never actually written down what your migration steps are. If your tiers are improvised per quote, in which case scope reduction is not available to you and the discount really is your only lever, which is a structural problem worth fixing before a sales one. And if your average deal is under a few hundred a month, where the buyer's transition risk is small enough that price genuinely does decide it. Start with the diagnosis, not the rebuild. On the next three deals that stall, ask question one and question five and write down the answers. If two of the three say they would still hesitate at an identical price, you have confirmed the problem is not your number, and you now know which part of your proposal is doing no work at all.