Episode insight · June 2019 conversation
Expansion works when the local need is real
Built In’s early interest from Denver and Los Angeles mattered because local leaders could articulate the problem, the audience, and why rebuilding the platform made no sense.
By Unicorn Road Editorial · Bytes Over Bagels
Katris recalls getting calls from people in other cities who had examined Built In and wanted the same connective tissue for their own technology communities. That demand became the opening for expansion.
Look for a local champion, not just a new market
One of the strongest signals came from a city leader who had already assessed the cost of rebuilding a comparable platform. The question was not whether a central team could launch somewhere new; it was whether a local community had enough conviction to make the platform useful on day one.
Use contrasting markets as a test
Built In chose markets with very different scale profiles. In Katris’s telling, that helped the team learn how the model behaved beyond one familiar city rather than assuming the original market was universally representative.
The practical principle
When a community product expands, do not export a template blindly. Confirm that the local problem exists, find partners who understand the place, and test whether the underlying behaviour—not just the brand—transfers.
This reflects Katris’s 2013 account of Built In’s early expansion.