Stop Hiding Behind the Deck: If You Can't Explain It on a Beermat, It Isn't Ready

There's a particular kind of meeting that happens in co-working spaces across Britain every single day. Someone opens a laptop. The fan whirrs to life like a tired border collie. A PowerPoint loads — forty-three slides deep, full of arrows pointing at other arrows — and the person presenting says, with complete sincerity, "So this is our MVP."

It isn't.

What they've built is a pitch. A mood board with a roadmap stapled to it. A collection of assumptions dressed up in Montserrat Bold. The actual product — the thing someone might conceivably hand over money for — is buried somewhere around slide thirty-one, sandwiched between a TAM/SAM/SOM diagram and a quote from a podcast nobody listened to.

Britain's tech scene has a PowerPoint problem. And the cure, as it turns out, has been sitting on pub tables the whole time.

The MVP Myth We All Quietly Agreed To

The minimum viable product was supposed to be a liberating idea. Ship something small. Learn fast. Don't build the Death Star when a catapult will do. Eric Ries said it, everyone nodded, and then — somehow — the concept got completely mangled in translation.

What 'MVP' came to mean in practice was: build the smallest possible thing that still requires six months of development and a pitch deck to contextualise. The 'minimum' quietly expanded. The 'viable' got hedged into oblivion. The 'product' became optional.

Ask a British founder to describe their MVP and you'll often get a ten-minute explanation that begins with market context, pivots through a competitor analysis, and eventually — breathlessly — arrives at what the thing actually does. Which is fine for a Series A conversation. Catastrophic for a Tuesday afternoon in a Pret.

The beermat principle isn't a design methodology. It's a honesty test. If you can't write down what your product does, who it's for, and why they'd pay for it in the space of a soggy cardboard circle, you haven't got a product yet. You've got a hypothesis with branding.

What 'Simple' Actually Looks Like

Consider some of the most quietly successful software businesses to come out of the UK in recent years. Not the ones that raised £40 million and appeared on the BBC. The other ones — the ones making genuinely good money while their founders drink tea and go to bed at a reasonable hour.

A small team in Leeds built a tool that does exactly one thing: it reminds tradespeople to send invoices before they forget. That's it. No CRM integration. No AI-powered cash flow forecasting. No 'ecosystem'. Just: you did a job, here's a nudge, get paid. The whole product fits on a beermat with room to spare. It has thousands of paying customers and a churn rate that would make a VC weep with confusion.

A two-person outfit in Bristol makes software for independent letting agents to handle maintenance requests without using WhatsApp groups. Again — one problem, one solution, one sentence. They didn't spend eight months on 'discovery'. They asked three landlords what was annoying them, and then built the thing that was annoying them.

Neither of these companies has a product vision slide. Neither has a North Star metric framed above the kettle. They have something rarer and more valuable: a product you can explain to your mum without her eyes glazing over.

The Customer Discovery Theatre Problem

Here's where it gets uncomfortable. A lot of what passes for 'customer discovery' in British startups is, if we're being honest, a sophisticated form of procrastination.

You interview fifteen potential users. You synthesise their feedback into themes. You build a journey map. You run a jobs-to-be-done workshop. You present your findings to the team. You update the roadmap. You schedule another round of interviews. Three months pass. Nobody has built anything.

This isn't discovery. It's anxiety with a Miro board.

The beermat approach forces a different question. Not what might users conceivably want in an ideal world, but what is the smallest useful thing I can ship this week. It's the difference between studying the menu and actually ordering something.

The founders who get this right tend to have an almost embarrassing willingness to ship before they're ready. Their first version is clunky. The onboarding is a Google Doc. The pricing page is a PayPal link with a handwritten label. But it works. And crucially, it tells them something true — which is more than forty-three slides ever could.

Why British Founders Are Quietly Rejecting the Deck

There's a generational shift happening, mostly below the radar of the tech press. A cohort of British founders — many of them outside London, most of them bootstrapped — are building things that are almost aggressively simple. Not because they lack ambition, but because they've watched too many overfunded startups spend two years building something nobody needed, and decided they'd rather just ship the thing.

They're using Notion instead of a product spec. They're doing 'customer calls' over a pint rather than a Calendly link. They're launching to a hundred people instead of waiting for a thousand. They're treating their first product like a conversation starter, not a finished sentence.

And they're making money. Actual, real money. The kind that arrives in your bank account rather than your cap table.

This isn't anti-ambition. It's anti-theatre. There's a difference between building something small because you lack vision, and building something small because you understand that small and working beats large and theoretical every single time.

The One-Sentence Test

Before you open Figma. Before you book the co-working space. Before you register the company and buy the domain and argue about the logo for three weeks — do this.

Write down what your product does in one sentence. Not a mission statement. Not a positioning line. A plain English description of the thing it does and who it does it for. If you need a second sentence to make it make sense, that's fine. If you need a third, you might want to have another think.

Then write down who pays for it and why.

That's your beermat. That's your MVP. Everything else — the features, the integrations, the pricing tiers, the eventual Series A narrative — comes after you've shipped the thing the beermat describes.

The deck can wait. The beermat cannot.

Because here's the truth that every overworked founder eventually learns: nobody ever bought a PowerPoint. They bought the thing the PowerPoint was trying to explain. Start there.