How we run a project

We start every implementation with a CPQ Analysis Workshop. Five online sessions, 3-4 hours each, over 1-2 weeks. The goal is to figure out what goes into the first release and what gets saved for later. The workshop shapes the entire project.

After the workshop, you get a fixed price and a clear project plan.

From there, we run projects online, starting with short, focused training sessions. As the configuration progresses, we shift into a coaching role — because you're the one who understands your products. Our job is to make sure the product logic is described correctly from the start, and then help you take ownership of it.

Our goal is go-live within 5 months.

What we set up

A typical implementation covers:

Configuration logic — your product rules, dependencies, and valid combinations. We build it with you, not for you — so your team can maintain it after go-live.

Pricing — from simple price lists to complex models with discounts, margins, and regional variations. Sometimes connected to your ERP so the CPQ always reflects current prices.

Quote documents — multilingual, branded documents generated from the configurator. Sometimes integrated with your PIM to pull in the right texts, images, and illustrations.

Integrations — connecting CPQ to ERP, CRM, PIM, CAD, and other systems. We set up the data flows so the right information moves in the right direction.

Visualization and CAD — if relevant, real-time 3D visualization and drawing generation as part of the configuration process. We work with partners like Dynamaker for this.

What makes our approach different

Fixed price after the workshop. You know exactly what the project costs before you commit. No open-ended time-and-material engagements that run over budget.

We coach, not just build. We believe the people who understand the product should be the ones describing the sales logic. We train your team and guide them — so you're not dependent on us after go-live.

Small, experienced team. Our consultants have 10-25 years of CPQ experience, most of it at Tacton. You work directly with senior people, not juniors learning on your project.

Scope discipline. We know what to leave out of the first release. That's often more important than what goes in. A CPQ that's live with 80% of the scope beats one that's stuck at 100% in a never-ending project.