Milestone Payments for Solo Founders — Structure Projects So You Are Never Funding Them
On a long project, the question is never "will I get paid" — it is "when, and how much of my own money is trapped meanwhile". Milestone payments answer that structurally: the client’s cash funds the project as it progresses, and no phase starts on your credit.
This guide covers the mechanics: how to slice milestones so each is genuinely payable, how much to weight the front, how to define "done" so approvals cannot be gamed, and what to do when the last 10% stalls.
The short answer
- Front-weighted milestones (40% upfront or more) eliminate most cash-flow gaps on 6-12 week projects.
- Projects with 3-5 milestones see dramatically fewer end-loaded payment disputes than single-invoice projects.
- A "done" definition per milestone, signed in advance, prevents most approval gaming at the finish line.
Who this playbook is for
Built for solo founders running multi-week projects who cannot afford to finance client work from their own cash.
Step 1: Slice the project into deliverable-sized milestones
Each milestone must produce something the client can see and value on its own: discovery doc, designed homepage, working module. Never split by time ("weeks 1-3") — split by artifact. Artifacts are easy to approve and hard to dispute; time periods invite scope arguments.
Step 2: Weight the schedule toward the front
Standard solo-founder schedule: 40% on signing, 30% at midpoint artifact, 30% at delivery. For new or larger clients, 50/25/25. The deposit funds setup risk (your unbilled learning curve), the midpoint keeps momentum honest, and the tail is small enough that a stall hurts them more than you.
Step 3: Define "done" per milestone, in writing
Each milestone ships with acceptance criteria: what is included, how it will be reviewed, and the approval window — "review within 5 business days; silence equals acceptance". Auto-acceptance clauses are the single strongest protection against the forever-reviewing client.
Step 4: Invoice the moment a milestone is accepted — or deemed accepted
Invoice attached to the delivery email itself, with acceptance criteria restated in two lines. The gap between "delivered" and "invoiced" is where payment timelines die; collapsing it to zero moves every downstream date earlier.
Step 5: Handle the stalled final payment with structure, not fury
Sequence: reminder (day 3), direct conversation about what is blocking approval (day 7), formal notice with the auto-acceptance clause cited and late fee clock referenced (day 14). If stalled on feedback, offer one consolidated revision call — the goal is converting vague dissatisfaction into a finite list, then finishing it.
Your weekly operating rhythm
| Day | Action | Time |
|---|---|---|
| Per project start | Milestone schedule + acceptance criteria signed | 2 hrs |
| Per milestone | Deliver, restate criteria, invoice same day | 30 min |
| Weekly | AR check: anything past grace window? | 10 min |
| Per project end | Debrief: which milestone dragged? Fix the slicing | 30 min |
KPIs that tell you it is working
| Metric | Healthy target | Why it matters |
|---|---|---|
| Cash cycle per project | Never negative overall | The client’s deposits should always cover work-in-progress |
| Milestone approval time | Under 5 business days | Slower means acceptance criteria need sharpening |
| % collected by midpoint | 60-70% | Front-weighting sanity check |
| Final-milestone stalls | Rare and short | Auto-acceptance language should make stalls impossible to extend |
Common mistakes to avoid
- Equal-weight milestones (33/33/33). Back-loading invites gaming; you are safest when the final payment is the smallest.
- Splitting milestones by calendar time. "Month one" is unfalsifiable; "homepage designed and approved" is checkable in minutes.
- Starting the next milestone while the previous invoice is overdue. The pause clause only protects you if you actually use it, kindly and promptly.
A tool stack that fits a one-person budget
| Tool | Where it fits |
|---|---|
| Bonsai / Dubsado | Milestone schedules wired to invoicing |
| Stripe | Deposit links and milestone payment links |
| Notion | Acceptance criteria template per milestone type |
| Google Docs | The auto-acceptance clause, in every contract |
Keep going
Use these internal references while implementing this guide:
- One Person Company Hub
- How to Start a One Person Company
- Solopreneur Operating System
- Scope Creep Contract Language
- A Pro Bono Policy for Solo Founders
- Refund Policies for Services
FAQ
Q: What if a client refuses any upfront payment?
Treat it as a serious risk signal. Compensate structurally: shorter milestones (one week each), payment at the end of each week, and higher total price for the payment risk. If they refuse weekly terms too, the client is asking you to finance them — decline politely.
Q: How do acceptance windows work legally?
The contract states the review period and that failure to respond constitutes acceptance. This is common commercial practice and enforceable in most jurisdictions — but have a local professional check your template once; the clause must match your jurisdiction’s norms.
Q: Can milestones coexist with retainers?
Yes — use milestone logic inside retainer quarters: deliverables defined per month with acceptance windows. This keeps retainers scoped (see the leak problem) while preserving the predictable revenue you chose them for.
Q: How many milestones is too many?
More than five per project and administration eats margin. Large projects get phases, each phase gets 2-3 milestones. If you find yourself invoicing weekly on a small project, switch to a simple weekly-in-arrears subscription instead.
Get the weekly operating brief
Every Monday: 3 moves, 5 minutes. Actionable strategy for your one-person company — no fluff, no filler.