Why I Built a Reverse Marketplace (and Why Traditional Marketplaces Are Broken)

WTB.land — Thu, 09 Apr 2026 18:39:43 +0000

Traditional marketplaces like eBay, Craigslist, and Facebook Marketplace all share the same fundamental design: sellers list products, and buyers hunt through thousands of listings to find what they need.

After spending years as a buyer on these platforms, I realized the model is fundamentally broken - at least from the buyer's perspective. So I built something different.

The Problem with Traditional Marketplaces

As a buyer, the experience goes something like this:

You search for what you want - filtering through hundreds of irrelevant results
You compare prices - opening 20 tabs to find the best deal
You message sellers - only to find out the item is already sold, or the price is "negotiable" (meaning higher)
You repeat - because the first three attempts didn't work out

The buyer does all the work. The seller just posts a listing and waits.

Now flip that around: what if buyers posted what they wanted, and sellers competed to offer the best deal?

The Reverse Marketplace Model

That's exactly what I built with WTB.land (WTB = "Want To Buy").

Here's how it works:

Buyer posts a request - "I want a MacBook Pro M3, budget $1500, good condition"
Sellers see the request and submit competing offers
Buyer picks the best offer - based on price, condition, seller reputation
Deal happens through built-in chat

The key insight: the person with money should have the leverage, not the person with inventory.

Why This Works Better

For buyers:

No more endless scrolling through listings
Sellers compete on price, so you get better deals
You describe exactly what you want - no compromises

For sellers:

You know the buyer is serious (they posted a specific request with a budget)
No need to compete for search rankings
Direct access to motivated buyers

The Numbers So Far

WTB.land launched with:

26 categories (electronics, vehicles, real estate, fashion, collectibles, and more)
5 languages (English, German, Italian, Spanish, Russian)
185+ SEO blog articles driving organic traffic
Zero fees for everyone - buyers and sellers

What's Next

I'm focused on growing the marketplace to critical mass. The classic chicken-and-egg problem of marketplaces applies here too - you need buyers to attract sellers, and sellers to attract buyers.

My approach: focus on niches where the reverse model makes the most sense. Used electronics, collectibles, and vehicles are categories where buyers often have very specific requirements that are hard to satisfy by browsing listings.

If you're interested in trying it out: https://wtb.land

I'd love to hear your thoughts. Is the reverse marketplace model something you'd use? What categories would you find most useful?

I Built a Reverse Marketplace with .NET 10, gRPC-Web, and Vanilla JS

WTB.land — Thu, 09 Apr 2026 17:22:23 +0000

The Problem with Traditional Marketplaces

Every marketplace works the same way: sellers list products, buyers scroll through thousands of listings hoping to find what they need at the right price.

I wanted to flip this model. What if buyers posted what they wanted and sellers competed to offer the best deal?

That's WTB.land - a reverse marketplace (WTB = Want To Buy).

How It Works

Buyer posts a request - "I want a MacBook Pro M3, budget $1500, like-new condition"
Sellers browse requests and submit offers with price and description
All offers are public - sellers compete, highest bid gets a TOP BID badge
Buyer picks the best deal - chat with sellers, compare offers, done

The Tech Stack

Backend: .NET 10 (ASP.NET Core MVC + gRPC)
Database: SQLite (yes, really)
Frontend: Vanilla JavaScript SPA (~1800 lines, no React/Vue/Angular)
Protocol: gRPC-Web over protobuf (not REST/JSON)
CSS: Tailwind CSS 3.4
Deploy: Single binary on a $7/month Hetzner VPS

Why gRPC-Web Instead of REST?

Binary protobuf is ~30% smaller than JSON. I wrote a 98-line custom gRPC-Web transport that handles binary framing over XHR. No code generation on the client - protobuf.js parses the .proto file at runtime.

Why Vanilla JS Instead of React?

The entire SPA is 1800 lines. It does pushState routing, SSR hydration, lazy loading, and real-time chat polling. Adding React would have tripled the bundle size for zero benefit.

Why SQLite?

For a young marketplace with hundreds of requests, SQLite is perfect. Single file, zero config, instant backups.

SEO: The Hard Part

A JavaScript SPA is invisible to search engines by default. My solution: hybrid SSR + SPA architecture.

Server renders full HTML with SEO content (meta tags, JSON-LD, Open Graph)
Client JS hydrates from server-injected JSON - no duplicate API call
Subsequent navigation uses pushState + gRPC calls

Result: Google PageSpeed 100/100 on mobile and desktop.

Try It

WTB.land is live and free. 26 categories, built-in chat, no fees. 60-90ms response times on a single-core VPS.

Have you built anything with gRPC-Web? I'd love to hear your thoughts.

DEV Community: WTB.land

Why I Built a Reverse Marketplace (and Why Traditional Marketplaces Are Broken)

The Problem with Traditional Marketplaces

The Reverse Marketplace Model

Why This Works Better

The Numbers So Far

What's Next

I Built a Reverse Marketplace with .NET 10, gRPC-Web, and Vanilla JS

The Problem with Traditional Marketplaces

How It Works

The Tech Stack

Why gRPC-Web Instead of REST?

Why Vanilla JS Instead of React?

Why SQLite?

SEO: The Hard Part

Try It