Why we chose hyperlocal over broad reach for Urban Hood

Every social app that starts small eventually gets asked the same question: when are you expanding? We get it early with Urban Hood, usually from people who mean it as encouragement. But the premise of the question, that "broad reach" and "real reach" are the same thing, is exactly what we built against.

Urban Hood is a shared space for the people of one neighborhood. Local places, local happenings, local voices, built for residents, not advertisers. That last part matters more than it sounds. A broad-reach community app has to monetize breadth, which means it eventually optimizes for engagement across strangers instead of usefulness among neighbors. We didn't want to build something that gets better as it gets bigger and worse as it gets more personal. We wanted the opposite.

A neighborhood is a strange, specific unit. Everyone in it already shares something real: a street, a school run, a local shop that's been there longer than anyone can remember. A broad platform has to manufacture that sense of shared context with algorithms and interest graphs. We just had to not get in the way of context that already existed.

We could build a thin layer over "everywhere," or a real layer over "here." We picked here.

So the tradeoff was obvious once we named it honestly: we could build a thin layer over "everywhere," or a real layer over "here." We picked here. It's a smaller number on a slide, and we think it's a better product, and we'd rather be right about the second thing than impressive about the first.