How do I chase a milestone payment when the client is still active in Slack?

Keep it on email, where there is a paper trail, and reference the deployed milestone by name. Start with a delivery-confirmation frame — "the sprint shipped and I want to make sure the invoice landed" — before moving to a direct question about the payment date.

A client wants new features before paying for the last milestone — how do I respond?

Treat new features as new scope, not a continuation. Acknowledge the request, quote the additional cost and timeline in writing, and tie the previous milestone's payment to the start of the new work. BidPropel can draft the email that draws that line politely.

How do I bring up unpaid milestones before starting the next sprint?

Make milestone payments a gating event, stated in the proposal from day one: no cleared payment, no next sprint. When it is in writing, the follow-up email is just a reminder of the agreement — not a negotiation.

Payment Follow-Up Emails for Freelance Developers

You scope the sprint, ship the code, and deploy — and the project quietly runs 3x over budget while milestones go unpaid. Scope creep grows in the gap between "we need one more thing" and the invoice that never moves. For developers, late payment is not a cash flow problem; it is the sign that the scope itself is out of control.

BidPropel writes the exact follow-up email so you don't have to — calibrated to your client, the amount, and how late they are.

Generate your email now — free →

No credit card needed. 3 free per month, credit packs available.

How Freelance Developers use BidPropel

From the proposal that prevents the problem to the follow-up that collects the cash — built for developers.

Proposal writing for technical specs

Translate a technical spec into a milestone-based proposal with fixed payment triggers. When every merge has a price attached, scope creep stops being free.

Budget-to-scope checking

Run the quoted budget against the actual scope before you start — and surface any gap in writing. Developers who check this upfront do not end up 3x over budget.

Milestone payment follow-ups

Chase each milestone payment on a schedule tied to deployment, not to convenience. The client may be active in Slack — your invoice should be active too.

Example emails for developers

Templates calibrated to different stages and situations in the follow-up sequence.

First invoice

Subject: Invoice #INV-3075 — developer project

Hi [Client],

Here's the first invoice for the recent developer work — $3,500, due within 14 days per our agreement.

You can pay via the link on the invoice. Let me know if you have any questions about the billing process — happy to walk through it.

Really enjoyed this project.

Gentle nudge

Subject: Invoice #INV-1213 — quick check

Hi [Client],

Quick note — invoice #INV-1042 for the recent developer work went out last week. Making sure it landed in the right inbox and you've got everything you need on your end.

Can you confirm you received it?

Firm but warm

Subject: Invoice #INV-7962 — following up

Hi [Client],

Invoice #INV-1088 for $3,500 is now 2 weeks past due. Haven't seen it come through yet.

Can you give me a sense of when this one's getting processed? Happy to resend if it got buried.

Final notice

Subject: Invoice #INV-3943 — requires resolution

Hi [Client],

Invoice #INV-1201 for $3,500 is now over a month past due with no response to prior messages.

If I don't hear back with a concrete payment date by end of week, I'll pause active work and send a formal notice.

I'd much rather sort this out directly — what's the soonest you can get this through?

Broken promise

Subject: Invoice #INV-6376 — checking on the timeline

Hi [Client],

You mentioned payment would land by the date we discussed — checking in since I haven't seen invoice #INV-1142 come through yet.

Can you give me an updated timeline? Totally understand things come up.

Offer payment plan

Subject: Invoice #INV-3015 — payment options

Hi [Client],

Invoice #INV-1088 for $3,500 is past due. I understand the full amount at once may not work right now — would breaking this into a couple of payments help?

Happy to work out something that fits your timeline. Let me know what works.

Pause project

Subject: [Project] — update on timeline

Hi [Client],

Invoice #INV-1177 for $3,500 is past due. I'll need to pause active work on the project until payment clears.

Once it comes through I can pick things right back up — everything's queued and ready. Can you let me know when the payment goes through?

Thank you

Subject: Received — thank you for the payment

Hi [Client],

Payment for invoice #INV-1104 landed — thank you. Really appreciate how smooth this developer project has been.

Looking forward to the next phase.

Frequently asked questions

How do I chase a milestone payment when the client is still active in Slack?: Keep it on email, where there is a paper trail, and reference the deployed milestone by name. Start with a delivery-confirmation frame — "the sprint shipped and I want to make sure the invoice landed" — before moving to a direct question about the payment date.
A client wants new features before paying for the last milestone — how do I respond?: Treat new features as new scope, not a continuation. Acknowledge the request, quote the additional cost and timeline in writing, and tie the previous milestone's payment to the start of the new work. BidPropel can draft the email that draws that line politely.
How do I bring up unpaid milestones before starting the next sprint?: Make milestone payments a gating event, stated in the proposal from day one: no cleared payment, no next sprint. When it is in writing, the follow-up email is just a reminder of the agreement — not a negotiation.