Key Takeaway: Most organizations that fail at AI transformation had capable engineers and enough budget. What they didn't have was a named person with authority to restructure something concrete. This framework is a pre-qualification tool — the conversation before the contract is cheaper than the same conversation six months in when the project has stalled.
Most organizations that fail at AI transformation had the engineers, the budget, and the intent. What they didn't have was the organizational wiring to act on what the technology surfaces. A capable VP who couldn't sign off on workflow changes without six people in the room. Data that existed but required eighteen approvals to access. A leadership team excited about AI in the abstract, unwilling to restructure anything concrete.
This framework exists to find that out before the work starts. Pre-qualify hard. The conversation before the contract is cheaper than the same conversation six months in, when the project is stalled and everyone is telling different stories about why.
Five dimensions
Executive Sponsorship (highest weight). One named person with authority, budget, and willingness to spend political capital. Not a committee. Not "the leadership team is excited." The diagnostic: "Who signs off on workflow changes affecting more than one department?" If the answer involves more than one name, that's a problem. If the answer is "we'll figure that out as we go," walk away. I've seen three engagements die because the sponsor had authority to start but not to finish — innovation budget requiring quarterly re-approval, VP promoted to a different division mid-project, CEO who surfaced "concerns" six weeks into implementation because the CTO hadn't socialized upward.
Data Access (not data quality). Quality can be improved during the engagement. Access is a governance and political problem no outside team solves. The test: can the team get read access to production data within the first two weeks? Not sanitized samples. Not last quarter's export. Production data with schemas and context. I give this a two-week hard deadline. If you can't get data access in 14 days, the organizational antibodies are stronger than the executive sponsor's authority.
Willingness to Change Workflows — where most companies fail. They want AI to make current processes faster, not different. The value is structural — replacing judgment loops with automated ones, collapsing sequential processes into parallel ones. The diagnostic: "Are you willing to eliminate roles based on findings?" Companies that will actually change point to specifics. Companies that won't give you strategy-deck language about "augmenting our team." When I hear "augment," I mentally lower the estimate.
Technical Team Quality (not size). Three excellent engineers implement AI faster than thirty mediocre ones. I assess by talking to the technical team directly, not their managers: what's your deployment pipeline? How do you monitor model performance? What was the last production incident and how did you handle it? Confident, specific answers mean the team is real. Buzzword soup means the team is a slide deck.
Timeline Expectations. Realistic: 90 days to working POC, another 90 to production, another 90 to organizational adoption. Companies insisting on "quick wins in month one" will optimize for demos over systems. A demo that impresses the board but can't handle production data is worse than no demo — it creates false confidence and makes the real work harder to fund.
This framework loses engagements. Good. The organizations that clear it ship to production and become references. The ones that don't would have become the projects you warn your team about afterward. Technical readiness has engineering solutions. Organizational readiness has only one: a leader who decides the change is happening and makes it stick. No framework can give an organization that. But it can tell you whether they already have it.