Most overdue invoices are really an ownership problem
Most people treat late payment like a reminder problem.
Send a better email.
Follow up faster.
Ask for a date.
Those things matter.
But the more I work on Billzy, the more I think a lot of overdue invoices are really an ownership problem.
Nobody clearly owns what happens next.
The invoice was sent by one person.
The work is managed by another.
Approval sits with someone else.
Accounts payable may not even be in the thread.
So you follow up and get something like:
"We're processing it."
"Finance is handling it."
"I'll check internally."
That sounds like movement.
But a lot of the time it just means the next step is floating between people.
That is why I think a useful follow-up should not just ask for status.
It should surface ownership.
Who is approving this?
Who is processing the payment?
Who should be copied to get this closed?
If you do not know who owns the next action, the invoice is still at risk no matter how polite or clear the reminder is.
That has become a product lesson for me too.
The real job is not just sending nudges.
It is making the next owner visible.
Because once there is an owner, the conversation changes.
No owner = vague reassurance.
Named owner = a next step you can actually track.
This feels bigger than invoicing.
A lot of business bottlenecks are not caused by disagreement.
They are caused by missing ownership.
Everyone assumes someone else has it.
So the work sits still while the thread stays active.
If I were writing an overdue follow-up today, I would want it to answer 2 things:
1. What date should I expect payment?
2. Who owns getting this done?
That is a much stronger position than just asking for another update.
Curious how other founders handle this:
When payment gets stuck, do you push for the date first or for the name of the person who owns the next step?
I had this exact issue with client work, the reminder copy wasnt the blocker, it was never knowing whether AP, the project lead, or the founder actually owned the next move. I tried generic reminder sequences first, then Stripe nudges, and now I'm building ChaseFlow around surfacing that owner before reminder 2, imo the name question changes the whole thread.I had this exact issue with client work, the reminder copy wasnt the blocker, it was never knowing whether AP, the project lead, or the founder actually owned the next move. I tried generic reminder sequences first, then Stripe nudges, and now I'm building ChaseFlow around surfacing that owner before reminder 2, imo the name question changes the whole thread.
This really resonates. When I was freelancing, I learned this the hard way — chasing late payments by just sending "friendly reminders" almost never worked. The problem was exactly what you describe: nobody on the client's side felt personally responsible for paying me.
What eventually worked for me was asking for the name upfront. Not just "when will this be paid?" but "who specifically is going to process this?" Once you have a name, the dynamic shifts completely. You're no longer emailing into the void. You have someone accountable.
I actually started building this thinking into the invoicing tool I'm working on now. Instead of just tracking "sent" and "paid," we track who the invoice is assigned to on the client side. Small change, but it makes follow-ups way more effective.
To answer your question directly: I push for the name first. Once you have ownership, the date usually follows naturally.
I agree with this a lot.
"Who specifically is going to process this?" is a much stronger question than most people ask, because it turns a vague thread into an owned step.
That's the part I find most interesting too: once there'ss a name attached, the conversation usually gets more concrete very quickly. The date becomes easier to ask for because there is now someone connected to the outcome.
I also like that you are building this into your tool. Tracking client-side ownership feels small on paper, but operationally it changes a lot because it gives follow-up a target instead of just a status.
That's a big part of how I’m thinking about Billzy too: less “is this paid yet?” and more “what is still unclear, and who owns removing that uncertainty?”
Curious: when you started asking for the name first, did clients usually give it right away, or did that itself require another round of follow-up?
Good question. Honestly, it was mixed. Smaller clients (solo founders, small agencies) would usually give you a name pretty quickly because there's only 1-2 people who handle payments anyway. The friction was low.
Bigger companies were a different story. The first response was almost always "I'll check" — which is really just a nicer way of saying "I don't know either." But even that response was useful, because it surfaced the real problem: nobody had ownership. That realization alone changed how I framed follow-ups. Instead of "any update?" I'd say "who should I loop in to get this resolved?"
It usually took one extra round. But once I had a name, the next invoice to the same client went smoother because I already knew the path.
This is a really useful distinction.
"I'll check" is exactly the kind of reply that sounds helpful but usually reveals the real issue: the ownership path is still fuzzy.
That is why I think even a weak reply can still be useful if it exposes the right uncertainty. Once it becomes clear that nobody actually owns the next step, the follow-up gets much more specific.
I also like the point about the next invoice going smoother. That feels important because part of the value is not just recovering the current invoice, but learning the payment path for the client so the same friction does not repeat.
"Who should I loop in to get this resolved?" is a much better line than another generic update request.
Curious: once you had the name, did payment speed improve mainly because follow-up got more direct, or because you could start future invoices with the right person already included?