Four Rungs, and the Courage to Stop

The facts behind The Demo Is a Question, Not an Answer: how we actually ran AI pilots at Avidity, and why so few of them ever became the stalled kind.

What happened

Every ask ran a gauntlet before it earned a dollar of build.

The first gate was buy versus build. We only built what we could not or would not buy, for reasons that deserve their own piece someday. The second gate was a person. Our AI Product Partner was the first line who took in a request and asked whether a no-code tool already solved it. Most of the time something did. Only when the honest answer was no did the ask move to engineering.

Inside engineering we had built an AI Hub, shared infrastructure that let us prototype features and workflows quickly without standing up plumbing every time. Against it ran a four-rung ladder: Sub24 to App to Program to Platform.

• A Sub24 was a clickable prototype an engineer could turn around in under twenty-four hours of a narrowly scoped request. Its only job was to let the business partner see what they had actually asked for, because nine times out of ten they did not yet have the words for what they needed and reached for a solution instead of describing the pain. It pulled the real problem into the open, fast and cheap, before anyone committed to building anything.
• An App was that one validated workflow built for real: a single self-contained tool that did exactly the thing and nothing more, deployed through the AI Hub so the partner could pilot it and give feedback without us standing up new infrastructure.
• A Program was what an App became once it drew enough demand to justify more. That meant executive sponsorship, a resourcing conversation, and a commitment larger than a single self-contained workflow.
• A Platform was the rare survivor that earned a place as durable, shared infrastructure meant to last. Most asks never reached it. The AI Hub the other rungs ran on was itself a Platform.

What it produced

Because investment followed traction rather than hope, we could pilot, take feedback, refine the request, and often decide to stop. A good number of asks were sunset once the project team concluded they were not solving the problem we had targeted, and that was the system working, not failing.

The clearest example came from Legal, who asked for a way to assess contract clauses across many contracts. We had a full platform plan on paper. We prototyped and piloted it the way described above, and we stopped at the Program layer, because we had solved the pain earlier than we expected to. The platform never needed to be built. The money and attention it would have consumed stayed free for the next real problem.

The conditions that made it work

• A person at intake, not a queue. The AI Product Partner reframed the ask and routed it, and the no-code gate meant engineering only ever saw problems that genuinely needed building.
• The demo was a question, not a pitch. A Sub24 existed to surface the true requirement in a day, not to impress a room into funding a roadmap.
• Investment was gated by traction, and stopping was allowed. Nothing climbed a rung it had not earned, and an ask that solved its problem early was celebrated for ending, not pushed to justify its plan.
• It was human-first, not only technical. Scaling resource commitments was paired with enabling and training the people who would use each tool, so traction meant real adoption rather than a login count.

How this was measured. The ladder, the gates, and the Legal example are the operator’s firsthand account. The “nine times out of ten” is a heuristic from experience, not an audited figure, and no independent success rate was calculated. A directional account from a single organization, offered as one worked example of the argument, not as proof of a number.

Cheers,
-Titus