Replatforming: what should we fix first, the platform, the data or the team?

The plan first, then the team and the data, with the platform last. For commerce replatforms, three things decide whether any platform works: clean product data, one inventory count every system agrees on, and a team that can deploy changes safely. Almost none of them are platform features. Who you sell to, who you sell through and who owns the customer decide which platform fits.

The order

The order
we’d work in.

A replatform is on the table for a reason: the site launched and nothing moved, or sales, marketing and commerce don’t share customer data. The platform gets blamed while the operating model stays broken.

The order follows the Apex Connected Growth System, which aligns a company’s plan, people, systems and partners around one business goal and keeps it moving: Start with the plan, then the people and the systems.

  1. 01

    Plan.

    Write down the goal the move serves, the milestones and the cost. Decide how you sell before you pick a vendor: who you sell to, who you sell through, and who owns the customer at the end.

    Plan
  2. 02

    People.

    Name who will run it, and make sure the team can deploy changes safely.

    People
  3. 03

    Data.

    For a commerce replatform: fix product data first. Then one inventory count every system agrees on, and a record of what customers do, kept in a database you already own.

    Systems
  4. 04

    Platform.

    Last. Once the plan, the team and the data are settled, the platform choice is usually clear.

    Systems

The platform, last

When the platform
finally gets chosen.

In commerce, clean product data, one inventory count every system agrees on, a record of what customers do kept in one place, and a team that can deploy safely decide whether it works on any platform. Almost none of them are platform features.

We deliver on Webflow, Sanity and Vercel for brand and experience, and on Shopify and BigCommerce for commerce. Which one fits depends on who you sell to, who you sell through and who owns the customer.

The aim is a system you own, built so a part can be swapped without rebuilding the rest.

Other ways to do it

A platform swap
or a system change?

A swap fixes the platform and leaves the operating model as it was. If the plan, the data and the team already work, that can be all you need. If they don’t, the new platform inherits the old problems.

The Studio keeps testing and improving after launch, and hands your team a system it can run.

How a hire, an agency, a tool stack and an Apex pod compare ↗

Is this the right route?

Who it’s for.
Who it isn’t.

The Studio fits a replatform when the growth problem crosses brand, website, commerce, data and AI.

A good fit

  • A replatform is on the table, and you want it to fix growth, not only the site.
  • Marketing, sales and commerce don’t share the same customer data.
  • Direct, wholesale and dealer sales run on separate systems.

Another route fits better

  • You want only the migration, with no plan behind it. A production shop will be faster.
  • You want the code handed over at launch and no work after it.
  • You are running a vendor shortlist and want a feature matrix. We sit at the table with you.

Questions

Questions about
replatforming.

What companies ask before a fit call.

Should we pick the platform first?

No. Decide how you sell before you pick a vendor: who you sell to, who you sell through, and who owns the customer at the end. The platform is the last decision, not the first.

What do we fix first in the data?

For commerce builds our first-year order is: fix product data first, establish one inventory count every system agrees on, keep a record of what customers do in a database you already own, and measure visits from AI assistants.

Why can’t customers find our products on our website?

Product data comes first in a commerce build: fix the data, then the site.

Which platform should we move to?

Which one fits depends on who you sell to, who you sell through and who owns the customer. We deliver on Webflow, Sanity and Vercel for brand and experience, and on Shopify and BigCommerce for commerce.

Does replatforming mean starting over?

Not if the architecture is built so a part can be swapped without rebuilding the rest. The aim is a system you own.

How long does a build take?

Typically 4 to 6 weeks for Launch (one market, one language, standard commerce), 7 to 10 weeks for Build (direct, retail and dealer or B2B working together) and 10 to 14 weeks for Scale (multiple regions, languages, channels or teams, or complex integrations). The plan sets the scope before anything is built, and timelines assume you can supply product data and approved brand assets and make decisions on schedule.

Who does the work?

A pod of senior operators who work alongside your team: two or three people to start, up to eight as the scope calls for it, named in your plan. The people you meet are the people who do the work.

Next step

What should the
replatform fix?

Bring the growth problem you would fix first. We’ll say whether Apex is the right team.

Book a fit call

A conversation to check fit. No charge.