There is a stage in a marketplace company that nobody has a good name for. The product exists. Real people use it. The founder is no longer the only person who touches the roadmap, and there is now an engineering team, or an agency, or two contractors and a Notion board. And the decisions have quietly become bigger than anyone currently has time to make properly.
You can spot it by a particular symptom. The same strategic argument keeps coming back. Should we build the supplier dashboard or fix buyer onboarding? You discuss it in January, decide something, and find yourselves discussing it again in March as though the first conversation never happened. Nothing is being decided, exactly. Things are being deferred with confidence.
The Gap Nobody Names
Founders in this position are usually offered two options, and neither one fits.
Option one is a consultant. Someone senior comes in, spends a few weeks understanding the business, and leaves you with a document. The document is often genuinely good. The problem is that a document does not make Tuesday's decision, and Tuesday's decision is the one you keep getting wrong. Six weeks later the deck is in a folder and you are back to relitigating the supplier dashboard.
Option two is a full-time hire. A head of product, or a CPO if you are being ambitious about titles. This is the right answer eventually and the wrong answer now, because a senior marketplace product person costs what they cost, and at your revenue you would be spending a meaningful chunk of runway on someone whose job for the first two quarters is roughly two days of work a week. Founders know this, which is why the role sits unfilled on the org chart for a year.
Between those two there is a third thing, and it is badly marketed, which is why most founders have not seriously considered it. Someone senior who owns the roadmap, sits in your standups, and makes the call, for a few days a month.
What Breaks Without Product Leadership
The damage from this gap is not dramatic. Nothing explodes. It accumulates, which is worse, because there is never a moment where anyone says the problem out loud.
The backlog stops being a plan and becomes a graveyard. Nobody prunes it, because pruning requires someone with the authority to say a thing will never be built, and no one has quite got that authority. Engineers start making product decisions by default, not because they want to but because someone has to decide what the empty state says and the founder is in a fundraising meeting. Those decisions are usually reasonable in isolation and incoherent in aggregate.
And the marketplace-specific version of this is sharper than the general one. Two-sided platforms force a constant sequencing question that single-sided products never face: which side gets this quarter. Get that wrong twice in a row and you have a supplier base that has churned while you were polishing the buyer experience, or a beautiful supplier tool that nobody uses because no buyers arrived. That is a strategy question wearing the costume of a roadmap question, and it needs someone whose job is to hold both sides in their head at once.
“A consultant tells you which side to build for. A fractional product lead is still there in six weeks when the answer turns out to have been half right.”Darren Cody, Marketplace Studio
What a Fractional Marketplace PM Actually Does
The word fractional describes the time, not the seniority and not the commitment. A fractional marketplace product manager is a senior product person who works a defined number of days a month, ongoing, with real ownership. In practice the work tends to be:
- Owning the roadmap, including the unpopular half of that job, which is deciding what comes off it
- Making the supply-versus-demand sequencing call each quarter, and being accountable for it
- Writing the specs that engineering actually builds from, so those decisions stop happening by accident at 4pm on a Friday
- Deciding which metrics the team steers by, and killing the ones that only ever go up
- Sitting between the founder and the build team as the person who translates in both directions
That last one matters more than it sounds. A great deal of what goes wrong in early marketplace companies is a translation failure. The founder knows the market intimately and describes what they want in market language. The engineers hear a feature request. Something gets built that technically matches the request and misses the intent entirely. Someone who speaks both languages fluently removes an enormous amount of waste, and that person does not need to be there five days a week.
Fractional, Agency, or Full-Time
These three get compared on cost, which is the least interesting axis. The useful comparison is who is accountable when the thing that shipped does not work.
| Consultant | Fractional | Full-time | |
|---|---|---|---|
| Owns the outcome | No | Yes | Yes |
| Present for the next decision | No | Yes | Yes |
| Ramp-up cost | Low | Low | High |
| Cost per month | Low, one-off | Moderate, ongoing | High, ongoing |
| Right when | One big question | Continuous questions | Continuous, full days |
Agencies sit slightly outside this table because they are usually buying you delivery capacity rather than judgement. That is a genuinely useful thing to buy, and plenty of marketplaces are best served by a build team plus a fractional product lead who decides what that team builds. What does not work is buying delivery capacity and hoping product leadership emerges from it. It does not, and the resulting product is a faithful implementation of whatever the founder said in the last meeting.
When Fractional Is the Wrong Answer
I would rather talk a founder out of this than into it, so here are the cases where it does not work.
If you have not launched and have not validated the idea, you do not need a fractional product lead. You need to talk to fifteen people on each side of your market and find out whether the thing you are imagining is a business. Hiring product leadership to run a roadmap for an unvalidated idea produces a very well-managed march in the wrong direction.
If the founder does not actually want to hand over decisions, fractional will fail, and it will fail expensively and slowly. Some founders are product people and should stay in the seat; what they need is capacity underneath them, not a peer above. That is a fine answer, and it is worth being honest about early rather than discovering it in month four.
And if the product questions genuinely require full days of continuous presence, because you have three squads and a live platform doing real volume, fractional is a stopgap you will outgrow in a quarter. Use it while you run the search for the permanent hire, not instead of running it.
How to Hire One Without Getting Burned
The failure mode in this market is buying advice dressed as ownership. Someone charges you a monthly retainer and delivers what is functionally a recurring consulting call. Three things protect you from that.
Ask what they will own, not what they will advise on. The answer should include artifacts with their name on them. A roadmap they maintain. Specs they write. A metric they are accountable for moving. If every answer is a verb like guide, support, or align, you are buying a consultant with a subscription.
Ask what they have shut down. Anyone can list features they shipped. A product leader who has never killed anything has never actually held the authority, and in a marketplace where scope creep is the default failure mode, the killing is most of the value.
Ask about the two-sided sequencing decision specifically. Not in the abstract. Ask about a real quarter where they had to choose between supply and demand, what they chose, and what it cost. Product people from single-sided companies are often excellent and still get this wrong for a year, because the intuitions do not transfer and nothing in a SaaS background prepares you for a supplier base that quietly leaves.
For what it is worth, this is the shape of engagement I spend most of my own time in. We run it as our fractional team service, usually alongside founders who have a live marketplace and a build capability but no one holding the product line. If you are earlier than that, or you are not sure which of the three options you actually need, marketplace consulting is the cheaper first conversation, and we will tell you honestly if the answer is that you do not need us yet.
