Handling price objections and discount requests

0:00 Handling price objections

It's too expensive. Four words that make many freelancers and agency owners panic, and reach straight for a discount. But here's what the best negotiators know. An objection is usually a question in disguise. Too expensive compared with what? With their budget, with a competitor, or with what they expected to pay? In this lecture, you'll learn a framework for handling objections, responses to the most common ones, including the new one, we can get AI to do this, why you should never discount without a trade, how discounts hit your profit, when to walk away, and how to handle procurement teams.

0:44 Why it matters

Why does this matter? Because the way you handle the first objection often decides both whether you win the deal and how profitable it is. Discount at the first push, and you teach the client that your prices are soft, you lose margin, and you often attract the most price-sensitive clients. Handle it calmly with questions, and you usually learn something that helps you either adjust the scope sensibly or show the value more clearly. Here's the key idea. Treat objections as information, not attacks, and never give value away without getting value back.

1:25 The diagnosis analogy

Here's an analogy. Think of a doctor whose patient says, this treatment sounds painful. A bad doctor immediately offers a weaker treatment. A good doctor asks, what worries you most? It might be the pain, or the time off work, or the cost. Each worry has a different answer. Price objections are the same. Your first job is to diagnose the worry. Is it budget, meaning they can't afford it? Is it value, meaning they don't yet see why it's worth it? Or is it comparison, meaning they've seen something cheaper? Only then do you prescribe.

2:07 The framework

Here's the framework. First, pause and acknowledge: thanks for being direct. Next, ask a clarifying question: compared with what? Or, what budget did you have in mind? Listen carefully. Then respond to the real concern. If it's budget, adjust scope, not price for the same scope. If it's value, connect back to the outcomes and figures they shared. If it's comparison, compare what's included, side by side. And finally, confirm: does that address your concern? Throughout, stay calm and curious. A price objection means they're interested enough to negotiate.

2:46 Never discount without a trade

Now the rule that protects your business. Never discount without a trade. Let's see why. A project priced at fifteen thousand, with twelve thousand of direct costs, makes three thousand profit. A ten percent discount takes the price to thirteen and a half thousand. Costs don't change. Profit falls to fifteen hundred. You've halved your profit, and you'd need twice as many projects to earn the same. So every discount must buy something: a scope reduction, a longer term, upfront payment, a case study or a referral. If I can't reduce the price for the same scope, but if we remove this, I can bring it to that.

3:33 Worked example 1: Rhys in Cardiff (illustrative)

A simple worked example, illustrative. Rhys, a freelance photographer in Cardiff, quotes two thousand pounds for a product shoot. The client says, can you do twenty percent off? Old Rhys would agree to sixteen hundred. New Rhys asks: what budget were you working with? Sixteen hundred. So he offers options. At sixteen hundred, he can shoot thirty products instead of fifty, with one lifestyle scene instead of three. Or at two thousand, the full scope, with payment split half now, half on delivery, which helps their cash flow. The client chooses the full scope with the split payment. Rhys kept his price by solving the real problem: cash timing.

4:20 Common objections

Now responses to common objections. Your competitor is cheaper: they may well be. Let's compare what's included: scope, seniority, reporting, support and guarantees. If the scope is genuinely the same, they may be the better choice. That honesty builds trust. We need to think about it: of course; what's the main thing you'll be weighing up, and who else will be involved? And the new one, we can get AI to do most of this: for some tasks, absolutely. Where we add value is judgement, integration, accountability and results. Would a smaller scope focused on those parts work better? Sometimes that's the right answer for both of you.

5:07 Worked example 2: procurement in Islamabad (illustrative)

Now the realistic scenario, illustrative. Imran's IT services company in Islamabad bids for a support contract with a large manufacturer. Procurement runs the process: standard forms, a request for a best and final offer, and a target of fifteen percent savings. Imran prepares. He knows his BATNA: two other contracts in the pipeline. He learns the evaluation criteria: price counts for forty percent, and service levels and local presence count for the rest. So he offers three scope levels, keeps his core price, and trades a five percent reduction for a three-year term and payment within thirty days instead of ninety. He also meets the IT director, who owns the project. He wins, at a healthy margin.

5:58 Watch me: 'too expensive'

Watch me handle an objection live, using the scripts in the lesson. The client says: honestly, it's too expensive. I pause, and say: thanks for being direct. Compared with what? They say: we had budgeted about twenty percent less. So it's budget. I say: that's helpful. Let's look at what we'd change in the scope to fit that. We could phase the project, or remove the monthly reporting deck and give you a live dashboard instead. They like the dashboard idea. We land within their budget, and my margin is protected because the scope changed too. Nothing was given away for free.

6:42 When to walk away

When should you walk away? When the only way to agree is below your reservation point. When the client wants the full scope at a price that makes the work unprofitable. When red flags pile up, like disrespect, unrealistic demands or a history of late payment. Walk away politely, and leave the door open: it sounds like we can't make the numbers work this time. I'd rather say that honestly than agree to something neither of us will be happy with. Budgets change, and a respectful no often becomes a yes next quarter.

7:22 Common mistakes

Let's list the common mistakes. Discounting at the first objection. Discounting without a trade. Arguing instead of asking. Assuming every objection is about price. Attacking competitors. Getting defensive when clients mention AI. Negotiating only with procurement and never meeting the person who owns the project. And not knowing your walk-away point, so you accept work you'll regret.

7:47 Recap and try this now

Let's recap. Objections are questions in disguise. Pause, acknowledge, ask compared with what, respond to the real concern, and confirm. Adjust scope, not price for the same scope. Never discount without a trade, because discounts cut profit much faster than they cut price. Handle competitor and AI comparisons honestly, focusing on inclusions and value. Prepare for procurement with your BATNA, their criteria and scope options. And know when to walk away. Your try this now: print the objection scripts, calculate what a ten percent discount does to your profit on a typical project, and write your polite walk-away line. Next, we'll negotiate payment terms that protect your cash.