Three organizations. Three industries. Three different classes of logic failure — each one proven to exist before a single line of configuration was written. Each one a deployment disaster that did not happen.
NovaCorp Relocation Services was experiencing 3-7 day billing delays and frequent invoicing errors across a multi-system environment running MoversSuite, CrewPro, and Abby. The assumption was that the systems were configured correctly and people were not following the process. The solution under consideration was retraining and tighter manual oversight.
Nobody had looked at the logic underneath the process. Nobody had asked whether the rules the systems were configured to enforce were actually satisfiable.
They were not.
Every enterprise account over $500,000 would have deadlocked at onboarding. Compliance could not approve without KYC. KYC could not run without an activated account. Activation required Compliance approval. The system would have launched, processed its first enterprise client, and immediately stalled — with no error message, no escalation path, and no resolution procedure. The billing delays being blamed on execution were structural. Retraining would not have fixed them.
Airtrex Fleet Telematics had a Salesforce CPQ instance and a clear goal: enable sales reps and channel partners to generate accurate quotes without engineering involvement. The company had invested in the right platform. The plan was more product training and better documentation.
The actual problem was not knowledge. It was that the logic required to validate a quote — VIN-based hardware compatibility, kit constraints, inventory status — had never been formally defined. It lived in engineering heads. It could not be encoded in CPQ because it had never been structured as logic in the first place.
Training does not fix the absence of a validated rule structure.
Engineering would have remained a permanent bottleneck — not because sales lacked knowledge, but because the compatibility rules that would have enabled self-service quoting were never formally defined and therefore could never be encoded in CPQ. A Salesforce CPQ deployment without a verified data path to Epicor would have produced quotes based on compatibility data it could not actually access. Errors would have appeared at installation — after contracts were signed and hardware was shipped.
Pacific Asphalt Solutions ran a complex multi-contract operation on physical yellow forms, whiteboard scheduling, text message crew notifications, and red cards for post-job issue resolution. Billing fed manually into NetSuite. The executive mandate was clear: digitize the operation. Protect the reputation. No dropped calls, no missed deadlines.
The assumption was that the process worked and the problem was the medium. Move the yellow forms into Salesforce Field Service Lightning. Replace the whiteboards with a digital dispatch calendar. The logic would come with it.
The logic was the problem. The medium was hiding it.
The digital transformation would have replicated every paper failure in software — at the speed of automation and without the human flexibility that had been quietly compensating for the logic gaps. Yellow form ambiguities would have become system errors. Text message crew notifications would have become unauditable digital messages. Government and commercial contracts would have followed the same logic path in a system that executes rules without exception. The compliance exposure that existed on paper would have become a compliance exposure that runs automatically, on every contract, without anyone noticing until an audit.
Every organization believes its process is sound. The kernel is indifferent to that belief.
Request a Session