Start in one suburb, not the whole country.

Strategy · 5 min read

I had a client who wanted to launch nationally on day one. The app would be available across Australia from the moment it hit the App Store. Their reasoning was simple: the more people who can access it, the more chance of success. Makes sense on paper. Doesn't work in practice.

The problem with launching everywhere at once is that you end up proving nothing anywhere. You spread your marketing budget thin. You spread your support capacity thin. And if the app depends on any kind of local density to be useful, you end up with a handful of users in every city and not enough in any one place to create momentum.

Why density matters

Some apps don't need density. A meditation app works the same whether you've got one user in Brisbane or ten thousand. But if your app connects people, relies on local services, depends on geographic data, or benefits from word-of-mouth, density is everything.

Ten users in one suburb talk to each other. They tell their mates. They post about it locally. They create a cluster of activity that makes the app feel alive. Ten users spread across ten cities? They each open the app, see nothing happening, and delete it. Same number of users. Completely different outcome.

Every successful platform company understood this. Uber launched in San Francisco. Airbnb launched in New York. They didn't go national until they'd proven the model worked in one place. Not because they couldn't handle more. Because they knew that density creates the experience that attracts more users.

The marketing math works better small

Say you've got $5,000 for marketing at launch. Spread that across Australia and you've got maybe fifty bucks per city. That buys you nothing. Focus it on one area and you can run targeted ads, attend local events, do direct outreach, and build genuine relationships with early users. That $5,000 goes from invisible to impactful just by narrowing the target.

The same applies to support. When your early users are local, you can meet them. You can watch them use the app over coffee. You can respond to their feedback in hours, not days. That level of attention creates loyalty that no amount of national advertising can buy.

And when something goes wrong, and something will, you're dealing with a contained problem. A bug that affects users in one suburb is fixable. A bug that affects users in fifty cities while you're trying to triage support requests from everywhere is a crisis.

When to expand

Expand when you've got evidence, not optimism. When the users in your first location are actively using the app, recommending it to others, and giving you feedback that's improving the product, that's your signal. When you've figured out your acquisition channels, your retention patterns, and your support processes, you're ready for city number two.

The second city is easier than the first because you've already solved the hard problems. You know what your onboarding should say. You know where users get stuck. You know which features they use and which they ignore. That knowledge makes every subsequent launch faster and cheaper.

Start in one suburb. Own it. Then take the next one. That's not thinking small. That's thinking smart.

Sources
Do Things That Don't Scale (Paul Graham) - Start focused, build density, then expand.
Strategies for Two-Sided Markets (Harvard Business Review) - Geographic focus creates the critical mass needed for platform businesses.

Related blog posts:

How to validate your app idea →

What if nobody downloads it? →

What is an MVP? →