What's the difference between a CRO and a VP of Sales for a B2B marketplace?

The end-to-end process both roles sit inside

A B2B marketplace does not have one revenue process. It has two acquisition motions that must be sequenced against each other, plus a matching layer in the middle that neither motion controls alone. Understanding where each role plugs into that sequence is the whole distinction.

The seller motion runs: source candidate sellers in a target category → verify them (licensing, insurance, capacity, references) → onboard them into listings or catalog → deliver their first qualified buyer → get them to a repeat transaction. That last step is where the seller becomes durable supply rather than a logo on a page. Most marketplaces find the drop-off between "listed" and "first transaction" is the single largest leak on the supply side, because a seller who lists and receives nothing within a few weeks quietly stops responding.

The buyer motion runs: generate demand in a category → qualify the buyer's spend and category fit → let them search and see whether inventory exists → produce a match → close the transaction → drive repeat purchasing. The buyer motion has a hard dependency the seller motion does not: it fails at the search step if the seller motion has not already succeeded in that same category. A buyer looking for certified suppliers of a specific industrial component in a specific region does not care that your marketplace has thousands of sellers overall. They care whether three to five of them serve their category and geography.

The matching layer sits between the two: search ranking, filters, RFQ routing, quote turnaround, and the review or rating system that lets buyers trust a seller they have never met. This layer is usually built and tuned by product and engineering, but its business rules — which sellers get surfaced, whether promoted placement exists, how fast a seller must respond before they are down-ranked — are revenue rules with revenue consequences.

A VP of Sales sits inside one lane of this process: the buyer motion from qualification through close, plus whatever quota-carrying team executes it. Their inputs are leads and inventory; both arrive from somewhere else. When a deal stalls because the category is thin, the VP of Sales can escalate but cannot fix it, because the fix lives in a seller-acquisition budget and a product ranking rule they do not own.

A CRO in a marketplace owns the sequencing across all three layers. That means deciding that the next quarter's seller acquisition spend goes to two categories instead of six, that buyer demand generation is deliberately throttled in a third category until supply catches up, and that the matching layer prioritizes response time over price because slow quotes are killing conversion. Those are the decisions that determine whether the revenue exists at all, and they cannot be made from inside a single lane.

The sequencing decision is the CRO's signature move, and it is genuinely uncomfortable. Turning down buyer demand in a category feels like turning down revenue, and a VP of Sales compensated on booked revenue will fight it every time — correctly, given their incentives. The CRO makes that call because they are measured on whether the category is still producing transactions two quarters later, not on this quarter's bookings alone.

Where the difference creates or leaks revenue

The clearest way to see the difference is to trace where money actually escapes a two-sided business, and then ask which role has the authority to stop it.

The empty-category leak. A qualified buyer arrives, searches their category, finds zero to two credible sellers, and leaves. In most marketplaces this buyer does not come back — the cost of a second disappointing search is higher than the cost of calling a known supplier directly. Every dollar of demand-generation spend that lands in a thin category is burned twice: once on the wasted acquisition cost, and once on the permanent loss of that buyer's future volume. Only a leader with a supply budget can fix this, either by pausing spend in that category or by funding the seller acquisition that fills it. A VP of Sales can report the pattern. They cannot redirect the money.

The one-and-done seller. A seller onboards, receives a trickle of low-intent inquiries, gets no closed business, and goes dormant. Dormancy is worse than never signing them, because their stale listing still appears in search results, produces slow or no responses, and teaches buyers that the marketplace is unreliable. The fix is either lead throttling (send fewer, better-matched inquiries to fewer sellers so each one converts) or an explicit supply-side service motion. Both are supply-side spend decisions.

The discount leak. This is the most direct incentive conflict between the two roles. A VP of Sales with authority over take rate will trade rate for volume, because rate is invisible in their comp plan and volume is not. Concede a few points to land a large buyer, and the concession does not stay contained — it becomes the reference price for the next negotiation, it leaks to sellers who wonder why some transactions carry lower fees, and it permanently resets the yield on that account's entire future volume. Rate concessions compound in a way one-time discounts on a software deal do not, because the marketplace re-earns its fee on every subsequent transaction. Giving up two points on a buyer who transacts monthly for three years is a very different decision from giving up two points once.

The mismatch leak. Buyers who transact once and never return usually did not have a bad experience with the marketplace — they had a mediocre experience with a specific seller the marketplace routed them to. That is a matching-quality failure, and it shows up in the sales team's numbers as "churn" with no attributable cause. Diagnosing it requires joining transaction data to seller-quality data to buyer-repeat behavior, which is a RevOps build, not a pipeline review.

The disintermediation leak. In B2B especially, a buyer and seller who meet on the platform and transact repeatedly have an obvious shared incentive to take the relationship off-platform and split the fee. This is the structural revenue risk unique to marketplaces, and the countermeasures are not sales activities: escrow and payment terms, dispute resolution, financing, compliance documentation, integrated logistics or inventory visibility — services worth paying for that only exist on-platform. Deciding which of those to build, and how to price them, is a monetization decision sitting squarely outside a sales function.

Where the difference creates revenue. The upside case is the mirror image. When one leader owns both sides, they can run deliberate liquidity plays: concentrate seller acquisition into one category, then open the demand taps into that same category thirty to sixty days later, so buyers arrive to a market that is actually stocked. They can price asymmetrically — subsidize the constrained side, monetize the abundant side — which is impossible if the person setting buyer pricing has no visibility into seller economics. And they can align both comp plans against the same repeat-transaction outcome instead of against two metrics that quietly fight each other.

Concrete numbers and benchmarks worth arguing about

Marketplace benchmarks vary enormously by category, average order value, and whether the transaction is repeat-consumable or one-off capital equipment. Treat every figure below as a structure for your own measurement rather than a target to import.

Take rate. B2B marketplace take rates generally sit well below consumer marketplace rates, because B2B order values are larger and seller margins are thinner. A distributor operating on a modest gross margin cannot absorb a double-digit fee on top; a services provider with high labor margin sometimes can. The practical test is simple: compare your take rate against the seller's fully loaded cost of acquiring that same customer through their own channel. If your fee is lower than their blended customer acquisition cost per order, you are cheaper than their sales team and they will stay. If it is higher, they will use you for incremental demand only and route their best relationships off-platform. Model this per category, because the answer changes completely between categories with different margin profiles.

Liquidity ratio. Track active buyers to active sellers per category per period, where "active" means transacted or was matched within the window — not registered. Registered-account ratios flatter every marketplace and predict nothing. The healthy ratio depends on how much volume a single seller can absorb: a category where each seller can serve many buyers tolerates a high buyer-to-seller ratio; a capacity-constrained category (a specialized fabricator with a finite queue) needs far more sellers per buyer. Set the target per category from seller capacity, not from a blanket rule.

Match rate and search-to-quote. The two diagnostic metrics a VP of Sales rarely watches. Match rate is the share of buyer searches or RFQs that produce at least one credible seller response. Search-to-quote is how long that takes. Both degrade silently as the marketplace grows into new categories, because new categories start thin by definition. A falling blended match rate with rising overall volume is the classic signal that growth is outrunning supply.

Repeat transaction rate. For a marketplace in a consumable or recurring-purchase category, the share of buyers who transact more than once within a defined window is the closest thing to a health score. One-and-done buyers mean the marketplace is functioning as a lead-generation vendor, and lead-gen businesses do not sustain marketplace-level valuations or marketplace-level take rates.

Ramp and lag. Buyer-side enterprise reps in B2B marketplaces ramp on a timeline comparable to enterprise SaaS reps — roughly two to three quarters to full productivity. Supply-side reps often ramp faster, because the seller pitch is more transactional. The number that matters more than either is the lag between onboarding supply in a category and seeing measurable demand-side conversion improvement there. Measure your own — it is typically a month or two, and it is the constant that governs how far ahead of demand your supply investment must run.

Cohort forecasting instead of pipeline forecasting. Pipeline-weighted forecasting understates marketplace revenue in liquid categories and wildly overstates it in thin ones, because it assumes every qualified opportunity has inventory behind it. The CRO's forecast should be built from category cohorts: active supply in the category, historical match rate at that supply level, historical repeat rate for buyers in that category, and observed average transaction value. This produces different — often uncomfortable — numbers than the sales forecast, and the gap between the two is usually the most informative number in the business.

Concentration risk. Track the share of gross merchandise value from your top handful of buyers and top handful of sellers. High concentration on either side means the marketplace is a managed brokerage wearing a platform's clothes, and it makes both disintermediation risk and forecast volatility much higher than the aggregate numbers suggest.

Pitfalls and how to avoid them

Hiring a CRO title for a VP of Sales job. The most common failure. A company hires a "CRO," then keeps supply acquisition under operations, pricing under finance, and matching under product. The CRO is now a VP of Sales with an inflated title and no lever that matters. Before hiring, write down which of these the role actually controls: seller acquisition budget, take-rate structure, both comp plans, matching business rules, and category go-to-market sequencing. If the answer is fewer than three, hire a VP of Sales, pay them well, and be honest about the scope.

Hiring a CRO too early. Below the liquidity threshold — before you know which categories work and why — the work is founder-led experimentation, not organizational design. A full-time CRO at that stage inherits a machine that does not exist yet and starts building process around a hypothesis. A fractional or advisory revenue leader is genuinely better here: the job is diagnosing which categories have real demand, designing the first take-rate test, and building the measurement layer. That is a few days a month of senior judgment, not a full-time executive.

Splitting the two sides under separate executives with separate targets. Supply under a COO with a seller-count target, demand under a VP of Sales with a bookings target. Both hit their numbers. The marketplace still stalls, because seller count grows in categories with no demand and bookings grow in categories with no supply. If the two sides must report separately, at minimum give both leaders a shared metric — matched transactions or repeat rate in target categories — with meaningful weight in both comp plans.

Compensating on the wrong side of the transaction. Buyer-side reps paid purely on first transaction value will chase one-off large deals and ignore repeat behavior. Seller-side reps paid on listings will onboard anyone with a pulse, filling the marketplace with sellers who never respond to an inquiry. Both plans are individually rational and collectively destructive. Fix by paying at least a meaningful portion of variable comp on outcomes that require the other side to succeed: repeat transactions, seller activation within a window, category-level match rate.

Letting the sales team hold pricing authority. Sales should absolutely inform pricing — they hear every objection first. But the structural decision (rate tiers, volume breaks, subscription versus transaction, promoted placement, which side gets subsidized) belongs with whoever is accountable for aggregate yield. The clean arrangement: sales gets a defined discretion band and an escalation path; anything structural goes to the CRO or, in a VP-of-Sales-only org, to the CEO or CFO explicitly.

Buying a SaaS RevOps stack for a marketplace. Standard CRM objects assume one customer and a linear pipeline. A marketplace needs both parties as first-class records, a transaction object joining them, category as a dimension on nearly every report, and cohort analysis by category and side. Teams that skip this end up reporting on the buyer pipeline because it is the only thing the CRM natively supports, which quietly makes the whole company think like a VP of Sales regardless of who is in the chair.

Confusing GMV growth with revenue health. GMV grows when you add large low-margin transactions, when you concede take rate for volume, and when a single buyer places one unusual order. Net revenue after any subsidies, credits, or promotional rate reductions is the honest number. Report both, always, and treat a widening gap between them as a warning rather than a growth story.

Ignoring the disintermediation curve. The buyer-seller pairs most likely to leave the platform are your best ones — highest volume, most established relationship, most fee paid. Track fee-per-relationship over time. A relationship whose transaction count is rising while its on-platform frequency is falling is leaving, and the countermeasure has to be built well before you notice.

Selection checklist for which role you actually need

Work through these in order. The answer usually becomes obvious by the third question.

Does one person need authority over both sides' budgets? If supply acquisition and demand generation are trading off against each other quarter to quarter — and in any marketplace under real capital constraint they are — you need a single owner. If supply is essentially solved (an open catalog, self-serve seller onboarding, abundant inventory) and the constraint is purely demand, a VP of Sales is the right hire and a CRO is expensive overhead.

Is take rate a live strategic question? If you are still testing rate structures, evaluating subscription versus transaction fees, or considering asymmetric pricing between sides, that work needs an executive owner with revenue accountability. If rate is settled and defended, the pricing argument for a CRO weakens considerably.

How many revenue channels exist? Direct sales plus self-serve plus channel partnerships plus platform integrations is a portfolio that needs allocation decisions across it. A single enterprise sales motion does not.

Where is the constraint? If your match rate is healthy and you simply cannot get enough qualified buyers into the funnel, that is a sales and marketing problem. Hire the best VP of Sales you can and give them the demand budget. If match rate is falling, categories are thin, or sellers are churning, the constraint is structural and a sales leader cannot reach it.

Is the org already split? If supply and demand teams exist under different executives with different metrics and are visibly fighting, you need a single owner above them more than you need a better closer.

Full-time or fractional? Below the liquidity threshold, or when the immediate work is diagnosis, category selection, comp design, and measurement architecture, a fractional revenue leader delivers most of the value at a fraction of the cost — and, importantly, does not create an executive seat you have to unwind if the model changes. Convert to full-time when the work shifts from designing the system to running a multi-team organization inside it: when both sides have real headcount, when category expansion is a repeatable process rather than an experiment, and when the weekly liquidity review has more attendees than a founder can personally manage.

One more framing that resolves most debates: in a marketplace, VP of Sales is not a smaller CRO. It is a role inside the CRO's scope. If you hire a VP of Sales and no CRO, someone still has to make the CRO-level decisions — usually the founder or CEO. That is a legitimate structure, and plenty of marketplaces run it well for years. The failure mode is not choosing one over the other; it is assuming the decisions disappear because nobody has the title.

Related questions

Can a VP of Sales grow into the CRO role at a marketplace?

Yes, but the gap is real: pricing elasticity, supply economics, and matching-quality analysis are not sales skills. The transition usually works when the VP has already run supply-side experiments and can defend a take-rate decision with data rather than deal anecdotes.

Should the supply team report to sales or operations?

To whoever owns aggregate revenue. Under operations, supply optimizes for seller count and service levels; under sales, for whatever the demand team needs this quarter. Under a CRO, it optimizes for matched transactions — the only metric that reflects both sides.

What single metric best separates the two roles?

Match rate. A VP of Sales is judged on conversion of matched demand; a CRO is judged on whether the match existed at all. If nobody in your leadership owns match rate, you have a VP of Sales structure regardless of titles.

Does this difference hold for a services marketplace versus a goods marketplace?

The structure holds; the numbers shift. Services marketplaces are capacity-constrained per seller, so they need denser supply per buyer and tolerate higher take rates against higher labor margin. Goods marketplaces face thinner margins and heavier disintermediation pressure.

How does a marketplace CRO work with product?

Closely and continuously. Search ranking, response-time penalties, review systems, and payment terms are all revenue levers built by product. The CRO brings the yield and liquidity data; product owns implementation. A VP of Sales rarely has standing in that conversation.

FAQ

Does a B2B marketplace need both a CRO and a VP of Sales?

Not simultaneously at every stage. Early on, a VP of Sales plus a founder making the structural calls is often enough. Once both sides carry real headcount and category sequencing becomes a recurring budget decision, a CRO with a VP of Sales reporting into them is the natural shape. Having both before that creates an expensive layer with no distinct decision rights.

Who owns marketplace liquidity?

The CRO, when the role is scoped properly. Liquidity is the product of supply acquisition, demand generation, and matching quality — three functions that no single sales leader controls. If nobody owns liquidity end to end, it defaults to the CEO, and it usually shows up as a surprise when growth stalls in a category everyone assumed was healthy.

How should compensation differ between the two roles?

A VP of Sales is weighted heavily toward quota attainment on closed demand-side revenue, with accelerators above target. A CRO's plan should reflect the whole engine — net revenue after subsidies, take-rate yield, repeat transaction rate, and category-level liquidity health — with a longer measurement window, because most CRO decisions pay off over quarters rather than weeks.

Which role owns pricing and take rate?

Structural pricing belongs to the CRO: rate tiers, volume breaks, subscription versus transaction, asymmetric subsidies between sides. The VP of Sales executes within a defined discretion band and feeds back what the field is hearing. In a VP-of-Sales-only org, structural pricing should sit explicitly with the CEO or CFO rather than defaulting to whoever is negotiating.

What does RevOps need to build differently for a marketplace?

Both parties as first-class records with a transaction object joining them, category as a dimension on nearly every report, cohort analysis by category and by side, and a liquidity dashboard showing active participants, match rate, and take-rate yield. Standard SaaS pipeline reporting is not merely incomplete here — it actively hides the supply-side failures that cause demand-side misses.

When is a fractional CRO better than a full-time hire?

Before the liquidity threshold, or when the immediate work is diagnosis and system design rather than running teams. Category selection, comp architecture, take-rate testing, and building the measurement layer are senior-judgment work measurable in days per month. Convert to full-time when execution scale — not design — becomes the bottleneck.

Sources

• https://www.nfx.com/post/19-marketplace-metrics
• https://a16z.com/marketplace-100/
• https://andrewchen.com/marketplace-liquidity/
• https://hbr.org/2016/04/pipelines-platforms-and-the-new-rules-of-strategy
• https://www.bvp.com/atlas/the-marketplace-100
• https://sloanreview.mit.edu/article/finding-the-platforms-in-your-pipes/
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/b2b-marketplaces-are-taking-off
• https://www.lennysnewsletter.com/p/how-to-kickstart-and-scale-a-marketplace

Related on PULSE

• [What does a fractional CRO actually do in the first 90 days?](/knowledge.html)
• [How do you set a take rate without killing seller supply?](/knowledge.html)
• [How should RevOps model a two-sided funnel in Salesforce?](/knowledge.html)
• [When should a founder hire a VP of Sales versus a CRO?](/knowledge.html)
• [How do you compensate supply-side and demand-side sales teams differently?](/knowledge.html)