“The most expensive mistake in enterprise AI is not choosing the wrong model, it is misunderstanding which game you are playing.”
What is our AI strategy?
The pressure to adopt Artificial Intelligence is immense, and the penalties for inaction feel existential. Yet for many executives, stepping into the AI landscape feels less like strategic planning and more like navigating a bazaar where every stall-holder shouts “AI!” while selling fundamentally different goods.
The confusion is not a failure of executive intelligence. It is a failure of the technology industry’s language. When a startup founder says “we use AI” and OpenAI’s Sam Altman says the same thing, they are describing activities separated by roughly five orders of magnitude in cost, complexity, and organisational commitment. The Stanford HAI 2025 AI Index Report documents that 78% of organisations now report using AI in at least one business function, up from 55% a single year earlier. That is the kind of adoption curve that typically takes enterprise technology half a decade. But adoption of what, exactly?
What follows is that map. Three tiers, three fundamentally different games, three distinct cost structures, talent profiles, and risk envelopes. Getting the tier right is not a technical decision. It is the single most consequential strategic decision an organisation makes about AI.
Tier One: Buying the Power Drill
“”This needs to be stated with uncomfortable clarity: using AI to write code is not developing AI. It is giving your software engineers a more sophisticated power drill. The drill does not design the house. It does not decide where the walls go. It drives screws faster.””
The first tier is the simplest, and it is where most organisations should start. Using AI means equipping your existing team with commercially available tools: Claude Code for software developers, ChatGPT Enterprise for knowledge workers. You are purchasing a licence. The AI sits alongside your people, suggesting, accelerating, and automating the mechanical parts of creative and technical work.
This needs to be stated with uncomfortable clarity: using AI to write code is not developing AI. It is giving your software engineers a more sophisticated power drill. The drill does not design the house. It does not decide where the walls go. It drives screws faster. The honest framing: AI coding assistants reduce friction on routine work and let experienced developers spend more time on design decisions. They do not transform a junior team into a senior one.
The organisational implications at Tier One are minimal. You are not restructuring. You are not hiring new roles. Your existing developers, writers, and analysts learn a new interface, and your IT leadership handles procurement, enterprise licensing, and governance. The governance piece matters more than most executives realise, because a developer pasting proprietary code into a public AI tool is a data leak, not a productivity hack. Enterprise-grade licences with private instances exist precisely for this reason.
The investment is measured in subscription fees and onboarding time. The ROI is measured in hours reclaimed per week. The risk is low. If Tier One is all your organisation needs, acknowledge it, budget accordingly, and resist the temptation to narrate it as something grander. The power drill is a good tool. Calling it an engine factory does not make it one.
Tier Two: Renting the Brain
“You are not building a brain. You are renting one.”
The second tier is where most product-building organisations find their strategic sweet spot, and it is also where the language starts getting dangerously imprecise. Integrating AI means your engineering team builds features powered by external models, calling OpenAI’s GPT, Google’s Gemini, Anthropic’s Claude, or similar services through an API. You send your data across a secure bridge, the model processes it, and you get back a summary, a classification, a recommendation, or a drafted response.
“You have a dependency on an external provider… But the risk is categorically different from the risk of building your own model. You are not betting on whether the science works. Someone else has already spent billions proving that it does”
The technical work at Tier Two is genuine software engineering, but it is a specific kind of engineering. Your team designs the product experience: when does the application call the model, what context does it provide, how does it handle the response, and what happens when the external service is slow or unavailable? This is the domain of Retrieval-Augmented Generation (RAG), a pattern where your system fetches relevant proprietary documents, feeds them to the model alongside the user’s query, and receives a grounded, context-aware answer.
The team for this tier looks different from Tier One but does not require exotic hires. You need product managers who can define when AI adds value and when it is decorative. You need integration engineers who build reliable connections between your systems and external models. You need someone, whether you call them a prompt engineer or a senior developer with strong language skills, who crafts the instructions and context the model receives. And you need security leads who ensure proprietary data crossing the API bridge is stripped of anything that should not leave your perimeter.
Tier Three: Forging the Engine
Here is where timelines stretch and budgets detonate. Developing AI means training a proprietary model from raw data. You are no longer writing rules for a computer to follow. You are constructing the mathematical architecture for a machine to learn, to extract patterns from millions or billions of data points, to generalise those patterns into something that resembles understanding. This is not software engineering. This is research.
“Developing AI means training a proprietary model from raw data. You are no longer writing rules for a computer to follow. You are constructing the mathematical architecture for a machine to learn… This is not software engineering. This is research.”
The financial reality is stark. Anthropic’s CEO Dario Amodei has stated publicly that frontier AI model training runs from roughly $100 million at the lower end to over a billion dollars for models currently in development, with projections reaching $10 to $100 billion within the next few years. Even smaller, domain-specific models carry significant costs: training a seven-billion-parameter model runs $50,000 to $200,000 in compute alone, and a twenty-billion-parameter model can reach $2 million before a single line of production code is written.
The assembly line that makes Tier Three work requires three distinct, highly specialised roles that cannot substitute for one another. Misunderstanding this is where most organisations stumble.
The Data Engineer is the miner and logistics architect. Before any model can learn, data must be extracted from scattered legacy databases, cleaned of errors and duplicates, formatted consistently, and transported into a centralised warehouse. Raw enterprise data is almost never ready for machine learning. It is messy, incomplete, contradictory, and riddled with encoding artifacts from decades of system migrations. Research consistently finds that 70% to 85% of AI project failures trace to data quality issues, not algorithmic shortcomings. MIT research shows 82% of machine learning projects stall specifically because the data is not ready. The old computer science aphorism holds with brutal precision: feed bad data into a sophisticated model and you get a confidently wrong sophisticated model.
The Data Scientist is the blueprint architect. Once clean data arrives in the warehouse, someone must determine what is actually possible to predict, classify, or automate. Data Scientists design controlled experiments, test mathematical algorithms, and build the theoretical framework for how the model should learn. They are statisticians, researchers, and mathematicians, and their job is to ensure the model is solving the right problem with the right method, not simply memorising noise in the training set.
The Machine Learning Engineer is the factory manager. A Data Scientist’s prototype might perform beautifully on a laptop with a curated test dataset. The ML Engineer takes that prototype and turns it into production-grade software: managing the training runs on expensive cloud GPU clusters, optimising the model for speed and memory efficiency, deploying it into infrastructure that serves thousands of concurrent requests without crashing, and building the monitoring systems that detect when the model’s performance degrades over time. Research shows 91% of ML models experience temporal degradation, meaning the work does not end at deployment, it shifts to continuous retraining and validation.
The honest question every executive must ask before entering Tier Three is not “Can we do this?” but “Must we do this?” You only build a proprietary model when the AI is your product and you possess genuinely unique data that no commercially available model can replicate. If your competitive advantage lies in how you apply intelligence rather than in the intelligence itself, Tier Two is almost certainly the correct answer, and you will reach the market years faster.
The Misallocation Trap
The misallocation trap has a human cost, too. When Tier Two work is narrated as Tier Three, engineers are hired for roles that do not match the actual work. Data Scientists are brought in and then asked to build API integrations. ML Engineers are recruited and then tasked with prompt engineering. The frustration is predictable, the turnover expensive, and the lost time irrecoverable. In a talent market where 72% of employers cannot find the AI skills they need and positions take half a year to fill, misallocating the people you do manage to hire is an extraordinarily expensive error.
The practical framework is straightforward once the categories are clear. Start by asking three questions.
First: are we trying to make our existing people faster at their existing work? That is Tier One, and the answer is almost always yes for every organisation regardless of size or sector.
Second: are we building a product feature that requires intelligence we do not need to own? That is Tier Two, and the answer is yes for the vast majority of software companies.
Third: is our core business value derived from a model that cannot exist without our unique data? Only if the answer to this third question is an unambiguous yes does Tier Three become defensible.
The cost ratios between tiers are not linear. They are exponential. Tier One is measured in thousands of dollars per year in licensing fees. Tier Two is measured in tens of thousands to low hundreds of thousands in engineering and API costs. Tier Three starts in the millions and, for frontier work, reaches into the billions. The talent requirements follow the same curve: Tier One uses your existing team, Tier Two adds a handful of specialised engineers, and Tier Three demands an entire research division with roles that take months to fill and years to develop institutional knowledge.
None of this means Tier Three is wrong. It means Tier Three is specific. It is the right answer for a narrow set of organisations with proprietary data assets, deep capital reserves, and a business model where the model is the product. For everyone else, the most valuable strategic insight in enterprise AI today is recognising how far you can go by renting intelligence rather than forging it.
References
- McKinsey & Company (2025). The State of AI in 2025: Agents, Innovation, and Transformation. McKinsey Global Survey. https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai
- Stanford University Human-Centered Artificial Intelligence (2025). The 2025 AI Index Report. Stanford HAI. https://hai.stanford.edu/ai-index/2025-ai-index-report
- Gartner (2025). Hype Cycle for Artificial Intelligence, 2025. Gartner Research. https://www.gartner.com/en/articles/hype-cycle-for-artificial-intelligence
- Deloitte (2025). AI Maturity and Digital Value. Deloitte Insights. https://www.deloitte.com/us/en/insights/topics/emerging-technologies/ai-maturity-digital-value.html
- Weill, P., Woerner, S., Sebastian, I., and Kaganer, E. (2025). Grow Enterprise AI Maturity for Bottom-Line Impact. MIT CISR. https://cisr.mit.edu/publication/2025_0801_EnterpriseAIMaturityUpdate_WoernerSebastianWeillKaganer
- Menzies, T. and Zimmermann, T. (2025). The Buy-or-Build Decision, Revisited: How Agentic AI Changes the Economics of Enterprise Software. arXiv:2604.26482. https://arxiv.org/abs/2604.26482
- Peng, S., Kalliamvakou, E., Cihon, P., and Demirer, M. (2025). Developer Productivity With and Without GitHub Copilot: A Longitudinal Mixed-Methods Case Study. arXiv:2509.20353. https://arxiv.org/abs/2509.20353
- DLA Piper (2025). SEC Emphasizes Focus on “AI Washing” Despite Perceived Enforcement Slowdown. DLA Piper AI Outlook. https://www.dlapiper.com/en/insights/publications/ai-outlook/2025/sec-emphasizes-focus-on-ai-washing
- Holland & Knight (2025). SEC and DOJ Warm Up to Enforcement over AI Washing. Holland & Knight Insights. https://www.hklaw.com/en/insights/publications/2025/07/sec-and-doj-warm-up-to-enforcement-over-ai-washing
- Galileo AI (2025). How Much Does LLM Training Cost? Galileo Blog. https://galileo.ai/blog/llm-model-training-cost
- IBM (2025). Why AI Data Quality Is Key to AI Success. IBM Think. https://www.ibm.com/think/topics/ai-data-quality
- BusinessWire / ResearchAndMarkets (2025). Retrieval-Augmented Generation (RAG) Industry Report 2025 to 2035. ResearchAndMarkets.com. https://www.businesswire.com/news/home/20251010008494/en/Retrieval-Augmented-Generation-RAG-Industry-Report-2025-2035

