Evaluate your startup idea before you build
By Idea OS · Product and founder education
Idea OS helps early-stage founders evaluate a startup idea and decide what to test before building. It organizes analysis around demand, customers, market size, competition, monetization, execution, and risk. The result is a starting point for decisions and experiments; it is not proof that a business will succeed.
Who is this for?
Use Idea OS when you have an initial idea, an unclear customer segment, or several assumptions to investigate before committing to an MVP. It is especially useful when you want a repeatable review structure and a place to develop your evaluation into planning documents.
If you only need a quick brainstorm, a general chatbot may be enough. If you need to establish demand, you still need customer conversations, observations, and real buying behavior.
What you provide
Describe the customer, the problem, the proposed solution, and how people solve the problem today. Include evidence you actually have: interview notes, experiment results, sources, and dates. State what is unknown. You can start with a short description and refine it through the clarification workflow.
What you receive
- A structured evaluation of the idea and its risks.
- Questions and suggested experiments to investigate assumptions.
- A workflow for refining the idea and developing planning artifacts such as a Lean Canvas, pitch outline, or PRD, subject to plan and credits.
See a worked evaluation and read the published methodology before deciding whether the structure suits your work.
From an idea to a decision
For a fictional scheduling service, “coaches hate scheduling” is an assumption. The useful next step is to observe a coach's current workflow and test whether they will pay for a change. A detailed report cannot substitute for that observation.
In the CoachSlot example, the decision is to investigate scheduling pain and offer a small paid pilot before building a broad coaching platform. The example is editorial and fictional, not a customer outcome or an actual product transcript.
Cost and access
Public examples and the planning tools are available without an account. Running and saving an evaluation requires a free account. New accounts receive 20 one-time Test Credits. Paid plans and credit requirements are explained on the pricing page; review them before starting paid work.
What Idea OS cannot establish for you
AI analysis can miss facts, misinterpret inputs, or suggest an unsuitable experiment. Check cited material and keep assumptions separate from observations. An internal score is not a calibrated probability of success. Neither a generated market estimate nor a polished pitch establishes willingness to pay.
Start with your riskiest assumption
Write down who must change their behavior, what they must do, and what would cause you to stop or revise the idea. Use the hypothesis worksheet, then evaluate your assumptions.
Common questions
Can I use Idea OS before I have customers?
Yes. Describe the idea and explicitly mark demand, pricing, and retention as unverified. Use the evaluation to plan evidence gathering.
Does a positive evaluation mean I should build?
No. Review the assumptions and run the smallest useful test first. A positive analysis is not customer validation.
How is this different from asking a chatbot?
Idea OS packages the review into a dedicated startup workflow. A chatbot offers a flexible conversation that you can structure yourself. Compare the workflows.