How to scope a project backwards from a fixed client budget
A client names a budget and asks what you can do for it. Build the scope backwards: set a reserve, convert dollars to hours, then cut or phase work until the plan fits.

A client says the budget is $9,000 and asks what you can deliver. If you quote the full wish list, you lose the deal. If you say yes to all of it, you lose money. The better move is to work backwards from the budget and agree what fits. This post walks through that method with a worked example.
Start by checking the budget is real
A stated budget can mean three different things: a hard ceiling, a rough target, or an opening position. Ask one plain question before you plan anything: "Is that the most you can spend, or a number to aim for?"
Then ask what the budget must cover. Some clients expect it to include stock images, hosting, paid tools or a second round of changes. Write down what is inside the number and what is not. If the client will not say, plan for the strictest reading.
If there is no budget at all, a different approach applies. See how to price a small project when the client has no budget.
Turn dollars into hours
Dollars hide the real constraint, which is your time. Divide the budget by your rate to see how many hours it buys.
Say your internal rate is $100 an hour. A $9,000 budget buys 9,000 / 100 = 90 hours. If you are unsure of your own rate, the hourly rate calculator shows the minimum you need to charge.
Now you have a number you can plan against: 90 hours. Everything that follows is about fitting the work inside it.
Hold back a reserve first
Projects rarely run exactly to plan. Before you allocate any hours, set aside a reserve. In this example it is 10% of the budget: 9,000 x 0.10 = $900, which is 9 hours.
That leaves 9,000 - 900 = $8,100 to plan against, or 81 hours.
The reserve is not padding to hide from the client. It is a stated part of the plan, and you can tell them it covers small changes and surprises. If you want a more careful way to size it, three-point estimating gives a buffer from your own best and worst cases.
Estimate the full wish list
Next, estimate what the client actually wants, ignoring the budget for a moment. Break it into tasks and give each a number of hours. In this example:
- Discovery: 8 hours
- Design: 30 hours
- Build: 36 hours
- Testing: 10 hours
- Project management and client communication: 12 hours
- Two revision rounds: 5 hours each, 10 hours
Add them: 8 + 30 = 38. Then 38 + 36 = 74. Then 74 + 10 = 84. Then 84 + 12 = 96. Then 96 + 10 = 106 hours.
At $100 an hour, the full scope costs 106 x 100 = $10,600. That is $1,600 above the $9,000 budget, and the gap is bigger once you count the reserve.
Find the gap
Compare the full estimate with the hours you can plan against.
- Full scope: 106 hours
- Plannable hours after the reserve: 81 hours
- Gap: 106 - 81 = 25 hours
You now know exactly how much has to change: 25 hours of work, worth $2,500 at your rate. This turns a vague conversation about money into a concrete one about what to remove.
Close the gap in one of four ways
You have four honest options. You can combine them.
- Cut scope. Remove features, pages or deliverables. This is the cleanest option.
- Phase the work. Deliver what fits now and put the rest in a later phase with its own budget.
- Raise the budget. Show the client the gap and ask whether more is possible.
- Reduce the service level. For example, fewer revision rounds or a slower turnaround.
The option to avoid is cutting your rate quietly to make the numbers work. That solves this one project and teaches the client that the number was negotiable.
A worked example of cutting scope
Take the 25-hour gap and choose cuts together with the client.
- Drop one secondary page template: 12 hours
- Reduce revisions from two rounds to one: 5 hours
- Move one lower-priority feature to a second phase: 8 hours
Add the cuts: 12 + 5 = 17. Then 17 + 8 = 25 hours. The gap is closed.
Now check the final plan. Planned hours are 106 - 25 = 81. At $100 an hour, that is 81 x 100 = $8,100. Add the $900 reserve and the total is 8,100 + 900 = $9,000, exactly the client's budget.
Present it as a choice, not a loss. The client sees what they get for $9,000, what moved to phase two, and what the reserve is for.
Write the plan into the agreement
A plan that is not written down will drift. Put three things in your scope statement: the deliverables, the number of revision rounds, and what is out of scope.
Then agree how extra requests are handled. When something outside the plan comes up, you can point to the document and offer options, as described in how to say no to out-of-scope requests.
Track hours against the budget
The method only works if you can see how fast the hours are being used. Check logged hours against the 81 planned hours every week. If a stage runs over, you find out while there is still reserve left to absorb it. HireOrSell has project budget tracking and time entries linked to projects and milestones, and time tracking is part of the paid plans, so check the pricing page for current details. A spreadsheet works too if you keep it current.
This post is general information, not legal or accounting advice.
Next step
Pick one current or upcoming project with a stated budget. Divide the budget by your rate, set aside a 10% reserve, and compare the result with your full estimate. If there is a gap, list the cuts you would offer before you reply to the client.
Ready to run it all in one place?
Projects, clients, time tracking and invoicing in one platform.