How Enterprise Brands Should Buy eCommerce Capability: Build, Hire or Partner
Build versus buy is the wrong question because it is actually three questions: technology, operations, and growth. Enterprises that answer all three the same way pay for it, usually eighteen months later.
- Split the decision three ways. Technology, operations, and growth have different failure modes, and the right sourcing answer differs for each.
- Own the data, the customer relationship, and the decision rights in-house. Rent execution capacity and specialist skill, which change too fast to be worth permanent headcount.
- Partners work when governance exists: a single internal owner, shared dashboards, quarterly business reviews against pre-agreed metrics, and contractual data ownership with clean exits.
Enterprises keep asking me the build versus buy question as if it has one answer. It has three, because eCommerce capability is three different things wearing one name: technology, operations, and growth. They fail differently, they age differently, and they should be sourced differently. I have sold to enterprises for most of my career, and the pattern I see is consistent. The companies in trouble are not the ones that chose wrong on one axis. They are the ones that answered all three axes with a single decision, usually whichever one the loudest stakeholder preferred.
Technology: build the differentiated, rent the commodity
Most enterprise eCommerce technology projects fail by building things the market already sells. Storefronts, checkout, catalogue management, order management, these are mature, commoditised layers. Building them internally consumes quarters of engineering time before a single order flows, and the maintenance burden never leaves. The build case exists only where your business is genuinely unusual: a pricing engine tied to your dealer network, integrations into legacy systems nobody else has, a product configurator competitors cannot copy. The rule I give every enterprise room is simple. Rent the commodity, build the differentiator, and own the data layer regardless of who writes the code. If your customer data, order history, and integrations live inside a vendor’s black box, you have not bought capability. You have bought dependence.
Operations: hire the core, flex the edges
Operations is the one layer where in-house ownership is usually non-negotiable. Daily marketplace hygiene, inventory sync, pricing execution, returns, reconciliation, account health: this work touches money and brand reputation every single day, and it compounds knowledge that should stay inside your walls. An enterprise that outsources all of it learns nothing and controls nothing. But the mirror mistake is just as common: hiring a large permanent team sized for peak season, then carrying that cost through the quiet months. The stable answer is a compact internal core that owns the numbers and the decisions, with partner capacity flexed for events, expansions, and new channel launches. The core provides memory. The partners provide elasticity.
Growth: partner first, then hire the owner
Growth skill decays faster than any hiring cycle can refresh it. Marketplace algorithms shift, ad platforms change quarterly, quick commerce rewrites its rules season by season. A specialist you hire today is maintaining last year’s playbook within eighteen months unless they live across many accounts, which by definition your in-house team does not. This is the strongest structural case for partnering. An agency sees patterns across dozens of brands and amortises the cost of staying current. But partnering only works with an internal counterweight: one senior owner who sets targets, reads the same dashboards, and can challenge the partner’s choices. Enterprises that hand growth to an agency without that owner get autopilot. Enterprises that refuse partners entirely get a team that is confident, expensive, and slowly out of date.
Each model fails in a signature way
Knowing the failure modes in advance is most of the defence. They are remarkably consistent:
- Build fails by calendar. The platform ships late, the market moved, and the sunk cost keeps a mediocre system alive for years because nobody wants to write it off.
- Hire fails by isolation. A capable individual inside a slow approval structure, cut off from cross-market pattern exposure, with no succession plan when they leave. One resignation erases the capability.
- Partner fails by neglect. The agency’s A-team fades after onboarding, reporting becomes theatre, and nobody inside the enterprise has enough context to notice for two quarters.
Governance is what makes any of this work
The sourcing decision matters less than the governance wrapped around it. Every arrangement that works, in my experience, shares five features. A single internal owner with real authority, not a committee. Shared live dashboards, so the partner and the enterprise argue from the same numbers. Quarterly business reviews against metrics agreed at contract signing, not invented at review time. Contractual data ownership, with accounts, ad assets, and analytics in the enterprise’s name. And clean exit terms, because a partner who knows you can leave behaves like a partner who wants you to stay. Run that governance and the build, hire, partner mix becomes adjustable as you learn, which is the actual goal. We see this most clearly in technology engagements, where an enterprise keeps product direction and data in-house and brings us in for App Development capacity under exactly this structure. The capability ends up owned by the enterprise, rented where renting is rational, and governed well enough that the question of who built what stops mattering. That is what buying eCommerce capability properly looks like.