Two companies spend the same money, buy comparable technology, and launch within months of each other. Five years later, one runs a different business. The other has a nicer website.
I can’t predict which enterprise commerce projects will pay off by looking at them from the outside.
On paper, two organizations look alike. Same industry, comparable revenue, similar customers, technology of equal capability. Sometimes the same implementation partner. Read the two project plans side by side and you’d expect matching outcomes.
They rarely match.
One company comes out of the project faster and easier to scale. Customers adopt the digital channel because it matches how they want to buy. Sales reps spend their time growing strategic accounts instead of keying in repeat orders. The company folds in acquisitions without a fire drill. Shipping a new capability becomes routine work rather than a six-month plan. Five years on, the leadership team still calls it one of the best investments they ever made.
The other company launches on time, celebrates the redesign, sends the press release, and checks the box. The new site performs better than the old one. Running the business still feels the same. Customers keep emailing purchase orders because some workflows never made it online. Sales reps still process orders instead of advising accounts. Product data lives in four places. Reporting doesn’t reconcile. The platform is new, and most of the frustrations that justified the spend survived the migration intact.
Afterward, the executives tend to land on the same line:
“The implementation was successful, but it didn’t feel transformational.”
I’ve heard that sentence from a lot of people.
Almost none of those projects failed. Most launched. Most delivered what the contract promised. The software worked, the integrations held, the timeline was reasonable. Judge them by standard implementation metrics and many score well.
Something is still missing, and I don’t think it’s a technology problem. I think we keep asking technology to solve business problems it was never built to solve.
We Modernize the Interface Before the Business
When a company decides to invest in commerce, the conversation starts with the storefront. That’s reasonable. The storefront is the most visible part of the experience, where customers browse, order, and check inventory. It’s also where operational problems surface.
When negotiated pricing displays wrong, customers blame the website. When inventory is off, or reordering is clumsy, or a quote takes three emails and a phone call, they blame the website too.
The storefront wears the operational decisions of the past decade on its face. Customers see it, so it’s the easiest place to point a budget.
Customer experience rarely begins at the storefront. It starts upstream, in the systems that decide what the storefront can deliver. ERP holds pricing, inventory, and order history. Product data decides whether a customer can find and compare items. Customer records drive personalization. Internal workflows decide whether an approval, a quote, a return, or a service request can happen online at all.
The website exposes those experiences. It doesn’t create them.
Replace the front end without touching the business underneath, and you get a better-looking version of the same experience. The company paid for a new digital experience. Customers still hit the operational reality they hit before the project started. The interface changed while the business stayed put.
The Best Commerce Projects Start With Questions That Aren’t About Commerce
One pattern shows up again and again.
The projects with the biggest impact don’t start by comparing platforms. They start with questions that sound unrelated to commerce.
- Why does customer service answer the same five questions thousands of times a month?
- Why are experienced buyers still emailing purchase orders instead of using the portal?
- What do customers keep asking sales reps for that should already be online?
- Why does adding a product line mean changes across five disconnected systems?
- Which processes break tomorrow if one key person takes a long vacation?
None of those questions are about Adobe Commerce, Shopify, or Shopware. They’re about operational friction.
The distinction matters because friction compounds. Each workaround looks harmless on its own. One spreadsheet isn’t a strategy problem. One approval step isn’t expensive. One integration that needs the occasional patch feels manageable.
Stack a decade of those decisions together and they shape how the business runs. Teams work around the friction because they have to. Customers work around it because they want to keep buying from you. After a while, people assume this is how enterprise commerce works.
It’s how this business works today, which is a different thing.
Technology Became the Easy Part
Ten years ago, the platform choice felt like the biggest decision in the room. Today it’s one of the least interesting.
Platforms still matter. Adobe Commerce, Shopify, Shopware, commercetools, and BigCommerce each suit different kinds of organizations, and the choice shapes the business for years. It deserves real evaluation.
A platform no longer creates a competitive advantage on its own. The advantage comes from what you do with it.
- Can you launch a product without touching five systems?
- Can customers solve routine problems without calling support?
- Can your sales team build relationships instead of processing transactions?
- Can you put AI into a workflow that matters because your operational data holds up?
Those capabilities matter more than whether a feature shows up on a comparison matrix.
AI made this impossible to ignore. Companies are excited about intelligent search, AI support, automated merchandising, and agentic commerce. Those are real. They all sit on a foundation that gets far less attention: connected systems, reliable product data, consistent customer records, and operational discipline.
AI surfaces the complexity underneath instead of removing it.
For years, companies worked around disconnected systems because people covered for them. Someone knew which spreadsheet had the right pricing. Customer service knew how to read an incomplete order history. Sales reps filled the gaps the software left.
AI doesn’t cover for you. It expects the business underneath to make sense.
Companies that built operational maturity years ago are seeing large returns from AI now. For the ones that didn’t, AI put an old business problem in plain sight.
Maybe We Need a Different Definition of Modernization
I’ve started to think we define modernization too narrowly.
For many companies, modernization means swapping one platform for another. A project with a start date, a launch date, and an end. They measure success by whether it shipped on time and whether the planned features work.
That’s one definition. I don’t think it’s the most useful one anymore.
The companies that get the most from modernization don’t talk much about the launch afterward. They talk about how fast they can respond to a customer request, absorb an acquisition, test a new business model, or move into a new market without rebuilding the stack every few years.
What they’re buying is the organization’s ability to change quickly. That outcome keeps paying off long after the project ends.
Final Thought
Next time replatforming comes up, don’t open with vendor demos or feature matrices. Those have their place, and they’re worth more once you know what business you’re trying to build.
Ask where customers hit friction. Ask which manual processes your team accepted as normal. Ask whether your operational data can support the business you’re planning, not just the website you’re about to launch.
The companies that get the most out of this are using technology to become better businesses.