How to split a project into milestones

What a good milestone looks like

A milestone is a chunk of work with a clear finish line and its own payment. Think of it as a checkpoint. At the end you can look at the result, try it, and say yes or ask for changes.

• It delivers something you can use or see, not only internal work.
• It has a short list of things that must work, written before the work starts.
• It fits a fixed time frame. On ErdiBuilds, Each milestone is funded before work starts and runs 1, 2, 3, 4, 6 or 8 weeks.
• It is paid for on its own, so risk stays small. Milestones are from 50 to 2,000 each in your project currency.

A method in four steps

1. Write the user journey: the path from opening the product to reaching the goal.
2. Mark the smallest version that makes the journey work end to end. This is your first release.
3. Cut that version into slices, each one adding a working piece, like sign-up, then the main screen, then payment.
4. Write a done-list for each slice: three to six checks you can do yourself.

The free milestone planner helps with steps three and four. It runs in your browser and lets you move pieces around until the plan feels right.

Example plan for a booking app

Here is a sample plan with phases and weeks, no prices. Your own plan will differ, and a developer may suggest a better order.

Mistakes that make milestones hurt

• Splitting by technical layer, such as database first and screens last. You see nothing for weeks. Slice by what users can do.
• A giant last milestone called Everything else. Keep every piece small, including the finish.
• Vague checks like looks good. Write checks you can test with a click.
• Changing scope inside a milestone. Put new ideas into the next one.

How approval fits in

After delivery you review the milestone. You can approve it or request changes. If you do not respond, it is approved automatically after 14 days, so check delivery notifications. Funds are released after approval and a short holding period. Unless both sides agree otherwise in writing on the platform, the rights to the result of a milestone pass to the client once that milestone is paid in full.

Not sure what goes in the first milestone? Start from a clear project brief and your plan will follow faster.

Writing a done-list that works

A good done-list uses plain checks. Instead of the search works, write: I type a city, press search and see at least one result with a name and a photo. Checks like this leave little room for different readings, so approval becomes quick and calm.

Share the done-list before the milestone is funded. If the developer sees a check that is unclear or too big, you can fix it while changing the plan is still cheap.