Every B2B commerce leader is facing the same set of decisions right now. Should we build this AI capability ourselves. Should we buy it from a vendor. Should we wait until the market settles before committing budget.
Getting these three decisions right matters more than picking the right AI use case. A team that buys when they should build ends up locked into a vendor that owns their data. A team that builds when they should buy spends two years reinventing what was available off the shelf. A team that invests when they should wait funds a category that will look completely different in eighteen months. All three mistakes are common. All three are avoidable with a clear framework.
Here is the framework we use across enterprise B2B commerce engagements.
The three questions, in order
The framework is sequential. Each question filters out a category of bad decision, and the answers compound.
Question one. Is the capability strategic or commodity. A strategic capability is one that differentiates the business in a way buyers notice. A commodity capability is one that customers expect but does not differentiate. Strategic capabilities are candidates for building. Commodity capabilities are candidates for buying.
Question two. Is the technology mature enough to commit to. Mature technology has stable vendor offerings, defensible reference architectures, and a track record of production deployments in similar enterprise B2B environments. Immature technology has shifting vendor landscapes, no clear architectural standards, and limited enterprise B2B precedent. Mature is a candidate for building or buying. Immature is a candidate for waiting.
Question three. Is your substrate ready to support the capability. Even strategic, mature capabilities fail when the data and integration layer underneath cannot support them. Substrate-ready is a green light. Substrate-not-ready is a red light, regardless of how strategic or mature the capability is.
Walking through all three for any AI capability under consideration produces a defensible answer in under an hour. The framework forces the conversation past "should we do this" to the more useful "should we do this now, and in what form."
When to build
Build when the capability is strategic, the technology is mature, and the substrate is ready, but the vendor offerings do not match the specific way your business operates. This pattern shows up most often in B2B contexts where account hierarchies, contract structures, or industry-specific workflows make off-the-shelf AI tools insufficient.
Specific examples worth considering as build candidates. Internal AI tools for merchandising teams that understand your specific catalog structure. AI-powered configuration assistance for complex products where your engineering rules cannot be easily expressed to a vendor. Account-specific recommendation logic that incorporates your contract structure. Custom integrations between commerce AI and your proprietary back-office systems.
Building also makes sense when the capability is foundational enough that vendor lock-in would create strategic risk. AI search and discovery infrastructure, account-aware recommendation engines, and conversational support routing all fall into this category for many enterprise B2B teams. The architecture for these is well-understood, the substrate dependencies are manageable, and the long-term value of owning the capability outweighs the short-term cost of building. We have written about the architectural patterns that make this kind of build manageable.
The risk of building is real. Internal AI development requires technical depth, ongoing maintenance, and accumulated organizational expertise that most enterprise B2B commerce teams do not have on staff. The decision to build is also a decision to invest in the team capable of maintaining what gets built. Without that investment, the build becomes technical debt the moment the original team turns over.
When to buy
Buy when the capability is commodity, the vendor offerings are mature, and the substrate is ready to integrate with them. Commodity AI capabilities are everywhere in B2B commerce right now, and many of them are genuinely valuable. The instinct to build everything internally is usually a mistake when good vendor offerings exist.
Specific examples worth treating as buy candidates. AI-assisted content generation for product descriptions and marketing copy. AI-powered customer support tools layered on top of help-desk platforms. Predictive analytics tools for forecasting and inventory planning. AI search engines that handle the bulk of catalog discovery, augmented by lightweight custom logic where needed.
The buy decision becomes more complex when capability and commodity blur. AI-powered personalization, for example, is increasingly available as vendor offerings, but the implementations differ significantly in how account-aware they actually are. For many B2B teams, the right move is to buy the underlying personalization engine and build the account-aware layer on top, hybrid rather than pure buy. This pattern works well when the vendor is mature on the foundational technology but limited on B2B-specific logic.
The risk of buying is over-buying. AI vendor pricing is rising fast, and the temptation to subscribe to multiple overlapping tools is real. Three subscriptions for capabilities a single vendor could provide is not a savings strategy. It is a cost-creep problem that compounds quarterly.
When to wait
Wait when the technology is moving faster than the market can absorb, when vendor offerings are still maturing, or when your substrate is not yet ready to support the capability responsibly. Waiting is not the same as ignoring. It is an active decision to monitor, prepare, and commit later, when the conditions for success are stronger.
Specific examples worth treating as wait candidates in 2026. Fully autonomous purchasing agents in regulated procurement environments. AI-driven contract negotiation. Multi-agent orchestration patterns where the technology is real but the operational and governance patterns are not yet enterprise-grade. We have covered the line between what is real and what is hyped in agentic commerce specifically.
Waiting is also the right call when the substrate is not ready. Investing in advanced AI capabilities on top of fragmented data, batch integrations, and unmanaged taxonomies produces results that look promising in pilot and fail to scale. The work to fix the substrate is the prerequisite, and that work is the right investment for the current quarter. The AI capability comes after.
The risk of waiting is falling behind. Waiting is not a free strategy. Competitors who move now build advantages that compound. The framing is not "should we wait" in absolute terms. It is "what should we wait on, and what should we move on now to be positioned when the technology matures." That is an active strategy, not a passive one.
A worked example
Consider a B2B distributor evaluating an AI-powered conversational support tool. The framework runs as follows.
Strategic or commodity. The capability itself is commodity. AI-powered conversational support is available from multiple mature vendors. The customizations that make it valuable for this distributor (account-aware contract pricing, integration with their order management system) are where the strategic differentiation lives.
Mature or immature. The underlying conversational AI technology is mature. Vendors have production deployments in similar B2B contexts. Reference architectures exist.
Substrate ready or not ready. Mixed. The order management integration is event-driven and well-instrumented. The contract pricing data lives in the ERP with a clean API. The customer data layer is unified across CRM and commerce.
The decision. Buy the underlying conversational AI engine from a mature vendor. Build the account-aware customizations on top. Integrate with the substrate that is already ready. Total time to value: roughly four months. This is a hybrid build-buy decision, and it is the pattern that works most often for B2B teams operating in mature AI categories.
How to use the framework in practice
For Directors and VPs of eCommerce building 2026 and 2027 AI roadmaps, the framework is most useful as a forcing function for the conversation. Walk every candidate AI initiative through the three questions in order. The conversation that results is consistently sharper than the alternative, which is debating individual vendor demos without a framing structure. The output is typically a prioritized roadmap, not a single decision. For teams whose substrate readiness is the limiting factor on multiple candidate initiatives, the eCommerce technology assessment we run includes the build-buy-wait analysis alongside the broader technical and organizational review.
AI in B2B commerce is delivering real value for the teams that make sharp decisions about what to build, what to buy, and what to wait on. The teams that make bad decisions in any of the three categories pay for it twice. Once in the wasted investment. Once in the opportunity cost of what they could have built instead.
The framework is not complicated. The discipline to use it consistently is.
FAQs
Q: How do I decide whether to build or buy an AI commerce capability?
A: Walk through three questions in order. First, is the capability strategic or commodity. Strategic capabilities that differentiate the business are candidates for building; commodity capabilities are candidates for buying. Second, is the technology mature enough to commit to. Mature means stable vendor offerings, defensible reference architectures, and production track record in similar B2B contexts. Third, is your substrate ready to support the capability. Substrate-not-ready is a red light regardless of how strategic or mature the capability is. The answer that emerges is often hybrid: buy the foundational technology and build the specific customizations that make it strategic for your business.
Q: When is the right time to wait on an AI commerce capability?
A: Wait when the technology is moving faster than the market can absorb, when vendor offerings are still maturing, or when your substrate is not yet ready. In 2026 specifically, candidates for waiting include fully autonomous purchasing agents in regulated procurement, AI-driven contract negotiation, and multi-agent orchestration patterns where the operational and governance frameworks are not yet enterprise-grade. Waiting is not the same as ignoring. It means actively monitoring, preparing the substrate, and committing when the conditions for success are stronger. The teams that wait well also move quickly when the conditions arrive.
Q: What is the biggest risk in build-versus-buy decisions for AI commerce?
A: Two risks recur. The first is over-buying: subscribing to multiple overlapping AI tools instead of consolidating to a smaller vendor footprint with hybrid customization on top. AI vendor pricing is rising quickly, and uncontrolled tool sprawl compounds quarterly. The second is over-building: treating commodity AI capabilities as differentiation candidates and investing scarce engineering capacity in reinventing what mature vendors already offer. The framework that works treats most AI capabilities as hybrid decisions, with the strategic customization built and the commodity foundation bought.