Services
Six things I do well. Everything below has shipped to real users on a real deadline — the capability list is short on purpose.
01
A complete web application, front to back. I own the data model, the API, the interface and the way they fit together, so there is one person accountable when something does not line up.
02
One Flutter codebase producing an iOS and an Android app that share their logic with your web product. I take it all the way through review and into the stores.
03
The interesting part of an AI feature is not the prompt. It is what happens when the model is wrong — and whether your users can tell. I build the parts that make it safe to ship.
04
For teams sitting on a large codebase nobody fully understands. I build the tools that make its shape visible, and the gates that stop it getting worse.
05
An interface is a promise about how much you care. I build the visual system underneath it, so quality survives the tenth screen and the third developer.
06
Software that is not deployed is not finished. I set up the path from a commit to production and stay reachable once real people depend on it.
Engagements
Every project is quoted against a written scope, so you know the number before any work begins. No hourly meter running in the background.
Option A
One to two weeks, fixed price. For when the idea is clear but the shape is not.
You keep everything, including the plan — even if you build it elsewhere.
Option B
Typically six to sixteen weeks. The main way I work: a defined product, built and launched.
Scope changes are re-quoted openly, never absorbed silently into the timeline.
Option C
A monthly retainer. For products already live that need a steady hand rather than a rebuild.
Month to month. If it stops being worth it, you stop.
A good fit
Not a good fit
Questions
It depends entirely on scope, so I quote per project rather than publishing a rate card. After a short call you get a written scope with a fixed number attached. Small, well-defined pieces of work are quoted as a single figure; larger builds are split into milestones you approve and pay as they complete.
A discovery sprint runs one to two weeks. A first usable version of a focused product is usually six to ten weeks; larger platforms with mobile apps and multiple user types run longer. You will have a staging URL to click within the first week either way.
Yes, and often that is the better arrangement. I join your repository, your board and your review process, and work the way your team already works rather than importing my own.
You do — fully, from the first commit. It lives in your repository under your accounts, and the handover includes documentation written for whoever maintains it next. No proprietary framework you can only run through me.
Every build includes a warranty window for anything that turns out to be broken. Beyond that, you can take it in-house with documentation, or keep me on a monthly retainer for features, releases and incidents.
Yes to NDAs, before any detail is discussed. I have built healthcare products where confidentiality and careful data handling were requirements rather than preferences, and I am happy to work inside your compliance constraints and review process.
I work with clients across time zones and keep a reliable overlap window for calls, with written updates covering the rest. Deadlines and response windows are agreed in writing before we start.
Next step
A half-hour call, then a written scope with a real number in it. No obligation attached to either.