The ETO Challenge: Every Order Custom, Every Cycle Costly
Engineer-to-order manufacturers build products to customer specification — overhead cranes, screw conveyors, process vessels, structural steel systems, custom material handling equipment. The defining characteristic of ETO is that the product doesn't exist until the order is placed. There is no finished goods inventory, no standard configuration that ships off the shelf. Engineering is required for every job.
This creates a cost structure fundamentally different from high-volume manufacturers. In high-volume production, engineering costs are amortised across thousands of identical units. In ETO, every order absorbs the full engineering effort. For a business winning 200 orders a year, that means 200 separate quoting cycles, 200 drawing packages, 200 BOM generations. The engineering team is the production line.
The temptation is to conclude that ETO is impossible to automate — that every job is too unique, too dependent on engineering judgement, too variable to systematise. This conclusion is wrong, but it's wrong in a specific way. Not all of the work in an ETO cycle is genuinely custom. Most of it follows patterns that have been repeated hundreds of times. The custom part is the specification. The execution of that specification into drawings and documentation is, for a large proportion of orders, highly repetitive.
Where the Time Actually Goes in an ETO Cycle
When you map the time spent across a typical ETO order cycle — from initial enquiry to drawing issue — the breakdown usually looks something like this:
- Quoting and preliminary sizing: 2–5 days. An engineer interprets the specification, sizes the product, checks feasibility, and produces a cost estimate. Often done from memory and experience, with reference to past jobs.
- Engineering review and design confirmation: 1–3 days. Once the order is placed, engineering reviews the quote assumptions, confirms the design approach, and prepares to issue drawings.
- Drawing production: 3–10 days. The bulk of the engineering time. General arrangement drawings, detail drawings, assembly drawings — produced manually in CAD, one at a time.
- BOM generation: 1–2 days. Parts lists compiled from drawings, cross-referenced against standard components, formatted for purchasing or ERP.
- Documentation: 1–2 days. Calculation reports, compliance documentation, customer-facing specifications.
Of engineering time in a typical ETO business is spent on work that follows a pattern — not genuinely novel design. The variation between jobs is real, but the process of executing that variation into drawings, BOMs, and documentation is largely repetitive.
The insight that makes ETO automation possible is this: the novelty in most ETO jobs is concentrated in the specification and in certain design decisions. The execution — converting a confirmed specification into drawings and documents that follow your established standards — is mostly the same work done differently for each job. That's the work automation targets.
The Quoting Bottleneck: Why Sales and Engineering Are Always in Conflict
In most ETO businesses, quoting creates a structural conflict between sales and engineering. Sales needs a fast, accurate price to win the job. Engineering needs enough detail to produce an accurate price. The customer wants a quote before committing to providing that detail. And engineering has live production work competing for the same time.
The result is a compromise that satisfies nobody: sales quotes conservatively and loses margin, or quotes aggressively and loses it on delivery. Engineering gets interrupted for quotes that don't convert. Customers wait days for responses that should take hours. The larger the order pipeline, the worse this bottleneck becomes.
A product configurator addresses this by capturing the rules an engineer applies when quoting. The decision logic — how capacity affects structural sizing, which components are required for which configurations, how labour estimates scale with product dimensions — gets encoded once and then applied automatically every time. Sales enters the customer's requirements. The configurator applies the engineering rules. A quote, a specification, and a preliminary BOM are produced in minutes.
The engineer's role shifts from producing quotes to maintaining the rules that govern them. This is a better use of engineering knowledge — and it scales. A single engineer can effectively govern the quoting accuracy of an entire sales team without reviewing every enquiry individually.
Drawing Production: The Repeatable Work Hidden Inside Custom Orders
Drawing production is where ETO businesses spend the most engineering time, and where the case for automation is most straightforward — once you can see past the apparent uniqueness of each job. Variant drawing automation is specifically designed for this ETO pattern: parameterising your standard product families so that each new order generates a complete drawing set automatically from its specification.
Consider two orders for the same product type: a screw conveyor for 2 tonnes per hour and one for 5 tonnes per hour. The specifications are different. The drawings will show different dimensions, different shaft diameters, different support structures. But the drawing structure is identical. The same views. The same annotation conventions. The same title block. The same BOM format. The same general arrangement layout. The same detail drawing types.
What changes between the two jobs is the parameters — not the process of producing the drawings. And if the parameters change but the process stays the same, the process can be automated. Feed the parameters in; get the drawing set out.
- Parametric master models — SolidWorks, Inventor, or AutoCAD models where dimensions and features are driven by external parameters rather than fixed values. Change the parameters and the geometry updates automatically.
- Drawing templates — Drawing files where views, annotations, title blocks, and BOMs are pre-configured and update automatically when the model changes.
- Rule-based automation — Logic that determines which views to include, which notes to add, which components appear in the BOM, based on the product configuration.
Drawing set turnaround achieved by ETO manufacturers who have automated variant drawing production for their standard product families — down from 3–5 days of manual engineer time per order.
The critical distinction is between variant work — orders that fall within the range your automation has been built to handle — and genuinely novel work — first-time product types, unusual specifications, or edge cases outside the automation scope. The goal is not to automate everything. It's to automate the variant work so that engineers have capacity for the novel work.
Automation That Works for ETO: What to Automate and What Not To
Not all parts of the ETO cycle are good candidates for automation, and attempting to automate the wrong parts creates more friction than it removes. Understanding the boundary is as important as understanding the opportunity.
High-value automation targets in ETO:
- Variant quoting. Sizing calculations, component selection, and cost estimation for orders that fall within a defined product family — the work that currently requires engineer involvement for every enquiry.
- Variant drawing production. Generating drawing packages from confirmed order parameters — the parametric execution work that follows the same pattern for every job of a given type.
- BOM generation. Extracting structured bills of material from confirmed models, formatted for purchasing, fabrication, and ERP.
- Calculation reports. Structural or mechanical calculation outputs that follow a standard format and are driven by the order parameters — produced automatically rather than re-run and reformatted for each job.
What automation should not attempt in ETO:
- First-article design for new product types. When you're designing a product configuration that hasn't been built before, that's genuine engineering work. Automation can't substitute for the judgement involved.
- Exceptions before the rules are stable. If your product configuration rules are still evolving — new variants being added regularly, edge cases changing the logic — automating too early locks in rules that will need constant rework.
- Any workflow that isn't documented. Automation encodes a process. If the process only exists in the heads of experienced engineers and hasn't been written down, you don't yet have a process to automate. Documentation comes first.
How Configurators and Drawing Automation Work Together
The highest-value ETO automation pattern combines a product configurator at the front end with automated drawing production at the back end. The two systems work as a connected pipeline rather than separate tools.
The sequence works like this:
- Sales enters customer requirements into the configurator — capacity, dimensions, material, environment, options. The configurator applies engineering rules to validate the configuration and produce a quote with a confirmed specification.
- The confirmed specification becomes the automation input. Once an order is placed, the same specification data that produced the quote drives the drawing automation. No re-entry of data. No translation between systems.
- Drawing automation generates the drawing package. The parametric model updates from the specification. Views, annotations, and title blocks update from the model. The BOM is extracted automatically. The result is a complete drawing set, ready for engineering review.
- Engineering reviews, not produces. The engineer's job at this stage shifts from drawing production to drawing review and approval. They check the output against the specification, handle any edge cases the automation flagged, and approve for fabrication.
This pipeline doesn't require the configurator and the drawing automation to be built simultaneously. Most successful ETO automation projects start with drawing automation, build confidence in the output, and then layer the configurator on top once the drawing rules are stable.
A Real-World ETO Automation Pattern
A manufacturer of custom material handling equipment was producing drawing packages manually for each order. Each package consisted of a general arrangement drawing, multiple detail drawings, a BOM, and a calculation report. The process took 3–5 engineering days per order. With 150 orders per year in one product family, this represented a significant portion of total engineering capacity.
The product family — screw conveyors for bulk material handling — had genuine variation across orders: different lengths, diameters, throughput capacities, inlet and outlet configurations, drive arrangements. But the drawing structure was consistent. The same views appeared on every general arrangement. The same calculation approach applied to every sizing exercise. The variation was entirely in the parameters.
An automated system was built around a web-based configurator that captured the key specification inputs — material, capacity, length, diameter, inlet/outlet positions — and applied the engineering rules to validate the configuration and produce a preliminary sizing. On order confirmation, the same inputs drove a parametric SolidWorks model and an automated drawing generation process.
From confirmed order inputs to complete drawing package — 14 configuration inputs, 38 engineering rules applied, 40 drawing sheets generated. A process that previously required 3–5 engineering days, now completed in under five minutes.
Engineering's role in the standard order cycle shifted from drawing production to drawing review. The time freed was redirected to non-standard orders, first-article designs, and engineering improvements that had been deferred for years due to capacity constraints. The same team handled significantly more order volume without additional headcount.
Where to Start: Finding the Repeatable Core in Your Custom Work
The starting point for ETO automation is identifying the product family with the most volume, the most established drawing conventions, and the clearest engineering rules — the family where engineers are doing the same drawing exercise repeatedly with different numbers.
A practical path to identifying that starting point and building from it:
- Count your order types, not your orders. Of all the orders you received last year, how many fell into recognisable product families where the design approach was the same even if the dimensions were different? That number — not your total order count — is your addressable automation volume.
- Document the rules before building the system. Sit down with your most experienced engineer and document every decision they make when sizing and drawing a standard order in that family. Which dimensions are driven by which inputs? Which components are selected under which conditions? This document is the automation specification — and it's the part most projects rush past.
- Start with drawing automation before the configurator. Building drawing automation first is lower risk and produces faster results. It validates the parametric model structure and the engineering rules before you layer a customer-facing configurator on top.
- Measure the before state explicitly. Before starting automation work, log how long a standard order in your target family actually takes — from confirmed specification to issued drawings. This number becomes your baseline for measuring the ROI of the automation you build.
- Treat the first product family as a proof of concept. The rules, templates, and tools you build for the first family establish a pattern that makes the second family faster to automate. ETO automation compounds — each family built makes the next one easier.
If you're not sure which product family represents the best starting point, or if you want to understand realistically what automation would look like in your specific ETO environment before committing to a build, the right first step is a workflow assessment. Our free Engineering Automation Audit reviews your current order cycle, identifies the highest-value automation opportunities, and gives you a clear picture of what a realistic implementation looks like — including timeline, scope, and expected return — before any development begins.