Help users identify unique distribution advantages and master the lifecycle of acquisition channels to build a sustainable engine for growth and retention.
日本語の概要は準備中です。原文の説明を表示しています。
Help users define precise liquidity metrics, set competitive take rates based on value delivery, and manage the delicate balance between supply-side health and platform profitability.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Optimize the balance between transaction reliability and monetization to build a defensible ecosystem.
Help the user with marketplace liquidity and take rates using insights from 6 guests and posts across Lenny's Podcast and Newsletter.
Dan Hockenmaier: "For a marketplace, you're like messing with this ecosystem that you don't actually really understand how it works. And sometimes you might do something over here which drives this long-term effect two months later, and then you're going to be pulling your hair out two months later trying to figure out what you did over here that made that thing happen."
Marketplace health depends on complex interactions where small changes cause delayed ripple effects. Leaders should use a light touch and monitor downstream impacts for months after making changes.
From "Choosing a take rate": "Differences in take rates are primarily driven by three factors: (1) whether you can drive new demand, (2) how much convenience you provide the seller, and (3) the level of competition in the market."
Your fee should reflect the new demand you generate and the operational ease you provide. Start with a 10% baseline for platforms and 20% for marketplaces, then adjust based on product value.
From "Choosing a take rate": "The most dangerous strategy for any platform company is to price too high – to charge a greedy and overzealous rake that could serve to undermine the whole point of having a platform in the first place."
High take rates create friction and leave room for competitors to undercut you. Lower rates can secure a long-term edge in winner-take-all markets by reducing barriers to transaction.
From "The most important marketplace metrics to track": "Since there’s so much confusion around this term, I prefer to avoid using it altogether when we’re describing operational metrics, and instead get specific about what I mean (e.g. fill rate, supply quantity, supply success, etc.). If you do use it, explain what you actually mean. Don’t assume anyone knows what you’re talking about when you say ‘liquidity.’"
The term liquidity is too ambiguous for daily operations. Replace it with specific metrics like fill rate or success rate to ensure the team is aligned on what a successful match looks like.
From "Why marketplaces fail": "The most fundamental job of a marketplace is to efficiently match supply with demand. If you can’t do this reliably (i.e. fill-rate) or quickly (i.e. time-to-match), you’ll fail."
Users will abandon a platform for more reliable alternatives if they experience low fill rates or slow matching times. Prioritize providing high certainty of a match over broad expansion.
From "The inside story of Facebook Marketplace": "Once we had the tab within the Facebook app to drive buyer engagement, we settled on the key metric of weekly buyer retention."
Focusing on demand-side retention ensures the marketplace provides repeatable value rather than temporary growth. Set weekly buyer retention as your north star metric for product-market fit.
From "Choosing a take rate": "Companies like Upwork, Patreon, StockX, Doordash, Uber Eats, and Grubhub take advantage of The Take Rate Formula by offering different take rates for more or less Convenience and Demand."
Tiered pricing allows you to map different take rates to the specific level of service each seller needs. Use volume-based tiers to reward your most active participants while capturing value from others.
See references/artifacts.md for the full list with details.
For all 17 sourced insights from 6 guests, see references/guest-insights.md
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Help users identify unique distribution advantages and master the lifecycle of acquisition channels to build a sustainable engine for growth and retention.
日本語の概要は準備中です。原文の説明を表示しています。
Help users build functional product prototypes from natural language or visual mocks using AI coding tools. This skill enables product leaders to bypass engineering bottlenecks and validate ideas through hands-on building.
日本語の概要は準備中です。原文の説明を表示しています。
Help users build robust infrastructure for measuring, monitoring, and iterating on AI product performance using human, code-based, and LLM-as-a-judge methodologies.
日本語の概要は準備中です。原文の説明を表示しています。
Help users interact with probabilistic models by designing interfaces that manage fluidity, intent, and agency while maintaining trust and control.
日本語の概要は準備中です。原文の説明を表示しています。
Help users decide where to apply AI effectively, manage the transition from deterministic to probabilistic software, and build long-term defensibility through verticalization and proprietary data.
日本語の概要は準備中です。原文の説明を表示しています。
Help users convert massive volumes of qualitative and quantitative feedback into high-confidence product decisions through rigorous synthesis and internal immersion.
日本語の概要は準備中です。原文の説明を表示しています。