Tell me aboutyour idea.
Eleven questions, one at a time. They are the ones I would ask you out loud, so writing them down first means the call — if we get that far — starts at the interesting part instead of at the beginning. And everything worth checking before you do is on this page: what you own, the terms, the price, and the questions people ask.
No scoring, no auto-reply, no chatbot in between.
What happens after you send it
- You answer the questions. One at a time, nothing else on the screen, and it saves as you go — close it and come back. Ten minutes if you take your time, two if you don’t. Only the idea and your email are needed; skip anything you would rather say out loud.
- I read them and reply within one working day. Either with a couple of times for a call, or, if what you wrote already tells me this is not a fit, with that and a better direction. I read every one myself.
- The call, if there is a fit. Free, 20 to 30 minutes, on video. We talk through what you wrote rather than starting from nothing. No pitch, no pressure, no follow-up sequence.
The answers are yours to keep either way, and they are worth more to you than to me: they are the same questions the two weeks would start with.
What you own at the end
Yours to keep, extend, or hand to any team. No license, no lock-in, no dependency on me continuing to exist. If you take it to another developer tomorrow, everything they need is in the repository.
Short enough to read in one sitting and written so a co-founder or an investor can read it too. It states the question and the bar first, then how to tell a go from an adjust from a stop. Once the sessions are done the call goes at the top, with the evidence behind it. If the two ever disagree, trust the evidence.
Where to find people with the problem rather than people who like you, how many you actually need (fewer than you would expect), and how to keep politeness from quietly ruining your results. Reusable on every idea you have after this one.
That last one matters more than it looks. It's the part that keeps working long after the two weeks end.
You should never be stuck with me.
Plenty of people in this business are quietly hoping you'll stay. This works the other way round. When the two weeks end, you can read your own evidence, make your own call, and move forward or walk away without another opinion. You keep the build, the brief, and the method.
People do come back. Usually with the next idea, or the same one pointed somewhere new. That's a choice, not a dependency, and it's the only kind worth having.
How pricing works
Step one
Is this worth building?
€450 fixed
The first days of the two weeks: we go through what you wrote, find the riskiest assumption, and shape what — if anything — deserves to be built. Priced so that "don't build" is a cheap answer to get.
Step two
The build
€2,500–4,000 scoped in step one
The rest of the two weeks: the flow built, the bar set, the brief and the playbook in your hands. Agreed in writing before anything is built, so the number is yours to say no to.
Optional
The testing, run for you
€900 flat
Finding the right people and getting them in front of it takes real calendar time, which is why it sits outside the two weeks. Run it yourself with the playbook, or have it added on.
No retainer, no hourly meter, no invoice you didn't see coming. Every number is agreed in writing before the work it pays for begins.
Why you can trust the answer
You get judgment, not just a build.
Anyone can generate an app now. The hard part is knowing what to make and what to cut, and that's the part you're paying for.
You get advice from someone who isn't paid to say yes.
When the honest answer is "don't build this," you'll hear it. That's only possible because the value here is the clarity, not the code.
You get speed without losing the thinking.
The idea gets real in days, with a designer's read on how people actually behave built in.
The judgment comes from 20 years of deciding what to build and what to cut. The speed comes from nine working apps built in the last few months. If you want that story, it's on the about page.
Questions people ask
What if you tell me my idea is bad?
Then you've saved months and a fortune, and you'll get a clear reason why, not a vague no.
Do I need to understand the tech?
No. You need to understand your customer. The rest is handled.
Who owns what gets built?
You do. It's yours to take anywhere.
Is this a full product?
No, and that's the point. It's the smallest real thing that answers the biggest question. Building the full product before that answer is exactly the expensive mistake this avoids.
How long until I actually have an answer?
The build and the bar take two weeks. The answer takes as long as it takes to get the right people in front of it, usually a week or two more, and that part nobody can promise. Which is exactly why the sessions sit outside the fixed scope: putting them inside would mean either padding the timeline or rushing the recruiting, and rushed recruiting is how you end up testing on whoever was available instead of whoever has the problem.
What if I already know it's a good idea?
Then step one is quick and you'll have saved nothing but a little time. Most people who are certain turn out to be certain about the wrong part.
Read it all? Then you know what I'd ask.
Ten minutes of questions, in your own words, and a reply within one working day. Or write to [email protected] if you would rather just say hello — same reader, same reply.
Tell me about your ideaHere it is. It’s yours either way.
Nothing has been sent yet — this site has no server to send it to, and a form that says “sent” when it means “discarded” is worse than no form. Copy it or open it in your mail app, and it reaches me the moment you hit send. Keep a copy either way: the answers are more use to you than they are to me.