When a Client Asks for a Refund (The Exact Reply to Send)
- A refund request is a symptom. Diagnose which of the three causes it is - unmet expectation, timeline, or a change on their side - before you say anything about money.
- Reply fast, acknowledge the frustration, do not concede fault in the first message, ask one question, and propose a concrete next step. Silence is what escalates a request into a dispute.
- Decide your refund position before the conversation, not during it. Work delivered is work owed. Work not started is money you should return without a fight.
- Write the terms that prevent the next one: milestone payments, a written acceptance step, and a change log that makes scope creep visible while it is happening.
The Three Reasons Behind Almost Every Refund Request
The word refund is doing a lot of work in that email, and it is usually covering something more specific. Before you reply, work out which of these you are actually dealing with, because the right response for one is the wrong response for the others.
- The build does not do what they thought it would. This is an expectation gap, and it is the most common by a distance. It is also the most fixable.
- It took longer than they were told. This is a trust problem, not a product problem. The work may be perfect and they still want out.
- Something changed on their end. Budget got cut, priorities moved, or the person who championed the project left. Nothing you built is wrong.
You cannot tell which one it is from the word refund. You can usually tell from what they mention first. If they describe a feature, it is an expectation gap. If they mention dates, it is timeline. If they are vague and apologetic, it is almost always a change on their side.
Reply Within 24 Hours, Even If You Have No Answer
Delay is what converts a refund request into a payment dispute. A client who has asked for money back and heard nothing for four days stops thinking of you as a person to negotiate with and starts thinking about their card provider. Whatever else you do, get a reply out within a day.
You do not need to have decided anything yet. Confirming receipt and giving a date when you will respond properly is enough to keep the conversation inside the relationship instead of escalating outside it.
The Four-Part Reply
Every refund reply I send has the same four parts in the same order. The order matters more than the wording.
- Acknowledge the frustration without accepting fault. You are recognizing how they feel, not agreeing that you failed.
- Restate what was agreed, factually and without defensiveness. Reference the actual scope document or proposal, quietly.
- Ask one question that identifies which of the three causes this is. One. A list of questions reads like a legal defense.
- Offer a specific path forward that is not a refund, while making clear you will discuss the money if that path does not work.
Here is the shape of it: I am sorry this has not landed the way you hoped, and I want to sort it out. The original scope covered the three deliverables we agreed in June, and those are built and live. Can you tell me specifically which part is not doing what you need? If it is something inside the agreed scope I will fix it this week at no cost. If it turns out to be outside it, I will tell you honestly and we can talk about the options, including the money.
Deciding Your Actual Refund Position
Decide this before you open the conversation, because deciding mid-thread is how people give away money they were owed or dig in on money they should have returned.
| Situation | Position | Why |
|---|---|---|
| Work delivered and accepted | No refund, offer to fix in-scope issues | The value transferred. Fixing is fair, refunding is not. |
| Work delivered, never reviewed | No refund, but restart the acceptance process | They may simply not have looked at it yet. |
| Partially built, client changed direction | Refund the unstarted portion only | Hours spent are hours owed. Hours not spent are not yours. |
| Paid, nothing started | Refund in full, immediately | There is no argument here and fighting it costs you more than the money. |
| You genuinely under-delivered | Refund and say so plainly | Your reputation is worth more than one invoice. |
A defensible refund position by project state
That last row is the one people avoid. Sometimes the honest answer is that you overcommitted, the build is not good enough, and the client is right. Refunding fast in that situation costs you one project and buys you the ability to keep looking people in the eye. Dragging it out costs you the same money and your reputation with it.
When to Just Pay It
There is a threshold below which arguing is a bad trade even when you are right. Work out what your hours are worth and compare that against the disputed amount. If a week of back-and-forth to defend a small invoice would cost you more in lost billable time than the invoice itself, that is not a principle worth defending, it is an expensive hobby.
The other case for paying quickly is anyone with a public voice in a market you sell into. That is not weakness, it is arithmetic. A single well-placed complaint from someone with an audience can cost you several projects you will never hear about.
The Terms That Prevent the Next One
Most refund requests are structural. The build did not go wrong at the point the client complained, it went wrong weeks earlier when nobody wrote down what done meant. Four things fix nearly all of it.
- Milestone payments instead of a single sum. Smaller amounts in dispute, and a natural checkpoint where problems surface early.
- A written acceptance step per milestone. The client confirms in writing that the milestone met the spec before you move on.
- A dated change log for every request outside the original scope, with an estimate attached. Scope creep becomes visible while it is happening rather than at the end.
- A refund clause in the agreement that says what is refundable and what is not. Boring to write, and it removes the entire argument later.
This is the same discipline that stops a build from quietly overrunning in the first place, and it is worth reading alongside [a scope of work that prevents scope creep](/blog/scope-of-work-that-prevents-scope-creep) if your quotes are where the expectation gap starts.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
Should I give a refund if the client just changed their mind?
Refund the portion you have not started and keep the portion you have delivered. Hours already spent are owed regardless of why they changed direction, but holding money for work that will never happen is what turns a mild parting into a dispute.
How fast should I reply to a refund request?
Within twenty four hours, even if you have not decided anything. A short message confirming you have seen it and giving a date for your full response keeps the conversation between the two of you instead of escalating it to a card provider.
What if the client threatens a chargeback?
Reply calmly and in writing, restate the agreed scope, and put a specific offer on the table. Keep every relevant message, the signed scope, and the delivery evidence in one place. Providers weigh documented delivery heavily, and a clear paper trail is worth more than a strongly worded email.
Should I refund a client who is difficult but not actually wrong?
Compare the disputed amount against what the argument will cost you in billable hours and attention. Below that threshold, paying and moving on is usually the better trade even when you would win.
How do I stop refund requests happening at all?
Bill in milestones, require written acceptance at each one, keep a dated change log with estimates for out-of-scope requests, and put a refund clause in the agreement. Most requests trace back to nobody having written down what done meant.
Last reviewed August 13, 2026.
Co-founder of the Claude Code Profit Room. Went from shipping software to closing paying clients, and now teaches builders the selling half of the equation.
More from David Iya →
