Marketplace Is an Outcome, Not a Goal

TL;DR

• Companies that try to "launch a marketplace" as a standalone project typically end up with low adoption, high costs, and blurry returns
• The right question isn't "how do I build a marketplace?" but "how do I digitize the operation I already have?"
• The network of customers, sales reps, and suppliers that exists today is the real asset; the marketplace is what emerges when that network is digitized consistently
• Treating the marketplace as a destination instead of a consequence is the main reason these projects die before they scale

Why do so many marketplace projects stall right after launch?

The logic seems reasonable at first glance: the company sees competitors digitizing channels, realizes its sales process still depends on phone calls, spreadsheets, and in-person visits, and decides to "launch a marketplace." It hires the technology, builds the storefront, configures the catalog. Six months later, transaction volume is negligible, reps are still running everything through texts and email, and leadership starts questioning whether the project makes sense at all.

The problem isn't the technology. It's the sequence.

When the marketplace is treated as the goal, the project starts with the interface, not the operation. The company builds a store before digitizing the sales process that would feed that store. There's no habit of digital record-keeping, no integration with the real order flow, no clear reason for the rep or the buyer to change their behavior. The result is a technically functional platform that operates on the sidelines of the real business.

This isn't a one-off execution failure. It's a design flaw.

The asset that already exists and hasn't been digitized

Every company with some level of commercial maturity already has a network: repeat customers with purchase histories, field reps or independent sales agents with active relationships, suppliers or partners the supply chain already runs on. This network exists in the physical world, supports real revenue, and carries trust built up over time.

The mistake of the "marketplace as a goal" project is ignoring that network and trying to build a new one from scratch, this time digital. The company essentially competes with itself: the old channel keeps operating because that's where the relationships live, while the new channel waits for adoption that never comes.

The right question comes earlier: how does this existing network start operating digitally? How does the order that today arrives by text message become a structured record? How does the rep who visits ten customers a week gain visibility into those customers' behavior between visits?

When digitization starts from this real network, three things happen sequentially and sustainably.

First, the current operation gains efficiency. Orders come in structured, inventory responds in real time, and customer history becomes accessible without depending on a rep's memory. This reduces transaction costs within the chain that already exists.

Second, with the operation digitized, adjacent revenue opportunities emerge that were previously invisible. The customer who regularly buys input X is a natural candidate for a working capital line. The partner selling product A has the right profile to offer complementary service B. Upsell and cross-sell stop being prospecting efforts and become data reading from a network that's already operating.

Third, and only then, does market share expansion make sense. The platform has volume, documented behavior, and metrics that justify growth. New reps step into a structure that works. New buyers find an experience that's already calibrated.

The marketplace that appears at the end of this journey isn't a project. It's the name given to the state of the operation after it's been digitized.

The "we already have a website" objection

A frequent pushback in boardrooms goes like this: "we already have a digital presence, we don't need a marketplace", or, at the opposite extreme, "we don't want to become Amazon."

Both objections stem from the same conceptual mistake: they assume a marketplace is a product category, a type of website, a business model decision. From there, the company compares what it has with what it sees from the big players and concludes it doesn't apply, that it's too complex, that the cost isn't justified.

But a marketplace, in the sense used here, isn't a model to imitate. It's the natural consequence of digitizing a commercial chain that already has multiple participants, whether that's distributors and retailers, a network of independent reps and end customers, or suppliers and intermediary buyers.

Having an e-commerce site is not the same as having a digitized operation. A website captures transactions. A digitized operation connects the participants in the chain, records behavior, creates actionable data, and reduces friction at every touchpoint, from quote to post-sale.

The Cost of Inaction

Keeping the sales operation in an analog or semi-analog model carries costs that rarely show up under that label on the income statement, but that consistently erode margin.

• Rework cost: order errors due to lack of structured data entry, manual reprocessing, discrepancies between what the rep promised and what the system recorded
• Opaque relationship cost: without digital data, the company doesn't know which customers are reducing purchase frequency before they churn, and can't act preemptively
• Lost opportunity cost: the customer who would buy an adjacent service never gets the offer because there's no data identifying the right moment
• Key-person dependency cost: when the customer relationship lives in the rep's contact list and personal phone, they leave and take the customer with them. Digitizing the operation transfers the relationship to the company's platform

These costs don't show up as "digitization delay" on the P&L. They show up as thinner margins, unexplained churn, growth below potential, and a sales team overloaded with operational tasks that shouldn't exist.

Principles for getting it right

• Start by mapping the current operation: who are the participants in your chain, how does each transaction happen today, where's the friction
• Digitize what already exists before creating what doesn't: digital habits grow on top of real behavior, not on top of a new interface
• Treat data as a byproduct of the process, not as a separate project: when the operation is digital, data emerges naturally
• Define the marketplace as a state, not a deliverable: it will be "done" when the existing network operates predominantly through digital channels
• Measure network adoption, not just transaction volume: the relevant metric is how many of your current participants already operate through the digital channel

FAQ

Does the company need to abandon its current channels to digitize the operation? No. The starting point is digitizing the channels that already exist, not replacing them. Behavior migration is gradual and happens as the digital channel offers less friction than the analog one.

Is this process only for large companies? No. Any operation with recurring transactions and multiple participants, regardless of size, benefits from the same logic. The scope is smaller, but the sequence is the same.

How long does it take for the marketplace to emerge? It depends on the complexity of the chain and the depth of digitization. But the more useful question is a different one: how much longer will the company keep losing margin while postponing the decision?

About this publication

The Cost of Selling is CWS Platform's publication dedicated to the economics of B2B sales operations. Each edition starts from a business thesis and develops the argument with a focus on executive decision-making: what it costs, what stalls it, and how to structure it. CWS builds digital infrastructure for complex commercial operations, reducing transaction costs in chains with multiple participants.