███╗   ███╗ ██╗   ██╗  ██████╗ ███████╗ ██╗
████╗ ████║ ╚██╗ ██╔╝ ██╔════╝ ██╔════╝ ██║
██╔████╔██║  ╚████╔╝  ██║      █████╗   ██║
██║╚██╔╝██║   ╚██╔╝   ██║      ██╔══╝   ██║
██║ ╚═╝ ██║    ██║    ╚██████╗ ███████╗ ███████╗
╚═╝     ╚═╝    ╚═╝     ╚═════╝ ╚══════╝ ╚══════╝
DemoAcademyPricing
Sign inBook a meeting

Running an agency · August 28, 2026 · 7 min

Chasing an invoice without losing the client

Most overdue invoices are not a refusal to pay — they are an invoice that reached one person who is not the person who pays. A four-rung ladder where the escalation is in the specificity rather than the tone, the three rules underneath it, and the four things to fix before you fix the chasing.

By Islam Hachimi, Founder

Most overdue invoices are not a refusal to pay. They are an invoice that reached one person, who is not the person who pays, and who has not thought about it since.

Which means the thing that gets you paid is rarely a firmer tone. It is a specific ask, sent to somebody who can act on it, on a schedule you do not have to remember.

Why it feels awkward, and why that instinct is wrong

Chasing feels like asking for a favour. It is not. You did work, they agreed a price, and a date passed. The awkwardness comes from a real fear — that pushing costs you the relationship — and the fear is worth taking seriously, because it is what stops most people chasing at all.

The resolution is that the thing which damages a relationship is not the chase. It is the SURPRISE. A client who hears nothing for six weeks and then gets a letter about late payment interest has been ambushed. A client who got a friendly note on day three, a specific question on day ten, and a clear statement of what happens next on day twenty-one has been kept informed, and nothing that arrives is a shock.

A ladder that works

Four rungs, and the escalation is in the SPECIFICITY rather than the tone.

Day 3 after the due date — assume it is admin

Short, friendly, no apology and no chasing language. Attach the invoice again, because the most common reason it is unpaid is that it is in somebody's archive. Ask one question: is there anything you need from us to get this processed.

A third of overdue invoices resolve on this one. It costs nothing and it is the cheapest money in the business.

Day 10 — find the right person

This is the rung most people skip, and it is the one that does the work. Your day-to-day contact is often not the person who pays. Ask directly: should I be sending this to your accounts team, and do you have a purchase order number I should quote.

"Who should I send this to?" is not an escalation. It is a favour to somebody who has been meaning to forward it for a week and feels slightly bad about it.

Day 21 — state what happens next

Still not angry. Now specific about consequence: work pauses on a date, or late payment interest applies from a date, or the next month's retainer does not start. Whatever your terms actually say — and if your terms do not say anything, that is the real problem and no email fixes it.

Name the date. "We'll need to pause on the 14th" is actionable. "We may need to pause work" is not, and everyone knows it.

Day 35 — a person picks up the phone

Not another email. By this point email has been tried four times and the information you are missing is not something email will give you: either they cannot pay, or something is wrong with the work and nobody wanted to say so.

Both of those are conversations, and both are better had at day 35 than at day 90.

The three rules underneath the ladder

  • Stop the moment they reply.Any reply, including "sorry, chasing our finance team". A sequence that keeps sending after a human answered is the single fastest way to make a late payment into a lost client, and it is what almost every automated chaser gets wrong.
  • Never chase a disputed invoice. If they have raised a problem with the work, the ladder stops and a person takes over. Chasing money over an unresolved complaint is how you lose both.
  • One ask per message.Not "please pay, and also can you confirm the PO, and let me know about next month". A message with three asks gets zero answers.

What to fix before you fix the chasing

Chasing is downstream of four things, and two of them are usually the actual problem:

  • Terms on the invoice, in words. "Payment due within 14 days" beats "Net 14" for anyone outside finance.
  • The payment method they prefer. A bank transfer to a company that pays by card is a two-week delay that has nothing to do with willingness.
  • A purchase order number, collected before the work starts. At a company that needs one, an invoice without it does not enter the system at all. It is not late; it is invisible.
  • The right recipient from day one. Ask at kickoff who invoices should go to. It is a normal question at the start and an awkward one at day 21.

Fixing the PO question alone removes a meaningful share of what looks like late payment and is actually a filing failure.

Why automate it at all

Not because a machine writes a better chase. It does not. Because the failure mode of manual chasing is not a badly-worded email, it is silence: the invoice that nobody sent a note about on day three because that week was busy, and then day ten felt too late to start.

The value is the schedule being kept when you are not thinking about it, and the stopping rule being obeyed when you are. Both halves matter, and the second is the one worth checking before you trust any tool with it.

Everything described here is in the kernel that runs Mycel — the scheduler, the wedges, the guards, and the tests that hold them.

Read the kernel →More writing →

Read next

  • How to tell if AI work is actually getting betterOne number tells you whether AI is doing your client work or drafting near it: how much of each draft you rewrite before it goes out. If it is the same in month three as in month one, you bought a tool, not a colleague — and most vendors have never measured it.
  • Why your cold email stopped arrivingCold email rarely dies from one bad day. It dies from a fortnight of small mistakes — a ramp that looks like a leak, a sequence that retries dead addresses, one domain quietly carrying the whole day — and by the time you notice, the fix is a new domain and three months of waiting.
  • What a junior actually costsA junior on $55,000 costs about $100,000 in their first year once you count payroll tax, health insurance, recruiting, equipment and the fifteen days of your own time it takes to ramp them. Here is the full arithmetic, and the test for which work is worth hiring for and which is a process problem wearing a headcount costume.

Take the client you turned down last month.

Describe what you deliver and the first draft exists before you have finished your coffee.

Start 7 days free

The first AI delivery firm. You sign.

All systems operational

Ask an AI about us

  • Claude
  • ChatGPT
  • Perplexity

It reads the site and answers on its own. We do not get to edit what it says.

Product

  • What you get
  • Pricing
  • Changelog
  • What it runs
  • Free reports
  • Product map
  • Team
  • Blog
  • Glossary
  • AI Visibility Index
  • Sign in
  • Docs

Compare

  • vs ChatGPT, Claude, or whichever tab is already open
  • vs Grok Bot and the AI-employee platforms
  • vs Hiring an account manager
  • vs Profound
  • vs Otterly
  • vs Building it yourself
  • vs Zapier & n8n
  • vs Temporal
  • vs LangGraph
  • vs CrewAI & AutoGen
  • All comparisons

Legal

  • Privacy
  • Sub-processors
  • Terms
  • DPA
  • Security
███╗   ███╗ ██╗   ██╗  ██████╗ ███████╗ ██╗
████╗ ████║ ╚██╗ ██╔╝ ██╔════╝ ██╔════╝ ██║
██╔████╔██║  ╚████╔╝  ██║      █████╗   ██║
██║╚██╔╝██║   ╚██╔╝   ██║      ██╔══╝   ██║
██║ ╚═╝ ██║    ██║    ╚██████╗ ███████╗ ███████╗
╚═╝     ╚═╝    ╚═╝     ╚═════╝ ╚══════╝ ╚══════╝