How to chase final payment after a website goes live

The moment a website goes live, the power balance shifts. Your client has the product, you have an unpaid invoice, and every day you wait makes that final €3,000–€4,000 feel less inevitable. Knowing how to chase final payment after a website goes live is not really about writing the perfect email. It is about setting up the conditions before launch so that chasing is rarely necessary.

Why post-launch payment is uniquely hard for designers

Every other milestone has a natural gate. You send the first draft; the client reviews it. You send the staging link; they approve it. But the final invoice? There is no gate. The site is live. The client is thrilled, announcing it on LinkedIn, and your invoice is sitting in a queue behind someone's expense approval process.

The problem compounds when:

• The project runs over the original timeline (client-side delays count here too).
• The client treats "after launch" as "whenever we sort out budget."
• You are invoicing in GBP for a US client or USD for a European one, so currency confusion adds another layer of friction.

None of this is solved by a strongly worded reminder. It is solved by structure put in place before the site goes live.

The pre-launch lock-in: three things to do before you flip the switch

This is the window where you still hold leverage. Use it deliberately.

1. Issue the final invoice before launch, not after.

Send the invoice 48–72 hours before the scheduled go-live date. Frame it plainly: "The final invoice is attached. Payment is due on [launch date]. I will push the site live once I have confirmation it is in process." You are not threatening anyone. You are running a professional handover.

2. Set the payment terms to something concrete.

"Due on receipt" or Net 7 is reasonable for a final milestone. Net 30 on a final invoice is a gift you cannot afford to give. If the contract already says Net 14, issue the invoice early enough that the due date lands on or just after launch.

3. Put a hold-back clause in the invoice notes.

One line is enough: "DNS transfer and final file handover completed within 24 hours of cleared payment." This keeps the deliverable partially in your hands without being adversarial. The site can be live; the source files and admin credentials follow payment.

The post-launch reminder schedule that actually works

You sent the invoice. The site went live. Nothing arrived. Here is the cadence that keeps pressure steady without burning the relationship:

• Day 0 (go-live day): Send a short, warm "we're live" email. Attach the invoice again. No drama.
• Day 3: A brief check-in. "Just flagging this in case it got buried." One sentence.
• Day 7 (due date): A clear, professional reminder with the invoice link and your payment details.
• Day 10: A direct message (WhatsApp, Slack, wherever you actually talk). Payment reminders that arrive via the channel the client actually reads get responded to.
• Day 14: A formal final notice. This one names the amount, the original due date, and what happens next (late-payment interest if your contract includes it).

That is five touchpoints over two weeks. It feels like a lot until you have watched a €5,000 invoice age past 60 days.

What to do when the reminder schedule fails

If two weeks pass and you have heard nothing substantive, escalate in this order:

Involve a decision-maker. The person who hired you may not control the cheque. Ask directly: "Who should I copy on payment queries?" One CC to the right person often unblocks things in 24 hours.

Send a formal letter of demand. In the EU and UK, a written demand is a prerequisite for late-payment interest claims under statutory frameworks. Keep it factual: amount, original due date, interest accruing per day.

Consider a partial release. If the client is genuinely cash-flow-stretched, a structured split (50% now, 50% in 14 days) recovers something quickly and avoids a dispute. Set this up as a second invoice with its own due date and reminder schedule rather than an informal agreement.

Do not give away access first. If credentials or source files are still outstanding, hold them until you have cleared payment or a signed payment plan. This is not hostage-taking; it is standard professional practice.

The mindset shift that prevents most post-launch chases

The designers who rarely chase final payment are not more assertive emailers. They are better at the pre-launch conversation. They normalise the invoice before launch day arrives, make payment easy (a link, a QR code, bank details right there on the invoice), and set reminders so that a busy client cannot simply forget.

A €4,500 final invoice sitting unpaid for 45 days is roughly €22 in lost interest at a modest rate. It is also several hours of your time, a fraying client relationship, and the mental overhead of checking your bank account every morning. Set the structure up front. Let the reminders run. Save your energy for the next project.