Put “satisfaction guaranteed” on your website and you have promised considerably more than you think.
The FTC’s guides on advertising guarantees are specific about it. 16 CFR 239.3(a) says a seller should use the terms “Satisfaction Guarantee”, “Money Back Guarantee” or “Free Trial Offer” only if they refund the full purchase price of the advertised product at the purchaser’s request.
At the purchaser’s request. Not on proof of fault, not subject to review, not if the work was genuinely bad. On request.
Which inverts how almost everybody treats this. The vague guarantee feels like the cautious option, the one you can wriggle out of. It is actually the largest commitment available, and the specific one you were afraid to write is smaller.
What the rules actually require
Two parts, and the second is the one that catches people.
Subsection (a) is the full refund on request, above. Subsection (b) says an advertisement mentioning a satisfaction guarantee should disclose, with such clarity and prominence as will be noticed and understood by prospective purchasers, any material limitations or conditions that apply.
So the conditions cannot live in the small print. If your guarantee requires a complaint within thirty days, that belongs next to the word guarantee, not in a terms page nobody opens. The FTC’s own examples in the same section put the condition directly in the advertising copy: return the unused portion within thirty days for a full refund.
Worth being precise about what these are. They are Guides, which describe practices the Commission considers deceptive, and the Guides themselves say they do not limit the Commission’s authority to act under Section 5 of the FTC Act. So this is not a fine schedule. It is a published account of how your wording will be read if anybody looks, which is a more useful thing to know than a penalty would be.
And while you are in there: if you are tempted by “lifetime”, section 239.4 says you have to disclose whose life you mean. The life of the product, the life of the car, the period of your ownership. Pick one and say it.
So write the specific version, which is also better marketing
Here is where the legal position and the commercial one agree, which does not happen often.
A buyer has read “satisfaction guaranteed” on a thousand websites. It is unfalsifiable, which means it is not information, which means they discount it to zero. It does not increase their confidence and it has never moved a decision.
A guarantee with a named condition does the opposite, because it tells them something they could check. “If we have not produced a working first draft by the agreed date, you pay nothing” is a claim about your own process. It implies you know your delivery times well enough to bet on them.
The specific version is a smaller promise and a bigger signal. That is the whole argument of this post.
It is also the same reason a stated price beats “competitive rates”, which I went through about publishing pricing.
Three shapes that work
A refund with a named condition. One condition, stated in the open, that you can verify without a dispute. A date missed. A deliverable not produced. A defined metric not reached. Avoid conditions that depend on the client’s state of mind, because those are the ones you end up arguing about.
A redo rather than a refund. For service work this is frequently the better trade for both sides. The client wanted the outcome rather than their money back, and you would rather spend time than cash. State a limit: one redo, within a defined window.
A cap on the first engagement. Not a guarantee at all, technically, and it does the same job. “The first phase is fixed at this number and if it runs over, that is ours.” Buyers reading a proposal are mostly afraid of the unbounded version, so bounding it removes the fear without promising an outcome you do not control.
What I would avoid entirely is guaranteeing a result that depends on somebody else. No ranking guarantees, no lead number guarantees. I have said elsewhere that the people promising those are lying, and offering one to look competitive is the fastest way to join them.
Who actually claims, and what it tells you
Few people. In my experience the claim rate on a well-written specific guarantee is low enough that the arithmetic is not the deciding factor, and anybody modeling this as a refund cost is solving the wrong problem.
The more interesting part is who claims. In the cases I have seen, the people who invoke a guarantee are disproportionately the accounts that were mispriced or misscoped at the start: the job you took reluctantly, the client whose requirements never settled, the project you quoted on incomplete information.
Which makes the claim useful rather than merely expensive. A guarantee is a sensor on your own qualification. If you are getting claims, the first place to look is not the guarantee, it is how those engagements were sold.
The cost that nobody budgets
Not the refunds. The arguments.
Here is what actually happens. Your condition was “a working draft by the fifteenth”. You delivered on the fifteenth. The client says it was not working. You say it was. Now you are in a conversation with no referee, about a word nobody defined, with somebody you were hoping would refer you.
That conversation costs a day of your attention and a relationship, and it is the reason to write conditions that are checkable by a third party rather than conditions that sound generous. A date is checkable. A deliverable existing is checkable. “Working” is not.
Every ambiguous word in a guarantee is a future hour of your life. Spend ten minutes removing them now.
The worst Friday test
Here is how I would decide the final wording, and it is the only test I would trust.
Imagine the worst Friday of next year. The project has gone badly, partly through something you did, partly not. Cash is tight. The client, who you still like, emails and invokes your guarantee.
Read your own wording in that moment. Would you honour it immediately and without an argument?
If yes, publish it. A guarantee you would pay quietly is worth something, because the only reason it works as a signal is that buyers suspect you will not.
If your honest answer is that you would push back, look for the ambiguity, or ask them to be reasonable, then do not publish that version. Not because it is unethical, but because the version you would litigate is worth less than nothing: it converts a prospect on a promise and then produces the fight it was supposed to prevent.
Write the one you could live with on a bad Friday. It will be narrower than you wanted and it will do more work than the broad one ever did.
If you’d like a second read on a guarantee before it goes on your site, drop me a line on email, WhatsApp, phone or LinkedIn and we can have a quick chat, and my notes on how I work cover the rest. I’m taking on a small number of contracts at the moment, so I’ll tell you straight whether it’s something I could help with.