Web · Implementation study
A quote estimator that qualifies before the first call
An interactive scoping tool that turns a vague enquiry into a shared understanding of budget, so the conversation starts from a realistic number instead of ending on one.
What the demo shows
The estimator uses illustrative scope options and an example rate model. The range it produces is a demonstration of the interaction, not a price list, and no submission is sent anywhere from this page.
Proposed system flow
- 01Scope selections
- 02Rate model
- 03Confidence range
- 04Qualified enquiry
01
Price a range, and be explicit about why it is a range
A single number invites an argument, and a number with no explanation invites disbelief. A useful estimator returns a band whose width reflects the unknowns still in play, and narrows visibly as the visitor answers more questions. That behaviour teaches the reader something true about custom work: precision is bought with information. The rate model itself belongs in one reviewed place rather than scattered through interface code, so an estimate can be reproduced months later and a pricing change does not require hunting through components.
02
Ask only the questions that move the number
Every question costs completions, so each one has to earn its place by materially changing the output. Integrations, content volume, whether an existing system must be kept alive, and compliance obligations move a software estimate; a visitor's job title does not. Questions should be ordered so the largest drivers come first and the estimate becomes useful before the form is finished, which means a visitor who abandons halfway still leaves with something and still leaves behind a usable signal about what they need.
03
Make the calculation legible to assistive technology
A figure that updates silently when a control changes is invisible to a screen reader user, who is left with a form that appears to do nothing. Announcing the updated range through a polite live region, and keeping every control a real labelled form element rather than a styled div, is what makes the tool usable rather than decorative. Grouped options need proper fieldset semantics so the question is announced along with the choices, and the running total needs to be reachable in the tab order rather than parked visually beside the controls.
04
Treat the submission as the beginning of a workflow
The estimate itself is a by-product; the valuable output is a qualified enquiry with the scope attached. That record should capture the selections, the resulting range, the rate model version used, and the page the visitor arrived from, then route to whoever answers it with enough context that the first reply can be specific. Sending the visitor their own copy makes the number harder to misremember and gives the follow-up conversation a shared reference point.
Validation plan
- Confirm the estimate is computed from one shared rate model and that the same selections reproduce the same range after a deployment.
- Verify each range update is announced by a screen reader and that every control is reachable and labelled without a mouse.
- Measure completion and abandonment per question to find the ones costing more than they contribute, and remove them.
- Compare estimator output against the final agreed scope on real projects and recalibrate the model rather than defending the original number.
More in web
Have a similar problem to solve?
Discuss your project