TL;DR:
Listen first: restate the objection in your own words so the reader knows you read it.
Clarify what sits behind it, then connect your answer to the value they said they wanted.
End with no pressure: one easy next step and a real way out.
Someone you have been talking to writes back: "Thanks, but it's too expensive." The easy reflexes are to cut the price at once or to defend it with a list of features. Both skip the part that matters, which is finding out what the objection actually means.
An objection by email is a gift of information. The reader told you what stands between them and a yes. Your reply should treat it that way, and it can be written in about ten minutes with any mail app and a notes document.
When an objection email deserves a careful reply
Not every no needs a long answer. Reply carefully when the person has shown real interest before (they asked questions, joined a call, or requested a quote) and the objection is specific. A one-word brush-off from a stranger can get a short, polite reply or none.
Common objections are price, timing, "we already use something", and "I need to ask my manager". The method below works for all of them. The worked example uses price because it is the one that most often hides something else.
Before you write: gather what you know
Open the earlier thread and your notes. What did they say they wanted to fix? Use their words, not yours.
Note what they are comparing you with. "Too expensive" next to what?
Know your real options before you write. Can you offer a smaller scope, a different plan, or a later start? Do not hint at one you cannot deliver.
Decide what a good outcome is. Often it is a short call or a clearer picture, not an instant yes.
Four steps for the reply
Listen: Open by restating the objection in a sentence, in a neutral tone. Thank them for saying it plainly. This shows you read it and takes the heat out of the exchange.
Clarify: Ask one or two questions, not five. Aim at the thing behind the words: is it the total amount, the budget timing, or doubt that it is worth it?
Connect to value: Point back to the outcome they told you they wanted, and say plainly what it is worth to them. Use their numbers or their wording. If you cannot find any value for them, say so honestly.
No pressure: Offer one easy next step and an easy exit. Say that a no is fine and that you will not keep chasing. People answer more honestly when they do not feel cornered.
Worked example: replying to "it's too expensive"
Say you run a small bookkeeping service. A shop owner wrote earlier that she spends her Sunday evenings catching up on receipts. After your quote she replies: "Thanks, but it's too expensive." Here is a reply that follows the four steps.
Subject: Re: Quote for monthly bookkeeping
Hi Dana,
Thanks for telling me straight. So I understand: the monthly fee feels higher than you expected.
Could I ask what you were expecting, or what you compared it with? If it is the amount itself, I may be able to quote a smaller scope. If it is more about whether it pays off, that is worth looking at together.
You mentioned that Sunday evenings go to receipts. If that is about four hours a week, that is roughly sixteen hours a month you would get back. Only you can say what those hours are worth, and that is the number I would weigh against the fee.
No pressure at all. If it is not the right time, that is fine and I will not chase you. If it helps, I can send a version that covers receipts only, so you can see the difference in price.
Best,
SamCheck the arithmetic in the middle paragraph: 4 hours × 4 weeks = 16 hours. The email says "if that is about four hours", so it does not claim a fact the reader has not confirmed. Dana, Sam and the shop are made up for this example.
Notice what the reply leaves out. It does not drop the price, argue, or add a deadline. It asks one real question, ties the answer to her own words, and offers a smaller option that she can say yes or no to.
Mistakes that lose the conversation
Discounting in the first reply. It teaches the reader that the price was not real and does not solve the cause.
Answering a feeling with a feature list. If the worry is value, more features rarely help.
False urgency such as "this price ends Friday" when it does not. Readers notice, and it breaks trust.
Writing too long. Four short paragraphs are plenty; put the question near the top.
Sounding hurt. Keep the tone as warm as your first email.
Other objections, same four steps
The shape holds when the words change. For "we already use something", listen by naming what they use, clarify what it does well and where it falls short for them, and connect only to a gap they mention. For "bad timing", ask what would need to change, then offer to check back on a date they choose.
For "I need to ask my manager", offer help rather than pressure: a short summary they can forward, written for someone who was not on the earlier calls. In every case the reply ends with a choice that is easy to make and easy to decline.
Read your draft as the other person
Before you press send, read the email once as the reader would, on a phone, between meetings. Is the first line something you would be glad to receive? Does it ask for one thing? If you find a sentence that sounds like a script, cut it or say it the way you would say it across a desk.
Doing it faster
Keep a short file of your own past replies to each objection type, and copy the structure, not the sentences, so each email still sounds like a reply to one person. If you want a second pair of eyes on a draft, DuckyHelper can see your screen while you write and you can ask it out loud what reads as pushy. You decide what to send.
Frequently asked questions
Should I reply right away?
Reply within a day or two if you can, but a reply you thought about beats a fast one. If you need to check a number, say you will come back to them and give a day.
What if they do not answer my clarifying question?
One gentle follow-up after a few days is reasonable. After that, leave the door open and stop. A short closing line such as "I'll leave it here, and you know where to find me" is enough.
