The configurator in action
What your team stops doing by hand, one screen at a time.
No mock-ups: these are the screens of the configurator we build on your rules, recorded on demonstration data. Four moves that used to run through emails, phone calls and one person's memory.
See the demo on your products — free call01 — The rules
“Every new option goes through engineering, then through the software vendor.”
Your team changes a rule itself, without waiting for anyone.
Two options, how they relate (one rules out the other, one requires the other), the message the salesperson will see: the rule is put together with menus, not code. The effect shows up in the configurator right away.
Your estimator's judgement becomes the rule, and they are the one who reviews it. They settle the hard cases instead of checking every quote.
02 — The scenarios
“The customer finds it too expensive, and we will never know what they would have taken.”
Three versions in one send: the customer chooses instead of saying no.
Good, better, best, built from the same configuration. The customer sees what each version adds and what it costs on top, side by side, instead of answering yes or no to a single price.
Your salespeople stop rebuilding a full quote for every “what if we took out…”. The variant follows the same rules as the original.
03 — The approvals
“Discounts get negotiated over email, and nobody knows who said yes.”
Who approves what: drawn once, applied to every quote.
A discount past the threshold, a margin under the floor, an unusual amount: each case goes to the right person, to a team, or to several people at once. The path is drawn like an org chart and reads without training.
The request goes out on its own when the salesperson crosses the line. The decision stays attached to the quote, with who made it and when.
04 — The assistant
“Our approval rules exist, but only in the director's head.”
You state the rule in one sentence. The assistant asks what is missing.
“Any discount over 15% on assembly cells must be approved by the sales director, then by the president.” The assistant spots what is still vague (here: the whole family, or a single product?) and asks, instead of guessing.
What it does not do: decide. It shows you a summary in plain sentences, you approve it, and the rule starts out inactive. It only applies once you have read it and switched it on.
Pick what you need
You take what hurts. The rest can wait.
The configurator is assembled in modules. We start with one product family and with the problem that costs you the most.
Configure
Options that do not go together no longer show up. The salesperson cannot quote what the shop cannot build.
Price
Cost, upcharges, volume tiers, discounts and taxes, every layer readable. A price you can defend in front of the customer.
Quote
A proposal in your colours, in French and English, with several scenarios in a single send.
Approve
Discounts and margins outside the limits go to the right person, without an email.
Connect
Parts and costs read from your ERP, order and bill of materials sent back. Nobody re-keys anything.
Measure
Options sold, options never chosen, discounts by salesperson: what your catalogue actually does.
The other modules come in once the first one is adopted, not before.
The limits, up front
What these screens do not promise you
This is demonstration data. The products, prices and names on screen are fictitious. With you, it is your rules we model, and that is where the real work happens.
This is not off-the-shelf software. What you see is the foundation. Your configurator is built on your rules and installed separately, on your side.
Your ERP stays in place. We connect to it to read and send back data. We do not replace it.
Bring a real rule. We build it in front of you.
A discount only the director can grant, three options that must never go together: name it during the call, and you will see it on screen.
Your rule is only used to build your example. Never shown to a third party, never cited without your written consent.