Moving to London: What Changes When You Join a Global Tech Hub
After building from the US-Mexico border and Italy, I moved to London. A global tech ecosystem changed my perspective on markets and ambition.

I'd built products from Tijuana, San Diego, and Rome. Each city shaped my building style. The border taught me about cross-cultural products, Italy gave me aviation domain knowledge, San Diego provided access to the US market.
London changed the scale of my ambition.
What London Provides
Global market access. London sits at the intersection of US, European, Middle Eastern, and African markets. A product built in London naturally thinks globally. The city's diversity makes domestic-only thinking feel parochial.
Dense ecosystem. Within a few square miles: fintech headquarters, AI labs, legal tech startups, aviation companies, travel tech firms. The density of relevant companies and people is higher than anywhere I'd built before. Accidental encounters with people in adjacent industries happen weekly.
Timezone advantage. London's timezone overlaps with European business hours, the US East Coast morning, and Middle Eastern/African afternoon. For a product portfolio serving global users, London minimizes timezone friction.
Regulatory proximity. The UK's regulatory environment (financial regulation, data protection (GDPR), aviation authority (CAA)) influences European and sometimes global standards. Being close to regulators and understanding regulatory trends firsthand is an advantage for building regulated-industry products.
What Changed in My Building
Market sizing expanded. In Tijuana, I thought about the border region. In San Diego, I thought about the US market. In London, I started thinking about European, Middle Eastern, and global markets. The same product, positioned for a global audience, has dramatically different economics.
Competition awareness sharpened. London's ecosystem surfaces competitors and adjacent products that I wouldn't have discovered from smaller cities. Awareness of competition isn't discouraging. It's informing. Knowing what exists helps me build what doesn't.
Network quality increased. Not better people, but different access. Meeting founders who've scaled across Europe, investors who understand regulated industries, and operators who've built marketplace logistics in multiple countries. The conversations changed from "how do I build this?" to "how do I scale this?"
Product quality standards rose. London users have high expectations. They've used the best products in the world and judge everything against that standard. Building for London users forced quality improvements that benefited all users globally.
What Didn't Change
The fundamentals of building stayed the same. The stack. The process. The prioritization framework. The shipping discipline. The focus on solving real problems for real users.
Location provides context and connections. It doesn't provide the discipline to ship or the judgment to build the right thing. Those came from years of building, not from a postal code.
London accelerated my trajectory by expanding my perspective. But the trajectory was already established by the years of building that preceded the move.
Enjoyed this article?
I write about building products, AI, aviation, and the journey of entrepreneurship. Follow along for more.
Keep reading

Surfyx: What Building a Surf App Taught Me About Distribution
Surfyx is a surf tracking app and social network. Building it taught me that distribution, not features, determines whether a product succeeds in a niche market.

How I Use AI to Run a One-Person Product Studio
I maintain ~20 products solo. AI is not replacing my work, it is multiplying it. Here is how I use Claude and AI tooling to operate at impossible scale.

Building Software for Lawyers: UX Lessons from a Non-Lawyer
What I learned about designing legal software as someone who has never practiced law, and why outsider perspective might actually be an advantage.