Winston Francois develops the growth product function for two-sided marketplaces: one prioritization framework that evaluates supply-side and demand-side work together, growth loop metrics that measure real liquidity rather than vanity conversion rates, and a cross-functional cadence that keeps supply ops, demand marketing, and trust and safety moving in the same direction.

The Challenge

Supply and demand roadmaps compete for the same sprint capacity

A marketplace growth PM does not manage one backlog, they manage two: seller tooling, listing quality, and payout speed on the supply side, and search, discovery, and checkout on the demand side. Both roadmaps report to the same engineering team and the same two-week sprint. When the team defaults to whichever roadmap has the loudest internal advocate, the platform ends up over-invested in one side and starving the other of the product work it needs to grow.

Prioritization frameworks built for one side fail on two-sided platforms

RICE and ICE scoring were built to rank features against one user's activation and retention curve. On a marketplace, a feature that helps demand can quietly hurt supply, faster checkout that compresses seller margins, or algorithmic ranking changes that boost buyer relevance while tanking a segment of sellers' visibility. A growth PM who scores features on reach and impact alone, without a supply-demand tradeoff lens, ships work that grows one side of the ledger while eroding the other.

Liquidity, match rate, and repeat transaction rate are measured in silos, when they are tracked at all

Most growth teams inherit SaaS-style dashboards built around signup funnels and feature adoption. Those dashboards do not surface whether supply actually meets demand in a given category, how often a search or request results in a completed match, or whether transacting users come back for a second and third transaction. Without a single owner accountable for the liquidity number, teams optimize local metrics, like listing volume or app downloads, that can rise while the core exchange the platform depends on gets worse.

Trust and safety friction can conflict with growth targets

Verification steps, identity checks, and review holds exist to protect the marketplace, but every one of them adds friction to onboarding and to the transaction path. A growth PM who is not directly coordinating with trust and safety will either ship growth experiments that get quietly vetoed after the fact, or inherit safety requirements late in a sprint that force a redesign of a feature that was already scoped and estimated.

How We Support You

We begin by mapping your real growth loop, rather than the version reflected in the org chart.

Next, we create one prioritization framework that scores each candidate feature across both sides of the platform simultaneously, not only the side that asked for it.

We then establish the growth loop metrics as a shared instrument panel: liquidity by category, match rate from search or request through completed transaction, and repeat transaction rate by cohort.

Cross-functional coordination becomes part of the operating cadence instead of being left to hallway conversations.

Execution happens through focused, alternating sprints: a supply-constrained category receives targeted product work for a set window, after which the team moves to demand-side experiments that make the added supply worthwhile. We do not treat supply and demand work as two permanently separate tracks, because marketplace growth happens only when both sides advance together.

Measurement completes the loop in every cycle. We report on the liquidity, match rate, and repeat transaction numbers established at the engagement's outset and identify the specific product changes that affected them. The next cycle's roadmap decisions come from that evidence, not from whichever function made the loudest case in the previous planning meeting.

What we deliver

A single supply-demand prioritization framework that scores every feature on both sides of the platform, replacing separate single-sided roadmaps
Growth loop instrumentation covering liquidity by category, match rate, and repeat transaction rate as the shared scoreboard for the product team
A cross-functional planning cadence that seats supply ops, demand marketing, trust and safety, and product together before features ship, not after
A category-by-category view of where the growth loop is currently constrained, so sprint capacity gets allocated to the actual bottleneck
An engineering sprint model that alternates and combines supply-side and demand-side work instead of running two permanently separate roadmaps
A reporting model that ties every shipped feature back to its effect on liquidity, match rate, or repeat transaction rate

A marketplace growth PM's real role is not simply shipping features. It is choosing whose problem gets solved this sprint, supply's or demand's, and demonstrating that the decision improved liquidity rather than only one side's local metrics.

Our Methodology

Our 90-day approach starts with instrumenting the growth loop before changing the roadmap. We extract liquidity, match rate, and repeat transaction rate by category from existing data, interview supply ops, demand marketing, and trust and safety separately to understand where each function thinks the platform is constrained, and compare those perspectives with what the data actually reveals. This nearly always uncovers at least one category where the team has been creating demand-side features despite a supply shortage, or the reverse.

Once the constraint is clear, we create the shared prioritization framework and lead the first cross-functional planning cycle, scoring the current backlog across both platform sides and re-ranking it with the people responsible for supply, demand, and trust and safety. Roadmap disputes that were previously settled by seniority or volume are instead resolved through evidence.

By day 90, the team has a repeatable planning cadence in place, shared growth loop metrics are live across functions, and the first round of prioritized work has shipped against the identified constraint. We transfer a framework the team can operate independently, together with a clear perspective on which category or growth loop stage should receive the next quarter of product capacity.

Our Working Process

Days 1-30 center on assessment and instrumentation: we map the complete growth loop, pull or create category-level dashboards for liquidity, match rate, and repeat transaction, and interview supply ops, demand marketing, and trust and safety to determine where each function sees growth being blocked. This phase ends with one shared view of the platform's true constraint.

Days 31-60 center on the operating model: we create the supply-demand prioritization framework, score the current backlog again using it, and establish the recurring cross-functional planning cadence. The first prioritized sprint ships against the constraint found in phase one, with trust and safety participating in the design before building begins rather than afterward.

Days 61-90 center on measurement and handoff: we report how the shipped work affected liquidity, match rate, and repeat transaction rate by category, refine the framework based on the data, and transfer the cadence and dashboards to your team for independent operation. If the team wants another perspective on the reprioritized backlog, we remain available for the following planning cycle.

The core team consists of a growth product strategist responsible for the framework and metrics, supported by an analytics lead who creates and maintains the liquidity and match rate instrumentation. Both collaborate directly with your engineering, supply ops, demand marketing, and trust and safety leads instead of working as an external advisory layer. The cadence features a weekly cross-functional planning sync plus a monthly leadership liquidity readout.

A single prioritization framework replacing separately run supply-side and demand-side roadmaps
Live liquidity, match rate, and repeat transaction dashboards by category, owned jointly across functions
A cross-functional planning cadence that resolves supply-demand tradeoffs before features ship
Trust and safety involved as a design input rather than a late-stage blocker
A documented view of which growth loop stage deserves the next quarter of product capacity

If your b2b & b2c marketplaces company needs growth product management leadership, we should talk.

Expand your marketing team output with our experts

Let us take a custom approach to your growth goals by assembling and leading the best-in-class marketing team to support your next stage.

Frequently asked questions

How does marketplace growth product management differ from growth PM at a single-sided SaaS company?

A SaaS growth PM improves one user's journey from signup through activation and retention, with every feature scored against that single curve. A marketplace growth PM must evaluate each feature for two distinct users, supply and demand, whose interests may not align. The true measure of success is liquidity, whether supply and demand actually connect and transact, rather than signup or activation figures for either side by itself.

When the team can build only one, how do you choose between a supply-side and demand-side feature?

We evaluate both candidates with one framework: how each affects liquidity, match rate, and repeat transaction rate within the category it addresses, rather than only the metrics already monitored by the requesting team. When thin supply is the category's true platform constraint, a demand-side feature is deprioritized even when it is simpler to build, because adding demand to limited supply does not improve liquidity; it only means more buyers find nothing available.

Who should be responsible for the liquidity, match rate, and repeat transaction numbers?

A single growth product function should own all three through a shared scoreboard, rather than dividing them between separate supply and demand teams. Splitting ownership causes each side to optimize what it controls, such as listing volume for supply or signup volume for demand, while no one remains accountable for whether both sides are actually connecting and transacting.

How can trust and safety be incorporated into the growth product roadmap without slowing everything down?

Trust and safety participates in the planning cadence from the beginning, allowing verification and safety requirements to be incorporated during feature scoping instead of added after engineering has estimated the work. This approach does not remove friction from onboarding or transactions, but it avoids the late-stage rework caused by safety requirements emerging after a sprint has already been committed.

How soon will we see the growth loop metrics begin to improve?

Instrumentation and the initial cross-functional planning cycle are generally live within 60 days, and the first prioritized sprint ships against the identified constraint by day 90. Significant gains in liquidity and repeat transaction rate typically require one to two more quarters because those metrics capture genuine behavior change across both platform sides, not merely the release of a feature.

What is the cost of a Winston Francois marketplace growth product engagement?

Most marketplace growth product engagements cost $15K-$35K monthly, based on the number of categories and platform sides included and the amount of dashboard and instrumentation work required beyond the prioritization framework and planning cadence. We define the scope after the initial growth loop assessment, ensuring the cost aligns with the categories that truly require attention.

What marketplace size is best suited to this service?

This engagement is designed for Series A through growth-stage marketplaces, approximately $5M to $100M in ARR or GMV, that already have platform supply and demand but do not have one framework for determining what the product team should build next. If neither side of the platform has launched yet, a marketplace growth product engagement is too early; you need a launch strategy first.

Growth Product Management for B2B & B2C Marketplaces