Brighton and the Web
How a seaside city became one of the UK's most interesting places to build software, and why geography still matters in a remote-first world.
Brighton and the Web
Brighton has more tech workers per capita than anywhere in the UK outside London. For a city of 290,000 people, that’s absurd.
There’s no university computer science programme driving it. No government tech hub. No tax incentives. People just keep showing up and building things.
The Accidental Scene
In the early 2000s, Brighton was cheap enough that freelance web designers could afford to live there while working for London agencies. The train to Victoria takes 55 minutes. Close enough to take meetings, far enough to have a life.
Those freelancers became small agencies. The agencies hired graduates who couldn’t afford London rent. The graduates eventually went freelance. The cycle repeated.
By 2015, Brighton had a density of independent web professionals that rivalled cities five times its size. Not because anyone planned it, but because the conditions were right: affordable rent, good transport links, a creative culture that didn’t take itself too seriously.
Why Geography Still Matters
The remote work revolution was supposed to make location irrelevant. In some ways it has — I work with clients across the UK and occasionally beyond. But geography still shapes the work in ways that aren’t obvious.
Local clients have local problems. A Brighton restaurant has different needs than a Manchester restaurant. The tourist season, the demographic, the competition — these are geographic realities that inform design decisions. Understanding the place helps you understand the business.
Proximity enables trust. Video calls are fine for status updates. They’re terrible for the early, ambiguous conversations where a client is trying to articulate what they need. Sitting in someone’s shop, seeing how they work, noticing what they struggle with — that’s how good briefs happen.
Community creates accountability. In a small city, your reputation travels fast. Every project is a reference. Every client talks to other businesses. This creates a natural quality filter that doesn’t exist when you’re a faceless contractor in a global marketplace.
The Brighton Client
After years of working here, I’ve noticed a pattern in Brighton businesses. They tend to be:
Independent. Brighton has more independent shops per capita than any UK city. These aren’t franchise operators following a corporate playbook — they’re people who care deeply about what they’re building.
Design-aware. Living in a city with strong creative energy means business owners have higher visual standards than average. They notice when a website looks generic. They care about typography, even if they can’t name the font.
Pragmatic. Brighton is expensive enough that budgets matter. Businesses here don’t want overbuilt solutions. They want something that works, looks good, and doesn’t cost a fortune to maintain. This aligns perfectly with how I like to build.
Building for Here
There’s something satisfying about building software for your own city. Walking past a restaurant and knowing their booking system runs on code you wrote. Seeing a shop’s website on your phone and remembering the afternoon you spent photographing their products.
It’s not scalable. It’s not a venture-backed growth story. But it’s work that connects to a place, and that connection makes both the work and the place better.
Brighton doesn’t need another tech hub narrative. It just needs people who build good things for the businesses around them. That’s enough.
Good software, like good cities, is built by people who give a damn about where they are.