The moment the crates open

The room is quiet in that way only construction sites can be. Dust in the air. Two installers. One homeowner. Crates open. And everyone looks at me.

Home elevators aren’t assembled at the factory. They’re assembled in someone’s house, months after the order. As Swift Lifts put it, “It’s not until the product arrives on-site that the product is put together. It’s at that point we confirm that everything worked.”

That’s the moment a tiny quoting mistake becomes a very expensive problem. Left became right. The travel height is off by 40 mm. The door type doesn’t meet the local regulation. You don’t discover any of it in your CRM. You discover it in a client’s hallway, with a wall already cut open.

I’ve had that call. An installation team in Bangkok, a distributor on WhatsApp, and a homeowner who took time off work to be there. The quote was clean. The CAD looked fine. The site wasn’t. Everyone paid for it.

Speed is not the problem

Most leaders think they need CPQ to make their sales team quote faster and produce more proposals. I get why. Volume feels measurable. You can point to minutes saved and call it progress.

That focus is a trap. For complex hardware, the real enemy isn’t a slow quote. It’s an incorrect one. The mistake made three steps upstream that travels quietly through emails, PDFs, and spreadsheets until it explodes at installation.

Stop measuring minutes per quote. Start measuring zero on-site failures.

Swift Lifts tried selling without a configurator. It meant a big order-taking department, lots of back-and-forth, and what they called “stupid mistakes” - left becoming right, colors not matching, measurements wrong. Each one looked small on paper. Each one was massive on-site.

Yes, speed matters. You’ll get it as a side effect. But speed without correctness is like flooring a car with misaligned wheels. You won’t like where you end up.

CPQ’s real job: a correctness engine

I’ve said it for years: CPQ has never primarily been a software problem. It’s a correctness problem. The job is to guarantee that what sales promises is what engineering can design, manufacturing can build, and the installation team can assemble without surprises.

CPQ is not about automation - it’s about correctness.

Manual processes create gaps. A PDF template that doesn’t know about the new door option. A spreadsheet that only one person updates. An email thread where someone misreads a dimension. Those gaps breed errors.

CPQ closes the gaps by making logic explicit. Product rules. Price rules. Regional regulations. BoM structures. All in one place. Not hidden in someone’s head or a local file. When talking about systems that only uses symbolic logic for configuration, the difference is whether the rules are brittle or explainable. If they’re brittle, you’ve just moved the single point of failure into software.

At Swift Lifts, the turning point wasn’t a demo. It was their BoM and drawings expert - the person who rarely praises tools - saying “OK, this is powerful.” That’s when everyone realized the logic could carry the weight. That matters more than any UI trick.

If the system cannot explain itself, it will never be trusted.

Trust is built when a salesperson sees not just the answer, but why it’s the answer. Not allowed because the door hinges clash with the shaft width. Price adjusted because local regulation requires a different safety package. Logic you can read and test. That’s how adoption sticks.

How correctness wins on-site

Here are the rules I give teams who sell complex, installed products.

Rule 1: Make zero on-site failures your primary KPI. Track it like warranty claims. Every failure gets a root cause. Was the rule missing, wrong, or ignored? Swift uses CPQ to simulate price model changes and product updates before they reach the field. The goal is fewer surprises, not prettier proposals.

Rule 2: Move from tribal knowledge to visible rules. If your best expert needs to sit in on tricky quotes, you have a bottleneck, not a business. I call it the single-lane bridge. Founder-only quoting worked when you did five deals a month. It collapses at fifty. CPQ widens the bridge, so a distributor rep can quote correctly on day one.

Rule 3: Explainability beats magic. Sales doesn’t just need a valid configuration. They need to explain it to a customer and to themselves. Show the why. Show the constraint. If your system can’t surface that logic, reps won’t trust it. They’ll route around it and we’re back to spreadsheets.

Rule 4: Design for change in hours, not quarters. New options, new regulations, new markets. If adding a feature requires updating 40 PDF templates and retraining everyone, you will drift back into error land. Swift saw this before CPQ - new features existed, but no one used them because templates lagged. With Tacton, the logic changes once and propagates everywhere.

Rule 5: Test like engineering, not like sales. You test products. Test your configuration logic the same way. Build a suite of edge cases and regional variants. Run them before every release. Don’t just click around. When you find an error, write a test so it never returns. That’s how rules become assets.

Rules are not the enemy - brittle rules are.

Why the old way keeps failing

Let’s be honest about the manual path. You rely on a few people to translate a house and a set of wishes into a validated configuration. A founder or regional manager becomes the last mile of quality control. It works until they go on vacation or the market expands.

Distributors feel this too. Before CPQ, Swift’s smaller partners had exactly one person who could create a quote. Everyone else waited. The whole business was forced through a single-lane bridge. With roles and guardrails in CPQ, they put more people on the job without increasing risk.

And the cost of wrong? It’s not just labor. It’s a homeowner losing trust. It’s a claim you shouldn’t have to pay. It’s a schedule slip that cascades into three other projects. Speed won’t save you from that. Correctness will.

What actually works

I’ve implemented Tacton CPQ since the early 2000s, from demo tables to enterprise programs. The teams that win treat CPQ as a risk system first, a sales system second. They align the business around correctness, not just velocity.

Three moves you can make now:

1) Audit your last 10 on-site issues. Don’t sanitize it. Where did the error enter? What artifact let it pass? Which rule was missing? Put those cases into a test suite. Your next release should make all 10 impossible.

2) Move your expert’s brain into the system. Sit with the person who always catches mistakes. Ask them why they catch them. Codify that logic. Tacton’s constraint engine is built for this - it mirrors how experts reason, not just how parts list. When your expert says “OK, this is powerful,” you’re on track.

3) Change your metrics and rituals. Report zero on-site failures. Track quote revisions that required no manual fixes. Measure time-to-revision, not just time-to-first-quote. And hold a monthly session where sales and product review logic gaps. Governance isn’t overhead. It’s how you scale change without breaking sales.

If you want AI in the mix, great. Just remember: AI does not replace logic - it depends on it. Fluent guesses are not what you want in a staircase. Put AI on top of explicit, testable rules and make it an assistant, not a roulette wheel.

Adoption is the only metric that matters.

Systems that help reps think get used. Systems that hide logic get bypassed. You’ll know you nailed it when new distributors can create solid quotes without waking your product manager at 6 pm.

The quiet truth

I’ll acknowledge the counterpoint. Speed does win deals. Shorter cycles matter. But correctness is what protects those deals when the crates open.

The cost of a bad quote isn’t the hour it took to create. It’s the thousands you burn and the relationship you lose when it fails at installation. Correctness isn’t a feature. It’s the cheapest insurance you’ll ever buy.

Read the full customer story at cpq.se