What I take on

Four kinds of work. The stack follows the brief, and I'll tell you if something is the wrong tool.

AI and automation

Machine learning when the task needs it. Chat and search over your own documents, extraction, and agents that call an API you already use. Orchestration can route requests across models, including local and open models, etc., when that fits the job. If the workflow doesn't need a model, I'll say so.

Models and workflows on a real task, including chat over your own knowledge.

Digital products

I design and build the product: screens, API, and the parts that have to keep working after launch. Recent work has used Next.js, React, Angular, Flutter, FastAPI, etc.

Web apps, mobile apps, and tools a team uses every day.

Websites

Most of this work is Next.js, etc. I use WordPress when you need to edit pages yourself. The aim is a site that is fast, readable, and doesn't need a rebuild to add a page.

Company and product sites that load quickly and are easy to extend.

Product design

Flows, screens, and a small component set in Figma, kept close to the code. I design when I'm also building, and I take design-only work when the brief is already clear.

Interface design an engineer can build, often because I am that engineer.

How a project runs

The note

What needs to exist, who it is for, and any timing already known. A loose note by email is enough to start.

The shape

The flow, the empty and error states, and what is explicitly out of scope. Agreed in writing before the build starts.

The build

Screens and software together. The stack follows the job: Next.js, React, Angular, Flutter, Python, FastAPI, Docker, Kubernetes, Kafka, etc., when the system needs them.

What you leave with

Working software, and a structure another developer can change without a call.