The AI coding space is moving at an uncomfortable pace.
Even as an AI consultant who tracks this full time, I can’t keep up with every tool that launches. Today’s best model is from Anthropic. Next week it might be OpenAI. The week after, Google surprises everyone.
This makes buying decisions genuinely hard for enterprises — you’re not buying stable software, you’re placing a bet on a moving target.
Here’s how I think about the decision.
1. The model
Anthropic has the Claude series, OpenAI has GPT, Google has Gemini. Each family gets meaningful updates every few months, and which one leads on any given benchmark shifts constantly.
More importantly, models aren’t uniformly good.
Some are better at generating new code, some at finding bugs, some at reasoning through long-running autonomous tasks. This usually reflects where that company focused its training efforts in the last cycle — which means the rankings shift as priorities shift.
Don’t pick a model based on a benchmark from three months ago.
2. The harness
The harness is how your team actually interacts with the model — an IDE integration, a terminal agent, a chat interface.
This matters more than most people realise.
Anthropic’s models have been specifically optimised for use inside Claude Code, and they perform measurably better there than when accessed through a generic wrapper. Other models are trained more broadly and don’t have a preferred harness.
Some harnesses give models access to more tools — file editing, terminal execution, web search — and this directly affects what they can accomplish on real tasks.
The practical implication: if your team builds workflows, hooks and institutional knowledge around a specific harness, that investment doesn’t transfer easily.
Lock-in at the harness level is often a bigger risk than lock-in at the model level.
3. Infrastructure and data residency
Where is the model running, and where is your data going?
Claude is available directly through the Anthropic API and through all major cloud providers. Gemini is Google-only. Some APIs let you specify that requests stay in Europe — important for GDPR compliance.
Others route to wherever spare capacity exists, with no guarantees. This is not a detail to sort out after you’ve signed a contract.
For regulated industries or anything involving sensitive data, data residency needs to be a first-order requirement, not an afterthought.
4. Payment model
This is the decision most teams get wrong, and it has long-term consequences. Subscription gives you predictable costs but unpredictable performance.
Providers have every incentive to quietly degrade quality during peak periods — you’ve already paid. Subscription pricing is also heavily subsidised right now. When that subsidy has to give way to sustainable unit economics, the price will look very different.
Per-request pricing, as used in GitHub Copilot, is conceptually tidy but practically broken. Requests vary enormously in complexity. Pricing them uniformly means either the provider loses money on hard tasks or you overpay on easy ones.
I don’t see this surviving long-term.
Token-based pricing — you pay for exactly what you use — is the most transparent and the most portable. It gives you access to any harness, any model, through APIs or aggregators like OpenRouter.
It’s also the most expensive at face value, though often cheaper than subscription once you account for actual usage patterns.
The practical advice
Don’t make a five-year platform decision in a market that changes every five months.
Run experiments across different teams, don’t sign contracts that are hard to exit, and plan explicitly to revisit the decision every six months. Build that review cadence into the rollout, not as an afterthought.
Next issue I’ll cover the questions this one doesn’t answer: security and legal vetting, the lock-in risk in more depth, and when local models actually make sense for enterprise teams.
If you want to go deeper than tool selection, I also run training programs for development teams on AI-assisted coding, agentic workflows, and how to actually integrate these tools into day-to-day engineering work.
The goal isn’t to chase every new model launch — it’s to help teams build a practical workflow they can trust.
If your team is currently evaluating AI coding tools, hit reply and tell me where the decision is getting stuck — model choice, security, cost, or developer adoption.
|
