How to Build a Two-Sided Marketplace App with Greta
TL;DR: Building a two-sided marketplace with Greta in 2026 is approachable for the technical build --- 3--5 days for the core supply and demand sides, listings, search, messaging, and transactions. The harder work is the cold-start problem (which side do you bootstrap first?), trust infrastructure (reviews, verification, dispute resolution), and the niche selection that gives your marketplace any chance against horizontal incumbents. This guide covers the realistic build sequence, the trust patterns, payment flows (Stripe Connect for marketplaces), commission models, and the operational discipline that separates marketplaces that get to first 100 transactions from marketplaces that launch and disappear.
Introduction
Two-sided marketplaces are one of the highest-leverage business models when they work --- Airbnb, Uber, Etsy, Upwork, DoorDash. They're also one of the hardest to build because of the cold-start problem: without buyers, sellers don't list; without sellers, buyers don't show up; without volume, neither side stays. Solo founders who try to build the next horizontal marketplace usually fail. Solo founders who build niche marketplaces with deep specific fit can succeed.
In 2026, AI app builders compress the technical build dramatically. With Greta, the core marketplace (supply and demand sides, listings, search, messaging, transactions) ships in 3--5 days. The cold-start problem, trust infrastructure, and niche selection remain the hard work --- they're not technical problems; they're business model and operations problems.
This guide covers the realistic build. The data model and architecture, the build sequence, payments via Stripe Connect, trust patterns (reviews, verification, dispute resolution), commission models, and the cold-start strategies that actually work for niche marketplaces. By the end, you'll know what's possible and what's required beyond the build to make a marketplace work.
What makes marketplaces hard
- Cold-start problem --- Neither side joins without the other
- Trust at scale --- Strangers transacting with strangers requires trust infrastructure
- Liquidity --- Below critical mass, marketplaces feel empty and die
- Unit economics --- Take rates need to fund operations + customer acquisition
- Disintermediation --- Buyers and sellers may transact outside the platform after first match
- Quality control --- Bad actors damage trust for everyone
- Cross-side network effects --- Value to each side depends on the other
Why niche marketplaces win in 2026
Horizontal marketplaces (compete with Etsy, Airbnb, Upwork at scale) are essentially impossible for solo founders. Niche marketplaces succeed because:
- Cold-start is solvable --- Smaller universe means you can manually seed both sides
- Trust is easier --- Smaller community has more accountability
- Liquidity is achievable --- Critical mass is much lower for a niche
- Unit economics work --- Higher AOV in niche categories, defensible take rates
- Defensibility --- Niche expertise creates moat against generalists
- Customer acquisition is targeted --- You know exactly where your sides hang out
Examples of niche marketplaces that work
- Marketplace for niche service providers (e.g., specialized photographers, niche fitness coaches, language tutors for specific languages)
- Marketplace for specific physical goods (vintage typewriters, rare books, niche musical instruments, custom-made items)
- B2B marketplaces (e.g., agencies hiring freelancers in specific specialties, businesses finding industry-specific vendors)
- Marketplace for specific events or experiences (private chef bookings, niche workshops, hyperlocal experiences)
- Marketplace for specific space rentals (photography studios, recording studios, niche commercial spaces)
- Talent marketplaces in specific industries (musicians for events, models for niche shoots, voice actors for specific languages)
- Knowledge marketplaces (1:1 expert consultations in specific domains)
The marketplace data model
| Entity | Key Fields | Relationships |
|---|---|---|
| User | Email, Name, Type (Buyer/Seller/Both), Stripe Account ID, Status | Has many Listings (if Seller), Bookings (if Buyer) |
| SellerProfile | Bio, Photo, Verifications, Rating, Response time | Belongs to User; has many Listings |
| Listing | Title, Description, Price, Type, Category, Status, Photos | Belongs to Seller; has many Bookings |
| Booking | Listing, Buyer, Status, Dates, Total, Commission | Belongs to Buyer, Listing |
| Message | Sender, Recipient, Body, Booking | Threaded by participants |
| Review | Reviewer, Reviewee, Booking, Rating, Body | Belongs to Booking |
| Transaction | Booking, Payment Intent, Total, Commission, Payout | Belongs to Booking |
| Dispute | Booking, Initiator, Reason, Status, Resolution | Belongs to Booking |
The 3--5 day build sequence
Day 1: Spec, scaffold, user roles
- Hour 1--2: PRD (niche, supply-side persona, demand-side persona, key transaction shape, commission model)
- Hour 3--4: Scaffold the data model with multi-role user system (Buyer, Seller, Both)
- Hour 5--6: Build sign-up flows for each side with role-specific onboarding
- Hour 7--8: Seller profile creation and listings dashboard
Day 2: Listings and search
- Hour 1--3: Listing creation with category, pricing, photos, availability (if relevant)
- Hour 4--5: Browse/search interface for buyers (filters, sort, map view if location-relevant)
- Hour 6--7: Listing detail page with seller profile, reviews, booking CTA
- Hour 8: Saved listings and favorite sellers for buyers
Day 3: Messaging and bookings
- Hour 1--3: Messaging system between buyer and seller (per-booking thread)
- Hour 4--6: Booking flow --- initiate, accept/decline, confirm
- Hour 7--8: Booking management for both sides (upcoming, active, completed)
Day 4: Payments via Stripe Connect
- Hour 1--3: Stripe Connect setup --- Express accounts for sellers, Customer accounts for buyers
- Hour 4--5: Payment flow with destination charges and application fees
- Hour 6--7: Payout handling and dashboard for sellers
- Hour 8: Email notifications for payment events
Day 5: Trust, reviews, polish, launch
- Hour 1--3: Review system (post-completion reviews; visible after both sides review or after grace period)
- Hour 4--5: Basic verification (ID, email, phone)
- Hour 6: Dispute reporting flow
- Hour 7: Mobile responsive, empty states, error handling
- Hour 8: Soft launch with seeded supply
Stripe Connect: marketplace payments specifically
Stripe Connect is Stripe's product for marketplace payments. It handles the complexity of taking buyer money, holding it briefly, and paying sellers (minus your commission).
Account types
- Express accounts --- Sellers onboard via Stripe-hosted flow; minimum effort; Stripe handles most KYC. Most common for indie marketplaces.
- Custom accounts --- More control over UX; you handle more compliance burden
- Standard accounts --- Sellers have full Stripe dashboards; less common
Payment flow
- Buyer initiates payment via your checkout flow
- Stripe processes the payment to your platform account
- Application fee (your commission) deducted
- Remainder transferred to the seller's Connect account
- Seller payouts to bank account on Stripe's schedule (or your custom schedule)
Key concepts
- Destination charges --- Payment goes through your account; you control the flow
- Direct charges --- Payment goes directly to seller's account; you take application fee
- Application fee --- Your commission percentage or flat amount per transaction
- Transfer reversal --- When you need to refund a buyer; transfers from seller back
- Holding funds --- Stripe holds payments during dispute periods
Trust infrastructure: what's required
Verification levels
- Email verification --- Baseline; one-tap via magic link
- Phone verification --- Adds friction; reduces spam accounts
- ID verification --- Required for higher-trust marketplaces; use Stripe Identity or Onfido
- Background checks --- For certain marketplaces (childcare, in-home services); use Checkr or similar
- Address verification --- For physical goods marketplaces
Review system
- Post-transaction reviews (both sides review each other)
- Reviews hidden until both submitted or after grace period (prevents retaliation)
- Public ratings visible on profiles and listings
- Response option (sellers can respond to reviews)
- Reviews can't be deleted by reviewees (only flagged for moderation)
Dispute resolution
- In-marketplace dispute reporting
- Hold buyer payment during dispute period
- Manual review by you (or your team) for v1
- Resolution options: refund, partial refund, release to seller
- Stripe Disputes handle credit card chargebacks separately
Anti-fraud measures
- Stripe Radar for payment fraud detection
- Rate limits on new account actions
- Pattern detection (multiple accounts from same IP, unusual transaction patterns)
- Manual review for high-value transactions
- Suspended account workflow for confirmed bad actors
Commission models
| Model | Pattern | Best For |
|---|---|---|
| Percentage commission | 10--20% of transaction value | Most services marketplaces |
| Listing fee | Flat fee per listing | Listings-driven marketplaces (eBay-style) |
| Subscription for sellers | Monthly fee for posting access | B2B marketplaces, talent platforms |
| Payment processing markup | Stripe's fee + your markup | Lower-margin marketplaces |
| Lead fee | Charge per qualified lead | Service marketplaces (mortgage, home services) |
| Hybrid | Subscription + transaction fee | Higher-trust marketplaces |
Honest framing: 15% commission is the typical sweet spot for services marketplaces. Below 10% rarely funds operations + customer acquisition. Above 25% drives sellers off-platform. Etsy is around 6.5% + transaction fees; Uber is around 25%; freelance platforms vary 5--20%.
The cold-start problem: strategies that work
Strategy 1: Supply first
- Manually recruit 50--100 sellers before launching to buyers
- Free or reduced commission for early sellers
- Personal outreach to people you know in the niche
- Concierge onboarding (white-glove signup help)
- Demand-side launch only after supply is genuinely populated
- Example: Airbnb famously did this with hosts
Strategy 2: Demand first
- Build the demand-side audience first (newsletter, community)
- Recruit sellers to serve the audience you already have
- Sellers see traction immediately
- Works when you can build an audience without supply
- Example: Substack writers becoming sellers in adjacent marketplaces
Strategy 3: Single-player first
- Build a single-side tool (e.g., portfolio for photographers)
- Tool becomes valuable on its own
- Add marketplace functionality once side has critical mass
- Example: Some freelance platforms started as portfolio sites
Strategy 4: Geographic concentration
- Launch in one specific city or region first
- Concentrate supply and demand in same geography
- Achieve liquidity locally before expanding
- Example: Uber's city-by-city launch model
Strategy 5: Niche concentration
- Launch in one specific niche (single category)
- Achieve liquidity in that niche before expanding to adjacent
- Niche-specific marketing channels reduce CAC
- Example: Etsy started with one category; expanded later
Customer acquisition for marketplaces
- Niche community participation --- Where both sides hang out
- SEO for niche keywords --- Both supply and demand search
- Direct outreach for supply --- Often personal recruitment for first 50
- Demand-side: content marketing in niche channels
- Partnerships with niche newsletters and influencers
- Referral programs once liquidity is established
- Paid acquisition only after unit economics are clear
Common Mistakes Building Marketplaces
- Going horizontal --- Trying to compete with Etsy/Upwork/Airbnb on breadth. Niche-fit is essentially mandatory.
- Building both sides at once --- Either supply first or demand first. Trying to build both simultaneously without a plan usually fails.
- Underestimating cold-start --- Marketplaces stay empty for the first 6--12 months. Persistence matters.
- Skipping trust infrastructure --- Without reviews, verification, and dispute resolution, trust collapses with the first bad actor.
- Wrong commission model --- Too low and you can't fund ops; too high and sellers leave. Test the sweet spot for your niche.
- Allowing disintermediation --- Some marketplaces lose users who match once then transact off-platform. Build value beyond the match.
- Skipping Stripe Connect setup --- Building marketplace payments from scratch is months of work. Use Stripe Connect.
- Underestimating operational burden --- Marketplaces require ongoing trust and safety work, dispute resolution, fraud monitoring.
- Ignoring the legal layer --- Marketplaces have liability for transactions, sales tax obligations, regulatory exposure in specific categories.
- Trying to scale before liquidity --- Expanding geographies or niches before achieving liquidity in the first kills marketplaces.
Frequently Asked Questions
Q1: Can a non-developer really build a marketplace in 3--5 days? Yes for the core build via AI app builders. The harder work is supply seeding, trust setup, customer acquisition, and operational discipline --- these don't speed up with AI app builders.
Q2: What about Stripe Connect alternatives? Stripe Connect dominates marketplace payments. Alternatives exist (Adyen, Braintree Marketplace) but are typically chosen by larger or enterprise marketplaces. For indie marketplaces, Stripe Connect is the default.
Q3: How long does it take to achieve liquidity? Highly variable. Niche marketplaces can achieve liquidity in 6--12 months with disciplined supply seeding. Horizontal marketplaces typically need years and significant capital. Plan for at least 12 months to first 100 sustained transactions.
Q4: What about chicken-and-egg in messaging? Until supply and demand match, no messages exist. Solve by recruiting supply first (manually); then demand sees real listings to message. Without real supply, demand bounces.
Q5: How do I prevent disintermediation? Build ongoing value: reputation/reviews tied to platform, payment protection, dispute resolution, repeat-customer features, additional services beyond the match. The more value beyond the initial match, the more transactions stay on platform.
Q6: What about marketplace operations workload? Trust and safety, dispute resolution, fraud monitoring, customer support --- ongoing work. Indie marketplaces typically need 5--20 hours/week of operational time at v1; grows with transaction volume. Plan for it.
Q7: Are marketplaces still viable in 2026 or is the space saturated? Horizontal marketplaces are saturated. Niche marketplaces remain viable opportunities. Many niches still don't have purpose-built marketplaces; the build-cost reduction in 2026 makes more niches addressable for indie founders.
Conclusion
- Two-sided marketplaces in 2026: 3--5 days for the technical build via AI app builders; 6--18 months for liquidity and trust infrastructure. The build is the easy part.
- Niche-fit is essentially mandatory. Horizontal marketplaces require capital and time that indie founders rarely have. Niche marketplaces have addressable cold-start, defensible position, and viable unit economics.
- Stripe Connect handles marketplace payments cleanly. Express accounts onboard sellers fast; destination charges + application fees structure the commission flow. Don't build payments from scratch.
- Cold-start strategy matters more than the build. Supply first, demand first, single-player first, geographic concentration, niche concentration --- pick one based on your specific niche dynamics.
If you're considering a marketplace, pick the niche this week. Map the supply and demand sides --- who they are, where they hang out, what triggers them to join. Run the 3--5 day build once the niche is clear. Begin supply recruitment immediately after build (or in parallel). The technical build is solved; the cold-start and trust work is what determines whether your marketplace becomes a real business or another launched-and-abandoned attempt. Stay patient; stay disciplined; serve your specific niche deeply. The niche marketplace opportunity is real in 2026 --- but it requires the work that AI app builders don't shortcut.
