Freelancers of IH — how do you actually deal with a client paying late (or never)?
I'm researching this space (and exploring building in it). If you've freelanced: what did your worst late-payment look like — amount, how late? What did you actually send or do, and did it work? And the question I'm most curious about: how long did you put off sending that first reminder, and why? I'll compile the patterns (the wording and timing that actually got people paid) and post them back here next week.
Trending on Indie Hackers
The thing that changed this for me was moving leverage earlier, before the work is done. A deposit up front, usually 30 to 50 percent, quietly filters the clients who were never going to pay the last invoice anyway. The ones who push back hardest on the deposit are almost always the same ones who go quiet at the end.
Since I come from the dev side, the other piece is that the work lives on my infrastructure until the final invoice clears. Staging, not production. It is not a threat you announce, just how the engagement is structured, and it removes the chasing because nothing ships until payment does.
On your actual question about the first reminder: early on I would sit on it for a week or more, and the reason was exactly the signal problem someone already pointed out here, the reminder felt like it was accusing them. Pushing the first touch to before the due date is what fixed it for me, so by the time anything is late the follow-up is just a status check and not the first awkward contact.
I don't have a useful personal war story here, but one pattern I would separate in the research is whether the first reminder is being asked to do too many jobs.
A reminder after the due date often carries at least three signals at once:
That is why people delay it even when the amount matters. They are not only asking for payment; they are renegotiating the relationship.
The prevention angle is interesting because a pre-due note can be much less loaded. Something like: "Just a quick heads-up that invoice X is due Friday. Do you have everything you need on your side, or is there anything I should resend before then?"
That catches admin blockers without implying distrust. Then if it becomes late, the next message is not the first awkward contact; it is a status follow-up.
So I would probably track three buckets separately:
Those probably need different products. Recovery tools help the first and third. Prevention tools might be stronger for the first two.
This might be the most useful comment on the thread. The "three jobs in one email" framing explains the dread better than anything I've collected — it's not a payment request, it's a relationship renegotiation. And your pre-due wording is genuinely better than what I had: "anything I should resend before then?" catches the missing-PO/approver class of lateness without implying distrust. Underrated side effect: once that pre-due note exists, the day-7 message is a reply in an existing thread, not a cold open — the awkwardness never gets to reset.
One gentle pushback: I'm not sure prevention and recovery are different products so much as different steps of one sequence — a pre-due admin-catcher, then escalating follow-ups if it slips. Same system, same voice, no seam. Your buckets would then drive the wording per step rather than the tool choice. One addition from the stories: client-side "admin delay" also includes payment-tech failures (expired card, blocked transfer) — those need a "let's fix the rail" email, not an intent-probing one. Your taxonomy is going straight into the compilation — thank you.
I'm curious what convinced you the biggest opportunity is helping freelancers recover overdue payments rather than helping them avoid getting into that situation in the first place.
Did your research point more strongly toward recovery than prevention?
Honest answer: nothing has convinced me yet — that's what this thread is for. Early pattern says the prevention/recovery line is blurrier than it looks: the same pre-due heads-up that prevents admin-related lateness becomes step one of recovery if things slip anyway. Holding conclusions loosely until there are more first-person stories in the pile. If you've freelanced (or hired freelancers), your worst late-payment story would help me more than my thesis 🙂
Appreciate the context.
Would be interesting to continue the conversation as you collect those stories.
What's the best email to reach you on?
The delay in sending that first reminder often reveals something deeper - you're calculating whether the client relationship is worth the awkwardness vs. the actual revenue impact. Early reminders signal you value the small payment relative to the relationship; long delays signal you've written it off mentally. The pattern might not just be about payment recovery but about how freelancers assess sunk vs. future cost of managing that client.
This is a sharp frame — and it matches about half of what I'm collecting. The relationship-calculus version definitely shows up: one freelancer described waiting 6+ months on a $300 invoice from a long-term client, fully aware she's trading the money for the relationship. But the other half doesn't look like calculation at all — it looks like avoidance: someone described rewriting the same reminder four times over two weeks without ever sending it. No cost-benefit running. Just dread on a loop.
So maybe the delay has two species: a deliberate write-off (your model) and a paralysis spiral (no model at all). One design consequence I find interesting: a heads-up sent before the due date carries zero relationship signal — the calculus never gets to start.
Did you freelance yourself? Curious whether you've ever caught that calculation running live — and what tipped it either way.