The tension between sales and engineering is one of the most recognizable patterns in manufacturing. It usually sounds something like this:
"How hard can it be? It is just a small color adjustment. The customer needs this and we need to send an offer today." — Sales
"Why did you promise this feature? You know it requires time-consuming customization. We are already overwhelmed. Why can't you just sell what we already have?" — Engineering
As demand for customization grows, the Engineer-to-Order (ETO) approach creates a bottleneck in engineering that turns this tension into a structural problem. Growth stalls. Sales is slowed by complex rules and long lead times. Profits are eroded by manual processes and production errors. Configure-to-Order (CTO) offers a way out.
The friction between sales and engineering is not a personality problem. It is a process problem. In an ETO environment, the gap between what sales promises and what engineering can deliver becomes a daily source of conflict:
The result is two teams with the same goal, delivering great products, working against each other.
The frustration between sales and engineering is a symptom of deeper business problems. The real cost shows up in:
Configure-To-Order (CTO) means that not everything needs to be fully custom to meet customer requirements. Customization within defined limits is still real customization. With a CTO approach, products can be configured and ordered without involving engineering, and sometimes even without sales. That is the shift that changes the relationship between the two teams.
The foundation of CTO is managing rules:
These rules need to be maintained continuously as the product evolves, and they need to be accessible to everyone. When that is in place, salespeople gain the freedom to sell without consulting engineers on every detail. Lead times for quotes that previously took weeks can drop to minutes, with zero engineering involvement.
No. Configure-to-Order is not a replacement for ETO, it is a complement to it. Product configurators and process automation should be applied to what can be reasonably standardized. The rest can remain as engineered customization.
A successful CTO implementation frees up engineering time, so engineers can focus on the customizations and product development that genuinely require their expertise. There will always be a need for engineers. The difference is that they spend their time on work that matters, not on repetitive sales support.
The starting point is understanding your current situation clearly. Before defining where you want to go, map where you are:
Every company's situation is unique, and a CTO implementation will reflect that. The transition takes time, but it starts with one clear decision: to stop relying on informal knowledge and manual processes, and to put that knowledge into a system your team can manage themselves.
Curious what that looks like for your business? Get in contact with KonfigDesign or explore how Elfsquad CPQ supports the transition from ETO to CTO.
Do you want to learn more about this topic?
Get in contact with KonfigDesign here.
*This was a special-guest blog authored by KonfigDesign CFO Per-Erik Eriksson. KonfigDesign is a Swedish provider of qualified product configuration services within PLM (Product Lifecycle Management) and partner of Elfsquad.