/compose-saas-mvp - Rapid SaaS MVP Workflow Composition

Purpose

The /compose-saas-mvp prompt orchestrates a complete SaaS MVP setup using dynamic workflow composition. Unlike /generate-implementation-tutorial which creates comprehensive reference guides, this prompt focuses on rapid implementation with intelligent sequencing based on your specific needs.

How It Actually Works

1. Discovery Phase: Analyzes your SaaS vision and requirements
2. Dynamic Workflow: Composes custom sequence based on dependencies
3. Intelligent Sequencing: Adapts order based on B2B vs B2C needs
4. Rapid Implementation: Executes with focus on speed and functionality
5. Time-Boxed: Completes MVP in hours/days, not weeks

Key Differences

Aspect	/compose-saas-mvp	/generate-implementation-tutorial
Focus	Rapid implementation	Comprehensive planning
Output	Working MVP code	Reference-based guide
Timeline	Hours to days	Weeks to months plan
Approach	Build first, refine later	Plan thoroughly, then build
Best For	Validation & demos	Production systems

Use Cases

1. Startup MVPs: Launch quickly to validate ideas
2. Proof of Concepts: Demonstrate feasibility to stakeholders
3. Hackathon Projects: Build complete solutions rapidly
4. Client Demos: Create working prototypes for proposals
5. Feature Validation: Test new SaaS features quickly

Argument Structure

/compose-saas-mvp <product-description> [target-audience] [--options]

Arguments

1. product-description (required)

   • Clear description of the SaaS product
   • Core value proposition
   • Key features to include

2. target-audience (optional)

   • B2B, B2C, or specific segment
   • Helps tailor UX and features
   • Influences pricing model

3. options (optional)

   • --timeline: Target completion (hours, days)
   • --features: Comma-separated priority features
   • --integrations: Required third-party services

Examples

# Basic SaaS MVP
/compose-saas-mvp "Project management tool for remote teams"

# With audience specification
/compose-saas-mvp "AI writing assistant" "content creators and marketers"

# With specific features
/compose-saas-mvp "Customer support platform" --features="ticketing,live-chat,kb"

# Rapid prototype
/compose-saas-mvp "Invoice generator" --timeline="8-hours"

Adaptation Strategies

Intelligent Composition

The prompt automatically:

1. Selects Core Features

   • Authentication & authorization
   • User management
   • Billing & subscriptions
   • Admin dashboard
   • Basic analytics

2. Adds Domain Features

   • Analyzes product description
   • Identifies essential functionality
   • Prioritizes MVP features
   • Defers nice-to-haves

3. Configures Infrastructure

   • Database schema
   • API structure
   • Authentication flow
   • Payment integration
   • Email system

Template Optimization

Based on requirements:

• Chooses optimal template
• Customizes for use case
• Removes unnecessary features
• Adds missing components
• Configures for quick launch

Time-Based Adaptation

Adjusts scope based on timeline:

• 4 hours: Core features only
• 1 day: Core + essential domain
• 3 days: Full MVP with polish
• 1 week: MVP + growth features

Memory Usage

Generated Structure

saas-mvp/
├── CLAUDE.md                    # Product vision & decisions
├── .orchestre/
│   ├── mvp/
│   │   ├── features.md         # Implemented features
│   │   ├── deferred.md         # Future features
│   │   └── architecture.md     # Technical decisions
│   └── launch/
│       ├── checklist.md        # Launch requirements
│       └── metrics.md          # Success metrics
└── docs/
    ├── SETUP.md                # Quick start guide
    └── FEATURES.md             # Feature documentation

MVP Documentation

# SaaS MVP: TeamSync Project Manager

## Product Vision
Remote team project management with focus on async collaboration

## Implemented Features
1. **Authentication**
   - Email/password login
   - Google OAuth
   - Team invitations

2. **Core Functionality**
   - Project creation & management
   - Task assignment & tracking
   - Async comment threads
   - File attachments

3. **Team Features**
   - Role-based permissions
   - Team workspaces
   - Activity feed

4. **Billing**
   - Stripe integration
   - Free/Pro/Team tiers
   - Usage-based limits

## Technical Stack
- Frontend: Next.js + Tailwind
- Backend: Next.js API routes
- Database: PostgreSQL + Prisma
- Auth: NextAuth.js
- Payments: Stripe
- Hosting: Vercel

## Launch Checklist
- [x] Core features working
- [x] Payment flow tested
- [x] Email system configured
- [ ] Terms of service
- [ ] Privacy policy
- [ ] Production environment

Workflow Examples

Startup MVP Sprint

# 1. Generate MVP
/compose-saas-mvp "Freelancer time tracking with invoice generation" "freelancers"

# 2. Add critical feature
/execute-task "Add Stripe Connect for freelancer payouts"

# 3. Prepare for launch
/execute-task "Set up production environment with monitoring"

# 4. Create landing page
/execute-task "Build conversion-optimized landing page"

Hackathon Project

# 1. Rapid prototype (4 hours)
/compose-saas-mvp "AI code reviewer for pull requests" --timeline="4-hours"

# 2. Add differentiator
/execute-task "Integrate GPT-4 for intelligent code suggestions"

# 3. Create demo
/execute-task "Build demo workflow with sample data"

Client Demonstration

# 1. Create targeted MVP
/compose-saas-mvp "Inventory management for small retailers" "retail-stores"

# 2. Customize for client
/execute-task "Add barcode scanning and POS integration"

# 3. Brand for client
/execute-task "Apply client branding and create demo accounts"

Intelligent Features

Feature Prioritization

Automatically determines:

• Must-have features
• Should-have features
• Nice-to-have features
• Future roadmap items

Smart Defaults

Provides sensible defaults for:

• Pricing tiers
• User limits
• Feature flags
• Email templates
• Error messages

Growth Preparation

Even in MVP, includes:

• Analytics hooks
• A/B testing setup
• Referral system stubs
• Upgrade prompts
• Onboarding flow

Security Basics

Implements from start:

• Secure authentication
• Data validation
• CSRF protection
• Rate limiting
• Basic monitoring

Generated Components

1. Authentication System

• Sign up/Login flows
• Password reset
• Email verification
• Session management
• Team invitations

2. User Dashboard

• Overview metrics
• Recent activity
• Quick actions
• Settings access
• Billing status

3. Admin Panel

• User management
• Subscription oversight
• System metrics
• Feature flags
• Support tools

4. Billing Integration

• Subscription plans
• Payment processing
• Invoice generation
• Usage tracking
• Upgrade flows

5. API Structure

• RESTful endpoints
• Authentication middleware
• Rate limiting
• Error handling
• Documentation

MVP Variations

B2B SaaS

/compose-saas-mvp "Contract management platform" "enterprise-legal-teams"

Includes:

• Team workspaces
• Role permissions
• Audit logs
• SSO preparation
• Enterprise pricing

B2C SaaS

/compose-saas-mvp "Personal finance tracker" "individual-users"

Includes:

• Simple onboarding
• Social login
• Mobile-responsive
• Freemium model
• Viral features

Marketplace SaaS

/compose-saas-mvp "Freelance marketplace" "freelancers-and-clients"

Includes:

• Multi-sided platform
• Payment splitting
• Review system
• Search & matching
• Communication tools

Integration Points

With Other Prompts

• ← /orchestrate: Use plan for MVP
• → /execute-task: Add specific features
• → /add-enterprise-feature: Scale up
• → /security-audit: Pre-launch check

With External Services

Pre-configured for:

• Stripe payments
• SendGrid emails
• Vercel hosting
• PostgreSQL database
• Redis caching

Best Practices

1. Clear Value Proposition

   # Good: Specific problem and solution
   /compose-saas-mvp "Automated social media scheduling with AI content suggestions"
   
   # Vague: Too broad
   /compose-saas-mvp "Marketing tool"

2. Realistic Scope

   # Good: Focused MVP
   /compose-saas-mvp "Team standup tool with async video updates" --timeline="3-days"
   
   # Unrealistic: Too much
   /compose-saas-mvp "Complete ERP system" --timeline="1-day"

3. Iterate Quickly

   # Generate base
   /compose-saas-mvp "Customer feedback tool"
   
   # Add differentiator
   /execute-task "Add sentiment analysis to feedback"
   
   # Polish for launch
   /execute-task "Optimize onboarding flow"

Launch Preparation

Pre-Launch Checklist

The prompt generates:

• [ ] Production environment setup
• [ ] Domain configuration
• [ ] SSL certificates
• [ ] Email delivery testing
• [ ] Payment flow validation
• [ ] Error monitoring
• [ ] Analytics setup
• [ ] Backup configuration

Documentation

Automatically creates:

• Setup instructions
• Feature documentation
• API reference
• Deployment guide
• Environment variables

Marketing Assets

Suggests creating:

• Landing page copy
• Feature descriptions
• Pricing table
• FAQ content
• Email templates

Tips

1. Start Specific: Clear descriptions yield better MVPs
2. Time-box Properly: Be realistic about timelines
3. Focus on Core: Don't over-engineer the MVP
4. Plan for Growth: Architecture should support scaling
5. Launch Fast: Perfect is the enemy of good