Skip to content
The Handbook
CHAPTER 1

Start here

What PlanMySaaS is, the five stages, and the words you need before anything else

8 min · 5 sections

PlanMySaaS takes one sentence about a product and turns it into two things: an honest answer about whether the idea is worth building, and a blueprint detailed enough for a developer — or an AI coding tool — to build from. This chapter is the map. Read it once and the rest of the product stops looking like forty unrelated screens.

The five stages

The whole product in one table — what each stage is for and what it hands to the next one.

Everything in PlanMySaaS happens in five stages, always in the same order. Each stage produces something the next stage needs. If you know which stage you are in, every screen in the product has an obvious place.

You do not have to finish a stage before looking at the next one. But a later stage built on a skipped earlier one is a guess wearing a suit — the research it needed simply is not there.

StageWhat happensWhat you getWhere it lives
1. IdeaYou describe the product in your own words and answer a few follow-up questions.A saved idea with your intake answersIdeas → New idea
2. ValidationThe system researches the idea across up to 29 sections and gives a verdict.A validation report with a score and a recommendationIdeas → your idea
3. BlueprintThe validated idea becomes a project: architecture, features, technical design, frontend, phases.A developer-ready planProjects → your project
4. OutputThe plan is turned into things you can hand over: build prompts, documents, exports.Prompt pack, PRD, exportsProject → Output group
5. EvolutionThe plan changes as you learn: new versions, upgrades, backlog, change requests.A history you can compare and roll backProject → Evolution group
Validation and blueprint are separate on purpose
Validation asks whether you should build this. The blueprint describes how to build it. Keeping them apart means the research can tell you an uncomfortable answer without the plan quietly assuming you will build anyway.

Signing up and your first 100 credits

What the free credits cover, and what they do not.

The PlanMySaaS sign-up screen
Sign-up needs an email and a password, or a Google account. No card is asked for.

A new account starts with 100 free credits. Credits are the single unit of spend in PlanMySaaS — every piece of AI work uses them in proportion to the work it takes, and you see the typical cost before it starts, and nothing runs without your click.

100 credits let you try it on one real idea — enough to judge whether the depth is worth paying for, and not enough to complete a full blueprint.

What it is
A workspace with 100 credits and no card on file.
Why it matters
Credits, not seats, are what you spend. Knowing the cost of each action is how you avoid surprises later.
Can you edit it
Your account details are yours to edit at any time in Settings.
What it costs
Free. The first 100 credits need no payment method.
Next step
Create your first idea — Ideas → New idea.

What things cost

The credit price of every generation, and what a complete blueprint adds up to.

Nothing charges silently. Every generation states its price before it runs, and the amount is taken when the work completes.

Credit cost per generation

GenerationCreditsWhat you get
Idea research60Up to 20 named competitors, each scored and positioned, plus market sizing, personas and risk flags
Strategic analysis30Product-market-fit scoring on that research, and the gaps worth building into
System architecture20Service diagram, data flow, tech-stack picks with reasoning, hosting cost estimate
Feature specifications25User stories, acceptance criteria, API signatures, edge cases
Technical design30Data models with real fields and relations, service responsibilities, API endpoints
Frontend blueprint40Routes, pages, layout system, design tokens, state management
Prompt Pack3026 copy-paste build prompts written against your own blueprint
Documents8–18Each. PRD and onboarding are short; API reference and business plan are long

Taking one idea through the whole pipeline comes to roughly ~1,009 credits before documents, and about ~1,205 with the core document pack. Most spend after the first draft goes on regenerating sections as your thinking changes, so plan for fewer products and more iterations on each.

The billing screen showing the current plan, available plans and recent credit activity
Billing shows your balance, your plan, and a line for every credit you have spent.
  1. 1Your remaining balance is always in the top bar as well, so you never have to open this page to check.
  2. 2Recent credit activity lists what each spend was for, which is the fastest way to see where a month went.
  3. 3Unused credits do not carry into the next cycle.

The workspace: dashboard, ideas, projects

Three top-level places, and what belongs in each.

The left navigation has three places that matter for the work itself. Everything else is settings, billing and support.

The PlanMySaaS dashboard
The dashboard answers one question: what should I do next.
  1. 1Suggested next steps is the shortest path back into unfinished work.
  2. 2Pipeline progress shows how far each project has moved through the five stages.
  3. 3Credit spend for the last 30 days sits next to workspace health, so cost and progress are read together.
PlaceWhat lives hereWhen you use it
IdeasEvery idea you have described, validated or not.Before you commit to building. This is where validation happens.
ProjectsEvery idea you promoted into a build plan.After validation, when you are planning the actual product.
DashboardA summary of both, plus what to do next.Every time you come back and cannot remember where you stopped.
An idea and a project are not the same object
An idea holds research and a verdict. A project holds a build plan. Promoting an idea creates a project and links the two — the idea stays exactly as it was, so you can always see what you believed at the time you decided to build.

The words used everywhere

Ten terms that appear on almost every screen.

These are the words the product uses constantly. Learning them here saves guessing later.

Idea
Your product described in your own words, plus the answers you gave to the follow-up questions. The starting object for everything.
Validation
Research that judges whether the idea is worth building. Runs as up to 29 separate sections and ends in a verdict.
Section
One piece of the validation report — for example Problem Validation or Unit Economics. Each is generated, scored and saved on its own.
Verdict
The headline recommendation on a finished report: Build, Reconsider, or Do not build, with a score out of 100.
Promote
Turning a validated idea into a project. This is the moment the product switches from judging to planning.
Project
The build plan for one product: architecture, features, technical design, frontend blueprint, phases and everything downstream.
Artifact
Any single generated document inside a project — the architecture, the feature specs, a phase plan. The Artifact Hub lists them all.
Prompt Pack
Copy-paste prompts written against your own blueprint, for use in an AI coding tool.
Credits
The unit of spend. Every generation has a stated credit price and nothing runs without your click.
Version
A saved snapshot of a generated artifact. Regenerating never destroys the previous one — you can compare and roll back.