Map each input to the estimate it can actually change
Read the guide →Guide preview
Ask for an answer only when it changes the estimate or a necessary next action.
Separate quantity, units, unknowns and contact purpose before building the calculation.
Separate quantity, units, unknowns and contact purpose before building the calculation.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
Ask for an answer only when it changes the estimate or a necessary next action.
Do not treat an unknown answer as a valid zero simply to let the form continue.
The same number means different work when the unit changes; keep the unit attached throughout the journey.
Reject or explain out-of-range values; do not quietly clamp a visitor’s request into a cheaper job.
Ask the branch-defining questions early, then calculate from the final relevant answers.
A range should come from stated uncertain inputs, not an arbitrary confidence-looking percentage.
An honest manual-review path is better than a precise estimate for work the model cannot understand.
Separate the value of the estimate from permission to contact someone; explain any required handoff.
A syntactically valid answer can still be inaccurate; do not confuse format checks with identity or suitability.