There's a specific trajectory in some vertical SaaS companies: you build workflow software that connects two sides of an industry transaction — a buyer and a supplier, a professional and a service provider, a business and its vendors. At some point, the workflow software is facilitating so much transaction activity that it makes more sense to take a percentage of that transaction value than to charge a software subscription.
This is the SaaS-to-marketplace evolution, and it happens most reliably in verticals where:
Transactions are frequent and standardized. Construction materials procurement, staffing platforms, insurance underwriting, freight brokerage — these are transaction-heavy workflows where the software naturally sits in the middle of economic exchange.
Both sides of the transaction benefit from network effects. The more suppliers on your platform, the more valuable it is for buyers, and vice versa. SaaS subscriptions don't capture this value; marketplace take rates do.
The transaction value is large enough to sustain take rates. A 1-3% take rate is meaningful on a $100K transaction. It's not meaningful on a $500 transaction.
The transition challenges are significant:
Monetization model transition. Moving from predictable SaaS subscription revenue to variable transaction-based revenue changes your revenue predictability, your COGS structure, and your investor narrative.
Supply side recruitment. Building a two-sided marketplace requires acquiring suppliers at scale. This is a different go-to-market problem from selling SaaS subscriptions, often requiring different team skills.
Regulatory considerations. Many transaction-heavy verticals (financial services, insurance, healthcare) have specific regulations about marketplace operators that SaaS companies don't face.
The companies that make this transition successfully are usually the ones that let marketplace features emerge organically from customer behavior rather than forcing the transition as a strategic pivot. Watch for the marketplace signals in your usage data. They're there if you look.