Basics

From configurator to site survey: handling enquiries for stairs and balconies

How stair and balcony makers qualify configurator enquiries, route them to dealers or sales, and take them through site survey to quote. Built vs proposed.

Short answer: for stairs and balconies, a configurator does not end in a shopping basket; it ends at the site survey. Its job is to produce an enquiry that lets your sales team decide whether a visit is worth it, who should make it and which product is likely to fit. That takes every dimension, every check result, the location and who is asking. Whether a dealer, your inside sales team or a project manager takes it from there is a question about your sales channel, not about the software.

This guide is for sales directors and the people who own the enquiry process at manufacturers of stairs, railings and balconies. It covers both example configurators in this group, the spiral stair configurator and the bolt-on balcony configurator. Both are example configurators with fictional products and example values. Throughout, we keep what the demos actually do apart from what a project would add.

Bolt-on balcony configurator – preview of the example configurator
Example configurator · fictional product · example values. Loads only when you click. Open the demo page →

What is the path from configuration to order?

  1. Configure: the buyer or designer puts together the product and its dimensions.
  2. Enquire: every value, check result and contact detail reaches the manufacturer.
  3. Qualify: sales checks whether the enquiry, product and region fit.
  4. Assign: inside sales, field sales, a dealer or an installer takes over.
  5. Survey and design: measurements on site, structural design and approvals by the manufacturer and the structural engineer.
  6. Quote and order.

A 3D configurator covers the first two steps and feeds the third and fourth. It does not replace the survey, the structural design or the quote. That is why the checks in both demos are labelled as example values; the balcony demo states that they do not replace a site survey, statics or planning by the manufacturer.

Why do stair and balcony enquiries behave differently?

Spiral stairBalconies on apartment buildings
Unit of saleone stairmany balconies on one building
Typical enquirerhomeowner, dealer, installer, architecthousing provider, developer, architect
Values that decide the quotefloor-to-floor height, opening, direction, step-off sidebuilding, layout per storey, types, sizes, fit-out
Next stepsurvey or call-back, often via a dealerproject meeting, survey of the existing building, structural design
Shared internally by the buyerrarelyoften: the PDF goes to owners, boards, designers

So the two need different enquiry forms. For a stair, what matters is that the measurements are right and the enquiry reaches the right partner. For balconies, what matters is that the enquiry describes a project someone can pass around. The product side of each is covered in staircase configurators for manufacturers and balcony configurators for manufacturers.

What the example configurators actually do

FunctionSpiral stairBolt-on balcony
Summary of every valueyesyes, with the layout per storey
Check results in the enquiryyes: example guide values marked within or outsideyes: example checks
Copy enquiry textyesyes
PDFyesyes, with facade and side views
Contact detailsblank lines in the enquiry text for name, email or phone, project ZIP codename, company, email, phone, project or location, note
Send the enquirynono

Neither demo sends anything. The balcony demo tells the user that entries are not sent or stored and that the text and PDF are created only in the browser. In a project, enquiries go to your sales team by email or webhook; we deliberately leave that switched off in the demos.

What do the two enquiries look like?

The enquiry texts in the demos show the difference between a single sale and a project.

Stair: the text opens with "Spiral stair inquiry (example)", followed by every row of the summary from product line to finish. Below that come the example guide values, each marked within or outside. The closing line asks the manufacturer to confirm the opening, landing and rotation and to send a quote, followed by blank lines for name, email or phone and the project ZIP code. For inside sales, that means seeing at a glance whether the stair fits the opening, and knowing in which region a visit would take place.

Balconies: the text is written as an email to the manufacturer, with the subject "Balcony enquiry (example configuration)". It describes the facade, the layout per storey, the fit-out and the checks, and ends by asking for a quotation or for contact about a site survey, statics and questions. The PDF adds the facade and a side view with the shadow. For project sales, that is a preliminary design to discuss with the enquirer, not an order.

Both texts are written for people, not machines. If enquiries should land in a CRM, the same values are also needed as structured data; more on that below.

What makes an enquiry qualified?

  • The product: every chosen value, exactly as shown in the configurator and in the same order as the summary. In both demos, the text and the PDF carry the same rows as the summary.
  • The checks: which values were inside your limits and which were not. An enquiry with a red fit check is not a bad lead; it needs a different next step.
  • The context: location, role (private buyer, dealer, designer, housing provider) and timing. Both demos leave room for the location, and the balcony demo also asks for the company; role and timing would be project additions.

More required fields do not automatically mean better enquiries. For a private stair buyer, the location may be enough; for a balcony project, the company matters more than a phone number.

What a project may add

None of the following is built into either demo. We assess each per project, based on how your sales team works today.

Routing to dealers and installers

If you sell through dealers: the stair demo's enquiry text already has a line for the project's ZIP code, which could drive routing by territory. Whether the enquiry then goes to the dealer, to you or to both, and whether the dealer gets a copy with their own terms, is your decision. Technically it is a table of territories and recipients; organisationally it is about how you protect dealer territories.

Handing enquiries to a CRM

A webhook can pass the enquiry to a CRM or ticketing system as structured data rather than as email text. That makes sense if your sales team already works there. Direct ERP integration is not something we offer as standard.

Saved configurations and attachments for balcony projects

For balcony projects it may help to save a configuration as a link an architect can reopen later, or to attach facade drawings. Neither is part of the demo; both are assessed per project.

A shop instead of an enquiry

For kits in fixed sizes, a basket can work. For made-to-measure stairs and balcony projects it usually does not. Quotation PDFs and CPQ are not part of our standard offer.

How to tell whether it is working

Count outcomes, not only enquiries: how many lead to a survey or a project meeting, how often you still have to call back, which options people choose. For the last one, a configurator can count control events. The balcony demo is set up so that only the features used are visible, never what people type. Which events you need is agreed per project; we do not promise performance figures.

Next step

Before we quote a stair or balcony configurator, we look at your current enquiry form and the path from first contact to survey. The build itself is covered in building a 3D configurator for stairs and balconies; how we work overall is on custom 3D configurator development.

Sources

  1. Demo features: library pages and the demos (read 14 November 2026): spiral stair, bolt-on balcony
  2. Project scope (enquiries by email or webhook; not standard: quotation PDFs, CPQ, ERP): the "Possible in your project" section of the same pages (read 14 November 2026)

Read next