Quote a fixed-price project with fewer surprises
Convert uncertainty into explicit assumptions before you commit.
Break down delivery effort. Resolve material unknowns.
Break the work into deliverables
Estimate the labor and purchased inputs for each meaningful deliverable. Add project management, quality checks, and the expected revision work. Compare with completed projects when you have records; do not treat your best-ever delivery time as a normal estimate.
Name the uncertainties
Identify missing content, unknown site conditions, third-party dependencies, and unclear acceptance criteria. Decide which uncertainties can be resolved before pricing and which require a stated assumption. For highly uncertain work, a paid discovery phase may be more suitable than a precise-looking guess.
Stress-test the numbers
Model a realistic overrun in hours and a change in input costs. Check whether the resulting price still supports the target gross margin. A contingency is an estimating tool, not a substitute for defining the scope or communicating changes.
Review actual performance
After delivery, record the estimate, actual cost, and reasons for variance. Keep a short note on assumptions that proved wrong. Use that information to improve the next quote instead of relying on whether the job felt easy or difficult.
A fixed-price estimate with an uncertainty
Illustrative example—not a reported client result.
| Input or decision | Illustrative application |
|---|---|
| Known work | Three defined deliverables |
| Unknown | Condition of an existing integration |
| Response | Inspect the integration before final pricing |
| Boundary | Price excludes unverified third-party repair work |
Price the uncertain part explicitly
Illustrative working example, not a reported client result.
A website refresh appears to require 30 hours at an internal planning rate of $60, giving $1,800 in labor cost. The existing content has not been inventoried, and nobody knows whether the old forms can be reused. Instead of hiding those unknowns inside an optimistic total, separate the known work from the uncertain work. A bounded technical review may reveal whether the project needs a simple rebuild or a different integration.
You can then quote the defined scope, include a clearly stated allowance, or split the project into a discovery stage followed by delivery. Whichever route you choose, describe what happens when the assumption proves false. An estimate is easier to defend when its dependencies were visible before the client accepted it.
| Checkpoint | Working record |
|---|---|
| Known effort | Named deliverables with estimated hours and direct costs. |
| Unknown | Condition of existing content and integrations. |
| Control | A review, a bounded allowance, or a separate discovery stage. |
| Change trigger | A documented condition that requires a revised scope or price. |
A contingency is not a substitute for understanding the work. Adding an arbitrary percentage to a poorly defined project can still leave both parties with incompatible expectations.
Should I disclose my internal hourly estimate?
That depends on the engagement. You can explain deliverables, assumptions, and change triggers without publishing every internal cost calculation. Avoid implying that a fixed fee buys unlimited work.
Use the related business calculator to test the numerical assumptions where applicable. Record nonfinancial decisions in your action plan.
Put the idea to work.
- Break down delivery effort.
- Resolve material unknowns.
- Review the estimate against actual cost.
One more question
Is contingency the same as profit?
No. Contingency addresses estimated uncertainty; profit is what remains after the relevant costs. Keep the two concepts explicit in internal planning.
AI-assisted educational content. Examples are illustrative, not reported client results. Editorial standards.