W1-4 dev.to
Eleven weeks. That's how long the last one took, from the first missed invoice to the money landing. I'm writing it down because during those eleven weeks I couldn't find a single account that described what it actually feels like, and most of the advice I found was written by someone who had never had a client go dark on a $4,200 invoice.
So: what happened, what I did in what order, and what I'd do differently.
Week 0: the first missed invoice
Invoice due on the 15th. On the 18th, a one-line email: "Just saw this, will get it processed this week."
This is the stage where most freelancers do nothing, because it feels rude to chase. That's the mistake. Not because the client is lying — they might not be — but because the silence set the expectation. Meanwhile I was already doing new work for them, which meant the leverage I had (unfinished deliverables) was disappearing.
What I should have done: stopped work the day the invoice went past due, and said so plainly. One sentence: "Pausing the current sprint until invoice #1042 clears — happy to resume the moment it's settled." That's not aggressive. It's a fact about cash flow.
What I did: sent a polite nudge. Sent another a week later. Kept working.
Week 3: the second missed promise
"We're waiting on a client payment ourselves, should clear by Friday."
Now the story changed shape. It wasn't an admin backlog, it was a cash-flow problem. That's important information, and it changes the strategy entirely — you're no longer chasing a process, you're now a creditor.
What I should have done at this point: moved to written formality. Not hostile, formal. A short email restating the invoice number, amount, original due date, and asking for a payment date. Written down, with a date in it. This creates a record, and records change behavior.
What I did: replied sympathetically. Which was, in retrospect, the third time I'd signaled that the deadline was negotiable.
Week 6: the disappearing act
Two emails, no reply. Then a reply that was warm and apologetic and contained no payment date at all.
This is the phase where the emotional cost exceeds the financial one. You start drafting emails five times, you start wondering if you were somehow at fault, you start avoiding the situation because confronting it feels worse than the money.
The thing that helped: separating the two questions. "Will I get paid" is out of my control. "Have I done everything a reasonable person would do" is entirely in my control, and I could answer it. Once I'd done every item on that list, the anxiety dropped even though nothing was resolved.
Week 8: the escalation
I sent a final notice. Specifically:
- Invoice number, amount, original due date
- A summary of every contact attempt with dates
- A clear statement of what happens next (in my case: suspension of all work, and referral to a collections process)
- A stated deadline — 7 days
- Professional tone throughout, no sarcasm, no accusation
The key word is specific. "If this isn't resolved I'll take further action" is noise. "If payment hasn't cleared by the 14th I'll suspend all work and refer the invoice to collections" is a sentence with consequences in it.
Week 11: payment
They paid, in two installments, after the escalation. No drama. The relationship didn't survive, but eleven weeks of my life came back.
The timeline, compressed
| Week | What happened | What I did | What I should have done |
|---|---|---|---|
| 0 | Invoice 3 days late | Polite nudge | Stop work that day |
| 3 | Second broken promise | Sympathetic reply | Formal written notice with a date |
| 6 | Client goes quiet | Kept emailing | Send final notice now, not at week 8 |
| 8 | Two weeks of silence | Final notice + 7-day deadline | — |
| 11 | Paid in 2 installments | — | Should have happened at week 3 |
Every delay in that table is mine, not theirs. The client was slow to pay. I was slow to escalate. Only one of those was under my control.
What I'd do differently, in order
- Stop work the day it goes past due. No exceptions, no "just this one sprint." This single change would have saved me eight of those eleven weeks.
- Put a date in every message. Never end a payment email without one. A message without a date is a message that can be ignored for free.
- Keep one file. Invoice, every email, every promise, every date. When you eventually need it, reconstructing it from memory costs hours and you'll get details wrong.
- Decide your escalation point before you need it. Mine was day 60. Having decided in advance meant the decision wasn't made while I was emotional.
- Charge a late fee, and put it in the contract. I didn't, and the absence of any contractual cost made the invoice genuinely optional for eleven weeks.
The part nobody writes about
The client was not a villain. They were a small agency in a cash crunch who handled it badly, which is what most non-paying clients are. The reason this is worth writing down is that the standard advice — "be firm, be professional" — doesn't tell you when, and when is the whole question.
FAQ
At what point do you stop being polite and get formal?
The first missed promise, not the third. Politeness that persists past a broken commitment stops reading as professional and starts reading as optional.
Is collections worth it for a small invoice?
Generally no below a few thousand dollars — the cost and time usually exceed recovery. But saying you'll refer it is worth doing, because the sentence does work even when the process wouldn't.
Should I have kept working to preserve the relationship?
No. This is the single most expensive instinct in freelancing. Continuing to deliver removes the only leverage you have, and the relationship you're protecting is one where you don't get paid.
Does a late fee actually help?
Yes, but not because you'll collect it — because it changes the default. An invoice with no cost for being late is a request. One with a cost is an obligation.
What if the client is genuinely in trouble?
Then they're a creditor situation, and you treat it like one: written terms, a payment plan in writing, and no new work until the plan is honored. Sympathy is fine. Free labor is not.
I write about the operating side of freelance work at AIXHDD. Related: the full freelance late payment playbook, including the exact email templates I used.
