How I work
A calm, prototype-first process that turns “I think I want…” into something you can click — usually within a couple of weeks.
The process, step by step
Prototype-first. Always.
Most projects go wrong in the gap between what you meant and what got built. So I close that gap early: you get a working prototype you can click, react to, and change — long before it's expensive to change. Ten years in, it's the one habit that has made projects calmer and better for everyone.
Five steps, no surprises
- 01
Understand
We talk through your business, your customers, and what “done” really means. I map the constraints before a line of code — no assumptions.
You get: a shared, written picture of the goal.
- 02
Prototype
Within a couple of weeks you're clicking a real prototype, not reading a document. You tell me what's off; we fix direction while it's still cheap.
You get: a clickable prototype and fast feedback.
- 03
Build
I build in small, reviewable steps on a solid stack. You see working software every week — no big reveal at the end.
You get: weekly progress you can follow.
- 04
Launch
We ship carefully: tested, fast, and easy to find. I handle the deploy and the last mile so launch day is boring — in the best way.
You get: a smooth, well-tested go-live.
- 05
Maintain
I stay on to keep it healthy — security, performance, and small improvements — so it keeps earning its place. The part most agencies skip.
You get: dependable, long-term care.
What you can count on
Something to click
You're never staring at a spec, guessing. There's always a real thing to react to.
One person, end to end
Whoever scopes it, writes it and maintains it. Nothing gets lost in a handover.
Weekly progress
You see working software every week, so surprises get caught early — not at the deadline.
Still here after launch
Launch is the middle, not the end. I stick around to keep things healthy.
Have a project in mind?
Tell me what you're building — I reply within a day.