Approach

How I build, and why.

Every site here is custom-built and shipped as static files. That one decision shapes the speed, the running cost, and how much of your week the site takes up after launch. Here’s the reasoning, the rules I hold every build to, and what the four to six weeks actually look like.

Why static

Most small business sites are heavier than they need to be.

Page builders are quick to start and expensive to live with. I build the other way round: more care up front, almost nothing to maintain after.

Speed

Four to eight seconds on a phone, once the plugins finish loading.

A second or two on a phone. Nothing to wait for.

Upkeep

Theme updates, plugin updates, PHP updates, and something breaking every few months.

Nothing to update. Less to break.

Cost

A builder subscription, plugin renewals, and a bill every time something goes wrong.

One flat monthly price. Hosting, backups, and care included.

Security

A login page and a plugin stack that bots know by heart.

No database, no admin panel, nothing to break into.

The rules

Six rules. No exceptions.

These aren’t aspirations. They’re the checks every site has to pass before the DNS gets cut over.

  1. Rule 01

    It still works in ten years

    No framework to fall out of date, no build step to break, no plugin that stops being maintained the year after you launch. HTML and CSS are the only things on the web that have never stopped working.

  2. Rule 02

    Mobile is the design

    I design for a small phone first and enhance up to a 4K monitor, not the other way round. Most of your visitors are on a phone.

  3. Rule 03

    Accessible from day one

    Semantic HTML, real alt text, keyboard navigation, AA contrast at minimum. Plenty of your customers use glasses, assistive tech, or both.

  4. Rule 04

    Nobody gets to watch your visitors

    No retargeting pixels, no ad tech, no fonts phoning home to Google. Analytics is there to tell you which pages get read, it stays off until a visitor accepts it, and it never follows anyone to another site. Everything that loads is named in the privacy policy.

  5. Rule 05

    It reads with JavaScript switched off

    Every page is plain HTML before a single script runs. Turn JavaScript off and you still get the words, the links, and the whole site; the scripts add polish, never content. Search engines and screen readers see exactly what your customers see.

  6. Rule 06

    You own the keys

    Your domain stays registered in your name. I manage DNS however you prefer, but I never hold the domain itself. Want the source code? Ask, and I’ll quote a buyout.

How it works

Four to six weeks, give or take. You’ll know where things stand every day.

No mystery and no big reveal at the end. You watch the site take shape as it happens.

  1. 01 · Before we start

    Discovery call

    Thirty minutes on the phone or over coffee. What you do, who you want to reach, what’s working and what isn’t. Free, and not a pitch.

  2. 02 · Week one

    Content and structure

    What pages you need, what each one has to do, and what it actually says. Getting this right first is why the build goes quickly and why nothing gets written twice.

  3. 03 · Weeks two onward

    Daily staging links

    While I build, you get a private link that updates every day. Look at it on your phone, show it to your staff, send me notes. Nothing is a surprise on launch day.

  4. 04 · Final week

    DNS cutover

    I point your domain at the new site, check every page on real devices, and hand you the keys. Then the looking-after starts, and you go back to running your business.

Next step

Sound like the way you want it done?

The first step is a thirty-minute call, and it costs nothing. Tell me what you do and what is bothering you about the site you have.