Ask any freelancer who has been at it more than a year or two and they have a getting-burned story. The client who went quiet the week the final invoice was due. The two-month build that ended with "we've decided to go in a different direction" and no payment. The deposit that never came, right before the work that never got paid for. These stories are not rare, and they are not the freelancer's fault β they are the predictable result of doing the work first and hoping to be paid after.
Escrow exists to end that pattern. Paired with milestone payments, it is the difference between taking on a big project and gambling on one.
The problem: work-first, pay-later
The default freelance arrangement quietly puts all the risk on you. You deliver weeks of labour, then send an invoice, then wait β with no leverage, because the one thing you had (the work) is already handed over. If the client vanishes, disputes, or simply cannot pay, you are not inconvenienced; you have a hole in your month or your year.
This is why so many freelancers cap their ambitions at "projects small enough to survive not being paid for." The risk, not the skill, sets the ceiling.
What escrow actually is
Escrow is an old, boring, brilliant idea: a neutral third party holds the money while the work gets done. It is the same mechanism behind property transfers and business acquisitions, now available to independent professionals.
The flow is simple, and the simplicity is the point:
- You and the client agree scope, price, and milestones up front.
- The client funds the project β the money leaves their account and is held by a neutral party. Not with you, not with them.
- You do the work, able to see that the money is real and committed.
- As each milestone is delivered and accepted, the matching funds release to you.
- If a dispute arises, there is a defined process β and critically, the money is already out of the client's discretionary control.
Notice what changed. You are no longer extending an interest-free loan of your labour and hoping. The client is no longer wiring a large sum to a stranger and hoping. Both sides swap hope for structure.
Why milestones make it work
Escrow without milestones is better than nothing; escrow with milestones is what actually protects you. Breaking a project into funded stages does three things at once:
- It limits everyone's exposure. Neither side is ever risking the whole project value β only the current stage.
- It creates a payment rhythm. One distant payday becomes a steady sequence across the project, which is far kinder to your cash flow.
- It forces clarity. Defining milestones forces the scope conversation early β and vague scope is the number-one cause of project conflict.
A few rules for structuring them well:
- Keep each milestone small enough that neither side is overexposed β three to five works for most projects.
- Define acceptance objectively: "homepage delivered in agreed format", not "client is happy".
- Put a review window in the agreement so acceptance cannot be stalled forever.
- Front-load the risky parts as early milestones, while everyone's energy is high.
"Won't asking for escrow offend the client?"
This is the fear that keeps freelancers exposed, and it has the logic backwards. Proposed properly, escrow signals professionalism, not distrust:
- The client's money is not handed over on faith β it releases against accepted work, which protects them too.
- Serious clients recognise the mechanism from property and corporate deals; proposing it puts you in professional company.
- The clients who flatly refuse to fund a project are, statistically, exactly the ones you most needed protection from.
Frame it as process, not suspicion: "I run projects through milestone-funded escrow so we both know the money and the work are secured at every stage." That sentence wins you good clients and filters out bad ones.
Getting burned vs getting protected
Put the two side by side and the choice makes itself. The freelancer who works first and invoices last has effort, a hopeful attachment, and no leverage. The freelancer working through milestone escrow has committed funds, a clear scope, a payment rhythm, and a defined process if anything goes wrong. Same skills, same client β wildly different exposure.
The unlock is bigger than safety. Because non-payment risk is off the table, you can say yes to the two-month build, the full rebrand, the first project with a brand-new or international client β the exact work that grows a freelance business but was previously too risky to touch.
The takeaway
Getting burned is not bad luck; it is the natural outcome of the work-first, pay-later default. Escrow with milestone payments replaces that default with structure: the client funds each stage, you deliver, funds release against accepted work, and nobody has to rely on hope for the money part.
Escrow is built directly into KAZI, powered by Paystack: clients fund milestones, you deliver through the same platform that runs your projects and invoices, and releases happen against accepted work β in Rands or international currencies. We are opening access gradually: join the waitlist at kazii.ai and make your next big project a protected one.