WEBSITES
Your website is fine. Until you need to change something.
Most of the sites I get called in for aren't broken. They're frozen — built years ago by someone who's gone, on a platform nobody left in the company understands, where every small change turns into an outside quote and a two-week wait.
The problem
You have a site that just is.
Content keeps piling up, but the platform, the navigation, the pages that matter and the images have all been left alone for years. Nobody decided to neglect it. There was just never a moment where updating it was more urgent than everything else.
Then something breaks, or you outgrow it, or you need a change — and the person who built it is long gone. If you're particularly unlucky, you're on a platform hardly anyone works with, and finding someone who'll touch it is its own project.
The cost isn't usually one dramatic failure. It's that the site slowly stops being something you can use, and quietly becomes something you work around.
01
It's frozen in the year it was built
Still running the design and structure it launched with. Often not properly usable on a phone — which is where most of your visitors now are.
02
You've outgrown it
It was right for the business you were. Now you sell more things, in more places, to more people, and every addition is a fight with a structure that wasn't built for it.
03
Nobody can touch it
Custom code, a niche platform, or a builder only one person understood. Changing a phone number becomes a quote and a wait, so you stop asking.
How I approach it
A site you can't change isn't finished. It's abandoned.
The most expensive thing about a website usually isn't building it. It's the years afterwards, when nobody in the company can safely alter anything, so nothing gets altered.
So the test I care about isn't how it looks the week it launches. It's whether you can still change a price, add a page or fix a typo two years later without calling anyone.
Some things will always need me. Most things shouldn't.
- Try to change a phone number or a price on your own site. Time it.
- If you can't, name the person who can. Do you still work with them?
- Find out where the site is hosted and who holds the login.
- Check it on your phone. All of it, not just the homepage.
What i do
Built, rebuilt, and kept running afterwards.
-
New builds
Sites built around what your business actually needs to do, on a platform chosen for your situation rather than my preference.
-
Rebuilds and migrations
Moving off a legacy site without losing what works. Old custom themes, hand-coded pages and years of accumulated content, gone through properly.
-
Mobile and responsive
Working properly on a phone — which for most service businesses is where the majority of visitors arrive, and where old sites fail first.
-
Speed and technical health
The unglamorous part: load times, broken links, plugin conflicts, the accumulated debris that makes a site feel old before it looks old.
-
Payments and checkout
Adding or changing payment processors, fixing checkout flows, and dealing with the ecommerce platforms most people won't touch.
-
Integrations
Booking systems, email marketing, CRMs and the other tools your business already runs on — connected properly rather than bolted on.
-
Tracking built in from the start
Measurement designed in while the site is being built, instead of retrofitted afterwards when the structure already works against it.
-
-
Ongoing maintenance
Updates, changes, and the thing that breaks on a Tuesday. I'm still the person you call in year three.
-
HOW I WORK
Repair or rebuild — worked out, not assumed.
Plenty of sites don't need replacing. Some do. Deciding that honestly is the first job, and it's the one that decides what the whole thing costs you.
Find out what's actually there
What the site is built on, what's been added over the years, what's still working and what's quietly broken. Often nobody currently at the company knows all of it.
Decide honestly whether to repair or rebuild
If fixing what you have is the right answer, I'll say so — that's the cheaper outcome for you and I'd rather tell you than sell you a rebuild you didn't need.
Build it so it can be changed
Structured so the things that change often — prices, text, images, pages — can be changed by you, without risk of breaking something.
Connect it to the rest of your operation
Booking, payments, email, and measurement wired in while it's being built, so the site is part of how the business runs rather than a brochure sitting beside it.
Stay reachable afterwards
You should have someone to call when something breaks or you need a change. That's the part that's usually missing, and it's the part I don't drop.
PROOF
What this looks like in practice.
Recent project
A site that hadn't been touched since the early 2010s
A professional association running a WordPress site built on a custom theme, from an era before mobile mattered. It couldn't simply be swapped to a modern theme — years of hand-added markup meant every page had to be gone through and cleaned up individually. Around 60 hours to bring it onto something current, mobile-usable, and maintainable by people who aren't developers.
Related case study
When the site and the measurement don't agree
A booking flow that crossed a domain boundary mid-purchase and lost attribution on every sale. The kind of thing that's invisible in the browser and expensive in the ad account — and a reason tracking belongs in the build, not after it.
FIT
Worth being straight about who this suits.
This is for you if
- Your site hasn't been meaningfully updated in years
- It doesn't work properly on a phone
- You're on a platform nobody in your company understands
- The person who built it is no longer around
- Small changes turn into outside quotes and long waits
- Your site needs to connect to booking, payments or proper measurement
Probably not, if
- You have someone in-house who owns this and does it well
- You want brand identity and visual design work — I build and maintain sites, I'm not a brand designer
- You want the cheapest possible template put up quickly
- You want it built once and never touched again — that's how sites end up frozen in the first place
start here
Start with what you've already got.
Before anyone talks about a rebuild, it's worth knowing what condition your current site is actually in - and whether replacing it is even the right answer.
-
- What it's built on, and how much of that is still supportable
- How it behaves on a phone, and where it falls over
- What's genuinely broken versus what merely looks dated
- Which changes you should be able to make yourself, and currently can't
- Whether repairing it or rebuilding it costs you less over the next three years
You end up knowing what you have and what it would take — whether or not I'm the one who does it.
START HERE
Tell me what you're working with.
What it's built on, what's stopped working, and what you've been putting off. If it's in better shape than you think, I'll tell you that too.