Billzy
Simple invoice tracking for freelancers / get paid on time.
-
1
I ran into the same thing with client work, the first question for me was whether the promised date slipped or I was still chasing the wrong person. I tried a sheet first, then Stripe reminders, and now I'm building ChaseFlow for the awkward middle where reminder 2 needs a different tone, tbh your ops-triage framing is dead on.
-
1
I ran into the ownership gap and promised-date bucket the most, those were the invoices that looked like late payment when the real issue was nobody owned the next click. I tried a spreadsheet first, then Stripe reminders, and now I'm building ChaseFlow around that triage layer, ngl the bucket framing is way more useful than a single aging number.
-
1
Priority gap, easily. Most of my late payments were from clients who genuinely intended to pay, but my invoice just got buried. Two things that made a real difference: sending the invoice the same day work is completed (not end of week) and switching from 30-day to 14-day terms. The shorter window created urgency without upsetting anyone.
The ownership gap is sneaky too. Once I started asking "who actually clicks approve?" at the start of a project and adding that person to the invoice email, chasing dropped a lot.
For UK freelancers, there's also a legal angle worth knowing - you can charge statutory interest on late payments under the Late Payment of Commercial Debts Act. Most clients do not know this. I built a free calculator for it at landolio.com/tools/late-payment-interest-calculator if anyone wants to see what they might be owed.
-
1
This is a really good breakdown.
I think priority gap is probably the most common one too, because intent and urgency are not the same thing. A client can fully intend to pay and still let the invoice slide if nothing in the workflow keeps it visible.
Sending the invoice the same day and shortening terms to 14 days both make a lot of sense to me, because they reduce drift before the recovery process even starts.
And I agree on the ownership point too. "Who actually clicks approve?" is such a better question than discovering halfway through chasing that the real approver was never in the loop.
Also useful callout on the UK late-payment angle. Even if someone never uses it, just knowing that statutory interest exists probably changes how they think about delay.
Curious: which change had the biggest impact for you in practice, same-day invoicing, 14-day terms, or adding the approver early?
-
-
1
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.
-
1
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.
-
1
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?
-
1
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.
-
1
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?
-
-
-
1 Comment
I ran into this exact thing with client work, an overdue tag looked useful until I still had to guess whether the next move was nudge, fix missing info, or pull the real owner in. I tried a plain aging view first, then Stripe reminders, and now I'm building ChaseFlow around that next-step decision layer, tbh your 4 buckets are way closer to the real job.