ONE BISON

Turning a business directory into a two-sided marketplace

Turning a business directory into a two-sided marketplace

As One Bison expanded from a directory of 800+ vetted businesses into commerce, I designed the buyer and seller journeys that make transactions possible—from seller onboarding and product discovery to cart, checkout, and order tracking.

As One Bison expanded from a directory of 800+ vetted businesses into commerce, I designed the buyer and seller journeys that make transactions possible—from seller onboarding and product discovery to cart, checkout, and order tracking.

ROLE:

UX/ UI Designer

SCOPE:

Marketplace UX
Seller onboarding
Product discovery
Checkout & payments
Design system

STATUS:

V3 — ongoing
Onboarding shipped,
Checkout in build

CHALLENGE

The directory worked for discovery. It wasn't designed for transactions.

The directory worked for discovery. It wasn't designed for transactions.

One Bison had built a network of more than 800 vetted businesses, but its directory structure created friction as the product moved toward commerce. Shoppers struggled to understand where to start, while business owners faced unclear signup and pricing paths. Purchases still happened outside the platform, breaking the experience at the moment trust mattered most.

One Bison had built a network of more than 800 vetted businesses, but its directory structure created friction as the product moved toward commerce. Shoppers struggled to understand where to start, while business owners faced unclear signup and pricing paths. Purchases still happened outside the platform, breaking the experience at the moment trust mattered most.

Unclear value proposition

Unclear value proposition

Shoppers couldn't quickly understand why One Bison was different.

Complex navigation and IA

Buyer, seller, service, and discovery paths competed in the navigation.

Low conversion for business signups

Pricing and onboarding left business owners unsure what they were choosing or what happened next.

No path to purchase on the platform

Purchases moved users off-platform, interrupting trust and limiting the marketplace relationship.

MY ROLE

I owned UX design across key buyer and seller experiences, from problem definition through responsive production UI.

I owned UX design across key buyer and seller experiences, from problem definition through responsive production UI.

I designed: Seller onboarding, pricing, discovery, cart, checkout, confirmation, and order-management flows.

I created: Information architecture, user flows, responsive patterns, and reusable components.

I partnered with: Product/founder, engineering, QA, and other business stakeholders to move designs toward implementation.

How I found the highest-friction moments

How I found the highest-friction moments

This led me to prioritize three areas: entry-point clarity, seller onboarding, and transaction trust.

This led me to prioritize three areas: entry-point clarity, seller onboarding, and transaction trust.

Existing-product audit

Existing-product audit

Mapped navigation, IA, signup, and transaction gaps across the live experience.

Behavioral evidence

Behavioral evidence

Used available analytics and product signals to identify where discovery and engagement were breaking down.

Team knowledge

Team knowledge

Combined founder, engineering, QA, and business feedback to understand operational and seller constraints.

KEY DESIGN DECISIONS

  1. Clarifying buyer and seller intent at entry

Decision: Give product discovery primary prominence without hiding business signup.

Why: One Bison had two audiences arriving with very different jobs to be done.

Design response: Simplified navigation and homepage hierarchy around a dominant shopper journey, while keeping a persistent path for business owners.

  1. Making seller value clear before commitment

Decision: Separate seller onboarding from the generic authentication experience and clarify what each plan includes.

Why: Asking business owners to create an account before understanding the value created hesitation.

Design response: Created a dedicated seller journey with clearer pricing, expectations, and progressive onboarding.

  1. Carrying trust into the transaction

Decision: Treat trust as part of checkout UX rather than marketing copy.

Why: Buying from independent sellers introduces questions about payment security, fulfillment, and responsibility.

Design response: Added seller identity, buyer-protection language, itemized costs, payment reassurance, and clear post-purchase support.

THE TRANSACTION LIFECYCLE

The marketplace isn't one screen — it's a chain, and trust has to survive every link. I designed each step to answer the question a first-time buyer is actually asking at that moment.

The marketplace isn't one screen — it's a chain, and trust has to survive every link. I designed each step to answer the question a first-time buyer is actually asking at that moment.

  1. CART: Who am I buying from?

  1. CART: Who am I buying from?

Seller named above the line items, with a plain statement that the order ships directly from them.

  1. CHECKOUT: Is this safe, and what's the real total?

  1. CHECKOUT: Is this safe, and what's the real total?

Guest checkout with an account-found prompt, itemized costs, Stripe and buyer protection under the button.

  1. CONFIRM: Did it work, and what now?

  1. CONFIRM: Did it work, and what now?

Order number, ship-from seller, and a route into order history so the purchase creates an account relationship.

  1. POST-PURCHASE: Where is it, and who helps if it's wrong?

  1. POST-PURCHASE: Where is it, and who helps if it's wrong?

Delivery stepper, tracking, confirm-delivery, and an explicit “Report a problem” path — the backbone of buyer protection.

PRE-LAUNCH MOMENTUM

Business growth is building ahead of the marketplace launch.

Business growth is building ahead of the marketplace launch.

Growth in business signups

Growth in business signups

+32%

+32%

Growth in engaged sessions

Growth in engaged sessions

+45%

+45%

Growth in search usage

Growth in search usage

The commerce experience is currently in development.

The growth above reflects One Bison's existing business and pre-launch marketplace momentum—not post-launch commerce performance. My work focuses on designing the seller, discovery, checkout, payment, and post-purchase experiences that will support this growing ecosystem when transactions go live.

Designing the marketplace to be AI-ready

Designing the marketplace to be AI-ready

I wouldn't add AI simply to make the product feel more advanced. I looked for moments where it could reduce effort while keeping users in control. Each concept follows the same principle: AI can draft, recommend, or explain—but users verify consequential decisions.

I wouldn't add AI simply to make the product feel more advanced. I looked for moments where it could reduce effort while keeping users in control. Each concept follows the same principle: AI can draft, recommend, or explain—but users verify consequential decisions.

AI-assisted product listing

Store URL → AI drafts product data → seller reviews/edit → seller publishes.

Store URL → AI drafts product data → seller reviews/edit → seller publishes.

Augmentation, not automation

Augmentation, not automation

Intent-aware discovery

Natural-language request → matching products → visible reasons → editable filters.

Natural-language request → matching products → visible reasons → editable filters.

Explain recommendations

Explain recommendations

Post-purchase assistance

AI handles status questions → confidence/fallback → human handoff for refunds, money, or disputes.

AI handles status questions → confidence/fallback → human handoff for refunds, money, or disputes.

Escalate high-risk actions

Escalate high-risk actions

WHAT I'D DO DIFFERENTLY

Instrument before redesigning

I designed the signup funnel before reliable event tracking existed. Next time, I would establish baseline events before making major flow decisions so that prioritization is grounded in behavior rather than persuasion.

Design for the commerce model, not today's edge case

My first checkout assumed one seller per order. Supporting multi-seller transactions later introduces split shipping, payouts, and order-status complexity that would have been easier to model earlier.

Talk to sellers sooner

The onboarding flow relied heavily on existing team knowledge and competitive patterns. Earlier seller interviews would have helped me validate which setup fields actually created the most friction.

Next case study

Designing game-based learning for kids with short attention spans

Designing game-based learning for kids with short attention spans

Designing game-based learning for kids with short attention spans