Configurators

Guided Selling: How It Works in CPQ

Guided selling asks buyers needs-based questions and recommends the right configuration. See how it works in CPQ, with real manufacturing examples.

Kalle Brunö
15+ years implementing PLM and CPQ across manufacturing industries
Updated December 2022
32 hrs
HMF quote turnaround, down from 11 days
35
Countries HMF quotes in from one guided flow
40 → 1
Swift Lifts: workbooks replaced by one guided model
4–5 mo
Typical time to a live guided-selling flow

We design these question flows for manufacturers as part of every Tacton CPQ implementation we run. Disclosure up front: we're a Tacton reseller and implementation partner, so when we describe how a platform handles guided selling below, that's not a neutral comparison, it's what we build.

What is guided selling?

Guided selling is a sales technique where software leads a buyer through a series of needs-based questions, what the product has to do, where it will be used, what it has to connect to, and recommends the configuration and price that best fits the answers. It replaces the older model of handing someone a catalogue or price list and asking them to identify the right part number themselves.

The point isn't the questions for their own sake. It's that the questions are the interface to a rules engine: each answer removes options that would be invalid, oversized, undersized, or simply wrong for the stated need, so the buyer ends up at a configuration that can actually be built, without needing to know the product line as well as the manufacturer does.

How guided selling differs from a plain configurator

A plain configurator presents every valid option and lets the buyer pick, good, if the buyer already knows what they need. Guided selling flips the order: it asks what the buyer needs first, then presents only the configuration(s) that satisfy it. The difference matters most for buyers who aren't product experts, a first-time distributor, a new sales hire, or an end customer configuring directly.

Catalogue / price listGuided selling in CPQ
Starting pointBuyer browses parts or packagesBuyer answers questions about their need
Product knowledge requiredBuyer or seller must already know the rangeLives in the system, not in one person's head
Invalid combinationsCaught late, often after orderingFiltered out before they can be selected
Best forSimple, low-variant productsConfigurable products with real complexity

Neither approach is wrong in isolation, a simple product with five variants doesn't need guided selling. The trigger is the same one we use for CPQ generally: once a product has enough valid combinations that no single seller can reliably hold them all in memory, needs-based questioning starts paying for itself.

Needs-based questioning: how the flow is actually built

The questions themselves aren't arbitrary, each one exists because it maps to a constraint in the underlying rules engine. In our projects, three patterns show up repeatedly:

  1. Environment and use-case questions first. Where will this run, under what load, in what conditions? These questions eliminate the largest blocks of invalid options early, so the buyer isn't wading through choices that were never going to apply to them.
  2. Non-sequential answering. A well-built flow doesn't force one fixed question order, the buyer or seller can answer whatever they know first, and the system re-narrows the remaining valid set after each answer, rather than blocking progress until question three is answered in order.
  3. Recommendation over restriction. The best guided-selling flows don't just remove invalid paths, they actively recommend the best-fit valid path when several remain, for example, defaulting to the option with the shortest lead time or lowest total cost when two configurations satisfy the stated need equally well.

An illustrative example we use with prospects: a manufacturer selling configurable antennas can't reasonably expect every dealer to know which mounting, frequency band and power option suits a given installation site. A guided flow asks about the installation environment and required range first, filters out the antenna models that don't fit, and only then presents mounting and finish choices, rather than starting the buyer at a 40-row spec table.

Guided selling in Tacton CPQ

In Tacton CPQ, guided selling isn't a separate module bolted onto the configurator, the same constraint rules that keep a configuration valid also drive which questions get asked and in what order. That's why we build the guided-selling question set during the same workshop where we define the product rules, rather than as a later, separate exercise: the questions are a reflection of the rules, not a UI decision made independently of them.

This matters most for distributors and new sales hires. Our customer HMF Cranes lets dealers across many markets configure a crane against a specific vehicle through a guided flow, and generate a correct, multilingual quote, quote turnaround dropped from around 11 days to about 32 hours across the roughly 35 countries HMF quotes in. Read the full HMF story. Swift Lifts went further: distributors who previously worked from around 40 separate pricing workbooks per product line now use one guided, CAD-connected flow to configure, visualize and quote independently, without looping in the factory. Read the Swift Lifts story.

Where guided selling fits in the CPQ flow

Guided selling sits at the very front of the CPQ sequence: needs-based questions → constraint engine narrows valid options → configuration is confirmed → price calculates → quote generates. It's the entry point, not a separate stage, everything downstream (pricing, quoting, the order that eventually reaches ERP) depends on the configuration the guided flow arrives at. That's also what makes it extend naturally to channels beyond your own sales team, letting distributors and, in some product lines, end customers configure and quote on their own.

Guided selling vs. a sales configurator

The terms get used almost interchangeably, and in practice most manufacturing CPQ platforms combine both in one tool. Where people do distinguish them: "guided selling" usually refers specifically to the needs-based question flow, while "sales configurator" refers to the fuller front-end experience, including visualization and, often, pricing, that the guided flow feeds into. If you're evaluating a platform, the practical question isn't which label it uses, it's whether the questions are generated from the same rules that validate the configuration, or maintained separately and prone to drifting out of sync.

Is guided selling worth building for your product?

The same threshold we use for CPQ generally applies here: guided selling pays off once a product has enough configuration options, or enough non-expert people selling it, that nobody can reliably hold the full rule set in their head. That's especially common in manufacturing, where product complexity, not deal complexity, is usually the actual bottleneck. If your product line is simple enough that any seller already knows every valid combination, a guided flow adds process for a problem you don't have yet.

Want to see what a guided-selling flow would look like on your own product range? Book a 30-minute walkthrough and we'll show you honestly whether it's worth building yet.

Frequently asked questions

Guided selling is a sales technique where software leads a buyer through needs-based questions and recommends the best-fit product configuration and price, instead of asking them to choose from a static catalogue or price list.