Skip to content

From idea to deployed

Built in days. Built to keep working.

Web development, design, technical SEO and automation. One person, start to finish.

Websites, web apps and Webflow builds for people who want the thing working, not a deck about the thing. The automation goes in too, so it keeps running after you stop watching it.

Book a callSee the work
Where
Remote, working globally
Who with
Founders and small teams
Right now
Available for new builds

how a build runs

  1. tell me what it has to do
  2. design and build the thingweb
  3. structure it so it can be foundseo
  4. wire the forms, the leads, the integrationsn8n
  5. ship it to accounts you ownlive
Stack
  • codeNext.jsTypeScriptReactTailwindPythonDjango
  • no-codeWebflowWordPressShopify
  • seoSearch ConsoleSchemaCore Web Vitals
  • automationn8nAPIsWebhooks
  • deployVercelGitHubCloudflare

Services

What I build

Six things, done properly. No packages, no price list. Every one of them starts with a call.

  1. 01

    Web design and build

    Landing pages, marketing sites and redesigns. Designed and built to say what you do in the first line.

    • Landing pages
    • Marketing sites
    • Redesigns
    • Copy
  2. 02

    Web apps and MVPs

    A working product instead of a deck. Real data, real accounts, deployed where people can use it.

    • MVPs
    • Internal tools
    • Dashboards
    • APIs
  3. 03

    Automation that runs itself

    Lead capture, outreach and internal workflows wired together so the thing keeps working after launch.

    • n8n workflows
    • Integrations
    • Lead routing
    • Notifications
  4. 04

    Technical SEO

    The half of SEO that is engineering. Structure, schema, speed, and the reporting set up so you can see what changes.

    • Site structure
    • Schema
    • Core Web Vitals
    • Search Console
  5. 05

    Webflow builds

    For sites your team edits without calling a developer. Built properly, with the CMS set up so nobody can break the layout.

    • Webflow
    • CMS collections
    • Migrations
    • Handover
  6. 06

    Deployment and handover

    Shipped, monitored and handed over. Repositories, domains and pipelines you actually own.

    • Vercel
    • GitHub
    • Domains and DNS
    • Monitoring

Something that is none of the above

Most work is a mix of several of them anyway. Describe the problem and I will tell you whether I am the right person for it.

Book a call

Selected work

Recent builds

A short caption each. If you want the detail behind one of them, ask on the call.

All work

How we work

From your requirements to a finished product

Six stages, the same every time. What you have to do is in every card, because it is the part people actually want to know.

Day oneLive
  1. 01Half a day

    Requirements

    We agree what the thing is for and who it is aimed at, before anything gets built.

    You
    One call, then answers to a short list of questions
    Me
    Turn all of it into a written specification
  2. 02One to three days

    First draft

    A version to react to instead of a blank page. This is where the speed comes from.

    You
    Nothing yet
    Me
    Build the layout, the code and the copy
  3. 03Runs alongside the draft

    Review

    Every line read, tested and corrected, on real devices. Nothing ships because it looked right on my screen.

    You
    Nothing yet
    Me
    Throw out what is wrong, test what is left
  4. 04Half a day to two days

    Automation

    The parts that keep working when nobody is watching the site.

    You
    Access to the tools you already use
    Me
    Wire the forms, the leads and the integrations
  5. 05Half a day

    Launch

    Live on infrastructure in your own accounts, documented and handed over.

    You
    A review pass, then the go-ahead
    Me
    Deploy, document, transfer everything
  6. 06Your call

    After launch

    Changes, additions, or nothing at all. Whichever suits you.

    You
    Decide whether you want ongoing work
    Me
    Hourly for defined pieces, or a monthly retainer

Worth saying plainly

Tools have got faster. Deciding what to build, noticing when something is quietly wrong, and carrying the consequences have not. That part is still a person, and on your project the person is me.

Start at stage one

Questions

07

The things people ask first

Mostly about the AI part, and reasonably so. Longer answers to the first three are on the blog.

Something not covered here?

Ask it on a call. Thirty minutes, no pitch.

Book a callor email
  • 01What do you actually build?

    Websites and web apps, in code or in Webflow depending on who has to edit them afterwards. Technical SEO so they can be found, and automation so the leads and the admin move without anyone copying and pasting.

  • 02Webflow or custom code?

    Webflow when the client wants to edit pages themselves without calling a developer. Custom code when the site has to do something Webflow cannot, or when it is an application rather than a set of pages. I will tell you which one your project is on the first call, including when the answer is the cheaper one.

  • 03How fast is a typical build?

    A marketing site is usually days rather than weeks. A web app with real business logic is two to three weeks for a working first version. Anyone quoting one number for every kind of project has not thought about it properly.

  • 04Do you do the SEO as well?

    The technical half, always, because it is part of building the thing properly: structure, metadata, schema, speed, and Search Console set up so you can see what happens next. Content and ongoing link work is a separate conversation.

  • 05What does the automation actually do?

    Usually it removes a step that depends on somebody remembering. An enquiry reaching the right person in the tool they already use, a follow-up that fires on its own, a record that writes itself. Mostly built in n8n, connected to whatever you already run on.

  • 06What does it cost?

    Hourly for defined pieces of work, or a monthly retainer for ongoing work. There are no fixed packages, because packages always either cheat you or cheat me. Pricing comes out of the first call.

  • 07Do I own what you build?

    Yes. Everything is deployed to accounts in your name, in a repository you control, and documented well enough that somebody else could pick it up. If you cannot leave, I have built the wrong thing.

Available for new builds

Tell me what you are building

Thirty minutes, no pitch. You describe the problem, I tell you whether it is worth building and roughly what it takes.

Book a callSend an email

Usually replies within a day. Remote, working globally.