Understanding 50/30/20 Design Project Payments: Milestones and Risk Control

Many clients see "50% kickoff payment, 30% design approval payment, and 20% final payment" and instinctively ask: Why pay half at the beginning? Vendors have the opposite concern: What happens if they accept only a small deposit, invest several weeks, and the client suddenly pauses the project? A payment ratio is ultimately an arrangement for sharing risk, cash flow, and control.

Do not judge a payment schedule by percentages alone. More important questions are what outcome corresponds to each payment, when it is considered approved, what happens if it is not approved, and what is delivered before and after the final payment.

01 The 50% Kickoff Payment Does Not Buy One Design Comp

Requirements clarification, schedule reservation, team allocation, research, and directional exploration already occur during kickoff. The advance payment confirms that the project has genuinely started and covers early labor costs that cannot be recovered.

But a kickoff payment should not be tied only to a sentence stating "payable upon contract signing." The client should also receive the project plan, requirements checklist, communication process, and first-phase delivery date.

02 The 30% Midpoint Payment Must Be Tied to a Verifiable Milestone

The midpoint payment is best scheduled after approval of a direction or core deliverable—for example, the selected brand Logo direction, approval of the corporate website home page and core templates, or approval of an APP's key workflows and visual direction. It should not be tied to a vague phrase such as "design substantially complete."

Approval should preferably be recorded through written feedback or a phase acceptance form. The contract should also state in advance whether failure to respond by a deadline constitutes approval.

03 The 20% Final Payment Is Not Leverage for Unlimited Revisions

The final payment is usually tied to project completion, launch acceptance, or final deliverable approval. It preserves the client's right to inspect before delivery ends, but it does not allow an approved direction to be overturned at the end of the project.

Before the final payment, define whether the remaining work is defect correction, an adjustment within agreed revision rounds, or a new requirement. Each has different responsibilities and costs.

04 Align Payments with IP Rights, Source Code, and Account Handover

Design source files, development source code, production-environment permissions, and final IP rights typically transfer or take effect after all fees are paid. If the client needs some assets in phases, the contract can establish separate terms.

A vendor also should not withhold a client's own accounts, domain names, or paid third-party assets because a final payment remains. Both parties should distinguish asset ownership at the start of the project.

05 Define Settlement Rules for Pauses and Unilateral Termination

Real projects do not always follow the plan. Budget freezes, business changes, and personnel departures can all cause a pause. The contract should define when a pause requires rescheduling, how completed phases are settled, and whether unstarted work is charged.

"Deposits are nonrefundable" is not a substitute for a complete termination mechanism. A fairer approach distinguishes incurred costs, delivered work, and work not yet started.

06 Small Projects, Retainers, and Development Projects Can Use Different Structures

A single-page design completed in five days does not need a mechanical three-part payment plan. Long-term monthly services suit monthly advance payment. Long development cycles with many deliverables can add milestones for prototypes, design, testing, and launch.

The ratio is not the central issue. Funds and work should move in sync so neither party carries excessive, unsecured risk.

Common Payment Structures Compared

Frequently Asked Questions

Is a 50% Kickoff Payment Too High?

Assess it against the project timeline, early investment, and vendor size. The key is whether kickoff provides a clear schedule, phase deliverables, and an exit mechanism.

Can Revisions Continue After the Midpoint Payment?

Yes, within the agreed scope and revision rounds, but this does not automatically allow reversal of an approved direction. A redesigned direction is generally a change request.

Must the Project Be Live Before the Final Payment?

Not necessarily. A pure design project may require payment after final design approval. A development project may tie it to test-environment acceptance, production launch, or a period of stable operation.

What Happens to Payments If the Client Pauses the Project?

The contract should distinguish completed work, invested work not yet delivered, and unstarted work and define the schedule and cost of restarting.

When Are Source Files Delivered?

A common approach transfers final design and code source files after full payment. The client's own accounts, materials, and purchased assets should not be withheld.