Skip to content

Case study · Two-sided B2B marketplace

AddSale

Businesses apply once. Providers compete for them.

A Latvian B2B marketplace that matches businesses with payment providers. Merchants describe the business once; providers receive a qualified lead with the full requirements and work it through to a signed integration. Built from scratch in four months — a designer and me.

addsale.io
AddSale home page
AddSale home page on a phone
4 months
from start to launch
2 people
a designer and a developer
2 sides
two account types, one dataset
EN · LV
product and pages in two languages

The product

Merchants want the right provider without ten sales calls. Providers want leads that already fit. Both sides work from the same structured data.

MerchantsBusinesses choosing a provider

  1. 1Apply onceCompany, processing needs and payment methods in one structured application.
  2. 2Get a shortlistSent by email once the address is confirmed.
  3. 3Compare and chooseSide by side, up to three providers.
addsale.io/account/provider-selector
Merchant's provider selector in the account

ProvidersCompanies receiving the leads

  1. 1Build a profileMethods, countries, features and integrations — nine tabs.
  2. 2Receive qualified leadsWith the merchant's full requirements attached.
  3. 3Work the pipelineSeven stages, from first contact to integration.
addsale.io/account/leads-opportunities
Provider's leads and opportunities overview

Merchant side

Every provider needs the same answers. The application asks once, in a structure every provider can read — and saves step by step, so nothing is lost.

10
turnover bands, up to 100M+
14
industries
2
channels: online and POS
6
start timelines
addsale.io/account/processing-requirements
Processing requirements step of the merchant application

Provider side

Qualified leads, not cold emails

Every lead arrives with the merchant's full requirements and moves through one shared pipeline, visible to both sides — so nothing stalls silently.

  1. Stage 1Lead
  2. Stage 2Contact
  3. Stage 3Sales
  4. Stage 4Application
  5. Stage 5Underwriting
  6. Stage 6Integration
  7. Stage 7Outcome
addsale.io/account/leads-opportunities
Leads and opportunities table
addsale.io/account/leads-opportunities/139890
A single lead with the merchant's requirements

Matching

Providers describe what they really support. Searchable lists on every tab keep the data comparable, and the same fields power the matching and the public pages.

  • 1Company
  • 2Solutions
  • 3Payment methods
  • 4Countries
  • 5Features
  • 6Verticals
  • 7Integrations
  • 8Languages
  • 9Advantages
addsale.io/account/profile-settings
Provider profile settings with nine tabs

Built to rank

15
method guides
9
comparisons
4
markets
4
platform guides
  • addsale.io/compare/nuvei-vs-adyen
    Provider comparison page

    Head-to-head comparisons

  • addsale.io/providers
    Providers directory

    Providers directory

  • addsale.io/methods/by-country
    Payment methods by country

    Methods by country

  • addsale.io/markets/united-kingdom
    Market page

    Market pages

Team of two

4 months, two people

Design by @khrystyzaidova. Everything else by me: data model, two account types, matching, the lead pipeline, 50 public pages, emails and security.

  • Email verification before any lead is shared
  • Argon2 password hashing
  • Cloudflare Turnstile on public forms
  • How AddSale works on a phone
  • Merchant application on a phone
  • Provider leads on a phone
  • Next.js
  • React
  • TypeScript
  • MongoDB
  • NextAuth
  • MUI
  • Resend
  • Cloudflare Turnstile

Building a marketplace or a B2B platform with two sides to serve?

Let's design the data first and ship it fast.

Clean360 website first screen
Next caseClean360 website

Like this project?

– likes · – views