Start with the work, not the number
Before calculating a price, write down what the client will receive. A budget for “a website” is hard to estimate; a budget for a five-page site with supplied copy, a contact form and one round of revisions is much clearer. Note the deliverables, formats, deadlines and who is responsible for providing materials. If a detail is undecided, label it as an assumption rather than silently including it.
Break the work into stages that match how you will actually complete it: discovery, planning, production, feedback, revisions and handoff. A designer making a presentation, for example, might list a kickoff call, an outline, slide design, one review round and export of the final file. This makes small but necessary tasks visible and gives both you and the client a way to spot missing work before it becomes a surprise.
Estimate time and direct costs
For each stage, estimate the hours you expect to spend and multiply them by the rate you use for planning. Include communication, file preparation, testing and delivery, not only the time spent creating the main asset. If a task is unfamiliar, estimate its parts separately instead of treating it as a single block. Keep your working calculations even if you ultimately offer the client one fixed project price.
Next, list costs that arise specifically because of the project. These might include a licensed image, a font, printing, a specialist collaborator or a tool purchased for the assignment. Check whether the client will buy an item directly or reimburse you for it, and whether approval is needed before you spend. Do not bury an uncertain purchase in an apparently firm total.
For a simple illustration, suppose you estimate 20 hours of work at a planning rate of 50 per hour, plus 80 for approved assets. Your starting estimate is 1,080 in the agreed currency. Those figures are only an example: the useful habit is to show how the total follows from defined work and known costs.
Make room for revisions and uncertainty
Creative work often changes once a client sees a draft. Define how many feedback rounds the budget includes, what counts as a revision and when feedback is due. Changing the color or wording of an approved design may be a revision; requesting a new concept or an additional deliverable may be new scope. Clear boundaries let you welcome feedback without promising unlimited work.
You can also set aside a modest allowance for work that is difficult to predict, such as troubleshooting a file supplied in an unexpected format. Treat that allowance as part of your internal plan, not as a reason to leave the brief vague. If a major unknown could substantially change the work, state what you need to learn and when you will revisit the estimate. A budget is more trustworthy when its assumptions are visible.
Turn the calculation into a clear proposal
A client-facing budget should be easy to connect to the project brief. Name the deliverables and included stages, give the price in a stated currency, identify any separately approved expenses and explain the revision limit. Add a simple payment schedule tied to understandable milestones, such as project start and final delivery. Make clear what files or access the client will receive at handoff.
State how additional requests will be handled. For example, you might pause to describe the new work, its cost and its effect on the timeline, then wait for written approval before proceeding. This is more useful than a vague warning that extra work “may cost more.” Keep the approved brief and budget together so you and the client can refer to the same version.
Track the budget while you work
Once the project starts, record time and expenses against the stages you estimated. A basic spreadsheet with columns for task, planned hours, actual hours, planned cost and actual cost is enough for many small projects. Review it at natural checkpoints, especially before a feedback round or a new stage. If the remaining work no longer fits the plan, discuss the reason early rather than waiting until delivery.
After handoff, compare the estimate with what happened. Note which tasks took longer, which assumptions held and whether the revision allowance was realistic. Keep these notes with the project brief, not just the final invoice. Over time, they become a practical reference for budgeting similar work—and for deciding how to describe that work accurately in a portfolio.
