How to structure milestone invoices for design projects

You do great work, you deliver on time, and then you wait. The second half of a €6,000 branding project sits unpaid for weeks because the client hasn't "officially launched" yet. Structuring milestone invoices correctly is the single most effective way to stop funding your clients' timelines with your cash flow.

What milestone billing actually means for designers

Milestone billing ties each invoice to a deliverable event, not a calendar date. That distinction matters because a date ("invoice on 1 March") is something you control, while a deliverable event ("concept approved") is something you and the client agree on in writing before the project starts.

The common mistake is treating milestones as project phases (Discovery, Design, Delivery) when they should be client decision points: moments when the client reviews something, approves it, and formally moves forward. That approval is your invoice trigger.

A client who hasn't approved the concept hasn't triggered the invoice yet. That sounds like it hands them power, but the opposite is true: you can now follow up on the approval itself, not on the money. "Hey, I need your sign-off on the concept deck to schedule the next sprint" is a much easier conversation than "hey, can you pay my invoice."

The three-milestone structure that works for most design projects

There is no universal rule, but for a €2k–€8k project with a 4–10 week timeline, three milestones hit the right balance between client comfort and your cash flow protection.

Milestone 1: Project kick-off (30–40%)

Invoiced before any work starts. This is your deposit, and it is non-negotiable. A €5,000 brand identity project should open with a €1,500–€2,000 invoice due on receipt.

This payment covers your discovery work (stakeholder calls, brand audit, competitor research) and compensates you if the client goes quiet. Frame it in your contract as "project commencement fee" rather than "deposit" because a deposit implies it might come back.

What to put on the invoice: discovery session, brand audit, project kick-off. If you are VAT-registered, this is a standard taxable supply. If you are billing a UK-based client from Germany, check whether reverse-charge applies.

Milestone 2: Concept approval (30–40%)

This invoice fires the moment the client approves a creative direction, not when you present it. The language in your contract should read: "Invoice 2 is due upon written approval of the chosen concept direction."

"Written approval" means a reply email, a Slack message, a signed PDF. Get it before you open your files and start execution. Without that language, a client can approve verbally on a call and then claim they "never really committed" when Invoice 2 lands.

For a €5,000 project, this milestone is another €1,500–€2,000. At this point you have received 60–80% of the project fee before touching final files, which is exactly where you want to be.

Milestone 3: Final file delivery (20–40%)

The balance, invoiced when you send the final packaged files. Note: not when the website goes live, not when the client posts the logo on LinkedIn. When you hand over the ZIP.

If your contract ties final payment to "launch," change it today. Launch timelines are outside your control. Developers miss dates. Internal approvals stall. You have zero leverage once the files are delivered and the payment trigger hasn't happened yet.

For projects where the client insists on a post-launch milestone, cap it at 10–15% of the total and keep 25–30% tied to file delivery. You can live with chasing a €600 tail payment. Chasing €2,400 after handover is a different problem.

How currency and timing interact on cross-border projects

If you are a Berlin-based designer billing a London agency in GBP, every day of delay is also an FX exposure. A £4,000 project quoted in October may settle at a different EUR equivalent in December. That gap is not your client's fault, but it is your loss.

The practical fix: lock the GBP amount at milestone sign-off, not at project start. Put the GBP figure in the contract and send each invoice in GBP. That way, whatever happens to EUR/GBP between kick-off and final delivery, your client pays the agreed sterling amount and you convert at the rate on the day funds arrive.

Handling the classic delay tactic: slow concept approval

The most common way a designer loses cash flow is not a client who refuses to pay. It is a client who never formally approves the concept, which means Invoice 2 never triggers, which means you are doing execution work on a project where 60–70% of the fee is still outstanding.

Three things prevent this:

1. Set an approval deadline in the contract. "Client has 5 business days to approve or request one round of revisions on the concept presentation. Silence after 5 days constitutes approval." Harsh? No, this is standard agency practice. Clients who have worked with professional studios expect this language.

2. Send a reminder on the approval, not the invoice. "Just following up on the concept deck from Tuesday. I need your written go-ahead to move into execution. Once confirmed, I will send Invoice 2." Keep the money off the table until the approval conversation is resolved.

3. Set up your Invoice 2 in advance and trigger it the moment you get the reply. With recurring and draft invoices queued up, you are not scrambling to build the invoice after approval. You send it within minutes, which signals professionalism and sets the right tone for the rest of the project.

What to put on each milestone invoice

Vague line items create disputes. Every milestone invoice should include:

• A clear reference to the milestone: "Brand identity project: Milestone 2 of 3, concept approval"
• The deliverables included in this phase (bullet list)
• Any VAT treatment (standard rate, reverse-charge note for EU B2B, or exempt)
• Payment terms: Net 7 for Milestones 1 and 2, Net 14 maximum for the final balance
• Your bank or payment details. If the client is in the UK, include your GBP receiving account or a QR code for bank transfer.

Short payment terms on earlier milestones are fair and expected. A client who asks for Net 30 on a kick-off invoice is signalling something worth noting before the project gets deeper.

The structure is the protection

Milestone invoices are not an admin task. They are the mechanism that keeps a solo design business cash-flow positive across a pipeline of 1–3 concurrent projects. Get the splits right (30/40/30 or 40/40/20), tie each invoice to a client decision point, lock the currency at sign-off, and remove "after launch" as a payment trigger from every contract you send from this point forward.

The invoicing system should then do the follow-up work for you, so you can focus on the concept deck that unlocks Milestone 2.