What 30+ freelancers taught me about getting paid — and the tool I'm building from it

Two weeks ago I asked this community how freelancers actually deal with clients paying late. It turned into the best thread I've been part of on IH — 25+ comments, three mini-interviews, and a pattern write-up I posted back into the thread as promised: https://www.indiehackers.com/post/freelancers-of-ih-how-do-you-actually-deal-with-a-client-paying-late-or-never-55972ef40e

Today I'm doing the second half of what I said I'd do: building from it. In public, starting with this post.

What the stories actually said

Four findings shaped everything:

It's almost never forgetting. It's a buried email, an avoidance spiral (one person rewrote the same reminder four times and never sent it), or what got named "the creditor switch" — the reminder turns you from collaborator into collector, so you stall. And every un-enforced deadline quietly teaches the client that deadlines don't matter.
The bottleneck is the writing, not the remembering. Calendar reminders collapse the moment 3–4 invoices are open at once. The alarm fires; the awkward email still has to be drafted; it gets snoozed.
One law, said five different ways: a system, not a decision · policy, not personal · process, not courage · structure, not threats · process, not punishment. Everything about enforcement gets established before enforcement — the late fee announced at signing almost never needs charging.
An invoice needs to be a visible status with a next action — not a line in a spreadsheet you have to interrogate.

So this is Duebell → https://duebell.co

Polite, escalating invoice reminders that go out in your name and stop the instant your client replies. The sequence is basically the thread, productized:

A pre-due heads-up that catches admin blockers — "anything you need from my side, a PO number, a re-send?" (that exact wording came from this community)
Day-after-due first nudge — because "waiting longer has never improved the relationship"
A firmer note with a diagnostic menu — "waiting on an approver, a PO, or a payment-run date?" — so the client can answer in five seconds
A final status reset, not a threat — "I'm marking this unresolved unless I hear back by [date]"
Every email waits for your approval. Amount + link in the first lines, one specific date, framed around the deliverable. No QuickBooks, no client-facing portal, and it never touches the money — you keep whatever payment rails you already use.

Founding 20 — and why I'm charging before it exists

The build starts now; doors open early September. I'm opening 20 founding spots at $9/mo locked forever (launch price is $19). It's a real charge today — because after two weeks of research, the one thing stories can't tell me is whether this is worth paying for. Only a checkout can. So: full refund anytime before launch and 14 days after, no questions, just reply to my email.

Founding members also get the first vote on what ships after core — the three candidates that came straight out of the research: a Terms Card that writes your payment-terms paragraph and then enforces it, a "billing voice" option for the firm stages, or autopilot for reminder #1 only.

Two asks (besides the obvious one):

If you've freelanced: tear the landing apart. Does it read like the problem you've actually had?
And I'm still collecting stories — if a client went quiet on you recently, the research thread is still open.

Thanks again to everyone who answered the original question. You wrote half of this product before I did.