What a sales-ready 3D configurator lead should include

A sales-ready 3D configurator lead is more than a contact form submission. It links a person and their buying intent to a saved product configuration: the model, dimensions, selected options, rule status, price context and the next action for sales. If those details are missing, a salesperson has to start the configuration again on the first call.

For a manufacturer or dealer, the useful question is not “How many leads did the configurator collect?” It is “Can the person receiving this enquiry understand what the buyer chose, what remains undecided and what can be quoted?” This guide gives you a field map and a set of tests for answering that question. It is intended for teams evaluating or planning a 3D product configurator, not as a universal CRM schema.

When does a visitor become a sales-ready project?

Treat browsing, saving and requesting a quote as different states. A person who changes a roof color has shown interest, but has not necessarily asked to be contacted. A quote request creates a task for someone to review and answer. Conflating those states inflates “lead” totals while leaving the sales team unsure what to do.

For most configurable products, the quote enquiry is the first point at which a sales representative needs a complete, actionable record. A lead-generation workflow should be designed around that handoff, not around the form fields alone.

Which fields belong in the handoff?

Keep the buyer's answers and the system's interpretation separate. “Anthracite frame” is a selected option; “this combination is allowed under catalogue revision 12” is a rule result. Likewise, a visible price may be final for the configured scope, indicative, or awaiting review. Those distinctions prevent the next team from treating an incomplete enquiry as a confirmed order.

Not every field has to be demanded before the buyer can explore. Ask for personal details when there is a clear reason to respond, and collect only the information needed for that journey. The crucial design decision is that the product data stays linked to the enquiry when the buyer does submit it.

A pergola example: what should the sales team receive?

Consider a buyer configuring a wall-mounted pergola. They choose a 4.2 × 3.5 m footprint, an anthracite frame, a louvered roof and LED lighting, then request a quote. They have not selected a side screen, and installation depends on a site check.

A weak handoff reads: “New website lead — interested in a pergola.” A useful project record tells the salesperson what can happen next:

A configurator should not show a fixed price when site conditions, installation or exceptions still change the commercial result. The pergola configurator page shows the product category; the test in a real implementation is whether your own catalogue and pricing rules produce a reliable handoff for your team.

The price needs a status, not just a number

“Live price” can mean several things. Decide what your buyer is allowed to conclude from the number on screen, then carry that meaning into the quote enquiry.

The amount by itself does not tell sales which category applies. Keep the currency, included and excluded items, tax treatment where relevant, account or dealer context, and pricing-rule revision with the saved project. If a representative changes the configuration later, retain the submitted version so there is no ambiguity about what the buyer first saw.

Preserve the configuration across CRM and sales tools

The configurator project and the CRM contact are related, but they are not the same record. One contact can request quotes for several products. One product project can have several revisions. A dealer may work on behalf of an end customer. Model those relationships explicitly instead of squeezing the entire specification into a single “lead notes” field.

A practical mapping is:

1. Give the configured project its own stable identifier and version.
2. Associate the buyer or dealer contact with that project.
3. Record the request event and the assigned follow-up owner.
4. Store a human-readable summary and the structured selections needed to reopen or review the project.
5. If a CRM submission fails, retry or reconcile it without creating a second opportunity for the same request.

The receiving CRM determines the exact object and property mapping. For example, HubSpot's CRM schema documentation describes custom objects, properties and associations; Salesforce's lead-conversion documentation distinguishes a lead from the account, contact and optional opportunity created during conversion. Neither model is a reason to discard the saved product specification. Agree the mapping with the team that owns the CRM before the configurator goes live.

This does not mean every site needs a complex integration on day one. A small team can begin with a reviewable project record and a reliable notification, then add CRM field mapping once the required data and owners are clear. What matters is that a salesperson can find the same configuration the buyer submitted.

Route by useful context, not an opaque “hot lead” score

Lead quality is a business decision, not a magic number. Start with observable signals that determine who should respond: product family, service area, dealer territory, quote request, rule exceptions and whether essential dimensions are present. Then define a clear owner and response path for each state.

For example, a valid pergola quote request in an active dealer territory can go to that dealer's sales queue. A garden-room project with an unsupported dimension might go to technical review first. An enquiry outside the service area should not be silently dropped; the business should define what response the buyer receives. A duplicate form submission should update or reference the existing project, not create competing sales tasks.

If you later use lead scoring, make the underlying signals visible to the salesperson. “Priority: review mounting conditions” is more actionable than “Score: 82.”

Eight tests to run before launch

Use one real product family from your catalogue and record the result of each test. A polished demo is not proof that the handoff works when data is incomplete or a system is unavailable.

Ask to inspect the received project, not only the customer-facing animation. The best acceptance test follows a selection through the 3D view, rule result, commercial status, enquiry and the salesperson's next action. If an output depends on your ERP, CRM or quoting system, identify that dependency and test the actual connection before calling the handoff complete.

Questions to bring to a configurator demo

• Can you reopen the same configuration the buyer submitted, including its revision?
• What exactly happens to options and prices when a product rule changes?
• Which fields are structured data, and which are only text or an image?
• How do incomplete, invalid and manually reviewed requests reach the right person?
• What happens if a buyer submits twice or the CRM is temporarily unavailable?

These questions make a vendor comparison more useful than a feature checklist. A manufacturer considering a 3D configurator rollout should test them against its own catalogue, dealer model and sales workflow.

Where Configurix fits

Configurix connects interactive 3D product configuration, product rules, pricing, quotes and project follow-up in one configurable sales journey. The useful demonstration is not a generic gallery: it is your product family, one valid selection, one exception and the record your sales team would receive. That is how to evaluate whether the configured product can move from buyer interest to a proposal your team can act on.

If you are preparing a configurator project, book a Configurix walkthrough and bring your catalogue, a representative price rule and your current enquiry or quote form. We can map the information that needs to survive the handoff before discussing the interface around it.