Freelance builders · 2026

What to do when a freelance client won’t pay

Direct answer: stop new work the same day, keep staging and source under your account, send a dated payment deadline, then escalate. Do not “finish a few more features” to win them back — that is how unpaid CRMs get built.

1. Same day — freeze the bleed

• No new commits, no “quick fixes,” no free training calls.
• Confirm who owns hosting and the repo. If it’s you, leave it that way.
• Write down: invoice number, amount, due date, what was delivered, staging URL.

2. Day 1–7 — remind, then firm deadline

Day 1: assume oversight. Day 7: one firm date. Offer a payment plan only if they reply with a real date — not vibes. Attach the invoice every time.

3. Day 14 — pause work in writing

Send a pause notice: further work and production handover stop until the balance clears. This is the line most builders never draw — and why “we’ll pay when we know next steps” becomes months of silence.

4. The phrase that means trouble: “we don’t know what to do next”

After you delivered the agreed scope, that sentence is not a product failure by default. It is a decision point: close and pay, book a paid walkthrough, or pause. Treat it like a change in commercial terms, not a request to keep coding for free.

5. Prevent the next unpaid build

• 50% deposit before kickoff — non-negotiable for new clients.
• IP and production transfer only after full payment.
• Two revision rounds max; everything else is a Change Order.
• Staging on your account until money clears.

FAQ

Can I withhold a website until I’m paid?

If your agreement says IP and production handover transfer only after full payment, and you still control hosting/repo, pausing handover is enforcing the deal — not sabotage. Put that clause in writing before you start.

Client says they don’t know what to do next. Do I keep building for free?

No. Delivered scope is delivered. Offer: close phase + final invoice, a paid walkthrough, or a formal pause.

What if we never signed a contract?

Email proposals and accepted scopes still matter. Send a clear demand with dates and amounts. For the next job, do not start without deposit + written scope.

Are invoice email templates enough?

They help after the invoice is late. Most builder losses happen earlier — when GitHub, Vercel, and admin access move before final payment.