Do You Need a Configurator?
In another article I work through the full reasoning of when and whether setting up a configurator actually pays off. Too long to read right now? This compact question catalogue cuts straight to the point. Answer yes to most questions — a configurator is likely worth considering. Answer no to most — a different approach or further process standardisation may be the better first step.
Competitive
Advantage
Where a configurator changes the buyer experience and your position in the deal.
Efficiency &
Automation
Time, errors and repetitive work that a configurator can quietly absorb.
Scalability &
Knowledge
Growing without growing the number of people who hold the rules in their heads.
Maintenance &
Change
How fast product changes propagate through the rest of the business.
Volume & Process
Stability
Whether the process is ready to be mapped, and whether the volume justifies the build.
Worth It?
Sure you're on the right site?
Hard to imagine that none of these points apply to a company with a wide range of products.
Could be worth it
Even a single point could make a configurator worthwhile. Get help to evaluate the potential benefits with experts.
You need a configurator
The question remains: which and how many? There is not that "one" configurator, but rather the right one for each use case.
You need a configuration orchestra
Just a single tool won't do it. Bring in experts to avoid confusion and ensure efficiency by orchestrating your configurators.