How do I get working software built without a development team?
I build it myself, with AI as my team, in two-week phases at a price agreed before we start. Two routes: a Product Build takes an idea to a live product in 6 weeks from €18,000, and an Automation Build adds an agent system to an operation that already runs, in 4 weeks from €12,000.
from €12,000
Duration: 4 to 6 weeks
Who is a Build for?
Founders with no development team who need software people can actually use, not another clickable prototype. And companies where something already runs, but a person is doing by hand what a system should be doing.
It is not for you if you are still deciding what to build. A Product Clarity Day settles that: €1,500, one day. It is not for you either if a product of yours is already live and you do not know why the numbers are weak. A Product Audit is the first step there: €4,500, 2 weeks. And if what you want is ongoing help rather than a finished thing, that is Product Partner. I take one Build at a time, and every Build has an end date.
What do you get at the end?
A deployed product that people can use, plus everything you need to keep it running without me.
- Product Build · 6 weeks · from €18,000: an idea taken to a live, usable product
- Automation Build · 4 weeks · from €12,000: an agent system built onto an operation that already runs
- A deployed, working version at the end of every two-week phase, not a demo
- Documentation and a handover session, so the system runs without me
- The repository, the accounts, and the infrastructure in your name from day one
- Architecture and UX design included, with no separate designer to brief
How does a Build actually run?
In two-week phases, each one ending in a deployed, working version. At every phase boundary you decide whether to continue.
Before week 1: the scope
I write down what gets built and what does not. We pick the route, and then I fix the price. A Clarity Day or a Product Audit gives me that document already. Otherwise we start with a scoping call and I write the scope document from it.
Phase 1, weeks 1 and 2: the spine
The most important flow works from the first screen to the last, deployed. You get a link you can open, not screens to approve.
Phase 2, weeks 3 and 4: the product around it
The remaining flows, the data, and the integrations: everything that makes it usable by someone who is not you. An Automation Build finishes here, with its documentation and handover session.
Phase 3, weeks 5 and 6: hardening and handover
This phase exists in a Product Build only. Edge cases, speed, documentation, a walkthrough, and my own access removed from your accounts.
Every phase boundary: you decide
You can stop, continue, or change what comes next. Payment is tied to those boundaries, so what you have paid always tracks what exists.
Throughout: the rhythm
A written update every week, with a link to the current state. One call per phase, everything else async.
What is not included?
Anything that is not in the scope document we agree on before week 1. These are the ones that come up most often.
- Ongoing operation after handover. That is Product Partner: 2 days a month, €2,000 per month, minimum 3 months
- New features outside the agreed scope. They move to a later phase and get quoted before that phase starts
- Third-party licences, hosting, and API usage. Those run on your own accounts
- Brand identity, logo design, and marketing copy
- Moderated user testing. That is an add-on to a Product Audit: 5 participants, plus €2,000
Questions
The catch is scope. A 6-week Product Build makes one product do one job properly, and that job is agreed before week 1. The limit was never typing speed. It is deciding what deserves to exist.
You own all of it. The repository and the accounts are in your name from day one, not transferred at the end. The stack is mainstream: Next.js, Supabase, Swift. Any developer can pick it up from the handover documentation.
Four things, all priced before we start: how many user roles exist, how many outside systems it connects to, whether existing data has to be migrated, and whether payments or sensitive data are involved. Complexity gets quoted, not discovered.
What comes before and after a Build?
Before a Build, most clients run a Product Clarity Day at €1,500 or a Product Audit at €4,500. The full €1,500 of a Clarity Day comes off a Build booked within 30 days of the Clarity Day, and it can be credited once. After a Build, most founders keep me on as a Product Partner: 2 days a month, €2,000 per month, minimum 3 months, then monthly notice.
Let's Build Your Digital Future
Whether you need something built, a system automated, strategic product advice, or a perspective on staying grounded while building at speed: let's talk. I bring 11 years of thinking about what makes digital products work, for the people who use them and for the person building them.