Your software works. Their floor routed around it.

For technology vendors

In the sales demo, the data was clean and the workflow was linear. Sixty days after go-live at the customer’s site, the receiving clerk is typing dummy quantities to clear the dock, the planner has exported your screen back into Excel, and the executive sponsor is asking why the promised ROI has not shown up before renewal.

Most rollouts do not fail in the model or the core code. In a 2015 NeurIPS paper, Sculley and colleagues noted that a mature machine-learning system might end up at most 5% model code and at least 95% glue code; on tau-bench, the 2024 benchmark from Yao and colleagues, even frontier language-model agents pass fewer than 50% of multi-step retail and airline workflows when they must follow domain rules across turns. In the field, that 95% is where the customer’s dirty master data, local incentives and shift shortcuts quietly break your product.

Sources: Sculley and colleagues, Hidden Technical Debt in Machine Learning Systems, NeurIPS 2015; Yao and colleagues, tau-bench, 2024.

What I check first

Where I have stood

What I don’t claim

How we would start

  1. Discover on the floor. Walk the customer’s receiving dock, aisles and planning desk alongside your team; reconcile a blind sample of physical stock against the ingested feed. Out: floor-to-schema gap log and baseline discrepancy count.
  2. Tune. Translate the customer’s real physical constraints and exception rules into a tested data contract: field tolerances, join invariants, unit-of-measure rules and fallback behavior. Out: executable data contract and edge-case test fixtures for your engineering team.
  3. Orchestrate. Run your system in a safe draft stage where the operator’s play, your engine’s recommendation and the status quo sit side by side before write-back goes live. Out: signed-off cutover checklist, rollback triggers and shift playbook.
  4. Value case. Measure the operational baseline before cutover and re-measure 30 and 90 days after go-live in metrics the customer’s CFO and COO both accept. Out: before-and-after operational ledger for renewal and expansion.
  5. Let go. Train the customer’s floor leads on the exception loop and hand your deployment engineers a repeatable onboarding runbook. Out: customer sign-off and the one-page onboarding plan (PDF).

Tell me which rollout is stalling

Engagements and fees, Proof, Working terms