Online Quote Configurators: When They Help and How to Design One

A quote configurator is useful when the requests you receive are all different but the questions to ask are always the same. It isn't there to make a price appear where there wasn't one before: it's there to collect, in an orderly way, what today takes three emails and a phone call to extract, and to get the sales team a request that's already readable. Designed to replace the salesperson, it doesn't work; designed to prepare their work, it almost always does.

Which variables deserve a place in the configurator

The temptation is to rebuild every possibility in the catalog online. It's the surest way to end up with a long path no one completes. The variables worth keeping meet two conditions at once: the customer knows how to answer, and the answer noticeably changes what you'll offer them.

• The customer knows how to answer. They have the measurements of a room; a material's rating or the required load capacity, often not. If a question needs your own expertise, it's not a configurator question: it's a site-visit question.
• The answer changes something. An option with little impact that lengthens the path should be asked later. The configurator isn't a complete order form.
• The answer is verifiable, or stated as needing verification. A quantity given by the customer can be wrong: it should be treated as an assumption, not as established fact.

A practical way to choose: reread the last twenty requests you received and the answers you gave. The questions you had to ask almost every time are the ones to include; the ones asked twice out of twenty stay out.

Allowed combinations and missing information

A configurator that allows impossible combinations produces requests the sales team has to unpick, and in the meantime the customer has formed a wrong idea of what they'll receive. Compatibility rules need to be written in advance, and that's work for whoever knows the product, not whoever builds the site.

• Forbidden combinations should be prevented where they're chosen, not flagged at the end. If a finish doesn't exist for a certain size, it shouldn't appear when that size is selected.
• Limits need to be stated with the reason: “beyond this length a joint is needed” is useful information, “value not allowed” is a wall.
• Missing information needs to be stated. If shipping depends on the delivery location and that isn't known yet, it should say it will be quantified later.

Estimate, quote, and confirmation aren't the same thing

Confusing them is the mistake that makes the configurator useless, because the three documents have different value and need to be presented differently.

The estimate can be shown right away, the quote is sent after a human check, the confirmation arrives once availability and timing have been verified. Skipping a step is possible, but it needs to be a decision made on purpose, not a side effect of how the site was built.

An illustrative path

A company that makes custom fixtures for shops receives generic requests and loses time reconstructing them. The configurator collects the bare minimum needed.

1. First question: what type of space. Three possible answers, worded the way a customer would say them. The choice changes the following questions.
2. Measurements and quantities, with a reference drawing next to the fields, so it's clear what to measure and from where.
3. Materials and finishes, with only the achievable combinations and a note on choices that extend lead times.
4. Uploading a floor plan or a photo: optional, but it's the attachment that avoids an exploratory site visit.
5. A readable summary of the configuration, with the order of magnitude stated as indicative and a list of what's still to be verified: shipping, assembly, condition of the space.
6. Submission. The customer receives the summary in writing, the office receives the same record with the attachments and a unique reference.

The value isn't the calculated number: it's that the request arrives complete, and whoever answers no longer has to ask for the measurements.

What arrives at the department

A configurator that ends up in a plain-text email has only solved half the problem. The configuration needs to be delivered in a form that can be worked with.

• A summary a person can read, with the choices expressed in words, not internal codes.
• The same data in structured form, so whoever prepares the quote doesn't have to retype it: retyping is where errors originate.
• The attachments linked to the request, not scattered across different mailboxes.
• A unique reference to cite in all subsequent communications, including phone calls.
• An indication of what the system calculated and what the customer stated: these are two different levels of reliability.

When the configurator isn't worth it

There are situations where building one is an expense that doesn't pay off.

• When there are only a few variables: two questions fit better in a simple form, without building a step-by-step path.
• When product rules aren't written down anywhere and change often. The configurator fixes them in place: if they're unstable, it'll be wrong within a month.
• When every job requires a site visit anyway. A form that prepares for the visit, with photos and measurements and no number on screen, works better.
• When requests are few. The cost of maintaining the rules is justified by volume.

What this guide doesn't cover

This guide covers the customer-facing part: what to ask them and what to show them. How offer documents are produced internally — pricing rules, discounts, versions, validity, consistency across price lists — is a business management software matter and has its own guide. The upstream choice between a browsable catalog, a quote request, and direct purchase is also covered elsewhere.