Most freelancers obsess over the invoice.
That’s backwards.
By the time you send an invoice, the money conversation should already be finished. The invoice is a receipt for something both sides already agreed — not a hope that finance will invent a due date for you.
I wrote separately about what to do when payment is already late. This post is the stack that makes “late” less common: four boring documents you send before kickoff.
1. A short services agreement (not a novel)
You don’t need twenty pages of recycled legalese. You need clarity on:
- Who the parties are (legal names)
- What you’re selling at a high level
- Fee, currency, deposit, when you invoice, due dates (Net 7 / Net 14 beats “ASAP”)
- What happens if they cancel mid-project (kill fee)
- Whether you can pause work if payment is overdue
- When IP transfers (usually on full payment) and portfolio rights
Keep it plain English. If the project is large or regulated, get local counsel. For everyday freelance work, a short agreement beats a vague chat t
“Homepage + four inner pages in Figma, two revision rounds, stock photos provided by client” is scope.
When something new appears mid-project, you don’t argue vibes. You point at the SOW and quote a change order.
3. An invoice template finance can actually pay
Blank or half-finished invoices create delay. AP pays what they can process.
Minimum fields I reuse every time:
- Your legal / business name and contact
- Client name and project name (matching the agreement)
- Invoice number, issue date, due date
- Line items tied to the SOW (not vibes)
- Payment methods that work for them
- A one-line reference to the agreement / late fee if you use one
I keep the same invoice in Word, Excel, and a simple HTML version for email. Matching the client’s preferred format removes one excuse.
4. Payment follow-up emails written when you’re calm
When money is overdue, emotion is expensive. Process is cheap.
I reuse the same sequence:
How the four fit together
Agreement + SOW before work.
Invoice that matches those documents.
Follow-ups that don’t invent new rules mid-chase.
If you only fix one thing this week: send the agreement and SOW before kickoff, and put a real due date on the invoice. That alone beats another round of “just circling back.”
I packaged the templates I actually use (agreement, SOW, invoice formats, and those Day 0/7/14 emails) into a $5 starter pack here: https://kitdesk.carrd.co
Steal the process even if you write your own files. The win isn’t the PDF — it’s sending the right paper before the work starts.
- Day 0 overdue: polite reminder + invoice reattached + payment details
- Day 7: firmer note that references the payment terms you already agreed
- Day 14: pause-work / final notice — only if your agreement allows it
Write these once. Reuse them. You’re not being cold; you’re being consistent.hread.
Buy Freelancer Kit ($5) — contract, SOW, invoice templates + payment emails: https://workspace50.gumroad.com/l/cpzjm
2. A one-page scope of work (with out-of-scope)
This is where unpaid “one more tweak” dies — or thrives.
Good SOW lines look like: deliverables, formats, revision rounds, assumptions, timeline dependencies on client feedback/assets, and a short out-of-scope list.
“Website redesign” is not scope.
Top comments (0)