The planning tools help you plan a build before you spend time or money on it. They are free on every plan: they run in your browser and use no credits and no AI. You find them under "Planning tools" on the Build tools page.
The five tools
- "MVP estimator": hours and weeks to a first version (MVP means the smallest first version you can launch). List the features, rate the effort of each from 1 (a few hours) to 5 (about two weeks of work), and set the "Hours a week you can give it". It estimates effort in hours, not cost.
- "Stack picker": stacks that fit your platform, how you build, your budget and what the product must handle. The starting answers come from your founder profile and the project, and you can change any of them.
- "Prioritisation": rate each feature for impact, confidence and effort from 1 to 5. The tool ranks them into "Must have", "Should have", "Could have" and "Not now".
- "Readiness score": how ready you are to launch, from proof of the problem, demand, room to win, the build and the launch prep. There is no score without proof of the problem, or with too little data.
- "Launch checklist": what to do before and after launch, with extra items for your track (the kind of product you build).
The MVP estimator, the stack picker, prioritisation and the readiness score each show their rule on the page, under "How this is worked out".
Use a tool on a project
Once you have a project, each tool shows a "Project" picker. Pick a project and the tool reads it. Choose "No project (nothing is saved)" to try things out without saving.
- Open a planning tool from Build tools. The "Estimate the build" and "Pick a stack" steps of a project's journey also open their tool on that project.
- Check the project under "Project".
- Make your changes. In the MVP estimator, "Fill from the project's tasks" brings in the tasks that have an effort rating.
- Save what you chose: "Save to project" in the MVP estimator, "Use this stack" in the stack picker. In prioritisation and the launch checklist, each rating and tick is saved to the project as you go.
Saving to a project needs a paid plan, because projects are part of the paid plans. A paused or archived project is read-only, so nothing can be saved to it.
How they feed the journey
A saved estimate, a picked stack and the launch checklist each count toward a step of the project's journey: "Estimate the build", "Pick a stack" and "Work through the launch checklist". The MVP estimator keeps the effort ratings and your choices in the project, not the feature names.
The readiness score is separate from the journey progress. On a project, it reads the evidence, demand and competition of the linked niche (and the verdict of a linked evaluated idea), and the project's tasks and checklist. You can click "Try other numbers" to enter your own. Those numbers stay on the page and are not saved.