You take on a three-month project, start work in January, and invoice when you’re done in March. If the client pays on Net 30 terms, you might see money in April, four months after you started. Meanwhile, software subscriptions, contractors, and your rent don’t wait for your client’s AP cycle.
Why Long Projects Require Milestone Billing
Projects over 60 days create two cash flow risks. First, you front a significant amount of time and overhead before receiving any payment. Second, the longer the project runs, the more opportunity there is for scope drift, relationship friction, or client-side budget changes to complicate the final payment.
Milestone billing solves both problems by converting a single large payment event into three smaller, lower-risk ones.
The 30-40-30 Framework
Invoice 1, Deposit (30%): Due at contract signature, before work begins. This covers your first four to five weeks of work plus any upfront costs: software licenses, subcontractors, research tools. It confirms the client is financially committed. No deposit, no start date.
Invoice 2, Midpoint (40%): Due upon delivery of the primary midpoint deliverable. The 40% is the largest payment because it corresponds to the heaviest phase of the project, the core work. Define the midpoint milestone precisely in the contract: “Delivery of the first complete draft” or “Delivery of the wireframe set” or “Completion of the first development sprint.” This payment should arrive when the project is roughly half complete by effort.
Invoice 3, Completion (30%): Due upon delivery of the final deliverable. The 30% final payment is intentionally smaller than the midpoint payment. This matters because it makes it less tempting for a client to delay the final payment, the absolute amount is lower, and the cost of not paying is easier to communicate. It also means that if a final payment dispute arises, you’ve already received 70% of your total fee.
The final payment is 30% rather than 50% by design. A smaller final payment is easier to collect, and you’ve already received the majority of your income before the project close conversation begins.
Defining Milestones That Don’t Depend on Client Approval
The milestone trigger should always be your delivery, not client approval. “Upon delivery of the first draft”, not “upon client approval of the first draft.”
If you tie payment to client approval, a slow or indecisive client can delay your invoice indefinitely without technically violating your contract. Tie billing to your action. If the client needs revisions after delivery, that revision process happens in parallel with your invoice being due.
Your contract can include: “Invoice 2 is due upon delivery of [Deliverable]. Client may request up to two rounds of revisions, which will be addressed within [timeframe]. Invoice 2 is not contingent on completion of revisions.”
The Deposit as Commitment Signal
A client who pays the 30% deposit without hesitation is telling you something: this project is real, budgeted, and a priority. A client who drags their feet on the deposit is telling you something too.
Use deposit payment as a data point. A client who takes two weeks to process a deposit will likely take two weeks to process every subsequent invoice. Price that lag into your schedule. A client who pays the deposit within 48 hours is probably running a tight, organized operation that values your time.
Adjusting the Structure by Project Type
The 30-40-30 split is the default, but some project types benefit from variations:
- Research/strategy projects: 50-50 (heavy upfront, large final delivery). These projects have no mid-deliverable.
- Development projects with multiple sprints: 25-25-25-25 (quarterly milestones). Keeps cash flow steady across four equal phases.
- Small projects under 4 weeks: 50-50. Simple, clean, protects against non-payment on short engagements.
- Retainers: Monthly in advance. The retainer is its own milestone structure.
The right milestone structure mirrors the project’s effort curve. Front-load payment where you front-load effort. The 30-40-30 default works because most projects front-load planning and peak at execution.
The Contract Language
In your “Payment Terms” section:
“Project fees are billed as follows: Invoice 1 (30%, $[amount]) upon contract signature; Invoice 2 (40%, $[amount]) upon delivery of [specific midpoint deliverable]; Invoice 3 (30%, $[amount]) upon delivery of the final deliverable. All invoices are due within [Net 14 / Net 21 / Net 30] days of issuance. Work pauses if any invoice is not paid within [14] days of its due date.”
The work-pause clause is critical. It gives you a contractual mechanism to stop the project if an invoice goes unpaid, without being in breach yourself.
What to Do When a Client Misses a Milestone Invoice
If Invoice 2 is not paid by its due date, send a brief email: “Invoice 2 ([amount], due [date]) is currently unpaid. Per our agreement, I’ll be pausing work on [project name] until this is cleared. Please let me know the expected payment date.”
Then actually pause. Do not continue delivering work toward Invoice 3 while Invoice 2 is outstanding. Doing so communicates that your payment terms are negotiable and weakens your position on every future invoice.
