Marketplace and SaaS Hybrids Explained

By Brian Tr · Updated Oct 7, 2026

Most marketplaces start with a simple bargain: we find you customers, and we take a cut when you sell. Most software companies start with a different one: you pay us a recurring fee, and we make your work easier. A hybrid does both. It sells software to one side of a market and also runs the place where the two sides transact.

That sounds like a strict upgrade, two revenue engines instead of one. In practice it's a harder business to run, because the two engines want different things. Software wants a focused customer, a clean product, and predictable renewals. A marketplace wants breadth, liquidity, and volume. This article defines the two common hybrid shapes, explains the strategic logic behind each, shows how the revenue mix and the metrics change, and lists the risks that come with trying to be both.

Two shapes, often confused

The word "hybrid" covers two different starting points. The distinction matters because the strategy, the early metrics, and the failure modes differ.

The SaaS-enabled marketplace. Point Nine's overview of the category, written by Savina van der Straten in October 2016, defines it as a business that combines a marketplace component connecting two or more parties with a SaaS component offering software features. The test it applies is that the software must be usable as standalone software. A booking calendar that only works inside the marketplace doesn't count. A booking calendar a provider could use even with no marketplace listing does. The essay says these companies can monetize the transaction through a fee or the software through a subscription.

The marketplace that adds software. Here the marketplace comes first, and software arrives later to serve sellers (and sometimes buyers) better. Point Nine's March 2019 essay by Julia Morrongiello, Come for the Network, Stay for the Tool, argues for this reverse order: build the marketplace first, then introduce SaaS tools once scale exists, which in her view can reduce churn and increase loyalty. It names Docplanner (which started as a doctor-booking marketplace), Xeneta, Hired, Upwork, and Metalshub among its examples.

These aren't always clean categories. A company can start with one shape and drift into the other, and a few sit in between. But asking "which came first?" is a quick way to work out which problems you're likely to have.

The strategic logic

Why would anyone take on two business models at once? There are four recurring arguments, and each is worth testing against your own market rather than assuming.

Software as a wedge for supply

The classic statement comes from Chris Dixon's January 2015 essay, Come for the tool, stay for the network. He describes a popular strategy for bootstrapping networks: initially attract users with a single-player tool, then over time get them to participate in a network. In his words, the tool helps reach initial critical mass, while the network creates the long-term value and defensibility. His examples are Delicious and Instagram, and he adds that single-player tools are like kindling.

For marketplaces, the tool is usually built for the supply side. A provider who runs scheduling, invoicing, or inventory in your software has a reason to be on your platform before a single buyer arrives. That's one way out of the cold-start trap known as the chicken-and-egg problem, and our reference on single-player mode goes deeper on when it works.

Software to deepen the relationship with sellers

The reverse order has its own case. Once a marketplace has traffic and sellers, tools that run a seller's daily operations make leaving more expensive. The 2019 Point Nine essay says SaaS tools can reduce churn and increase customer loyalty, and calls the resulting product uniquely defensible. That's an argument, not a measured result, so treat it as a hypothesis to test with your own retention cohorts.

Software to reduce leakage

Disintermediation happens when a buyer and seller meet on the platform and then transact off it. A tool the seller uses to run their business changes that calculation, because the seller's schedule, client records, or payments already live inside your product. Taking a booking offline now means doing extra work. The mechanics of leakage and the counter-levers are in marketplace disintermediation, and software is one of several levers there, not a cure.

Data and a second revenue line

A tool that touches the seller's workflow generates data a pure marketplace never sees: how busy a provider is, what they charge outside the platform, how repeat customers behave. That data can improve matching and pricing. And the subscription gives a revenue stream that doesn't depend entirely on whether this week's transactions happen. Both are plausible benefits, and both depend on execution.

How the revenue mix works

The hybrid's income has two kinds of lines, and they behave differently.

Filings from public companies show what the mixes look like in practice. None of the companies below is a pure hybrid, but they show how revenue lines are reported.

Etsy is a marketplace first. Its FY2025 10-K says its revenue is a mix of marketplace activities and optional services provided primarily to sellers. Marketplace revenue, mainly transaction, payments processing, and listing fees, was 69.6% of the total in 2025. Services revenue, mainly on-site advertising and shipping labels, was 30.4%, up from 28.0% in 2024. Etsy sells services to sellers, though the filing doesn't describe them as standalone SaaS. Our piece on value-added services covers that wider category.

Shopify sits on the software side, and it isn't a marketplace. Its FY2025 10-K says it has two revenue components: a recurring subscription component it calls subscription solutions, and a merchant success-based component it calls merchant solutions. Subscription solutions accounted for 24% of total revenues in 2025, down from 26% in 2024. Merchant solutions come mostly from payment processing and currency conversion fees, plus lending, referral fees, shipping labels, and advertising. It's a useful picture of the other end of the spectrum: a software company whose revenue leans on activity-linked fees.

Put the two side by side and you see a pattern. A marketplace that adds services grows its non-transaction share. A software company that adds payments and fees grows its transaction-linked share. The hybrid is the zone in the middle where both lines matter, and where the mix itself is a strategic choice. Measuring a hybrid means reading ARR next to GMV and take rate; the transaction side of that stack is laid out in marketplace metrics.

How the metrics change

A pure marketplace is judged on volume and take rate. A pure SaaS company is judged on recurring revenue and retention. A hybrid has to hold both sets, and they don't merge neatly.

Marketplace metrics: gross merchandise volume (GMV), take rate, liquidity, and repeat usage.

Software metrics: ARR and MRR, net revenue retention, logo churn, and seat or account expansion.

A few rules keep the reporting honest.

1. Report the two streams separately. Blending subscription revenue and transaction revenue into one growth number hides which engine is working. Transaction revenue moves with market conditions. Subscription revenue moves with renewals.
2. Don't count transaction fees as ARR. ARR is built on contracted recurring fees. Fees tied to volume fluctuate, so labelling them recurring overstates how predictable they are. If you want a combined number, define it openly and name it something else.
3. Compare take rate with and without the subscription. If sellers pay a subscription and a fee, the effective cost to a seller is the sum. Total seller payments divided by GMV shows the real burden, and it's the figure sellers feel.
4. Track the software cohort separately. Subscribers and non-subscribers behave differently. Compare their GMV, retention, and leakage to see whether the software actually changes behavior.
5. Watch attach rate. In the reverse model, what share of active sellers adopt the tools? A low attach rate means the tools aren't earning their development cost.

The risks of being both

Two models in one company create friction that neither model has alone.

Focus split

Software teams and marketplace teams optimize for different customers and cycles. Roadmap decisions that help the tool (deep supplier workflows) can compete with decisions that help the network (buyer experience, search, liquidity). Without a clear rule about which side wins in a conflict, resources drift toward whichever is louder.

Channel conflict

If the software is usable on its own, some customers will use it and never list on the marketplace. That's the point of the wedge, but it also means your tool can become a way for sellers to run their own direct business, with no take rate attached. And in the reverse model, adding seller tools can look like competing with the independent software vendors that sellers already use. Decide in advance whether that's an intended trade or an accident.

Pricing complexity

Sellers see a subscription fee and a transaction fee together. If the two aren't designed as a pair, sellers can feel charged twice for the same value. A common design question is whether the subscription buys down the transaction fee, or whether the two are independent. Whichever you choose, the pricing page should make the total cost easy to calculate.

The wedge may never turn into a network

In the SaaS-first model, the tool can succeed as software and still fail to become a marketplace. Some vertical software businesses are happy as software businesses. Others find that the demand side is much harder to acquire than the supply side was. If the second step never works, you've built a SaaS company with a marketplace-shaped hole in the strategy.

A crowded software category

The 2019 Point Nine essay calls the SaaS landscape ever-competitive and says the SaaS-first route is easier said than done. A marketplace layer on top of a tool that's merely adequate can't rescue it. The software has to hold up against specialist products on its own.

When the hybrid fits

The model tends to fit when three conditions hold. First, the supply side runs a real, repeatable workflow that software can improve, such as scheduling, quoting, inventory, or compliance. Second, the market is fragmented enough that suppliers lack good tools today, which is the logic of vertical market strategy. Third, the demand side can be reached once supply is in place, so the network step is realistic.

It fits poorly where supply is commoditized and transactional, where sellers have no ongoing workflow to manage, or where buyers already have a dominant place to search. In those markets, the software has nothing to attach to, and the marketplace has no reason to give it away.

A short checklist before committing:

• Can the tool stand alone and justify its price?
• Does the tool create data or switching costs the marketplace alone wouldn't?
• Will subscribers also transact on the platform, or just use the software?
• Is the combined seller cost (subscription plus fee) clear and fair?
• Can one team own both roadmaps without starving either?

Key Facts: Marketplace and SaaS Hybrids

• Point Nine defines a SaaS-enabled marketplace as a marketplace component plus a SaaS component that is usable as standalone software (Savina van der Straten, October 2016).
• Chris Dixon's January 2015 essay describes attracting users with a single-player tool, then getting them into a network, as a way to bootstrap.
• Point Nine's March 2019 essay argues for the reverse sequence: marketplace first, tools later.
• Etsy's FY2025 10-K shows 69.6% marketplace revenue and 30.4% services revenue for 2025.
• Shopify's FY2025 10-K says subscription solutions were 24% of total revenues in 2025, with the rest from merchant success-based solutions.
• ARR should include only contracted recurring fees. Volume-linked transaction fees belong in a separate line.

Related Reading

• What Is Single-Player Mode?
• Marketplace Revenue Models
• Marketplace Take Rate
• Marketplace Disintermediation
• Marketplace Value-Added Services
• Vertical Market Strategy