When I started building websites, there was a prevailing belief that the more technically perfect a site was, the better it would perform. This wasn't just about speed or mobile responsiveness – though those were certainly factors even in the early days. It was about pristine code, impeccable on-page SEO, and a structure that Google's crawlers could navigate flawlessly. I spent years chasing this ideal, convinced that if I could just build the 'perfect' website, success would inevitably follow.
My early work, particularly for local businesses around Suffolk and Felixstowe, often involved meticulously crafting sites that met every technical guideline I could find. We'd pore over keyword density, ensure every meta tag was just so, and agonise over the exact HTML structure. We were building websites for clients, but in many ways, we were building them for Google.
The Era of Technical Obsession
In the early 2000s, 'web design' and 'SEO' were often seen as distinct but intertwined disciplines. As a developer, my focus was on the underlying architecture. Was the HTML valid? Were the CSS files optimised? Was the server configuration lean? These were the hallmarks of a 'good' website in my mind, and in the minds of many peers. I remember client conversations where I’d proudly explain the technical merits of their new site, assuming they’d share my enthusiasm for its elegant backend or its perfect Lighthouse score (if Lighthouse had existed then, of course).
SEO, too, had a strong technical component. We'd dissect algorithms, study patent filings, and experiment with every known factor to nudge rankings. The idea was simple: if we could make a site technically superior and tick all of Google's boxes, it would naturally rise to the top. This led to an almost obsessive focus on things like clean URLs, deep internal linking structures, and carefully crafted heading tags. It felt like a puzzle, and solving it through technical precision was incredibly satisfying.
I worked on countless projects where the technical implementation was, by all objective measures, excellent. Websites were fast, code was clean, and on-page elements were optimised to within an inch of their lives. We saw these sites climb the search rankings, sometimes achieving impressive visibility for competitive terms. This reinforced the belief: technical excellence was the path to online success.
The Disconnect: When Rankings Didn't Equal Revenue
But over time, a pattern began to emerge that started to challenge this deeply held conviction. I noticed that some of our most technically 'perfect' websites, the ones that ranked highly and attracted what seemed like good traffic, weren't always delivering the expected business results for our clients. Conversely, some less technically sophisticated sites, perhaps built with less developer-centric perfection, were quietly generating significant value.
One particular local e-commerce project comes to mind. We'd built a beautiful, fast, and technically sound online shop. It ranked well for its target products, and analytics showed consistent traffic. Yet, sales were sluggish. The client was frustrated, and so was I. We'd done everything 'right' from a technical perspective, but the cash register wasn't ringing as loudly as we'd hoped. This was a stark contrast to other projects where, for example, a simpler website for a service business, while not technically perfect, converted enquiries into leads at a much higher rate. It was one of the early lessons that taught me the difference between traffic numbers and true business value.
I started to see that our technical achievements, while impressive on paper, often existed in a vacuum. We were optimising for a machine, not necessarily for a human buyer. The user experience, the clarity of the offer, the ease of purchase – these elements often took a back seat to things like perfect keyword placement or minimal HTTP requests. We were building excellent websites, but not always excellent businesses.
This wasn't a universal failure, of course. Many technically sound sites did succeed. But the crucial insight was that technical perfection was a component of success, not a guarantee. It was an enabler, not the primary driver. This was a hard pill to swallow for someone who prided himself on building things 'the right way' according to the prevailing technical wisdom.
The Realisation: Beyond the Code
The turning point came as I moved further into e-commerce projects and started building my own online ventures. The direct feedback loop of my own businesses, where every sale (or lack thereof) directly impacted me, was a powerful teacher. I began to understand that the website itself was rarely the finished product; it was a tool within a larger business ecosystem. This perspective is something I've written about before, particularly how the website was never really the finished product.
My focus shifted. Instead of asking 'Is this code perfect?', I started asking 'Does this help a user achieve their goal?', 'Does this clearly communicate the value proposition?', and critically, 'Does this convert into a lead or a sale?'. I began to understand that sometimes, a slightly imperfect but incredibly clear and persuasive page would outperform a technically flawless one that confused or overwhelmed visitors.
This isn't to say technical quality became irrelevant. A slow, broken website will always struggle. But the hierarchy of importance changed. The user's journey, the business's goals, and the clarity of the message rose to the top. Technical excellence became a supporting act, not the headline. I started letting go of some of the web design obsessions that now seem trivial.
Connecting to Today: Building for Outcomes
This shift in perspective profoundly influenced how I approach building things online today. When I'm working on something like InPlay.finance or developing new tools for my Control Room, my primary focus isn't on the elegance of the code for its own sake. It's on the problem it solves, the value it creates, and the outcome it delivers.
I still value well-built systems – in fact, my automation efforts and the custom platforms I've created are testament to that. But the 'why' behind the build is always rooted in a practical, measurable business objective. The technical implementation serves that objective, rather than being the objective itself.
This journey from technical obsession to outcome-driven building has been one of the most important lessons of my career. It's why I eventually stopped building websites for clients and started building for myself – to have that direct connection to the business impact of every line of code, every design decision, and every strategic choice.
The web has changed dramatically since those early days of technical SEO. Google's algorithms are far more sophisticated, and user expectations are higher than ever. But the fundamental lesson remains: building a great online business isn't just about technical perfection; it's about deeply understanding human needs and delivering real value.
