Work with me
If you can describe what keeps being done by hand, that is enough to start.
You do not need a specification, a wireframe, or a view on how it should be built. Those are my job. What I need from you is the part only you know: what the work actually is, and what it costs you today.
What I take on
01
A product, end to end
From the first conversation to the thing running in front of real users — web, mobile, or both.
02
AI where it earns its place
Phone calls that hold a real conversation, documents read without a person reading them, answers in your own language.
03
Work that runs itself
Collecting, checking and reporting on a schedule — the weekly job nobody enjoys and everybody forgets.
04
Finishing what was started
A prototype that half works, or a build somebody left behind. Often the fastest way to something usable.
How it goes
- 01You describe the workOne call. What happens today, who does it, and how long it takes. If there is a spreadsheet involved, bring it.
- 02I tell you what it costsA price and a timeline, in writing, before anything is built. If I think it is not worth building, I say that instead.
- 03You see it earlyThe first working version comes before it is finished, not after. Changing direction is cheap then and expensive later.
- 04It is yoursThe code, the accounts and the keys are handed over. Nothing stays locked to me, and you can hire anyone to continue.
What I do not do
- Take on more than two builds at a time. The second one would be worse than the first.
- Bill by the hour. You should know the price before the work starts, not after.
- Rebuild something that already works, because a rewrite feels tidier.
- Add AI to something that does not need it. Most work is a script, not a model.
- Design by committee. One person decides on your side, or the work stalls.
Start here
Two lines about the work is enough.
What happens today, and roughly how often. I will tell you whether it is worth building before either of us spends anything.
[email protected]