Table of Contents
The advance is the single most protective structure in service business — and the one new freelancers are shyest about. An advance filters serious clients from browsers, funds your upfront costs, compensates your reserved capacity, and converts "interested" into "committed." This guide covers designing the policy: how much to ask, when it's refundable, how to word it, and how to answer the objections.
What an Advance Is Actually For
Four distinct jobs, worth understanding because they justify the policy:
- Commitment filter — money is the only inquiry qualifier that never lies
- Capacity compensation — a booked date/slot is inventory you stop selling; the advance prices that reservation
- Working capital — decorators buy flowers, caterers buy provisions, everyone spends before delivery
- Risk sharing — the client's skin in the game against cancellation, yours against wasted preparation
How Much: The Bands by Business Type
- Event services (photo, makeup, DJ, mehendi): 30–50% to block the date — the industry spine
- Material-heavy work (decor, catering): 50% at confirmation, because your spend curve front-loads; often a second pre-event instalment
- Projects (design, development, consulting): 30–50% to start; milestone instalments after
- Small-ticket sessions and first-time clients: 100% upfront is normal and increasingly standard
- Retainers: first month in advance, always
Below 30%, the advance filters nothing and funds nothing; above 60% (outside materials businesses), client resistance rises without adding protection.
Refundable or Not: Say It Precisely
The default for date-based businesses: non-refundable, because the date is inventory. Two wording rules with legal weight:
- Call it a retainer or booking fee, not a "deposit" — deposits imply refundability in many contexts; a retainer is earned on receipt in exchange for reserving capacity
- Write the earned-consideration line: "The booking retainer is non-refundable and is earned upon receipt as consideration for reserving the date and declining other engagements." That sentence, agreed before payment, is the whole enforceability game.
Then layer fairness on top — it's what makes the policy defensible and referrable: one free reschedule with notice, transfer to a future date at your discretion, and full refund if you cancel. The cancellation-policy framework supplies the complete scale.
The Paperwork Sequence
Contract → signature → advance → date blocked. In that order, always:
- The signed agreement contains the advance and cancellation terms (terms agreed after money moves protect no one)
- The advance gets a proper receipt — receipt voucher if GST-registered — showing amount, what it reserves, and balance remaining
- The final invoice later shows the advance deducted, closing the loop visibly
"Date blocked once the signed confirmation and advance are in" is a sentence that does more collecting than any reminder ever will.
Handling the Objections
"Why should I pay before the work?" — "The advance reserves your date exclusively; from that moment I turn down other bookings for it. The balance is only due [before delivery/on the day]." Calm, structural, done.
"What if we cancel?" — Point to the written scale: what's retained, what the free-reschedule covers. Fairness in writing beats reassurance in tone.
"We'll confirm now, pay later." — "I completely understand — and the date stays open until an advance lands, for everyone. I'd hate for you to lose it." True, kind, and the deadline is theirs now.
Corporate "we can't do advances." — Often false at the process level: a proforma invoice usually unlocks it. Where genuinely impossible, compensate with milestone billing and Net-15 terms.
Track Advances Like the Liabilities They Are
An advance is money you hold against future delivery — across a season of overlapping bookings, memory fails exactly here: what's been paid, by whom, against which event, with what balance. Every advance recorded against its booking with the balance visible — Brightdesk does this automatically, free — turns your advance policy from a good intention into an operating system.