The three-touch nudge: late-payment recovery without burning the relationship

The invoice is fourteen days overdue. You've been telling yourself for a week that you'll send the follow-up tomorrow. You haven't. The cash matters, but chasing it feels gross, and the email you're about to write keeps stalling out at "I'm so sorry to bother you, just wanted to circle back…"

Most solo consultants have a procedure for the sales side of an engagement and no procedure for the money side. Discovery calls are followed by debriefs, proposals are followed by follow-up sequences, kickoffs have agendas. Invoices get sent into the void, and when they go unpaid, the consultant's response is improvised every single time. The result is what you'd expect: apologetic emails sent too late, tense emails sent too late, and engagements that quietly slip into the consultant absorbing the risk of the client's accounts payable workflow.

The fix is a three-touch nudge cadence — day 1, day 7, day 14 — that runs on a schedule whether you feel like sending it or not. Each nudge has a specific job, a specific tone, and a script. The whole thing takes about two minutes per nudge to send. This article is the cadence, what each touch is doing, and why the day-14 nudge is the only one that actually moves money.

Why the apologetic email is the wrong default

The single most damaging pattern in solo consultant invoicing is the apologetic followup. "Hi, sorry to bother you, just checking on the invoice from last month — no rush, just wanted to make sure it didn't get lost!"

That email achieves three things, all bad:

It signals that you don't take your terms seriously. The client reads "no rush" and concludes there isn't one. The next invoice slips further because they've now learned your payment terms are flexible.

It signals that chasing is awkward for you. Operators who are confident about their work are confident about getting paid for it. The apologetic followup tells the client you're uncomfortable with the basic transaction at the heart of the relationship. They will notice.

It produces no information. A polite "sorry to bother you" email gets ignored or gets a vague reply ("thanks, will look into it") and nothing changes. You haven't learned whether the invoice is in the AP queue, lost, disputed, or being deliberately deferred. You've just confirmed that you'll be quiet about it for another week.

The cadence below replaces this with three different emails, each with a specific job. None of them apologize. All of them produce information.

The three-touch cadence

Day 1 past due — the benign check-in. Two sentences. Subject: "Quick check on invoice [number]."

"Just confirming you received invoice [number], due [date]. If there's a delay on your side, let me know what timeline works."

The job here is to give the client a benign explanation before they have to provide one. The email got lost, the AP system is slow, the approver is on vacation — any of those is fine. Most late payments resolve at day 1 because the invoice genuinely was missed and now it isn't. No apology, no over-explanation, no "hope this finds you well."

Day 7 past due — the term reminder. Three sentences. Subject: "Invoice [number] — payment update."

"Following up on invoice [number], now seven days past due. Our terms are net [X]; please confirm payment timing or flag if there's a blocker on your side. Happy to talk if anything's stuck."

Tone shifts. You're now referencing the agreed terms directly, which is what professionals do. The "anything's stuck" phrasing leaves a door for the client to surface a real problem — sometimes there's a dispute, sometimes there's a cash-flow issue, sometimes there's an internal approval blocker. The day-7 nudge surfaces those.

Day 14 past due — the consequential one. Four sentences. Subject: "Invoice [number] — pausing engagement."

"Invoice [number] is now 14 days past due. Per our terms, I'm pausing active work on [engagement] until payment clears. To restart, reply with payment timing or wire confirmation. If something has changed about the engagement on your end, please tell me directly so we can sort it."

This is the email that actually moves money. The pause is the lever you have. State it cleanly without apology. No threat, no drama — just the operational consequence of the unpaid invoice meeting the terms you both agreed to. Most engagements that reach the day-14 nudge either pay within 48 hours or were never going to pay. Both outcomes are better than the consultant absorbing the carry.

The three nudges run in order. You don't skip ahead. You don't add nudges between them. The cadence works because it's predictable, professional, and ends in an unambiguous consequence.

Why the day-14 nudge is the only one that actually moves money

The first two nudges are about information and continuity. They give the client a graceful path to resolve the late payment without anybody feeling weird about it. They work most of the time — by the day-7 mark, most late payments have either cleared or surfaced a real reason.

The day-14 nudge is different. It's the email that creates an actual consequence. Pausing work is the only lever a solo consultant genuinely has without going to legal, and it's a lever you should be willing to pull. The reason most consultants don't get paid late once is because they paused once. The reason others get paid late perpetually is because they've trained the client to know that they won't.

The pause has to be real. If you send the day-14 nudge and then keep working anyway, the next late payment will be worse, because you've now demonstrated that your "pause" was rhetorical. State the pause; mean the pause. If the client replies within 48 hours with a payment timing, you can choose to resume on good faith. If they don't, you actually stop work — calendar holds drop, deliverables freeze, the engagement is on hold until payment clears.

This sounds aggressive. It isn't. It's what professional operators do. Vendors give discounts for late payment; professionals pause work. The client experience of being paused once is what makes future invoices land in the AP queue with the right priority.

What Claude does, and what doesn't

The nudges are mostly templated, but each one needs a small amount of personalization — match the client's communication style, name the specific engagement and amount, reference the specific terms.

Claude does the personalization fast. You paste the template, paste a sample of the client's prior emails (so Claude can match tone), name the situation, and Claude produces a draft you can edit in 30 seconds. The whole nudge ships in two minutes.

The part Claude can't do: deciding when to break the cadence. If a long-term client whose invoices have always cleared misses a payment because of an internal restructure they told you about three weeks ago, you don't run the cadence. You send a "hey, no pressure — just confirming the timing is still what we discussed" email and move on. The cadence is the default; judgment overrides it.

The same is true in the other direction. If a client has missed three previous invoices and you're now at day 7 on a fourth, you skip the day-1-style benign framing and go straight to the term reminder. The cadence is the structure; the judgment is which structure applies to which client.

Before the cadence ever fires: invoice hygiene

The reason most consultants need a nudge cadence in the first place is that their invoice send was sloppy enough to create avoidable late payments. Three habits prevent the majority of late invoices, and they cost nothing to install.

Send the invoice on a scheduled day, not when you feel like it. For project work, the invoice for the 50% deposit goes out on the day you and the client agreed the engagement starts. The 50% balance goes out the day you deliver. For retainers, the invoice goes out on the same day every month — whatever you committed to in the proposal. Inconsistent invoice timing trains clients to treat invoices as suggestions. Predictable invoice timing trains them to expect the invoice and route it through AP on arrival.

The cover email is three sentences. Not more. "Attached is the [name] invoice for [scope or period]. Due [exact date]. Reply if anything looks off." That's it. Don't apologize for sending an invoice. Don't say "no rush." Don't pad. The three-sentence cover note signals that invoicing is a procedural part of the engagement, not a special ask.

The due date is a specific date, not a relative phrase. "Due May 15" — not "due in 30 days." Relative phrases get misinterpreted (does the 30-day clock start on send date, receive date, or PO date?). A specific date eliminates the ambiguity that creates late payments.

These three habits, plus the cadence above when payments slip anyway, cover about 95% of solo-consultant invoicing pain. The remaining 5% is dispute, fraud, or insolvency — none of which a nudge cadence solves anyway.

Pitfalls

Soft-launching the pause. "I might need to pause work if the invoice isn't resolved soon." That's not a pause; that's a hedge. A pause is "I'm pausing active work." Present tense, no conditional.

Sending all three nudges from the same email thread. Each nudge should be a new email with the relevant subject line. Threading them buries the escalation; the day-14 nudge needs to land in the inbox as a new message that gets attention.

Apologizing in nudge 3. "Sorry to have to send this, but…" No. Pausing is a procedural action, not a personal failing. Apologies belong elsewhere.

Restarting work before the payment clears. A wire confirmation is not a payment. The actual money in your account is the trigger to resume. Anything else is the client buying themselves more time.

Skipping the file step. Every invoice send and every nudge gets a copy in clients/<name>/invoices/. When the engagement wraps and you're writing the case study (or, occasionally, the engagement-end debrief), the paper trail matters.

The procedure that fires this

The cadence above works because it's a procedure, not a judgment call. Day 1 past due → nudge 1. Day 7 past due → nudge 2. Day 14 past due → nudge 3. The trigger is the calendar; the consultant doesn't have to decide whether today is a chasing day.

The operational version of this — the cover-email template for invoice send, the three nudge scripts with the right subject lines, the paired Claude prompt for personalizing each one to the specific client, and the pitfalls list — is SOP 03 in The Solo Operator's SOP Bundle. Each SOP in the bundle has the same shape: when to use, the procedure, the paired Claude prompt, the pitfalls. The invoicing SOP slots into a client folder the same way the kickoff and weekly-update SOPs do, and the cadence runs on triggers whether the consultant feels like sending the email or not.

The day-14 email is the cheapest line item in the catalog of things that protect your business. Three sentences, sent on a date. The compound return on having sent it once is most clients learning that your invoices clear on time.