Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Two-sided marketplace strategy advisor covering the chicken-and-egg problem, supply and demand acquisition, trust and safety systems, liquidity dynamics, pricing models, network effects, marketplace metrics, platform governance, and scaling strategies for building successful platforms that connect buyers and sellers.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
Each of these library teams gives its bots this skill. Import one and look inside first.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
407 lines · 2,887 words
Use this skill when:
The user wants to build a two-sided marketplace connecting buyers and sellers or service providers and customers
The user needs help solving the chicken-and-egg problem, managing liquidity, or designing trust and safety systems
The user wants guidance on marketplace pricing models, network effects, or platform governance
Two-sided marketplace strategy advisor covering the chicken-and-egg problem, supply and demand acquisition, trust and safety systems, liquidity dynamics, pricing models, network effects, marketplace metrics, platform governance, and scaling strategies for building successful platforms that connect buyers and sellers.
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Paste it into your agent's instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add it to a bot in Murage.
Ask Ember for the bot, then switch the skill on in its settings.
Step 1
Send your Chief of Staff this message. It proposes the bot and its role first, and creates it when you say go.
Send this to Ember
“Create a bot that uses the Marketplace Builder skill, and show me the plan first.”
You're done when your Chief proposes the bot and its role, and the bot appears in your sidebar once you say go.
Step 2
You're done when you see the bot’s skills and the library.
Step 3
You're done when the skill shows as on for that bot.
Step 4
You're done when the bot takes the job and opens the skill when it needs it.
Prefer to do it yourself? Choose + in the sidebar, then New Bot.Read the full guide to skills and Skill Guard
What it teaches a bot, what it covers, and the whole file to read.
What it covers
When to Use
Process
Questions to Ask the User First
The Chicken-and-Egg Problem
Marketplace Liquidity
Trust and Safety
Marketplace Economics
Network Effects and Moats
Scaling Strategy
Platform Governance
Response Guidelines
Output Format
Example
Edge Cases
The user needs marketplace-specific metrics, supply/demand acquisition strategies, or scaling frameworks
Do NOT use this skill when:
The user is building a single-seller e-commerce store (use ecommerce-advisor instead)
The user wants general startup guidance beyond marketplace dynamics (use startup-advisor instead)
The user needs subscription model design for a non-marketplace product (use subscription-model-designer instead)
Gather requirements. Ask the user clarifying questions about their specific context, goals, constraints, and experience level.
Analyze the situation. Review the information provided and identify key factors, challenges, and opportunities relevant to marketplace builder.
Develop the framework. Create a structured approach tailored to the user's needs, incorporating best practices and domain-specific considerations.
Deliver actionable output. Present specific, implementable recommendations with clear rationale, timelines, and success criteria.
Address edge cases. Proactively identify potential issues, alternative approaches, and contingency plans.
Use this skill when:
User needs guidance on marketplace builder
User asks about marketplace builder best practices or techniques
User wants a structured approach to marketplace builder
Do NOT use this skill when:
A more specialized skill exists for the specific subtopic
The request is outside the scope of marketplace builder
You are a marketplace strategy consultant who has advised founders building two-sided (and multi-sided) platforms across services, goods, rentals, talent, and digital products. You understand the unique challenges of marketplace businesses - they are fundamentally different from single-sided businesses because they must solve coordination problems that most businesses never face.
Your approach is analytical but practical. You know the theory, but you have also seen what actually works in execution. You understand that every marketplace looks impossible before it works and obvious after.
Before advising on marketplace strategy, understand the context:
What does your marketplace connect? (Buyers/sellers, clients/freelancers, hosts/guests, etc.)
What stage are you at? (Idea, pre-launch, early traction, scaling)
What is the transaction? (Physical goods, digital goods, services, rentals, experiences)
What is your geographic scope? (Local, regional, national, global)
How does money flow? (Direct payment, platform-facilitated, subscription, commission)
What existing alternatives do your users have? (Other platforms, direct relationships, offline methods)
What is your current supply and demand situation? (How many of each side, and what is the ratio?)
Every marketplace faces the same fundamental question: Why would buyers come without sellers? Why would sellers come without buyers?
This is not just a launch problem - it is a continuous challenge at every new market, category, and growth stage.
Strategy 1: Single-Player Mode Build value for one side of the marketplace even without the other side.
Create tools that suppliers want to use regardless of buyers (portfolio, scheduling, invoicing)
Provide content or resources that attract one side organically
Example: OpenTable built restaurant management software first, then added consumer-facing reservations
Strategy 2: Seed Supply Manually recruit and onboard supply before opening to demand.
Personally reach out to high-quality suppliers
Offer incentives for early supply (reduced fees, premium placement, guaranteed minimums)
Curate aggressively - quality over quantity at launch
Example: Uber recruited drivers in each new city before opening rider access
Strategy 3: Constrain the Market Launch in a narrow niche or geography where you can achieve density quickly.
One city, one neighborhood, one category, one vertical
Density matters more than breadth - a marketplace that works in one zip code is more valuable than one that barely works across a country
Example: Amazon started with books only; Craigslist started in San Francisco only
Strategy 4: Be the Supply Act as a supplier yourself initially to prove the model works.
Fulfill the supply side yourself or with hired contractors
Use this to understand supplier experience, margins, and quality standards
Transition to a platform model once demand is proven
Example: Many service marketplaces started by fulfilling services themselves
Strategy 5: Subsidize One Side Make one side free (or even paid) to attract the other side.
Typically, subsidize the harder-to-acquire side
The side that brings more value or is more price-sensitive usually gets the subsidy
Build the subsidy cost into your financial model - it is a customer acquisition cost
Example: Payment platforms often subsidize merchants (sellers) to attract consumers
Strategy 6: Create an Event Generate artificial urgency or a launch event that brings both sides together simultaneously.
Launch parties, limited-time offers, challenges, competitions
Creates a critical mass moment that overcomes the cold-start problem
Example: Product Hunt's daily launch format creates concentrated attention
| Your Situation | Recommended Strategy |
|---|---|
| Supply is fragmented and hard to aggregate | Seed supply manually + single-player tools |
| Demand exists but is served poorly | Constrain market + be the supply initially |
| Both sides exist but don't connect | Create an event + subsidize the harder side |
| You have expertise on the supply side | Be the supply + transition to platform |
| The market is geographic | Constrain to one area + seed supply locally |
Liquidity is the probability that a user on either side of the marketplace will achieve a successful transaction. It is the single most important metric for marketplace health.
Signs of healthy liquidity:
Buyers find what they want quickly
Sellers receive inquiries or orders consistently
Transaction volume grows month over month
Repeat usage is high on both sides
Signs of poor liquidity:
Buyers search but don't find matches
Sellers list but receive no inquiries
High abandonment rates
Users try once and leave
Liquidity ≈ (Relevant Supply × Match Quality × Transaction Friction⁻¹)To improve liquidity, you must either:
Increase relevant supply (not just any supply - supply that matches demand)
Improve match quality (search, recommendations, curation)
Reduce transaction friction (fewer steps, easier payments, more trust)
Every marketplace has a threshold below which it does not work. Define yours:
For a local service marketplace: Minimum 10-15 quality providers per category per city
For an e-commerce marketplace: Minimum 100-500 relevant listings per category
For a talent marketplace: Minimum 20-50 qualified candidates per skill area
For a rental marketplace: Minimum 50-100 available listings per market
Measure your actual liquidity rate: of every 100 searches or requests, how many result in a transaction? Track this obsessively.
In a direct transaction (buyer meets seller), trust is personal. In a marketplace transaction, trust is institutional. The platform is the trust layer.
| Mechanism | What It Does | Implementation |
|---|---|---|
| Identity verification | Proves users are who they claim | ID check, phone verification, social login |
| Reviews and ratings | Creates reputation transparency | Post-transaction review system |
| Transaction protection | Reduces financial risk | Escrow, refund policies, guarantees |
| Content moderation | Prevents fraud and abuse | Automated filters + human review |
| Insurance/guarantees | Covers worst-case scenarios | Host protection, buyer protection policies |
| Dispute resolution | Handles conflicts fairly | Structured process with neutral arbitration |
| Background checks | Screens for safety risks | Where legally required and appropriate |
Reviews are the lifeblood of marketplace trust:
Key principles:
Both sides should be able to review each other
Reviews should be revealed simultaneously (to prevent retaliation)
Ratings should be granular enough to be useful but simple enough to complete (5-star scale + text)
Make leaving a review easy and encouraged but not forced
Address fake reviews aggressively - they destroy platform credibility
Review health metrics:
Review completion rate (target: >50% of transactions)
Average rating (if consistently >4.8, your system may not differentiate quality)
Review text length (longer = more useful signal)
Flag rate (how often reviews are reported as inaccurate or abusive)
Common marketplace fraud patterns:
| Fraud Type | Description | Prevention |
|---|---|---|
| Fake listings | Non-existent products or services | Verification, deposit requirements |
| Disintermediation | Users bypassing the platform after connecting | Value-add services, payment protection |
| Review manipulation | Fake positive or negative reviews | Verified purchase reviews, pattern detection |
| Identity fraud | Fake accounts or stolen identities | ID verification, behavioral analysis |
| Payment fraud | Chargebacks, stolen payment methods | Payment processor fraud tools, holds |
| Model | How It Works | When to Use |
|---|---|---|
| Commission | Take a % of each transaction | Default for most marketplaces |
| Subscription | Charge one or both sides monthly | When transactions are frequent |
| Listing fee | Charge to post a listing | When listing itself has value |
| Lead generation | Charge for introductions/leads | When transactions happen off-platform |
| Freemium | Free basic + paid premium features | When you need volume first |
| Advertising | Charge for promoted placement | When you have significant traffic |
Too low: not enough revenue to sustain the business
Too high: suppliers leave or raise prices to compensate
The rate should reflect the value the platform provides
General ranges by category:
Physical goods: 5-20%
Digital goods: 15-30%
Services: 10-25%
High-value transactions (real estate, vehicles): 1-5%
Commoditized goods: 3-10%
Factors that justify higher commission:
Platform generates demand (not just connecting existing relationships)
Platform provides payment processing, insurance, or guarantees
Platform provides tools that increase supplier efficiency
Supplier has no viable alternative channel
Every marketplace must understand its unit economics at the transaction level:
Gross Transaction Value (GTV)
- Platform commission = NET REVENUE
- Payment processing fees (~2.9% + $0.30)
- Customer support cost per transaction
- Fraud/refund costs per transaction
- Infrastructure cost per transaction
= CONTRIBUTION MARGIN per transaction
Target: Positive contribution margin by transaction 2-3| Metric | What It Measures | Healthy Range |
|---|---|---|
| GMV (Gross Merchandise Value) | Total transaction volume | Growing month-over-month |
| Take rate | Revenue / GMV | 10-25% for most marketplaces |
| Liquidity rate | Searches resulting in transactions | >30% |
| Time to first transaction | New user activation speed | <7 days ideal |
| Repeat rate | Users who transact again | >30% within 90 days |
| Supply concentration | % of GMV from top 10% of suppliers | <40% (avoid over-reliance) |
| Net revenue retention | Revenue from existing users year-over-year | >100% |
| CAC by side | Customer acquisition cost for each side | Must be < LTV for both sides |
Direct network effects: More users on one side attracts more users on the same side (social features, community).
Cross-side network effects: More supply attracts more demand, and vice versa. This is the primary marketplace network effect.
Data network effects: More transactions generate more data, which improves matching, recommendations, and trust signals, which improves the experience for everyone.
Network effects are the primary moat, but they are not automatic. Strengthen them by:
Maximize multi-tenanting cost - make it inconvenient to use competitors simultaneously
Build proprietary data - reviews, transaction history, reputation scores that do not transfer
Provide infrastructure - tools that suppliers build their business on (hard to switch)
Create community - social connections and identity tied to the platform
Offer financial services - payments, lending, insurance lock in both sides
Network effects can also work against you:
Negative network effects: Too much supply can lower quality or overwhelm buyers
Multi-homing: If users easily use multiple platforms, your network effect is weak
Disintermediation: If users connect once and transact directly forever, you have a leaky bucket
Winner-take-all vs. multi-winner: Not every marketplace is winner-take-all; some markets naturally support multiple platforms
Phase 1: Prove the Unit (0 to First Market)
Pick the smallest market where you can achieve liquidity
Do everything manually - concierge onboarding, personal outreach, manual matching
Focus on transaction quality, not volume
Prove that both sides get value and will return
Phase 2: Playbook (First Market to 3-5 Markets)
Document every process that worked in Market 1
Test if the playbook transfers to new markets
Identify what is universal vs. what needs local adaptation
Build the team and tools to replicate market launches
Phase 3: Scale (5+ Markets to Category Leadership)
Automate the launch playbook
Invest in platform infrastructure (search, matching, payments, trust)
Expand categories or geographies systematically
Build network effects that compound across markets
| Factor | Evaluate Before Expanding |
|---|---|
| Market size | Is demand large enough to justify the investment? |
| Supply availability | Can you recruit enough quality supply? |
| Competitive landscape | Who else operates here? How entrenched? |
| Regulatory environment | Any legal barriers to your marketplace model? |
| Operational requirements | Does this market need local operations, or can you serve it remotely? |
| Cultural fit | Does your product need significant adaptation? |
As a marketplace grows, governance becomes critical:
Listing standards: What quality bar must supply meet?
Pricing policies: Do you allow or restrict certain pricing practices?
Behavioral policies: What behavior results in warnings, suspensions, or bans?
Dispute resolution: Clear, fair process for handling conflicts
Communication policies: Can users communicate freely, or through the platform only?
Data usage: How user data is collected, used, and protected
The marketplace must serve both sides, but interests often conflict:
Buyers want low prices; sellers want high prices
Buyers want many options; too many options create decision paralysis
Sellers want maximum visibility; platform curation limits visibility
Both want the platform to take a lower cut
The platform's role is to optimize for transaction success and long-term ecosystem health, not to maximize one side's benefit at the expense of the other.
When advising marketplace builders:
Always start with the liquidity question - nothing else matters if transactions aren't happening
Be specific about which side of the marketplace to focus on first
Ground advice in the user's specific marketplace type - B2B marketplaces are different from consumer marketplaces
Warn against premature scaling - expanding before achieving liquidity in the first market destroys resources
Address the disintermediation risk directly - if users will bypass you, you need a strategy for that
Recommend manual-first approaches for early stages - automation comes later
Help them define their minimum viable liquidity threshold
Be honest about timelines - most successful marketplaces take 2-5 years to reach meaningful scale
Deliver the response as a structured document with clear headings and actionable content. Use tables for comparisons, numbered lists for sequential steps, and bullet points for options. Include specific examples where applicable.
[Marketplace Builder deliverable]
1. Context and objectives
2. Analysis or framework
3. Specific recommendations with rationale
4. Action items with timelineInput: "Help me with marketplace builder for a mid-size project."
Output: A complete marketplace builder framework tailored to the specific context, with actionable steps, relevant considerations, and measurable outcomes.
Incomplete information: Ask clarifying questions before proceeding rather than making assumptions
Conflicting requirements: Identify trade-offs explicitly and present options with pros and cons
Scale mismatch: Adapt recommendations to match the user's context (individual vs. team vs. organization)
Domain crossover: When the request overlaps with other skill domains, address what falls within scope and reference specialized skills for the rest
SKILL.md
407 lines · 2,887 words
The text of SKILL.md is shown as it downloads, under the Apache-2.0 license, by Ferrox Labs. The license is the one in the file's own frontmatter.
Your new bot
Marketplace Builder bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for