Why you should never quote hours × rate
Software estimation research and every freelancer's experience agree: projects take longer than estimated, almost never shorter. The work has unknowns, the client adds 'one small thing,' and revisions multiply. A risk buffer of 15–25% on top of your base estimate isn't padding — it's the honest expected cost of the project.
Revisions deserve their own line because they behave differently from scope risk: they arrive at the end, when you're least able to absorb them. Pricing in a revision allowance (and capping included rounds in your contract) keeps the last 10% of the project from consuming 30% of the time.
Why three tiers beat one number
A single price invites a yes/no decision — and 'no' ends the conversation. Three options change the question from 'should we hire you?' to 'which version should we buy?'. Anchoring also works in your favor: next to a premium tier, your standard price reads as reasonable rather than expensive.
Keep the tiers honest. The essential tier should be genuinely smaller in scope (not the same work at a discount), and the premium tier should carry real value: faster delivery, more revisions, post-launch support.
Frequently asked questions
- How big should my risk buffer be?
- 15–25% for well-understood work, 30–50% for projects with new technology, vague requirements, or a client you haven't worked with before. If a project feels impossible to estimate, that's a signal to price hourly instead.
- Should I show clients the hour breakdown?
- Usually no. Quote the project price and the deliverables. Itemized hours invite line-by-line negotiation and anchor the client to your time instead of the outcome you're delivering.
- What if the client picks the cheapest tier?
- That's a success, not a failure — the essential tier is scoped smaller, so you're paid fairly for less work, and clients who start small frequently upgrade once they trust you.