01
There is a design and no answer
A Figma, maybe a deck. What there is not is one person outside the building who has used the thing and said whether they want it.
Prototype in five days
1,800 EUR, fixed
One flow of your product, built, deployed on a domain and handed over. You use it, you send the link to other people, and then you decide whether the real thing is worth building.
Five working days, 1,800 EUR, half on start
You usually get here after one of these
0301
A Figma, maybe a deck. What there is not is one person outside the building who has used the thing and said whether they want it.
02
Both numbers may well be right. Neither of them can be justified before you know whether anyone wants it.
03
An investor, a partner, your first ten customers. A recording of a prototype is not the same thing as a link they can open on their own phone.
What arrives on Friday
01
Not a set of screens that look right and do nothing. One path through the product, with real data that gets saved and comes back.
02
You send a link. People use it on their own phone, without you on a call explaining what they are looking at.
03
I came into this through design. A prototype that looks provisional gets judged as provisional, and that is the wrong thing to find out from the people you are testing on.
04
What holds, what would have to be rewritten, and roughly what the real version costs. One page, at the end, whether or not you continue with me.
How five days is possible
This page ships 5 KB of JavaScript
Five days is not a sales number, it is what the work takes now. I decide what gets built, in what order, and what it looks like. The implementation is written with AI. I test it, and I am the one who answers for it.
That is the whole reason the price is 1,800 and not twelve thousand, and the reason one person can hand you a working product in a week. Writing the code stopped being the expensive part. Knowing what to build, in what order, and what breaks later is still the expensive part, and that is the part you are paying for.
This site was built the same way: fourteen pages in two languages, five kilobytes of JavaScript, and a script that checks every page for unreadable text and sideways overflow before anything goes out. You are reading the method, not a description of it.
Before you order it
Not productionIf what you need is the real thing, with real payments and real users, that is a project with phases and a different price. Say so in the first message and we skip this page.
The week
The week
01
Morning of day one
Half a day, on a call and then in writing, cutting the idea down to what fits in the days that are left. You decide what stays in. I tell you what will not fit.
02
Days one to four
It gets built. At the end of each day there is a link that works, so you are never waiting until Friday to find out what you are getting.
03
Day five
You use it and tell me what is wrong. I change what fits in the day. Then it is handed over: domain, accounts and code in your name.
Answered the same working day, in writing. If it does not fit, I say what does.