#saas-template.md
Version: 1.0.0
Target Models
- DeepSeek V4
- DeepSeek V3.2
- DeepSeek R1
- DeepSeek V3 Family
- Future DeepSeek Models
#Purpose
This template provides a complete engineering context for designing, reviewing, improving, and evolving Software-as-a-Service (SaaS) products.
It is intended to organize product thinking, business objectives, technical architecture, user experience, scalability planning, operational requirements, security expectations, and long-term product evolution into one structured engineering specification.
The objective is not to generate random features.
The objective is to enable consistent, business-driven engineering decisions throughout the product lifecycle.
#Core Philosophy
Understand the Business
↓
Understand the Users
↓
Define the Product
↓
Design User Experience
↓
Design System Architecture
↓
Validate Business Value
↓
Prepare for Scale
↓
Continuously Improve
Every engineering decision should increase customer value while reducing unnecessary complexity.
#Product Overview
Clearly describe
Product Name
Business Problem
Target Audience
Business Goals
Primary Value Proposition
Competitive Advantages
Expected Business Outcomes
Long-Term Vision
The overview should explain why the product deserves to exist.
#Business Context
Define
Target Customers
Customer Segments
Business Model
Revenue Model
Market Position
Competitive Landscape
Pricing Strategy
Growth Strategy
Every technical decision should support measurable business objectives.
#User Personas
Describe
Primary Users
Secondary Users
Administrators
Business Owners
Internal Teams
Power Users
Enterprise Customers
Support Teams
Every feature should solve a real user problem.
#Core Features
Identify
Authentication
User Management
Organization Management
Billing
Subscription Management
Notifications
Search
Analytics
Dashboard
Settings
Administration
Audit Logs
Reporting
Integrations
Every feature should provide measurable business value.
#User Journey
Describe
User Registration
↓
Onboarding
↓
Activation
↓
Daily Usage
↓
Collaboration
↓
Retention
↓
Expansion
↓
Long-Term Success
The entire user experience should feel predictable, intuitive, and frictionless.
#Dashboard Structure
Define
Navigation
Primary Views
Secondary Views
Widgets
Analytics
Tables
Forms
Filters
Search
Settings
Responsive Behavior
Accessibility
Information hierarchy should prioritize user productivity.
#Data Model
Define
Core Entities
Relationships
Ownership
Permissions
Lifecycle
Validation Rules
Business Constraints
Retention Policies
Business data should remain consistent throughout the product.
#API Requirements
Define
Resources
Endpoints
Authentication
Authorization
Validation
Rate Limiting
Pagination
Filtering
Sorting
Versioning
Error Handling
The API should remain predictable, stable, and maintainable.
#Security Requirements
Define
Authentication
Authorization
RBAC
Encryption
Audit Logging
Session Management
Secrets Management
Compliance Requirements
Security should protect business operations without reducing usability.
#Performance Requirements
Define
Expected Users
Concurrent Users
Latency Targets
Availability Targets
Scalability Goals
Caching Strategy
CDN Strategy
Database Performance
Background Jobs
Performance should support business growth.
#Scalability Strategy
Describe
Horizontal Scaling
Vertical Scaling
Caching
Load Balancing
Database Scaling
Storage Scaling
Queue Systems
Disaster Recovery
Scalability should preserve simplicity whenever possible.
#Observability
Define
Logging
Metrics
Tracing
Alerting
Dashboards
Incident Detection
Operational Visibility
Monitoring should explain system behavior before failures affect customers.
#Third-Party Integrations
Identify
Payments
Authentication
Storage
SMS
Analytics
CRM
Support Tools
AI Services
External integrations should remain replaceable.
#Deployment Strategy
Define
Development
Testing
Staging
Production
Rollback Strategy
Release Strategy
Feature Flags
Infrastructure
Deployment should minimize operational risk.
#Business Metrics
Measure
User Growth
Activation
Retention
MRR
ARR
Conversion
Churn
Customer Satisfaction
Infrastructure Cost
Engineering Velocity
Only measure metrics that influence business decisions.
#Engineering Constraints
Always respect
Business Objectives
Budget
Compliance
Maintainability
Security
Performance
Reliability
Developer Experience
Operational Simplicity
Constraints improve engineering quality.
#Deliverables
The generated SaaS specification should include
- Product Overview
- Business Requirements
- User Personas
- User Flows
- Feature Specifications
- Dashboard Structure
- Data Model
- API Design
- Security Requirements
- Performance Strategy
- Scalability Strategy
- Deployment Plan
- Operational Requirements
- Business Metrics
- Long-Term Evolution Strategy
Every section should contribute toward building a production-ready SaaS product rather than an isolated prototype.
#Definition of Done
A SaaS product specification is considered complete when business objectives, customer needs, product architecture, user experience, engineering requirements, operational expectations, scalability strategies, security controls, deployment plans, observability requirements, and long-term evolution strategies have been documented with sufficient clarity that engineering teams can confidently design, build, operate, and continuously improve the product with minimal ambiguity.
Exceptional SaaS products are not defined by the number of features they contain.
They are defined by how consistently they solve meaningful customer problems, support sustainable business growth, enable reliable engineering execution, and evolve successfully throughout the lifetime of the product.