June 10, 2026 · 5 min read
The hidden costs of a desktop routing workflow
The license fee is the visible cost. The expensive part is everything around it: idle engineers, stale exports, and re-work the yard finds for you. A field guide to the costs that don't show up on the PO.
Ask what cable routing costs and you'll get a license number. That number is almost irrelevant. The real costs of a desktop-bound routing workflow never appear on a purchase order — they appear in the schedule.
1. The waiting
One routing seat means routing is a queue. Engineers who could be routing are instead checking email, and every downstream deliverable — pull sheets, MCT calcs, production planning — inherits the queue's latency. On a program with thousands of cables, the queue is the schedule.
2. The exports
Routing data that leaves the tool as a spreadsheet starts aging immediately. Someone always edits a copy. Someone always emails the wrong version. The cost shows up later as reconciliation work: an engineer spending days figuring out which of four spreadsheets reflects reality, usually under deadline, usually because the yard asked.
3. The re-work after design changes
Every model revision invalidates routes. In a desktop workflow, finding the affected cables is manual archaeology — and the cables you miss become the expensive kind of problem: discovered during installation, fixed at deck-plate prices.
The rule of thumb holds in cable routing like everywhere else in engineering: a data error caught at routing time costs minutes; the same error caught in the yard costs orders of magnitude more.
4. The bus factor
When routing lives on one machine and in one person's working knowledge, that person's vacation is a program risk. Onboarding a second engineer means another license, another install, another long ramp. Knowledge that should live in the platform lives in a head instead.
Adding it up
None of these line items appear in a tooling comparison, which is why routing workflows survive long past the point where they're costing more than they ever saved. The fix isn't working harder inside the bottleneck — it's removing it: shared live data, validation at routing time, and change impact you can query instead of hunt.
That's the design brief behind Unreal Routing. If you'd rather see it than read about it, book a demo.