A guided quotation form helps a buyer explain what they need without a long unstructured email. It becomes misleading when it implies that a few answers can produce a reliable price for work that still needs assessment.
Related service: Website and ecommerce development- 01Choose the requirement
- 02Ask relevant follow-ups
- 03Review the answers
- 04Submit for assessment
- 05Assign a response owner
SECTION 01
Define the decisions the form can support
Begin with sample inquiries and ask the team what information is repeatedly missing. Translate those gaps into questions a customer can reasonably answer. Avoid asking for internal product codes or technical measurements without an explanation. Decide which answers change the next question and which simply help the reviewing employee.
W3C's forms guidance supports manageable groups and clear instructions. MDN describes validation in the browser and the need for server checks. In the brief, specify both the visible decision tree and the accepted data rules. A hidden field from an abandoned branch should not accidentally influence a later quote or appear as a current requirement.
SECTION 02
Illustrative example: a fitted storage inquiry
Imagine a furniture business asks visitors about room type, approximate dimensions, installation location, and desired finish. A visitor choosing a freestanding unit does not need questions about wall fixing. The form collects enough information for a staff conversation while making clear that measurements and installation conditions still require verification.
At the review step, show the selected options and any uploaded reference the business has approved collecting. If the visitor changes from fitted to freestanding, remove obsolete answers from the submitted requirement. Staff should receive a readable summary with the request reference, not a raw collection of unexplained field names. This is an example workflow, not a claim of a delivered customer project.
SECTION 03
Choose between a form, calculator, and product configurator
A form gathers information; a calculator applies defined assumptions; a configurator may select a purchasable combination. These are different development scopes. If the business has no maintained pricing rules, start with staff-reviewed requests. A simple explanation of the next step can be more honest and useful than a precise-looking total that will later change.
Ask the agency to test back navigation, changed answers, incomplete branches, long text, invalid uploads, and repeated submission. Confirm keyboard operation and readable errors on a phone. The handoff should include the question map, field meanings, routing rules, and the person authorized to change them. Changes to pricing or eligibility rules need review, because a minor interface edit can alter the commercial meaning of a request.
SECTION 04
Frequently asked questions
Can the form show a rough price?
Only with approved assumptions and clear limitations. Show what is included and what still needs review; do not imply automatic acceptance.
Should every field be mandatory?
No. Require information needed for the next decision and explain why sensitive or unfamiliar details are requested.
What if the customer changes an earlier answer?
Recalculate the relevant branch and remove obsolete values. Let the customer review the final requirement before submitting it.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Forms TutorialW3C WAI
- Client-side form validationMDN Web Docs
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy