@askwhykartik Curious what kind of chasing strategy you used.
I’ve noticed silence and delayed responses behave very differently. Silence usually ends with more losses than recoveries.
Silent clients are harder to deal with than late-paying clients.
At least late payers respond.
Silence creates uncertainty — and that’s what stresses freelancers the most.
#freelancers#buildinpublic#saas
Dropped notifications for my iOS app.
No backend. No cron jobs. No fake reminders.
Everything runs on-device. Urgency shows only when you open the app.
If your product needs notifications to work, it’s weak.
Building a decision engine, not a reminder app.
#buildinpublic
Almost capped disputes.
Then realized — clients don’t behave linearly.
Promise → Delay → Dispute → Repeat.
So I didn’t limit it.
I made every broken promise increase pressure.
Good software survives messy reality.
#buildinpublic#indiehackers#freelancers#saas
Late payments aren’t random.
We combined client behavior + overdue invoices into one signal.
Now it knows how serious it is.
Less invoicing. More recovery.
#buildinpublic#freelancers#indiehackers#cashflow
Most invoice reminder tools are dumb.
They keep chasing clients even after they reply.
Makes you look like a bot.
I’m building something to fix this — starting manual, next step is auto-detecting replies + pausing.
How do you handle this today?
#buildinpublic#indiehackers#saas
@apexstack most tools optimise for paid vs unpaid. they treat payment chasing as a linear process not a feedback loop. In all reality its a conversation without business relationships
Most invoice reminder tools are dumb.
They keep chasing clients even after they reply.
Makes you look like a bot.
I’m building something to fix this — starting manual, next step is auto-detecting replies + pausing.
How do you handle this today?
#buildinpublic#indiehackers#saas