1
0 Comments

What building Zipprr's classified marketplace taught us about local liquidity

I'm part of the team at Zipprr, and this is something we learned the hard way while building our classified marketplace product, not something we knew going in.

A local buy-and-sell app isn't one marketplace. It's a few hundred small marketplaces that happen to share a database. Liquidity lives inside a postcode. If someone lists a sofa and the nearest active buyer is 40km away, the listing is technically live and commercially dead.

We watched a bunch of founders plan a national launch, get thin coverage everywhere, and conclude the product had failed when really it was the rollout geography that failed. Going narrow first, one city, sometimes one set of suburbs, and actually saturating it before expanding, kept coming up as the thing that worked.

A few things fell out of that for us on the product side:

Location has to be the default view, not a filter someone remembers to apply. If a new user's first screen shows listings they can't reach, they leave before onboarding even finishes.

Keeping chat inside the platform matters more than it sounds like it should. The moment a buyer and seller swap numbers and move to WhatsApp, you lose all visibility into whether the deal even closed, so your ratings, your fraud signals, everything goes dark.

Two-sided reviews on every transaction turned out to matter more than we expected too. In P2P classifieds the other person is a stranger, so trust is really the product being sold, not the listing itself.

Still curious how others here who've built or run local marketplaces think about the narrow-vs-wide tradeoff, and whether it held up for you past the first city.

If useful context, the platform is here: zipprr.com/letgo-clone

on September 10, 2026