Skip to content

I take products from the first sketch to launch.

I design it, build the front end and the agents behind it, and ship it.

What I take on

Four things, and I do them myself.

  • Product design

    I research the problem, map the flows, draw the screens and build the component system underneath them. Dense B2B tools are where I spent five years at Maersk.

  • AI agents and automation

    I automate the work around the product: research, reporting, outreach and the jobs nobody wants to do twice. The agents run on their own, and rules decide what waits for your approval.

  • Growth and search

    I design the content structure and the technical SEO in from the start rather than bolting them on later. One site climbed from under 100 daily search impressions to 5,003 in about six months.

  • Brand and visual

    I make the identity, the campaign work, the motion and the icons. When nobody else covers that part, it does not wait for a second hire.

How it runs

I write it down first, then build it in the open.

  1. 01 · One conversation

    Book a call. I look at what you have, say what I would do first, and tell you if I am the wrong person for it. No charge and no deck.

  2. 02 · A brief we both sign off

    We agree what we are making, who it is for and what finished looks like. That agreement decides whether the rest goes well, so it comes before I build anything.

  3. 03 · You watch it get built

    You see working screens, then working software, rather than a reveal at the end. Anything that reaches your customers waits for your call.

What you end up with

Things you keep, and a team can take over.

  • Software running in production, not a prototype.
  • The Figma file behind it: components, states and specs a developer can build from.
  • The agent workflows, and the rules that decide what runs on its own.
  • An architecture document in the repo, so whoever touches it next knows the standard.
  • Content structure and search that ship with the product rather than arrive later.

Proof

One I built exactly this way.

The Engine Behind This Site

A portfolio that sits still is a brochure. I wanted a system I could run: one that keeps the work organized, does the research and the reporting on its own, and holds to a standard I would defend in a review. That meant building production software, and I am a designer who does not hand-write code.

Tell me what you are building.

A call costs you half an hour. You leave it knowing what I would do first, whether or not you hire me.