Creating your first project
How to use the project creation wizard and Product Idea page to give Nova the right context for a professional-grade blueprint.
What is a project?
A project in PlanMySaaS represents a single product idea. Inside each project, Nova AI generates:
- Product analysis and market research
- System architecture and data model
- Feature specifications for every module
- Technical design (API, database, services)
- Development phases and milestones
- AI coding prompts ready for Cursor, Copilot, or ChatGPT
The quality of all this output depends heavily on the quality of your initial input. A vague 2-line idea produces generic output. A detailed, structured input produces a professional-grade blueprint.
The 5-step creation wizard
When you click "New Project", you're guided through a 5-step wizard. It's designed to be fast (under 5 minutes) but captures the signals that matter most.
Step 1: Basics
Step 2: Audience & Business
Step 3: Core Features
Step 4: Planning Guidance
Step 5: Review & Generate
The Product Idea page — refine after creation
After creating your project, the Product Idea page lets you add more detail. It has three layers:
- Layer 1 — Essential: Project name, one-line summary, problem, audience, business model, features, and founder instructions. These are always visible.
- Layer 2 — Optional: Product goal, main user action, geographic market, constraints, and design direction. Expand when you want better planning output.
- Layer 3 — Advanced: User roles, integrations, competitors, existing assets, success criteria, and anti-goals. For power users who want maximum control.
You don't need to fill everything — the essential fields are enough for a strong blueprint. Optional and advanced fields improve quality but never block progress.
Founder Instructions — your most powerful tool
The Founder Instructions field is the single most impactful way to improve your output. It tells Nova what you care about, what to prioritize, and what to avoid.
Good founder instructions include:
- Scope control: 'Keep version 1 simple', 'No enterprise features yet'
- Market focus: 'India-first', 'Global from day 1'
- Tech direction: 'Use Laravel only', 'Mobile-first', 'No native apps in v1'
- Revenue focus: 'Prioritize revenue-generating features', 'Freemium model'
- What to avoid: 'Don't build a full LMS', 'No AI features in phase 1'
Weak vs. strong input — examples
The difference between generic and professional-grade output often comes down to input quality:
One-Line Summary
Problem Statement
Core Features
Founder Instructions
Best practices
- Start with the wizard — fill at least the 5 essential fields to get a solid blueprint.
- Come back to the Product Idea page later to add optional fields and refine your inputs.
- Write your problem statement as if explaining to a smart developer who's never heard of your product.
- Use founder instructions to prevent generic output — be specific about what you want and what you don't.
- If you're building for a regulated industry (healthcare, finance), mention it in constraints.
- Name real competitors — even partial ones. Nova uses them to find gaps your product can fill.
- Don't try to fill every field at once. The essential layer is enough to start generating.