Retainers make pausing awkward. The work is continuous, the relationship is usually warm, and the invoice sitting open is rarely a refusal — it's an accounts-payable queue nobody's watching. So you keep delivering. Then you keep delivering again. By month three, the open balance is large enough that pausing feels like an overreaction, and you've talked yourself into being a lender.
The fix isn't nerve. It's a rule you wrote down before you needed it.
Decide the trigger while you're calm
Put a pause clause in the retainer agreement, in plain language:
Work is scheduled monthly and continues while the account is current. If an invoice reaches 15 days past its due date, we pause new work on written notice and resume once the account is current.
Two things make that clause work. The trigger is a date, not a mood. And the notice is written, so nobody remembers it differently later.
Triggers that hold up in practice: one invoice 15 days past due, or two invoices open at the same time, or an open balance larger than one month of the retainer. Pick one. Tell your bookkeeper what it is so they can flag it without asking you each time.
Find out why before you pause
One short exchange first. Late retainer invoices are almost always one of four things:
- It never reached AP — it's in one person's inbox.
- It's blocked on a PO number or a missing vendor form.
- The approver is out and nobody has a backup.
- The client is genuinely tight this month.
Only the fourth needs a payment plan. The first three need a name, a resend, and ten minutes. Pausing delivery over a missing PO number is an unforced error, and clients remember it.
This is the part worth automating. FetchDue chases from your own mailbox, reads the reply, and tells you which of the four you're actually in — before you spend relationship capital on the wrong one. You approve every send, so nothing goes out in your name that you haven't seen.
Warn first, then pause on a boundary
A pause should never be the first news. Send the heads-up at least five business days ahead, and pause at a natural seam — end of a sprint, after a scheduled publish, not mid-revision. Stopping cleanly reads as process. Stopping mid-file reads as retaliation.
Define what "pause" means
Write this down once so your team isn't guessing.
Stops: new deliverables, new requests, strategy calls, any ad spend you front.
Continues: hosting, domains, monitoring, anything already scheduled to publish, anything whose failure would hurt the client's own customers.
Never: locking clients out of accounts they own, deleting work, withholding files they've already paid for.
Leverage is fine. Harm isn't, and it's usually also a contract problem. The point of a pause is to resume.
The three emails
Heads-up, day 10. Short, no drama.
Hi Dana — invoice 1042 ($6,400, due July 3) is still showing open on our end. Our agreement pauses new work at 15 days past due, which would be Friday the 18th. I'd rather not do that mid-campaign. Can you tell me where it is in your process, or point me to whoever handles AP?
Pause notice, day 15.
Hi Dana — as of today we've paused new work on the account per our agreement. Hosting and the scheduled Thursday send continue as normal; nothing is at risk. The August sprint is held, not cancelled. We'll resume the day invoice 1042 clears, or as soon as we agree on a schedule for it — happy to split it across three weeks if that's easier. Let me know which is simpler on your side.
Resume.
Payment landed this morning, thank you. Work resumes today. The August sprint moves to a start of the 4th, so the landing page lands the 15th instead of the 11th. Everything else is unchanged.
Offer the plan in the pause notice, not three emails later. It converts far more often than a second reminder, and it costs you nothing to have ready.
Tell your own team the same day
Put the pause on the project board and tell the delivery lead directly. Nothing undermines you faster than a designer shipping a revision two days into a pause you announced in writing. It tells the client the line isn't real, and the next one won't be either.
The part people skip
Pausing once, early and politely, does less damage than delivering quietly for three months and then having a hard conversation about a number with a comma in it. Small, on-schedule, unemotional — that's what makes it survivable. Clients who pay late constantly are usually managing a queue, not judging your worth. Give them a clear rule and most of them will just work inside it.