User Experience
Explain configuration estimates without implying a final quote
Configuration tools can help customers explore options without pretending to issue a binding price. Make assumptions, exclusions, uncertainty, and the next scope discussion visible beside any indicative estimate.
A configuration screen can make an uncertain proposal look exact. Customers select options, see a polished total, and may assume the commercial scope is settled. Design the result to support an informed conversation instead. The output must clearly state that it is an indicative estimate, not a final quotation, and remains subject to scope discussion and agreement.
Explain what the estimate represents
State what the selected configuration includes and which assumptions the calculation uses. Separate confirmed choices from defaults the customer has not reviewed. Identify excluded work, dependencies, and information still needed. Do not hide these qualifications in a distant general disclaimer beneath an apparently definitive total.
Where uncertainty is material, explain its cause rather than adding false precision. An integration option might depend on an external interface that has not been assessed. The next useful step is to discuss that dependency, not suggest that selecting a checkbox resolves it.
Keep exploration separate from commitment
Use action labels that match the actual next step, such as requesting a scope discussion or sharing a configuration. Avoid a purchase-style button if the process only sends an inquiry. The saved summary should repeat the estimate limitation so that forwarded copies retain the same meaning.
For submissions that create legal commitments or financial transactions, WAI describes safeguards including reversal, checking, or confirmation.[7] That guidance concerns interaction safeguards. It does not establish the legal status of an estimate or replace appropriate commercial review. Confirm the intended process with the responsible business owner.
Hypothetical example: configuring a service portal
A hypothetical buyer selects two interface languages, an approval workflow, and an integration option for a service portal. The tool produces an indicative estimate with explicit assumptions about the workflow and available integration documentation. It identifies migration and third-party charges as unresolved discussion items, not silently included promises.
The buyer changes the integration option. The screen explains which assumption changed and marks the earlier summary as superseded within the session. The next action requests a scope discussion. No final quotation or delivery commitment exists merely because the configuration has been saved.
Review the result as a customer would
Read the screen, downloaded summary, and inquiry confirmation separately. Each should distinguish an estimate from an agreed commercial offer. Ask a reviewer unfamiliar with the tool what they believe is included and whether they think they can purchase immediately.
More qualifications can make exploration harder to read. Use a concise limitation beside the result and structured detail nearby. Do not remove uncertainty merely to simplify the layout.
- Display indicative estimate and not final quotation beside the result.
- List assumptions, exclusions, and unresolved dependencies.
- State that scope discussion and agreement are required.
- Keep action labels consistent with an inquiry rather than a purchase.
- Repeat limitations in saved or shared configuration summaries.
