Begin with the decision
A configurator is easiest to define when you start with the choice a customer is trying to make. That might be choosing upholstery for a chair, comparing kitchen finishes or specifying a specialist vehicle. The product can be complex; the purpose of the experience should be easy to state.
Write down what a customer should understand at the end and what they should do next. A quote request, a conversation with a dealer and a direct purchase each need a different handover. This decision shapes the information you collect, the summary you produce and the systems you may need to connect.
Choose a representative product
The first product does not need to be the largest collection in the catalog. Choose one that contains the important material, component and business-rule challenges without bringing every exception into the first prototype.
A useful reference product exposes the questions the larger system will need to answer. If upholstery changes by base type, include that relationship. If the difficult part is showing polished metal beside fabric, include both. The prototype should test the assumptions that could otherwise become expensive later.
Make the option map explicit
A spreadsheet of finishes is a useful input, but it is not yet a configuration model. List the available choices, their identifiers and the relationships between them. Then agree what should happen when a customer selects an option that affects an existing choice.
- Which selections are required, and which are optional?
- Which options depend on a model, size or package?
- Which combinations are unavailable?
- Who owns the final product and pricing information?
- What should happen when an option is retired?
Audit the assets before setting the scope
Existing CAD and rendering files can be a strong starting point, but the production work depends on their condition. Review model organization, scale, separate components, material references and the available photography together.
Identify the views the customer actually needs. A product seen from a room overview requires a different level of visible detail from one inspected close enough to judge stitching. Agreeing the views early helps focus production effort where it changes the experience.
Define success in observable terms
Avoid a brief that only asks for the experience to feel premium. Define representative materials, key views, supported devices, loading expectations and the full route from first selection to final handover.
Commercial measurement should follow the intended journey. You might observe whether visitors begin a configuration, reach a valid selection or submit a useful enquiry. Decide what to measure with the team responsible for the business outcome, and avoid collecting information that serves no agreed purpose.
Leave the study with a shared plan
A good discovery phase produces more than a presentation. It leaves you with a product-option map, an asset assessment, a customer journey, a visual target and a clear view of the integrations involved.
With those decisions visible, a prototype has a precise job: demonstrate that the important assumptions work together. The production estimate then has a concrete basis, and both teams know what they are building towards.
