marketplace-liquidity
The marketplace-liquidity skill guides users through building and managing two-sided marketplace balance using frameworks from product leaders. Use it when addressing supply and demand mismatches, improving match rates, achieving critical mass, or diagnosing whether a marketplace is supply-constrained, demand-constrained, or facing matching problems. It establishes liquidity metrics like fill rates and recommends targeted interventions for geographic focus, supply acquisition, and matching quality.
git clone --depth 1 https://github.com/RefoundAI/lenny-skills /tmp/marketplace-liquidity && cp -r /tmp/marketplace-liquidity/skills/marketplace-liquidity ~/.claude/skills/marketplace-liquiditySKILL.md
# Marketplace Liquidity Management Help the user build and manage marketplace liquidity using frameworks from 4 product leaders. ## How to Help When the user asks for help with marketplace liquidity: 1. **Understand the marketplace type** - Ask about their supply/demand dynamics, how fragmented the market is, and whether needs are uniform or heterogeneous 2. **Diagnose the constraint** - Determine if they're supply-constrained, demand-constrained, or facing a matching problem 3. **Define liquidity metrics** - Help them establish clear measures of marketplace reliability and fill rates 4. **Design interventions** - Guide them on where to focus to improve liquidity (geographic focus, supply acquisition, demand generation, matching quality) ## Core Principles ### Liquidity is how marketplaces win Benjamin Lauzier: "Liquidity is how marketplaces win. It's this measure of your ability to match buyers and sellers efficiently." Focus on the core metric of how reliably you can connect supply with demand. This is the foundational metric that determines marketplace success or failure. ### Liquidity = reliability of the marketplace Dan Hockenmaier: "How reliable is the marketplace? If the consumer is looking for something or supplier is looking to sell something, how often can they do that thing they're trying to do?" Define liquidity as fill rate - the percentage of times buyers find what they want and sellers find buyers. Make this your number one metric. ### Marketplace management is whac-a-mole Ramesh Johari: "Marketplaces are a little bit like a game of whac-a-mole... a lot of marketplace management is moving attention and inventory around." Expect constant rebalancing between supply and demand across different segments and geographies. Build systems to reallocate attention and inventory dynamically. ### No supply without demand, no demand without supply Tim Holley: "If you've got supply without demand, then you don't really have a marketplace. If you've got demand and no supply to meet it, then you also don't have a marketplace." Watch for the "graduation problem" where successful sellers leave the platform. Use data to guide supply toward areas of unmet demand. ## Questions to Help Users - "How do you define liquidity for your marketplace? What's your fill rate?" - "Are you currently supply-constrained or demand-constrained? Does this vary by geography or category?" - "How fragmented are the needs in your marketplace - are they uniform or highly heterogeneous?" - "What happens when you add more supply? Does it immediately get absorbed by demand?" - "Are you seeing a 'graduation problem' where successful suppliers leave your platform?" ## Common Mistakes to Flag - **Growing both sides equally** - Usually one side is the constraint. Focus resources on the bottleneck - **Ignoring geographic/category fragmentation** - National liquidity metrics can hide severe local imbalances - **Not measuring fill rate** - Without a clear liquidity metric, you can't manage toward it - **Over-expanding before reaching local density** - It's better to be highly liquid in one market than illiquid across many ## Deep Dive For all 4 insights from 4 guests, see `references/guest-insights.md` ## Related Skills - Measuring Product-Market Fit - Designing Growth Loops - Pricing Strategy - Retention & Engagement
Help users create and run AI evaluations. Use when someone is building evals for LLM products, measuring model quality, creating test cases, designing rubrics, or trying to systematically measure AI output quality.
Help users define AI product strategy. Use when someone is building an AI product, deciding where to apply AI in their product, planning an AI roadmap, evaluating build vs buy for AI capabilities, or figuring out how to integrate AI into existing products.
Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
Help users get promoted at work. Use when someone is preparing for a promotion conversation, building their case for advancement, trying to understand what's blocking their promotion, or figuring out how to get to the next level in their career.
Help users build and scale their sales organization. Use when someone is hiring their first salespeople, deciding when to bring on sales leadership, structuring sales compensation, or transitioning from founder-led sales.
Help users build and maintain strong team culture. Use when someone is defining team values, creating psychological safety, onboarding to a new team, navigating cultural change, or building distributed team norms.