I think a lot of overdue recovery gets treated like a series of isolated annoyances.
Missing PO this time.
Wrong contact this time.
Promised date slipped this time.
Finance was not copied this time.
But the more I work on Billzy, the more I think one pattern matters a lot:
if the same payment issue happens twice, it should probably stop being a reminder and start becoming a rule.
Why?
Because once an issue repeats, it is no longer just bad luck.
It is part of the operating reality for that client.
And if it is part of the operating reality, the workflow should change.
For example:
- if AP needs to be copied twice, make it the default
- if the client misses promised dates twice, tighten the next invoice
- if paperwork is missing twice, make it a required pre-send check
- if the invoice only moves once the approver is named, ask for that name earlier every time
That feels much more useful than collecting the same lesson over and over.
I think this is where a lot of receivables pain stays more manual than it should.
People notice the pattern.
But the pattern never graduates into a rule.
So the next invoice goes out with the same setup,
the same friction appears,
and the team acts surprised even though the signal was already there.
That is one of the product ideas I keep circling with Billzy too.
Not just:
"what happened?"
More like:
"has this happened enough times that the system should stop relying on memory?"
That is a much more useful threshold to me.
Because reminders are fine for one-off issues.
Rules are better for recurring ones.
And I think a lot of founders wait too long to make that switch.
This applies outside invoicing too.
Any repeated operational friction is basically asking the same question:
is this still a one-time exception,
or is it already a system rule hiding in plain sight?
Curious how other founders and freelancers think about this:
What repeated payment issue would you turn into a hard rule first: missing AP, missed promised dates, missing paperwork, or unclear owner?