Author: Taras Oliinyk

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

• What is a product discovery phase?

  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.

• How long does a discovery phase take?

  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.

   

• How much does a discovery phase cost?

  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.

• Can we skip discovery if we already have a spec?

  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.

• What deliverables should a discovery phase produce?

  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.

• Who should be involved from our side?

  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 Approvals: Explaining Unlimited Allowance Honestly

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.

What to Measure

Connect Rate, First-Transaction Rate, Signature Abandonment

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.

If you’re designing or rebuilding the onboarding flow for a Web3 or DeFi platform, book a discovery call. Download our free Web3 design e-book for a deeper framework on designing for Web3 users.

FAQ

• Why do users abandon Web3 apps during onboarding?

  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.

• Should a Web3 product require a wallet to browse?

  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.

• What is account abstraction and does it fix onboarding?

  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.

• How do you explain gas fees to a first-time user?

  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.

• Is social login safe for a crypto product?

  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.

• How do you back up a seed phrase without scaring people?

  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.”

A platform launched in one market, processed payments through a single provider, and grew to fourteen countries in eighteen months. In month fourteen, they tried to pay out to sellers in Brazil and the Philippines. Their payment provider didn’t support either market. Re-architecting payments on a live platform — with real sellers, real buyers, and real funds in transit — cost them six months of engineering time and two key markets to a competitor who had solved this on day one.

The payment model is not a technical detail to revisit after launch. It determines your compliance burden, your unit economics, and your international roadmap before you write a line of product code. This article covers the four payment models available to multi-sided platforms, how split payments work mechanically, what payouts actually cost, and how to choose a stack that won’t trap you.

This is not legal or financial advice. Get qualified counsel before making payment architecture decisions.

---

The Four Payment Models for Multi-Sided Platforms

Pass-Through (Buyer Pays Seller Directly)

In a pass-through model, the buyer pays the seller directly. The platform facilitates the introduction but is not in the money flow. The platform charges separately — typically via subscription or invoiced commission — rather than taking a cut of the transaction at the point of payment.

This is the simplest model to build and the most limited. The platform has no hold on funds, no ability to enforce a commission at the point of payment, and no recourse when a transaction fails. It works for high-trust B2B categories where sellers invoice buyers and the platform’s value is in the match, not the transaction. It does not work for consumer marketplaces where trust and protection are part of the product.

Liability sits with the seller. The platform has no financial exposure to individual transaction failures.

Aggregator / Payment Facilitator

A payment facilitator (PayFac) is an entity that processes payments on behalf of sub-merchants — in a marketplace context, on behalf of sellers. The PayFac holds the master merchant account with a card network or acquirer and onboards sellers as sub-merchants underneath it.

The platform collects the full buyer payment, deducts its commission and fees, and pays out the remainder to the seller. This is the model Stripe Connect, Adyen for Platforms, and Mangopay operate on — they provide the PayFac infrastructure and the platform uses it.

Becoming your own PayFac requires direct registration with card networks, an underwriting process, and significant ongoing compliance obligations. Most platforms should use a provider that already is a PayFac and let it absorb the regulatory burden.

Liability: platform is liable for chargebacks and refunds on transactions it processes.

Merchant of Record

A merchant of record (MoR) is the entity legally responsible for the sale — the name on the receipt, the entity collecting VAT (Value Added Tax) or GST (Goods and Services Tax), the party liable for chargebacks and refunds. When a platform becomes the MoR, it takes full legal ownership of every transaction on its platform.

Platforms that become MoR typically do so to simplify tax compliance for their sellers (the platform handles all VAT/GST centrally) or to offer a fully branded checkout experience without third-party interruption.

Liability: platform absorbs full liability for all transactions, refunds, chargebacks, and tax obligations.

Marketplace with a Regulated Partner

The most common model for early and growth-stage platforms: partner with a regulated payment provider that acts as the licensed entity, holds funds, and manages compliance, while the platform controls the product experience on top.

Stripe Connect, Adyen for Platforms, Mangopay, and Rapyd all operate this way. The compliance obligations sit primarily with the provider — though the platform still inherits KYC (Know Your Customer) and AML (Anti-Money Laundering) obligations for its seller onboarding.

Liability: shared between platform and provider. The provider handles regulatory compliance. The platform handles product experience and seller verification.

How Each Model Changes Who Is Liable

Pass-through puts liability on the seller. The PayFac model puts chargeback and refund liability on the platform. MoR puts full liability on the platform including tax. The regulated partner model shares liability — the provider handles funds and compliance, the platform handles the product layer.

The model you choose is a liability decision before it’s a technical decision.

Split Payments Explained

Splitting at Capture vs Splitting at Payout

A split payment is one buyer payment divided between multiple recipients — the seller, the platform’s commission, and in some cases, additional parties such as logistics providers or referral partners.

The split can happen at two points: at capture (the payment is split into separate transfers the moment the buyer pays) or at payout (the full amount is captured into a platform account and distributed in separate transfers at a later point).

Splitting at capture is simpler from a ledger perspective but less flexible for platforms that need to hold funds before releasing them. Splitting at payout gives the platform more control over timing and allows it to implement dispute holds before releasing seller funds.

Handling Commission, Taxes and Processing Fees in One Transaction

A single transaction on a marketplace typically involves: the buyer’s total payment, the payment processing fee charged by the provider (typically 1.5-3.5%), the platform’s commission, any applicable taxes, and the seller’s net payout.

Design your commission logic to operate on the net amount after processing fees, not the gross — otherwise your effective margin shrinks at high transaction volumes.

Multi-Seller Carts and Partial Fulfilment

When a buyer purchases from multiple sellers in one checkout, the payment architecture needs to handle splits to multiple recipients from a single capture. Partial fulfilment — one seller ships, another doesn’t — requires partial release logic and a clear buyer-facing view of which part of their order is in what state.

Payouts: The Part Founders Underestimate

Payout Schedules and Their Effect on Seller Retention

How fast sellers get paid is a supply-side retention lever. Sellers on platforms with faster payouts churn less. The trade-off: faster payouts increase exposure to fraud and dispute losses.

Typical payout schedules by category: physical goods, 3-7 days after delivery confirmation; services, 5-14 days after completion; digital goods, 24-48 hours; high-value transactions such as vehicles or B2B contracts, 14-30 days or on explicit buyer acceptance.

Cross-Border Payouts, FX and Local Rails

Paying out to sellers in multiple countries requires currency conversion (FX — Foreign Exchange), access to local payment rails (SEPA in Europe, ACH in the US, UPI in India, PIX in Brazil), and in some markets, local bank account registration.

FX costs are real and often underestimated. A platform paying out $1M per month to sellers in five currencies at a 1.5% FX spread loses $15,000 per month to currency conversion. Evaluate provider FX rates explicitly — they vary significantly between Stripe, Adyen, Rapyd, and dedicated providers like Wise for Business.

Local rails matter for seller activation. A seller in Indonesia who can only receive a SWIFT wire transfer waits 3-5 business days. A seller who receives via local bank transfer gets funds the same day. Payout friction directly affects retention in markets where local rails aren’t supported.

Failed Payouts, Negative Balances and Clawbacks

Payouts fail. Bank account details change. Every platform needs a failed payout handling flow: retry logic, seller notification, a queue for unresolved payouts, and a policy for what happens to funds that can’t be delivered.

Negative balances occur when a seller has been paid out and then a refund or chargeback is processed against a transaction they’ve already received. Your payout logic needs to support balance adjustments and a policy for sellers whose balance goes negative.

KYB / KYC Onboarding Without Killing Seller Conversion

KYB (Know Your Business) and KYC are regulatory requirements for onboarding sellers who will receive payouts. The design challenge: collecting this information without destroying seller activation.

Best practice is progressive verification — collect the minimum required to list, require full verification before the first payout. A seller can list and sell before they’ve fully verified. They cannot receive funds until they have.

Compliance Obligations You Inherit

KYC, AML and Sanctions Screening

Even when using a regulated payment partner, platforms inherit obligations for seller onboarding. You are responsible for ensuring sellers are not on sanctions lists — OFAC (Office of Foreign Assets Control) in the US, OFSI (Office of Financial Sanctions Implementation) in the UK, EU sanctions lists — and for maintaining records that demonstrate due diligence.

PCI DSS: What You Actually Have to Cover

PCI DSS (Payment Card Industry Data Security Standard) governs handling of cardholder data. If your checkout uses a provider’s hosted fields — Stripe Elements, Adyen Drop-in — you operate under the lowest PCI scope and your obligations are minimal. If you build a custom checkout that accepts card numbers directly, your PCI scope increases significantly. Use hosted checkout components.

Tax Reporting Obligations by Region

DAC7 is the EU directive requiring digital platforms to report seller earnings to tax authorities annually. The US equivalent is Form 1099-K. Canada, Australia, and the UK have equivalent frameworks. Build tax reporting infrastructure before you hit the reporting threshold, not after.

SCA and 3-D Secure in the Checkout Flow

SCA (Strong Customer Authentication) is required under PSD2 (Payment Services Directive 2) for card transactions in the European Economic Area. 3-D Secure (3DS) is the implementation mechanism. SCA exemptions exist for low-value transactions (under €30) and transactions flagged as low-risk. Understanding exemptions matters — 3DS adds friction and increases checkout abandonment.

Choosing Your Stack

Stripe Connect, Adyen for Platforms, Mangopay, Rapyd — Where Each Fits

Stripe Connect is the fastest to integrate and the right choice for most platforms at launch. Strong documentation, broad payout coverage, hosted seller onboarding. Limitations: FX rates not best-in-class, limited payout flexibility, thin emerging market coverage.

Adyen for Platforms is more complex to integrate but more flexible at scale. Better FX rates, more local payment methods, stronger high-volume payout support. Minimum volume requirements make it impractical early-stage.

Mangopay is designed specifically for marketplaces. Strong escrow, e-wallet, and multi-currency payout support. Well-suited for European platforms with complex payout logic.

Rapyd specializes in emerging market coverage — Southeast Asia, Latin America, Africa. The right choice when your payout geography includes markets Stripe and Adyen don’t support well.

Ledger Design: Why You Need Your Own, Even With a PSP

A PSP (Payment Service Provider) ledger records what happened at the provider level. Your own ledger records what happened at the business level — which seller earned what, which commission was collected, which dispute was resolved.

Build your own ledger from day one. Every transaction should produce a ledger entry: buyer payment, commission, processing fee, seller payout, adjustments. This is the foundation of your financial reporting and regulatory audit trail. This is a core part of custom software architecture for any serious marketplace platform.

Reconciliation and the Reports Finance Will Ask For

Finance will ask for: daily transaction volumes by currency, commission earned by period, processing fees by provider, payout totals by country, failed payout volumes, and chargeback loss by category. Design reconciliation as a first-class product concern from day one.

Designing the Money UX

Making Fees and Holds Legible to Sellers

Sellers who don’t understand why funds are held become sellers who churn. Every hold, deduction, and fee should be explained at the point it appears — in the interface, not in a terms document.

“Your funds are held for 7 days after delivery confirmation to protect buyers. They’ll be released on [date].” One line. Eliminates a category of support tickets. Reduces churn.

The Seller Balance Screen as a Retention Surface

The seller balance screen is one of the highest-value screens in a marketplace product. Show: pending balance, available balance, payout history, upcoming payout date, and the full calculation — earnings minus commission minus fees — so the seller can verify the math independently.

Failure States: Declines, Holds, Reviews

Payment failures need designed states. A buyer whose card declines should see a specific explanation and clear next step. A seller whose payout is on hold should know why, for how long, and what they need to do. Undesigned failure states are where trust breaks. See how we’ve approached financial UX in fintech platform design.

Conclusion

The payment model you choose before launch determines your compliance burden, your seller retention levers, your international expansion timeline, and your unit economics. Changing it in month fourteen costs more than getting it right in month one.

Start with a regulated partner model using Stripe Connect or Mangopay. Build your own ledger from day one. Design your payout schedule around your category’s dispute window. Plan compliance obligations by the markets you intend to enter in year two, not just the market you’re launching in.

If you’re designing the payment architecture for a marketplace platform and want to pressure-test the model before you build, book a discovery call.

FAQ

• What are split payments in a marketplace?

  A split payment is one buyer payment divided between the seller, the platform’s commission, and any additional fees — all processed in a single transaction. The split can happen at capture (separate transfers the moment the buyer pays) or at payout (funds held in a platform account, then distributed). The choice affects hold logic, dispute handling, and ledger complexity.

• Do I need to be a payment facilitator to run a marketplace?

  No. Most platforms use a regulated payment provider — Stripe Connect, Adyen, Mangopay — that is already a licensed payment facilitator and holds funds on the platform’s behalf. Becoming your own PayFac requires direct card network registration, underwriting, and significant ongoing compliance. The flexibility gain rarely justifies the cost for platforms below significant transaction volume.

• What is a merchant of record and when should a platform become one?

  A merchant of record is the entity legally responsible for the sale — collecting payment, remitting tax, and liable for chargebacks. Platforms become MoR to simplify tax compliance for sellers (the platform handles all VAT/GST centrally) or to gain full control of the checkout experience. MoR status increases liability significantly and requires robust tax infrastructure.

• How much do marketplace payments cost?

  Payment costs have four components: processing fee (1.5-3.5% of transaction value), platform fee charged by your PSP (0.25-0.5% for Stripe Connect standard), payout fee ($0.25-2.00 per payout depending on destination), and FX spread (0.5-2.5% on cross-currency payouts). Total cost per transaction on an international platform commonly runs 2.5-5% before your own commission.

• How fast should sellers get paid?

  Payout speed is a trade-off between seller retention and fraud and dispute exposure. Physical goods: 3-7 days after delivery confirmation. Services: 5-14 days after completion. Digital goods: 24-48 hours. High-value transactions: 14-30 days or on buyer acceptance. The right schedule is the shortest one where your chargeback rate remains within acceptable bounds.

• Can we start with one payment provider and switch later?

  Yes, but only if you own your own ledger and abstract the provider behind your internal payment service. Platforms that build directly against a single provider’s API face a complete re-architecture when they switch. Platforms with their own ledger and a payment abstraction layer can swap providers in weeks. The cost of not doing this is usually discovered in month eighteen when a new market makes the original provider inadequate.

A buyer pays. The seller ships nothing. The buyer opens a support ticket. The support team has no record of the transaction details, no evidence of what was promised, no policy that covers this exact situation, and no mechanism to recover the funds.

That’s not an edge case. That’s what happens when a marketplace treats trust as a homepage badge instead of a set of product mechanics.

This article covers what a trust layer actually consists of, how escrow and dispute flows work in practice, and the build-vs-buy decisions that determine whether your platform can enforce what it promises. If you’re designing or rebuilding transaction flows on a live marketplace platform, this is the systems view you need before you write a line of code.

---

What a Trust Layer Actually Consists Of

Identity: Who Is on the Other Side

Trust starts before the transaction. A buyer needs to know the seller is real. A seller needs to know the buyer can pay. Neither can verify this themselves.

The platform’s identity layer does three things: verifies that users are who they claim to be, maintains a public record of their transaction history, and signals the level of verification achieved without revealing raw personal data.

At minimum, this means email verification and a linked payment method. At the level required for high-value transactions — professional services, real estate, vehicles, financial instruments — it means government ID verification, liveness checks, and in some jurisdictions, proof of business registration.

Identity verification is not a trust badge. It’s a precondition for accountability. A user who has verified their identity has something to lose. That changes behavior more reliably than any review system. A user who transacted anonymously has nothing at stake beyond the transaction itself.

Money: Who Holds the Funds and for How Long

In a direct payment model, the buyer pays the seller directly. The platform has no hold on the funds and no leverage when something goes wrong. This is fast to build and immediately fragile.

In a held-funds model, the buyer pays the platform. The platform holds the funds and releases them to the seller on a defined trigger. This is slower to build, requires regulatory consideration, and is the only structure that gives the platform actual recourse when a transaction fails.

Every serious marketplace eventually moves toward a held-funds model. The question is whether they do it before or after their first major dispute crisis.

Evidence: What the Platform Can Prove Later

A dispute is a competing claim. The platform resolves it by evaluating evidence. If the platform didn’t capture evidence at the point of transaction, it has nothing to evaluate.

Evidence that matters: what was listed (the listing state at time of purchase, not the current state), what was agreed (messages, if the platform has them), what was delivered (shipping confirmation, digital delivery receipts, buyer confirmation), and when each of these events occurred (timestamps, audit trail).

Most platforms capture some of this passively. Very few design for it explicitly. The difference becomes visible the first time a high-value dispute reaches your team and you have no record of what was actually sold.

Recourse: What Happens When It Goes Wrong

Recourse is the set of actions the platform can take when a transaction fails. At minimum: hold remaining funds, initiate a refund to the buyer, claw back a payout that has already been released (if the payout structure allows it), and restrict or remove the offending account.

The gap between what platforms promise in their terms and what they can actually do mechanically is where trust breaks down. If your refund policy says “full refund within 7 days” but your payout structure releases funds to sellers within 24 hours, the policy is unenforceable. You will pay the refund from platform funds.

Escrow and Delayed Payouts

How Escrow Works in a Marketplace Context

Escrow in a marketplace is simpler than legal escrow. The buyer pays the platform. The platform holds the funds in a pooled account (or, in more regulated structures, in individual virtual accounts per transaction). The platform releases the funds to the seller when a trigger condition is met.

The platform acts as a trusted intermediary — not a legal escrow agent in most cases, but functionally equivalent from the user’s perspective. The legal structure underneath this varies by jurisdiction and is handled either through a regulated payment partner or, in some cases, requires the platform to hold a payments license.

Choosing the Release Trigger (Delivery, Acceptance, Time-Based)

Three common release triggers, each with different trade-offs:

Delivery-confirmed release: funds release when a shipping carrier confirms delivery. Fast for physical goods, useless for services or digital products. Doesn’t account for damaged or wrong items.

Buyer-acceptance release: funds release when the buyer explicitly confirms satisfaction, or after a defined window with no dispute raised. This is the most balanced model. The window length is a design decision — too short and buyers don’t have time to evaluate, too long and sellers wait too long for cash.

Time-based release: funds release after a fixed period regardless of buyer action. Simplest to build, most vulnerable to abuse. A buyer who fails to raise a dispute within the window loses their recourse permanently.

For most marketplaces, buyer-acceptance with a time-based fallback is the right default: funds hold until the buyer confirms or 5-14 days pass with no dispute, whichever comes first.

Escrow vs Instant Payout: The Trade-Off Nobody Talks About

Instant payouts are a supply-side acquisition tool. Sellers prefer platforms that pay fast. Every day of hold is a cash flow cost for a seller operating at volume.

Held funds are a buyer-side trust tool. Buyers transact more confidently when they know funds are protected. These interests are in direct tension.

The resolution isn’t to pick one — it’s to be explicit about the trade-off in your category. High-frequency, low-value transactions can often run on instant payouts because the dispute rate is low and the per-transaction loss is manageable. High-value, low-frequency transactions require held funds because a single failed transaction represents significant loss to both the buyer and the platform.

What Escrow Does to Your Regulatory Position

Holding user funds is a regulated activity in most jurisdictions. In the EU, this falls under PSD2 and typically requires an e-money license or partnership with a licensed institution. In the US, money transmission laws vary by state.

The common workaround: partner with a regulated payment provider that acts as merchant of record and holds funds on your behalf. This is not legal advice. Get qualified legal counsel before holding user funds.

Designing the Dispute Flow

The Four Stages: Raise, Evidence, Mediate, Resolve

Stage 1 — Raise: the buyer or seller initiates a dispute from the transaction record — not from a separate support page. Funds freeze automatically on dispute initiation.

Stage 2 — Evidence: both parties submit their account and supporting documentation. Structured evidence submission produces better decisions faster. Give each party equal time — typically 48-72 hours — and close the window when the timer expires.

Stage 3 — Mediate: a human reviewer or automated rules engine evaluates the evidence. Low-value disputes resolve through rules. High-value disputes require human review.

Stage 4 — Resolve: the platform issues a decision. Both parties are notified with the rationale. An appeals path should exist for decisions above a value threshold.

Dispute lifecycle: Transaction completed → Dispute raised (funds freeze) → Evidence window opens (48-72h) → Evidence window closes → Automated rule or human review → Decision issued → Funds released or refunded → Optional appeal window → Final resolution

Timers, SLAs, and Auto-Resolution Defaults

Every stage needs a timer. Without timers, disputes age indefinitely, funds stay frozen longer than necessary, and seller cash flow suffers without cause.

Define: how long buyers have to raise a dispute after delivery confirmation (typically 3-14 days). How long each party has to submit evidence (48-72 hours). How long the review team has to issue a decision (3-5 business days). What happens if either party doesn’t respond — auto-resolution in favor of the responsive party is standard.

Capturing Evidence at the Right Moment — Not After the Fact

The best evidence capture happens before any dispute exists. Design the post-transaction flow to encourage documentation: a delivery confirmation prompt with photo upload, a review prompt that captures condition at receipt, a service completion sign-off.

Evidence captured in the ordinary course of a transaction is more credible than evidence gathered after a dispute is raised. The buyer who photographs a damaged item at delivery gives you better evidence than the buyer who uploads a photo five days later.

When to Let the Parties Talk and When to Step In

Early in a dispute, direct negotiation resolves a significant percentage of cases without platform intervention — typically 30-50% of low-value disputes. Design a structured negotiation phase before escalating to platform review. Give the parties 24-48 hours to reach agreement.

Step in when: the negotiation window expires without agreement, either party requests escalation, or the transaction value exceeds a threshold warranting immediate review.

Refunds, Chargebacks, and Who Absorbs the Loss

Partial Refunds and Split Liability

Not every dispute is binary. Design your dispute interface to support partial resolutions — percentage-based or fixed-amount — with a required rationale from the reviewer. This resolves cases more accurately and costs the platform less than a full refund default.

Chargebacks: Why the Platform Usually Pays

A chargeback is a buyer disputing a charge directly with their card issuer, bypassing the platform. The card issuer reverses the charge. The platform absorbs the loss plus a chargeback fee (typically $15-25 per incident).

If the seller has already been paid out, recovering those funds is difficult or impossible. This is why early payout structures are dangerous — the platform pays refunds from its own funds when chargebacks arrive.

The primary defense: a dispute resolution flow that’s accessible and responsive enough that buyers use it instead of going to their card issuer.

Writing a Refund Policy Your Product Can Actually Enforce

Before publishing a policy, map each promise to a product mechanic. “Full refund if item not delivered” requires a delivery confirmation mechanism and a held-funds structure. “Refunds within 7 days” requires that funds haven’t been paid to the seller within 7 days.

If the mechanic doesn’t exist, remove the promise. A policy you can’t enforce is worse than no policy.

Trust Signals in the Interface

Reviews That Cannot Be Gamed

Transaction-gated reviews, two-sided blind release, and decay weighting — combined, these three mechanics eliminate the most common manipulation vectors. Only verified buyers can review. Both parties submit before seeing the other’s review. Recent reviews carry more weight than older ones.

Verification Badges That Mean Something

A badge should represent a specific, verifiable claim: government ID verified, business registration confirmed, background check completed. Badges that represent vague assertions erode the credibility of all badges on the platform.

Progressive Disclosure of Risk Before Checkout

High-value or first-time transactions should surface relevant risk information before the buyer confirms payment — not buried in terms, but as a contextual signal: “This seller has completed 3 transactions. Your funds are held until you confirm receipt.”

Why Over-Reassurance Reduces Trust

A platform that claims every transaction is perfectly protected creates a larger gap between promise and reality when something goes wrong. Calibrated honesty — “we hold your funds for 7 days and have a structured dispute process, but we can’t guarantee every outcome” — builds more durable trust than unconditional guarantees.

We applied this principle directly in the Swissgrams project, where trust communication was a core design challenge for a gold-backed financial product operating within the Swiss regulatory framework.

Build vs Buy: Stripe Connect, Adyen, Escrow Providers, Custom

What Off-the-Shelf Covers and Where It Stops

Stripe Connect handles payment processing, seller onboarding, fund splitting, delayed payouts, and basic dispute management. It doesn’t handle your dispute logic, evidence collection interface, or refund policy enforcement — those are your product’s responsibility.

Adyen Platforms offers similar capabilities with more flexibility in payout timing and stronger support for high-volume structures.

Dedicated escrow providers handle the full escrow lifecycle but are designed for individual transactions, not platform integration at scale.

Custom infrastructure becomes relevant when payout logic is complex enough that off-the-shelf solutions require too many workarounds, or when regulatory requirements in your market aren’t covered by available providers. For most fintech-adjacent marketplace platforms, this is a year-two decision, not day one.

Cost, Timeline, and Control Compared

Stripe Connect: fastest to integrate (days to weeks), predictable per-transaction cost, limited payout flexibility, no custom escrow logic.

Adyen Platforms: slower integration (weeks to months), volume-based pricing, more flexible payout timing, stronger international coverage.

Custom: slowest to build (months to years), highest upfront cost, complete control over payout logic and dispute mechanics, full regulatory responsibility.

Conclusion

Trust is not a feature. It’s a set of mechanics — identity verification, fund holds, evidence capture, dispute flows, refund enforcement — that either work or don’t when a transaction fails.

The platforms that earn lasting trust from both sides design these mechanics explicitly, before they need them, and make them visible in the interface without over-promising outcomes they can’t guarantee.

If you’re rebuilding transaction flows or designing the trust layer for a new marketplace platform, we run focused discovery sessions on exactly this. Book a call and we’ll work through your specific category and risk profile.

FAQ

• What is escrow in a marketplace?

  Escrow in a marketplace means the buyer pays the platform, the platform holds the funds, and releases them to the seller when a defined trigger is met — delivery confirmation, buyer acceptance, or a time window with no dispute. The platform acts as a neutral intermediary, giving both sides accountability without requiring direct trust between them.

• Do you legally need a license to hold user funds?

  It depends on jurisdiction and structure. In most markets, holding user funds requires a payments license or e-money registration. The common workaround is partnering with a regulated payment provider — Stripe Connect or Adyen — that acts as merchant of record and holds funds on your behalf. This is not legal advice; get qualified counsel before structuring your payment flow.

• How long should funds stay in escrow?

  Tie the hold period to the dispute window appropriate for your category, not an arbitrary number. Physical goods: 3-7 days after delivery confirmation. Services: 5-14 days after completion. High-value or complex transactions: up to 30 days. The hold should be long enough that a buyer who receives something wrong has time to identify the problem and raise a dispute.

• Who pays for a chargeback on a marketplace?

  Usually the platform. When a buyer disputes a charge with their card issuer, the reversal hits the platform regardless of whether the seller has been paid. If the seller has already received a payout, recovering those funds is difficult. This is why early payout structures are risky — the platform absorbs the chargeback loss from its own funds.

• How do you stop fake reviews?

  Three mechanics combined: transaction-gated reviews (only verified buyers of that specific product can review), two-sided blind release (both parties submit before either sees the other’s review, preventing retaliation suppression), and decay weighting (recent reviews carry more weight than older ones, keeping ratings reflective of current behavior).

• Should disputes be resolved by humans or automated rules?

  Use automated rules for low-value, high-volume disputes where the evidence pattern reliably predicts the correct outcome. Use human review above a transaction value threshold or when evidence is ambiguous. Cost per human review is typically $15-40 in staff time — below a certain transaction value, human review costs more than the disputed amount itself.

A marketplace launched with 400 listings and 11 transactions in its first month. The product worked. The listings were real. The design was clean. Nobody was buying anything because nobody believed anyone else was buying anything.

That’s the chicken-and-egg problem. Not a marketing failure. Not a product failure. A sequencing failure — and it’s fixable, but only if you understand what you’re actually solving for.

This article gives you a framework for diagnosing which side to build first, six tactics that have worked in real marketplace platforms, and the product design decisions that either accelerate or kill liquidity.

---

What the Chicken-and-Egg Problem Actually Is

Why Supply and Demand Refuse to Arrive at the Same Time

Supply won’t show up without buyers. Buyers won’t show up without supply. Both sides are rational. Both sides are waiting for the other to move first.

The standard response — launch anyway, market hard, hope momentum builds — fails because it treats the problem as a distribution problem. It isn’t. It’s a coordination problem. You can’t solve a coordination problem with advertising spend. Every dollar you put into acquisition before you have liquidity accelerates the churn cycle, it doesn’t break it.

Liquidity, Not Signups, Is the Only Metric That Matters

Signups measure willingness to explore. Liquidity measures willingness to transact.

A marketplace has liquidity when a user who arrives with intent can complete a transaction within an acceptable time. Acceptable varies by category: minutes for ride-sharing, days for B2B procurement, weeks for high-value real estate. The failure mode is always the same — search intent arrives, finds nothing useful, leaves.

Liquidity is a ratio: successful searches divided by total searches. When that ratio is below roughly 60-70% in your target segment, you don’t have a marketplace yet. You have a directory.

The Three Symptoms of a Marketplace Without Liquidity

Symptom 1: High browse, low contact. Users look but don’t message or book. They’re doing research, not transacting. The supply isn’t relevant or trustworthy enough to act on.

Symptom 2: Long time-to-first-response. Supply is present but slow. Buyers send inquiries and wait 48+ hours. They’ve moved on before the response arrives.

Symptom 3: Repeated one-and-done behavior. Users transact once and don’t return. The first experience didn’t deliver enough value to create a habit.

Pick a Side First: Supply-Led vs Demand-First Launch

When to Go Supply-First (High-Consideration, Low-Frequency Categories)

Supply-first works when your category involves high trust, low purchase frequency, and long consideration cycles — real estate, professional services, home renovation, legal services, B2B procurement.

In these categories, buyers research extensively before transacting. They’ll tolerate a longer wait to find the right match. But they won’t tolerate arriving and finding nothing. Supply density is the prerequisite for any buyer to take the platform seriously.

Airbnb went supply-first. They photographed listings in New York themselves before buyers existed at scale. The supply quality — professional photos, accurate descriptions — made the demand side possible. The lesson: supply quality in high-consideration categories is more important than supply quantity.

When to Go Demand-First (Commodity Supply, Aggregatable Inventory)

Demand-first works when supply is abundant, undifferentiated, and can be aggregated without much friction — ride-sharing, food delivery, freelance commodity work.

Uber went demand-first. In a new city, they guaranteed drivers a minimum hourly rate regardless of rides. This manufactured artificial demand density — drivers earned whether or not passengers existed — and gave Uber a working product to show passengers. The manufactured demand became real demand fast enough to sustain the supply.

A Simple Test to Decide Which Side Is Harder in Your Category

Ask two questions:

1. If I had unlimited demand tomorrow, could I find the supply within 30 days?
2. If I had unlimited supply tomorrow, could I convert it into transactions within 30 days?

Whichever answer is no — that’s your constrained side. Start there.

Six Tactics That Actually Break the Deadlock

Constrain Geography or Category Until Density Is Real

The most common cold-start mistake is launching nationally or across all categories on day one. You get a thin layer of supply and demand spread across a surface area too large to produce real liquidity anywhere.

Craigslist launched city by city. Etsy launched in craft and handmade only — not all of e-commerce. Facebook launched at Harvard before opening to other universities. Pick one city, one category, one buyer persona. Prove liquidity there before expanding.

Seed Supply Manually (Concierge and Do-Things-That-Don’t-Scale)

Before the platform exists, you are the platform. Call potential suppliers. Onboard them personally. Create the listings yourself if you have to. Do the matching manually in a spreadsheet.

Airbnb’s founders photographed early listings personally. DoorDash’s founders delivered food themselves. Not because it scaled, but because it didn’t need to yet. Every manual transaction tells you what the automated platform will need to do.

Be Your Own First Supplier

Some marketplaces solve the supply cold-start by becoming the supply. Reddit seeded its own communities before real users arrived. In a service marketplace, this might mean delivering the service yourself through contractors you manage directly — appearing to the demand side as a platform while operating as an agency on the supply side.

Single-Player Utility Before Network Value

If your product is only valuable when both sides are present, you have a brittle cold-start problem. OpenTable solved this by building restaurant management software first. Restaurants adopted it for reservation management — no diners needed. The diner network value came later.

Ask: what does the supply side need that has nothing to do with buyers? Build that first. Use it as the acquisition hook.

Subsidize the Scarce Side, Never Both

Subsidizing both sides simultaneously burns cash without building liquidity. Subsidize only the side that’s genuinely scarce in your category. Tie the subsidy to completed transactions, not signups. Set an explicit exit condition — a date, a transaction count, a density threshold — before you start.

Piggyback on an Existing Network

PayPal grew by integrating with eBay’s existing seller base. Airbnb bootstrapped their supply side from Craigslist listings. In 2026, the equivalent: target communities on Slack, Discord, or Reddit where your supply side already gathers, or integrate with tools they already use.

How Product Design Either Creates or Kills Liquidity

Search, Filters, and the Empty-State Problem

When supply is thin, broad search returns nothing useful. Design your search to succeed with thin supply. Default to narrower queries. Return results in a constrained geographic or category scope before expanding.

Empty states are the most underdesigned screen in most marketplaces. Design the empty state as an active response — show adjacent results, offer to notify the user when supply arrives, collect the failed search as a signal for supply acquisition. See how we’ve approached this problem in our marketplace case studies.

Matching Speed: Time-to-First-Response as a Core KPI

Time-to-first-response is the single strongest predictor of transaction completion. Design supply-side onboarding to establish response time expectations before the first inquiry arrives. Show response time prominently on supply profiles. Build automatic nudges when a response is overdue.

Etsy’s response time badge creates accountability and sets buyer expectations simultaneously — a minor feature with a major effect on liquidity.

Onboarding Friction on the Scarce Side

If supply is your scarce side, onboarding UX should do three things: get supply live as fast as possible, set expectations about early traction, and give supply something valuable before the first buyer arrives — analytics, portfolio hosting, or a credible signal that buyers are coming.

Designing for a Thin Marketplace Without Looking Empty

Use editorial framing — “top-rated in London”, “fastest response time” — rather than aggregate counts that reveal thinness. Launch with a curated landing page, not an open browse. The perception of curation buys time for supply to grow.

Metrics to Watch Before You Spend on Growth

Match Rate, Fill Rate, and Time-to-Liquidity

Match rate: percentage of buyer searches that return at least one relevant result. Below 60% means supply is too thin or too misaligned with demand intent.

Fill rate: percentage of buyer requests that result in a completed transaction. The gap between match rate and fill rate reveals where in the funnel liquidity breaks down.

Time-to-liquidity: median time from buyer arrival to completed transaction. Track this as a distribution, not just a mean — the long tail reveals where friction lives.

Cohort Repeat Rate by Side

Track repeat behavior by cohort for both sides separately. A marketplace where buyers repeat but suppliers churn has a different problem than one where suppliers stay but buyers don’t return.

The Liquidity Threshold Test Before Scaling Paid Acquisition

Before spending on paid acquisition: can you reliably fill 70%+ of search intent in your target segment? Can you deliver time-to-first-response under 24 hours in your primary category? If no to either — fix liquidity first.

Four Mistakes That Burn Runway

Launching Nationally Instead of in One Dense Pocket

National launch with thin supply produces thin coverage everywhere. Nobody has a good experience. Investor pressure to show geographic coverage is not a reason to dilute density.

Buying Both Sides at Once

Acquisition spend on both sides simultaneously produces signups without transactions. Pick the scarce side, subsidize it to a transaction, then use transaction data to acquire the other side organically.

Treating GMV as a Health Metric

GMV measures volume. Liquidity measures health. A marketplace can show strong GMV growth while liquidity deteriorates — if a small number of large transactions mask a high rate of failed smaller ones. Track liquidity ratios alongside GMV.

Building Features Before Reaching Liquidity

Every feature built before liquidity is a feature built for a product that may not find product-market fit. The minimum viable marketplace is the smallest surface that produces a reliable transaction in one narrow segment. Everything else is premature.

Liquidity Readiness Checklist — Before You Spend on Growth

1. Match rate in your primary segment is above 60%
2. Time-to-first-response is under 24 hours for 80%+ of inquiries
3. You have at least one geographic or category pocket with real density
4. Supply-side repeat rate is above 40% at 90 days
5. You have completed at least 50 transactions manually before scaling
6. Empty states in search are designed — not just “no results found”
7. You know your liquidity threshold and haven’t crossed it yet
8. Paid acquisition is paused until items 1–3 are true

Conclusion

The chicken-and-egg problem is a sequencing problem. Pick the scarce side. Constrain your geography. Seed manually. Design for thinness. Measure liquidity, not signups.

Most marketplaces that fail don’t run out of money before they find liquidity. They run out of money while subsidizing a national launch that never produced density anywhere.

If you’re pre-launch or at early traction on a marketplace platform and want to pressure-test your sequencing strategy, we run focused discovery sessions for this. Book a call and we’ll work through your specific category.

FAQ

• What is the chicken-and-egg problem in a marketplace?

  Neither side of a two-sided marketplace will join without the other. Supply won’t list without buyers; buyers won’t come without supply. The consequence is a launched platform with listings but no transactions, or traffic but no available inventory. It’s a coordination problem, not a marketing problem, and it requires a sequencing solution rather than additional spend.

• Which side should you build first — supply or demand?

  Build whichever side is harder to acquire and slower to replace if you lose it. Run the two-question test: if you had unlimited demand tomorrow, could you find the supply in 30 days? If you had unlimited supply tomorrow, could you convert transactions in 30 days? Whichever answer is no identifies your constrained side. Start there

• How long does it take a marketplace to reach liquidity?

  There is no universal number. It depends on transaction frequency in your category, geographic density required for a match, and average transaction value. Low-frequency, high-value categories typically take 12–24 months to reach reliable liquidity. High-frequency commodity categories can reach it in 90 days with the right seeding strategy.

• How many listings do you need before launching?

  Stop thinking in listing counts. Think in search-success rate within one narrow segment. A workable rule: you’re ready to launch when 70%+ of searches in your primary category and geography return at least one relevant result. Ten high-quality, fast-responding listings in one category beat 400 listings spread across a national surface area with 11 transactions a month.

• Is it worth paying users to join early?

  Yes, with conditions. Subsidize only the scarce side — never both simultaneously. Tie the subsidy to a completed transaction, not a signup. Set an explicit exit condition before you start: a date, a density threshold, or a transaction count. Subsidies without exit conditions become permanent operating costs that don’t produce self-sustaining liquidity.

• Can you build a marketplace MVP without solving liquidity first?

  Yes, but the MVP must deliver single-player value — utility to one side that has nothing to do with the other side being present. OpenTable built restaurant management software before it was a reservation marketplace. If your product is only valuable when both sides exist simultaneously, you don’t have an MVP — you have a bet on liquidity that hasn’t been placed yet.

   

Choosing a digital product development agency is one of the highest-stakes decisions a founder makes. The right partner ships a product that works in production. The wrong one delivers a Figma file that looks great in a presentation and breaks the moment real users arrive.

This guide covers how to evaluate agencies, what to look for, what to ask, and what to avoid — so you make the decision once, not twice after a rebuild.

---

Agency Types: Studio vs Freelance vs In-House

Freelancers. Cheapest option. One person handles design or development. Works for small, well-defined tasks — a landing page, a logo, a single feature. Falls apart on complex products where design, development, and strategy need to work together.

Boutique studios. Small team — usually 5-20 people. Founders are often involved in client projects. Fast communication. Specialized in specific verticals or product types. Best for startups and mid-stage companies that need a partner, not a vendor.

Large agencies. 100+ people. Works for enterprise with big budgets. Overkill for startups — you pay for the structure whether you need it or not.

In-house team. Full control. Full cost. $300K-500K/year before overhead. Makes sense after product-market fit. Before PMF, an agency is faster and cheaper.

The right choice depends on your stage. Pre-PMF: boutique studio. Post-PMF: in-house or long-term agency partnership. One-off task: freelancer.

What to Look for When Choosing an Agency

Portfolio and Case Studies

The portfolio tells you what the agency has built. The case study tells you how they think.

A portfolio full of beautiful screenshots means nothing if the products aren’t live. Ask to see products in production — apps you can download, websites you can visit. Sign up and use them. If the onboarding is confusing or the app crashes — the screenshots lied.

Look for case studies with context: what was the problem, what decisions were made, what were the results. “We designed a marketplace” is a description. “We redesigned seller onboarding and activation went up 34%” is evidence.

Reviews and Ratings

Clutch is the most reliable review platform for agencies. Reviews are verified through phone interviews with actual clients. Look for agencies with 4.8+ rating and 20+ reviews — enough volume that the rating is meaningful.

DesignRush and Sortlist provide additional verification. Cross-reference reviews across platforms. If an agency has 5.0 on their website and no presence on Clutch — that’s a signal.

Industry Specialization

A generalist agency can build anything. A specialist agency has already built your thing.

If you’re building a SaaS product, the agency should have SaaS in their portfolio. If you’re building a marketplace, they should understand two-sided dynamics, trust architecture, and payment escrow — not just “e-commerce.”

The specialist has already made the mistakes your product would encounter. A generalist discovers them on your budget.

Process and Communication

Ask what the first two weeks look like. The answer tells you everything.

Right answer: discovery sprint — user research, competitive audit, flow mapping, product strategy. Before anyone opens Figma.

Wrong answer: “We’ll start wireframing on Monday.”

Agencies that skip discovery save you two weeks and cost you three months of redesigning what they should have researched.

Communication matters equally. Direct access to the designer, or everything routed through a project manager? If every message goes through an account manager — you’re paying for a game of telephone.

Questions to Ask During a Brief

“Show me a live product I can sign up for.” Not a Behance case. A real product with real users. If the agency can’t show one — they’ve designed screens, not products.

“What does your first week look like?” Discovery or mockups? The first week predicts the next six months.

“Who will actually work on my project?” Meet the designer and developer — not just the sales team. The proposal is sold by one team. The work is done by another.

“What happens when we disagree on a design decision?” Good agencies push back with evidence. Bad agencies do whatever the client says.

“What’s your approach to [your specific product type]?” If you’re building a marketplace — ask about trust UX, seller onboarding, and payment architecture. If the agency gives a generic answer, they haven’t built one before.

“What does post-launch support look like?” The product launches. Bugs appear. If the answer is “we hand off the Figma file and you’re on your own” — keep looking.

Red Flags to Watch Out For

No discovery phase. Jumping straight to design means every decision is based on assumptions. Assumptions are expensive to correct in production.

Fixed price with no scope document. A fixed price without a detailed scope is either too high or too low.

No live products in portfolio. If nothing is live and usable — the agency designs, but doesn’t ship.

The sales team disappears after signing. You spoke to a senior partner during the pitch. Now your project is handled by a junior designer you’ve never met.

“We can build anything.” An agency that builds everything builds nothing exceptionally. Specialization matters.

Timeline promises without scope. “We’ll deliver in 8 weeks” before understanding what they’re building is not a timeline. It’s a guess dressed as a commitment.

How to Estimate Project Cost

Simple product — landing page, basic web app, single-feature MVP: $10K-30K. Timeline: 4-8 weeks.

Medium complexity — SaaS product with user accounts, dashboard, integrations: $30K-80K. Timeline: 2-4 months.

Complex product — marketplace platform, fintech app, multi-role system with payments: $80K-200K+. Timeline: 4-8 months.

What drives cost up: real-time features, complex payment logic, multi-platform, compliance requirements, and third-party integrations.

What keeps cost reasonable: focused MVP scope, a product audit before building, and a design system that accelerates front-end development.

Get 3-5 quotes. If they range from $15K to $150K for the same brief — the agencies are scoping different products. The brief needs more detail, not more quotes.

Agency Selection Checklist

→ Can they show live products — not just portfolio screenshots?

→ Do they start with discovery — not wireframes?

→ Do they have 20+ verified reviews on Clutch?

→ Do they specialize in your product type?

→ Can you meet the actual team — not just sales?

→ Is pricing transparent before signing?

→ Do they have a post-launch support plan?

→ Do they push back with evidence — not just agree?

→ Can they work embedded with a small team?

→ Does their process include user testing before launch?

If more than 3 answers are “no” — keep looking.

---

U1CORE is a product design and development studio specializing in marketplace platforms, SaaS, fintech, and Web3. $720M+ processed through products we’ve built. Book a strategy call.

AI isn’t coming for product development. It’s already here — in the design tools, the code editors, the research platforms, and the testing pipelines. The question isn’t whether to use it. It’s where it helps, where it breaks things, and where it creates more problems than it solves.

This guide covers how AI is changing product development in practice — from UI/UX design and software engineering to user research and analytics. Not the hype. The reality of using AI tools on production products in 2026.

---

How AI Changed the Development Market

Two years ago AI in product development meant ChatGPT writing copy and Midjourney generating concept images. Today it’s embedded in every stage of the product lifecycle.

Designers use AI to generate layout variations in minutes instead of hours. Engineers use Copilot to write boilerplate code that used to take a full sprint. Researchers use AI to analyze thousands of user sessions and surface patterns no human would catch in time.

The market shifted fast. Clients expect faster timelines. Competitors ship faster. The teams that integrated AI into their workflow deliver in weeks what used to take months.

But the shift isn’t uniform. AI dramatically accelerated the mechanical parts of product development — generating code, producing variations, processing data. The strategic parts — deciding what to build, understanding user needs, making architecture decisions — remain fundamentally human.

The product teams winning in 2026 aren’t the ones using the most AI. They’re the ones using it in the right places and keeping humans where AI fails silently.

AI in UX/UI Design

Layout Generation

AI layout tools can generate 10-20 screen variations from a text prompt in minutes. What used to require a designer spending half a day exploring directions now happens before the first coffee.

This is genuinely useful for exploration. Early-stage concepts, wireframe alternatives, rapid iteration on spacing and hierarchy — AI compresses the divergent phase of design significantly.

Where it breaks: AI generates layouts that look plausible but lack product logic. It doesn’t know that the seller dashboard needs different information hierarchy than the buyer dashboard. It doesn’t understand that the checkout button needs trust copy above it.

At U1CORE we use AI for layout exploration after the product architecture is defined — never before. The architecture decisions are human. The visual exploration is accelerated by AI.

Interface Personalization

AI-driven personalization adapts interfaces based on user behavior. Different dashboard layouts for power users vs new users. Personalized onboarding flows based on user role. Dynamic content ordering based on engagement patterns.

This works well at scale. A marketplace platform with 100,000 users has enough behavioral data for AI to surface meaningful patterns.

Where it breaks: at early stage. A product with 500 users doesn’t have enough data for AI personalization to be meaningful. The recommendations are essentially random — but they look confident, which is worse than showing nothing.

Rule of thumb: AI personalization needs 10,000+ interactions to be useful. Below that, curated defaults designed by humans outperform any algorithm.

Automated Testing

AI-powered testing tools can run through user flows automatically, identify visual regressions, and flag accessibility issues across hundreds of screen states. What used to require a QA team spending a week now runs overnight.

Where it adds real value: regression testing across responsive breakpoints. A web design that works on desktop may break on 4 different mobile viewports. AI catches these inconsistencies at a speed no manual QA matches.

Where it falls short: AI can tell you something changed. It can’t tell you whether the change is correct. Human judgment still decides what’s a bug and what’s a feature.

AI in Software Engineering

Copilot and Development Speed

GitHub Copilot, Claude Code, Cursor — AI coding assistants have become standard tools in 2026. The impact on speed is real: boilerplate code, repetitive patterns, and standard implementations happen 2-3x faster.

For straightforward tasks — API endpoints, CRUD operations, form validation — AI assistants are genuinely productive. A developer who used to spend 30 minutes on boilerplate now spends 5 minutes reviewing AI-generated code.

Where it breaks: complex architecture decisions. AI can write an escrow payment flow. It can’t decide whether your marketplace product needs escrow in the first place. It can generate a notification system. It can’t determine which notifications matter for seller retention.

The pattern we see at U1CORE: AI speeds up the 60% of development that’s well-defined. It creates problems on the 40% that requires understanding the product and business logic. Teams that use AI for everything ship faster and debug longer. Teams that use AI selectively ship at the same speed and debug less.

One more reality: AI coding tools moved to token-based pricing in 2026. Teams that used AI for everything saw bills go from $29/month to $750+. The tool that was supposed to make custom software development cheaper became an unpredictable cost center.

AI in User Research and Analytics

This is where AI delivers the most underrated value in product development.

Session analysis at scale. Tools like Hotjar and FullStory now use AI to analyze thousands of user sessions and surface patterns. A researcher would need weeks to find these insights manually. AI surfaces them in hours.

Survey analysis. Open-ended responses used to sit in spreadsheets, manually coded by theme. AI categorizes thousands of responses in minutes. The themes it surfaces are usually correct. The nuance it misses is usually important. Best used as a first pass that a human validates.

Behavioral prediction. AI can identify users likely to churn based on behavioral patterns — login frequency, feature usage, support ticket history. Product teams can intervene before the user leaves rather than analyzing why they left.

Competitive analysis. AI tools can monitor competitor products, track feature changes, and summarize review sentiment across platforms. What used to require a full-time analyst now runs in the background.

Where AI research fails: it finds patterns but doesn’t understand context. “Users drop off at step 3” is a finding. “Users drop off because they don’t trust the platform enough to enter payment details” is an insight. AI delivers findings. Humans deliver insights. A product audit that combines AI-powered analytics with human interpretation consistently outperforms either alone.

Risks and Limitations of AI in Products

The confidence problem. AI outputs look polished regardless of whether they’re correct. The more confident the output looks, the less likely teams are to question it.

The homogeneity problem. AI tools are trained on the same data. Every AI-generated landing page converges toward the same layout. Differentiation requires human decisions that deviate from the average.

The context problem. AI doesn’t understand your specific users or business constraints. It generates from patterns. Your competitive advantage usually lives where you break patterns intentionally.

The cost problem. AI tools that were flat-rate are moving to usage-based pricing. The “AI saves money” narrative is being replaced by “AI shifts costs from salaries to subscriptions.”

The accountability problem. When AI-generated code breaks in production, who’s responsible? AI generates output. Humans own consequences.

The Future of AI in Product Development

AI agents will handle multi-step workflows — not just generating a screen but researching the need, proposing the solution, and testing it. Early versions exist. Impressive in demos. Unreliable in production.

AI will become invisible — embedded in Figma, code editors, and analytics dashboards. Doing work in the background without requiring a prompt.

The human role will shift from production to judgment. When everyone has the same AI tools, the differentiator becomes the human decisions: what to build, who to build it for, what to cut. These require experience, empathy, and judgment — exactly the things AI doesn’t have.

AI Tools for Product Teams

Design: Figma AI, Galileo AI, Relume, Midjourney and DALL-E.

Development: GitHub Copilot, Claude Code, Cursor, v0 by Vercel.

Research: Hotjar AI, Dovetail, Maze, Synthetic Users.

Testing: Applitools, Percy, Playwright with AI assertions.

Analytics: Amplitude AI, Mixpanel, FullStory.

Project management: Linear, Notion AI, Gamma.

The tools change fast. The principle doesn’t: use AI for speed on well-defined tasks. Keep humans on strategy and decisions where being wrong is expensive.

---

At U1CORE we use AI tools across our workflow — and we know exactly where to stop. AI makes us faster. Experience makes us right.

U1CORE is a product design and development studio. We offer UI/UX design, web design, mobile design, custom software development, app development, branding, and product audit. $720M+ processed through products we’ve built. Book a strategy call.

Most SaaS landing pages fail before the visitor reads the second paragraph. Not because the product is wrong. Because the page doesn’t answer three questions every visitor asks in the first ten seconds: what does this do, who is it for, and why should I trust you.

This guide covers how to structure a high-converting SaaS landing page — from hero section to pricing to CTA. At U1CORE, landing page design is one of our most requested services for growth-stage SaaS companies. Here’s what actually moves conversion.

---

Why SaaS Products Need a Dedicated Landing Page

A SaaS homepage serves multiple audiences: existing users, potential customers, investors, job candidates. A landing page serves one audience with one message and one goal.

A landing page built for a specific acquisition channel converts at two to five times the rate of a generic homepage because the message matches the visitor’s context. Every significant acquisition channel deserves its own landing page.

Structure of a High-Converting SaaS Landing Page

Hero Section and Value Proposition

The hero section is the only part of the page every visitor sees. If it fails to communicate what the product does and why it matters in under ten seconds, the rest of the page doesn’t get read.

A high-converting SaaS hero has four elements.

Headline: a specific, outcome-oriented statement. Not a tagline. A clear answer to “what is this.” The best SaaS headlines follow a simple structure: Verb, outcome, audience. “Close more deals without updating your CRM.” “Build and ship features twice as fast.”

Subheadline: one or two sentences that expand the headline with the specific mechanism or audience. Together, headline and subheadline answer: what does this do, who is it for, what’s different.

Primary CTA: one action, clearly labeled. “Start free trial” is better than “Get started” because it tells the visitor what they’re starting. Avoid generic labels — Sign up, Learn more, Submit — that could belong to any product.

Hero visual: a product screenshot or short product video. Not a stock photo. Visitors want to see what they’re buying. A realistic product screenshot reduces the “is this real” question and increases time on page.

Stripe’s hero shows a code snippet and a payment interface simultaneously — answering “what does this do” and “how does it work” in a single visual. Linear’s hero shows the actual product interface at high resolution, communicating product quality before a word is read.

Social Proof and Testimonials

Social proof reduces the purchase anxiety every SaaS visitor carries. The most effective forms, in order of credibility:

Named testimonials with photos and company logos. A quote from “Sarah M., VP of Operations, Acme Corp” with a headshot and company logo is more credible than a generic five-star review. Specificity signals authenticity.

Customer logos. A row of recognizable company logos communicates that the product has been adopted by credible organizations.

Usage statistics. “50,000 teams use this product” or “4.8 from 2,000+ reviews on G2” are credible because they’re specific and verifiable. Vague claims are less credible.

Case study snippets. A one-paragraph outcome story is more persuasive than a generic testimonial because it describes a specific result.

Place social proof immediately below the hero — not buried at the bottom of the page.

Pricing Section

The pricing section is the highest-intent moment on a SaaS landing page. A visitor who scrolls to pricing is actively evaluating. A high-converting pricing section has three properties.

It shows the actual price. “Starting at $49/month” is more credible than “pricing available on request.” Hiding price creates friction at the highest-intent moment.

It has a clear recommended plan. Label one plan as “Most popular.” Visitors who are unsure which plan to choose are more likely to convert when the page removes the decision.

It addresses the objection at the decision point. “Free to cancel anytime” and “14-day free trial, no credit card required” belong in the pricing section — not in the FAQ at the bottom.

CTA Blocks

A long SaaS landing page needs multiple CTA placements. The minimum structure: hero section, after the features section, adjacent to the pricing table, and footer. Each placement uses the same primary action with varied supporting copy.

Common SaaS Landing Page Mistakes

Leading with features instead of outcomes. “Automated reporting, custom dashboards, and API integrations” describes what the product has, not what it does. Reframe: “See the data that drives your decisions — automatically, in real time.”

Vague value proposition. “The platform for modern teams” could describe a thousand products. Be specific about who the product is for and what it specifically solves.

No mobile optimization. A significant share of initial SaaS research happens on mobile. A desktop-only design loses mobile visitors immediately.

Hero visual that shows nothing. A gradient background or stock photo communicates nothing. If visitors can’t see what they’re buying, they leave.

Testimonials without specificity. “Great product, highly recommend!” from “John D.” is not social proof. Real testimonials name a specific outcome, from a named person with a real role, company, and photo.

Loading time above three seconds. Every additional second of load time reduces conversion. Unoptimized images and render-blocking scripts are the most common causes.

Tools to Build a SaaS Landing Page

Webflow is the strongest choice for design-quality landing pages that marketing teams need to update independently. It produces clean code, strong Core Web Vitals performance, and a visual editing interface that non-developers can use after initial setup. Our Webflow development service covers end-to-end delivery on this stack.

Framer has emerged as a strong alternative for design-led teams. It supports advanced animations that Webflow handles less elegantly, and its AI-assisted design features accelerate initial builds.

Unbounce and Instapage are purpose-built for conversion-optimized landing pages with built-in A/B testing. They produce pages faster. The trade-off is design flexibility.

Next.js or Astro for custom development is appropriate when the landing page needs to integrate tightly with the product’s authentication system or when performance requirements exceed what no-code tools deliver.

For most early and growth-stage SaaS products, Webflow is the best default.

How to Test and Improve Conversion

A landing page is a starting point for ongoing conversion optimization, not a finished deliverable.

Start with qualitative data. Before running A/B tests, understand why visitors are not converting. Session recordings from Hotjar or Microsoft Clarity, user interviews with recent trial signups, and exit surveys tell you more than aggregate metrics alone.

Identify the highest-impact test. The element with the most traffic and the most visible drop-off is the first test candidate. For most SaaS landing pages, that is the hero headline and primary CTA.

Test one element at a time. Testing two elements simultaneously makes it impossible to know which change drove the result.

Measure conversion, not engagement. Time on page and scroll depth are engagement metrics. Trial signups and demo requests are conversion metrics. Optimize for what you actually want.

Give tests sufficient time. Most meaningful conversion tests need at least two weeks and sufficient traffic to reach statistical significance.

Best SaaS Landing Page Examples

Linear shows the actual product interface at high resolution in the hero. The value proposition is specific. No stock photography. Social proof consists of named testimonials from engineering leaders. The page loads in under two seconds.

Notion segments immediately in the hero — showing different use cases for different audiences — and uses user-generated content as social proof. The result speaks to multiple buyer types without losing specificity for any of them.

Stripe uses the hero to speak simultaneously to two audiences: developers (code snippet showing API integration) and business owners (payment success interface). Technical sophistication and business legitimacy, communicated at the same time.

Figma uses video in the hero — a short demonstration of real-time collaboration that differentiates the product from alternatives. The video communicates the core differentiator faster than any written description could.

The common thread across all four: specific value propositions, real product visuals, specific social proof from named sources, fast loading, and a single conversion goal per page.

---

Need help designing a SaaS landing page that converts? U1CORE has shipped landing pages and SaaS UI/UX design for growth-stage companies across marketplace, fintech, and Web3. Get in touch to discuss your project.

U1CORE is a product design and development studio specializing in SaaS, marketplace platforms, and custom software development. $720M+ processed through products we’ve built.

Most products don’t fail because the idea was wrong. They fail because somewhere between the first user session and the tenth, something breaks — and nobody caught it before it became a churn problem.

A UX audit is how you find exactly where that break is happening, before it shows up in your retention numbers.

---

What Is a UX Audit and Why It Matters

A UX audit is a structured evaluation of a digital product or website — its usability, information architecture, user flows, and design consistency — against defined criteria. The output is a prioritized list of problems and recommendations, not a general impression.

The difference between a UX audit and a design review: a design review is an opinion. A UX audit is evidence.

Most teams know something is wrong — conversion is lower than it should be, support tickets cluster around the same flows, users drop off at a specific step — but they don’t know exactly what to fix or in what order. A UX audit answers both questions.

At U1CORE, a post-audit redesign of a marketplace onboarding flow increased seller activation by 34% in 60 days. The audit identified the exact step where sellers were abandoning — not a guess, a finding backed by analytics and session recordings.

Types of Audits: Expert vs User Testing

Expert evaluation (heuristic analysis): an experienced UX designer evaluates the product against established usability principles without involving users. Fast and doesn’t require recruiting. Limitation: it reflects what an expert thinks will be a problem, not what actual users experience.

User testing: real users complete defined tasks while observed. Catches what expert evaluation misses — the assumptions your team made that users don’t share, terminology that confuses externally, flows that test well in theory and fail in practice.

For most products: start with expert evaluation, then validate critical findings with user testing before committing to redesign. Five users is the minimum to surface the majority of usability problems.

UX Audit Process Step by Step

Analytics Review

Before evaluating any screen, look at the data.

Drop-off rates by step in key flows. If 60% of users complete step 2 of onboarding but only 35% complete step 3, step 3 is your first audit target.

Time on page by section. Unusually high time on a single step can mean engagement or confusion. Session recordings will tell you which.

Search queries within the product. What users search for is a direct signal of what they can’t find through navigation.

Support ticket categories. The top three categories are almost certainly UX problems, not user errors.

Tools: Google Analytics 4, Mixpanel, Amplitude. Session recordings: Hotjar, FullStory, Microsoft Clarity (free).

Heuristic Evaluation

Evaluate each flow against Nielsen’s 10 heuristics:

1. Visibility of system status
2. Match between system and real world
3. User control and freedom
4. Consistency and standards
5. Error prevention
6. Recognition over recall
7. Flexibility and efficiency
8. Aesthetic and minimalist design
9. Help users recover from errors
10. Help and documentation

Score each heuristic per screen. Severity scale: 0 (not a problem) to 4 (must fix before launch).

User Testing Sessions

Write tasks as goals, not instructions. “You need to buy a birthday gift for a friend who likes cooking — show me what you’d do” surfaces real behavior. “Add an item to your cart” tests whether users can follow instructions.

Note: where users hesitate, where they look in the wrong place, where they give up, where they succeed faster than expected.

UX Audit Checklist

Navigation and Information Architecture

• Primary navigation is visible and clearly labelled
• Users can identify where they are at all times
• Back navigation works as expected
• Search returns relevant results with appropriate empty states

Onboarding

• First session delivers value before asking for information
• Progress indicators show how far through onboarding the user is
• Users can skip or return to steps without losing progress
• Confirmation and success states are explicit

Forms and Input

• Labels are visible above fields (not placeholder text only)
• Error messages appear next to the field that caused them
• Error messages explain what went wrong and how to fix it
• Form validation happens inline, not only on submit

Calls to Action

• Primary CTA is visually distinct from secondary actions
• CTA labels describe the action (not just “Submit”)
• Destructive actions require confirmation

Empty and Loading States

• Empty states explain why content is missing and what to do
• Loading states provide feedback within 1-2 seconds
• Timeout states offer a clear recovery path

Error Handling

• 404 pages include navigation back to useful content
• System errors are explained in plain language
• Users are never left without a next action after an error

Mobile and Responsive

• Touch targets are minimum 44×44px
• Content reflows correctly at all breakpoints
• No horizontal scrolling on any screen

Accessibility

• Color contrast meets WCAG AA minimum (4.5:1)
• Interactive elements are keyboard navigable
• Images have descriptive alt text

Tools for UX Audits

Analytics: Google Analytics 4, Mixpanel, Amplitude, Heap. Session recording: Hotjar, FullStory, Microsoft Clarity (free). User testing: Maze, UserTesting.com, Lookback. Accessibility: axe DevTools, Wave, Lighthouse. Documentation: Notion for findings, Loom for walkthroughs, Figma for annotating screenshots.

How to Interpret Results

Prioritize by impact and effort.

Impact: how many users does this affect, and how significantly does it affect their ability to complete a key task?

Effort: how complex is the fix?

Fix high-impact, low-effort items immediately. Prioritize high-impact, high-effort items in your next sprint. Deprioritize low-impact items regardless of effort.

Distinguish symptoms from causes. If users drop off at step 3 of onboarding, step 3 is the symptom. The cause might be that step 2 set incorrect expectations. Fixing step 3 without addressing step 2 produces partial improvement.

What to Do After the Audit

Write findings that non-designers can act on. Each finding: a plain-language description, the evidence, the severity rating, and a specific recommendation.

Present findings in person. A written report gets skimmed. A 45-minute walkthrough creates shared ownership. Show the session recordings — watching a real user struggle changes how a team thinks about fixing it.

Build a fix roadmap. Immediate fixes (this week), short-term improvements (this sprint), structural changes (next quarter). Assign owners. Set deadlines.

Measure before and after. Define the metric each fix is intended to improve before you ship. Measure at 30 days post-launch.

Re-audit on a cadence. Build a lightweight audit into your quarterly product review. The teams that catch UX problems earliest spend the least fixing them.

---

U1CORE runs UX audits for SaaS products, marketplaces, and fintech platforms. If your product has a conversion or retention problem you can’t explain, an audit is usually the fastest way to find out why. Book a free scoping call to discuss your product.

In fintech, design isn’t a visual layer on top of the product. It IS the product. The interface is where users decide whether to trust you with their money — or close the tab and never come back.

A confusing screen on a fintech app loses you a customer, a transaction, and potentially a regulatory complaint. This guide covers what makes financial UX different, how to build trust through design, what key screens need to get right, and the mistakes that kill fintech products before they scale.

---

What Makes Financial UX Different

Every interaction involves real money. A misplaced decimal point isn’t a UI bug — it’s a financial loss. A confusing confirmation screen causes a wrong transaction that may be irreversible. The cost of UX failure in fintech is measured in dollars, not bounce rates.

Users arrive with distrust by default. A new user carries years of conditioning from banking frustrations, fraud headlines, and data breach notifications. The UX design has to earn trust before asking for a bank account number — not after.

Complexity is non-negotiable. You can’t simplify away KYC. You can’t skip AML verification. You can’t hide transaction fees in the name of clean UI. Fintech products must present complex, regulated information clearly — without oversimplifying to the point of being misleading.

Errors have legal implications. A payment sent to the wrong account. A disclosure that wasn’t shown clearly enough. In fintech, UX failures can trigger regulatory action, not just bad reviews.

Building Trust Through Design

Trust in fintech isn’t built by saying “we’re trustworthy.” It’s built by making every screen feel safe, transparent, and predictable.

Visual Trust Signals

Consistent, professional visual system. Inconsistent spacing and mixed typography signal “this team doesn’t pay attention to details.” In fintech, that translates to “they might not pay attention to my money either.” A proper design system from a UI/UX design team eliminates these signals entirely.

Security indicators where they matter. Lock icons near sensitive fields. “Encrypted” labels near payment inputs. Context matters more than the claim — place security signals next to the exact input where the user enters their card number.

Status clarity on every transaction. Pending, processing, completed, failed — every state needs clear language. “Processing” with a spinner creates anxiety. “Processing — usually completes within 2 minutes” creates confidence. One line of copy. Completely different experience.

Real numbers, not vague promises. “Trusted by 50,000+ users” is vague. “€47M transferred this month” is specific. In fintech, specific numbers build trust. Round numbers build suspicion.

Onboarding with Verification

KYC and identity verification are mandatory. Most products treat them as friction to minimize. The best products treat them as trust-building moments.

Explain before you ask. “We need to verify your identity” creates resistance. “Identity verification protects your account and ensures only you can access your funds” creates alignment. Same requirement. Different completion rate.

Progressive verification. Don’t ask for everything upfront. Let the user explore the product and see the value. Then verify before the first transaction — when motivation is highest. Browse freely, verify to transact, enhance to scale.

Make verification feel like an upgrade. After completing KYC: “You’re now verified. Verified accounts get higher transfer limits and priority support.” The effort becomes an investment. People protect what they’ve earned.

Design for failure states. Document too blurry. ID expired. Face doesn’t match. Every rejection needs a clear explanation and recovery path — not “verification failed, try again.”

Key Screens in a Fintech App

Dashboard and Analytics

The dashboard is where most fintech users spend 80% of their time — and the most commonly over-designed screen.

Show what matters now. A fintech dashboard with 20 metrics is a spreadsheet. The user needs 3-5 key numbers: current balance, recent activity, pending transactions, and one actionable insight. Everything else lives one tap deeper.

Design for the glance. Most dashboard visits are under 10 seconds. The user checks balance, scans activity, and closes. The mobile design has to deliver value in that glance.

Make trends visible. “$4,230 in your account” is a fact. “$4,230 — up 12% from last month” is an insight. A simple trend indicator transforms static data into decision-supporting information.

Empty dashboard matters. A new user’s first dashboard has no data. If that screen shows blank charts and “No transactions yet” — the product feels broken. Design guidance into the empty state. The first session determines whether there’s a second one.

Payments and Transfers

The payment screen is where trust converts into action.

Show the full cost before confirmation. Amount, fees, exchange rate, and final total — all on one screen. No surprises at the last step. “The fee was hidden” is the number one complaint in fintech UX.

Confirm with clarity. Not “Confirm” — but: “Send €500 to Maria Garcia. Fee: €1.50. Arrives in 2-3 hours.” Every variable stated. Every consequence previewed.

Design for the wrong-recipient scenario. Users will enter wrong account numbers. Build a review step that shows the recipient name prominently — not just the account number.

Transaction status needs real-time updates. “Processing” is not a status. “Sent to recipient’s bank — estimated arrival: today by 5PM” is a status.

Regulatory Requirements in Fintech UI

Regulation isn’t a constraint on good fintech design. It’s a design requirement.

KYC/AML isn’t optional — but the experience of it is. The regulation dictates what you collect. The UX design dictates how you collect it.

Disclosures must be visible — not just present. Regulatory disclosures buried in scrollable terms of service are technically compliant and practically invisible. Surface key disclosures at the point of decision — not at the point of signup.

Data privacy requires designed consent flows. GDPR and CCPA require clear consent for data processing. Design explicit opt-in flows with plain-language explanations. A pre-checked box isn’t consent — it’s a liability.

Best Fintech Design Examples

Revolut reduced multi-currency management to a swipe. The key decision: show the rate AND the fee AND the final amount on one screen before confirmation. No surprises.

Wise built its entire brand on fee transparency. The transfer calculator shows exact fee, exchange rate, and delivery time before the user enters any personal information. Trust is built before the first input field.

Monzo used instant spending notifications to create a distinctive brand. The moment you tap your card — notification on your phone. A design decision that changed user expectations across the industry.

The common thread: each made complex financial operations feel simple without hiding the information users need for confident decisions.

Common Fintech UX Mistakes

Hiding fees until the last step. The number one way to destroy trust. If the user discovers a fee at confirmation that wasn’t visible before — you’ve lost them. Show fees early and clearly.

Over-simplifying at the expense of clarity. “Just tap to send money” sounds great. In production, users need to know: how much, to whom, what fee, when it arrives, and what happens if something goes wrong.

Treating KYC as a wall instead of a bridge. Front-loading full verification before the user sees any value creates maximum dropoffs at minimum motivation.

Ignoring error states. “Transaction failed” with no explanation. “Something went wrong” with a generic retry button. Every error needs a specific explanation and a specific next step. Users don’t retry vague errors — they leave.

Designing dashboards for power users first. Your first-time user needs balance and recent activity. Your power user needs analytics. Start simple, unlock complexity through progressive disclosure.

No offline design. Users check their balance on the subway. If the app shows a blank screen when offline — the user panics. “Last updated: 2 minutes ago — reconnecting” is the difference between trust and fear.

---

Need help designing a fintech product users trust? U1CORE has shipped trading platforms, payment infrastructure, and financial products across multiple markets. See our fintech work or get in touch.

U1CORE is a product design and development studio specializing in fintech, marketplace platforms, and custom software development. We offer UI/UX design, web design, mobile design, app development, branding, and product audit. $720M+ processed through products we’ve built. Book a strategy call.