DEV Community: Change Brief

3 Late-Payment Emails for Freelance Developers

Change Brief — Mon, 26 Oct 2026 09:54:45 +0000

You shipped the feature, fixed the bugs, and answered the "quick question" that turned into a two-hour debugging session. The invoice went out on the first of the month. Thirty days later: nothing.

The most I have ever waited on was $4,800. The client answered every message within a day - "accounts is processing it", "the approver is on holiday", "next Friday, promise". What got it paid was not a longer or angrier email. It was the third email in a sequence I already had sitting in my drafts folder, sent on day 30, worded almost exactly like the one below. The money arrived in 48 hours.

If you freelance or run a small dev shop, chasing payment for finished work is one of the worst parts of the job. The fix is not a better apology for asking. It is a process: the same three emails, on the same days, every time.

Here they are, copy-paste.

Day 7: the polite nudge

At seven days past the due date, assume a boring explanation. The invoice was missed, routed to the wrong person, or stuck in an approval queue. Your goal is a response without friction.

Subject: Quick follow-up on invoice #[NUMBER]

Hi [CLIENT NAME],

I'm following up on invoice #[NUMBER] for [PROJECT/DELIVERABLE], which was due on [DUE DATE].

Could you confirm that it's been received and let me know when I can expect payment?

For reference, the outstanding amount is [AMOUNT].

Thanks,
[YOUR NAME]

Why this works: you identify the invoice, state the amount, and ask for one specific next step. No accusation, no essay.

Send it in the original invoice thread so the context travels with it. If they reply with a payment date, write it down. A promise in a casual email is easy to forget - yours and theirs.

Day 14: the firm follow-up

Two weeks late, be more direct. This message says the balance needs attention; it does not ask whether anyone saw your last email.

Subject: Payment overdue - invoice #[NUMBER]

Hi [CLIENT NAME],

Invoice #[NUMBER] for [AMOUNT] was due on [DUE DATE] and remains unpaid.

Please confirm the scheduled payment date by [RESPONSE DEADLINE].

If payment has already been processed, please disregard this reminder and let me know so I can update my records.

Thank you,
[YOUR NAME]

Why this works: it replaces a vague request with a clear action and a deadline, and it gives the client an easy out if payment is already moving.

Set the response deadline at two business days. If the answer is "waiting for approval," ask when approval is expected. If "accounting pays on Fridays," ask which Friday your invoice is scheduled for. Turn "we'll get to it" into something you can track.

Check your contract before this email. If it allows late fees, interest, or pausing work, know the terms before you invoke them. Never add fees the contract does not mention.

These templates are communication examples, not legal advice. Check your contract and applicable local law before adding late fees or taking collection action.

Day 30: the final notice

A month overdue changes the conversation. Stay polite, but do not send a third email that sounds like the first one.

Subject: Final payment notice - invoice #[NUMBER]

Hi [CLIENT NAME],

Invoice #[NUMBER] for [AMOUNT], originally due on [DUE DATE], remains outstanding despite my previous follow-ups.

Please arrange payment in full by [FINAL DEADLINE] or contact me by that date to confirm a concrete payment arrangement.

If the balance remains unpaid and I have not received an agreed resolution, I will consider the next steps available under our agreement and applicable law, which may include formal collection or recovery proceedings.

Please confirm receipt of this notice.

Regards,
[YOUR NAME]

Why this works: it is factual, it documents the history, and it sets an explicit deadline without threats you cannot carry out.

Only name actions you are genuinely prepared and legally entitled to take. Before formal recovery, review your agreement, preserve the invoices and correspondence, and check the rules in the relevant jurisdiction. And do not assume you can shut down a live service, revoke access, or withhold source code - your contract decides that, not your frustration.

What happens between the emails matters as much

Keep a payment log. Invoice number, amount, due date, reminder dates, responses, promised dates. The day you have three late invoices, this log is the only thing keeping the story straight.
Separate payment from new work. A client who has not paid asking for another feature is not an automatic yes. Review the agreement and discuss a pause or revised schedule.
Make paying easy. Every email includes the invoice, the amount, payment instructions, and the reference their accounting needs. Every extra step is another week.
Fix the next contract. Explicit payment terms, a defined invoicing schedule, a stated late-fee rule. For larger projects, milestone payments instead of one big invoice at the end.
Do not let one client be your whole business. A great relationship is still a financial risk if one unpaid invoice stops you paying your own bills.

Build the system before you need it

The best time to decide how you handle late payment is before an invoice goes overdue. Set three calendar reminders for days 7, 14, and 30, save the scripts as templates, and when the day comes you fill in the brackets and send. You follow a process instead of writing an email while frustrated.

Your turn: what is worse - clients who ignore reminders, clients who keep promising "next week," or clients who dispute the invoice after the work is done? And what actually worked for you?

Written by the Change Brief team - we build practical, no-signup toolkits for freelancers.

AI assistance was used in drafting this article. The publisher reviewed and edited the content and takes responsibility for the final version.

Your client added 'one small thing' again. Here is the exact reply.

Change Brief — Mon, 26 Oct 2026 08:00:31 +0000

You shipped the fixed-price site. Then the client emails: "Can you just add a blog section? Should be quick." If you freelance or run a small dev shop, you know exactly what happens next.

Here is the reply I send now:

Happy to help with this. It falls outside the original scope, so I can either swap it for [existing deliverable] or quote it as an additional item. Which works better for you?

That is Script 1 of 9. The rest of this post is why it works, the other two scripts I use most, and the math that made me stop giving this work away.

A client of mine once ended a call with the blog-section line. I said "sure, no problem" because that is what you say when you like the client and want the next invoice paid on time. The blog section was two weeks of work. I did the two weeks. I did not invoice for them. That was an expensive way to learn that scope creep is not a communication problem. It is a billing problem, and it has a script.

The framework: acknowledge, clarify, price

Every scope-creep request gets the same three-part reply:

Acknowledge the request positively. You are not refusing. You are being a professional who tracks what things cost.
Clarify: swap or add? Every new item either replaces an existing deliverable or is new work. Make the client pick. This one question kills most scope creep, because it forces the trade-off into the open.
State the cost in writing. Not on a call. In writing, with a number, before the work starts.

The order matters. If you skip to step 3, you sound adversarial. If you skip step 2, you end up doing the original scope and the additions.

Script 2: the big ask

When the request is clearly a new phase of work:

This is a great idea and I want to do it properly. It is outside what we scoped, so I will put together a short change brief: what it includes, what it costs, and how it moves the timeline. You will have it tomorrow, and nothing starts until you approve it in writing.

Note what this does: you said yes to the relationship, yes to the work, and no to doing it for free. All in three sentences. "Nothing starts until you approve it in writing" is the load-bearing sentence. Say it every time.

Script 3: the retroactive ask

The worst kind: they mention, after the fact, that they assumed something was included.

I understand you read it that way, and I should have caught the ambiguity earlier. Looking at our agreement from [date], the scope covers [X, Y, Z]. This item is new, so here are the two ways we can handle it: swap it for something in the current scope, or I quote it separately. I do not want billing surprises for either of us.

"I should have caught the ambiguity earlier" is deliberate. You give them a face-saving exit, and in exchange the swap-or-pay frame stands. You are not conceding the work is free. You are conceding that contracts are read optimistically by people who want things.

The math that makes this non-negotiable

Freelancers treat each "small thing" as too petty to bill. Run the annual number instead. If you give away 30 minutes a day on a $100/hour rate, that is $12,500 a year. That is not a rounding error. That is a used car, or two months of runway, every single year.

The five-minute reply that prevents it costs nothing but the discomfort of sending it. The discomfort fades after the third time. The $12,500 does not fade.

Approvals live in writing, or they do not exist

Every scope decision, every approval, every "yes go ahead" gets an email or a message you can point to later. Not because clients are dishonest. Because in six weeks, both of you will remember the conversation differently, and the written record is the only version that invoices.

My rule: after any call where scope comes up, I send a two-line recap. "Confirming: we are swapping the testimonial section for the FAQ block, no price change." One reply of "confirmed" and I am covered. It takes ninety seconds.

The client with the blog section? I still work with them. The next time they called with "one small thing," I sent Script 1. They chose the swap, we both knew exactly what the project was, and the invoice after that was paid in four days.

Scope creep is a billing problem. Treat it like one.

What is the worst "one small thing" you have ever gotten?

Disclosure: this article was drafted with AI assistance and reviewed and edited by the Change Brief team before publication.