Big ideas, scribbled on small surfaces.
Forget the WeWork-era fantasies of hypergrowth. Up and down the country, lone developers are quietly earning serious money from niche utilities run out of spare bedrooms and garden sheds — and they'd rather you didn't know about it.
Procurement portals, G-Cloud frameworks, six months of silence followed by a Friday-afternoon email — selling to UK councils is a contact sport. Here's the map, the timelines and the tactics from vendors who made it through alive.
Every summer, British software teams down tools and refuse to deploy until September. Is this institutional wisdom or collective cowardice? Yes.
They didn't hire a growth hacker. They didn't do a Series A. They answered their support emails promptly, did good work, and somehow ended up building million-pound businesses while their flashier competitors burned through runway. Meet the British tech founders who got profitable by being, frankly, a bit boring — and why that was the smartest move they ever made.
Somewhere in a British server rack, right now, there is a function called 'fixThisProperlyLater' that was written in 2014 and has processed four million transactions. Nobody remembers who wrote it. Nobody wants to find out. This is the story of the code we're all too mortified to mention — and why pretending it isn't there is making everything worse.
If your startup's core problem takes longer to explain than it does to drink a pint, something has gone badly wrong. The beermat isn't just a surface — it's a diagnostic. Here's how British founders can use ruthless simplification to find out whether they're actually solving a real problem, or just very expensively decorating one.
Your distributed team is working incredibly hard. They're also, almost certainly, building three slightly different versions of the same thing. Nobody meant for this to happen — it never does.
Somewhere in a data centre you'll never visit, a system written before most of your colleagues were born is processing transactions that keep the country running. The developer responsible for it hasn't had a proper holiday in four years. This is their story.
They arrived with a laptop bag and a framework. They left with a day rate that made your eyes water and a 94-slide deck that nobody has opened since the handover meeting. Somewhere out there, they're doing exactly the same thing to someone else.
Manchester has the talent. Bristol has the energy. Edinburgh has the ideas. But London has the salaries, the investors, and an apparently magnetic force field that makes it almost impossible for regional tech hubs to hold onto their best people. Something is going wrong outside the M25, and the consequences are going to be felt for a long time.
British tech companies are haemorrhaging talent, momentum, and sanity — not to bad code or poor strategy, but to meetings. Perfectly avoidable, chronically recurring, soul-destroying meetings that could have been a single Slack message, a two-line email, or absolutely nothing at all.
Somewhere between the third Miro board and the second design sprint, British tech forgot how to actually think. The best software ideas in this country were sketched on napkins, scrawled on pub receipts, and argued over on whiteboards with broken markers — not colour-coded on a £25-per-seat collaboration platform.
The best British software ideas rarely arrive in a flash of inspiration. More often, they're mumbled over a warm pint by someone who's just had a genuinely terrible Tuesday. Here's why the pub remains Britain's most productive R&D department.
Somewhere in a British tech company, there is a beautifully documented, thoughtfully versioned, completely unused API. It took six months to build and has had three external callers — two of which were the developer testing it. This is not a rare story.
While your dev team was busy debating framework choices, Janet in accounts quietly built a self-auditing, macro-driven financial model that's been running flawlessly since 2009. It's time engineers stopped laughing at spreadsheets and started taking notes.
One morning you open LinkedIn and discover your senior engineer has just announced they're 'excited to be joining' somewhere else. You had no idea they were even looking. This is not bad luck — it's a symptom, and it's becoming an epidemic in British tech.
Somewhere in Britain, a development team is six months into building a bespoke notification system. There is a SaaS tool that does exactly this for £49 a month. Nobody mentioned it because nobody asked, and asking would have felt like admitting defeat.
It started as a quick fix. A tab here, a VLOOKUP there, a password nobody remembers protecting a sheet nobody dares touch. Then one day your beloved spreadsheet is running payroll for 400 people and your CTO is crying quietly in the car park.
Before there was Candy Crush, before there was Wordle, there was Dope Wars — a scrappy, anarchic little game that accidentally taught a generation of British teenagers the basics of economics, risk management, and why you should never trust a random event generator. It was basically an MBA in 64 kilobytes.
Your deployment pipeline has seventeen stages, four approval gates, a security scan that takes forty minutes, and a rollback procedure documented across three Confluence pages nobody has read. Congratulations — you have built a magnificent machine for not shipping software. It's time for a beermat reality check.