Approach
Four steps. One price. One person.
No nine-phase process diagram. This is how a project actually runs.
From first message to handover: a landing page in two to three weeks, a web application in four to ten. You see the first working version after roughly two weeks.
The call
30 minutes. You describe how things work today and what is wrong with it. I ask questions and tell you honestly whether I am the right fit. Free, and with nothing attached afterwards.
Scope and fixed price
One page: what gets built, what explicitly does not, by when, for how much. You sign a number, not an estimate. That page is also what we both measure the result against later.
Building, in the open
After roughly two weeks you see the first working version: not a picture of one, something you can click. Then a steady rhythm. You always know where things stand without having to attend meetings for it.
Handover
Go-live, a walkthrough, documentation, every credential. The code is yours. After that, either a maintenance agreement or silence. Both are fine, and I have had both.
Stated openly
How I work this fast.
I develop with AI assistance. All three projects on this site were built that way. I write that down plainly because it is the honest answer to how one person handles the workload of a small agency.
The benefit to you is not the tooling, it is two numbers: the price and the date. What an agency quotes at four months and five figures, I deliver in weeks. Not because I type faster, but because typing is no longer the bottleneck.
What explicitly does not change is accountability. I review, test and stand behind every line that reaches your server.
Is an AI just writing this?
No. An AI types faster than I can. What it cannot do is decide what should be built, where the edges of your business are, and which mistakes will cost you money at month end. That is my job. I review, test and stand behind every line that ships, with a completed computer science degree and four years of professional experience behind it. The difference for you is not quality. It is the price and the date.
What I hold to
Nothing only I can operate
Proven, widely used tools instead of exotic choices. So that any other developer could take over, even if it never becomes necessary.
The code is yours
Repository, credentials, documentation, on final payment. There is no dependency on me that I maintain artificially.
Bad news travels immediately
If a date is at risk you hear about it the day I know, not in the week it was due.
Accessible, because it is part of the job
Contrast, keyboard operation, screen readers. This site is the evidence: no cookies, no third-party servers, WCAG-checked colour values.
Two questions everyone asks
What happens if you are unavailable?
The fair question to ask one person. So: the code sits in a repository you have access to, documentation sits next to it, and nothing in the stack is exotic enough that only I can operate it. Any other developer can take over. That is not a contingency plan, it is the baseline.
Do I own the code?
Yes. Entirely, with all credentials, on final payment. No subscription you are locked into, no licence I can withdraw.
Does that fit?
Then tell me in two sentences how things work today. 30 minutes, no obligation, no slide deck.