How to plan project milestones and budgets you can actually track
Design milestones around client-visible outcomes, split an hours budget across them, tie each to a payment, and follow a weekly routine that shows overruns while they are small.

A project plan is only useful if you can compare it with reality every week. That means milestones that someone can verify and a budget broken into pieces small enough to check. This post builds both for an example project, ties payments to the milestones, and sets out a routine for tracking them.
What makes a good milestone
A milestone is an outcome the client can see or approve, not a stage of your internal process. "Design started" is not a milestone. "Homepage design approved" is.
Test each milestone with three questions:
- Can the client look at something and say yes or no?
- Can you name the date it should happen?
- Does something else depend on it, such as payment or the next phase?
If the answer to any is no, rewrite it. Four to six milestones suit a project of a few months. More than that and the plan becomes a task list.
The example project
Everything here is hypothetical. A studio agrees to rebuild a marketing website over 12 weeks. The client budget is $18,000. The studio plans on a blended rate of $100 per hour, so $18,000 ÷ $100 = 180 hours.
Do not allocate all 180 hours. Hold back a contingency for the unplanned, here 10 percent: 0.10 × 180 = 18 hours. That leaves 180 minus 18 = 162 hours to allocate.
Split hours across milestones
Allocate the 162 hours to the milestones:
- Discovery and sitemap approved: 18 hours
- Design approved: 48 hours
- Build complete on staging site: 66 hours
- Content loaded and QA passed: 30 hours
Check the total: 18 + 48 + 66 + 30 = 162 hours. Add the 18-hour contingency to get 180.
Now price each milestone in dollars at $100 per hour:
- Discovery: 18 × $100 = $1,800
- Design: 48 × $100 = $4,800
- Build: 66 × $100 = $6,600
- Content and QA: 30 × $100 = $3,000
- Contingency: 18 × $100 = $1,800
Total: $1,800 + $4,800 + $6,600 + $3,000 + $1,800 = $18,000.
Tie payments to milestones
Milestone payments make the plan real for the client. Say the studio invoices 20, 30, 30 and 20 percent at the four milestones:
- Discovery approved: 0.20 × $18,000 = $3,600
- Design approved: 0.30 × $18,000 = $5,400
- Build complete: 0.30 × $18,000 = $5,400
- Content and QA passed: 0.20 × $18,000 = $3,600
Check: $3,600 + $5,400 + $5,400 + $3,600 = $18,000.
The payment percentages do not have to match the hour split exactly, and here they do not. Front-loading a little protects you if the client delays later phases. Pick percentages by checking how much work you will have done and paid for by the time each invoice falls due, and make sure no milestone leaves you carrying more than you can afford.
Write acceptance into each milestone
A payment tied to a milestone needs a clear finish line. For each milestone write one sentence that says what "done" means and how long the client has to respond. For example: "Design is approved when the client confirms the homepage and two inner page designs in writing, or after five business days without comments."
Without that sentence, a milestone can sit open forever, and so does the invoice.
A weekly budget tracking routine
Budget tracking is a habit, not a report. Once a week, at the same time, do three things for each active milestone:
- Total the hours logged against the milestone.
- Estimate the percentage of the milestone that is complete.
- Compare the two.
Here is how it looks. At the end of week 5, the design milestone has 36 of its 48 hours logged. That is 36 ÷ 48 = 75 percent of the hours. The designer says the design is about 60 percent done. The gap is 15 points, and it is a warning.
A simple rule works: flag any milestone where the share of hours used is more than 10 percentage points ahead of progress. At 75 percent used and 60 percent done, this one is flagged.
Act on a flag the same week. Options are to re-estimate the remaining work, draw down the contingency on purpose, or raise a change request if the client has expanded scope.
Use the contingency deliberately
Contingency is only useful if you spend it with intent. Write each draw in a log: date, hours, reason. In the example, if the design milestone needs 9 more hours, the studio draws 9 of the 18 contingency hours. That leaves 9, and the log shows why.
If contingency is gone by the middle of the project, you have an early warning that the plan was optimistic. Better to learn that at week 6 than at delivery.
Tracking it in one place
You can do all of this in a spreadsheet, and many teams start there. Five signs your agency has outgrown spreadsheets lists the points at which that stops working. HireOrSell includes milestones, budget tracking and time logged against projects and milestones. Time tracking is part of the Pro plan, not Free, so check the pricing page for current prices.
Share the numbers with the client
You do not need to show the client your hours. Do show the milestones, the dates and where you are against them. A short weekly note works: milestone name, status, next date, anything you need from them. Budget conversations are easier when the client has seen progress every week.
Next step
Take one live project and rewrite its plan as four milestones with hours and a payment for each. Put a 10 percent contingency line in the budget, then run the weekly routine above on Friday.
Ready to run it all in one place?
Projects, clients, time tracking and invoicing in one platform.