Build, Buy, or Partner: The Real AI Strategy Decisions
“We need to be doing more with AI” is urgency, not strategy. The real decisions are specific: build when proprietary data or control is the edge, buy when speed to market matters more than originality, and partner when scale and influence matter more than ownership. In every case, the actual moat is the proprietary data and specific workflow a company builds around the model, not the model itself—everyone has access to roughly the same underlying architecture. Enterprise AI deployments mostly stall for three predictable reasons: vague objectives, dirty or fragmented data, and integration debt, not because the technology itself doesn’t work.
Build, Buy, or Partner: How the Smartest Companies Choose
The AI strategy question isn’t really whether to use the technology. It’s how. Three real patterns, not competing philosophies:
- Build when control is the advantage. J.P. Morgan built its own AI tools for traders and analysts because its data is too sensitive and its workflows too specialized to hand to an outside vendor. Proprietary data or genuinely unique processes justify the cost of building in-house.
- Buy when speed to market matters more than originality. HubSpot didn’t spend years developing language capabilities from scratch—it embedded existing machine-learning tools into its CRM and shipped fast. Buying is the right call when reinventing the wheel costs more time than it’s worth.
- Partner when scale and influence matter more than ownership. Nvidia didn’t try to own every layer of the AI stack—it built alliances across every major cloud provider and became the backbone of the computing boom without needing to control the whole stack itself.
The mistake to avoid: trying to do all three at once—building tools that weren’t needed, signing vendor contracts that never get fully used, and chasing partnerships with no clear strategic rationale.
That produces diffusion, not advantage. Clarity about which lever fits a given capability is the actual strategy; “doing more with AI” is not.
The Real AI Moat Is Data and Application, Not the Model
In the race for bigger LLMs, the model itself isn’t a moat. Most serious players use variations on the same basic architecture, which makes the model a commodity, not a differentiator.
The moat comes from proprietary training data and the specific use case connected to it.
Bloomberg didn’t try to out-build Silicon Valley’s largest labs. It trained Bloomberg GPT on decades of proprietary financial data—earnings calls, analyst reports, and trading signals—that no competitor has access to. That makes the application useful, trusted, and defensible in a way a generic model never could be on its own.
The same logic applies in healthcare: a generic LLM can summarize medical text, but the defensible product comes from training on years of clinical data, connecting it to HIPAA-compliant workflows, and designing around the specific needs of doctors and hospitals.
Even Microsoft’s real edge has less to do with access to OpenAI’s technology and more to do with embedding that technology into the daily workflow of 400 million Outlook, Teams, and Excel users.
The model makes the capability possible. The workflow is what makes it sticky—the same pattern that made Oracle’s databases defensible for decades, not because SQL was magic, but because it became tied to mission-critical business processes and trusted data.
Why the Biggest AI Labs Won’t Win the Application Layer
The assumption that AI’s future belongs to whoever has the biggest labs—Google, Meta, and Microsoft, with the GPUs, PhDs, and patents—misreads where the next wave of application-level innovation actually comes from.
It comes not from scale, but from speed, proximity to the problem, and a willingness to ship things that don’t look normal yet.
Big companies are structurally bad at that. Ideas run through roadmaps, legal review, and brand-consistency checks until whatever launches is safe, familiar, and forgettable.
Google published much of the core transformer research behind modern AI, and OpenAI—smaller and less polished—captured the world’s attention with ChatGPT anyway, because it shipped something raw instead of waiting for it to be safe.
Midjourney embarrassed Adobe on image generation, Perplexity is rewriting search behavior, and Runway is doing things in video production traditional studios haven’t touched. None of them out-funded the incumbents. They simply moved faster in the gray area before something becomes officially approved.
The most interesting AI applications increasingly won’t come out of corporate R&D labs at all. They’ll come from operators close to a real, narrow pain point—a recruiter building an AI screener or a logistics manager automating dispatch—solving one problem obsessively without waiting for permission.
AI has lowered the barrier to building something. For most large, efficiency-optimized organizations, the remaining barrier is culture, not capability, and culture is much harder to buy than compute.
DeepSeek Signals a Shift From Dependency to Ownership
Most companies building on AI today are tied to closed, metered platforms—OpenAI, Google, and Anthropic. They’re powerful, but expensive, and every request depends on someone else’s roadmap and pricing.
DeepSeek matters less as a single model release and more as a signal: it’s open-source, performs on par with GPT-4, and can be self-hosted and fine-tuned without an enterprise-grade GPU cluster, running acceptably on consumer-tier hardware such as A100s, RTX 3090s, and even local edge devices.
That puts serious AI capability within reach of startups and mid-market teams that previously couldn’t afford eight-figure infrastructure budgets.
The strategic shift underneath the cost savings is that companies can now own their models and shape their AI roadmap around what actually drives value, rather than around someone else’s billing model.
Call it a move from centralized AI dependency toward distributed AI ownership.
In AI, Agility Beats Scale
Between 2023 and 2025 alone, we saw multimodal capability, a wave of small language models, open-source breakthroughs, and constantly shifting pricing structures.
What worked last quarter may not work next. Companies treating AI as a “launch it and leave it” initiative are already behind companies treating it as a continuously iterating capability.
Agile companies test fast:
- Can this specific process be automated?
- What is the measured ROI of a pilot?
- Should the company expand it or kill it based on evidence?
They don’t wait to build a perfect solution before shipping anything.
HubSpot and Canva both shipped multiple lightweight AI features, learned what stuck, and iterated while slower competitors stayed in planning mode.
In a market this volatile, strategic flexibility—modular AI stacks, staying open to swapping in better tools as they emerge, and letting cross-functional teams experiment rather than centralizing every decision—is the actual competitive edge.
Being early doesn’t matter if a company is too rigid to adapt when the game changes again, which in AI right now, it reliably does.
AI as a Crisis Lever, Not Just a Cost Cut
Downturns test every company’s ability to adapt, and most respond by tightening budgets and pausing initiatives—exactly when AI offers a different lever.
Three levels of impact:
Cost-driven optimization: automating repetitive processes. Unilever used AI to optimize its global supply chain during COVID, saving millions in logistics and forecasting.
Smarter, faster decisions: AI-powered analytics help companies react to volatility with data instead of gut calls. Target has used AI-driven demand forecasting to preserve margins through uncertain periods.
Accelerating innovation while competitors stall: crises freeze most companies’ innovation exactly when market share is up for grabs. Shopify has doubled down on AI tooling during slowdowns, setting merchants and itself up for share gains once conditions normalize.
The companies that come out of a downturn stronger are usually the ones that used AI to keep moving while competitors defaulted to survival mode.
Why Most Enterprise AI Deployments Stall
Enterprise AI is genuinely transformative and still hitting real headwinds for two structural reasons.
First, the technology gets misunderstood—treated as a general-purpose fix rather than something that excels at specific, narrow tasks and struggles with the broader, nuanced judgment humans handle effortlessly. Copilot-style code generation has a clear, strong ROI; generic summarization and formatting tasks have a real but much smaller one.
Second, AI initiatives frequently get adopted from FOMO rather than strategy—rushed, poorly scoped projects launched because competitors are doing it, not because a clear business objective demands it.
The resulting failures cluster into three predictable buckets:
- Objectives: vague goals such as “improve efficiency” with no measurable success criteria. The fix is unglamorous: build a real ROI model before starting.
- Data: enterprises routinely lack the clean, sufficient, consolidated data AI actually needs to train well, and underestimate the investment required to get there.
- Integration: existing IT systems and fragmented data sources often can’t support new AI tooling without a costly consolidation project first.
The practical guidance that follows: resist placing large bets on a still-evolving technology, look for small projects with clear and achievable ROI to build internal confidence before scaling, and keep every initiative tied to actual strategy rather than chasing the hype cycle.
The gap between AI’s promise and its enterprise results right now is deployment discipline, far more than the technology itself.
The Chatbot Reflex Is a Lazy AI Strategy, Not a Real One
Most product teams responding to AI pressure default to one move: bolt on a chat interface and call it innovation.
This has already failed once.
Voice assistants—Alexa, Google Home, and Siri—sold in the billions, got used for weather and music for about 30 days, and then got exiled to a junk drawer because speaking instructions out loud is a genuinely poor interface for most tasks.
Chat is great for exploring an open-ended question. It’s terrible once someone already knows the outcome they want.
Asking an AI to format a spreadsheet feels magical once and infuriating by the third repetition, when a button would have taken one click. Microsoft Copilot in Excel is a real example of impressive technology applied to a worse interaction than the one it replaced.
Adobe Firefly is the counterexample done right. It has a prompt box, but most users still reach for sliders, presets, and visual controls because visual problems deserve visual interfaces. Adobe added AI capability without burning down the existing user experience.
The lesson generalizes past Firefly: AI should amplify existing behavior, not force people into a new one just because the underlying model is impressive.
Good AI user experience in the future probably won’t look like a chatbot on every page. It will be intelligence embedded so naturally that it’s barely noticed—closer to Clippy’s opposite than Clippy’s successor.
AI Won’t Kill Creativity. It Will Make It Impossible to Hide
A related strategic point is easy to miss in the deployment and ROI conversation: as AI makes “good enough” execution available to everyone instantly, “good enough” stops being a differentiator at all.
Technology raises the floor and exposes the ceiling. It makes execution trivial and makes originality visible by contrast.
Organizations that use AI to amplify genuine imagination—rather than mistake the tool for the idea—will stand out more, not less, as the volume of AI-assisted “good enough” work increases around them.
Should a company build, buy, or partner for AI capability?
It depends on what the advantage actually requires: build when proprietary data or control is mission-critical, buy when speed to market matters more than originality, partner when scale and influence matter more than ownership. Trying to do all three without a clear rationale produces confusion, not advantage.
Where does a real AI competitive moat actually come from?
Rarely the model itself; most companies use variations on similar underlying architecture. The moat comes from proprietary training data and the specific workflow or application built around it, the same pattern that made databases and CRMs defensible for decades before AI existed.
Why do most enterprise AI deployments fail to show strong ROI?
Three recurring causes: vague, unmeasurable objectives; poor-quality or fragmented underlying data; and IT systems that aren’t actually ready to integrate new AI tooling. The technology itself is rarely the limiting factor.
Is AI useful during an economic downturn, or just a cost-cutting tool?
Both, and the strategic opportunity is in the second half: cost reduction is the obvious use, but companies that also use AI to make faster decisions and keep innovating while competitors freeze tend to gain disproportionate market share once conditions normalize.
If you’re not sure whether to build, buy, or partner for AI
Chasing AI urgency without a clear build, buy, or partner rationale—or managing an enterprise deployment stalled on objectives, data, or integration—is exactly the kind of problem I help executives work through inside Fractional Strategy & Leadership.
If urgency is outrunning your actual AI strategy, book my free consultation and let’s get a clear-eyed read before the next budget cycle.
