Founder essay · 6 min · Satish Kumar N

Three cities, three functions

"Locate for function, not for flags — and a three-city company can out-operate a thirty-city one, because every node is doing real work, and none of it is theatre."

Three cities, three functions — illustrated essay card

Most companies expand into a new city for one of two reasons, and both of them are usually wrong. The first is to chase a market — to be physically present where the customers are. The second, which nobody quite admits to, is to plant a flag: a new city on the website, a new line in the investor deck, the quiet satisfaction of looking bigger. I have done both in my career, and I have watched both quietly drain companies that could not afford the drain. A few weeks ago I argued that being present in many places is reach, not scale, and that the two are completely different businesses. This is the other half of that argument — the question of why a company should be in any particular place at all.

Why an operating system frees the footprint

Here is what changes the entire calculation, and it is specific to what we are building. Because Simsy AI is an operating system rather than a service delivered in person, our customers do not need us to be near them. The system reaches a founder in Singapore or São Paulo or Riyadh exactly as well as one across the street — that is the whole point of building an operating system instead of a consultancy. And that single fact frees our physical footprint from the job it performs in almost every other company: the job of market coverage. We do not need an office where our customers are, because the software is already there.

Which leaves a far better question. If we do not locate ourselves to be near customers, then where should we actually be — not to cover a market, but to get the specific things the company needs done as well as they can possibly be done?

Three cities, three functions

That question, asked honestly, produces three cities. Not as three markets. As three functions.

Dubai is where the company is built to meet capital and government. It is our headquarters, in a jurisdiction — the DIFC — that was deliberately constructed for exactly this kind of company, and it sits at the centre of the institutional and sovereign market that is, for the next several years, the most interesting B2B environment in the world for what we do. Dubai is not a market we are covering. It is the function of being close to serious capital and serious buyers, in a place engineered to make that easy.

Bengaluru is where the product is built. It is where the engineering and the AI that make the operating system actually work are designed and maintained, drawing on one of the deepest pools of technical talent on earth — and, for me personally, the city where I built a company once before and learned how it is actually done. Bengaluru is not a market either. It is the function of building the machine itself, located where the people who can build it are.

New York is where the company meets the global capital markets and the kind of credibility a venture of real ambition eventually requires. It is the function of access — to Western investors, to global enterprise, to the conversations a company has when it intends to be more than regional. Three cities. Not three markets, very deliberately, but three functions, each located where it is strongest.

Small footprint, global reach

This is the inversion that I think actually matters, and it is the exact opposite of the model I criticised a few weeks ago. The companies that confuse reach with scale build a large footprint to chase a large market — a flag in every territory, each one rebuilt and re-staffed by hand. We are doing the reverse: a deliberately small footprint, three functional nodes, serving a deliberately unlimited reach. On any given day the operating system is working for an individual founder in Silicon Valley, a faculty cohort in Bengaluru, an intrapreneur inside a Dubai or Saudi enterprise, and a development-agency portfolio across Africa — none of which requires a flag in any of those places, because the system is already in all of them. The footprint is small precisely so that the reach can be total.

Locate for function, not flags

So here is the principle, and it is one I would offer any founder thinking about where to be. A footprint that matters is one you can justify by what each node does, not by how the map looks. If you can say exactly what a location is for — what function it performs that the company genuinely needs, and that the place performs better than anywhere else — then it belongs. If you cannot, it is a flag. And flags are expensive. They cost rent and travel and management attention and the slow dilution of focus, and they return, in exchange, mostly the feeling of being bigger. Locate for function, not for flags, and a three-city company can out-operate a thirty-city one — because every node is doing real work, and none of it is theatre.

The startups of the future aren't destined to fail — and the companies built to serve them are not required to be everywhere in order to matter everywhere. That used to be a contradiction. An operating system dissolves it: you can build from three cities chosen for what they do, and still reach every founder, in every language, on every continent. Small footprint. Total reach. That is not a compromise between the two. It is the entire point.

— Satish Kumar N · Founder & CEO, Simsy AI · Dubai · Bengaluru · New York

Build. Launch. Scale.

Get the next one in your inbox.

Founder essays, methodology notes, and the quarterly Hero KPI update. No spam, unsubscribe anytime.