What "Can You Do It Cheaper?" Really Means
When a client asks 'can you do it cheaper', they are almost never making a statement about your price - they are making a statement about your value. The real message is 'I cannot yet see enough here to feel good about paying that.' The gap is between what the build is worth to their business and what they currently understand it will do for them. That gap is your job to close, and you do not close it by moving the number.
This matters because the instinct is to hear a price objection and answer it with a price. You cannot. If you drop the number the moment it is questioned, you have just told the client that your first price was soft, that there was margin to give, and that pushing works. You will get pushed on the next project, and the one after that. The price objection is a value conversation wearing a price costume.
Why Discounting On the Spot Costs You More Than the Discount
Cutting your price the moment it is questioned does three kinds of damage, and only one of them is the money. It is worth seeing all three before your next call.
- It reprices your credibility. A number that drops the instant it meets resistance was never anchored to anything real, and the client now knows it.
- It trains the behavior. You have shown that objecting gets a reward, so every future quote becomes a negotiation you started from behind.
- It devalues the outcome. If the build is worth less than you said the second a client frowns, the client quietly concludes the outcome was worth less too - which is the opposite of what you need them believing before they start.
The Value-Anchor Response - Three Moves That Hold Your Price
The Value-Anchor response is the sequence I run every time the price gets questioned: acknowledge, re-anchor, then trade scope. It keeps the conversation calm, keeps you off the defensive, and gives the client a real path to yes that is not just 'you caved'.
- Acknowledge without flinching. 'Totally fair to ask.' You are not arguing and you are not apologizing. A short, steady acknowledgement signals the price is not a nervous guess you are ready to abandon.
- Re-anchor on the outcome and the cost of not doing it. Move the frame off your fee and onto what the build is worth: the hours it saves every week, the revenue it unlocks, the manual process it kills. 'This pays for itself the first month it runs.' The price only feels high next to nothing - next to the outcome, it is small.
- Trade scope, never rate. If they still need a smaller number, change what they get, not what you charge for it. 'I can hit a lower number if we start with just the piece that saves you the most time and add the rest in phase two.' Now the price moved for a reason the client chose, and your rate held.
What This Sounds Like On a Real Call
A client came back on a build quote and asked if I could do it for less. The old reflex would have been to shave a few hundred off to keep things moving. Instead I ran the sequence. I said it was a fair thing to ask, then I moved the frame: the automation was going to remove roughly a day a week of manual work for two people, so the question was not whether it was expensive, it was how fast it paid back. Then I gave them the choice.
I offered to start with just the highest-impact piece at a lower number and add the rest once they had seen it run. They took the phased version at my full rate - a smaller first invoice for a smaller first scope, with the rest lined up behind it. The price moved because the scope moved, not because I blinked. And because the first number held, the phase-two conversation started from trust instead of from a fresh haggle.
Two ways to answer 'can you do it cheaper'
| Response | What the Client Learns |
|---|---|
| Drop the price to keep the deal | The first number was padded; pushing works; the outcome must be worth less than you claimed |
| Re-anchor on value, then trade scope | The price is real; the outcome is worth it; a smaller number means a smaller build, decided together |
The Mindset That Makes the Words Work
The script only lands if you actually believe your price is fair, so do the work that earns that belief before the call. Know the outcome your build creates in the client's own terms - hours, dollars, headaches removed. When you can state the value plainly and calmly, holding your price stops feeling like a confrontation and starts feeling like a fact you are simply sharing.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How do you respond when a client asks if you can do it cheaper?
Do not answer a price objection with a price. Run the Value-Anchor response: acknowledge the question without flinching, re-anchor the conversation on the outcome and the cost of not doing the build, then - if they still need a smaller number - trade scope rather than rate. Offer to start with the single highest-impact piece at your full rate and phase the rest. The price moves because the scope moved, not because you caved.
Should I ever discount an AI project?
Only when you also reduce the scope. A lower number for the same deliverables tells the client your first price was padded and trains them to push you every time. A lower number for a smaller, clearly defined deliverable is a legitimate decision the client makes with you. Discount the scope, never just the rate.
What if the client genuinely has no budget?
Then it is a scope mismatch, not an objection to beat. Use the same last move: find the single piece of the project that delivers the most value for the budget they do have, deliver that first, and line up the rest as a later phase. They get a real result inside their budget and you keep your rate intact.
Why is discounting on the spot a mistake?
Because it costs more than the discount itself. Cutting the price the moment it is questioned reprices your credibility, trains the client that objecting gets rewarded, and quietly signals the outcome was worth less than you said. Holding your price and re-anchoring on value protects all three - your rate, your authority, and the client's belief in the result.
Last reviewed by Duncan Rogoff on July 26, 2026
