The quiet moment after someone says yes
There is a gap between the moment a client decides to book you and the moment they actually arrive. In that gap, nothing is binding. The decision was made on a wave of intention—Saturday-morning energy, a New Year's resolution, a wedding three months out—and intentions, as anyone who has ever bought a gym membership knows, cool. The question of whether to ask for a deposit is really a question about what happens inside that gap, and whether you can give the client's future self a reason to honor what their present self promised.
Most solo providers think about deposits in terms of money: protection against the lost hour, the empty chair, the ingredients bought for a no-show. That's real, but it undersells what a deposit actually does. A deposit is not primarily a financial instrument. It's a psychological one.
What a deposit actually changes in the brain
The core mechanism is loss aversion, the finding from Daniel Kahneman and Amos Tversky's prospect theory that losses loom larger than equivalent gains. Roughly speaking, the pain of losing something is felt more sharply than the pleasure of gaining the same thing. Before a deposit, a no-show costs the client nothing they can feel—they simply fail to receive a benefit, and unclaimed benefits are easy to shrug off. After a deposit, skipping the appointment means losing money they already parted with. The same event has been recategorized from a foregone gain into an active loss, and the brain treats those two things very differently.
This is reinforced by what behavioral economists call a commitment device: a step taken in a cool, rational moment to bind your own behavior in a future hot moment when temptation or inertia might win. When a client pays a deposit, they are—often without naming it—using your booking page to pre-commit. They are spending money now so that the version of them who is tired, double-booked, or mildly anxious on the day has a concrete reason to follow through. You are not just collecting funds. You are handing the client a small lever they can pull on their own behalf.
There's a third thread, too. Money paid creates a faint sense of ownership over the appointment. The endowment effect, documented in Richard Thaler's work, describes how we value things more once we feel they're ours. A booked-and-paid slot starts to feel like their slot, a thing they hold rather than a thing they're considering. People defend what they own.
Why "skin in the game" works better than a threat
It's tempting to frame a deposit as a penalty—book carelessly and you'll pay for it. But the more accurate, and more humane, framing is that a deposit gives the client skin in the game. The two feel similar from the outside and are completely different from the inside.
A penalty says: I don't trust you, so I'm protecting myself against you. A deposit, presented well, says: this time is real, and so is yours. The difference matters because of psychological reactance, a concept from Jack Brehm: when people feel their freedom is being threatened or controlled, they push back, sometimes by doing the opposite of what's asked. A deposit waved like a stick can trigger reactance—the client feels policed, and a policed client looks for the exit. The same deposit framed as a shared act of seriousness rarely does, because nothing about their freedom is being threatened. They're choosing to commit, and the page is simply making that choice tangible.
This is why the wording around a deposit does more work than the amount. "A 30% deposit secures your appointment and goes toward your total" lands differently than "A non-refundable deposit is required to prevent no-shows." Both describe the same transaction. One invites commitment; the other braces for betrayal.
How much, and when it backfires
The size of the deposit is a balancing act between two forces. Too small, and it fails as a commitment device—a five-dollar hold on a service worth two hundred isn't a loss anyone feels, so loss aversion never switches on. Too large, and you introduce friction at the exact moment the client is deciding whether you're worth the leap, which suppresses bookings from people who would have happily shown up.
There's no universal number, but the useful heuristic is: the deposit should be large enough to feel like something the client would notice losing, and small enough that handing it over doesn't feel like a gamble on a stranger. For many solo services that lands somewhere between a fifth and a half of the total. The deeper principle is that the deposit should scale with the cost of a no-show to you and the trust the client has in you—a long-standing client needs little; a first-time booking of a high-value, hard-to-refill slot justifies more.
There are also moments to skip it entirely. If your service is low-cost and easy to rebook, a deposit can cost you more in abandoned bookings than it saves in no-shows. If your audience is discovering you for the first time and has no reason yet to trust you with their card, asking for money upfront can read as presumptuous—trust has to be built before it can be spent. And if your cancellation terms are vague, a deposit will feel arbitrary rather than fair. The deposit works because it sits inside a clear, legible agreement; without one, it's just an unexplained charge.
The refund question is really a trust question
Whether the deposit is refundable is where most providers tie themselves in knots, and the resolution is less about policy than about clarity. A deposit that can vanish for any reason undoes its own logic—if the client suspects they might lose it unfairly, the whole thing reads as a trap and reactance returns. The cleaner approach is a stated, predictable rule: the deposit holds the slot and applies to the final cost; cancel with reasonable notice and it moves to another date or comes back; cancel last-minute or vanish, and it's the cost of the time you held for them and turned others away from.
Stated that way, the deposit stops being a punishment and becomes the visible shape of a fair exchange. The client can see exactly what they're agreeing to, which is the only condition under which a commitment device actually feels like commitment rather than coercion.
The point isn't the money
If you take one idea from all this, let it be that a deposit's job is to close the gap between intention and arrival. It does that by quietly engaging three of the most reliable patterns in human behavior—we hate losing what we've given, we honor what we've pre-committed to, and we defend what we feel is ours. The dollars are almost beside the point. What you're really collecting is a small, concrete signal, from the client to their own future self, that this appointment is real.
This is also why a deposit only works when the booking experience around it feels trustworthy and effortless. If taking a deposit means chasing payments over text, sending bank details, or juggling a separate checkout, the friction swallows the benefit. Slate is built so a solo provider can run the whole thing from their phone: the client opens a clean web link, sees the service, the price, and the deposit terms in plain language, and pays as part of booking—no back-and-forth, no app to install, no team overhead. The commitment device and the confirmation happen in the same ninety-second motion, which is exactly where they belong.
If you've been losing slots to people who meant to come and didn't, it may be worth letting a small upfront payment do the quiet work of holding them to their word. You can see how it feels at slate.lumenlabs.works.