2
36 Comments

Built a free system to stop chasing late-paying clients

Backstory: I kept losing time every month chasing freelance clients who paid late — not because I was bad at invoicing, just because I never had a consistent process for when to follow up, so every late payment turned into its own little decision paralysis.

Built a fixed system instead: a Day 0/7/14 reminder sequence, a late-fee clause that does most of the "hard conversation" for you, and a simple tracker so you stop relying on memory for which clients are actually repeat offenders. Wrote it up as a free playbook, then built out a paid version with the templates and tracker pre-filled for anyone who'd rather not build it themselves.

Just published it as a short Kindle book too (submitted today, live within a couple days) — same content, book form for anyone who'd rather read it that way.

Free playbook + everything else: https://luminous-marzipan-971270.netlify.app

Happy to answer questions on the reminder sequence or the tracker logic if anyone's dealing with the same thing — curious if other freelancers have found different approaches that work too.

on September 22, 2026
  1. 2

    Helpful post. How did you get your first bit of traction?

    1. 1

      No single hack — just commented on threads where people were already complaining about late invoices, no link, just real answers. A few turned into good back-and-forth, which is what pushed me to write it up and post it here. Still early, but the engagement felt real. If you're dealing with late payers yourself, the free playbook's linked in the post above — curious if the day-0/7/14 sequence fits how you work too.

  2. 2

    Late invoices are usually a cash-visibility problem before they are a collections problem. A simple guardrail that helps freelancers: treat expected invoice cash as unavailable until it clears, keep bare-minimum monthly runway separate from the tax reserve, and only count cleared money toward discretionary/build budget. That keeps chasing clients from turning into a panic about next month’s bills. Free lightweight runway/tax estimator if useful: https://runway-desk.pages.dev/estimator

  3. 1

    Day 0/7/14 is a solid default. The part that usually saves the relationship is adding one step before due — a short heads-up with invoice number, amount, due date, and payment link. Most “late” invoices are still sitting in someone’s inbox; the early nudge is visibility, not pressure, so the due-date message does not land like a cold chase.

    Two other guardrails that pair well with your ladder:

    1. On due date, ask one clear question (“Has this reached AP, or is there a blocker?”) instead of another “just checking in.” That diagnoses why it is late before you escalate tone.
    2. Put the late-fee clause in the contract and in the due-date email. Then day +7/+14 is executing terms you already agreed, not inventing a hard conversation under stress.

    The tracker bit matters more than people admit. Without a stop-when-paid rule, you send the stern follow-up to someone who paid yesterday. Fixed cadence + one next action per overdue row beats rewriting the same awkward nudge from scratch every time.

    Curious whether your free playbook treats the pre-due heads-up as optional or part of the core sequence — happy to compare notes on what actually gets a reply without making things weird.

  4. 1

    Solid lesson. Which channel has worked best for you so far?

    1. 1

      still early days, nothing at volume yet — will share once there's real data

  5. 1

    Really solid approach — curious how you're thinking about this, what's been the hardest part to figure out so far?

    1. 1

      Honestly, distribution — building the system was the easy part. Figuring out where people who actually have this problem hang out, and how to talk about it without sounding like an ad, has been the real challenge.

  6. 1

    Solid lesson. Which channel has worked best for you so far?

    1. 1

      still early days, nothing at volume yet — will share once there's real data

  7. 1

    Solid lesson. Which channel has worked best for you so far?

    1. 1

      still early days, nothing at volume yet — will share once there's real data

  8. 1

    Solid lesson. Which channel has worked best for you so far?

    1. 1

      Honestly, nothing yet — still early days. Reddit comments get the most eyeballs, Quora seems to convert later via search, this IH post is my first real self-promo push. Ask me again in a few weeks.

  9. 1

    Solid lesson. Which channel has worked best for you so far?

    1. 1

      Honestly, nothing yet — still early days. Reddit comments get the most eyeballs, Quora seems to convert later via search, this IH post is my first real self-promo push. Ask me again in a few weeks.

  10. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

    1. 1

      Playbook stays free, always. Built a $39 template pack for the DIY-but-faster crowd, and $149 if you want me to just set it up for you.

  11. 1

    How did you decide this was worth building in the first place?

    1. 1

      Kept seeing freelancers turn into part-time debt collectors just to get paid — tracking invoices in a spreadsheet with no reminders, no plan, just hoping. Built a repeatable follow-up system instead of re-deciding every time whether to chase.

  12. 1

    Day 0/7/14 is a good default. The useful part is removing the decision each time; chasing gets delayed when the next action is vague. One guardrail I’d add: after a gap, show one overdue item and one next action, not the whole tracker.

    I’m testing that with ADHD/ADHD-ish freelancers and solopreneurs: free 20-minute observed session, silent watch. I provide a sample overdue with a fake client, amount, and dates. They enter it, see the next action, and see the chase message. Free access, not a sales call. Happy to include anyone this fits.

  13. 1

    Nice work shipping it. What has been the biggest challenge since launch?

    1. 1

      Same one every solo builder hits on Reddit — figuring out which subs actually welcome you talking about what you built vs. auto-flagging it as spam. Lost two posts to the spam filter within an hour before I learned that lesson. IH's been a lot more forgiving since story-first posts are the actual culture here.