Why fixed prices need more than rate × hours
When you quote a project price, you are taking on the risk that the work takes longer than estimated. If you price at exactly rate × hours, every surprise comes out of your pocket. Professional estimators handle this by pricing three things on top of the raw labor:
- An uncertainty buffer. Your first estimate is a median guess, not a worst case. A 15–25% buffer converts "probably 60 hours" into "priced for 69–75 hours." The fuzzier the scope, the bigger the buffer should be.
- A complexity multiplier. New technology, many stakeholders, a client known for changing their mind — these multiply risk rather than add to it. ×1.15 for some unknowns, ×1.3 or more when you're genuinely exploring uncharted territory.
- A rush premium. Compressed timelines don't just cost evenings; they block you from taking other work. If the client wants to jump the queue, they can pay for the whole queue's worth of opportunity.
Pass-through expenses — stock photos, fonts, hosting, travel — get added at cost (or cost plus a small handling margin), not multiplied.
Presenting the number
Never present the breakdown of the buffer math to the client; it invites line-item haggling. Present the final price alongside a short scope statement: deliverables, number of revision rounds, what's excluded, and the change-request rate for anything outside scope. The price is justified by the deliverable, not by your hours.
If the total feels too high for the client, reduce scope, not the price. "We can hit your budget by cutting the second concept round" keeps your effective rate intact — discounting teaches clients your first number was padded.