Design and Build

Approach

How I think about this work

When I work on a web project, I'm not just thinking about look, feel and user experience. I'm thinking about the business outcomes it needs to enable, the operational practices needed to run it day-to-day, and the capabilities your team needs to maintain and evolve it. For products and platforms, the same thinking extends to application architecture, supportability, and how the whole system stays healthy after launch.

My definition of success is simple: you don't need me anymore. My goal on every engagement is to make myself redundant.

I've worked this way for twenty-five years — since my early days as a management consultant, when I was placed onsite to solve a specific problem and set myself the goal of solving it so completely that the client no longer needed me to do that. It worked. And then they asked me to solve the next problem. And the next.

That pattern has held ever since. The work compounds through trust, not lock-in.

Method

How the work gets done

I bring the systems and architecture thinking, the lived experience, and the team around the work. Modern AI development tooling does the heavy lifting on implementation.

Specifically, I choose to work with Claude Code as my primary development partner because of Anthropic's stance in the world, their values, and their ethical commitment to the betterment of humanity. In a field full of loud and often careless players, Anthropic's approach aligns with how I want to work and who I want to build the future alongside.

But tools don't build products on their own. Out of the box, Claude Code isn't necessarily thinking about your business outcomes, your team's capabilities, or what it takes to keep a product alive at 2am three months after launch. Claude has the knowledge of how to build almost anything, but not the visceral lived experience that haunts an experienced builder — and inspires them. A race car doesn't race itself. An experienced driver knows when to brake, when to corner, when to step on the gas, and when something feels slightly off and needs attention. And just as importantly, they build and lead the team around the car — strategy, pit stops, race conditions, the wider campaign.

That's the work I do. I bring the direction, the judgement, and the lived experience of what it actually takes to ship, operate and support a product. I build the team around the work — integrating the tooling with your people, your operational context, your business goals, and your team's ongoing capability to keep going after I'm gone. Implementation happens faster and cleaner than it used to, but the thinking, the direction and the craft of the work are still mine — and what you get is a system shaped by twenty-five years of experience, not a template.

Value added

What I do across the arc of a project

I work across the full arc, or I drop in on the phase where you need a partner most.

Engagements

How we can work together

Most engagements start with a short discovery conversation — free, no commitment — to understand what you're trying to build and whether I'm the right person to help. From there, I'll propose a scope that fits the phase you're in:

1. A discovery sprint One to three weeks to get clarity before committing to build.
2. A defined build A scoped project to ship a V1 or a meaningful release.
3. An ongoing retainer Monthly, for continuous design, development and iteration support.
4. The next thing, together When an engagement ends well, clients often come back with the next problem. That's how the work has compounded for twenty-five years, and how it still works today.

The principle across all four is the same: senior hands-on involvement, clear communication, work you can actually use — and a deliberate plan for your team to carry it forward.