Why we built trust before we built features
Most marketplaces optimize for liquidity first and clean up trust later. We did the opposite. Here's why - and what it cost us.
The fastest way to grow a marketplace is to lower the friction of joining it. Let anyone list, let anyone book, and let volume sort out quality. It works, until the first bad experience, which in a home-services marketplace means a stranger in someone's home.
We decided early that trust would be a precondition, not a feature we added once we had scale. That choice shaped the whole platform.
What "verified" actually means
Before their first job, every Neighbour verifies a government photo ID with a live selfie check, and our team reviews and approves their profile and each service they offer. Some services need extra documents, like certifications or photos of past work. Whether a Neighbour is allowed to work is decided on our servers, not in the app; the app just shows those rules, it never sets them. A Neighbour who hasn’t been verified and approved simply isn’t offered work, no matter what any screen shows.
Residents stay protected too. By default we show a first name and last initial, not full identities, and we lean on PIPEDA-aligned privacy practices rather than collecting everything we technically could.
The cost
Asking every Neighbour to verify their ID and be approved before they work means slower Neighbour sign-up and a smaller catalog on day one. That's a real cost, and we paid it deliberately. A marketplace where the median experience is excellent and the worst experience is contained beats one that's merely large.
Trust compounds. Every verified Neighbour, every booking that goes smoothly, every reported problem reviewed fairly makes the next resident a little more willing to open their door. That’s the asset we’re actually building.