Beating an Incumbent and Two $1B+ Competitors.
A retailer RFP against entrenched and billion-dollar alternatives.
The system could explain its own reasoning. That was the difference.
Overview
A large retailer with major logo recognition was evaluating trade-in partners for a new country. The field included the entrenched incumbent, already plugged in operationally, and two of the top global trade-in providers, both doing over $1B in revenue with polished, stable solutions. Incumbents in this space are traditionally very hard to dislodge. The program was the underdog by every conventional measure.
The solution had been built through an 18-month carrier program (Case Study 02) with shifting requirements and manual workarounds. It was functional, not polished. But it was a system that could explain itself: every exception documented with rationale, every handoff owned with a written definition of done, every decision traceable. Equally important was how the team was organized: decision authority sat with the person closest to the problem, not at a single bottleneck.
The prospect ran a standard reference call. The first client was honest about what had been hard, and equally specific about how the system absorbed it. They chose the program over all three alternatives. Not because the solution was more mature. Because the system, including how the team operated within it, gave them confidence that the right decisions would be made at every step.
The Full Story
The Situation
The Tier 2 carrier program (Case Study 02) had stabilized. The system worked. The handoffs held. But what had been built was more than a functioning flow. It was a functioning flow with a readable explanation of itself. Every manual exception was documented with the rationale and criteria for automating it. Every decision that deviated from the original plan had a justification that could be reviewed, challenged, and reversed. Every handoff had an owner with a written definition of done.
None of this had been built retroactively. It was operational discipline embedded in motion, recorded as decisions were made, not summarized after the fact. That distinction matters, because what came next tested whether the system's memory was real or cosmetic.
What Was Actually Broken
The standard failure mode after a chaotic build stabilizes is the memory problem. The team moves on. The lessons, what failed, why, how it was fixed, what to do differently, live in the heads of the people who were there. When those people leave, the lessons go with them. The next program inherits the same surface structure with none of the institutional knowledge that made the first one hold.
There's a meaningful difference between a program that works and a program that knows why it works. Most programs clear the first bar. Very few clear the second. And the second is the one that determines whether the system can survive a reference call, a competitive evaluation, or a handoff to a new team.
A system that documents its reasoning but centralizes every call is still fragile. A system that distributes authority and records why is the one that wins.
Diagnosis and Approach
The design choice was made during the build, not after it. At every stage where the team accepted a manual exception, it documented why, and what the criteria for automating it would be. The system wasn't just doing things. It was recording why it was doing them.
Equally important was how the team was organized within the system. Decision authority was decentralized: the right person was entrusted with making the relevant call at each step, without bottlenecking through a single point of control. That's not a loose management style. It's a deliberate structural choice. A system that can explain itself and a team that's organized to act on what it knows are two sides of the same principle: decentralize decisions, centralize the reasoning behind them.
Results
The opportunity came from the carrier program's unexpected byproduct. A large retailer, one of the most recognized logos in its category, was evaluating trade-in partners for expansion into a new country. The evaluation was formal: RFP, technical review, reference calls. The field was formidable. The entrenched incumbent was already plugged in operationally, and incumbents in this space are traditionally extremely hard to dislodge. Two of the largest global trade-in providers were also in the running, both doing over $1B in revenue, both with polished, battle-tested solutions. On paper, the program was the underdog by every conventional measure.
The prospect ran a standard reference call. The first client was honest about what had been hard: the shifting requirements, the extended timeline, the manual workarounds. But they were equally specific about how the system had absorbed it, and clear about what they'd seen throughout.
They chose the program. Not because the solution was more mature. Because the system, including how the team was organized within it, gave them confidence that the right person would be entrusted with the right decision at every step. The win wasn't just revenue. It was proof that the methodology was exportable, and that a system built under messy conditions in one market could be trusted to hold in another, even against far larger and more established competitors.
The Pattern
The test for structural memory is simple: if the person who built this left tomorrow, would the next person know what to do, and more importantly, why? If the answer is no, the program is only as good as its current operator. That's a consultant model. A system model encodes the reasoning, not just the steps. And when that system has to compete for a new client against entrenched incumbents and billion-dollar alternatives, the reasoning is what survives the reference call. The steps are table stakes. The 'why' is the differentiator.
Most companies accept returns.
Very few optimize the recovery.
TICE is the system we wished had existed. Ready to move forward?