How I build

The right tools, chosen around the job.

I work across strategy, design, code and measurement. The stack changes, but the goal stays simple: build something useful, easy to run and ready to improve.

Connected website, app, data and code interfaces forming one practical digital system
One connected process

More than choosing a platform

A website or app has to explain the offer, support the customer journey and fit the way the business actually works. That usually crosses the line between marketing and engineering.

I can help shape the message, design the experience, build it, connect the surrounding systems and use real behaviour to decide what happens next. That wider view is often more valuable than loyalty to any one platform.

Tools in context

A stack that follows the work

These are tools I work with, not a fixed recipe. I choose and combine them according to the audience, product, team and stage of the business.

  1. 01

    Shape the work

    Clarify the audience, message, structure and product flow before committing to a build.

    • Figma
    • Relume
  2. 02

    Build the experience

    Choose a website or app stack that fits the product, the team and the way it needs to change.

    • Webflow
    • Astro
    • Framer
    • Expo
  3. 03

    Measure and grow

    Connect behaviour, enquiries and pipeline so improvements are based on evidence.

    • PostHog
    • HubSpot
    • Chili Piper
    • Conversion.ai
  4. 04

    Run and connect

    Keep delivery organised, communication clear and the systems behind the customer experience reliable.

    • ClickUp
    • Slack
    • Vercel
    • Cloudflare
    • Resend
  5. 05

    Work with AI

    Use agents and connected tools where they improve delivery, research, testing or repeatable operations.

    • Codex
    • Claude
    • Grok
    • MCP servers
Choosing a stack?

Start with what the work needs to achieve.

Tell me what you are building, what already exists and where the current setup is getting in the way.

What guides the choice

Practical decisions that survive launch

  • 01

    The job comes first

    I start with the audience, commercial goal and working constraints. The platform follows from that decision, not the other way around.

  • 02

    Keep it ownable

    A clever stack is not useful if the team cannot update it, understand it or keep it healthy after launch.

  • 03

    Measure what matters

    Analytics should answer real questions about behaviour, conversion and pipeline, rather than produce another dashboard nobody uses.

  • 04

    Use AI with judgement

    Agents can make delivery faster and remove repetitive work. Important decisions, quality checks and consequential actions still need clear human ownership.

The approach in practice

Websites, apps and connected systems

See all work
Have something to build or improve?

Let's talk about it

Need a website or app built, improved, managed or automated? Tell me what is getting in the way and I'll get back the same working day.

A few useful details

A rough overview is enough to get started.

I usually reply within two working days.