What should be confirmed before writing?
Do not price a request before the information that materially affects scope is visible.
- Customer and contact details
- Requested result and location
- Quantities, timing and dependencies
- Unknowns that require assumptions
How should the quote be structured?
Use a predictable reading order that moves from outcome to scope, price, conditions and decision.
- Plain-language summary
- Included and excluded work
- Separate explainable price rows
- Validity and acceptance action
What should be checked before sending?
Use a second-pass review for commercial and factual errors.
- Current customer identity
- Correct units and currency
- Consistent totals
- Approved terms and attachments
Pre-send checklist
- 1Scope matches the inquiry
- 2Every price row has a purpose
- 3Assumptions are visible
- 4The next action is obvious
Common questions
How long should a quote be?
Long enough to support the decision, but structured so the customer can scan scope, price and conditions quickly.
Can a quote be created automatically?
Yes, when incoming data and pricing rules are controlled. Important or incomplete cases should still be reviewed before sending.