Replying when a customer asks for a discount: a calm founder's email
A customer writes asking for a lower price. How a small team can decide what to offer, reply without caving or sounding cold, and keep a record for next time.
On this page(9 sections)
Sooner or later a customer writes: "Do you have any discounts?" or "This is more than we budgeted. Can you do better?" For a small company the message lands in a slightly uncomfortable place. You want the customer. You also know that every price you give away once becomes the price people expect.
The reply you write in the next ten minutes matters less than the thinking you do before it. This post walks through a simple way to decide, a few email shapes that work, and the small habit that keeps one-off exceptions from becoming a mess.
First, find out what the message really means
"Can I get a discount?" can mean several different things:
| What they say | What it often means | Useful response |
|---|---|---|
| "Do you have a discount?" | Asking as a matter of habit | A friendly, honest answer |
| "It's over our budget" | A real constraint | Ask what the budget is, or offer a smaller scope |
| "Your competitor is cheaper" | Comparing, possibly negotiating | Ask what they need, then explain the difference |
| "We're a nonprofit / student / tiny team" | A fair special case | Decide in advance whether you offer anything |
| "I need approval from my boss" | They need something to justify the cost | Give them a clear summary they can forward |
You cannot tell which one it is until you ask. A short question back is often better than an immediate yes or no.
Decide your policy before the next message arrives
A founder who decides each request on the day, while tired, will be inconsistent. Write down three things in a note you can find again:
- What you will never discount. Many teams hold the monthly price and move only on commitment, such as paying yearly.
- What you can offer without asking anyone. For example, a longer trial, an annual plan, or a smaller starting scope.
- Who decides the rest. On a team of one, that is you, but write the rule anyway.
Prefer offers that change what the customer gets or commits to, rather than a raw cut in price. A discount for paying a year up front gives you cash and gives them a saving. A cut with nothing in return gives the customer a reason to ask again next renewal.
Four reply shapes
1. A plain no, kindly. Use it when the price is fixed.
Hi Dana, thanks for asking. Our prices are the same for everyone, which keeps things simple for us and fair for every customer. If the monthly plan is the issue, the yearly plan costs less per month, and I am happy to walk through what is included.
2. A question first. Use it when you need to understand the constraint.
Hi Dana, thanks for the note. Could you tell me a bit about the budget you had in mind, and which parts of the product matter most to you? I would like to find a setup that fits.
3. A trade. Use it when you will move, but want something back.
Hi Dana, I can offer the yearly plan, which comes to a lower monthly price than paying month to month. If you commit to the year, I will also help set up your first domain myself.
4. A forwardable summary. Use it when someone needs approval.
Hi Dana, here is a short summary you can pass on: what the plan includes, what it costs per month and per year, and what you would be able to do from the first day. If your manager has questions, I can answer them directly.
Keep each reply short and warm. Long justifications read as defensive.
What to avoid
- Inventing a discount code on the spot because the pause feels awkward. A silence of an hour is fine.
- Apologizing for your price. You can be gracious without suggesting it is wrong.
- Making claims about competitors. Say what you do, not what others do. For the tone of a firm but friendly refusal, see saying no to customers by email.
- Promising future discounts you cannot keep. "We'll sort something at renewal" becomes a commitment.
- Answering from the phone in a hurry. A rushed price reply is hard to take back. If you read mail on the move, save these for later, as described in triaging email on your phone.
Keep a record
Every exception you grant should be written down somewhere you can find it: who asked, what you offered, why, and the date. A note on the conversation is enough. If your team shares an inbox, an internal note keeps it out of the customer's view while letting teammates see it; the practice is explained in discussing customer email internally.
The record pays off in three ways. You answer the next person consistently. You notice if many customers ask the same thing, which may mean the price or the packaging is off. And at renewal, you remember what you agreed.
When many people ask
One discount request is a negotiation. Ten in a month is information. Look for the pattern:
- Are they all on the same plan, or from the same kind of company?
- Do they mention the same missing feature or the same alternative?
- Do they ask after seeing a particular page?
If the answer is yes, adjust the offer rather than answering each person from scratch. Similarly, the advice in handling feature requests by email applies: count the requests, then decide.
Making the reply easier with an assistant
If you use an AI assistant with your inbox, it can draft one of the shapes above in your voice, using your written policy as the guide. It cannot know what you are willing to offer, so give it the rules and read the draft before you send it. Koltrix drafts are never sent without you clicking send, which is exactly right for a message about money.
A short checklist
- Work out what the customer actually means.
- Ask a question if the constraint is unclear.
- Check your written policy, not your mood.
- Offer a trade, not a bare cut.
- Keep the reply short and friendly.
- Do not promise anything for the future.
- Note the exception on the conversation.
- Review the requests monthly for a pattern.
Key takeaways
A discount request is a conversation starter, not a verdict on your price. Decide your rules ahead of time, ask before you answer, prefer trades that give you something back, and keep a note of what you agreed. Done calmly, the reply protects both the customer relationship and the price.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
