1
0 Comments

This week convinced me invoice tools break on reminder #2, not invoice #1

I spent this week reading a bunch of late-payment and invoicing threads here. Same pattern every time: sending invoice #1 is easy, marking paid is easy enough, the messy part is day 9 when the client goes quiet and you have to decide whether reminder #2 should be soft, firm, or proof-heavy.

I started building ChaseFlow because thats the bit that kept turning into manual memory work for me. Different clients need different follow-up paths, and most tools still stop at sent, overdue, paid.

If youre dealing with the same thing, I put the waitlist here: https://chaseflow-ten.vercel.app?utm_source=ih&utm_medium=post&utm_campaign=ih-roundup-2026-06-07

on June 7, 2026
Trending on Indie Hackers
Most founders don't have a product problem. They have a visibility problem User Avatar 106 comments Day 4: Why I Built a $199 Workspace Nobody Asked For User Avatar 55 comments Hi IH — quick update. The MVP is live. User Avatar 28 comments I Built a Football Sentiment Platform in 18 Days. The World Cup Starts in 7 Days. Now I Need Distribution. User Avatar 17 comments Built an n8n booking alert system — is cold outreach dead for B2B micro-tools? User Avatar 16 comments Day 7: 51 people answered my question. I wasn't ready for what they said. User Avatar 15 comments