How I turn an idea into a digital system that holds up

Almost nobody comes asking for a system. They come asking for a website. But when you ask what they expect to happen once they have it, the answer always describes a system: people find them, understand what they do, and get in touch.

The problem first, not the solution

The first conversation isn't about design. It's about where their customers come from today, how fast they reply, what falls through the cracks, and what happens when someone does reach out. Often the bottleneck isn't the website — it's that nobody answers the message for two days.

If that's the case, I say so. A new site doesn't fix a broken process; it just makes it more visible.

Define what 'working' means

Before a line of code, I define with the client what the observable result is: how many requests a month, what share of visitors book, how much manual time gets saved. Without that number, every deliverable is debatable and every result is a matter of opinion.

Build the smallest piece that already helps

I don't ship the whole system at once. I ship the part that already creates value and can be measured: usually the site with lead capture and analytics. The rest gets added when the data says where the brake is.

This avoids the most expensive mistake I see: giant projects that take six months and reach the world without anyone knowing whether any of it worked.

Measure and adjust

Analytics and Search Console go live on day one. The first serious review is at one month: which pages bring people, where they drop off, which searches you're already showing up for. From there you adjust content, structure or message.

A digital system isn't delivered, it's maintained. The difference between a site that ages well and one that gets abandoned is whether someone is reading the numbers every month.