Brad Holmes web developer, designer and digital strategist.

Dad, husband and dog owner. Most days I’m trying to create fast, search-friendly websites that balance UX, Core Web Vitals, and digital strategy from my studio in Kettering, UK.

If you’re here, you either found something I built on Google or you’re just being nosey. Either way, this is me, the work, the thinking, and the bits in between.

Brought to you by Brad Holmes

Lets go

I Spent One Evening Stress-Testing a New Service. Here’s What I Found.

Brad Holmes By Brad Holmes
8 min read

I spent one evening asking hard questions about a new service I’d built. Not market research. Not a focus group. Just an honest conversation that started with “is this landing page ready to run ads on” and ended somewhere I didn’t expect.

I’m not an internet rockstar and I have no interest in becoming one. You won’t find me on TikTok. You won’t find me pumping out Instagram reels. I have two left feet and even less interest in proving otherwise to the internet. I’m not building a personal brand — I’m building a practice. Small, deliberate, capped at eight clients at a time. The goal was never visibility. It was to genuinely help businesses people are proud of perform the way they deserve to.

That’s it. That’s the whole ambition.

But ambition still needs interrogating. So I sat with the questions properly.

Is the service worth creating? Not for money. Not for profile. But because it’s natural and right — because it reflects how I already think about this work and what I already believe good looks like. That’s a harder question than it sounds. Most services get built around what the market will pay for or what’s easy to package and sell. This one had to pass a different test: would I actually want to use it myself?

The answers surprised me. Not because they revealed problems — but because they kept confirming something I hadn’t quite articulated yet. Every decision I’d made about this service, from the price to the free call to the way the portal would work, traced back to the same principle.

Honesty isn’t a strategy. It’s just what good work looks like when there’s nothing to hide.

I’ve been optimising global websites for over twenty years. Sites that get more traffic in an hour than most small business sites see in a year. That scale teaches you things no course or certification does — where performance actually breaks, why conversions quietly die, what fixes actually move the needle. This service exists because small businesses deserve that same standard of thinking and nobody is offering it to them at a price that makes sense.

But knowing that wasn’t enough. I needed to stress-test every part of the experience — the page, the call, the close, the portal, the price, the model — and ask whether each one was honest. Whether each one earned its place. Whether the whole thing held together not as a product but as a genuine offer from someone who means it.


The Page Did What It Should

The landing page converted. Someone booked a call.

That’s the only thing a landing page is supposed to do. Not rank. Not impress. Not demonstrate technical sophistication. Move one specific person toward one specific action.

When I looked at why it worked, there was nothing surprising. The headline said what the problem was. The copy said what the service does. The call to action said what happens next. No fluff, no manufactured urgency, no agency language dressing up a simple offer.

The metrics are good. It’s on brand. It loads fast — or it will, once a large JPG becomes a WebP and a render-blocking script gets deferred. I noticed those issues on my own page while building the service. So I fixed them. That’s the job.

The page isn’t the product. It’s just the door. What mattered was that it was honest about what was behind it.


The Call Is a Working Session

When someone books the free site check, they’re not walking into a sales call.

I’ll have already reviewed their site before they join. Performance scores, crawl errors, conversion friction, Core Web Vitals. I’ll have looked at it properly. When they arrive, we look at it together.

They leave with a clear picture of what’s working, what isn’t, and what changes would make the biggest difference. Whether they become a client or not, that’s a genuine outcome. If there’s nothing worth fixing, I’ll say that. If the site is in decent shape, that’s a good result for them.

There are no guarantees on the internet. A fix that should improve conversions might take three months to show in the data. Google might update something. A competitor might do something unexpected. The work is honest but the outcomes aren’t certain — and pretending otherwise would be the first dishonesty in a relationship that only works if it stays straight.

What I can guarantee is that the session is real. Not a rehearsed pitch with a pricing slide at the end. A working session where someone gets something useful regardless of what they decide.


Every Site Is in a Different Phase

This is the part most people selling website services won’t tell you.

Driving more traffic doesn’t always drive more leads. More visitors through a leaking funnel just means more people leaving. Sometimes the most valuable work has nothing to do with acquisition — it’s reducing bounce rate on a page that almost converts, or finding the long tail keywords that bring the right people rather than more people. The lever that moves the needle is different for every site.

Some sites need fixing. Broken forms, slow pages, conversion paths that go nowhere. That work has a natural end point. You find what’s broken, you repair it, the site performs properly. Three months, sometimes less.

Some sites are on the edge of growth without knowing it. The traffic is there. The product is solid. But the metrics telling the real story — the ones that connect behaviour to revenue — aren’t being read properly. More ad spend won’t fix that. A rebrand won’t fix that. Understanding what’s actually happening underneath will.

And some sites are ready to compound. Consistent improvements month on month. Each fix building on the last. That never really finishes because there’s always another percentage point to find.

The mistake is arriving with a prescription before understanding the phase. Most agencies do this. They apply the same playbook regardless of where the site actually is — more traffic, better ads, new landing pages — because the playbook is what they’re selling.

The first job is always diagnostic. What is this site actually doing? What phase is it in? What lever moves the needle here, for this business, right now?

That question has a different answer every time.


The Portal Is a Log of the Relationship

The client portal I’m building isn’t a product feature. It’s not a dashboard designed to justify the monthly fee or manufacture a sense of activity.

It’s a record of what happened.

Tasks with dated changelogs. Performance scores over time. A log of every time I logged in. A simple request box for when something comes up between months. Clean, plain, honest.

The task flags matter because language matters. “In progress” and “complete” are developer states. A business owner at 11pm checking the portal after a flat month doesn’t need developer states — they need to know whether to worry.

So a fix that’s live but waiting on Google to process it says: Deployed — Results Pending. That flag tells the whole story without a meeting. The work is done. It’s not in our hands anymore. No action needed.

The portal doesn’t make me more valuable. It just makes the work visible. Those are different things.


Churn Is Fine. Staying Is Fine. Both Mean the Work Was Honest.

If a client’s core problems are fixed in three months and they leave, that’s a good outcome. Not a retention failure. Not something to engineer against.

They got what they paid for. The work was real. They leave on good terms.

Some of them will come back when something changes — a new campaign, a performance dip, a site that’s drifted. When they do, I’ll already know their site. There’s no re-onboarding. We just pick up where we left off.

The ones who stay beyond that aren’t staying because the problems aren’t fixed. They’re staying because fixing problems isn’t the same as growth. A site that works properly is the baseline. What comes after that — compounding improvements, better conversion rates, understanding what the data is actually saying — is a different kind of work. Some businesses want that. The ones who do tend to stay.

Neither outcome is better than the other. Both are honest responses to where that site actually is.


The thing I keep coming back to is this: clarity isn’t something you add to a service to make it convert better. It’s what the service looks like when it’s built without anything to hide.

The page is clear because there’s nothing on it that needs obscuring. The call is genuine because there’s no outcome being engineered. The portal is simple because the relationship is simple. The churn is fine because the work is honest. The growth is real because it’s based on what the site actually needs — not what’s easiest to sell.

None of that is a strategy. It’s just what happens when you build something you’d actually want to use yourself.

What you should read next

Brad Holmes

Brad Holmes

Web developer, designer and digital strategist.

Brad Holmes is a full-stack developer and designer based in the UK with over 20 years’ experience building websites and web apps. He’s worked with agencies, product teams, and clients directly to deliver everything from brand sites to complex systems—always with a focus on UX that makes sense, architecture that scales, and content strategies that actually convert.

Thanks Brad, I found this really helpful
TOP