Slide 01

Every Engineer Picked Their Own. Now You Have a Ticking Time Bomb.

CTO + CFO + CISO + Board

Bottom line up front

Your principal engineers submitted procurement requests for every AI coding tool on the market. You are stalling on all of them. Meanwhile your engineers are not waiting — and your CISO has no idea any of this is happening.

The CLI team is using personal API keys expensed on corporate cards. The VS Code team found a trial version and is "evaluating" it in production. The web IDE team is on the free tier with their work email addresses. And Carl is building his own from scratch. You know all of this is happening. You are pretending you do not.

The exposure These tools have API access to your repositories. Processing your proprietary algorithms. Seeing customer data in test fixtures. Your CISO does not know. Your board does not know. The clock is running.

Slide 02

You Made This Decision in 2008. You Called It SAP. The Logic Is Identical.

The analogy

2008: The e-commerce decision

In 2008, your developers wanted to build the e-commerce platform from scratch. Better performance, perfect architectural fit, complete control. You bought SAP instead. Not because SAP was better. Because your best engineers should not be building shopping carts.

SAP was good enough. Which freed your senior engineers to work on problems that actually mattered — the capabilities that make customers choose you over competitors. Some engineers complained for six weeks. The board promoted you because you shipped.

The principle You did not buy SAP to make developers happy. You bought it so they could stop thinking about infrastructure and start thinking about customer problems. The same logic applies today.

2025: The AI infrastructure decision

Today's decision is identical. Your engineers want to pick their preferred AI tool — maximum workflow fit, personal productivity optimization. Carl wants to build from scratch. You can let every team pick their own and watch your CISO shut it all down. Or you can pick infrastructure.

Not the best tool today. Infrastructure that will exist in 2028. One platform. One security review. One contract. One governance model. Engineers complain for six weeks. Then they adapt. Then they focus on customers instead of tooling debates.

The board's view If that hot startup becomes the winner by 2028, your board will understand when you pivot then. But they won't forgive you for risking the company on unproven infrastructure today.

Slide 03

The Architecture Has Settled. Three Layers. Only One That Will Differentiate You in 2028.

Technology landscape

Layer 1

The model layer — commoditized faster than anyone predicted

Frontier LLMs from established providers. The models themselves are no longer differentiated. What matters is access to them. Today's best model is obsolete in six months. If your platform cannot give you access to whatever model is leading in 2028, you are building on a depreciating asset.

Layer 2

The toolchain layer — converging toward table stakes by mid-2026

Semantic search, context retrieval, system prompts, orchestration. This is what Carl thinks he needs to build. He is wrong. By mid-2026, every serious platform will have comparable toolchain capabilities. The differentiation is in platforms that evolve this layer automatically — not in your team maintaining it.

Layer 3

The viewport layer — least important, most debated

CLI, VS Code fork, or web-based IDE. Three patterns. Your engineers are having religious wars about which one matters. They are having the wrong conversation. The viewport is the most commoditized layer. What matters is whether the infrastructure behind it is stable and will exist in 2028.

Slide 04

Your Board Is Not Evaluating Developer Happiness. They Are Evaluating Enterprise Risk.

Board economics

What your board sees when they look at current state

CLI tool: 18 months in business. Your office sublease you are stuck with has been running longer. If they get acquired, pivot, or run out of funding, you are replatforming while competitors ship features.
VS Code fork: "Rethinking go-to-market strategy" = startup code for "haven't figured out monetization." Your infrastructure depends on their Series C closing.
Web IDE: 14 months old, burning VC to acquire users. Pricing will change the moment they need profitability. Your CFO will have uncomfortable questions when costs increase 400%.
Carl's project: Six months of your most expensive architect's time. Board asks why you're building infrastructure instead of buying it.

What your competitors did instead

Made one infrastructure decision. Picked a vendor who will exist in 2028.
CISO did one security review with a vendor whose practices have a multi-year track record.
Legal negotiated one contract with a company whose survival is not in question.
CFO approved one line item with predictable costs and sustainable vendor economics.
Engineers complained for six weeks and adapted. Now they measure feature velocity improvements — not tooling preferences.

Slide 05

Three Criteria. One Decision. Then Move On.

Selection framework

1

Extensibility without maintenance overhead

The platform evolves with new models, new security requirements, new capabilities — without your team becoming the integration layer. Your engineers should not be debugging toolchain updates. They should not be building the toolchain. They should be building features. This extensibility must be proven — not promised by a startup that has never maintained enterprise infrastructure through a technology transition.

2

Perpetual access to frontier models at sustainable economics

In 2028, frontier models are the secret sauce. Your platform must give you access to leading models as they emerge. If you pick a startup whose business model requires burning VC money to subsidize your usage, their pricing will change when they need profitability. If you pick Carl's custom solution, you are permanently locked to 2025's models.

3

Enterprise-grade governance from a vendor who will exist in 2028

Your CISO needs security and compliance from a vendor with a track record. Your Legal team needs contracts with a company whose survival does not depend on their Series C. Your CFO needs predictable costs from a vendor with sustainable economics. Your board needs to trust that when they ask "will this vendor exist in three years," the answer is yes.

Slide 06

By 2028, the Organizations Winning Made This Decision in 2025. From a Position of Strength.

The 2028 picture

Organizations that made the decision in 2025

One platform decision, defensible to the board. One security review. One contract.
When frontier models improved, they got access automatically — no reintegration, no procurement cycle.
Engineers focused on customer problems instead of tooling debates throughout 2025, 2026, and 2027.
If a hot startup from 2025 became the winner by 2028, they evaluated migrating from a position of strength. "We're moving to the proven winner" is a story boards love.
Compounding velocity advantage — three years of focus while competitors replatformed.

Organizations that did not

Their vendor got acquired and immediately pivoted the product strategy. Replatforming in 2026.
"Best-in-class" tool became abandonware when funding ran out. Six months of migration work.
Pricing increased 400% when vendor achieved market position. CFO conversation no one wants to have.
Carl's custom solution is running 2025 models in 2028, maintained by engineers who could be building features.
"We bet our infrastructure on a startup that hasn't existed as long as that office sublease" ends careers.

Slide 07

You Already Know How to Make This Decision. You Made It in 2008 When You Bought SAP.

Decision close

The decision frame

You can make 2% of your organization happy today by approving everyone's favorite startup tool. Or you can make your board 100% confident in 2028 by making an infrastructure decision now that delivers measurable business outcomes from a vendor your board trusts will exist.

One platform. One security review. One contract. One governance model. One vendor whose survival is not in question. Your CLI people will complain it is not as sleek as the startup tool. Your VS Code people will complain it is not as cutting-edge. Carl will complain it does not solve your specific architecture problems. They will all complain for six weeks. Then they will adapt and become more productive — because they can focus on customer problems instead of tooling problems.

Pick a platform that will exist in 2028.