Guide
Validate a startup idea by writing down who it is for, what they do today, and what would count as success in the first month. Cut anything that is not required to test that outcome. A one-page PRD and a build plan show whether the idea is specific enough to build, and whether the first version can be finished.
Describe the idea and get a PRD and build plan. No card required for the first one.
Generate your first PRD freeA testable idea names a person, the workaround they use now, and a result you could observe. If every outcome still counts as success, you are not validating anything.
Write the smallest product that would change that person’s behavior. That version is the scope of the PRD, not the whole company.
When the PRD is full of “and also,” the idea is not ready. Remove steps that do not help the user finish the one job. What remains is either small enough to build or still too fuzzy to start.
The build plan should say what happens first and how long that slice takes. If the first slice is already a quarter of work, the test is too big.
Validation here is a decision: build this slice, change the user, or stop. The document is how you make that decision before payroll and code make it expensive.
Generate the draft in FounderBrief, delete what you cannot defend, and only then open an editor or a contract.
Write the user, the current workaround, and the first outcome you would accept. Show that page to people who have the problem. If you cannot describe the first version, you are not ready to build it.
You cannot name who it is for, every feature feels required, or the first milestone is longer than you can finish. Tighten the outcome or stop.
The PRD is the test plan. It forces the user, the scope, the non-goals, and the sequence into one place so you can see whether the idea is specific.