For idea-stage founders
You have the idea. You do not yet have the plan.
At idea stage the expensive mistake is not picking the wrong feature. It is spending six months and your first check building something nobody was waiting for. Almost every founder knows this and almost every founder does it anyway, because a feature list feels like progress and customer conversations feel like delay.
The work at this stage is narrow: get specific about who has the problem, find the assumption that would sink the whole thing if it were wrong, and test that one first. You do not need a roadmap yet. You need to know which question to answer next, and in what order, so that the money you spend buys you information instead of code you throw away.
Sound Familiar?
This is for you if
The Work
What changes.
The idea gets stated so it can be wrong
A vague idea cannot be tested. We turn it into a specific claim about a specific buyer with a specific problem, which is the only form an idea can be checked in.
The riskiest assumption gets named
Every early idea rests on one or two load-bearing beliefs. We find them and put them at the front of the queue, so you are not validating easy things while the hard thing stays unexamined.
Scope gets cut to the smallest honest test
Most first builds are three times bigger than the question they are trying to answer. We cut back to what actually produces a signal, which usually saves months and most of the budget.
Engagements
What usually fits at this stage
Lightest first. Starting small is a real option, not a lesser one.
1–2 Weeks, Fixed Scope
Product Teardown
A short, fixed-scope look at your idea or early product before you commit real money to building it.
Learn moreMonthly, A Few Hours
Product Advisor Retainer
A few hours a month of senior product input on a standing cadence, without a hire or a long contract.
Learn moreWhen this is the wrong page
If you are still deciding whether to start a company at all, this is early. Come back when you have a problem you cannot stop thinking about and one or two people who have it.
FAQ
Questions at this stage
Is it too early to bring in product help?
+
No, and this is usually the highest-leverage moment for it. Product decisions made at idea stage set the direction everything else follows, and they are the cheapest decisions to change. The engagements that fit here are deliberately small: a fixed-scope teardown or a few hours a month, not a long consulting contract.
I do not have a product yet. What is there to look at?
+
Plenty. The idea itself, who you believe the buyer is, the evidence you have so far, the scope you are considering, and any deck or prototype. The absence of a product is not a gap, it is the point: it is far cheaper to change the plan now than after it is built.
Can you help me decide whether to build this at all?
+
Yes, and sometimes the honest answer is no, or not in this form. A clear no in week two is worth considerably more than a soft maybe that costs you a year. That outcome is a legitimate result of the work, not a failure of it.
Do you take equity instead of fees at this stage?
+
Occasionally, for advisory arrangements where the fit is unusually strong and the involvement is ongoing. It is a conversation worth having on a call rather than a standing policy.
More on scoping, pricing, and how engagements run on the full FAQ.
Other Stages
Not quite where you are?
Get started
Start with a conversation.
Thirty minutes, no deck. You describe what is stuck and the call ends with a recommendation, including when that recommendation is to wait.