The Website Was Never the Problem

For a long time, I thought people hired me to build websites. A client would come to me saying they needed a new website, a booking system, a membership platform, online payments, or some kind of automation, and I assumed my role was to take their requirements and turn them into something functional. After years of working with businesses of all sizes, I’ve realised that’s rarely what they’re actually hiring me for.

People come to me asking for websites, but what they’re usually looking for is clarity. A founder tells me they need a booking system, and as we start talking, it becomes clear that the real issue is that customers don’t understand which service they need. Someone asks for a membership platform and, before long, we’re discussing subscriptions, renewals, lifetime memberships and internal processes that nobody has properly mapped out. A business owner wants a contact form, but what they really need is a way to stop enquiries disappearing between inboxes, spreadsheets and sticky notes.

One of the biggest surprises of my career has been discovering how similar businesses are behind the scenes. When I was younger, I was intimidated by large organisations. Big budgets, impressive offices and long strings of zeros on project proposals seemed to suggest they had everything figured out. Then I started working inside them. What I found was that many of the same challenges existed in small family-run businesses. Important information still lived inside someone’s head. Projects still stalled because nobody had made a decision. Processes still depended on one person remembering to do something on a Friday afternoon. The scale was different, but the human challenges were remarkably similar.

Over time, I became less interested in the technology itself and more interested in what happens around it. When a customer submits a form, what happens next? Who receives that information? What decision do they make with it? Where does it go after that? What delays occur? What assumptions are being made? Which part of the process is creating stress or confusion? These questions have become more interesting to me than the software because they reveal how a business actually operates rather than how it thinks it operates.

Some of the projects I am most proud of are not the ones with the most impressive designs or complex functionality. They are the ones that quietly removed friction from somebody’s day. The founder who no longer had to spend hours creating reports. The team who could finally see where every client was in the pipeline. The business owner who stopped answering the same questions repeatedly because customers could find the information they needed. The client who could finally trust that enquiries were arriving where they were supposed to. Most of this work is invisible. When it works well, things simply flow more smoothly.

One belief I have developed over the years is that businesses should not scale complexity. They should scale ease. If growth means more stress, more firefighting and more confusion, then something is broken somewhere in the system. I have worked with founders generating impressive revenue while quietly dreading opening their inbox every morning, and I have worked with founders running smaller businesses who were genuinely excited about serving their customers and still had energy left at the end of the day for the people they cared about. The second group has always looked more successful to me.

Technology should make life easier. Systems should create freedom. Processes should reduce uncertainty rather than increase it. The longer I do this work, the less interested I become in building complicated things and the more interested I become in helping people move from confusion to clarity, from overwhelm to confidence, and from constant firefighting to something sustainable. The websites, systems and automations are simply the tools. The real goal is creating businesses that work clearly, calmly and effectively so the people inside them can do the same.

Related Posts

Most Technical Problems Aren’t Technical Problems

Most Technical Problems Aren’t Technical Problems

A few years ago, I was brought into a project that several developers had already worked on. The brief sounded straightforward enough. A membership organisation needed to separate memberships, subscriptions, payments and reporting across multiple organisations while...

read more
A Website Won’t Save Your Business

A Website Won’t Save Your Business

I've built websites that generated six-figure businesses. I've also built websites that changed almost nothing. The difference wasn't the design. It wasn't the functionality. It wasn't the SEO and it definitely wasn't the website. One of the most successful websites I...

read more