The Customization Tax Nobody Talks About
A mid-sized logistics company spent $400,000 on enterprise AI software last year. Great product. Proven ROI. Used by dozens of their competitors.
Six months later, they wondered why their AI investment hadn’t created competitive advantage.
The answer was simple: they’d paid for efficiency, not differentiation. Every one of their competitors could write the same check.
Most executives miss this: buying off-the-shelf AI tools gives you table stakes, not advantage. The customization you skip to save money today becomes the competitive gap that costs you market share tomorrow.
But I’ve also seen startups burn through runway building custom AI systems for commodity capabilities where excellent solutions already existed. Eighteen months and three engineers building what they could have licensed in an afternoon.
The question isn’t whether to build or buy. It’s knowing which capabilities deserve custom investment and which don’t.
The Build Calculus Has Changed
Three years ago, the rule was clear: if you’re not a software company, don’t build software. A hospital shouldn’t build its own electronic health records. A retailer shouldn’t build its own e-commerce platform. Software required specialized teams, long timelines, and maintenance that distracted from core business.
That calculus shifted.
I built my personal AI assistant system, Jarvis, over a weekend. It manages contacts, surfaces information before meetings, sends morning briefings, handles dozens of automated workflows. Three years ago, that would have required a development team and six months. Budget: $200,000 minimum.
Current hard costs: about $50 per month in API fees and hosting.
But here’s what matters for strategy: Jarvis is designed for exactly how I work. My specific meeting prep needs, my relationship tracking approach, my morning routine. No vendor would build that because the market for “Sean’s particular workflow preferences” is exactly one person.
That customization is the point. Off-the-shelf tools are lowest common denominator by design. They serve the average user. When you build, you create tools that fit your specific workflows, your specific data, your specific competitive context.
A caveat before anyone gets excited: I already understood cloud infrastructure, databases, and API integrations. AI accelerated my building, but it didn’t eliminate the need for foundational technical literacy. The barrier has dropped from “you need a development team” to “you need technical literacy plus AI assistance.” That’s massive. It’s not “anyone can build anything with zero knowledge.”
Three Questions That Clarify the Decision
When evaluating whether to build custom AI capabilities or buy existing solutions, three questions cut through the noise:
Do you have proprietary data that makes your AI better than anything you could license? A payments company with transaction data across millions of businesses revealing fraud patterns no single merchant could detect? Building fraud detection makes strategic sense. Using the same public datasets everyone else accesses? Buy the mature solution.
Is this capability core to how you differentiate? A pizza company built its own AI ordering system because they had data about ordering patterns nobody else had, and the capability was customer-facing and central to their experience. Their cloud infrastructure? Bought from a vendor. Hosting is commodity.
Can you attract and maintain the talent to build and iterate? Building isn’t a one-time project. It’s an ongoing capability. If you can’t staff it sustainably, buy even when building seems strategically attractive.
The honest assessment most leaders avoid: your organization is probably less ready to build than you think. Most companies think they’re more mature than they are. That gap matters because organizations that aren’t ready should be buying more than building, learning more than implementing.
What You Can Do This Week
List every AI capability your organization currently uses or is considering. For each one, answer the three questions above. Honestly.
You’ll quickly see which capabilities justify custom development and which should be purchased.
The pattern: build clusters around proprietary data and core differentiation. Buy clusters around speed to market and commodity capabilities. Alliance (the third option) emerges when you need complementary capabilities that would take too long to develop alone.
Most organizations should be building fewer custom AI systems than their engineers want and more than their executives think possible. The mistake isn’t picking the wrong answer. It’s applying the same answer to every capability without thinking through what creates advantage.
The full framework, including the maturity model, the strategic sourcing matrix, and worked examples across industries, is in AI Strategy for Business Leaders. I’ve also posted templates and assessment tools at my companion resources that walk through the build-buy-ally decision step by step. And if you want to understand how I approach the intersection of technology and strategy more broadly, my books cover the frameworks I return to again and again when the field shifts faster than the playbooks.