Milestone payments break a project into defined stages, with a payment due as each stage completes — and you should use them on any project running longer than a month or priced above a few thousand dollars. They keep cash flowing to you throughout the work and cap how much either side has at risk at any moment.

Why milestones beat 50/50 on bigger projects

The classic 50% up front / 50% on delivery split works fine for short projects. Stretch it over a three-month build and problems appear: you work months between payments, the final invoice is large enough to make clients hesitate, and if the project derails in the middle, the money and the work delivered don't match. Milestones fix all three:

  • Steady cash flow. You're paid every few weeks instead of at two distant endpoints.
  • Smaller, easier payments. Four invoices of $3,000 clear faster than one of $12,000.
  • Risk stays balanced. At any point, work delivered roughly equals money paid. Neither side is deeply exposed.
  • Built-in checkpoints. Each milestone forces a review and sign-off, catching misalignment early instead of at final delivery.

How to structure milestones

Three to four milestones suits most projects. More than five creates administrative drag and payments too small to matter. The rules that keep milestones healthy:

  • Tie each milestone to a deliverable, not a date. "Design approved" is a milestone; "end of March" is not. Date-based milestones fall apart the moment the schedule slips.
  • Make completion binary. Anyone should be able to say whether the milestone is done. "Homepage design delivered in Figma" passes the test; "design phase substantially complete" does not.
  • Front-load slightly. Weight early milestones a bit heavier than the work strictly justifies. It keeps your exposure low and mirrors the reality that early phases carry setup cost.
  • Keep the final payment meaningful but not huge. 15–25% at the end gives the client comfort while not leaving you hostage to a drawn-out launch.

Example: a $10,000 website build

  • Milestone 1 — 30% ($3,000): on approval, before work begins. This is your deposit.
  • Milestone 2 — 30% ($3,000): design approved.
  • Milestone 3 — 25% ($2,500): development complete on staging.
  • Milestone 4 — 15% ($1,500): site live.

Put the schedule in the proposal

Milestones only work when they're agreed before the project starts. Spell out each milestone, its deliverable, and its amount in the proposal, along with one crucial clause: work on the next phase begins when the current milestone is paid. That single sentence is your leverage. You never have to chase an overdue milestone aggressively — the project simply pauses, and clients who want their project moving pay quickly.

Handling the classic failure modes

  • The stalled approval. A client who goes quiet at a review checkpoint freezes your revenue. Add a clause: milestones are considered approved if no feedback arrives within X business days.
  • Scope creep between milestones. New requests mid-phase get priced and appended as a change order, not absorbed. The milestone structure makes this easy: "happy to add that — it adjusts milestone 3 to $3,100."
  • The vanishing final payment. Keep something the client needs — final files, handover, deployment — tied to the last payment.

Collecting without the invoice shuffle

The administrative cost of milestones is real: several payment requests per project instead of one or two. The way to keep that cheap is to schedule everything once, up front. With Tendrly, your proposal carries a one-click Stripe payment link and supports payment plans of up to 5 installments with scheduled email reminders — so the milestone schedule you agreed in the proposal turns into payments that request themselves, and you stay focused on the work.

FAQ

How many milestones should a project have?

Three or four for most projects. Two is just a deposit-and-balance split; more than five means payments too small and admin too frequent. Match milestones to the project's natural phases.

What if the client wants to pay everything at the end?

Decline, politely. All-at-the-end payment means you carry 100% of the risk for the entire project. If the client has budget-timing constraints, offer to shift milestone weights — but keep an up-front payment and at least one mid-project payment.

Are milestone payments refundable?

Generally no — each milestone pays for a completed, approved stage. State in the proposal that paid milestones are non-refundable once their deliverable is approved. Refund questions should only ever concern the current, incomplete phase.