How to say no in three lines
To say no well, thank the person, say the no plainly in one sentence, and give one next step with a date on it. Use those three lines on a discount ask, a fourth demo, a client's extra request or your manager's new project, and send them as one WhatsApp message if that's where the ask came in.
Thanks for asking, I can see why you want it.
I can't do that one.
What I can do is [the smaller yes, the referral or the later date], and I'll confirm by [day].
Three things are missing on purpose. There's no apology up front, no paragraph of reasons, and no "let me see what I can do" when you already know the answer. That last one costs the most. A soft maybe turns into three chasers from them and a week of carrying the ask around in your head.
The next step keeps the deal alive. A prospect who hears "no to $2,000 off, yes to dropping the setup fee, revised quote by Thursday" still has something to say yes to.
Why yes comes out first
Most people say yes before they've thought about it, for a short list of reasons. You want to be liked. You don't want an argument. Saying no makes you feel guilty. And when you're tired, yes is one word, while no takes a sentence and a plan.
Selling adds one more reason: the person asking is someone you want to sign. A request from a prospect feels like a test of the deal, and a request from your manager feels like a test of your job. So yes slips out, and the bill arrives next week.
James Clear sums up the cost in two sentences: "No is a decision. Yes is a responsibility." A yes today spends an hour of a future week. Agree to a fourth demo for a lead who stopped moving a month ago, and you've spent the hour you set aside for ten new calls, which means you said no to your prospecting block without anyone hearing it.
The fear is also bigger than the result. Julian Givi of West Virginia University and Colleen Kirk of New York Institute of Technology ran five experiments with more than 2,000 people, published in the Journal of Personality and Social Psychology and reported by the American Psychological Association. People who turned down an invitation expected the other person to be angrier and more disappointed than that person reported feeling. In their pilot study, 77% admitted going to something they didn't want to attend because they worried about declining. The study was about invitations, not sales requests, and the pattern is the same one you feel before a hard call: you picture a worse reaction than you get.
Decide before you answer
Don't answer a request on the spot unless it's an easy yes. Buy a few hours with one line that names a time:
"Let me check my week and come back to you by 4."
Then come back by 4. A pause only works if it ends. Use those hours to run three checks against your real week, not the one in your head.
- Would you agree if it were today? The economist Tim Harford's test, quoted by James Clear, is to ask "If I had to do this today, would I agree to it?" A meeting three weeks out feels free. It won't feel free on the day.
- What does it push out? Open your calendar. If the yes lands on your prospecting block or your follow-up hour, name what moves.
- Is it what they need? A prospect asking for a fourth demo usually needs one question answered, and a client asking for a call usually needs a decision, so the real need often fits inside a smaller yes.
Pass all three and it's a full yes. Pass one or two and offer a smaller yes: a 15-minute call instead of an hour, a written answer instead of a demo, next Tuesday instead of tomorrow. Fail all three and it's a no. Rank your day before it starts, promises first and deal-moving work next, the way prioritization does it, and the second check takes seconds.
What to say in a seller's week
Most weeks bring at least three of these. Say the middle column, then do the last one the same day, while you still remember what you promised.
| The ask | What to say | Then |
|---|---|---|
| A prospect wants $2,000 off | "I can't move the price. I can take the setup fee off if you sign this month." | Send the new quote today, set a check-in date |
| A stalled lead wants another demo | "Happy to help you decide. What's the one question a demo would answer?" | Answer it in writing, agree a decision date |
| A client wants extra work free | "That's a new piece of work. I'll send you a price for it by Friday." | Price it, note it on their record |
| A poor-fit lead wants to buy | "I don't think we're the right fit, and I'd rather say so now. Here's who is." | Refer them, close the lead with the reason |
| Your manager adds a project | "Yes. Which of my three priorities should slip to make room?" | Agree the swap in writing |
| A colleague wants you on a call in your call block | "I'm on calls till 11. I can join at 11:30, or send notes." | Block the time or send the notes |
| An event invite in month-end week | "Thanks for thinking of me. Month-end's packed, so I'll sit this one out." | Ask to be invited next time, if you mean it |
Two of those rows need more than a line, because they're the ones that cost you money when you get them wrong.
The discount. You're refusing the price cut, not the person, and the swap keeps a yes on the table. If you do give money off, trade it for something you want: a longer contract, an earlier start or a referral. When the push is "it's too expensive", ask whether they don't see the value or can't find the money this quarter. Each needs different words, and common sales objections gives you both.
The poor-fit lead. Turning down a sale feels wrong when you're behind on target. A customer who needed something you don't sell usually costs you hours of support and comes back as a complaint or a refund. Ask the four fit questions from how to qualify prospects on the first call, and the no comes in week one, not month three.
Saying no to your manager
Your manager's request isn't really a yes-or-no question. It's a question about what comes first, and the person who sets priorities should make that call.
Ask which project should move to make room. Greg McKeown makes the same point in Essentialism, and James Clear quotes him on the same page. Say it with numbers: "I can run the webinar. It lands on my Tuesday prospecting block, which is 40 calls. Do you want the webinar or the calls this week?"
Plenty of managers pick the calls. If yours picks the webinar, fine: it was their trade to make, and the dip in your call count has a reason on record.
Bring new asks to your weekly 1:1 with your calendar open. The 1 on 1 meeting template starts with the week's numbers, which is where a trade like this gets weighed.
If you manage reps, guard their prospecting blocks the same way. When you hand over a new task, say what it replaces. A rep who has to guess which of your asks matters will say yes to all of them and make the calls last.
Saying no to a prospect without losing the deal
A no to a prospect rarely ends the deal. Often it's the moment they learn you'll tell them the truth. William Ury, a co-founder of the Program on Negotiation at Harvard Law School, built a seminar and a book around saying no to customers and coworkers without losing them. The Program's page for the book puts the promise plainly: save the deal, save the relationship and still say no. His three-step method has you defend what matters to you, keep the no firm when the other side pushes, and still get to a yes.
On a sales call, start with what you're protecting: "We charge every customer the same price, so nobody pays more than the firm next door." Then the no, in one line: "So I can't do $2,000 off." Then the yes you can stand behind: "I can spread the setup over three months, or drop the second training day. Which suits you?"
The three noes you'll give prospects most often:
- No to a price cut. Swap, don't drop. Something comes off the scope, or something comes back to you.
- No to more free work. One proposal is selling. A third revised proposal with no decision date is working for free, so ask for the date before you write it.
- No to a deal that isn't right. Refer them on, and close the lead with the reason so you don't chase it again in three months.
Standing rules for clients you already serve, like reply hours and what the work includes, are better said once, at the start, than refused one request at a time: setting boundaries with clients covers that conversation.
Saying no in a chat
Text strips out your tone, so a short no reads cold and a long one reads nervous. Two lines does it: the no in the first, the next step in the second.
- "Thanks, Daniel. I can't do Saturday. I'm free Monday at 10 or Tuesday at 3, which works?"
- "I won't be able to go lower on price. I can remove the install fee, want the updated quote?"
- "I don't think we're the right fit for this one. I'll send you the name of someone who is."
- "Got this. I'll reply properly at 9 tomorrow."
Reply in their thread, with their name, one person at a time. A no is personal, so a broadcast or a group chat is the wrong place for it. Read it once before you send. If you've apologised twice, cut one. If the no isn't in the first line, move it up.
When they ask again
Some people treat the first no as an opening offer. Don't add reasons the second time, because every new reason is something new to argue with. Give the same no, in the same tone, with the same next step.
"Like I said on Tuesday, I can't do $2,000 off. The setup fee offer stands until Friday."
On a third ask, name it kindly and close the topic: "I've given you my answer on price, and it won't change. Do you want to go ahead with the setup fee off?"
Some asks need no softening at all. A request to fudge a number on a quote, promise something your product doesn't do, or pass on another customer's details gets a flat answer: "No, I won't do that." You don't owe a reason. If the ask came from inside your company, tell your manager and note the date.
A rep's week of noes
Made-up example: Farah sells payroll software to firms of 10 to 50 staff, and this week five people ask her for something she should turn down. Her target is 12 demos a month, and Tuesday and Thursday mornings are her prospecting blocks.
Monday: her manager, Ben, asks her to host Wednesday's webinar. She says yes and asks which should go, the webinar prep or Thursday's calls. Ben gives the webinar to a colleague with no calls booked that morning.
Tuesday: a prospect asks for $2,000 off a 30-seat deal. Farah says she can't move the price, offers to waive the setup fee for a signature this month, and promises the new quote by 5pm. She sends it at 4:40.
Wednesday: a lead who went quiet three weeks ago asks for a fourth demo. Farah asks what a demo would answer. The reply: "Whether it handles shift allowances." She answers in writing with a screenshot and asks for a decision by next Wednesday.
Thursday: a colleague asks her to cover a trade show stand on Saturday. She says no, and offers to brief whoever goes for 15 minutes on Friday.
Friday: a 300-person firm wants to sign, but they need a feature the product doesn't have. Farah tells them, refers them to a provider who has it, and closes the lead with the reason.
By Friday she has said no five times. She kept both prospecting blocks, the discount deal is still open with a date on it, and the quiet lead has a decision day. Every promise she made that week sits on her list as a dated follow-up.
A no is done when the next step has a date
Every no above ends with a promise: a quote by 5, a decision by a set date, a check-in next quarter. Those promises are the first thing to vanish in a busy week, and a no whose follow-up got lost reads to the other person like a door shut in their face.
So write the date down before you close the chat. A task with a day on it does the job, or a line on the contact's record. If you use ActivityTracker, type the follow-up with its day in it, like "send Kwong Hup the new quote Thursday", and it's saved with Thursday's date. On Thursday morning, a strip on the activity log counts it with everything else due that day, and with the overdue ones if you miss it.
Read those dates at your weekly pipeline review. A prospect who heard "not at that price" in March is worth a call in June, as long as you set the June date on the day you said no.
If your prospecting blocks keep getting eaten, timeboxing gives each task a fixed slot on your calendar, so a request that lands on your call hour has something visible to move.
Every contact record in ActivityTracker carries a follow-up date, and its card counts the days overdue, so the quote you promised after a no goes out on the day you named.
See follow-up dates in the CRMGet better at it in five working days
Saying no is a skill, and the small ones build it.
- Monday: count. Write down every request you say yes to, and mark the ones you didn't want.
- Tuesday: pause. Use "Let me check my week and come back to you by 4" once, and run the three checks.
- Wednesday: decline one small internal ask, like an optional meeting.
- Thursday: give one prospect or client the full three-line no, with a dated next step.
- Friday: review. Did anyone react as badly as you expected? Which line felt stiff? Rewrite it in your own words.
Most weeks, the answer to Friday's first question is no. Givi and Kirk found the same gap with invitations: the reaction you dread is bigger in your head than it is in theirs.
Keep reading
Questions people ask
Thank them, say the no in one plain sentence, and give one next step with a date. Skip the long apology and the list of reasons, because both invite a debate.
No. You're declining one request at one time, not the person. Say it warmly with a next step, and expect a milder reaction than you fear: in Givi and Kirk's experiments, people who turned down an invitation overestimated how upset the other person would be.
Make the trade visible instead of refusing. Say yes to the task and ask which of your current priorities should slip, so your manager makes the call and a lower call count has a reason on record.
Say what you're protecting, hold the no, and offer a yes you can stand behind, like a smaller scope or a later date. A no with a swap and a date keeps the deal open.
No. One short reason is fine, and none is fine too. Every extra reason gives the other person something new to argue with.
Give the same no in the same tone, with the same next step, and add no new reasons. On the third ask, say your answer won't change and move to the next decision.
Sources
- American Psychological Association, press release on the cost of turning down invitations (Julian Givi and Colleen Kirk, Journal of Personality and Social Psychology, published online 11 December 2023), read 28 October 2026
- James Clear, on saying no (with Tim Harford's test and Greg McKeown's advice for saying no to a manager), read 28 October 2026
- Program on Negotiation at Harvard Law School, The Power of a Positive No by William Ury, read 28 October 2026


