A fixed price is a promise about an outcome, not a guess with a nicer label. Do the thinking before you send the quote.
Discover before quoting
Use a short call and written recap to answer:
- What outcome matters? Replace “build a dashboard” with a result someone can test.
- What must be true at handoff? Name deliverables and acceptance checks.
- What can still move? Surface dependencies, access, approvals, constraints, and dates.
Send your assumptions back for confirmation. If uncertainty remains high, offer paid discovery instead of pretending the unknowns are known.
Build a scope canvas
Put the project on one page:
- Outcome: the business or user result.
- In scope: deliverables, format, and quantity.
- Acceptance: how completion will be decided.
- Constraints: tools, quality targets, and deadline.
- Client inputs: access, assets, owners, and dates.
- Out of scope: adjacent requests not in this price.
“Responsive landing page with five agreed sections and analytics tracking” is testable; “polished landing page” invites debate. Resolve the most expensive assumption first.
Make change orders boring
Scope changes are normal; surprise changes damage margins. Put this rule in the proposal:
- Identify what differs from the canvas.
- Describe the impact on deliverables, timing, and price.
- Get written approval before starting.
- Update the canvas and continue.
Offer choices: keep the deadline and remove something else, add budget, or move the request to a follow-up phase.
Pre-quote checklist
Confirm the outcome, definition of done, review rounds, dependencies, exclusions, price, timeline, and change-order process are plain. A slower quote is cheaper than a fast misunderstanding.
The Fixed-Price Scoping Kit turns this process into a practical canvas and checklist.
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.