Replatforming is one of the most consequential decisions a B2B e-commerce leader will make. Get it wrong, and the costs compound: lost time, blown budgets, and in some cases, lost jobs. But which element deserves priority attention, the platform itself or the partner who will implement it?
The stakes of the decision
Master B2B research shows that 53% of B2B sellers plan to change or upgrade their e-commerce platforms in the next two years. Companies typically pay 5 to 15 times the license price of the software to implement it. A world-class B2B e-commerce experience takes 12 to 18 months to deliver.
These numbers reflect the reality that building a digital business is more than a technology purchase. Three months are needed just to identify cross-channel customers, build the business case, and develop strategy. Then comes technology assessment, platform selection, building, testing, and change management.
One host shared a personal cautionary tale: selecting the wrong platform forced him to replatform twice in one year, costing the business competitive advantage and ultimately his job.
The debate format
Team Platform featured Teresa Kuske, marketing director at Ergodyne, and Tim Lavender, director of digital development at Beacon. Team Partner included Kristi Gloppen, VP of marketing and e-commerce at Waytech, and Stacy Hanks, VP of global digital commerce at SureWerx. All four practitioners had recently completed or were currently managing replatforming projects.
Round 1: Which choice comes first?
Tim Lavender argued that B2B requirements are so unique that businesses must own the requirements process. Every company has different priorities around order management, product management, or quoting. The platform must fit those specific business requirements, and the business owners understand those needs better than any outside partner.
Teresa Kuske agreed that internal users understand requirements best. Bringing in a partner to get up to speed takes longer than doing the work yourself. She added that partners may pigeonhole companies into solutions they know best, not what fits the business and its future growth.
Your partner might be pigeonholing you into solutions that they know best, and that might not be the best for your business and future growth.
Teresa Kuske, Ergodyne
Kristi Gloppen countered that implementing a platform takes more than technology. Platforms are made for the masses, and they cannot design user experiences. Only partners with deep integration experience can navigate legacy ERP connections and avoid costly overruns.
Stacy Hanks emphasized that partners ask questions while platforms do not. A good partner seeks to understand the business and will help select the right platform for that context.
Platforms do not ask questions. Platforms do not talk back. Your partner does. Your partner asks questions. Your partner seeks to understand what it is you want to do and they are going to help you accomplish it with the right platform.
Stacy Hanks, SureWerx
The partner team reframed the bias argument: experienced partners are biased toward platforms where they had good experiences and delivered successfully. That expertise is an asset, not a liability.
The audience voted 54% in favor of selecting the platform first.
Round 2: Assessing risk
Teresa Kuske stated that she would rather tell leadership they need a new partner than tell them they need to rip and replace a platform. The costs of replatforming extend beyond implementation to decreased traffic, sales, and customer experience.
Tim Lavender compared the platform to a marriage and partners to high school relationships. You want to be with a platform for 10 years. Marriages require communication and problem-solving together. Partners can be changed out when things go awry.
The platform is your marriage. It is a long-term commitment. Your partners are like your high school boyfriends and girlfriends. You can have a couple of them at the same time and throw them away when they are not good.
Tim Lavender, Beacon
Kristi Gloppen pushed back that platform-first advocates were treating partners as vendors rather than partners. True partners cannot be replaced casually because they accumulate knowledge about your business that takes time to rebuild.
Stacy Hanks argued that platforms operate on multi-year contracts and become less responsive once the deal is signed. Partners, by contrast, depend on referrals and have every incentive to make clients happy. When platform issues arise, the platform tells you to check community forums or file a ticket. The partner works to solve the problem.
The audience voted that there is more risk in choosing the wrong partner, giving Team Partner the round.
Round 3: Ecosystem considerations
The final round examined whether to work with partners who specialize in one platform or generalists who work across many.
Stacy Hanks advocated for specialized partners with deep working knowledge of specific platforms. Generalists may list platforms on their website without having true expertise in any of them.
Tim Lavender flipped the metaphor: a great driver in a slow car will not get far. The platform capabilities matter regardless of who implements them. Businesses must own their requirements and select platforms that meet those needs, then find the right partner for implementation.
Teresa Kuske noted that composable architecture changes the equation. With more modular systems, you want partners who have expertise across a breadth of technologies and solutions, not just deep knowledge of one monolithic platform.
Kristi Gloppen emphasized that platforms rate their service providers through certifications and training requirements. These ratings help identify which partners have invested in true expertise versus listing capabilities they do not actually have.
The audience split exactly 50-50, resulting in a tie for round three.
The verdict: A tie with practical implications
Team Platform won round one, Team Partner won round two, and round three was a tie. The overall debate ended in a draw, which the moderators interpreted as validation that both elements matter.
Three practical conclusions emerged from the debate. First, companies should not outsource their strategy. Internal teams must own the understanding of their customers and business requirements. That work cannot be delegated to a partner, regardless of expertise.
Second, the SI selection process deserves serious attention whether it comes first or second. Key factors include depth of platform expertise, relevant B2B market examples, industry focus, and cultural fit. Partners who simply list certifications without demonstrable experience are not true specialists.
Third, the real choice may be about where the marriage metaphor applies. Platform advocates say marry the platform and date the partners. Partner advocates say the partner is the one helping you build a business while the platform is increasingly commoditized technology that can be swapped. Where you land depends on how you view the relative difficulty of switching each element and how much you trust outside expertise versus internal judgment.