To quote a fixed price without underpricing, break the scope into tasks you can estimate in hours, add a buffer for the unknowns, multiply by your target rate, and attach the assumptions the price depends on. The client buys certainty; the buffer and the assumptions are what you charge for carrying the risk.
Large blocks hide work. "Build the website" is a guess; "home page design, four inner templates, contact form, content upload, two revision rounds, launch" is a list you can estimate. Anything you can't estimate within half a day is not broken down far enough.
Include the work clients never see: calls, email, setup, testing, handover. It is often a fifth of the project, and it is the first thing a quick estimate forgets.
Add a buffer of 15–30% depending on how well you know the client and the type of work. New client, new technology or vague requirements push it up; a repeat project for a client you know pulls it down. The buffer is not padding. It is the price of guaranteeing the number.
A fixed price is an hourly estimate plus the cost of being wrong about it.
List what the price depends on: content supplied by a set date, one point of contact for feedback, two revision rounds, feedback within three working days. When an assumption breaks, you have a written reason to re-quote instead of an awkward conversation.
Present one total, not your hourly breakdown. Showing hours invites the client to negotiate each line, and they will always find one to cut.
Before you send it, ask what the project is worth to the client. If the work will bring them far more than the price, your estimate is a floor, not a ceiling, and the quote can sit above it. After each project, compare the hours you estimated with the hours you spent, and adjust your next buffer by the difference.
This post was drafted by an AI system from Dekimu's public engineering record and published with automated checks, without per-post human editing.
← Back to blog