I build web products and AI systems that solve real business problems.

I work on SaaS platforms, web applications, dashboards and internal tools, AI agents and workflow automation, and business websites and landing pages. The common thread is a specific business problem rather than a particular technology.

Yes. I regularly improve, extend, optimize, or rebuild systems that are already running, including inherited codebases and platforms built by someone else. My first step is understanding what is already there and what is actually causing the problem, before I change anything.

Yes. I design in Figma and build the result myself, covering interface design, responsive layout, and the full frontend and backend build. For projects that need specialist brand or illustration work, I will tell you that rather than stretch.

Four steps. First I understand the problem: the workflow around it, who it affects, and what constrains the fix. Then I plan, agreeing the simplest thing that actually solves it and writing down what is in scope and what is not. Then I build, sharing working versions as they land so you can steer while steering is still cheap. Then I improve, letting how the thing actually gets used decide what changes next instead of guessing up front. Most of the value is decided in the first step, which is why I spend real time there before writing code.

I quote a fixed price for an agreed scope rather than billing by the hour, so you know the cost before the work starts. What a project costs depends on what it has to do, so I give you a number after the scoping conversation rather than a price list before it. That conversation is free and carries no obligation, and the written scope that follows it states what will be built, what it will cost, and roughly how long it will take.

It depends on scope. A landing page is measured in days, a business website in weeks, and a web application or AI system in weeks to months depending on how much has to be figured out first. I give you a timeline after the scoping conversation, not before it.

Yes. I do not disappear at launch. If something I built breaks, I fix it. Beyond that, I can stay on for ongoing changes, new features, or maintenance, arranged as an agreed monthly scope or as individual pieces of work. If you would rather run it yourself, that works too: the code and accounts are yours, structured so another developer can pick it up without needing me.

I reply within about a day. If the problem looks like a fit, the next step is a short call to understand the workflow, the goal, and the constraints. After that you get a written scope covering what will be built, what it will cost, and roughly how long it will take. There is no charge for that conversation, and no obligation to continue.