Time to first result
Day 4:
first working line app
6–11 months
(design → build → UAT)
4–7 months
∞
Release rhythm
Nightly builds; run them on the next shift
One big cutover
Sprints if you staff developers
None
Shop-floor adoption
Built with operators, tested each shift
Assumed; training arrives late
Heavy internal build effort
Workarounds persist
Cost of a change request
Low — overnight changes included
Steep once the scope freezes
Medium to high
Hidden in workarounds
Data integrity
Clean from day one (the work records itself)
Backfilled after go-live
Uneven unless standardised
Lives in people's heads
Fit for your 7% edge cases
First-class in the workflow logic
Out of scope
Reachable, eventually
Spreadsheet patches
Machine integration
Any machine or system — wired in hours
Heavy upfront API work
Fixed connector list
Manual re-entry
Who builds and iterates
Cupola plus your line experts
Consultants configuring for months
Your team designs and maintains
Paper and spreadsheets
Capital at risk
Paid first sprint, refunded in full if we miss
Locked licences and services
Internal headcount cost
Rising opportunity cost