refoundai/marketplace-fundamentals
Help users understand the core mechanics of marketplace businesses, from solving the cold start problem to maintaining quality and preventing platform leakage at scale.
npx skills add https://github.com/RefoundAI/lenny-skills --skill marketplace-fundamentals
Build, bootstrap, and scale a self-sustaining ecosystem of buyers and sellers.
Help the user with marketplace fundamentals using insights from 7 guests and posts across Lenny's Podcast and Newsletter.
Benjamin Lauzier: "If you don't have product market fit, and if you don't have a good enough growth strategy for at least one side of your marketplace, just forget about all this marketplace stuff. Focus on this core exchange of value, go deep with one side of the marketplace and see if you can rely on some crutch, some hack for the other side for time being."
Before focusing on complex economic ratios, ensure the core transaction provides enough value to both sides to sustain a growth strategy. Identify the most difficult side of the market to acquire and concentrate early resources there.
Ramesh Johari: "The moral is a marketplace business never starts as a marketplace business, because what we think of as a marketplace business is something which at scale is removing the friction of the two sides finding each other. But when you start, you don't have that scale."
Marketplaces struggle at low scale, so you must offer a high friction utility problem that provides value before critical mass is reached. This helps bootstrap the network by giving users a reason to join without existing liquidity.
Tim Holley: "Our sellers are incredibly astute business people. And if you had been making wedding dresses, and you know how to sew, and you've got material, and you've got a bit of time, making a mask is quite a simple task. And so we just saw this huge surge of demand, and then supply rising to meet it."
Maximize growth by helping your existing supply base apply their skills to new and high demand trends. Use platform signals to show sellers where emerging demand is going so they can adjust their offerings.
Benjamin Lauzier: "And I think on paper what makes a marketplace is pretty straightforward, it's two or more sides that are distinct from one another, and they provide value to each other, and then you have an intermediary trying to facilitate that exchange of value in the middle."
A true marketplace connects autonomous parties that provide mutual value. Verify that your two target audiences are distinct and provide independent value to each other through the platform interface.
Camille Hearst: "Which is why I actually think it's great that there's platforms who have stepped in and said, 'Hey, we see an opportunity. Let us insert ourselves in the center, let us aggregate, and let us do the hard work of pricing and payment and tax and finance and actually create value where it would be really hard for an individual person who's a creator to do all of this work and facilitate that connection.'"
Create unique value by aggregating supply and demand and then assuming the administrative or financial burdens that individuals cannot manage on their own. This central facilitation makes connections possible that were previously too difficult.
Dan Hockenmaier: "If you're building a SaaS business, you're a construction worker, you're building the product and the features and selling it, and it's this very linear thing. For a marketplace, you're like messing with this ecosystem that you don't actually really understand how it works."
Integrate software tools that provide linear and predictable value to participants. These tools help retain users and provide immediate utility while the unpredictable marketplace liquidity is still developing.
See references/artifacts.md for the full list with details.
For all 45 sourced insights from 7 guests, see references/guest-insights.md
Take refoundai/marketplace-fundamentals from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.