Client asking for a discount: what to reply
The quote went out and came back with “is there any flexibility on the price?” Below is the one-line answer that keeps your rate intact, the full script for the startup version of the ask, and how to build a smaller version of the job so the client still gets a yes.
The one-line reply
Nine times out of ten this is the whole answer, and it fits in a chat message:
The line
When: the client has seen the number and pushed back on it, without naming a figure of their own.
Understood. What budget did you have in mind? I’ll tell you what fits in it.
Slightly longer email version: “Understood, and thanks for saying so rather than going quiet. The [$X] is what this scope costs. Tell me the number you’re working with and I’ll put together the version of this that fits it, so you can see what you’d be getting.”
It does several things at once. It doesn’t say no, so the client isn’t rejected. It doesn’t defend the price, so there’s nothing to argue with. It asks them to name a figure, which is the piece of information you actually need and the one they were hoping not to give. And it promises a next step that is work on your side rather than a concession.
Then wait. The pause after that question feels long, and the temptation is to fill it with “but I have some flexibility” or “I could probably do a bit better.” Filling it costs you the whole negotiation before the client has said a word.
Cut scope, never rate
The kit’s pricing rules put it in one sentence: a smaller thing at full rate is a business; the full thing at a smaller rate is a hobby. The reason isn’t pride. A discounted rate follows you.
- It becomes the price. The rate you agree on the first project is the rate that client expects on the second, and the number they quote when they refer you to someone else.
- The work doesn’t shrink with it. A 20% discount doesn’t buy you 20% fewer emails, revisions, or hours. You carry the same delivery risk for less money.
- It changes how the client treats the project. A client who negotiated the price down tends to keep negotiating, because you taught them in week one that the terms are soft.
Reducing scope has none of those effects, and it gives the client a real choice rather than a smaller favour. There are three places to cut, and it’s worth knowing them before the call so you can build the smaller version live:
- Fewer deliverables. Three pages instead of eight. One email template instead of a sequence. This is the strongest cut, because the client can see exactly what they’re not buying.
- Fewer rounds. Drop from two revision rounds to one, and say clearly that additional rounds are priced. Worth real money to you, and it reads as a small trade to them.
- Less finish. You supply the build, they supply the copy. You do desktop and mobile, not tablet. Standard turnaround instead of a fixed date.
What you don’t cut is testing, or the handover. Those are the parts that come back as unpaid support in month two.
The script for the startup version
Sometimes the ask arrives dressed up: exposure, equity, a promise of much bigger work later, a founder rate. Script 10 in the kit handles all of those with the same three offers.
Script 10 · “We’re a startup, can you do it cheaper?”
When: they want the work, they want it cheaper, and they’re offering something that isn’t money.
Hi [Name], I appreciate you being straight about budget. I don’t take equity or exposure in place of fees. I’ve done it in the past and it doesn’t work out well for either side, since it makes every future request a negotiation rather than a job. What I can do: • Reduce scope to fit the budget. Tell me the number and I’ll tell you what it buys. Usually that’s a leaner version, [three pages instead of eight], done properly, rather than the full thing done cheaply. • Phase it. [Core deliverable] now at [$X], [the rest] when the next round closes. • Payment terms. [50/25/25 across three months] if cash flow is the issue rather than total cost. Which of those is worth a conversation? [Your name]
Chat version: “Appreciate the honesty on budget. I don’t do equity/exposure instead of fees, but I can shrink scope to fit a number, phase it, or spread payments. Give me the budget and I’ll tell you what it buys.”
The third option is the one people forget. A large share of discount requests aren’t about the total at all. The client can afford the project but not this month. Splitting the invoice across three months costs you nothing but timing, and it often closes the deal at full price. Ask which problem you’re solving before assuming it’s the number.
Notice that the refusal on equity comes with a reason about how the arrangement plays out later, not a lecture about valuing the work. Clients respond badly to being told they’re disrespecting the craft, and fine to being told the deal causes friction.
When they push back anyway
Some clients will ask a second time, usually with a new argument: it’ll be quick for you, it’s good for the portfolio, the last person charged half that. The kit’s instruction here is short and it works. Don’t invent new reasons. Repeat the options.
“I hear you. Same three choices from my side: a smaller scope at [$X], a first phase now, or spreading the payments. Which of those works?” Saying the same thing twice, calmly and without fresh justification, is what makes the price read as a fact about the work rather than an opening position. New reasons do the opposite. Each one sounds like you’re still hunting for an argument that will convince them, which implies there is an argument that would convince you.
If the answer stays no, let it be no, and leave the door open with a date: “No problem at all. If the budget changes in the next few months, send me a note and I’ll see what my schedule looks like.” A decent share of those come back.
One habit to drop while you’re here. The kit’s pricing file lists the openers that cost the most money: “unfortunately,” “I’m afraid I’d have to charge,” “I hope this is okay, but,” “I know budget is tight, so.” Each one labels your own price as bad news, and the client then answers it as bad news. Write “That’s [$X], and it adds [N days],” then ask a question that isn’t “is that okay?”, then sign your name.
The discount that is actually worth giving
There is a version of this that costs you nothing, because it’s a trade rather than a cut. If the client gives you something with real value, price it in and say so plainly.
- A flexible date. Work you can slot into a quiet week is worth a genuine reduction, because it costs you nothing to do it on your own schedule.
- All content up front. Late copy and missing assets are what turn a two-week project into a six-week one. A client who hands you everything before the start date has removed your biggest delay risk.
- Case study rights. Permission to publish the work, name the client, and quote a result is marketing you would otherwise have to buy.
Write it as an exchange, with an expiry: “I can do [$X] instead of [$Y] if we run it across [March] rather than to a fixed date, and if I can publish it as a case study once it’s live. That offer holds until [date].” Named reason, named amount, named deadline. That reads as a business decision. An unexplained 15% off reads as the first number having been invented.
Try it on the real email
Paste the client’s email
Paste the message where the client pushed back on price and it matches the situation, works the smaller-scope version against your change rate and the half-day minimum, and drafts the reply. Three a day, no signup, nothing stored.
Open the full tool in its own tab if the frame feels cramped.
Script 10 in full, the five pricing settings behind these numbers, and the proposal clauses that make the price harder to reopen later are in the $12 kit.
The other seven situations
- How to tell a client something is out of scope (email template)
- Client keeps asking for extra work: what to say
- Client wants more revisions than the contract says
- Client wants it by Friday 5pm: the rush-fee reply
- Client went quiet after the proposal: the follow-up
- Client keeps adding features mid-project: the change-order reply
- Client hasn’t paid the invoice: the reminder sequence
Or read the three full scripts on the free page, or paste an email into the reply tool.
Questions
Should I ever lower my rate to win a project?
Lower the scope, not the rate. A rate you discount once becomes the rate that client expects forever, and it travels to anyone they refer you to. Ask what budget they had in mind, then build the version of the job that fits it: fewer deliverables, fewer revision rounds, or a first phase now and the rest later.
What do I say when a client has a cheaper quote from someone else?
Ask what is in it. “Happy to look at it. What does their quote include?” Cheaper quotes are usually a smaller job: fewer pages, no revisions named, no testing, content supplied by the client. Once the two lists are side by side you are comparing scope rather than defending a number, and you can offer the matching scope at your rate.
How do I give a discount without devaluing the work?
Attach it to something you get back. A longer timeline that lets you slot the work into quiet weeks, all content delivered before the start date, or permission to publish the project as a case study are all worth a real number. Name the reason in the email, name the amount, and give it an expiry date so it reads as a trade rather than as your price being negotiable.