Your tier: Not Ready Yet. Your tier: Partially Ready. Your tier: Ready to Build.

A NOTE FROM THE FOUNDER

Most consultants would pitch you an engagement right now. I am going to tell you that pitching you would be the wrong move. A full AI engagement from your current readiness profile has a high probability of producing a failed pilot, and a failed pilot sets the entire organisation back for years.

What I would actually recommend: a gap-closure scoping engagement. Short, written deliverable, no production code. After that engagement most organisations return within 60-90 days at a materially higher tier, and the actual AI work then has a clear runway. I would rather build the right thing in 6 months than the wrong thing now.

Partially Ready is the most common tier we see — and the trickiest to scope correctly. The two failure modes are over-correction (six months of cleanup before any AI work begins, losing momentum) and under-correction (jumping into the build and hitting the same gaps mid-engagement, eroding trust).

The dual-track approach we run is calibrated for exactly this tier: scope a focused POC against a clean slice of the use case, while a parallel workstream closes the gaps that would block production deployment. It is a 6-8 week engagement, not a 6-month one, and it produces both a working prototype and a remediation plan you can take to the rest of the leadership team.

Most Ready-to-Build organisations come to us already pre-decided on the technical approach. Often the pre-decision is right; sometimes a 45-minute conversation reveals a trade-off that materially changes the architecture before any commitment is made. The deep-dive call is the cheapest way to test those trade-offs.

I personally run these technical deep-dives for engagements above a certain threshold. The point of the call is not pitch — it is to figure out whether the architecture you are about to commit to is the architecture that survives 18 months of production use. Sometimes the answer is yes; sometimes it is yes-with-this-modification; occasionally it is ‘this approach will be expensive to maintain — here is why.’