Hi [NAME],
Invoice #[NUMBER] for [AMOUNT] was due on [DATE] and is now 14 days
past due.
I need it settled by [DEADLINE]. Link: [LINK]
If something has changed on your end — budget frozen, approval stuck,
invoice never reached accounts, or you need something from me to get it
processed — tell me and we'll work it out. I'd rather know than keep
sending these.
If it's already been paid, forward me the remittance and I'll close
it off.
[YOU]
SendPage 6
Hard Emails, Handled
The three-email sequence that gets an invoice paid — and nine more client conversations nobody wants to have. Written, ready, and sounding like you.
You've been not-writing the same email for eleven days.
You know the one. The invoice that was due on the 3rd. Or the client who's added four "quick favors" to a fixed-price project. Or the rate increase you've needed to send since spring. You open the tab. You write "Hi —". You close the tab.
A solo operator sitting on one $2,400 invoice for three extra weeks isn't losing three weeks. They're losing the invoice after that one too, because the same silence repeats. You're not bad at business. You're bad at one specific email — and so is everyone else doing this alone.
Most people send one email. Then nothing.
That is the real problem, and it is not the wording. It is the sequence. One nudge goes out, it earns a "yes, we've got it", and the invoice sits there for another month while you decide whether to be annoying.
Three emails, on three dates, each doing a different job:
Day 3The polite payment reminder email that actually worksThe exact email to send when an invoice is a few days late. Firm, friendly, gives them an easy out — and it gets answered.
Day 14The second payment reminder email that gets you paidYour first nudge got ignored. This is the second email — no apology, one deadline, one easy way for them to respond.
Day 30The final payment reminder email, before you escalateThirty days late and still nothing. The email to send before you escalate — professional, dated, and it leaves you every option.
And between the rungs, nothing. No check-ins, no soft nudges, no "just seeing if this landed". Every extra email in the gaps lowers the weight of the next scheduled one, because you have taught the reader that your messages arrive whether or not anything has changed. That one rule is worth more than any single template in here.
What else is in it
A 32-page kit of the twelve client emails that are hard to write, written out in full, with the AI prompts that rewrite each one in your voice. You copy it into your own workspace and it's yours.
The three-email invoice sequence. Day 3, day 14, day 30 — the friendly nudge, the firm follow-up, and the final notice before you escalate. With the ladder that tells you when to send which.
The scope creep reply. The one that caps a fixed-price project without losing the client, in under 80 words.
The rate increase email. An announcement, not a request — which is the entire difference between keeping the client and opening a negotiation you didn't need to open.
Two ghosting scripts. One for a client who went silent mid-project, one for a prospect who vanished after the quote. They are not the same email and sending the wrong one is why neither works.
Twelve prompts, plus the master prompt. Paste three emails you've actually sent, and the template comes back sounding like you instead of like a template.
20 subject lines that get opened, and the seven that guarantee an archive.
The contract clause that prevents most of this. Two paragraphs. One of them means a client who hasn't paid doesn't own the work they're already using.
Ten filled-in examples. Real-shaped situations with the blanks filled and what actually came back.
And eight phrases that are costing you money
Page 19 is a list of the things people write instead of the email, and what each one actually communicates. The first four:
"Just checking in" — announces the email contains nothing.
"No rush!" — written permission to ignore you.
"Sorry to bother you" — frames your paid work as an imposition.
"Let me know your thoughts" — an invitation to do nothing.
None of the replacements are more aggressive. They're more specific. That's the whole trick.
Read three pages before you decide
Not a blurred screenshot and not a table of contents. Three complete pages out of the thirty-two, in full, exactly as they appear in the document.
Page 3
The one rule
Every email in here obeys a single rule, and if you only take one thing
from this document, take this:
Give them one specific thing to do, and one dignified way out.
That's it. That is the difference between an email that gets answered and
an email that gets archived.
One specific thing to do. Not "let me know your thoughts". Not "when
you get a chance". A dated, concrete action: pay this link by Friday,
reply with a number, tell me which of these two you want. Vague asks feel
polite. What they actually do is transfer the work of deciding what you
want onto a person who has forty other emails, and that person will
choose the one that requires no decision.
One dignified way out. People don't ignore you because they're
hostile. They ignore you because replying means admitting something
awkward — the budget's frozen, they forgot, they went with someone
cheaper, they can't afford you any more. Silence is the cheapest way to
avoid saying that out loud.
So say it for them. "If the budget's frozen, tell me and we'll work out a
plan." "It's more than you wanted to spend — that's fine and it doesn't
offend me." The moment the awkward thing is on the page in your
handwriting, it stops being awkward, and you get a reply.
Every template here is that rule twice: an ask with a date on it, and an
exit with no shame in it.
What this means for the tone question
You are probably worried about sounding aggressive. Look at what actually
makes these emails land — none of it is force. It's specificity and an
exit. You can be extremely warm and still be completely clear. What you
cannot be is vague and expect an answer.
The word to delete, everywhere, forever, is "just". Every instance of
it in an email is you apologising for having sent the email. Find it,
delete it, send.
Page 6
Late invoice — the firm follow-up (day 14)
When to use it. Invoice is 14 days past due. You've sent one friendly nudge. Silence.
The email
Subject: Invoice #[NUMBER] — payment status
Hi [NAME],
Invoice #[NUMBER] for [AMOUNT] was due on [DATE] and is now 14 days
past due.
I need it settled by [DEADLINE]. Link: [LINK]
If something has changed on your end — budget frozen, approval stuck,
invoice never reached accounts, or you need something from me to get it
processed — tell me and we'll work it out. I'd rather know than keep
sending these.
If it's already been paid, forward me the remittance and I'll close
it off.
[YOU]
Why it works. No apology, so nothing signals that asking to be paid is an imposition. One specific deadline, so there is a thing to be late for rather than a mood to manage. And an open door that makes it easy for them to tell you the real reason — because the real reason is nearly always a frozen budget or a stuck approval, and neither gets solved by another nudge.
What most people send instead. "Just circling back — no rush, whenever you get a chance!" This fails because it gives them permission to keep ignoring you. It is also the same email as day three, and the day-three email has already been tried. If a gentle nudge were going to work here it would have worked the first time; what is left is either a date or a decision.
A subject line has one job: make the email look like a specific piece of
admin rather than a feeling. Numbers, dates and nouns get opened. Verbs
about your emotional state do not.
Money
Invoice #1043 — due March 12
Invoice #1043 — payment status
Invoice #1043 — final notice before escalation
Payment plan for #1043?
Rate change from April 1
Stalled work
Redesign — I'm holding
Redesign — three options, pick a number
Blocked on the copy deck
Closing the file on the Q3 build?
Still want this in April?
Bad news
Redesign — new date
What fits in two weeks
Re: the extra landing pages
Wrapping up our work together
One thing before Friday
Good news and asks
One question about the rebrand
Done — and one small thing
Handover doc + final invoice
Two dates that work
Quick decision needed: A or B
What not to use
Checking in · Touching base · Quick question · Following up ·
Bumping this · Sorry to chase! · Just one more thing
Every one of those tells the reader the email contains no new
information. They are correct, and they archive it.
Scroll inside the frame to read all three.
Who this is for
Freelancers, consultants and agencies of one — people who do the work and send the invoices, with nobody else to hand the awkward email to. If you've ever opened a draft, written "Hi —", and closed the tab, this was written for you specifically.
Who it isn't for
Anyone with an account manager, a collections process, or a person whose job includes chasing payment. You already have this.
Anyone looking for legal templates. Page 21 has contract language and a clear warning that a lawyer needs to read it. That page is a starting point, not a service.
Anyone who wants a system rather than a document. If what's actually breaking is that all of this is manual, don't buy this — reply to me and describe what's breaking.
Who wrote this, and why you should discount it
I have not mastered difficult client emails. I avoid them.
Once, with an invoice past due, I sent a short email asking whether they had received it. They replied that they had missed it, and they paid. It worked, and it took me about four days to work up to sending it.
The next time an invoice went late, I sent a text instead.
That is the part worth sitting with. The email worked and I still did not send another one, because a text asks whether a document arrived and an email — even a mild one — feels like asking to be paid. I picked the option with less nerve in it, and a text does not get you paid. It gets you "yes, got it."
So this is not a collection of war stories from someone who finds this easy. It is the system I built because I needed one — worked out properly once, so that at 11pm the decision is already made and all that is left is a name and a number.
When the moment comes I do not have to be brave, only organised.