Most founders are building the wrong thing. They're obsessed with the wrong metrics, listening to the wrong people, and fetishising the wrong part of the process.
They are infatuated with technical complexity, believing the sheer intellectual weight of their code will forge an unassailable moat. It won’t. I learned this the hard way: market timing eats technical complexity for breakfast. A product the market needs right now will always beat a technically perfect product the market isn't ready for.
This isn't a pithy tweet. It's a lesson written in tens of thousands of pounds of my own wasted money and hundreds of hours of fruitless engineering. It's the scar tissue that informs every decision I now make, both in building our own agentic AI products and in advising the UK's most ambitious brands at Creative Marketing Group.
Early in my journey, before we had the clarity that led to products like Competable and Autoemails, I was convinced that the path to victory was through building something so technically intricate, so layered with complex logic, that competitors would simply give up. I fell for the siren song of the 'technical moat'.
The product was a horribly convoluted competitive intelligence platform. It attempted to ingest, analyse, and synthesise a bewildering array of unstructured data from dozens of sources. The engineering challenge was immense, and frankly, that's what excited me. I loved the intellectual puzzle. We spent months architecting database schemas, debating normalisation, and building byzantine data pipelines. In my mind, every line of code was another brick in our fortress.
The reality? Nobody cared. We had created a Swiss Army knife with a thousand blades for a user who just needed a screwdriver. The market wasn't thinking about the problem with the level of nuance our product was designed to solve. They were still using spreadsheets and Google Alerts. Our solution was technically elegant, but commercially illiterate. We were trying to sell a Formula 1 car to someone who needed to pop to the shops. It was a painful, expensive failure in market education.
This is a classic founder trap. We fall in love with the 'how' and forget the 'why' and, crucially, the 'when'. We assume that a product's value is directly proportional to the difficulty of its creation. The market has a brutal way of disabusing you of this notion. In an era where a new open-source model can kneecap your 'proprietary' algorithm overnight, a moat built on technical complexity is a sandcastle against the tide.
Distribution is the Only Moat That Matters
Here’s my contrarian take, forged in the fires of that failure: your product doesn't need to be 10x better if your distribution is 100x better. The real, durable moat is not your codebase; it's your ability to acquire customers profitably and at scale.
The product is not just the software. The product is the entire system of value, from the first ad a user sees, to the landing page they hit, to the onboarding email they receive, to the core function they use. Distribution isn't just 'marketing' tacked on at the end. It is the product.
Look at Monzo. When they launched, was their core banking product technically 10x better than Lloyds or Barclays? Of course not. It was a simple prepaid card with a slick app. But their distribution was revolutionary. They created a movement. The hot-coral card became a status symbol. The waiting list, the golden tickets, the transparent tone of voice—it was a masterclass in building a distribution engine fuelled by community and word-of-mouth. They didn't out-engineer the incumbents; they out-marketed them. The moat wasn't in their banking ledger technology; it was in the 1.6 million people on their waiting list before they even had a full banking license.
This is what we do for our clients. We don't just build ad campaigns; we design and implement entire customer acquisition engines. We build the distribution moat. My own experience building products has shown me that without this, even the most brilliant engineering is just a vanity project.