Build Product Context

Learn how to effectively structure and communicate your SaaS concept for better development planning and AI-assisted feature development.

💡 Getting started? Complete Installation first, then use this guide to plan what makes your application unique!

🎯 Why This Matters

The AI assistant becomes significantly more helpful when it understands:

Your specific use case and target market
Core features you want to build
Business model and pricing strategy
Technical requirements and constraints

📝 Structuring Your SaaS Concept

1. Business Overview

Start by describing your SaaS concept clearly:


Example Prompt:
"I'm building a project management SaaS for remote teams.
The core features include task management, team collaboration,
time tracking, and client reporting. My target market is
small to medium businesses with 5-50 employees."

2. Core Features Description

List your essential features in priority order:


Example Structure:
 
- Primary Features (MVP):
  - User authentication and workspace management
  - Task creation and assignment
  - Real-time team collaboration
- Secondary Features (Phase 2):
  - Time tracking integration
  - Client reporting dashboard
  - Mobile app support

3. User Personas

Describe your target users:


Example:
 
- Project Managers: Need overview and progress tracking
- Team Members: Need task management and collaboration
- Clients: Need progress visibility and reporting

🤖 Effective AI Communication

Prompt Templates

For Feature Development:


"Help me build a [feature name] for my [SaaS type].
This feature should allow [user type] to [specific action]
so they can [benefit/outcome]. Key requirements include:
- [requirement 1]
- [requirement 2]
- [requirement 3]"

For Business Logic:


"In my [industry] SaaS, I need to implement [business rule].
The logic should handle [scenario 1], [scenario 2], and
[scenario 3]. The expected user experience is [description]."

For Technical Architecture:


"My SaaS needs to handle [specific technical requirement].
Expected scale: [user count/data volume].
Integration needs: [external services].
Performance requirements: [specific metrics]."

🏗️ Using the Task-Driven Development Workflow

1. Create PRDs with AI

Use the AI to generate Product Requirement Documents:


Cursor Agent Command:
"Create a PRD for [your feature description]"

The AI will:

Ask clarifying questions about your feature
Generate a structured PRD
Save it to /product/wiki/prd-[feature-name].md

2. Generate Development Tasks

Convert PRDs into actionable tasks:


Cursor Agent Command:
"Generate tasks from the [feature-name] PRD"

3. Execute with AI Guidance

Implement features step-by-step:


Cursor Agent Command:
"Start implementing tasks from [task-file-name]"

📋 Information to Provide

Business Context

Industry/Market: E.g., “Healthcare SaaS for small clinics”
Business Model: Subscription tiers, freemium, usage-based
Target Market Size: Startup, SMB, Enterprise
Geographic Scope: Local, national, global

Technical Context

Expected Scale: User count, data volume, geographic distribution
Integration Needs: CRMs, payment processors, analytics tools
Compliance Requirements: GDPR, HIPAA, SOC2, etc.
Mobile Requirements: Web-only, responsive, native apps

Feature Priorities

Must-Have Features: Core functionality for MVP
Nice-to-Have Features: Future enhancements
Unique Differentiators: What sets you apart
User Workflows: How users interact with your system

💡 Example: Complete SaaS Description


SaaS Concept: "FleetFlow - Vehicle Fleet Management"
 
Business Overview:
 
- Target: Small-medium logistics companies (10-100 vehicles)
- Model: Tiered SaaS subscription ($29-199/month)
- Market: North American logistics and delivery companies
 
Core Features:
 
1. Vehicle tracking and route optimization
2. Driver management and scheduling
3. Maintenance tracking and alerts
4. Fuel cost monitoring and reporting
5. Customer delivery notifications
 
User Personas:
 
- Fleet Managers: Need oversight and optimization tools
- Drivers: Need route guidance and status updates
- Customers: Need delivery tracking and notifications
 
Technical Requirements:
 
- Real-time GPS integration
- Mobile app for drivers
- SMS/email notification system
- Integration with fuel card providers
- FMCSA compliance reporting
 
Scale Expectations:
 
- 500-1000 companies
- 10,000-50,000 vehicles tracked
- Real-time data processing
- 99.9% uptime requirement

🚀 Best Practices

Do’s

✅ Be specific about user needs and business logic
✅ Provide context about your industry and market
✅ Share user stories and real scenarios
✅ Mention technical constraints and requirements
✅ Iterate and refine your description based on AI questions

Don’ts

❌ Don’t be vague - “Build a project management tool” is too broad
❌ Don’t skip business context - Technical features need business rationale
❌ Don’t assume AI knows your industry - Explain domain-specific terms
❌ Don’t change requirements mid-conversation - Be consistent

Next Steps

After building your product context:

Setup Landing/Waitlist Page - Start building your audience with your clear value proposition
Setting up Payment - Configure subscription billing for when you launch
Customizing the App - Build your unique SaaS features

The better you communicate your vision, the more effectively the AI can help you build your unique SaaS application.

Next: Continue with Setup Landing/Waitlist Page →