A marketplace is not a website with two user types. It’s a system where two sides have to trust each other at the same moment — and the design partner you choose either understands that or learns it on your budget.
This guide covers the criteria that separate a marketplace design partner from a general UX agency. These are the five things that only matter for marketplaces, and that most agencies have never done.
What makes marketplace design different from regular product design?
A single-sided product has one user and one funnel. A marketplace has two users with opposite needs and two funnels that compete with each other.
Buyers want low prices, fast results, and protection. Sellers want visibility, high prices, and fast payouts. Every design decision for one side creates friction for the other.
A general UX agency optimizes one funnel. A marketplace design partner optimizes two competing funnels at once — and knows which trade-offs are worth making.
Criterion 1: Do they have experience with multi-role flows?
A marketplace has more than two users. Buyer, seller, admin, moderator, support, finance, compliance — each one needs a different interface, different permissions, and a different onboarding path.
What to ask:
How many user roles did your most complex platform have?
Can you name them and describe what each role sees?
How did you handle role-based permissions in the design system?
What a marketplace partner says: “13 roles. Super admin, fleet admin, accountant, compliance officer, driver, dispatch, support — each with its own dashboard view and permission set.”
What a general agency says: “Buyer and seller. Admin panel we’ll figure out later.”
The admin layer is usually 30-40% of a marketplace build. An agency that hasn’t scoped it will quote 60% of the real cost.
Criterion 2: Do they understand trust & safety as a design problem?
Nobody pays a stranger on a new platform without trust signals. Verified badges, transaction counts, response times, buyer protection copy, dispute resolution flows — these aren’t features. They’re the reason the transaction happens.
What to ask:
Where does a buyer decide to trust a seller on a platform you built?
What happens when a transaction goes wrong? Walk me through the dispute flow.
How do you design trust signals when the platform has 3 reviews instead of 300?
What a marketplace partner says: “Trust signals on the seller profile, buyer protection copy above the pay button, structured reviews, and a designed dispute flow with deadlines and evidence from both sides.”
What a general agency says: “We’ll add star ratings and a verified checkmark.”
Criterion 3: Have they designed payment architecture?
Marketplace payments are not a Stripe integration. Split payments, escrow, multi-currency, payout schedules, refund logic, dispute holds — each one adds complexity that generic web development doesn’t prepare a team for.
What to ask:
Describe the payment flow — from buyer checkout to seller payout.
How did you handle escrow? When does money release?
What happens when a refund overlaps with a scheduled payout?
What a marketplace partner says: “Escrow holds funds until buyer confirms. Payout runs weekly with reconciliation. Refunds adjust the next cycle with a visible breakdown. Disputes freeze the transaction until resolved.”
What a general agency says: “We integrate Stripe Connect.”
Criterion 4: Do they understand two-sided dynamics?
The chicken-and-egg problem, cold start, supply-demand fit, liquidity — these are marketplace-specific concepts that shape every design decision from day one.
What to ask:
Which side should we seed first and why?
How do you design for empty states when the platform has 20 listings?
What does the seller’s first 48 hours look like on a platform you built?
What a marketplace partner says: “Supply first. Empty states redirect to active categories. Sellers get an activity notification within 48 hours because silence is the number one reason sellers churn.”
What a general agency says: “We’ll design a great onboarding for both sides.”
Criterion 5: Is their handoff dev-ready?
A marketplace design that looks great in Figma but requires the engineering team to guess at permissions, edge cases, and state management costs more to build than it saved on design.
What to ask:
Does your design system include component states — loading, error, empty, disabled?
How do you document role-based permissions for the dev team?
Do you stay involved during development, or hand off and leave?
What a marketplace partner says: “Component library with every state documented. Permission matrix by role. Flow diagrams with edge cases. We stay embedded through launch.”
What a general agency says: “We deliver the Figma file and a style guide.”
What questions should I ask a marketplace design agency before signing?
→ How many user roles did your most complex platform have? Name them.
→ Walk me through the trust architecture on a live platform you built.
→ Describe your payment flow — escrow, payouts, refunds, disputes.
→ Which side of the market did you seed first and why?
→ Show me the seller’s first 48 hours on a platform you designed.
→ Show me a dev-ready handoff — component states, permission matrix, edge cases.
→ Show me a live marketplace I can sign up for right now.
→ Do you stay involved during development or hand off and disappear?
If more than three answers are vague — they’ve designed screens, not marketplaces.
How much does marketplace design cost?
Design-only for a marketplace MVP: $20K–50K. Design + development for a production platform: $80K–200K+. The biggest cost driver is payment architecture, trust systems, and multi-role UX — not the number of screens.
Ask for the estimation breakdown — hours per module, assumptions, risk contingency — not just the total.
Why does specialization matter more for marketplaces?
Marketplace design has its own rules — density, trust, two-sided flows, escrow, role permissions — that don’t transfer from other product types. The agency that has built marketplaces has already made the mistakes your project would encounter. The agency that hasn’t will discover all of this on your timeline and your budget.
At U1CORE we’ve processed $720M+ through platforms we’ve built. We work as your product team — without the equity, without the hiring.
FAQ
A UX agency optimizes one user’s journey. A marketplace design agency optimizes two competing journeys plus the admin layer, payment architecture, and trust systems.
Ask them to describe the payment flow, trust architecture, and multi-role permissions on a live platform. If they can’t name more than two user roles — they haven’t built one.
Full-stack. Marketplace design decisions are inseparable from engineering. A design-only agency hands off a Figma file and the engineering team has to guess at the rest.
Evaluating on portfolio aesthetics instead of platform experience. A live marketplace with real transactions tells you they can make the transaction happen.
Discovery: 2 weeks. MVP design: 6–8 weeks. Full platform: 3–4 months. If an agency quotes 3 weeks — they’re skipping the parts that matter.
U1CORE builds marketplace platforms for strong businesses whose digital doesn’t yet play at their level. $720M+ processed. Your product team — without the equity, without the hiring. Book a strategy call.
Every marketplace founder hits the same wall. Buyers won’t come without sellers. Sellers won’t come without buyers. Neither side sees value in an empty platform. This is the cold start problem — and it kills more marketplaces than bad design, bad code, or bad timing combined.
This guide covers what the cold start problem actually is, which side to seed first, seven strategies that work in practice, and the product design decisions that reduce cold start friction. Not theory. Just what we’ve seen work on real marketplace platforms.
What the cold start problem is
A two-sided marketplace needs both sides active simultaneously to create value. A restaurant marketplace with 500 restaurants and zero diners is a directory nobody visits. The same marketplace with 10,000 diners and zero restaurants is a search engine that returns nothing.
The cold start problem is the phase where neither side has enough density to make the other side stay. Every search returns too few results. Every listing gets too few views. Every seller waits too long for the first transaction. Both sides conclude the platform is dead — even if the other side exists, just not at the same time or in the same location.
The problem isn’t getting users. It’s getting both sides to show up in the same place, at the same time, with enough density to make transactions happen.
Why the chicken-and-egg problem breaks most marketplaces
Most marketplaces die in this phase. Not because the idea was wrong — because the execution attacked both sides equally with limited resources.
The founder launches in 12 cities. 15 categories. “Let’s see where traction happens.” Result: 3 listings per category per city. Every search returns almost nothing. Both sides assume the platform is dead.
100 sellers across 10 cities = 10 sellers per city. 10 sellers across 5 categories = 2 sellers per category. A buyer searches and finds 2 options. Not enough to compare. Not enough to trust. Not enough to transact.
Same 100 sellers in 1 city, 1 category = full inventory. Every search returns results. Transactions start. That’s not a marketing problem. That’s a density problem. And density requires constraint.
Which side to seed first: supply or demand?
Seed supply first. Almost always.
A buyer who arrives and finds nothing leaves and never comes back. A seller who lists and waits can be retained with activity signals — “3 people viewed your listing today.” The seller’s patience window is weeks. The buyer’s patience window is seconds.
The exceptions: when supply is abundant and undifferentiated (commodity products), seed demand first — sellers will follow the buyers. When both sides are identical (social networks, communication tools), seed the side that’s easier to acquire.
For most marketplaces — services, goods, rentals, B2B — supply first. Get 20-50 committed sellers before launch. Curate their listings. Make sure the first buyer finds something worth buying.
7 proven cold start strategies
Single-player mode — utility before the network
Build a tool that’s useful to one side even without the other. Yelp started as a review site. OpenTable started as a reservation management tool for restaurants. Sellers used it for their own operations before any buyer marketplace existed.
If your sellers can use the platform as a standalone tool — inventory management, booking system, portfolio page — they’ll onboard for the tool and stay for the marketplace. The network effect becomes a bonus, not a requirement.
Niche down by city, category, or community
Don’t launch a “marketplace for everything, everywhere.” Launch a marketplace for vintage watches in London. Or freelance designers in Berlin. Or organic produce in one neighborhood.
Constraint creates density. 50 sellers in one niche feel like a thriving marketplace. 50 sellers across 10 niches feel like a ghost town. The first market should be small enough to feel full and specific enough that both sides self-identify.
Airbnb started in San Francisco during conferences. Uber started in San Francisco with black cars only. Every successful marketplace started smaller than the founder wanted.
Concierge and manual matching
Before building the algorithm, be the algorithm. Manually match buyers with sellers. Email introductions. Phone calls. WhatsApp messages. Do things that don’t scale — they teach you what scaling needs to replicate.
If buyers won’t transact when you personally match them with the right seller — no technology will fix that. If they will — you’ve validated the transaction and learned exactly what the matching algorithm needs to do.
Seeding supply: partnerships, imports, direct outreach
Partner with existing communities where your sellers already gather. Industry associations, Facebook groups, existing directories, trade events. Don’t ask them to “join your platform.” Ask them to “list for free and see what happens.”
Import existing supply. Craigslist listings, public directories, open datasets. Populate the platform so the first buyer finds something. Then convert passive listings into active sellers when transactions start.
Direct outreach works at small scale. 50 personalized emails to sellers in your niche. Not “join our marketplace.” Instead: “I noticed you sell [specific thing]. I’m building a platform for [specific niche] and I’d love you to be one of the first.”
Incentives and subsidies for the hard side
The “hard side” is the one that’s harder to acquire and more valuable once active. Usually it’s supply. Subsidize them. Free listings for the first 6 months. Guaranteed minimum payouts. Featured placement for early sellers.
Uber subsidized drivers with guaranteed hourly rates. The drivers showed up because the money was guaranteed. The riders showed up because the drivers were there. Once both sides were active, the subsidies dropped.
The subsidy isn’t a cost. It’s customer acquisition for the side that makes the marketplace work.
Piggybacking on existing networks
Go where your users already are. Airbnb famously posted listings on Craigslist. PayPal attached itself to eBay. Build integrations, cross-postings, or plugins that bring your marketplace into existing platforms.
The key: piggybacking works when you offer something the existing network doesn’t — escrow, trust signals, verification, better UX design. If you’re just duplicating what they already have, there’s no reason to switch.
Community and offline events
Host events. Meetups. Webinars. Workshops. Bring both sides into the same room — physically or virtually. The relationships formed offline convert to transactions online.
Etsy built its early community through craft fairs. The sellers already knew and trusted each other. The marketplace became the digital extension of an existing community, not a platform trying to create one from scratch.
Product and design decisions that reduce cold start friction
Design for empty states. “No results found” kills a new marketplace. Replace dead ends with redirects: “Nothing in this category yet — browse popular categories” or “Be the first to list in this area.” The first session determines whether there’s a second one.
Show activity, not emptiness. “47 searches in this category today” tells a seller the demand exists even if the transaction hasn’t happened yet. “12 sellers joined this week” tells a buyer the platform is growing.
Seller first-48-hours design. A seller who lists and gets zero signal for 48 hours leaves. One notification fixes this: “5 people viewed your listing today.” Not a discount. Not a tip. Just proof the platform is alive.
Lower the commitment threshold. Don’t require full profiles and 10 photos upfront. Let sellers list with minimum effort — name, one photo, price. Friction during onboarding kills supply growth. Let them enhance their listings after the first transaction proves the platform works.
Trust signals that work at low volume. You can’t show “4.8 stars from 200 reviews” when you have 3 reviews. Show response time instead: “Responds in 2 hours.” Show verification: “ID verified.” These work from day one.
Metrics for the seeding phase: liquidity, match rate, time to first transaction
Marketplace liquidity. The percentage of listings that result in a transaction within a defined period. If only 5% of listings sell within 30 days, sellers will churn. Target varies by category — Airbnb targets 30-50% booking rate in mature markets. At cold start, track the trend more than the number.
Match rate. The percentage of searches that return relevant results. If 40% of buyer searches return zero results — you have a supply gap. Track which searches return nothing and fill those gaps with targeted seller acquisition.
Time to first transaction. How long between signup and first purchase. If it’s more than 7 days for buyers — the platform didn’t deliver value fast enough. If it’s more than 14 days for sellers — they’ll leave before experiencing the marketplace.
Repeat rate. The percentage of users who transact more than once. Below 15% — you’re a discovery tool, not a platform. Users find what they need and leave. Above 30% — you have a marketplace people come back to.
When you’re ready to scale to the next market
Don’t scale until the first market works. “Works” means:
Supply-demand fit — buyer searches consistently return relevant results. Match rate above 60%.
Organic growth — new users arrive without paid acquisition. Sellers refer other sellers. Buyers come back without reminders.
Unit economics — the cost of acquiring a buyer and a seller is less than the revenue each generates. If you’re subsidizing every transaction — you haven’t solved cold start, you’ve postponed it.
Repeat transaction rate above 20% — users come back because the platform is genuinely better than the alternative.
When all four are true in your first market — replicate the exact same playbook in market two. Don’t skip steps. Don’t “go faster this time.” The cold start problem resets in every new market. The only advantage is that you now know which strategy works.
FAQ
The phase where neither side of a two-sided marketplace has enough density to make the other side stay. Buyers find too few listings, sellers get too few views, and both conclude the platform is dead. It’s the #1 reason marketplaces fail before reaching product-market fit.
Supply, in most cases. A buyer who arrives and finds nothing never comes back. A seller who lists and waits can be retained with activity signals. The seller’s patience window is longer. Exceptions: commodity products where supply is abundant — seed demand first.
Enough to make every buyer search return relevant results. For a niche marketplace, that could be 20-50. The number matters less than density — 20 sellers in one category in one city is better than 200 sellers spread across 10 cities and 15 categories.
Own the transaction. Provide escrow, buyer protection, dispute resolution, and verified reviews — value that a direct WhatsApp conversation can’t match. If removing your platform makes the transaction equally safe and easy, the platform isn’t providing enough value.
When your first market has supply-demand fit (60%+ match rate), organic growth, positive unit economics, and a repeat transaction rate above 20%. The cold start problem resets in every new market — the only shortcut is knowing which strategy worked the first time.
U1CORE is a product design and development studio specializing in marketplace platforms. We’ve processed $720M+ through platforms we’ve built. If you’re launching a marketplace and need a team that understands cold start, trust architecture, and two-sided UX — book a strategy call.
Most articles about failed software projects blame communication, scope creep, or budget overruns. Those are symptoms. In custom platform development — marketplaces, exchanges, fleet systems, multi-sided products — the failures are structural. They’re baked into the architecture before the first sprint ends.
This guide covers the platform-specific failures that kill projects before launch, and the vetting process that prevents them. If you’re evaluating a product development agency for a platform build, these are the questions that separate studios who’ve shipped from studios who’ve Figma’d.
Failure 1: Nobody scoped the admin layer
Every platform has two products: the one users see and the one the operations team uses. Most studios scope the first and forget the second.
A marketplace needs seller verification workflows, dispute resolution screens, content moderation queues, payout reconciliation dashboards, compliance audit trails, and permission-based access for every internal role. A fleet platform needs driver management, document expiry tracking, payout calculations, onboarding workflows, and role-specific views for ops, finance, compliance, and fleet owners.
On the FluxRide fleet platform we built at U1CORE, the admin layer contains 21 modules and 13 user roles. Twenty-one modules that nobody would have budgeted for if we hadn’t scoped them in discovery. Most studios quote the driver app and the fleet owner dashboard. The admin layer — the part the operations team uses 8 hours a day — gets estimated as “admin panel” on one line of the proposal.
That one line becomes 40% of the actual build. The project goes over budget not because of scope creep but because the scope was never complete.
How to vet for this: ask the studio to list every internal role that will use the platform and what each role needs to see. If the answer is “we’ll figure out the admin panel later” — that’s where your budget overrun lives.
Failure 2: Payment architecture that breaks under load
A custom software project that processes payments isn’t the same as one that doesn’t. Split payments, escrow, multi-currency, payout schedules, refund logic, tax withholding, and dispute holds all add architectural complexity that generic web development doesn’t prepare a team for.
The pattern we see: the studio integrates Stripe Connect in week 6 and calls payments “done.” Then the platform launches. A seller in Germany sells to a buyer in the UK. VAT calculation fails. The payout includes a refunded transaction. A dispute arrives and the platform has no designed flow to handle it.
Payment architecture for marketplace platforms needs to handle peak load — not average load. A fundraising platform that processes $720M needs to handle donation spikes during Ramadan, not just Tuesday afternoon. A fleet platform processing weekly payouts for 400 drivers needs to run 400 calculations simultaneously without errors or timeouts.
How to vet for this: ask the studio to describe their payment architecture for a platform they’ve shipped. Not Stripe integration. Architecture. Split payment logic. Escrow flow. Refund handling. Payout scheduling. Dispute resolution flow. If they can’t describe the edge cases — they haven’t built one.
Failure 3: Designing one side of the market without the other
A marketplace UX design that optimizes the buyer experience and treats the seller dashboard as an afterthought creates a platform that acquires buyers and churns sellers. Every design decision for one side creates friction for the other.
Lower the commission to attract sellers — your buyer protection budget shrinks. Add strict verification to protect buyers — seller onboarding slows, signups drop. Build a beautiful buyer search experience with filters — but if sellers can’t create listings with structured data that maps to those filters, search returns garbage.
Most studios design the buyer journey, then adapt the seller side. The result: a seller who lists a product and gets zero signal for 48 hours. No views. No saves. No notifications. They assume the platform is dead. They leave.
The seller’s first 48 hours need the same design attention as the buyer’s first 60 seconds. Both sides have to work from day one — not buyer first, seller “phase two.”
How to vet for this: ask the studio to walk you through both the buyer journey AND the seller journey for a platform they’ve built. If they can only describe one side in detail, they’ve only designed one side.
Failure 4: No role-based access model from the start
A platform with one user type needs one login. A platform with buyers, sellers, admins, moderators, finance, compliance, and support needs a role-based access model designed before the first screen is wireframed.
Adding roles after the architecture is set is not a feature request. It’s a rebuild. The database schema, API permissions, front-end routing, and notification logic all depend on the role model. Bolting on a “compliance officer view” to a system designed for two roles breaks things nobody anticipated.
The 18F guide on de-risking custom technology projects specifically flags this: teams that don’t define user roles and permissions in discovery spend 2-3x more time retrofitting access controls after launch. NIST’s Secure Software Development Framework (SSDF) identifies access control architecture as a practice that must be defined before development begins — not bolted on before compliance review.
How to vet for this: ask how many user roles the studio’s most complex platform had. If the answer is “buyer and seller” — they haven’t built a production platform. Real platforms have 5-15 roles. The studio should be able to name them.
Failure 5: No compliance architecture
For fintech products, banking systems, and any platform handling personal data or financial transactions, compliance isn’t a feature. It’s an architectural requirement.
KYC/AML verification flows, data privacy (GDPR/CCPA), audit trails for every transaction, consent management, document retention policies — all of these need to be designed into the system from sprint one. Retrofitting compliance into a platform that wasn’t built for it is the most expensive type of technical debt.
ISO 27001 isn’t a badge you buy — it’s a framework that describes how your system handles information security. A studio building a platform that processes payments or personal data should be able to explain how their architecture supports audit trails, access logging, data encryption at rest and in transit, and incident response procedures.
How to vet for this: ask the studio what compliance requirements your platform will need to meet, and how they’ve handled them in past builds. If they say “we’ll add that later” — the later is a rebuild.
Failure 6: Estimating platforms like websites
A website is a set of pages. A platform is a system. The estimation methodology is fundamentally different.
A studio that estimates a marketplace the way they estimate a corporate website will get the number wrong by 3-5x. Platforms have state management, real-time data, concurrent users, payment flows, multi-role permissions, notification systems, and admin tooling that websites don’t.
The NIST SSDF recommends that software development estimates include security requirements, access control design, and testing scope from the initial planning phase. The 18F vendor management guide recommends that agencies require vendors to demonstrate estimation methodology — not just provide a number.
A single figure with no visible reasoning isn’t an estimate — it’s a price. And a price given before discovery is a sales tactic.
How to vet for this: ask the studio to show you their estimation breakdown for a past project. Not the total. The breakdown. Hours per module. Assumptions documented. Risk contingency. If the estimate is one number on one line — it’s a guess.
The Vetting Checklist: 10 Questions Before Signing
→ How many user roles did your most complex platform have? Name them.
→ Walk me through the admin layer of a platform you’ve shipped. How many modules?
→ Describe your payment architecture — not Stripe integration. Edge cases.
→ Show me both the buyer and seller journey for a platform you’ve built.
→ What compliance requirements did that platform need? How did you handle them?
→ Show me a live platform I can sign up for and use right now.
→ Show me your estimation breakdown — not the total, the methodology.
→ What happens in week one of the engagement? Discovery or wireframes?
→ Who will actually work on my project? Can I meet them before signing?
→ What does the first 48 hours look like for a seller on a platform you’ve built?
If more than three answers are vague — keep looking. The studio that checks all ten has built platforms in production. The rest have built decks in Figma.
FAQ
Incomplete scoping — specifically the admin layer, payment architecture, and role-based access model. These three elements are consistently underestimated because most studios scope the user-facing product and treat operational tooling as an afterthought. The result is a 40%+ budget overrun that isn’t scope creep — it’s scope that was never captured.
Ask to see live products — not portfolios. Ask about user roles, admin modules, and payment edge cases. Ask for estimation breakdowns, not totals. A studio that has shipped platforms can describe the admin layer, the payment architecture, and both sides of the marketplace in detail. A studio that hasn’t will answer in generalities.
NIST SSDF for secure development practices, ISO 27001 for information security management, GDPR/CCPA for data privacy, and PSD2/PCI DSS for payment processing. The specific standards depend on your industry and geography, but a studio should be able to name which ones apply to your platform and explain how they’ve implemented them in past builds.
A website is a set of pages with known content. A platform is a system with state management, concurrent users, real-time data, multi-role access, payment flows, and admin tooling. Platform estimation requires decomposition by module, three-point sizing, role-based complexity scoring, and risk contingency. Website estimation requires a page count and a design complexity assessment. Using the second methodology for the first guarantees an overrun.
U1CORE is a product design and development studio specializing in marketplace platforms, fintech, fleet operations, and banking & compliance automation. $720M+ processed through platforms we’ve built. Your product team — without the equity, without the hiring. Book a strategy call.
A marketplace where nobody transacts is just a directory. The difference between the two is UX design — the patterns that move a visitor from “browsing” to “paying a stranger on the internet.”
This guide covers the marketplace UX patterns that actually drive transactions — search, listings, trust signals, checkout, reviews, and the design decisions that separate platforms that convert from platforms that just look good in a portfolio.
Why marketplace UX is different from single-sided product UX
A SaaS product has one user. A marketplace has two — and they want opposite things.
Buyers want low prices, fast results, guaranteed quality, and protection if something goes wrong. Sellers want maximum visibility, high prices, low fees, and fast payouts.
Every design decision you make for one side creates friction for the other. Lower the commission to attract sellers — your buyer protection budget shrinks. Add strict verification to protect buyers — seller onboarding gets slower, signups drop.
A single-sided product optimizes one funnel. A marketplace optimizes two competing funnels simultaneously. That’s why generic product design playbooks break on marketplaces — the rules are different when every screen serves two audiences with opposing needs.
Designing for two audiences at once: buyer journey vs seller journey
Seller: sign up → create listing → wait for interest → respond → transact → receive payout → get review → list again.
The critical insight: 80% of drop-off happens in the transitions between steps, not on the steps themselves. What happens between “buyer sends message” and “seller responds”? If the seller doesn’t respond in 24 hours, the buyer is gone. What happens between payment and delivery? If there’s no status update, the buyer panics.
Design for the gaps. That’s where marketplaces die.
Core marketplace UX patterns
Search, filters and faceted navigation
Search is the product on most marketplaces. If search fails, nothing else matters.
At low inventory (under 500 listings), curated collections outperform search. “Top picks this week” turns 200 listings into a curated experience. A search bar with 12 filters on 200 listings returns 2 results and makes the platform feel dead.
At scale (5,000+ listings), search needs ranking algorithms, saved searches, and personalized defaults. The user who searched “size 42 Nike black” yesterday shouldn’t see the same generic homepage today.
The rule: match the discovery model to your inventory stage. Not to your competitor.
Listing card and detail page anatomy
The listing card is where the buyer decides to click — or scroll past. It needs: primary image, price, title, location, and one trust signal (rating, verified badge, or transaction count). Nothing else. Every additional element reduces click-through rate.
The detail page is where the buyer decides to pay. It needs: multiple images, full description, seller info with trust signals, clear pricing with fees visible, and a prominent CTA. The buyer should be able to decide from this page alone — without messaging the seller.
Seller profile, ratings and social proof
The seller profile is the trust layer between “I want this” and “I’ll pay this stranger.”
A name and photo is not trust. A verified badge, 47 completed deals, “responds in 2 hours,” and 4.8 rating with 23 reviews — that’s trust.
Design ratings to be meaningful. When every seller is 4.7-4.9, ratings lose all meaning. Show specific transaction counts, response times, and repeat buyer rates. These differentiate better than a star score that everyone shares.
Checkout, booking and request flows
Show the full cost before confirmation. Amount, fees, and total on one screen. “The fee was hidden” is the number one complaint in marketplace UX.
Confirm with clarity. Not “Confirm” — but “Pay £50 to Maria Garcia. Fee: £2.50. Buyer protected.” Every variable stated. Zero new information at the confirmation step.
For service marketplaces where the transaction is a booking or request: show availability, estimated response time, and what happens next. “Your request was sent. Most sellers respond within 4 hours” is infinitely better than a blank “Thank you” screen.
Reviews, messaging and dispute handling
Reviews need structure. “Great seller!” tells the next buyer nothing. Prompt for specifics: was the item as described? How was communication? How fast was delivery? Structured reviews build a trust profile. Unstructured reviews build a wall of text nobody reads.
In-platform messaging keeps the transaction on your platform. The moment users exchange phone numbers or emails, you’ve lost control of the transaction — and the commission.
Dispute handling needs a designed flow — not a support email. Structured report, evidence from both sides, deadline, resolution. One unresolved dispute costs you two users and everyone they tell.
Trust and safety as a design problem
Trust isn’t a page. It’s embedded in every element between search and checkout.
Verified badges — but only if verification means something real. A checkmark that implies more vetting than you actually do is a liability, not a trust signal.
Buyer protection copy — visible at the decision point. “Buyer protected on every transaction” above the pay button. Not in the FAQ.
Status clarity on every transaction. Pending, processing, shipped, delivered. Every state designed. “Processing” with no timeline creates anxiety. “Processing — usually completes in 2 hours” creates confidence.
Mobile-first considerations for multi-vendor platforms
Over 60% of marketplace traffic is mobile. Design mobile-first or lose the majority of your users.
Listing cards need to work at thumb-scroll speed. One image, price, one trust signal. Readable without stopping.
Filters need bottom-sheet design, not sidebar overlays. The user should filter with one hand.
Checkout needs to be completable in under 60 seconds on mobile. Every extra field is a lost transaction.
Seller onboarding on mobile — if sellers can’t create a listing from their phone, you’re limiting supply to desktop hours.
Designing for scale: design system, empty states, thousands of listings
A design system isn’t a luxury — it’s the only way to maintain consistency across hundreds of screens as the marketplace grows. Components, spacing rules, interaction patterns — documented so the development team builds without guessing.
Empty states are the silent killer. “No results found” on one category makes the entire platform feel dead — even if 2,000 listings exist elsewhere. Replace dead ends with redirects: “Nothing here yet — browse popular categories” or “3 sellers nearby are active.”
At thousands of listings, search ranking becomes the product. The default sort order determines what sells. Random or chronological sorting buries quality. Rank by relevance, seller quality, and conversion rate.
Marketplace UX audit checklist (12 points)
→ Can a buyer find a relevant listing in under 30 seconds?
→ Does the listing page build enough trust to pay without messaging the seller?
→ Are all fees visible before the confirmation screen?
→ Does the seller profile show verification, transaction count, and response time?
→ Are empty states designed with redirects — not dead ends?
→ Is the first session experience designed for new users — not power users?
→ Can a seller create a listing in under 5 minutes on mobile?
→ Does the seller get activity signals within 48 hours of listing?
→ Is there a designed dispute resolution flow — not a support email?
→ Does in-platform messaging keep conversations on the platform?
→ Is mobile checkout completable in under 60 seconds?
→ Does the design system scale — or is every screen custom?
If more than 3 answers are “no” — the marketplace needs a UX audit before it needs new features.
What leading marketplaces do well: 3 short teardowns
Airbnb. The search-to-booking flow is optimized for one thing: reducing the fear of staying in a stranger’s home. Verified photos, host response rate, Superhost badges, and a cancellation policy visible before checkout. Every element exists to make the buyer feel safe.
Etsy. Seller profiles feel like shops, not listings. Star Seller badge, shop policies, processing times, and review photos from actual buyers. The trust layer is built into the seller’s identity — not just the platform’s.
Uber. Reduced a complex two-sided transaction to one button. The trust architecture is invisible — background checks, insurance, GPS tracking, and automatic payments all happen without the user thinking about them. The best marketplace UX is the one the user never notices.
FAQ
Trust signals on the seller profile and listing page. Verified badges, transaction counts, response times, and buyer protection copy. Without these, nobody pays a stranger on a new platform — regardless of how good the UI looks.
E-commerce has one user (the buyer) and controlled inventory. Marketplace UX designs for two users with opposite needs, third-party inventory you don’t control, and trust architecture that makes strangers comfortable transacting.
A systematic review of every user flow — buyer and seller — to identify where users drop off and why. It combines analytics, heuristic evaluation, and user testing. A product audit typically takes 2 weeks and produces a prioritized list of fixes ranked by impact.
Own the transaction. Escrow, buyer protection, dispute resolution, verified reviews — value that a WhatsApp conversation can’t offer. If removing your platform makes the deal equally safe, your platform isn’t providing enough value.
Yes. Over 60% of marketplace traffic is mobile. If mobile design isn’t the starting point, you’re designing for the minority and retrofitting for the majority.
U1CORE is a product design and development studio specializing in marketplace platforms. We’ve processed $720M+ through platforms we’ve built. We offer UI/UX design, web design, mobile design, custom software development, app development, branding, and product audit. Book a strategy call.
Every founder who builds a marketplace faces the same problem: you need sellers to attract buyers, and buyers to attract sellers. Neither side shows up first. The ones who figure this out build platforms that compound. The ones who don’t burn their runway wondering why nobody’s transacting.
This guide covers how to start an online marketplace from scratch — from validating your niche through choosing a business model, scoping an MVP, handling payments, and getting your first 100 transactions. No theory. Just the decisions that determine whether your marketplace survives year one.
What an online marketplace is (and how it differs from an e-commerce store)
An e-commerce store sells its own inventory. You buy products, store them, ship them. You control supply, pricing, and quality. One user type: the buyer.
A marketplace connects buyers and sellers. You don’t own inventory. You own the platform where transactions happen. Two user types with opposite needs — buyers want low prices and fast delivery, sellers want high prices and low fees. Your job is to make both sides happy enough to stay.
That difference changes everything — the product design, the business model, the tech architecture, and the operational complexity. An e-commerce store has customers. A marketplace has two businesses inside one product.
The upside: marketplaces scale without inventory risk. The downside: everything is harder because you’re building for two audiences simultaneously.
Marketplace business models: commission, subscription, listing fee, freemium, ads
Your business model determines how you make money — and how both sides feel about paying for the platform.
Commission. You take a percentage of every transaction. The default model for most marketplaces. Aligns incentives — you only make money when your users make money. Downside: requires transaction volume to generate revenue, and top sellers will push back when fees get high.
Subscription. Sellers pay a monthly fee to list. Predictable revenue from day one. Downside: sellers pay whether they get sales or not. Churn is high if the platform doesn’t deliver value fast.
Listing fee. Sellers pay per listing. Controls supply quality — only serious sellers list. Downside: discourages experimentation and slows supply growth.
Freemium. Free to list, pay for premium features — visibility, analytics, priority placement. Maximum supply growth. Downside: becomes pay-to-play and organic sellers feel invisible.
Ads. Sellers pay for promoted listings. Works at scale when there’s enough inventory for organic results to feel competitive. Downside: too early and it kills trust.
How to pick a model for your niche and take rate
Match the model to your transaction type.
High-value, infrequent transactions (real estate, vehicles, luxury): commission works because each transaction generates meaningful revenue. Take rate: 5-15%.
Low-value, frequent transactions (food delivery, services): commission works but take rate needs to be low enough that both sides stay. Take rate: 10-25%.
B2B procurement: subscription or hybrid — businesses prefer predictable costs over variable fees.
Niche with limited supply: listing fee — controls quality and makes each listing meaningful.
The rule: if your average transaction is under $50, commission alone won’t sustain the business. You need volume or a hybrid model. If it’s over $500, commission is the simplest path.
Step 1. Validate the niche and the core transaction
Before building anything, answer one question: what is the transaction?
Not “what does the marketplace do.” What specific exchange of money for goods or services happens between two people on your platform? Describe it step by step.
“Buyer finds a vintage watch from a verified seller, pays through escrow, seller ships with tracking, buyer confirms delivery, funds release to seller.”
If you can’t describe the transaction in one paragraph — you’re not ready to build.
Validate demand. Talk to 20 potential buyers. Not friends. Real people who match your target audience. Ask: how do you currently find and buy [your product/service]? What’s frustrating about that process? Would you pay for a better solution?
Validate supply. Talk to 20 potential sellers. Ask: where do you currently sell? What’s your biggest problem? Would you list on a new platform — and what would convince you to try?
Test the transaction offline. Before building a platform, manually match 5 buyers with 5 sellers. Facilitate the transaction yourself — over email, WhatsApp, whatever works. If people won’t transact when you do the matching by hand, they won’t transact on a platform.
Step 2. Define the supply side and the demand side
A two-sided marketplace needs clarity on who each side is — because they need different onboarding, different dashboards, different trust signals, and different reasons to stay.
Supply side (sellers). Who are they? Individuals or businesses? How many listings will each seller have — 1 or 100? What do they need to succeed on the platform — visibility, tools, analytics? What makes them leave — low traffic, high fees, better alternatives?
Demand side (buyers). Who are they? How do they currently find what they’re looking for? What makes them trust a stranger on the internet enough to pay them? What makes them come back for a second transaction?
The chicken-and-egg problem. Which side do you seed first? Usually supply. Get 20-50 sellers committed before launch. Curate them. Help them create great listings. When the first buyer arrives, they should find something worth buying — not an empty platform with a “No results found” screen.
The worst launch: great marketing campaign drives 1,000 buyers to a platform with 12 listings. All 1,000 leave. None come back. The marketplace UX for empty states is the most important design work you’ll do pre-launch.
Step 3. Map the core user flows: search → match → transaction → review
Before opening Figma, map the complete journey for both sides.
Seller flow: Signup → create listing → wait for interest → respond to buyer → transact → receive payout → get review → list again
Where marketplaces break: the gaps between steps. What happens between “buyer sends message” and “seller responds”? If the seller doesn’t respond in 24 hours, the buyer is gone. What happens between “buyer pays” and “buyer receives”? If there’s no status update, the buyer panics.
Design for the transitions, not just the screens. Every gap is a potential drop-off point. A product audit of existing marketplaces shows that 80% of user drop-off happens between steps — not on them.
Step 4. Scope the marketplace MVP: must-have vs nice-to-have features
The marketplace MVP is the minimum set of features that makes the first transaction possible. Not the tenth feature. Not the admin dashboard. The transaction.
Must-have for MVP:
Seller onboarding — signup, profile creation, listing creation. Keep it under 5 minutes. Every field you add reduces completion rate.
Buyer discovery — search or browse that returns relevant results. At MVP stage with limited inventory, curated collections work better than search with filters.
Listing page — photos, description, price, seller info with trust signals. The page where the buyer decides.
Transaction flow — how money moves from buyer to seller. This needs escrow or at minimum a clear payment path. “Contact seller directly” is not a transaction flow — it’s a way to get disintermediated.
Trust signals — verified badge, transaction count, response time, buyer protection copy. Without these, nobody pays a stranger on a new platform.
Nice-to-have (build after first 100 transactions):
Analytics dashboard, recommendation engine, advanced filters, mobile app, seller analytics, automated dispute resolution, multi-language support. All valuable. None needed before you prove the transaction works.
Step 5. Choose the tech approach: no-code, SaaS platform, or custom build
No-code (Sharetribe, Arcadier). Launch in weeks. Limited customization. Works for validating the concept — not for scaling. You’ll outgrow it within 6-12 months if the marketplace works.
SaaS platform (CS-Cart, Mirakl). More powerful. Subscription model. Good for standard marketplace patterns. Limited when you need custom transaction flows, unique trust architecture, or complex payment logic.
Custom build. Full control. Built exactly for your business model. Takes longer and costs more upfront — but you own the architecture and can evolve it as the marketplace grows. Required for any marketplace with complex payment flows, multi-role users, or trust requirements beyond basic ratings.
How to decide: if you’re validating a concept and have under $10K — start with no-code. If you’ve validated and need to build for real — custom software development gives you the architecture that scales. The rebuild from no-code to custom always costs more than building custom from the start — but only if you’re sure the marketplace works.
At U1CORE every marketplace build starts with a 2-week discovery sprint. If discovery reveals the concept needs more validation, we recommend testing with no-code first. If the transaction is validated, we build custom from day one.
Step 6. Payments, payouts, legal, and tax basics
Payments. Stripe Connect is the default for marketplace payments in most markets. It handles split payments, seller onboarding, KYC, and payouts. Alternatives: Mangopay (strong in Europe), Adyen (enterprise scale), PayPal Commerce Platform.
The critical decision: escrow or direct payment. Escrow holds funds until the buyer confirms delivery. Direct payment sends money to the seller immediately. Escrow adds complexity and cost. Direct payment adds risk. For any marketplace where the product is shipped or the service is delivered after payment — escrow is not optional.
Payouts. How quickly do sellers get paid? Instant payouts cost more but attract sellers. Weekly payouts are cheaper but create friction. The payout schedule is a competitive lever — the marketplace that pays sellers fastest wins supply.
Legal basics. You’re not selling products — you’re facilitating transactions. Your terms of service need to reflect that. Key areas: liability limitations, dispute resolution process, refund policy, seller verification requirements, data privacy (GDPR/CCPA), and platform responsibility. Get a lawyer. This is not a template job.
Tax. In many jurisdictions, marketplace operators have tax reporting obligations for seller income. In the US, you may need to issue 1099s. In the EU, DAC7 requires reporting seller data. Build tax compliance into the platform from the start — retrofitting it is expensive.
Step 7. Launch, the first 100 transactions, and what to measure
Pre-launch. Seed 20-50 sellers. Help them create quality listings. Make sure the first buyer who arrives finds something worth buying.
Soft launch. Open to a small group. Friends, early supporters, one niche community. Fix what breaks. Every marketplace breaks somewhere in the first week — better with 50 users than 5,000.
First 100 transactions. This is your real validation. Not signups. Not page views. Completed transactions where money moved from buyer to seller through your platform.
What to measure:
Signup-to-first-transaction rate. Below 10% — your onboarding or discovery is broken.
Repeat transaction rate. Below 15% — users find what they need and leave. Your marketplace is a discovery tool, not a platform.
Time to first transaction. How long between signup and first purchase? If it’s more than 7 days, the buyer lost interest.
Seller activation rate. What percentage of sellers who sign up actually create a listing? Below 50% — seller onboarding is too complex.
Search-to-zero rate. What percentage of searches return no results? This is the silent killer. Every zero-result search is a buyer who thinks the platform is dead.
Common mistakes that kill early-stage marketplaces
Launching in too many categories or cities. 100 sellers across 10 cities = 10 sellers per city. 10 sellers across 5 categories = 2 sellers per category. Every search returns nothing. Both sides leave. Start with one city, one category. Full density. Then expand.
Building for both sides equally. Your MVP resources are limited. One side needs more attention. Usually it’s supply. Get sellers listed and active. Buyers will follow if the inventory is there.
No escrow. Transaction #87. Seller takes payment and disappears. You spend 3 weeks doing manual refunds from your personal email. Build escrow from day one or accept that you’ll be the escrow.
Ignoring seller experience. Most marketplace teams design the buyer experience and treat the seller dashboard as an afterthought. The seller who lists a product and gets zero signal for 48 hours — no views, no saves, no notifications — churns silently. Design the seller’s first 48 hours with the same care as the buyer’s first 60 seconds.
Disintermediation. Users find each other on your platform and transact on WhatsApp. Every marketplace faces this. The solution: own the transaction by providing value that WhatsApp can’t — escrow, dispute resolution, verified reviews, payment protection. If removing your platform makes the transaction equally easy, you don’t have a marketplace. You have an introduction service.
Scaling before supply-demand fit. More marketing spend won’t fix a marketplace where supply and demand don’t match. If buyers search and find nothing relevant — more buyers just means more disappointed users. Fix density first. Scale second.
FAQ
No-code MVP: $0-5K. SaaS platform: $5K-20K. Custom build: $40K-200K+ depending on complexity. The biggest cost driver is payment architecture, trust systems, and multi-role UX — not the number of screens. A marketplace design and development partner who’s built these before will scope more accurately than a generalist.
No-code: 2-4 weeks. Custom MVP: 8-12 weeks with a focused scope. If your MVP takes 6+ months, the scope is wrong. Build what makes the first transaction possible. Cut everything else.
Commission for most. Subscription for B2B. Hybrid for growth-stage. Match the model to your transaction value and frequency. High-value infrequent = higher commission rate. Low-value frequent = lower rate + volume.
Seed the supply side first. Get 20-50 sellers committed before launch. Curate their listings. Make sure the first buyer finds something worth buying. The worst launch is great marketing driving 1,000 buyers to 12 listings.
Seller onboarding, listing creation, buyer search/browse, listing page with trust signals, payment with escrow, and a review system. Skip the admin dashboard, analytics, recommendation engine, and mobile app until after your first 100 transactions.
Own the transaction. Provide escrow, buyer protection, dispute resolution, verified reviews — value that a WhatsApp conversation can’t offer. If removing your platform makes the deal equally safe and easy, your platform isn’t providing enough value to justify the fee.
U1CORE is a product design and development studio specializing in marketplace platforms. We’ve processed $720M+ through platforms we’ve built. We offer UI/UX design, web design, mobile design, custom software development, app development, branding, and product audit. Book a strategy call.
A product team ships an AI feature. Users try it. It gets the answer right four times and wrong once. The fifth answer is confidently wrong — presented without hedging, without a visible path to correct it, without any signal that the feature had any uncertainty at all. The user fixes the mistake manually, doesn’t open the feature again, and tells two colleagues it doesn’t work.
That’s the abandonment pattern. Not a feature that users tried and disliked. A feature that users tried, trusted, got burned once, and never trusted again. The first wrong answer costs more than ten right ones — because it resets the trust baseline to zero and leaves no mechanism for recovery.
This article covers how to design AI features that survive their first mistake: how to set calibrated expectations before first use, how to communicate confidence honestly, how to make human override effortless, and how to design failure states that keep users in the product rather than outside it. If you’re adding AI features to a SaaS product, this is the design work that decides whether users keep using it.
Why AI Features Get Abandoned
The First Wrong Answer Costs More Than Ten Right Ones
Trust in an AI feature is not linear. Users who experience a correct answer update their confidence slightly upward. Users who experience a wrong answer — especially a confidently wrong answer — update their confidence dramatically downward, often to zero.
This asymmetry means the failure boundary is the most important surface to design. Most product teams design the success state in detail and treat failure as an edge case. The users who abandon AI features are the ones who hit the failure state and found nothing there — no acknowledgment of uncertainty, no easy way to correct the output, no path back to doing it manually.
Design the wrong answer before you design the right one.
Unclear Scope: Users Do Not Know What It Can Do
AI features that fail without warning often fail because users applied them outside their actual competence. A summarization feature that works well on articles but poorly on spreadsheet exports will produce confident wrong answers when applied to spreadsheet exports — because nothing in the interface communicated that limitation.
Unclear scope produces misapplication, which produces wrong answers, which produces abandonment. The solution is not a longer tooltip. It is visible scope boundaries designed into the feature’s normal UI — not hidden in documentation.
No Path Back to Manual Control
An AI feature that replaces rather than augments manual control removes the user’s fallback. When the AI fails, the user has no path back to the workflow they knew. This is the design equivalent of removing the manual transmission and shipping a self-driving system that occasionally drives into walls.
Keep the manual path. Surface it prominently as an always-present option — not as a “something went wrong” fallback. Users who know they can override trust the feature more, not less.
Setting Expectations Before the First Use
Naming the Feature Honestly (Suggest, Draft, Detect — Not Solve)
The language used to name an AI feature sets the expectation that everything else in the UX must maintain. A feature called “AI Answer” implies authoritative correctness. A feature called “AI Suggestion” implies something to review and accept or reject.
The vocabulary of honest AI feature naming: Suggest, Draft, Detect, Flag, Highlight, Summarize, Estimate. These words communicate that the feature produces output for a human to evaluate — not a decision that has already been made.
Grammarly uses “suggestion” throughout its interface, not “correction.” GitHub Copilot uses “suggestion” for code completions. Both frame AI output as input to a human decision. Avoid: Solve, Know, Decide, Confirm, Guarantee.
Showing the Boundaries of Competence Up Front
A single sentence — “Works best with text over 200 words. May miss context in tables and images.” — calibrates expectations before the user encounters a failure. This is not a disclaimer. It is product information. Users who understand a feature’s actual competence apply it appropriately, get correct outputs more often, and trust the feature more as a result.
The first-run experience of an AI feature is the cheapest place to set accurate scope expectations. Design this moment deliberately — not as an onboarding tooltip, but as a functional part of the feature’s interface.
The First-Run Experience That Sets a Calibrated Expectation
The first interaction with an AI feature should produce a correct output on a representative input — not the best possible input, and not an edge case. Show the feature working on something realistic, show the confidence level it assigns to that output, and show how easy it is to override or edit.
A first-run experience that produces an impressive but unrepresentative result sets expectations that subsequent normal use will consistently fail to meet. The goal is not to impress — it is to accurately represent.
Communicating Confidence
When to Show a Confidence Level and When It Just Confuses
Showing a confidence score is only useful when the user can act differently based on it. The test: would a reasonable user make a different decision at 60% confidence than at 90%? If yes, show it — as a number or as a three-state visual. If no, express confidence through UI design rather than a number that users learn to ignore.
Degrading Gracefully: High, Medium, Unsure
Three-state confidence design is more actionable than a numeric score for most non-expert users.
High confidence: present the output as a primary action. “Fill in automatically” as the primary button. The output is applied directly, with an undo available.
Medium confidence: present with a visible review prompt. “Review before applying” label, output in an editable field rather than applied directly. The user sees the output before it takes effect.
Low confidence or unsure: present as a starting point, not an answer. “Here’s a draft — you’ll want to review this carefully.” The output appears in an edit-ready state with a visible unsure indicator.
Notion’s AI features use this model: high-confidence suggestions are presented as completions, lower-confidence outputs are presented as drafts explicitly labeled for review.
Designing the ‘I Don’t Know’ State
An AI feature that returns an output when it doesn’t have a good one is more dangerous than one that says nothing. Design an explicit “I don’t know” state: what it looks like, what copy it uses, and what the user should do next.
“I couldn’t find enough information to answer this reliably. You can search manually or provide more context.” Perplexity AI surfaces a sources indicator on every response — if sources are thin, the response is explicitly labeled as lower-confidence. Users can see the signal and adjust their trust accordingly.
Explainability That Helps a Non-Expert
Sources, Inputs and Reasoning — How Much to Reveal
Explainability should be calibrated to what a non-expert user can act on. A full model trace is not useful to a product manager or small business owner. What is useful: what inputs the feature used, what sources it drew on, and one sentence of plain-language reasoning.
The principle: explain enough that the user can verify the output using their own knowledge, not so much that the explanation requires expertise to evaluate.
Linking to Evidence Instead of Describing It
When a source can be linked, link it. “Based on your last 30 invoices” with a link to the invoice list is more verifiable than “Based on your recent data.” The link transforms the explanation from a claim into a verification shortcut: users who want to check can do so in one click.
In AI hiring platform design — where we worked on the matching and recommendation interface for Hyris — the interface surfaces specific profile signals that produced each match score rather than showing a single number. Users can verify the match reasoning against their own knowledge of the role, which builds trust in the score over time.
Explanation as Verification Shortcut, Not Justification
Explanation copy that reads like a marketing justification reduces trust rather than building it. “Our advanced AI analyzed thousands of signals to produce this recommendation” says nothing verifiable and sounds defensive.
Useful explanation is specific, brief, and verifiable. “Based on: location filter, response rate above 90%, previous bookings in this category.” Three signals, all visible to the user, all checkable. The user who wants to verify can. The user who trusts the summary can skip it.
Human in the Loop
Review, Approve, Edit: Choosing the Right Interaction Model
Three interaction models for human-in-the-loop AI, each appropriate for different output types and risk levels.
Review: the AI produces output and the user decides to accept or reject it wholesale. Appropriate for low-stakes, atomic outputs — a suggested category tag, a predicted label, an auto-filled field.
Approve: the AI produces output and the user approves before it takes effect. Appropriate for medium-stakes outputs that are difficult to undo — a draft email to a customer, a suggested price change, an auto-generated report.
Edit: the AI produces a draft and the user edits before finalizing. Appropriate for high-stakes or high-variability outputs — written content, complex data transformations, consequential recommendations. This is the model that produces the highest user trust because control is never fully delegated.
Making Override Effortless and Non-Punitive
Override must be a primary action, not a safety valve. If a user has to navigate to a settings page or click through a warning dialog to use manual mode, the friction communicates that overriding is wrong. It isn’t — it’s a legitimate, expected workflow.
Override button placement: same visual level as the accept action. Override copy: neutral and non-blaming. “Edit manually” or “Use your own” — not “Reject AI suggestion” or “Override.” The framing matters.
Capturing Corrections as Training Signal
Every user correction is a training signal. A user who edits an AI output from A to B is telling the system that B is better than A for this context. This signal should be captured, not discarded.
When a user modifies an AI output, ask once and optionally whether the correction should improve future suggestions. This closes the feedback loop and gives users a sense that their corrections matter — which increases engagement with the feature over time.
Where Automation Should Never Be Fully Autonomous
Some actions should never be fully automated regardless of model confidence: sending communications to external parties on behalf of the user, deleting data, making financial transactions, publishing content under the user’s name. In these categories, the AI generates a draft and the human confirms before execution. No confidence level removes the requirement for human confirmation.
Failure and Recovery Design
Error Copy That Does Not Blame the User
AI error copy routinely blames the user through implication. “Not enough data to generate a recommendation” implies the user should have provided more data. Design error copy that frames the AI’s limitation, not the user’s failure.
Copy don’ts:
“Invalid input” → implies user error
“Not enough information” → implies user failure
“An error occurred” → unhelpful and generic
“This feature requires more context” → shifts burden to user
Copy dos:
“Couldn’t find a match this time — try adjusting your filters”
“This one’s outside what I can handle reliably — here’s the manual path”
“I need a bit more to work with — [specific prompt]”
“No results this time. You can search manually or try a different input”
Undo, Version History and Reversibility
Any AI action that modifies existing content or data must be reversible. Single-level undo is the minimum. For consequential actions — bulk edits, content replacement, data transformation — version history is the right standard.
Google Docs and Figma both offer version history specifically because users need to recover from changes that seemed correct at the time. AI-applied changes are no different and deserve the same reversibility guarantees as any intentional user action.
Latency: Streaming, Skeletons and Honest Waiting
AI features with meaningful latency need designed waiting states. A blank screen or a spinner with no context fails users who don’t know whether the feature is working or broken.
Streaming output converts waiting into reading for text generation features — the most effective latency mitigation available. Skeleton screens with realistic placeholder shapes set accurate expectations for output structure before it arrives. An honest time estimate (“This usually takes 10-15 seconds”) is better than an indefinite spinner that gives no signal about when to give up.
Ethics and Disclosure in Product Terms
Telling Users When They Are Talking to AI
Users have a right to know when they are interacting with an AI-generated output presented as authoritative, when they are communicating with an AI agent rather than a human, and when an AI is making decisions that affect them.
The regulatory direction — EU AI Act, FTC guidance in the US — is toward mandatory disclosure in these contexts. Design for disclosure now: an “AI-generated” label on outputs, a visible “Powered by AI” indicator on features, and clear labeling when users interact with AI agents rather than humans.
Data Use, Retention and the Settings Users Look For
Users expect answers to three questions: does this feature use my data to train the model, how long is my data retained, and can I opt out. If the answers exist only in a privacy policy, users assume the worst.
Surface these settings in the feature’s UI. A small “About this AI feature” link that opens a plain-language explanation of data use is more trustworthy than a legally accurate but inaccessible policy document.
Bias in Ranking and Scoring Features
AI and ML features that rank, score, or sort people or listings carry bias risk. A hiring recommendation system that scores candidates can reflect and amplify historical biases in training data. A marketplace ranking that systematically under-exposes certain seller categories has both ethical and business consequences.
Audit ranking and scoring features for demographic and category disparities. Publish the factors that influence scores at the category level. Give users whose content is scored a visible explanation of what affects their score.
Conclusion
Trust in an AI feature is built at the failure boundary. A feature that handles its mistakes gracefully — with honest confidence signaling, easy human override, non-blaming error copy, and a visible path back to manual control — retains users through failures that would otherwise end the relationship permanently.
The design work that determines whether users keep using an AI feature is almost entirely in the states most product teams treat as edge cases: the wrong answer, the unsure state, the override flow, the correction capture, the latency experience. Get these right and users will stay. Get them wrong and a single mistake ends the feature’s useful life.
If you’re designing or auditing AI features in a SaaS or platform product, book a scoping call. We’ll work through your specific feature, its failure modes, and the interface decisions that determine whether users trust it.
FAQ
Three things working together: calibrated expectations (users understand what the feature can and cannot do before they use it), visible boundaries (the interface communicates when the feature is uncertain or out of scope), and easy override (users can always return to manual control without friction or penalty). A feature that handles its failures honestly retains trust better than one that only shows its successes.
Only when the user can act differently based on it. The test: would a reasonable user make a different decision at 60% confidence than at 90%? If yes, show it — as a number or as a three-state visual (high, medium, unsure). If no, express confidence through UI design instead. A numeric confidence score that users ignore adds visual noise without improving decisions.
Four elements: reversibility (any AI action that modifies data must be undoable), low-cost correction (editing an AI output should be easier than starting from scratch), non-blaming copy (errors are the feature’s limitation, not the user’s failure), and a manual path that was never removed. The last point is the most important — users who know the manual path exists trust the AI more, not less.
Yes, when output is presented as authoritative or human-like, and when an AI agent is communicating on behalf of the platform. The regulatory direction — EU AI Act, FTC guidance — is toward mandatory disclosure in these contexts. Design disclosure in now: an “AI-generated” label on outputs, a plain-language explanation of data use in the feature’s UI, and clear labeling when users interact with AI agents.
A design approach that keeps a human decision point in workflows involving AI output. Three interaction models: review (user accepts or rejects the AI output wholesale — for low-stakes atomic outputs), approve (user approves before the output takes effect — for medium-stakes changes), and edit (user edits a draft before finalizing — for high-stakes or high-variability outputs). The right model depends on the consequence of a wrong answer.
Four metrics beyond usage volume: acceptance rate (percentage of AI outputs accepted without modification — very high acceptance with no edits may mean users aren’t reviewing), edit distance (how much users change AI outputs — high edit distance indicates poor relevance), repeat use after first correction (whether users who corrected the AI return — the key trust retention metric), and task completion rate with AI versus without.
A marketplace spent four months building a recommendation engine. The model performed well in offline evaluation — precision at ten was strong, the coverage metrics looked good. They shipped it. Conversion moved zero percent. Repeat visit rate didn’t change. GMV per session was flat.
The post-mortem revealed the problem: the recommendations were appearing on a page that users almost never scrolled to, the explanation copy was absent so users didn’t know why they were seeing what they were seeing, and the model was trained on view data from a period when the supply mix was different. The model wasn’t wrong. Everything around it was.
This is the rule, not the exception. In marketplace AI, the model is rarely the bottleneck. The interface around it, and the data it is fed, decides whether matching improves conversion. This article covers where AI matching actually pays off, what data you need before the model, how to design the interface around it, and when heuristics outperform machine learning.
What ‘AI Matching’ Means in a Marketplace
Search Ranking vs Recommendations vs Matching
These three terms are used interchangeably and shouldn’t be.
Search ranking orders results for an explicit query. The user has expressed intent and the system orders results by predicted relevance. AI improves search ranking by learning which signals predict relevance better than keyword overlap alone.
Recommendations surface items the user hasn’t explicitly searched for. They operate on implicit signals — browsing history, saves, purchases — and predict what the user might want next.
Matching is specific to two-sided marketplaces: pairing a buyer with a seller, a requester with a provider, a renter with a listing. Matching considers both sides simultaneously. This is harder than ranking or recommendations because match quality depends on signals from both sides.
One-Sided Personalization vs Two-Sided Matching
Most recommendation systems are one-sided: they optimize for buyer relevance without modeling the supply side. A two-sided matching system considers whether a listing’s seller has capacity, responds quickly, and has historically converted well with buyers similar to this one.
Two-sided matching is significantly more data-intensive and more valuable. Most marketplace platforms should start with one-sided ranking and add supply-side signals only after the one-sided system is performing well.
Where AI Beats a Well-Tuned Filter — and Where It Does Not
AI matching outperforms rule-based filtering when the signal space is high-dimensional, when user preferences vary significantly across the population, and when there is enough interaction data to learn from.
AI does not outperform a well-tuned filter when the marketplace is thin, when user preferences are adequately captured by a small set of explicit attributes, or when the cost of a wrong recommendation makes explainability more important than accuracy.
A marketplace with fewer than one hundred interactions per listing per month is almost always better served by better filtering than by a recommendation model.
The Data You Need Before the Model
Implicit Signals: Views, Dwell, Saves, Abandons
The most reliable training signals for marketplace recommendations are implicit.
View: a user saw this listing. Weak signal on its own; strong when combined with what they didn’t view.
Dwell: how long a user spent on a listing page. A user who spends 90 seconds reading a listing and then leaves is expressing more interest than one who bounced in two seconds. Dwell is underused in most marketplace analytics stacks.
Save or favorite: strong signal of intent, weaker signal of purchase likelihood. Saves correlate with aspiration, not necessarily conversion.
Abandon: the user viewed and didn’t save, contact, or purchase. Used carefully, abandons help the model learn the boundary of a user’s preferences.
The practical requirement: to train a collaborative filtering model with reasonable coverage, you need roughly fifty to one hundred interactions per user and per item in your training set. Below this threshold, the model will over-rely on popularity and produce results that look like a top-ten list rather than personalization.
Explicit Signals and Why Users Rarely Give Them
Explicit signals — ratings, reviews, preference surveys — are high-quality but low-volume. Users who complete a preference survey represent a biased sample. Design for implicit signal collection primarily. Treat explicit signals as a supplement that adds precision for the users who provide them.
The Cold-Start Problem on Both Sides
New users have no interaction history. New listings have no view or purchase data. Both produce cold-start failures: the model falls back to popularity, which is the least personalized outcome.
For new users: use session-level signals immediately, apply geographic and category context, and use one or two onboarding preference questions to reduce cold-start degradation without creating friction.
For new listings: use content-based signals (category, price, attributes, seller history on other listings), place them in exploration slots, and use seller-supplied metadata to seed the content-based fallback.
Feedback Loops and Popularity Bias
A recommendation system that shows popular items gets more interaction on popular items, which makes those items appear more relevant, which causes it to show them more. Left unmanaged, this produces a rich-get-richer spiral where a small number of listings capture most recommendation traffic and new or niche supply becomes invisible.
Manage it with explicit exploration budgets — a defined percentage of recommendation slots allocated to items the model hasn’t yet gathered sufficient signal on — and with supply-side exposure monitoring.
Designing the Interface Around the Model
Placement: Where Recommendations Convert and Where They Annoy
Recommendations convert when they appear at moments of high browsing intent and low task focus.
High-converting placement patterns: “Similar listings” modules on listing detail pages, “Recently viewed” on homepage return visits, “Explore more in [category]” after a purchase or contact. These are the patterns Airbnb, Amazon, and Etsy use in their published interface approaches.
Low-converting or trust-damaging placement: recommendations on checkout or payment pages, recommendations that interrupt task completion, recommendation modules with no visible relationship to what the user is currently doing.
Explaining the Match and When to Stay Silent
Explanation copy — “Because you saved [item]”, “Popular in [location]”, “Similar to your recent searches” — builds trust when the explanation is accurate and the connection is legible. It reduces trust when the explanation is wrong, vague, or reveals tracking behavior the user didn’t realize was happening.
The rule: explain when the reason is specific and verifiable by the user. Stay silent when model confidence is low, when the reason would read as intrusive, or when the explanation would require more context than the UI can provide.
The minimum viable control surface: a “Not interested” dismiss action that removes a listing from recommendations and improves future outputs. Spotify’s “Adjust recommendation” and YouTube’s “Don’t recommend this channel” are examples of control surfaces that improve model output by gathering explicit negative signal while giving users a sense of agency.
Designing Confidence: What to Show When the Model Is Unsure
High-confidence module: “Based on your activity” — personalized results, explanation copy, a “why this?” tooltip available.
Medium-confidence module: “Trending in [category]” — accurate, useful, but not personalized. No false claim of personalization.
Low-confidence or new user module: “Popular right now” or “Top-rated in [location]” — explicitly editorial, no personalization claim. This is more honest and more trustworthy than a poorly personalized “For you” module.
Empty and Low-Confidence States
A recommendation module that can’t generate results should degrade gracefully rather than showing an empty container. Fallback hierarchy: category bestsellers, editorially curated selections, trending items. Each fallback should have its own honest label. An empty recommendation module is worse than a clearly labeled “Popular this week” fallback.
Two-Sided Matching in Practice
Matching Buyers to Sellers vs Ranking Listings
Ranking listings for a search query is a one-sided optimization. Matching buyers to sellers in a service marketplace is a two-sided optimization: maximize fit for both parties, accounting for seller availability, capacity, and historical conversion with similar buyers.
The UX implication: matched results in a service marketplace should communicate seller fit — response rate, typical response time, match quality — not just listing attributes. Upwork’s Job Success Score and Fiverr’s seller level system are examples of supply-side signals surfaced in the interface to support two-sided match evaluation.
Fairness and Supply-Side Exposure
A ranking algorithm that optimizes purely for buyer conversion produces unfair exposure distribution. High-quality, established sellers receive most traffic. New sellers receive almost none. Build supply-side exposure monitoring from the first day you ship a ranking model.
Preventing the Rich-Get-Richer Spiral
Three interventions: exploration slots (a defined percentage of result positions allocated to under-exposed listings), temporal decay (weight recent interactions more than historical ones), and explicit diversity constraints (ensure a minimum number of distinct sellers appear in any given result set).
Measuring Whether It Works
The Metrics That Mislead (CTR, Engagement)
Click-through rate measures whether users clicked, not whether clicking was good for the platform. A recommendation module that shows sensational items will have high CTR and low conversion — and the model will keep optimizing for CTR. Do not use CTR or engagement as primary success metrics for recommendation systems.
The Metrics That Matter (Match Rate, Repeat Rate, GMV per Session)
Match rate: percentage of recommendation impressions that result in a transaction within a defined window.
Repeat rate: percentage of buyers who return within a defined period. If recommendations improve discovery, satisfied buyers return.
GMV per session with recommendations vs without: the most direct measure of whether the recommendation system is moving revenue. Requires a properly instrumented test.
Running an Honest A/B Test on a Thin Marketplace
A/B testing on thin marketplaces produces noisy results. On a thin marketplace, the correct approach is often a staged rollout with careful monitoring rather than a formal A/B test — ship to a small percentage of traffic, monitor the metrics that matter, and expand only when the signal is clear.
Build, Buy or Wait
When Heuristics Outperform a Model
A well-tuned heuristic — “show the highest-rated listing in the user’s searched category that has responded in the last seven days” — will outperform a machine learning model when the marketplace has thin interaction data, when the category space is narrow enough that explicit rules capture most relevant variation, or when deterministic behavior is preferable to probabilistic output.
Build heuristics first. Measure them carefully. Build a model only when heuristics have demonstrably hit their ceiling and you have enough interaction data to train from.
Off-the-Shelf Recommendation Services vs Custom
Off-the-shelf services — AWS Personalize, Google Recommendations AI, Recombee — provide functional recommendation infrastructure without requiring a machine learning team. They are the right choice when your recommendation surface is relatively standard and your engineering team doesn’t have ML expertise.
Custom models are worth building when your matching problem is genuinely two-sided, when your data structure doesn’t fit standard collaborative filtering assumptions, or when you need control over fairness and exposure distribution that off-the-shelf systems don’t provide. See how we’ve approached AI and ML product design in practice, including in products like Hyris where AI-driven matching was a core mechanic.
A Staged Investment Path
Stage one — heuristic baseline: curated lists, category bestsellers, recently viewed. No model required. Measure match rate and repeat rate. Typical effort: two to four weeks of engineering.
Stage two — basic collaborative filtering: train on interaction data once you have sufficient volume. Use off-the-shelf infrastructure. Add explanation copy and basic confidence states to the interface. Typical effort: six to ten weeks including interface work.
Stage three — two-sided signals: add supply-side data to the ranking model. Add exposure monitoring and fairness constraints. Typical effort: ten to sixteen weeks.
Stage four — real-time personalization: session-level signals, real-time model updates, A/B testing infrastructure. Only warranted at significant scale and transaction volume.
Conclusion
A recommendation engine that sits in the wrong place on the page, explains itself poorly, and was trained on stale data will move GMV by zero percent — regardless of the model’s offline performance metrics.
The interface decisions are where the return on AI matching investment is won or lost. Placement, explanation, confidence signaling, and user control determine whether users trust and act on recommendations. The model is a prerequisite. The design is the product.
Before investing in model complexity, invest in heuristic baselines and interface instrumentation. Most marketplace platforms will find that well-designed heuristics close most of the gap — and that the remaining gap is in the interface, not the algorithm.
If you’re evaluating AI matching investment for your platform, book a discovery call.
FAQ
AI matching is ranking or pairing driven by learned signals — interaction history, behavioral patterns, supply-side attributes — rather than explicit keyword filtering. Where a filter returns all listings in a category sorted by recency, a matching system ranks or pairs based on predicted fit for a specific user, drawing on signals the user hasn’t explicitly provided.
The practical threshold is roughly fifty to one hundred interactions per item and per user in your training set. Below this, collaborative filtering models over-index on popularity and produce results indistinguishable from a top-ten list. Below this threshold, invest in better filtering and curation rather than model infrastructure.
Only when two preconditions are met: liquidity is adequate and relevance is already reasonable. Recommendations on a thin marketplace with poor relevance typically produce flat GMV metrics regardless of model quality. The precondition for AI matching to move GMV is a marketplace that already has sufficient liquidity to fulfill the intent recommendations surface.
Three approaches in combination: content-based fallback using category, price, and seller history on other listings; exploration slots that dedicate a defined percentage of recommendation positions to under-exposed new listings; and seller-supplied metadata that seeds the content-based signal at listing creation.
Usually yes, when the reason is specific and verifiable — “Because you saved [item]” or “Popular in [location].” Stay silent or use a generic label when model confidence is low, when the reason would reveal unexpected tracking behavior, or when the explanation would read as intrusive rather than helpful.
Yes, and most platforms should. A heuristic baseline will outperform a poorly trained model on a thin marketplace. Build heuristics first, measure match rate and repeat rate carefully, and invest in a model only when heuristics have demonstrably hit their performance ceiling and interaction data is sufficient to train from.
Your product has nine button variants. Four shades of the same blue. A modal that looks different on every page it appears. A designer who, when asked which is the correct primary button style, opens four different Figma files before giving up.
This is not a design problem. It is a coordination problem — and a design system is the coordination mechanism. But it is also not a problem every product needs to solve with a full design system. Most products that commission one don’t need one yet. Some that need one commission the wrong kind. And most that build one let it decay within six months.
This article covers what a design system actually contains, when building one is the right decision, what it costs, and — the part most guides skip — how to keep it alive after it’s built.
What a Design System Actually Contains
Tokens, Components, Patterns, Guidelines — The Four Layers
A design system has four layers. Conflating them is the most common reason systems are either over-built or under-built.
Tokens are the raw design decisions expressed as named variables: color values, typography scales, spacing units, border radius, shadow definitions. A token is not a color — it is a named relationship between a color and its intended use. color-primary-action: #1A73E8 is a token. #1A73E8 alone is a value.
A token hierarchy for a typical SaaS product works across three levels. Primitive tokens hold raw values — blue-500: #1A73E8, space-4: 16px. Semantic tokens reference primitives with intent — color-button-primary: blue-500, padding-input: space-4. Component tokens reference semantic tokens with scope — button-primary-background: color-button-primary. This three-level structure means a global change propagates without touching component definitions.
Components are the reusable UI elements built from tokens: buttons, inputs, modals, tables, navigation elements. A component in a design system is defined in both Figma and code. A Figma component with no code equivalent is a UI asset, not a system component.
Patterns are compositions of components that solve recurring product problems: an empty state pattern, a data table with sorting and filtering, a notification system. Patterns answer “how do we handle this situation?” rather than “what does this element look like?”
Guidelines are the documented rules governing when and how tokens, components, and patterns are used. Without guidelines, a component library produces inconsistency at a higher level of abstraction — you’ve standardized the button, but seventeen different page layouts still exist because nobody documented how pages should be structured.
The Difference Between a UI Kit and a Design System
A UI kit is a set of Figma assets — organized components, color styles, text styles — that designers use to build screens faster. It solves the design consistency problem for the design team.
A design system includes the UI kit, the corresponding code implementation, a governance model for how changes are proposed and approved, a versioning scheme, and documentation that explains how to use everything correctly. It solves the consistency problem for the entire product organization — design, engineering, and product management.
Most teams that say they have a design system have a UI kit. This is not a failure, but it is a different thing with different capabilities and different limitations.
The Code Side: Why a Figma Library Alone Solves Nothing
A Figma component library that isn’t reflected in the codebase creates a new problem: design and implementation diverge. A real design system requires a code component library — React, Vue, or framework-specific — built from the same tokens as the Figma library. When the primary button color changes, it changes in Figma and in production simultaneously, from one source of truth.
When You Should Build One — and When You Should Not
The Triggers: Team Size, Surface Count, Release Cadence
Three signals indicate a design system investment is warranted: more than one designer working in parallel on the same product, more than one product surface requiring shared design language, and repeated inconsistency bugs appearing in engineering tickets more than twice a month.
Headcount alone is not the signal. A two-person team shipping across a web app, mobile app, and admin panel needs a system more than a ten-person team with one well-maintained surface.
Why Pre-PMF Products Usually Should Not
A design system is infrastructure. Building infrastructure before the product it serves is stable is expensive. If your product hasn’t reached product-market fit, your UI is still changing significantly based on what you learn from users. A design system locks in decisions — about component behavior, token structure, interaction patterns — that are likely to change. The calculus changes when the product stabilizes. If your core flows have been consistent for six months and you’re hiring a second designer, that is the time.
The Middle Path: A Component Inventory Instead
Between “no system” and “full design system” is a component inventory: a documented list of every UI element currently in production, with screenshots, their variations, and which are the intended canonical versions. It takes days rather than months, requires no tooling decisions, and immediately solves the “which button is correct” problem. It is not a design system — but it is the foundation one gets built from, and for many teams it’s sufficient for the next six to twelve months.
Building It Without Stopping the Roadmap
Start From an Audit of What Already Exists
Before creating anything new, document everything that already exists in production. Google’s Material Design was built from an audit of inconsistency across Google products — the team counted 27 different blue values before establishing a token hierarchy. Shopify’s Polaris began with an audit of the Shopify admin UI. In both cases, the audit defined the scope of the work rather than assumptions about what the system needed.
Tokens First, Components Second
The most common sequencing mistake: starting with components before establishing tokens. Components built without a token foundation embed raw values directly into their definitions. When those values need to change, every component must be updated individually. Establish tokens first. Build components that consume tokens, not raw values. Token changes then propagate automatically to every component that uses them.
Adopt Incrementally: The Next-Feature Rule
Do not pause the roadmap to build the design system as a standalone project. Instead, apply the next-feature rule: the next feature that gets built uses system components. When a system component doesn’t exist for what’s needed, it gets built as part of that feature’s scope. This approach means the system grows alongside the product, is tested against real product needs rather than hypothetical ones, and never becomes a blocking dependency for shipping. IBM’s Carbon Design System was adopted across IBM’s product portfolio incrementally over eighteen months rather than in a single migration.
Accessibility Baked In, Not Retrofitted
Accessibility compliance — WCAG 2.1 AA as a minimum — is significantly cheaper to build into a design system than to retrofit into a production codebase. Color contrast ratios, focus states, keyboard navigation, ARIA labeling become default behaviors of system components rather than per-feature considerations. The cost of retrofitting accessibility into a SaaS product that hasn’t considered it is routinely underestimated.
What It Costs
Initial Build: Effort by Product Size
For a focused SaaS product with one primary surface: six to ten weeks of dedicated designer time plus four to six weeks of engineering time to build the code library.
For a multi-surface SaaS product — web app, mobile, admin panel — with cross-surface consistency requirements: twelve to twenty weeks of designer time plus eight to twelve weeks of engineering time.
These estimates assume the system is being built alongside the roadmap. A standalone project compresses the timeline but typically produces a system that doesn’t reflect real product needs as accurately.
The Ongoing Cost Everyone Forgets
A design system has a maintenance cost from the day it ships. Component updates when the product evolves. Token changes when the brand updates. Deprecation of components no longer used. Documentation updates when behavior changes. New component creation when new features require them.
This ongoing cost is typically ten to twenty percent of a senior designer’s time and five to ten percent of an engineer’s time, indefinitely. Teams that build a system without planning for this cost end up with one that decays — which is worse than not having one, because decay is invisible until it’s severe.
Where the Savings Actually Show Up
The return shows up in three places: reduced design time (thirty to fifty percent faster for screens within system coverage), reduced engineering time (twenty to forty percent faster implementation), and reduced QA time (fewer inconsistency bugs, clearer expected behavior). The savings compound over time as coverage increases and are largest when the product is shipping at high velocity across multiple surfaces.
Keeping It Alive
Ownership Models: Central Team, Federated, Hybrid
Central ownership: a dedicated team or individual owns the system, reviews all contributions, and controls releases. Produces the most consistent system. Becomes a bottleneck at scale.
Federated ownership: teams own their own component domains. Faster iteration. Produces drift between domains without strong governance.
Hybrid: a small central team owns tokens and core components. Feature teams own domain-specific components and contribute back through a defined process. This is the model both Material Design and Polaris operate on at scale — and it’s appropriate for most growth-stage SaaS teams.
Contribution and Deprecation Workflows
Without a defined contribution process, the system grows by accretion — components get added without review, creating redundancy. Without a deprecation process, old components stay alongside replacements, creating confusion about which is canonical.
A minimal contribution workflow: propose, review, build, approve and merge. A minimal deprecation workflow: announce, migrate, remove after a defined period.
Versioning and Breaking Changes
Adopt semantic versioning from the start. Major versions introduce breaking changes. Minor versions add functionality without breaking changes. Patch versions fix bugs. Document breaking changes explicitly and give consuming teams a migration period. This is the difference between a system teams trust and one they fork to avoid.
Measuring Adoption and What to Do When It Stalls
Track adoption as a percentage of production UI covered by system components. A new system should aim for sixty to seventy percent coverage within six months. Below forty percent at six months signals that the system doesn’t cover what teams actually need, or using it is slower than improvising. Fix the friction rather than mandating adoption.
Common Failure Modes
The System Nobody Uses Because It Is Slower Than Improvising
A design system that makes designers and engineers slower to ship will be abandoned, regardless of how technically correct it is. If using a system component requires more steps than writing a one-off solution, teams will write the one-off solution. Speed of use is a first-class requirement.
Over-Abstraction: Components With Nineteen Props
A button with nineteen configuration props is not a component — it is an interface that requires reading documentation to use correctly. Build for the cases that actually exist. Add props when real product needs require them, not in anticipation of hypothetical future needs.
Documentation That Went Stale in Month Three
Documentation that doesn’t reflect current component behavior is worse than no documentation — it produces incorrect implementations that look correct. Treat documentation as a deliverable of every component change. Merge requests that change component behavior require documentation updates before they’re approved.
Conclusion
A design system is infrastructure. Like all infrastructure, it should be built when the cost of not having it exceeds the cost of building and maintaining it — and not before.
When the triggers are present — multiple designers, multiple surfaces, visible inconsistency — a system investment pays back quickly and compounds over time. When they’re not, a component inventory and a shared Figma library are sufficient.
The systems that survive are the ones with an owner, a governance model, and a version history. The ones that fail are treated as a project that ends at launch.
If your SaaS product’s UI has drifted and you’re evaluating whether a design system is the right investment, the starting point is usually a UI/UX audit — inventory what exists before deciding what to build. See how we’ve approached design systems across our case studies. Book a scoping call to discuss your specific situation.
FAQ
A design system has four layers: tokens (named design decisions like color values and spacing), components (reusable UI elements built from tokens), patterns (compositions of components for recurring product problems), and guidelines (rules governing when and how each layer is used). A design system is distinct from a component library — it includes governance, versioning, and documentation, not just assets.
Three concrete triggers: more than one designer working in parallel on the same product, more than one product surface requiring visual consistency, and repeated engineering tickets about inconsistency. Headcount alone isn’t the signal — a two-person team shipping across four surfaces needs a system more than a ten-person team with one.
For a focused SaaS product: six to ten weeks of designer time plus four to six weeks of engineering time. For a multi-surface platform: twelve to twenty weeks of design plus eight to twelve weeks of engineering. Adoption takes longer than creation — seventy percent production coverage at six months is ahead of average.
A UI kit is a Figma asset library — components and styles for designers to use when building screens. A design system includes the UI kit, a corresponding code library, governance rules for how changes are proposed and approved, semantic versioning, and documentation. A UI kit solves design-side consistency. A system solves it across design and engineering simultaneously.
Yes, in specific cases: when speed to market matters more than brand differentiation, when your team lacks dedicated design system capacity, or when your product’s visual identity is flexible. The long-term cost is real — Material UI’s component API shapes your UI decisions and significant customization becomes progressively harder. Polaris and Carbon are worth studying for their token architecture even without full adoption.
A named owner is non-negotiable — unowned systems decay predictably. Central ownership produces consistency but creates bottlenecks at scale. Federated ownership moves faster but drifts without governance. The hybrid model — a small central team owns tokens and core components, feature teams contribute domain components — is the right default for most growth-stage SaaS companies.
A SaaS company spent eight months and $340,000 building a reporting module. It launched. Two percent of users opened it in the first month. Post-launch interviews revealed that the users the product was built for — operations managers — had their reporting needs fully covered by a spreadsheet export they’d set up two years ago. Nobody had asked them.
That is not a development failure. It is a discovery failure. The most expensive version of building the wrong thing is the one where you build it all the way to launch before you find out.
Discovery is not a slower start. It is the cheapest place to be wrong. A flow change in a Figma file costs hours. The same change in a shipped codebase costs weeks. This article covers what discovery actually produces, how long it takes, what it costs, and how to judge whether an agency’s discovery proposal is genuine or theater.
What a Discovery Phase Is (and What It Is Not)
Discovery vs Requirements Gathering
Requirements gathering is a documentation exercise. Someone describes what they want. The output is a specification. The specification is then built.
Discovery is an investigation. The starting question is not “what do you want to build?” but “what problem are you actually solving, for whom, and how do you know?” Requirements gathering assumes the problem is understood. Discovery tests that assumption before committing to a solution.
A requirements document says “users need a dashboard with five widgets.” A discovery process asks why those five widgets, whether users actually use dashboards, and what decision the dashboard is supposed to help users make. The answers are frequently different from the requirements.
Discovery vs a Design Sprint
A design sprint — the Google Ventures format — is a five-day intensive that produces a tested prototype of a specific solution. It is useful when the problem is understood and the goal is to prototype and test a solution quickly.
Discovery is broader and slower. It investigates whether the problem is real, who has it most acutely, and what constraints any solution must operate within. Running a design sprint in place of discovery assumes the problem definition is correct — which is exactly the assumption discovery is meant to test.
The Three Risks Discovery Is Meant to Reduce: Value, Usability, Feasibility
Every SaaS product fails for one of three reasons: it doesn’t solve a problem people have (value risk), it solves the problem but nobody can figure out how to use it (usability risk), or it can’t be built within available technology and resources (feasibility risk).
Discovery addresses all three before significant development investment is made. Week one typically addresses feasibility and constraints. Week two addresses value risk through user research. Week three addresses the competitive landscape. Week four produces the scoped, prioritized output that development can begin from.
The Discovery Process, Week by Week
Week 1 — Business Model, Constraints and Success Criteria
The first week is internal. The goal is to align on what success looks like before any research is conducted.
This includes: the business model and how the product makes money, the technical constraints (existing systems, APIs, infrastructure), the budget and timeline constraints, the regulatory context if relevant, and the definition of success — specifically, what metrics will be different in twelve months if the product works.
This week produces a constraints document and a success criteria framework. Without it, research and design are conducted without a filter for what actually matters to the business.
Week 2 — User Research and Jobs to Be Done
Week two involves talking to the people the product is being built for. Typically five to eight interviews with users or potential users in the target segment — enough to identify patterns without over-indexing on individual responses.
The framework that produces the most useful output for SaaS product design is Jobs to Be Done (JTBD): what job is the user trying to accomplish, what are they currently using to accomplish it, what is frustrating about the current solution, and under what circumstances would they switch.
This week produces user archetypes (behavior-based descriptions of how different user types approach the problem), a jobs-to-be-done map, and a documented set of unmet needs ranked by frequency and severity.
Week 3 — Competitive and Solution Landscape
Week three maps the existing solution landscape: what alternatives users currently use, what those alternatives do well and poorly, where the gap is, and what your product needs to do better to earn adoption.
This is not a feature comparison table. It is an analysis of how each alternative earns and loses users, and what the switching trigger is. A SaaS product entering a market where users are deeply embedded in an incumbent needs a different strategy than one entering a market served by spreadsheets and manual processes.
This week produces a competitive positioning map and a differentiation brief — a clear statement of what your product does better than the available alternatives for the specific user segment you’re targeting.
Week 4 — Scope, Architecture Direction and Roadmap
Week four synthesizes the previous three weeks into actionable output: a validated problem statement, a prioritized feature scope, a technical architecture direction, an integration map (what third-party systems the product needs to connect to), and a costed roadmap.
The prioritized scope is organized by impact on the validated user jobs and constraints. Features that don’t map to a validated user job are deprioritized or cut. Features that map to the highest-frequency, highest-severity user needs are in scope for the first release.
How the Timeline Changes for a Complex Platform
A four-week discovery process is appropriate for a focused SaaS product with a reasonably understood user base. Multi-sided platforms require a longer process because each side has separate user research, separate jobs, and potentially separate technical architectures.
A marketplace discovery process typically runs six to eight weeks: two weeks per distinct user type plus synthesis and scoping. Compressing this produces a discovery output that has mapped one side of the market well and guessed at the other.
What You Actually Get at the End
Validated problem statement and success metrics. A one-page document describing the problem, who has it, how you know it’s real, and what measurable outcomes define success. This is the filter every subsequent product decision is evaluated against.
User flows and information architecture. How users move through the product to accomplish their primary jobs, and how information is organized. This is the foundation of UI/UX design for SaaS — not a wireframe, but the structure wireframes are built from.
Clickable prototype or lo-fi wireframes. A testable representation of the primary flows. Rough enough that users respond to the structure rather than the aesthetics. This is the artifact that gets tested with users before any production code is written.
Technical feasibility notes and integration map. A documented assessment of the technical approach, the third-party integrations required, and any constraints or risks in the proposed architecture. Specific enough to inform scoping without being a full technical specification.
Prioritized scope and a costed roadmap. A phased breakdown of what gets built, in what order, and at what approximate cost. Phase one is what’s needed to test the core value proposition with real users.
A slide deck with research themes and opportunity areas is not a discovery deliverable. It is research without synthesis that doesn’t unblock any specific design or engineering decision.
What Discovery Costs and How to Judge the Return
Typical Cost and Duration by Product Complexity
For a focused SaaS product with a defined user base: four weeks, $15,000–$30,000. This covers stakeholder alignment, five to eight user interviews, competitive analysis, lo-fi wireframes for primary flows, and a prioritized scope document.
For a multi-sided platform or a SaaS product with complex integrations: six to eight weeks, $30,000–$60,000. The additional cost reflects research across multiple user types and more complex technical feasibility assessment.
For an enterprise SaaS product with regulated use cases or significant compliance requirements: eight to twelve weeks, $50,000–$100,000+.
The Rework Arithmetic: Changing a Flow vs Changing a Codebase
The cost of changing a user flow in a Figma prototype is measured in hours. Moving a step in an onboarding sequence, adding a field to a form, removing a feature that turns out to be unnecessary — these are low-cost changes before development.
The same changes after development cost more by an order of magnitude. McKinsey research (2022) found that fixing defects after launch is five to ten times more expensive than fixing them during the design phase. Discovery makes the high-cost changes happen at the lowest-cost point in the project.
When Discovery Is Not Worth It
Discovery is not always the right investment. Three situations where it isn’t:
The problem is genuinely well understood. If you have already built version one, operated it with real users for six months, and have clear data on what’s not working, you need a product audit and a redesign brief — not a full discovery process.
The scope is deliberately narrow. If you are building a specific, well-defined feature for a user base you know well, a two-day workshop and a round of prototype testing may be sufficient.
Speed is the constraint and being wrong is recoverable. In some market contexts, getting something live quickly and learning from real usage is more valuable than a thorough pre-launch investigation. This requires that being wrong early is genuinely recoverable — which is rare in B2B SaaS where users have switching costs.
Running Discovery Well
Who Needs to Be in the Room
Discovery requires three types of involvement from the client side: a decision-maker who can approve scope changes without escalating, a domain expert who understands the industry context and can evaluate whether research findings are real, and someone who talks to customers weekly and can validate or challenge what research surfaces.
Discoveries that involve only founders or only engineers routinely miss significant user context. Discoveries that involve only users miss significant business and technical constraints.
How Many Interviews Are Enough
Five to eight interviews with users in the same segment will surface the majority of patterns. Nielsen Norman Group research (2000, updated 2023) established that five users identify approximately 85% of usability problems in a given interface. Diminishing returns set in quickly after the first five to seven interviews.
If your product serves multiple distinct user types, you need five to eight interviews per segment — not per product.
Killing Your Own Idea: Making ‘Stop’ an Acceptable Outcome
Discovery should be capable of producing a “stop” recommendation — a finding that the problem isn’t real enough, the market is too small, or the technical constraints make the product unviable.
Most discovery processes are commissioned with an implicit assumption that they will produce a “build” recommendation. A genuine discovery process includes the explicit agreement, upfront, that a “stop” finding is a legitimate outcome — it is far cheaper than building the wrong product.
Red Flags in an Agency’s Discovery Proposal
No user interviews in the proposed scope
Deliverables described as “insights deck” or “research report” without specified design artifacts
Timeline shorter than two weeks for any product with external users
No mention of success metrics or how the discovery output connects to investment decisions
Discovery scope doesn’t include any technical feasibility assessment
No explicit process for incorporating findings that contradict the client’s assumptions
Conclusion
Discovery is the cheapest place to be wrong about what to build. The deliverables it produces — validated problem statement, user flows, clickable prototype, integration map, costed roadmap — are the foundation that every subsequent design and engineering decision builds from.
The arithmetic is straightforward: a $20,000 discovery process that prevents a $150,000 rebuild is a return that no other investment in your product cycle can match.
If you’re commissioning SaaS UI/UX design or a product build and want to understand what a genuine discovery process looks like for your specific product, book a scoping call. We’ll tell you whether discovery is the right investment for where you are. Learn more about us and how we approach product discovery.
FAQ
A product discovery phase is a structured investigation before design or development begins. It reduces three risks: value risk (building something nobody needs), usability risk (building something nobody can use), and feasibility risk (building something that can’t be built within constraints). It produces validated problem statements, user flows, wireframes, and a prioritized scope.
For a focused SaaS product: four weeks. For a multi-sided platform with multiple user types: six to eight weeks. For enterprise SaaS with regulatory requirements: eight to twelve weeks. What drives the difference is the number of distinct user segments requiring separate research and the complexity of the technical integration landscape.
Focused SaaS: $15,000–$30,000. Multi-sided platform: $30,000–$60,000. Enterprise SaaS: $50,000–$100,000+. Evaluate this against the cost of building the wrong thing. McKinsey research (2022) found that fixing defects after launch is five to ten times more expensive than fixing them during design. Discovery makes the expensive changes happen at the cheapest point.
A spec answers what to build. Discovery answers why this, for whom, and whether the assumptions behind the spec are correct. Skipping is reasonable in one case: you have already built and operated version one and are redesigning based on observed behavior — not assumptions. In that case, a product audit is the more appropriate investment.
A validated problem statement, user flows and information architecture, clickable prototype or lo-fi wireframes, technical feasibility notes and an integration map, and a prioritized scope with a costed roadmap. A slide deck of research themes is not a discovery deliverable — it doesn’t unblock any specific design or engineering decision.
Three roles: a decision-maker who can approve scope changes without escalating, a domain expert who understands the industry context, and someone who talks to customers weekly and can validate or challenge what research surfaces. Discovery conducted with only founders or only engineers routinely misses significant context that changes the output.
The wallet modal appears. A significant share of users — consistently measured at 40-60% across Web3 products — close the tab and never return. Not because the product is broken. Not because the feature set is wrong. Because something in those first seconds created a feeling that a mistake here could not be undone.
That feeling has a name: irreversibility anxiety. And it is the actual cause of most Web3 onboarding failure — not complexity, not technical literacy, not a poor feature list. Users who understand that a wrong action could permanently lose their funds respond to uncertainty by doing nothing.
This article covers what happens in the first 90 seconds of a Web3 onboarding flow, where the drop-off actually occurs, and how to design for the fear rather than the feature. If you’re building for a Web3 or DeFi platform, this is the framework that matters before you design a single screen.
Why Web3 Onboarding Drops Users
Irreversibility Anxiety: The Real Reason People Freeze
Web2 products are built on reversibility. Clicked the wrong button? Undo. Sent money to the wrong person? Call your bank. Created the wrong account? Delete it. Users have been trained over twenty years that digital actions are recoverable.
Web3 breaks this assumption at the infrastructure level. A transaction confirmed on-chain cannot be reversed. A seed phrase lost cannot be recovered. A token approval granted cannot be automatically revoked. These facts are true and material — and most Web3 products communicate them badly, which produces the worst possible outcome: users who sense the stakes but don’t understand the specific risks.
The design problem is not making irreversibility less real. It’s making the specific risks legible so users can act with appropriate confidence rather than freezing under vague fear.
Vocabulary as a Barrier (Gas, Approve, Sign, Bridge)
Every term that appears in a Web3 interface without explanation is a decision point where a user must choose between proceeding without understanding and abandoning the flow. Most choose abandonment.
Gas, approve, sign, bridge, allowance, nonce, slippage — these are precise technical terms with no mainstream equivalent. Uniswap has progressively replaced raw technical vocabulary with plain-language alternatives: “Network fee” instead of “gas fee.” “Allow Uniswap to use your USDC” instead of a raw approval transaction. The underlying mechanic is unchanged. The user’s ability to act on it is meaningfully improved.
The Wallet Modal Is a Dead End for Non-Holders
A wallet connect modal assumes the user has a wallet. A significant share of users arriving at a Web3 product for the first time do not. Showing a modal with options for MetaMask, Coinbase Wallet, WalletConnect, and Phantom to a user who has none of them installed is a dead end.
Coinbase Wallet has addressed this by surfacing a “Create a new wallet” option as a first-class path in their connect modal alongside existing wallet options. Phantom does the same. The principle: the wallet modal should serve users who don’t have a wallet as a primary case, not an afterthought.
The First 90 Seconds, Step by Step
Second 0-15: Show Value Before Asking for a Wallet
The product should be visible and usable — at least in a read-only state — before a wallet connection is requested. A user who can see what the product does, explore the interface, and understand the value proposition before being asked to connect is more likely to connect than a user whose first interaction is a wallet modal.
Uniswap allows full price exploration and interface exploration before asking for a wallet connection. The connection is required only to execute a swap. Connect rate on this model is higher than on products that gate all functionality behind wallet connection.
Before: user arrives → wallet modal appears immediately → user with no wallet exits. After: user arrives → browses product in read-only mode → decides to transact → wallet connection requested in context → user connects or creates wallet inline.
Second 15-40: Connect Without Committing
The wallet connection request should be clearly scoped. Most users — particularly those new to Web3 — do not understand the difference between connecting a wallet (read-only access to address and balance) and approving a transaction (permission to move funds).
Phantom labels the connection step as “Read your wallet address and balance” — not “Access your funds.” The language matters. A user who understands they’re sharing an address, not granting fund access, is less likely to freeze.
Design the connection step to communicate: what information the product can see, what it cannot do, and that connecting is reversible.
Second 40-70: The First Signature and How to Explain It
The first signature request is the highest drop-off moment in most Web3 onboarding flows. A signature popup shows a hex string, a domain, and a message that means nothing to a non-technical user.
The product interface can pre-explain the signature before the wallet popup appears. “You’re about to sign a message to verify you own this wallet. This doesn’t cost anything and doesn’t move any funds.” This pre-explanation, placed before the popup is triggered, significantly reduces abandonment.
Coinbase Wallet redesigned their signature confirmation to show plain-language descriptions of what is being signed alongside the technical data. The user sees “Sign in to [Product Name]” rather than a raw EIP-712 payload.
Second 70-90: Confirmation and the Next Obvious Action
After a successful connection or first signature, most Web3 products return the user to the same state they were in before. This is a missed moment. The first 90 seconds should end with an explicit confirmation and a clear next action.
“You’re connected. Your balance: 0.5 ETH. Ready to swap?” is more effective than returning silently to the main interface. Phantom’s onboarding ends with an explicit “Your wallet is ready” state with the first recommended action surfaced directly.
Custody Models and What They Cost You in UX
Self-Custody: Maximum Trust, Maximum Friction
Self-custody means the user controls their private key directly. No platform can access, recover, or move their funds without their authorization. This is the model MetaMask, Phantom, and hardware wallets operate on.
The UX cost: the user must manage key material. Seed phrase backup is required. Recovery is impossible without it. Self-custody is appropriate for users who have chosen it knowingly and understand the responsibility.
Embedded and Smart-Contract Wallets
Embedded wallets — provided by Privy, Dynamic, and Magic — create a wallet for the user without requiring them to manage a seed phrase directly. Smart-contract wallets, enabled by ERC-4337 (account abstraction), can support social recovery, session keys, and gas sponsorship.
The UX benefit: users can onboard without seed phrases, gas can be abstracted away, and recovery paths exist. The trade-off: the user is trusting the infrastructure provider’s security model rather than their own key management.
Social Login and Account Abstraction
Social login — connecting with a Google, Apple, or email account — is the lowest-friction onboarding path available. Account abstraction makes this viable at scale: gas can be sponsored by the platform and the user experience approaches Web2 in smoothness.
The custody trade-off should be disclosed clearly: the user’s key is controlled by or recoverable through the social login provider’s infrastructure.
Choosing Based on Who Your User Already Is
Self-custody is appropriate for crypto-native users who have actively chosen to manage their own keys. Embedded wallets and social login are appropriate for products targeting mainstream users primarily interested in the application, not the underlying infrastructure.
The wrong approach: defaulting to self-custody because it feels more Web3, then trying to design away the resulting friction.
Designing the Hard Moments
Seed Phrase Backup Without the Wall of Text
The seed phrase is the single highest-stakes moment in self-custody onboarding. Deferred backup works: allow the user to skip seed phrase backup for the first session, reach product value, and then surface the backup as an urgent task with a clear explanation of what is at risk.
Chunked steps work: present the phrase in groups of four words. Break the backup process into record, close, verify. Each step is smaller and less overwhelming.
Token approval grants a smart contract permission to spend a user’s tokens. Unlimited approval means the approved contract can spend any amount of the approved token at any future time.
Uniswap now offers a “Set specific spending limit” option alongside the unlimited default — with a plain-language explanation of what each means. This is the correct pattern: explain the trade-off, default to the more cautious option.
Gas Fees, Failed Transactions and Pending States
Gas fees should appear as a total fiat cost before the user confirms a transaction. “This transaction will cost approximately $3.40 in network fees” is actionable. Failed transactions need explicit designed states: “Your transaction failed. No funds were moved. Network fees of $0.80 were charged.” Pending states need progress indicators and an explicit statement that funds are not lost.
Chain Switching Without Losing Context
Phantom handles chain switching well: the current network is always visible in the header, the switch confirmation is brief and clearly scoped, and the user is returned to the same point in the interface after switching. Returning the user to the homepage after a chain switch produces unnecessary abandonment.
Trust UX in a Trustless Product
Audits, Proof of Reserves and Where to Surface Them
Security claims should be specific and verifiable. “Audited by [Firm Name] — view the report” is a trust signal. “Industry-leading security” is not. Surface audit information at the point of risk — near token approval flows, before large transactions — not only in a footer.
Transaction Preview and Simulation
Transaction simulation — showing the user the expected outcome before they sign — is one of the most effective trust-building mechanics in Web3 UX. “You will send 100 USDC and receive approximately 0.045 ETH. Network fee: $2.10.” Rabby Wallet pioneered this in a consumer wallet interface. Uniswap has since added it. It should be standard in any product where users sign consequential transactions.
Designing for the Scam-Aware User
A growing share of Web3 users have personal experience with phishing or drainer contracts. Design for this user: consistent domain, no unexpected redirects, clear provenance for all contract interactions, and approval requests that explain what is being approved and why.
Connect rate: percentage of users who complete a wallet connection out of those who see the connection prompt. Below 40% in a non-crypto-native audience typically indicates the connection flow needs redesign.
First-transaction rate: percentage of connected users who complete at least one transaction. The gap between connect rate and first-transaction rate reveals where friction sits after connection.
Signature abandonment: percentage of users who see a signature request and don’t complete it. This is the highest-signal metric for irreversibility anxiety in your specific flow.
Instrumenting a Funnel When You Cannot Track a User
Track wallet modal open, wallet selected, connection confirmed, first signature presented, first signature completed, first transaction submitted. These events describe the funnel within a single session — sufficient for onboarding optimization without requiring cross-session identity.
Conclusion
Web3 products don’t lose users because the technology is hard. They lose users because the interface communicates risk without communicating safety, uses vocabulary that signals expertise required, and asks for commitment before demonstrating value.
Design the first 90 seconds to show value before asking for a wallet, explain every irreversible action before it’s taken, and choose a custody model that matches your user’s actual sophistication — not the sophistication you wish they had.
The two highest drop-off points are the wallet connection modal — where users without a wallet have no path forward — and the first signature request, where irreversible consequences are implied but not explained. The primary cause is irreversibility anxiety: users sense that a mistake could be permanent, don’t understand the specific risks, and respond by doing nothing.
No. Read-only browsing consistently produces higher connect rates than gating all functionality behind wallet connection. A user who has already decided they want to use the product is more motivated to complete the connection flow than one who hasn’t seen the product yet.
Account abstraction (ERC-4337) allows wallets to be implemented as smart contracts, enabling gas sponsorship, social recovery, and social login. It significantly reduces friction for mainstream users. It does not solve vocabulary barriers, trust communication, or the challenge of explaining irreversibility clearly.
Show the total cost in fiat before the user confirms — never as an ETH amount after they click. Name what the fee pays for: “This fee goes to the network that processes your transaction, not to us.” Never present gas as a surprise at signature time.
It depends on the custody model. Social login via Privy or Web3Auth uses MPC (Multi-Party Computation) or TEE (Trusted Execution Environment) infrastructure to secure key material. The user’s funds are as safe as that infrastructure’s security model — strong, but not equivalent to self-custody. Disclose the trade-off clearly.
Four mechanics: deferred backup (let users reach product value before requiring backup), chunked steps (present the phrase in groups of four), a verification quiz (require confirmation of specific words in order rather than a checkbox), and an explicit statement of consequences: “If you lose this phrase, no one — including us — can recover your funds.”
Taras Oliinyk
CEO at U1CORE
Book an introduction call
During this call we do a quick intro and discuss your project and its
specific needs.
Let's talk about your project
Book a free consultation with us, so we will frame your product vision and strategy.
We’ve received your request and our team is already reviewing
it. We’ll get back to you as soon as possible to discuss how
we can help you achieve your goals.
Looking forward to collaborating with you!
Thank you for your interest in our Web3 eBook!
We’ve sent the download link to your email. Check your inbox
(and spam folder just in case) to access the eBook.
We hope you find it valuable for your Web3 journey. If you
have any questions or feedback, feel free to reach out!
FREE E-BOOK
We want your Web3 website to be great even if you don't hire us.
Master 30 proven Web3 design strategies;
Learn from the best case studies: Uniswap, OpenSea, Aave;
Implement user-centred UX/UI for higher engagement;
Stay ahead with emerging Web3 design trends for 2025.
We value your privacy
We use cookies to enhance your browsing experience, analyze site traffic, and personalize content.
By clicking “Accept all”, you consent to our use of cookies.
Read our Privacy Policy for more details.
