Autonomous Product Research & Documentation System v3.0 - Complete WebSearch Execution Guide

Generated: 2025-07-27

Overview

This is a complete autonomous execution guide for Claude Code to systematically research and document a software product from concept to market leadership. The system produces 116+ comprehensive markdown documents through 28 sequential phases, combining WebSearch research with visual competitor analysis and post-launch growth strategies.

AUTONOMOUS EXECUTION: This guide is designed for Claude Code to execute independently without human intervention, using WebSearch as the primary research tool throughout all phases, incorporating visual documentation tools, and extending through post-launch growth and market leadership phases.

Output Goal: Generate a thoroughly researched collection of 116+ markdown files (2,000-5,000 words each) plus 60+ visual assets that document every aspect of product development from problem discovery through MVP implementation, launch, growth, and market leadership establishment.

Autonomous Execution Methodology

CRITICAL REQUIREMENTS FOR CLAUDE CODE:

Strict Sequential Execution: Complete ALL deliverables in Phase N before proceeding to Phase N+1
WebSearch-Only Research: Use WebSearch tool for ALL market intelligence gathering (no other research tools)
Mandatory Query Execution: Execute ALL specified WebSearch queries in each phase
Word Count Compliance: Each markdown file must meet specified word count (2,000-5,000 words)
Fact Verification Requirement: Every statistical claim, market figure, industry trend, and technical specification MUST be sourced from WebSearch results with exact URLs
Zero Unsourced Claims: No assertions about market conditions, competitor capabilities, or user behaviors without documented WebSearch evidence
Citation Requirements: Every claim must cite specific WebSearch results with verifiable source URLs
Progression Triggers: Only proceed to next phase after completing "Phase Complete" checklist
No Human Intervention: System designed for complete autonomous execution

Universal Policy Framework References

IMPORTANT: The following universal policy frameworks have been extracted from comprehensive analysis and are available as foundational, reusable methodologies in /docs/private/policies/. These frameworks provide systematic approaches to architecture, development, and design decisions that apply universally across all projects and phases.

Tier 1: Critical Architecture & Development Frameworks (12 frameworks)

Technical Architecture Frameworks

AI-First Architecture Principles: @docs/private/policies/technical-architecture/ai-first-architecture-principles.md - Conversational interface patterns and intelligent automation systems for AI-native applications
Zero-Cost Architecture Methodology: @docs/private/policies/technical-architecture/zero-cost-architecture-methodology.md - Serverless cost optimization with scale-to-zero patterns and intelligent resource management
Serverless Infrastructure Patterns: @docs/private/policies/technical-architecture/serverless-infrastructure-patterns.md - Cloud-native scalability with multi-region deployment and auto-scaling architectures
Security Architecture Framework: @docs/private/policies/technical-architecture/security-architecture-framework.md - AI security with prompt injection defense, model validation, and comprehensive threat protection
Performance Optimization Methodology: @docs/private/policies/technical-architecture/performance-optimization-methodology.md - High-performance application design with systematic optimization and monitoring approaches
Integration Architecture Patterns: @docs/private/policies/technical-architecture/integration-architecture-patterns.md - Event-driven integration with message queuing, API management, and service orchestration

Development Excellence Frameworks

AI-Native Development Methodology: @docs/private/policies/development/ai-native-development-methodology.md - Conversation-driven development with intent analysis and AI-powered code generation workflows
Testing Framework Methodology: @docs/private/policies/development/testing-framework-methodology.md - Comprehensive quality assurance with automation-first approaches and continuous testing integration
Compliance Framework Methodology: @docs/private/policies/development/compliance-framework-methodology.md - Privacy-by-design exceeding global regulatory requirements (GDPR, CAN-SPAM, CASL)
Accessibility Implementation Methodology: @docs/private/policies/development/accessibility-implementation-methodology.md - WCAG AAA compliance with inclusive design excellence and automated accessibility validation

Design System Excellence Frameworks

Component Library Design System: @docs/private/policies/design-system/component-library-design-system.md - Atomic design with accessibility-first component architecture and universal interface patterns
Design Token System Methodology: @docs/private/policies/design-system/design-token-system-methodology.md - Universal token management with automated distribution and cross-platform synchronization

Tier 2: High-Value Specialized Frameworks (10 frameworks)

Advanced Technical Frameworks

Data Pipeline Architecture Patterns: @docs/private/policies/technical-architecture/data-pipeline-architecture-patterns.md - Streaming data processing with real-time analytics and scalable data transformation pipelines
Deployment Pipeline Methodology: @docs/private/policies/development/deployment-pipeline-methodology.md - Automated deployment with progressive strategies, infrastructure as code, and continuous delivery excellence
API Design Standards: @docs/private/policies/development/api-design-standards.md - RESTful API design with OpenAPI specifications, versioning strategies, and developer experience optimization

Advanced Design & UX Frameworks

UI/UX Pattern Library: @docs/private/policies/design-system/ui-ux-pattern-library.md - Comprehensive interaction patterns, user flows, and visual design systems for consistent user experiences

Additional High-Value Frameworks (6 remaining)

Note: Additional Tier 2 frameworks in development - Documentation Automation, Monitoring & Observability, Code Quality Standards, DevSecOps Integration, Multi-Cloud Architecture, and Advanced Analytics Patterns

Universal Application: These policy frameworks provide systematic methodologies that transcend individual projects, establishing foundational approaches for architecture decisions, development practices, and design standards. Reference using format @docs/private/policies/[category]/[framework-name].md throughout all phases.

Extracted Implementation Guides

IMPORTANT: The following implementation guides have been extracted from the phase documents and are available as standalone, reusable references in /docs/private/guides/. These guides provide step-by-step procedures for common development, design, and research tasks that are referenced throughout the phases.

Development & Technical Guides

Docker Development Setup: @docs/private/guides/development/docker-setup-guide.md - Complete containerized development environment setup procedures
n8n Deployment: @docs/private/guides/development/n8n-deployment-guide.md - Self-hosting n8n workflow automation on Google Cloud Run
AI Workflow Integration: @docs/private/guides/development/ai-workflow-integration-guide.md - AI-powered workflow generation system implementation
Testing Framework: @docs/private/guides/development/testing-framework-guide.md - Comprehensive testing implementation following testing pyramid methodology
API Integration: @docs/private/guides/development/api-integration-guide.md - Event-driven API integration patterns with resilience

Design & UX Guides

Accessibility Implementation: @docs/private/guides/design/accessibility-implementation-guide.md - WCAG 2.1 AA compliance implementation procedures
Component Library Creation: @docs/private/guides/design/component-library-guide.md - Building scalable, reusable component libraries with atomic design principles
Design Prototyping Workflow: @docs/private/guides/design/prototyping-workflow-guide.md - Interactive prototype creation and testing procedures
Information Architecture Planning: @docs/private/guides/design/information-architecture-guide.md - Systematic IA design and user mental model research

Research & Analysis Guides

Digital Investigation Research: @docs/private/guides/research/digital-investigation-guide.md - Comprehensive platform research across Reddit, social media, and review sites
Competitive Analysis Framework: @docs/private/guides/research/competitor-analysis-guide.md - Systematic competitive intelligence gathering and analysis
Problem Validation Framework: @docs/private/guides/research/problem-validation-guide.md - Evidence-based problem validation with quantifiable metrics

Usage Instructions: Reference these guides at relevant phases using the format @docs/private/guides/[category]/[guide-name].md. The guides contain product-agnostic procedures that can be applied to any development project.

Expected Output Inventory

By completion, Claude Code will generate 116+ comprehensive markdown files:

Phase 1: Problem Discovery (6 files, 15,000+ total words)

research-problem-discovery-plan.md (2,500+ words)
research-digital-investigation-guide.md (2,500+ words)
problem-statement-template.md (2,500+ words)
research-market-signals.md (2,500+ words)
research-anecdotes-evidence.md (2,500+ words)
research-pleasure-points.md (2,500+ words)

Phase 2: Market Analysis (4 files, 12,000+ total words)

analysis-competitor-framework.md (3,000+ words)
analysis-market-sizing.md (3,000+ words)
analysis-user-personas.md (3,000+ words)
analysis-pricing-research.md (3,000+ words)

Phase 3: Solution Design (4 files, 12,000+ total words)

prd-mvp-features.md (3,000+ words)
design-ux-specification.md (3,000+ words)
analysis-value-proposition.md (3,000+ words)
analysis-technical-feasibility.md (3,000+ words)

Phase 4: Technical Architecture (4 files, 16,000+ total words)

tech-system-architecture.md (4,000+ words)
tech-infrastructure-design.md (4,000+ words)
tech-security-architecture.md (4,000+ words)
tech-development-plan.md (4,000+ words)

Phase 5: Security Architecture & Design (4 files, 16,000+ total words)

security-architecture-design.md (4,000+ words)
security-threat-modeling.md (4,000+ words)
security-requirements-specification.md (4,000+ words)
security-compliance-planning.md (4,000+ words)

Phase 6: Business Model (4 files, 16,000+ total words)

business-model-canvas.md (4,000+ words)
business-financial-model.md (4,000+ words)
business-pricing-strategy.md (4,000+ words)
business-growth-model.md (4,000+ words)

Phase 7: Implementation Planning (4 files, 20,000+ total words)

implementation-roadmap.md (5,000+ words)
implementation-testing-strategy.md (5,000+ words)
implementation-devops-plan.md (5,000+ words)
implementation-launch-prep.md (5,000+ words)

Phase 8: Go-to-Market (4 files, 20,000+ total words)

marketing-launch-strategy.md (5,000+ words)
marketing-content-plan.md (5,000+ words)
marketing-acquisition-plan.md (5,000+ words)
marketing-analytics-setup.md (5,000+ words)

Phase 9: Technology Choices (4 files, 16,000+ total words)

tech-serverless-architecture.md (4,000+ words)
tech-stack-analysis.md (4,000+ words)
tech-integration-patterns.md (4,000+ words)
tech-cost-optimization-strategy.md (4,000+ words)

Phase 10: UI/UX Wireframes (9 files, 22,500+ total words)

wireframe-dashboard-overview.md (2,500+ words)
wireframe-campaign-creation.md (2,500+ words)
wireframe-automation-builder.md (2,500+ words)
wireframe-contact-management.md (2,500+ words)
wireframe-analytics-reporting.md (2,500+ words)
wireframe-onboarding-experience.md (2,500+ words)
information-architecture.md (2,500+ words)
interaction-design-patterns.md (2,500+ words)
overview-mockups.md (2,500+ words)

Phase 11: Visual Competitor Analysis (4 files, 14,000+ total words, 60+ screenshots)

analysis-competitor-ui-patterns.md (3,500+ words, 15+ screenshots)
design-ux-flows-visual.md (3,500+ words, 10+ flow diagrams)
design-system-components.md (3,500+ words, 20+ component examples)
design-brand-visual-strategy.md (3,500+ words, 15+ mood boards)

Phase 12: Feature Specifications (8 files, 32,000+ total words)

prd-technical-specifications.md (4,000+ words)
prd-feature-implementation.md (4,000+ words)
prd-user-stories-detailed.md (4,000+ words)
prd-testing-specifications.md (4,000+ words)
prd-migration-specifications.md (4,000+ words)
prd-deliverability-specifications.md (4,000+ words)
prd-compliance-specifications.md (4,000+ words)
prd-performance-specifications.md (4,000+ words)

Phase 13: UX/UI Design (6 files, 24,000+ total words)

design-mockups-specifications.md (4,000+ words)
design-prototype-specifications.md (4,000+ words)
design-pattern-library.md (4,000+ words)
design-accessibility-guide.md (4,000+ words)
design-onboarding-flows.md (4,000+ words)
design-template-gallery.md (4,000+ words)

Phase 14: Design System (6 files, 24,000+ total words)

design-system-architecture.md (4,000+ words)
design-system-components.md (4,000+ words)
design-system-implementation.md (4,000+ words)
design-system-governance.md (4,000+ words)
design-system-email-components.md (4,000+ words)
design-system-automation-components.md (4,000+ words)

Phase 15: MVP Implementation with Claude Code (4 files, 16,000+ total words + Working Code Output)

implementation-environment-setup.md (4,000+ words) + MANDATORY CLAUDE CODE PROMPTS → Working Next.js application
implementation-component-development.md (4,000+ words) + MANDATORY CLAUDE CODE PROMPTS → Working UI components
implementation-api-integration.md (4,000+ words) + MANDATORY CLAUDE CODE PROMPTS → Working API endpoints
implementation-testing-validation.md (4,000+ words) + MANDATORY CLAUDE CODE PROMPTS → Working test suite

Phase 16: Development Setup (4 files, 16,000+ total words)

setup-project-initialization.md (4,000+ words)
setup-development-workflow.md (4,000+ words)
setup-local-development.md (4,000+ words)
setup-team-onboarding.md (4,000+ words)

Phase 17: MVP Development (6 files, 30,000+ total words)

development-core-features.md (5,000+ words)
development-integrations.md (5,000+ words)
development-frontend-guide.md (5,000+ words)
development-backend-guide.md (5,000+ words)
development-automation-templates.md (5,000+ words)
development-support-system.md (5,000+ words)

Phase 18: Payment Integration (4 files, 16,000+ total words)

payment-stripe-integration.md (4,000+ words)
billing-automation-system.md (4,000+ words)
monetization-pricing-strategy.md (4,000+ words)
revenue-analytics-portal.md (4,000+ words)

Phase 19: Support Materials Production (4 files, 16,000+ total words)

support-documentation-system.md (4,000+ words)
user-onboarding-materials.md (4,000+ words)
help-center-knowledge-base.md (4,000+ words)
training-resources-guide.md (4,000+ words)

Phase 20: Testing & Validation (4 files, 16,000+ total words)

testing-execution-guide.md (4,000+ words)
testing-qa-automation.md (4,000+ words)
performance-load-testing.md (4,000+ words)
quality-assurance-validation.md (4,000+ words)

Phase 21: Security Compliance (4 files, 16,000+ total words)

security-compliance-frameworks.md (4,000+ words)
data-protection-privacy-policy.md (4,000+ words)
security-monitoring-incident-response.md (4,000+ words)
compliance-audit-certification.md (4,000+ words)

Phase 22: Beta Customer Acquisition (4 files, 16,000+ total words)

beta-customer-acquisition-strategy.md (4,000+ words)
product-market-fit-validation.md (4,000+ words)
feedback-collection-systems.md (4,000+ words)
early-customer-success-programs.md (4,000+ words)

Phase 23: SEO & Content Marketing (4 files, 16,000+ total words)

seo-strategy-keyword-research.md (4,000+ words)
content-marketing-editorial-calendar.md (4,000+ words)
help-center-seo-optimization.md (4,000+ words)
organic-growth-lead-generation.md (4,000+ words)

Phase 24: Marketing Launch (4 files, 16,000+ total words)

product-launch-campaign-strategy.md (4,000+ words)
pr-media-outreach-plan.md (4,000+ words)
community-social-engagement.md (4,000+ words)
launch-analytics-tracking.md (4,000+ words)

Phase 25: Customer Success (4 files, 16,000+ total words)

customer-success-framework.md (4,000+ words)
health-scoring-lifecycle-management.md (4,000+ words)
advanced-onboarding-personalization.md (4,000+ words)
retention-churn-prevention-advocacy.md (4,000+ words)

Phase 26: Growth & Scaling (4 files, 16,000+ total words)

growth-hacking-viral-mechanics.md (4,000+ words)
product-led-growth-strategies.md (4,000+ words)
team-infrastructure-scaling.md (4,000+ words)
performance-operational-efficiency.md (4,000+ words)

Phase 27: Product Iteration (4 files, 16,000+ total words)

product-iteration-feedback-analysis.md (4,000+ words)
competitive-intelligence-innovation.md (4,000+ words)
technical-debt-platform-enhancement.md (4,000+ words)
feature-roadmap-prioritization.md (4,000+ words)

Phase 28: Market Leadership (4 files, 16,000+ total words)

market-leadership-positioning.md (4,000+ words)
thought-leadership-content-strategy.md (4,000+ words)
innovation-labs-emerging-tech.md (4,000+ words)
strategic-expansion-exit-planning.md (4,000+ words)

Meta-Documentation (3+ files, 9,000+ total words)

decisions/decision-log.md (3,000+ words)
research/validation-tracker.md (3,000+ words)
research/market-intelligence.md (3,000+ words)

TOTAL OUTPUT: 153+ files, 628,000+ words of researched content, 60+ visual assets

Visual Documentation Requirements

CRITICAL IMPORTANCE OF VISUAL RESEARCH: Starting from Phase 10, visual documentation becomes essential for creating a competitive product. Screenshots, mockups, and visual examples provide concrete evidence that text alone cannot convey.

Why Visual Documentation Matters:

Competitor Interface Analysis: Screenshots reveal UI patterns, color schemes, and layout decisions that inspire better design choices
User Flow Documentation: Visual flow diagrams communicate complex interactions more effectively than written descriptions
Design System Components: Visual examples of buttons, forms, and components ensure consistent implementation
Accessibility Validation: Screenshots with annotations demonstrate WCAG compliance and inclusive design
Error State Documentation: Visual examples of error handling improve user experience consistency

Visual Asset Requirements by Phase:

Phase 10: 60+ visual assets using @knowcode/screenshotfetch for screenshots and @knowcode/imgfetch for existing images
Phase 10: Mockup descriptions and wireframe specifications
Phase 11: Component library visual examples and style guides
Phase 13: Implementation screenshots and progress documentation
Phase 14: Testing evidence and validation screenshots

Best Practices for Visual Documentation:

Always Include Alt Text: Every image must have descriptive alt text for accessibility
Annotate Key Elements: Use arrows, highlights, and callouts to draw attention to important features
Provide Context: Include captions explaining what the image demonstrates
Maintain Consistency: Use consistent image sizes and formats throughout documentation
Version Control: Include dates and version numbers on mockups and screenshots

Visual Documentation Implementation Guide:

Screenshot Capture (@knowcode/screenshotfetch)

For capturing screenshots of live websites and web applications:

// Install: npm install @knowcode/screenshotfetch
const { ScreenshotCapture } = require('@knowcode/screenshotfetch');

// Use for: Competitor homepages, dashboards, UI elements
// Output: High-quality screenshots with automatic cookie banner blocking
// Features: Built-in cookie consent handling, better reliability

Image Download (@knowcode/imgfetch)

For downloading existing images from URLs:

// Install: npm install @knowcode/imgfetch
const ImageFetcher = require('@knowcode/imgfetch');

// Use for: Logos, marketing materials, existing assets
// Output: Downloaded images from public URLs

When to Use Each Tool:

@knowcode/screenshotfetch: When you need screenshots of web pages, interactive elements, or dynamic content (automatically handles cookie banners)
@knowcode/imgfetch: When downloading existing images like logos, diagrams, or marketing materials

MANDATORY MARKDOWN STANDARDS FOR ALL DELIVERABLES

All 70+ markdown files MUST follow these standards for consistency and quality:

Visual Evidence Requirements

IMPORTANT: Throughout ALL phases, capture visual evidence when relevant:

Image Storage: All images must be stored in _images/ directory within the same folder as the markdown file
Screenshot Guide: Use @docs/prompts/screenshot-capture-guide.md for capture techniques
When to Capture:
- User complaints and testimonials (Phase 1)
- Competitor interfaces and features (Phase 2)
- UI/UX patterns and workflows (Phase 3)
- Error messages and pain points (All phases)
- Success examples and best practices (All phases)

Document Structure Requirements

H1 Title: Start each file with clear # Document Title
Overview Paragraph: Brief introduction immediately after title explaining document purpose
Hierarchical Headings: Use H2 for main sections, H3 for subsections (never skip levels)
Summary/Conclusion: End with key takeaways or next steps when appropriate

File Naming Standards

MANDATORY: All files must use lowercase with hyphens:

research-problem-discovery-plan.md
analysis-competitor-framework.md
Research_Problem_Discovery.md
competitor analysis.md

Content Quality Standards

Active Voice: Write instructions in present tense, active voice
Clear Language: Use concise, jargon-free explanations
Examples Required: Include specific examples, citations, data points
Lists & Tables: Use bullet points for unordered info, numbered lists for sequential steps
Descriptive Links: Use [See competitor analysis](analysis-competitor-framework.md) not "click here"

WebSearch Citation Requirements

UNIVERSAL CITATION STANDARDS - Apply to ALL content types across ALL phases:

Source Attribution: Every claim must cite specific WebSearch results WITH EXACT URLS
Link Format: Use descriptive link text with sources AND DIRECT LINKS
Data Validation: Include dates, source credibility, cross-verification notes
Quote Integration: Use direct quotes from research with proper attribution AND SOURCE URLS
MANDATORY URL VERIFICATION: Every testimonial, quote, and claim MUST include the exact URL where found
NO FABRICATED CONTENT: All content must be verifiable through WebSearch results
SCREENSHOT VERIFICATION: When capturing user testimonials, include visible URLs in screenshots

FACT-CHECKING MANDATE FOR ALL PHASES:

Statistical Claims: Revenue figures, market sizes, growth rates → WebSearch source required
Competitor Analysis: Feature comparisons, pricing data, customer counts → WebSearch verification mandatory
Industry Trends: Technology adoption, user behaviors, market shifts → WebSearch documentation required
User Testimonials: Reviews, complaints, success stories → WebSearch URLs mandatory
Technical Specifications: API capabilities, integration features, system requirements → WebSearch validation required
Business Intelligence: Company valuations, funding rounds, executive statements → WebSearch sources mandatory

CITATION FORMAT STANDARDS:

**Claim**: "ActiveCampaign raised prices by 40% in 2024"
**Source**: [ActiveCampaign Pricing Update](https://activecampaign.com/pricing-2024) - Verified July 2024

**Quote**: "Users report 67% dissatisfaction with new pricing"
**Source**: [Reddit Discussion Thread](https://reddit.com/r/emailmarketing/activecampaign-revolt) - 847 comments analyzed

Code & Technical Standards

Language Specification: Always specify language for syntax highlighting
Comment Inclusion: Add explanatory comments for complex examples
Example Quality: Show both correct and incorrect usage when relevant

Accessibility Compliance

Heading Hierarchy: Never skip heading levels (H1→H2→H3, not H1→H3)
Descriptive Text: Use meaningful descriptions for all links and references
Screen Reader Friendly: Ensure all content is accessible without visual context

QUALITY GATE: Each markdown file will be validated against these standards before considering the phase complete.

UNIVERSAL CITATION REQUIREMENTS FOR ALL PHASES

MANDATORY FOR PHASES 4-27: All phases beyond the initial research phases (1-3) must include comprehensive URL citation requirements for domain-specific content:

Technical Phases (4, 9-17): All code examples, architecture patterns, framework specifications, performance benchmarks, and technical standards MUST include exact URLs to official documentation, technical case studies, and verified implementation guides
Security Phases (5, 20): All security frameworks, threat assessments, compliance requirements, testing methodologies, and incident procedures MUST include exact URLs to official security standards, regulatory documentation, and industry best practices
Business Phases (6, 18-27): All financial data, market projections, pricing strategies, growth metrics, and business model assumptions MUST include exact URLs to industry reports, financial analyses, and business case studies
Design/UX Phases (13-14): All design patterns, UX principles, accessibility standards, and user research findings MUST include exact URLs to design resources, UX studies, and best practice guides
Marketing/Growth Phases (21-27): All marketing strategies, channel effectiveness data, customer acquisition costs, and growth tactics MUST include exact URLs to marketing case studies, industry benchmarks, and promotional strategy resources

IMPLEMENTATION NOTE: Each "Claude Code Instructions" section in phases 4-27 inherently requires URL citation for all domain-specific claims, data, and recommendations relevant to that phase's focus area.

VISUAL DOCUMENTATION IMPLEMENTATION GUIDE

CRITICAL FOR ALL PHASES: Visual documentation enhances understanding throughout the research process. Phase 8+ requires extensive screenshots.

Visual Evidence by Phase

Phase 1-3: Capture supporting evidence (10-20 images per phase)

User complaints, forum discussions
Competitor examples
Market trends and data visualizations

Phase 4-7: Technical and business diagrams (5-10 images per phase)

Architecture diagrams
Business model visualizations
Process flows

Phase 10+: Extensive visual documentation (60+ images)

Detailed competitor UI analysis
Complete design system documentation
Implementation progress screenshots

Follow these exact steps:

Image Capture Setup

Install @knowcode/imgfetch:
```
npm install @knowcode/imgfetch
```

Create Image Directory Structure:

docs/[phase-number]-[phase-name]/_images/
├── [competitor-name]/     # e.g., activecampaign/, mailchimp/
├── evidence/             # For user complaints, testimonials
├── ui-patterns/          # For general UI pattern examples
├── workflows/            # For flow diagrams and sequences
├── components/           # For component examples
└── brand/               # For branding and visual strategy

IMPORTANT: The _images/ directory must be at the same level as the markdown files

Screenshot Capture Process

Review the Screenshot Guide: Consult @docs/prompts/screenshot-capture-guide.md for:
- Cookie banner removal techniques
- Batch processing strategies
- Error handling approaches
- Performance optimization

Create a capture script using @knowcode/screenshotfetch:

const { ScreenshotCapture } = require('@knowcode/screenshotfetch');

// Example: Capture competitor homepage
const capture = new ScreenshotCapture();
await capture.init();
await capture.captureScreenshot({
  url: 'https://www.activecampaign.com',
  output: './docs/10-visual-analysis/_images/activecampaign/homepage.png',
  width: 1200,
  height: 800,
  fullPage: false,
  waitFor: 2000
});
await capture.close();

Systematic Capture List (minimum requirements by phase):
- Phase 10: 60+ screenshots (15+ per markdown file)
- Phase 10: 30+ mockup examples
- Phase 11: 40+ component examples
- Phase 13: 20+ implementation screenshots
- Phase 14: 20+ testing evidence screenshots

Image Embedding Format

MANDATORY: Every image must be embedded with this exact format:

![Descriptive alt text explaining what the image shows](./_images/category/filename.png)
*Figure X: Caption explaining the significance of this image in context.*

Path Requirements:

Always use relative paths starting with ./_images/
The _images/ folder must be in the same directory as the markdown file
Never use absolute paths or paths starting with /

Example:

![ActiveCampaign dashboard showing card-based layout with multiple analytics widgets](./_images/activecampaign/dashboard-overview.png)
*Figure 1: ActiveCampaign's dashboard demonstrates enterprise-focused information density with 12+ metric cards competing for user attention.*

Image Requirements

Naming Convention: platform-feature-variant-state.png
- Examples: mailchimp-email-editor-main.png, convertkit-button-primary-hover.png
Alt Text Requirements:
- Describe what the image shows
- Include platform name
- Mention key UI elements visible
- Note any significant patterns or issues
Image Organization:
- Group by competitor for platform-specific analysis
- Use feature categories for cross-platform comparisons
- Maintain consistent file sizes (typically 1200px width for full screenshots)
Caption Standards:
- Start with "Figure N:"
- Explain why this screenshot is significant
- Connect to analysis in the text
- Keep under 2 lines

Phase-Specific Visual Requirements

Phase 1 (40+ images): Problem Discovery Evidence

10+ pricing complaint screenshots from forums/Reddit
10+ complexity frustration examples
10+ alternative seeking discussions
10+ feature overload interface examples

Phase 2 (20+ images): Market Analysis

8+ competitor homepage/pricing screenshots
5+ market data visualizations
5+ user review screenshots
2+ persona-related visuals

Phase 3 (15+ images): Solution Design

10+ wireframe sketches
5+ user flow diagrams
Value proposition visualizations

Phase 8 (60+ images): Visual Competitor Analysis

15+ competitor interface overviews
10+ email editor comparisons
10+ automation builder examples
10+ dashboard and analytics views
5+ mobile interface examples
10+ component pattern examples

Phase 12 (30+ images): UX/UI Design

Mockup examples for each major feature
Responsive design demonstrations
Interaction state visualizations

Phase 13 (40+ images): Design System

Component library examples
Design token visualizations
Pattern library demonstrations

Verification Checklist

Before marking any phase with visual requirements complete:

All required images captured and saved in _images/ directory at same level as markdown
Every image has descriptive alt text for accessibility
All images are embedded in the relevant markdown sections
Figure captions explain significance
Image paths are relative (./_images/) and correct
Total image count meets or exceeds phase requirements
Cookie banners removed using techniques from screenshot-capture-guide.md
Images organized in appropriate subdirectories

PHASE 1: PROBLEM DISCOVERY EXECUTION PROTOCOL

Initial Product Context

Product Concept: NudgeCampaign - A focused email marketing platform with drag-and-drop editor, newsletter templates, visual automation builder, and behavioral tracking. Simplified alternative to complex, expensive tools like ActiveCampaign.

# Problem Definition
PROBLEM_DOMAIN: "Cost-effective email campaign tools for simplified marketing automation"
INITIAL_HYPOTHESIS: "ActiveCampaign and similar tools are overpriced and feature-bloated for most users"
TARGET_USERS: "Small businesses and software companies needing automated email marketing"
CURRENT_PAIN: "Existing tools are too complex and expensive for basic email automation needs"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 1

Claude Code Instructions: Execute ALL 8 WebSearch queries below sequentially. Use results to create 4 comprehensive markdown documents. DO NOT PROCEED to Phase 2 until Phase 1 Complete checklist is satisfied.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Pricing Pain Research

Query 1: "ActiveCampaign too expensive" pricing complaints reddit 2024 2025
Query 2: "email marketing tools overpriced" "small business" forum complaints
Query 3: "Mailchimp vs ActiveCampaign" pricing comparison "too costly"

2. Feature Complexity Research

Query 4: "email marketing tools too complicated" user experience complaints
Query 5: "simple email automation" alternatives "drag and drop" affordable

3. Market Gap Analysis

Query 6: "email marketing" pain points "too many features" bloated software
Query 7: "newsletter tools" comparison "basic automation" vs "advanced features"
Query 8: "email marketing platform" "stripped down" minimal features demand

4. Positive Sentiment & Success Research

Query 9: "email marketing success stories" case studies revenue ROI testimonials
Query 10: "GetResponse customer testimonials" quotes success stories revenue
Query 11: "Mailchimp success stories" customer testimonials case studies ROI
Query 12: "email marketing case studies" quantified results revenue increase conversions

CRITICAL VERIFICATION REQUIREMENTS

MANDATORY VERIFICATION PROCESS FOR ALL TESTIMONIALS:

WEBSEARCH DISCOVERY: Find testimonials only through WebSearch tool results
WEBFETCH VERIFICATION: Use WebFetch tool to verify quote exists on the claimed page exactly as written
EXACT QUOTE MATCHING: Quote must match word-for-word what appears on the source page - NO modifications
COMPANY/PERSON VERIFICATION: Customer name and company must be real and verifiable from the source
SCREENSHOT CAPTURE: Use @knowcode/screenshotfetch to capture screenshots showing the actual quote on the webpage
SOURCE ACCESSIBILITY: URL must be publicly accessible and load correctly at time of verification
CUSTOMER NAME INCLUSION: Include real customer names and companies when available in source

SCREENSHOT IMPLEMENTATION:

Tool: Use @knowcode/screenshotfetch for all screenshot capture (NOT Puppeteer)
Cookie Handling: @knowcode/screenshotfetch automatically blocks cookie consent banners
Verification: Screenshots must show the actual quote on the actual webpage
Naming: Follow pattern [category]-[type]-[number].png (e.g., testimonial-pricing-01.png)
Storage: Save to _images/ directory at same level as markdown file

FABRICATION WARNING:

NEVER create fictional quotes or testimonials
NEVER attribute real quotes to wrong sources
NEVER combine quotes from different sources
NEVER modify quotes to sound better or fix grammar
NEVER paraphrase or summarize customer feedback
ONLY use exact quotes found through WebSearch with URLs verified via WebFetch
ALL testimonials must be traceable to original source with screenshot proof

DELIVERABLE SPECIFICATIONS - CREATE 6 MARKDOWN FILES

After executing ALL 12 WebSearch queries above, create these files with exact specifications:

1.1 Digital Problem Discovery Plan (`research-problem-discovery-plan.md`)

WORD COUNT: Exactly 2,500+ words
STRUCTURE REQUIREMENTS:

Section 1: Executive Summary (400 words) - Problem discovery methodology overview
Section 2: WebSearch Findings Analysis (800 words) - Detailed analysis from all 8 queries above with specific citations
Section 3: Pricing Pain Documentation (400 words) - ActiveCampaign/Mailchimp complaints analysis
Section 4: Feature Complexity Analysis (400 words) - User experience pain points from research
Section 5: Market Gap Validation (300 words) - Evidence of demand for simpler tools
Section 6: Research Methodology Framework (200 words) - Systematic approach used

MANDATORY CONTENT:

Direct quotes from WebSearch results (minimum 15 citations)
Specific Reddit threads, forum posts, review sites referenced
Quantified data on complaint frequency and sentiment
Platform-specific research strategies (Reddit r/entrepreneur, r/smallbusiness, etc.)
Timeline for 7-day research execution
Hypothesis validation criteria with supporting evidence

1.2 Digital Investigation Guide (`research-digital-investigation-guide.md`)

WORD COUNT: Exactly 2,500+ words
STRUCTURE REQUIREMENTS:

Section 1: Platform Research Strategies (600 words) - Reddit, HackerNews, IndieHackers, Discord
Section 2: Search Operators & Techniques (500 words) - Advanced search methods for each platform
Section 3: Review Mining Framework (500 words) - G2, Capterra, Trustpilot analysis methods
Section 4: Social Listening Setup (400 words) - Brand mention monitoring strategies
Section 5: Data Triangulation Methods (300 words) - Validating findings across sources
Section 6: Research Documentation Templates (200 words) - Standardized capture formats

IMPLEMENTATION GUIDE: For detailed step-by-step procedures, refer to @docs/private/guides/research/digital-investigation-guide.md - Comprehensive platform research across Reddit, social media, and review sites with systematic data collection techniques.

MANDATORY CONTENT:

Specific subreddits: r/entrepreneur, r/smallbusiness, r/marketing, r/SaaS
Discord communities: Indie Hackers, SaaS Growth, Email Marketing
Review site analysis: G2.com ActiveCampaign reviews, Capterra complaints
Twitter/X search strategies for real-time complaints
YouTube comment analysis for tutorial-related pain points

1.3 Problem Statement Validation Template (`problem-statement-template.md`)

WORD COUNT: Exactly 2,500+ words
STRUCTURE REQUIREMENTS:

Section 1: Problem Definition Framework (500 words) - Structure for documenting problems
Section 2: Digital Evidence Collection (600 words) - Methods for gathering proof online
Section 3: Market Size Indicators (400 words) - Community sizes, discussion frequency metrics
Section 4: Current Solutions Analysis (500 words) - Existing tool shortcomings documentation
Section 5: Cost/Impact Quantification (300 words) - Financial impact analysis from research
Section 6: Validation Checklist (200 words) - Go/no-go criteria framework

IMPLEMENTATION GUIDE: For detailed step-by-step procedures, refer to @docs/private/guides/research/problem-validation-guide.md - Evidence-based problem validation with quantifiable metrics and systematic go/no-go decision frameworks.

MANDATORY CONTENT:

Template for documenting problem statements with WebSearch validation
Metrics for measuring problem frequency (posts per month, upvotes, engagement)
Framework for analyzing competitor shortcomings from reviews
Methods for quantifying willingness to pay from forum discussions
Timeline indicators and market readiness signals

1.4 Market Signal Research Framework (`research-market-signals.md`)

WORD COUNT: Exactly 2,500+ words
STRUCTURE REQUIREMENTS:

Section 1: Search Trend Analysis (500 words) - Google Trends methodology and interpretation
Section 2: Community Monitoring Strategy (600 words) - Reddit, forum, Discord tracking systems
Section 3: Competitor Intelligence Framework (500 words) - Support ticket analysis, feature requests
Section 4: Social Media Sentiment Tracking (400 words) - Twitter, LinkedIn complaint monitoring
Section 5: Industry Report Discovery (300 words) - Finding and analyzing market research
Section 6: Signal Interpretation Guidelines (200 words) - Distinguishing noise from real signals

MANDATORY CONTENT:

Specific Google Trends queries for email marketing tools
Reddit monitoring setup for r/entrepreneur, r/smallbusiness, r/marketing
Competitor analysis targets: ActiveCampaign, Mailchimp, ConvertKit, Drip
Social listening tools and manual monitoring techniques
Industry report sources: Gartner, Forrester, HubSpot State of Marketing
Framework for measuring signal strength and reliability

1.5 Visual Anecdotes & Evidence Collection (`research-anecdotes-evidence.md`)

WORD COUNT: Exactly 2,500+ words
VISUAL REQUIREMENTS: 40+ screenshots/images
IMAGE STORAGE: ./docs/01-problem-discovery/_images/

STRUCTURE REQUIREMENTS:

Section 1: Pricing Complaint Evidence (600 words) - Screenshots of price increase complaints
Section 2: Complexity Frustrations (600 words) - Visual evidence of user confusion
Section 3: Alternative Seeking Behavior (500 words) - Screenshots of migration discussions
Section 4: Feature Overload Examples (500 words) - Interface complexity documentation
Section 5: User Success Stories (400 words) - What users want instead
Section 6: Evidence Synthesis (400 words) - Key patterns from visual research

MANDATORY CONTENT:

40+ screenshots from Reddit, Twitter, review sites, and forums WITH VERIFIED URLS
Categorized visual evidence: pricing (10+), complexity (10+), alternatives (10+), frustrations (10+)
Direct quotes with screenshot context showing user pain points WITH SOURCE URLS
Visual proof of ActiveCampaign 40% price increases WITH DOCUMENTATION LINKS
CRITICAL: ALL testimonials and complaints MUST be real and include the exact URL where found
NO FABRICATED CONTENT: Every quote must be verifiable through WebSearch results
URL VERIFICATION: Include direct links to Reddit posts, forum discussions, review sites
Screenshots of users seeking simpler alternatives
Beautified presentation following beautiful-documentation-design.md guidelines

CAPTURE METHODOLOGY:

MANDATORY TOOL: Use @knowcode/screenshotfetch for ALL screenshot capture (NOT Puppeteer)
Cookie Banner Handling: @knowcode/screenshotfetch automatically blocks cookie consent banners
Implementation: Create capture scripts using ScreenshotCapture class with proper initialization
Verification Step: Use WebFetch tool to verify quote exists on page before capturing screenshot
Storage: Save all images to _images/ subdirectory at same level as markdown file
Naming Convention: Follow pattern [category]-[type]-[number].png (e.g., pricing-complaint-01.png)
URL Documentation: Include exact source URL for every screenshot in markdown
Fallback Strategy: If review sites block automated capture, document URLs for manual verification

1.6 Positive User Experience Research (`research-pleasure-points.md`)

WORD COUNT: Exactly 2,500+ words
VISUAL REQUIREMENTS: 30+ screenshots/images
IMAGE STORAGE: ./docs/01-problem-discovery/_images/pleasure-points/

STRUCTURE REQUIREMENTS:

Section 1: User Success Testimonials (600 words) - Screenshots of positive user reviews and testimonials
Section 2: Feature Appreciation Evidence (500 words) - What users love about current tools
Section 3: Successful Workflow Examples (500 words) - Screenshots of users praising specific workflows
Section 4: Loyalty & Retention Factors (400 words) - Why users stay with platforms
Section 5: Competitive Advantages Analysis (300 words) - Features that create strong differentiation
Section 6: Pleasure Point Synthesis (200 words) - Key patterns from positive research

MANDATORY CONTENT:

30+ screenshots from positive reviews, success stories, and testimonials WITH VERIFIED URLS
Categorized evidence: workflows (8+), features (8+), testimonials (8+), success stories (6+)
Direct quotes showing what users love about existing platforms WITH SOURCE URLS
Evidence of features that create user delight and satisfaction
CRITICAL: ALL testimonials and quotes MUST be real and include the exact URL where found
NO FABRICATED CONTENT: Every quote must be verifiable through WebSearch results
URL VERIFICATION: Include direct links to Reddit posts, forum discussions, review sites
WEBFETCH VERIFICATION: Use WebFetch tool to verify each quote exists on claimed URL before including
EXACT QUOTES ONLY: Never paraphrase, summarize, or modify customer quotes
CUSTOMER NAME VERIFICATION: Include real customer names and companies when available
Screenshots of successful onboarding and user experience examples
Documentation of competitive advantages that users refuse to give up
Cross-reference with pain points to identify improvement opportunities

CAPTURE METHODOLOGY:

MANDATORY TOOL: Use @knowcode/screenshotfetch for ALL screenshot capture (NOT Puppeteer)
Cookie Banner Handling: @knowcode/screenshotfetch automatically blocks cookie consent banners
Verification Protocol: Use WebFetch tool to verify quote exists on page before capturing screenshot
Focus Areas: 4-5 star reviews, positive community discussions, case studies with metrics
Implementation: Create ScreenshotCapture scripts with proper async/await handling
Storage: Save to _images/pleasure-points/ subdirectory at same level as markdown file
Naming Convention: Follow pattern pleasure-[category]-[number].png (e.g., pleasure-workflow-01.png)
URL Documentation: Include exact source URL for every testimonial in markdown
Quality Standards: Only capture screenshots that show verifiable, authentic customer feedback

PHASE 1 COMPLETION CHECKLIST

Before proceeding to Phase 2, Claude Code must verify:

ALL 12 WebSearch queries executed and documented (8 pain + 4 pleasure)
6 markdown files created with exact word counts (15,000+ total words)
Minimum 15 WebSearch citations per document
Specific competitor names referenced (ActiveCampaign, Mailchimp, ConvertKit, Drip)
Reddit communities documented (r/entrepreneur, r/smallbusiness, r/marketing, r/SaaS)
Review sites analyzed (G2.com, Capterra, Trustpilot)
Pricing pain evidence collected and quantified
Feature complexity complaints documented with sources
40+ pain point screenshots captured using @knowcode/screenshotfetch and saved in ./docs/01-problem-discovery/_images/
30+ pleasure point screenshots captured using @knowcode/screenshotfetch and saved in ./docs/01-problem-discovery/_images/pleasure-points/
ALL testimonials verified using WebFetch tool before inclusion
ALL quotes match word-for-word what appears on source pages
ALL source URLs verified as publicly accessible and loading correctly
Real customer names and companies included when available in sources
NO fabricated, paraphrased, or modified testimonials included
Positive user testimonials and success stories documented with verified URLs
Features that create user loyalty and satisfaction identified through verified sources
Cross-referenced pain points with pleasure points for balanced analysis using real data
All images properly categorized with clear naming conventions following [category]-[type]-[number].png pattern
Screenshot capture used @knowcode/screenshotfetch with automatic cookie banner blocking
Cookie consent banners successfully blocked in all captured screenshots
CITATION VERIFICATION: Every statistical claim includes exact WebSearch URL
FACT-CHECK COMPLETE: All market data, competitor info, and user testimonials verified with sources
ZERO UNSOURCED CONTENT: No fabricated claims or unverifiable assertions

PROGRESSION TRIGGER: Phase 1 Complete - Proceed to Phase 2

PHASE 2: MARKET ANALYSIS EXECUTION PROTOCOL

Market Research Context (Built on Phase 1)

Using validated findings from Phase 1 research, now execute comprehensive competitive and market analysis.

# Research Foundation from Phase 1
VALIDATED_PROBLEM: "Email marketing tools are overpriced and feature-bloated for basic automation needs"
TARGET_MARKET: "Small businesses and SaaS companies needing simple email automation"  
PRICE_SENSITIVITY: "Users complaining about $50-300/month costs for basic features"
FEATURE_COMPLEXITY: "Users want drag-and-drop simplicity without advanced CRM features"
COMPETITOR_GAPS: "No affordable, simplified alternative to ActiveCampaign/Mailchimp"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 2

Claude Code Instructions: Execute ALL 12 WebSearch queries below sequentially. Use results to create 5 comprehensive markdown documents. DO NOT PROCEED to Phase 3 until Phase 2 Complete checklist is satisfied.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Competitive Landscape Research

Query 1: "ActiveCampaign competitors" pricing comparison 2024 2025
Query 2: "Mailchimp alternatives" "small business" affordable email marketing
Query 3: "ConvertKit vs Drip vs ActiveCampaign" feature comparison
Query 4: "email marketing tools" market share revenue "industry report"

2. Market Sizing & Industry Analysis

Query 5: "email marketing software market size" 2024 growth projections
Query 6: "small business email marketing" spending budget statistics
Query 7: "SaaS email automation" market segments TAM SAM

3. User Persona & Behavior Research

Query 8: "small business owner" email marketing challenges needs survey
Query 9: "startup marketing automation" user behavior patterns requirements
Query 10: "email marketing ROI" small business case studies results

4. AI Features & Competitive Intelligence Research

Query 11: "ActiveCampaign AI features" machine learning "147 features" automation pricing 2024
Query 12: "Mailchimp vs ConvertKit vs MailerLite" AI features comparison machine learning automation 2024

DELIVERABLE SPECIFICATIONS - CREATE 5 MARKDOWN FILES

After executing ALL 12 WebSearch queries above, create these files with exact specifications:

2.1 Competitive Intelligence Framework (`analysis-competitor-framework.md`)

WORD COUNT: Exactly 3,000+ words
VISUAL REQUIREMENTS: 10+ competitor screenshots
IMAGE STORAGE: ./docs/02-market-analysis/_images/
STRUCTURE REQUIREMENTS:

Section 1: Competitor Landscape Overview (600 words) - Market leaders and challengers analysis
Section 2: Direct Competitors Deep Dive (800 words) - ActiveCampaign, Mailchimp, ConvertKit analysis
Section 3: Indirect Competitors Mapping (400 words) - CRM tools, marketing platforms competing for users
Section 4: Feature Comparison Matrix (600 words) - Comprehensive feature analysis across 8+ competitors
Section 5: Pricing Intelligence Analysis (400 words) - Detailed pricing model comparison
Section 6: Competitive Gap Analysis (200 words) - Opportunities identified through research

IMPLEMENTATION GUIDE: For detailed step-by-step procedures, refer to @docs/private/guides/research/competitor-analysis-guide.md - Systematic competitive intelligence gathering and analysis with SWOT frameworks and market positioning strategies.

MANDATORY CONTENT:

Specific competitors: ActiveCampaign, Mailchimp, ConvertKit, Drip, Klaviyo, GetResponse, AWeber, Constant Contact
Pricing data for each competitor (current 2024/2025 rates) with pricing page screenshots
Feature matrices comparing automation, templates, analytics, integrations
Customer sentiment analysis from G2, Capterra, Trustpilot reviews (capture review screenshots)
Market share data and revenue estimates where available
SWOT analysis for top 5 competitors with WebSearch citations
Visual evidence: competitor homepages, pricing pages, key features

2.2 Market Sizing Analysis (`analysis-market-sizing.md`)

WORD COUNT: Exactly 3,000+ words
STRUCTURE REQUIREMENTS:

Section 1: TAM Calculation Methodology (500 words) - Total addressable market research approach
Section 2: Global Email Marketing Market (600 words) - Industry size, growth, projections to 2027
Section 3: SAM Analysis (600 words) - Serviceable addressable market for small business segment
Section 4: SOM Projections (500 words) - Serviceable obtainable market scenarios (1%, 5%, 10%)
Section 5: Market Growth Indicators (500 words) - Trend analysis and growth drivers
Section 6: Regional Market Breakdown (300 words) - US, EU, global market distribution

MANDATORY CONTENT:

Industry reports: Gartner, Forrester, Statista, Grand View Research citations
Market size figures: $X billion TAM with 2024-2027 CAGR projections
Small business email marketing spending statistics
SaaS email automation market segments and sizing
Growth drivers: remote work, digital transformation, e-commerce growth
Competitive market share distribution and concentration analysis

2.3 User Persona Research (`analysis-user-personas.md`)

WORD COUNT: Exactly 3,000+ words
VISUAL REQUIREMENTS: 5+ persona-related screenshots
IMAGE STORAGE: ./docs/02-market-analysis/_images/
STRUCTURE REQUIREMENTS:

Section 1: Persona Research Methodology (400 words) - Data collection and analysis approach
Section 2: Primary Persona - Small Business Owner (600 words) - Demographics, needs, pain points
Section 3: Secondary Persona - SaaS Marketing Manager (600 words) - Role-specific requirements
Section 4: Tertiary Persona - E-commerce Marketer (600 words) - Industry-specific needs
Section 5: Persona Validation & Insights (500 words) - Cross-persona patterns and differences
Section 6: Decision-Making Framework (300 words) - How personas evaluate and purchase tools

MANDATORY CONTENT:

Demographics: company size, industry, role, budget authority
Workflow patterns: current email marketing processes and tools used
Jobs-to-be-done: specific automation needs and marketing goals
Pain points: frustrations with current tools (price, complexity, features)
Decision criteria: evaluation factors and purchase influencers
Budget constraints: spending patterns and cost sensitivity analysis

2.4 Pricing Strategy Research (`analysis-pricing-research.md`)

WORD COUNT: Exactly 3,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Competitive Pricing Landscape (600 words) - Current market pricing analysis
Section 2: Pricing Model Analysis (600 words) - Per-contact vs flat-rate vs feature-based models
Section 3: Price Sensitivity Research (600 words) - Willingness to pay analysis from user research
Section 4: Value-Based Pricing Opportunities (600 words) - ROI analysis and value perception
Section 5: Pricing Strategy Recommendations (400 words) - Optimal pricing approach based on research
Section 6: Price Testing Framework (200 words) - Methods for validating pricing decisions

MANDATORY CONTENT:

Competitor pricing: ActiveCampaign ($29-$149+), Mailchimp ($10-$300+), ConvertKit ($29-$79+)
Price sensitivity analysis from forum discussions and reviews
Value perception research: what features justify higher pricing
Freemium vs paid model analysis and conversion rate expectations
Enterprise pricing research and small business budget constraints
Price elasticity indicators and optimal price point recommendations

2.5 Comprehensive Competitor Features Matrix (`analysis-competitor-features-matrix.md`)

WORD COUNT: Exactly 3,000+ words
VISUAL REQUIREMENTS: 15+ AI feature screenshots and comparison tables
IMAGE STORAGE: ./docs/02-market-analysis/_images/
STRUCTURE REQUIREMENTS:

Section 1: Matrix Methodology Building on Framework (500 words) - How this builds on analysis-competitor-framework.md findings
Section 2: Comprehensive Feature Grid (800 words) - 5 validated competitors with complete feature analysis
Section 3: AI Features Deep Dive (800 words) - AI capabilities analysis targeting complexity reduction
Section 4: Feature-to-Pain-Point Resolution (400 words) - Direct mapping to Phase 1 pain points and competitor framework gaps
Section 5: Strategic Feature Positioning (300 words) - 30 essential features vs 147 bloat features approach
Section 6: Competitive Feature Advantages (200 words) - Opportunities from competitor framework weaknesses

MANDATORY CONTENT:

Reference Integration: Minimum 15 specific findings from analysis-competitor-framework.md
Competitor Base: ActiveCampaign, Mailchimp, ConvertKit, MailerLite, Brevo (from competitor framework)
AI Feature Categories: Email composition AI, send time optimization, predictive analytics, smart segmentation
Usage Reality Mapping: Which features users actually need vs are forced to pay for (building on framework's <30% usage finding)
Feature-to-Pricing Analysis: How AI features contribute to competitor pricing complexity
Strategic Gaps: AI features that solve Phase 1 pain points but are inaccessible due to pricing
Visual Evidence: Screenshots of AI features interfaces with cost analysis annotations

PHASE 2 COMPLETION CHECKLIST

Before proceeding to Phase 3, Claude Code must verify:

ALL 12 WebSearch queries executed and documented with citations
5 markdown files created with exact word counts (15,000+ total words)
20+ screenshots captured and saved in ./docs/02-market-analysis/_images/
Market size >$10B TAM identified through industry research
8+ specific competitors analyzed with pricing and features (with screenshots)
Comprehensive features matrix created with AI features analysis and cross-references to competitor framework
3 detailed user personas developed from research data
Price sensitivity patterns documented with forum/review evidence
Competitive gaps identified with supporting research citations
Growth projections backed by industry trend analysis
CITATION VERIFICATION: Every competitor analysis claim includes exact WebSearch URL
PRICING DATA VERIFIED: All pricing information sourced from official websites with URLs
MARKET SIZE SOURCED: All market sizing figures include exact research report URLs
USER TESTIMONY VERIFIED: All user quotes include forum/review URLs

PROGRESSION TRIGGER: Phase 2 Complete - Proceed to Phase 3

PHASE 3: SOLUTION DESIGN EXECUTION PROTOCOL

Solution Context (Built on Phase 1-2 Research)

Using validated market research from Phases 1-2, now design specific product solution.

# Research-Validated Insights  
MARKET_SIZE: "$15B+ email marketing software TAM with 12%+ CAGR"
COMPETITIVE_GAPS: "No affordable ($15-50/month), simplified email automation for SMBs"
USER_PRIORITIES: "Drag-and-drop editor, behavioral triggers, affordable pricing"
PRICE_SENSITIVITY: "Users want <$50/month vs ActiveCampaign $149+"
TECHNICAL_PREFERENCES: "Cloud-based, integrations with Shopify/WordPress, mobile-responsive"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 3

Claude Code Instructions: Execute ALL 8 WebSearch queries below sequentially. Use results to create 4 comprehensive markdown documents. DO NOT PROCEED to Phase 4 until Phase 3 Complete checklist is satisfied.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Feature Requirements Research

Query 1: "email marketing software" "must have features" small business requirements
Query 2: "drag and drop email editor" user experience best practices 2024
Query 3: "email automation workflows" small business use cases examples

2. Technical Architecture Research

Query 4: "email marketing platform" technical architecture scalability requirements
Query 5: "email deliverability" best practices infrastructure requirements

3. User Experience Research

Query 6: "email marketing UX design" usability patterns interface examples
Query 7: "simple email automation" user interface complaints preferences
Query 8: "email marketing onboarding" user experience flow examples

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

After executing ALL 8 WebSearch queries above, create these files with exact specifications:

3.1 MVP Product Requirements (`prd-mvp-features.md`)

WORD COUNT: Exactly 3,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Core Feature Definition (600 words) - Must-have features for MVP launch
Section 2: Feature Prioritization Matrix (500 words) - Research-based priority ranking
Section 3: User Stories & Acceptance Criteria (600 words) - Detailed requirements
Section 4: Success Metrics & KPIs (400 words) - Measurable outcomes
Section 5: Non-Features & Scope Exclusions (400 words) - What NOT to build in MVP
Section 6: Competitive Differentiation (500 words) - How features address competitor gaps

MANDATORY CONTENT:

Drag-and-drop email editor specifications with template library
Visual automation workflow builder with behavioral triggers
Contact management with segmentation capabilities
Email analytics dashboard with deliverability tracking
Integration requirements: Shopify, WordPress, Zapier, webhooks
Mobile-responsive design requirements
User stories for 3 personas identified in Phase 2

3.2 UX Design Specification (`design-ux-specification.md`)

WORD COUNT: Exactly 3,000+ words
VISUAL REQUIREMENTS: 15+ wireframe/mockup images
IMAGE STORAGE: ./docs/03-solution-design/_images/
STRUCTURE REQUIREMENTS:

Section 1: User Journey Mapping (600 words) - Complete user flows from signup to campaign
Section 2: Information Architecture (500 words) - Navigation, content organization
Section 3: Interface Design Patterns (600 words) - UI components and interactions
Section 4: Wireframe Specifications (600 words) - Key screen layouts and functionality
Section 5: Accessibility & Usability (400 words) - WCAG compliance and usability standards
Section 6: Mobile Experience Design (400 words) - Responsive design requirements

MANDATORY CONTENT:

Onboarding flow: account setup → template selection → first campaign
Email editor interface: drag-drop components, template library, preview modes
Automation builder: visual workflow canvas, trigger selection, condition logic
Dashboard design: campaign overview, analytics, contact management
Accessibility standards: WCAG 2.1 AA compliance, keyboard navigation
Mobile breakpoints and responsive behavior specifications

3.3 Value Proposition Analysis (`analysis-value-proposition.md`)

WORD COUNT: Exactly 3,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Customer Jobs Analysis (600 words) - What users are trying to accomplish
Section 2: Pain Point Mapping (600 words) - Current frustrations and how to solve them
Section 3: Gain Creation Framework (600 words) - Value delivered beyond solving pain
Section 4: Unique Value Proposition (500 words) - Differentiated positioning statement
Section 5: Competitive Positioning (500 words) - How to position against key competitors
Section 6: Messaging & Communication (200 words) - Key messages for different audiences

MANDATORY CONTENT:

Jobs-to-be-done: nurture leads, increase sales, improve customer retention
Pain relievers: affordable pricing ($25/month vs $149+), simplified interface
Gain creators: faster setup, better deliverability, intuitive automation
UVP: "Professional email automation made simple and affordable"
Positioning vs ActiveCampaign: "80% of functionality at 20% of cost"
Target messaging for small business owners, SaaS marketers, e-commerce

3.4 Technical Feasibility Assessment (`analysis-technical-feasibility.md`)

WORD COUNT: Exactly 3,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Architecture Requirements (600 words) - High-level technical approach
Section 2: Integration Specifications (600 words) - Third-party service requirements
Section 3: Performance & Scalability (500 words) - Technical performance requirements
Section 4: Security & Compliance (500 words) - Data protection and regulatory needs
Section 5: Development Resources (500 words) - Team, timeline, technology stack
Section 6: Technical Risk Assessment (300 words) - Potential challenges and mitigation

MANDATORY CONTENT:

Cloud architecture: AWS/GCP with microservices vs monolith decision
Email delivery infrastructure: SendGrid/Amazon SES integration
Database requirements: contact storage, campaign data, analytics
API integrations: Shopify, WordPress, Zapier, social platforms
Security: encryption, GDPR compliance, data retention policies
Development estimate: 6-month MVP with 4-person team

PHASE 3 COMPLETION CHECKLIST

Before proceeding to Phase 4, Claude Code must verify:

ALL 8 WebSearch queries executed and documented with citations
4 markdown files created with exact word counts (12,000+ total words)
15+ wireframes/mockups created and saved in ./docs/03-solution-design/_images/
MVP features defined with detailed specifications and user stories
UX design includes complete user journey and wireframe specifications
Value proposition clearly differentiates from competitors (ActiveCampaign, Mailchimp)
Technical feasibility confirmed with specific architecture decisions
Integration requirements specified (Shopify, WordPress, Zapier)
Performance and security requirements documented
TECHNICAL SPECS VERIFIED: All technology requirements sourced from official documentation URLs
COMPETITOR FEATURES SOURCED: All feature comparisons include exact competitor website URLs
INTEGRATION DATA VERIFIED: All API capabilities verified from official developer documentation URLs
PERFORMANCE BENCHMARKS SOURCED: All performance claims include exact research/benchmark URLs

PROGRESSION TRIGGER: Phase 3 Complete - Proceed to Phase 4

PHASE 4: TECHNICAL ARCHITECTURE PROMPT

Technical Parameters (After Solution Validation)

# Solution Requirements
MVP_FEATURES: "[List validated through research]"
PERFORMANCE_NEEDS: "[Benchmarks from competitor analysis]"
DATA_MODEL: "[Requirements from workflow research]"
INTEGRATIONS: "[Popular integrations from market research]"
SECURITY_REQUIREMENTS: "[Standards from compliance research]"

# Technical Constraints  
TEAM_SKILLS: "[Languages/frameworks team knows]"
TIMELINE: "[Development timeline]"
BUDGET: "[Infrastructure budget based on competitor analysis]"
SCALE_EXPECTATIONS: "[Users projected from market research]"

Phase 4 Generation Prompt

Design technical architecture for ${MVP_FEATURES} that meets ${PERFORMANCE_NEEDS} and ${SECURITY_REQUIREMENTS}, leveraging ${TEAM_SKILLS} within ${BUDGET} constraints informed by market research.

CITATION REQUIREMENTS: All technical specifications, architecture patterns, performance benchmarks, security standards, and infrastructure recommendations MUST be sourced from WebSearch results with exact URLs. Include links to official documentation, industry reports, and technical case studies.

4.1 Research-Informed System Architecture (`tech-system-architecture.md`)

Create comprehensive architecture:

High-level architecture based on successful competitor patterns
Component breakdown addressing research-identified requirements
Data flow diagrams supporting discovered user workflows
API design principles aligned with integration research
Microservices vs monolith decision informed by scale research
Technology stack justified through competitor technology analysis

4.2 Infrastructure Design from Market Analysis (`tech-infrastructure-design.md`)

Define infrastructure approach:

Cloud provider selection based on competitor infrastructure research
Compute strategy informed by performance benchmark research
Database technology choice validated through market analysis
Caching and CDN strategy based on competitor performance analysis
Monitoring approach aligned with industry best practices research
Disaster recovery requirements from compliance research

4.3 Security Architecture from Research (`tech-security-architecture.md`)

Design security measures:

Authentication model based on user preference research
Data encryption standards from compliance requirement research
API security aligned with industry standard research
GDPR/compliance requirements from regulatory research
Security audit checklist based on industry analysis
Incident response plan informed by competitor incident research

4.4 Development Plan Based on Research (`tech-development-plan.md`)

Create implementation roadmap:

Sprint breakdown informed by competitor development patterns
Technical milestones based on market timeline expectations
Testing strategy aligned with industry standard research
CI/CD pipeline design based on best practice research
Code quality standards from developer community research
Technical debt management informed by competitor analysis

Validation Gate: Before proceeding to Phase 5, ensure you have:

Architecture supports all research-validated features
Infrastructure costs validated through competitor analysis
Security meets research-identified industry standards
Implementation realistic based on market timeline research
Performance meets research-based user expectations

PHASE 5: SECURITY ARCHITECTURE & DESIGN PROMPT

Security Parameters (After Technical Architecture)

# Technical Foundation from Phase 4
SYSTEM_ARCHITECTURE: "[Architecture patterns from research]"
DATA_MODELS: "[Data flows identified from user research]"
INTEGRATION_POINTS: "[APIs and services from market research]"
PERFORMANCE_REQUIREMENTS: "[Benchmarks from competitor analysis]"

# Security Context
THREAT_LANDSCAPE: "[Industry threats from competitor research]"
COMPLIANCE_REQUIREMENTS: "[Regulatory needs from market research]"
USER_EXPECTATIONS: "[Security expectations from user research]"
BUDGET_CONSTRAINTS: "[Security budget informed by cost research]"

Phase 5 Generation Prompt

Design security architecture for ${SYSTEM_ARCHITECTURE} that addresses ${THREAT_LANDSCAPE} and meets ${COMPLIANCE_REQUIREMENTS}, all informed by comprehensive market research and competitor security analysis.

CITATION REQUIREMENTS: All security frameworks, threat assessments, design patterns, and compliance requirements MUST be sourced from WebSearch results with exact URLs. Include links to official security standards, industry reports, and regulatory documentation.

5.1 Research-Based Security Architecture (`security-architecture-design.md`)

Create security foundation based on research:

Security architecture patterns informed by competitor security research
Authentication and authorization design based on user preference research
Data protection strategy aligned with industry standard research
Infrastructure security requirements from cloud provider best practices research
API security framework based on industry vulnerability research
Security monitoring approach informed by security tooling research

5.2 Threat Modeling Analysis (`security-threat-modeling.md`)

Define threat landscape based on research:

Threat modeling methodology based on industry standard research (STRIDE, PASTA)
Attack surface analysis informed by architecture research
Risk assessment framework validated through competitor incident research
Threat actor profiling based on industry security research
Vulnerability assessment aligned with technology stack research
Risk prioritization informed by business impact research

5.3 Security Requirements Specification (`security-requirements-specification.md`)

Specify security requirements based on research:

Functional security requirements from user workflow research
Non-functional security requirements from performance research
Authentication requirements based on user experience research
Data protection requirements from regulatory research
Integration security requirements from third-party service research
Testing and validation requirements from quality assurance research

5.4 Compliance Planning Framework (`security-compliance-planning.md`)

Create compliance strategy based on research:

Regulatory landscape mapping informed by industry analysis
Compliance framework selection based on market research
Audit preparation roadmap aligned with certification research
Documentation requirements from regulatory standard research
Training and awareness plan based on compliance best practice research
Continuous compliance monitoring informed by regulatory research

Validation Gate: Before proceeding to Phase 6, ensure you have:

Security architecture addresses all research-identified threats
Threat model covers all system components and data flows
Security requirements align with user expectations and regulatory needs
Compliance plan meets all regulatory requirements discovered through research
Security design supports business objectives and budget constraints

PHASE 6: BUSINESS MODEL PROMPT

Business Parameters (After Technical Validation)

# Technical Reality
INFRASTRUCTURE_COST: "[Costs benchmarked against competitors]"
DEVELOPMENT_COST: "[Total MVP cost based on market analysis]"
MAINTENANCE_EFFORT: "[Effort estimated from competitor analysis]"
SCALE_LIMITATIONS: "[Technical limits researched from market]"

# Market Reality
VALIDATED_PRICE: "[Price validated through market research]"
MARKET_SIZE: "[TAM/SAM confirmed through research]"
COMPETITOR_PRICING: "[Comprehensive competitor price research]"
SALES_CYCLE: "[B2B/B2C cycles researched from market]"

Phase 5 Generation Prompt

Create a sustainable business model given ${INFRASTRUCTURE_COST} costs researched from market, ${VALIDATED_PRICE} pricing validated through research, targeting ${MARKET_SIZE} market with ${SALES_CYCLE} sales cycle discovered through analysis.

CITATION REQUIREMENTS: All financial projections, market size claims, competitor pricing data, cost structures, and business model assumptions MUST be sourced from WebSearch results with exact URLs. Include links to industry reports, financial filings, and business analysis resources.

5.1 Research-Based Business Model Canvas (`business-model-canvas.md`)

Complete canvas based on research:

Value propositions validated through market research
Customer segments identified through community analysis
Channels discovered through competitor customer acquisition research
Customer relationships modeled on successful competitor patterns
Revenue streams validated through pricing research
Key resources identified through competitor analysis
Key activities based on successful market player research
Key partnerships discovered through industry ecosystem research
Cost structure benchmarked against competitor analysis

5.2 Market-Validated Financial Model (`business-financial-model.md`)

Create 3-year projections based on research:

Revenue projections using market growth data (conservative, realistic, optimistic)
Cost breakdown benchmarked against competitor analysis
Unit economics analysis using industry benchmark research
Break-even analysis informed by market timing research
Funding requirements based on competitor funding pattern research
Key metrics dashboard aligned with industry standard research

5.3 Research-Informed Pricing Strategy (`business-pricing-strategy.md`)

Define pricing approach based on market intelligence:

Pricing model selection validated through competitor analysis
Tier definitions based on user research and competitor gap analysis
Price points justified through willingness-to-pay research
Discounting strategy informed by competitor promotional research
Enterprise pricing approach based on B2B market research
Price increase roadmap aligned with market maturity research

IMPORTANT: Interactive Cost Calculators

When creating business model and pricing strategy documents, always include interactive JavaScript cost calculators to make financial projections tangible and actionable. Follow the pattern established in the content ROI calculator:

When to Create Cost Calculators:

Business Model Canvas - Unit economics calculator showing LTV, CAC, contribution margins
Financial Projections - Revenue forecasting with different growth scenarios
Infrastructure Costs - Cloud cost optimization calculator with scaling scenarios
Headcount Planning - Team scaling cost projector with growth rates by department
Customer Support - Support cost calculator based on ticket volume and automation
Pricing Strategy - Pricing tier comparison calculator showing value at each level

Calculator Implementation Requirements:

Store all calculators in docs/05-business-model/calculators/ directory
Follow the same HTML structure and iframe pattern as content-roi-calculator.html
Include auto-resize functionality for proper iframe embedding
Use consistent visual design with gradient headers and card layouts
Implement real-time calculation updates with 500ms debouncing
Include comprehensive input validation and user-friendly error handling
Provide clear metric cards showing key results (ROI, costs, savings, etc.)
Add comparison tables or charts where multiple scenarios are valuable

CRITICAL: Auto-Resize Implementation Best Practices

Based on real implementation experience, follow these patterns to avoid infinite resize loops:

Calculator HTML Files (*.html in calculators/ directory):
- Each calculator must send its specific ID in postMessage: id: 'calculator-name'
- Use consistent naming: infrastructure-cost-calculator, unit-economics-calculator, etc.
- Include auto-resize script that monitors content changes and sends height updates
- Add buffer pixels to prevent scrollbars: height + 20
Markdown Document Embedding:
- Use consistent iframe wrapper with proper styling
- Set iframe id to match calculator's postMessage ID exactly
- Include min-height: 600px and transition: height 0.3s ease
- NEVER create multiple script tags with window.addEventListener('message')

Single Consolidated Resize Handler (Critical Fix):

<script>
// ONLY ONE SCRIPT TAG AT END OF DOCUMENT
window.addEventListener('message', function(e) {
    if (e.data && e.data.type === 'resize-iframe' && e.data.height) {
        const calculatorIds = ['calc1-id', 'calc2-id', 'calc3-id'];
        const targetId = e.data.id;
        if (targetId && calculatorIds.includes(targetId)) {
            const iframe = document.getElementById(targetId);
            if (iframe) {
                const newHeight = Math.max(600, e.data.height);
                iframe.style.height = newHeight + 'px';
            }
        }
    }
});
</script>

Common Mistakes to Avoid:

Multiple script tags with resize handlers (causes infinite loops)
Mismatched iframe IDs vs calculator postMessage IDs
Missing height buffers (causes content clipping)
Placing resize scripts throughout document instead of consolidating
Not validating calculator ID before resizing (affects wrong iframes)

Calculator Types to Create:

infrastructure-cost-calculator.html - Cloud infrastructure cost optimization with savings opportunities
headcount-cost-calculator.html - Multi-year team scaling projections with department growth rates
support-cost-calculator.html - Customer support cost modeling with automation impact analysis
unit-economics-calculator.html - SaaS unit economics analysis with LTV, CAC, and payback calculations
content-roi-calculator.html - Content marketing ROI with SEO growth projections (already created)

Calculator Integration Examples:

Based on successful implementation, here are the current calculator placements:

business-cost-structure.md - Contains 4 calculators:
- Infrastructure cost optimization (cloud scaling scenarios)
- Headcount planning (3-year team growth projections)
- Support cost modeling (ticket volume vs automation savings)
- Unit economics analysis (LTV/CAC ratios and profitability)
business-pricing-strategy.md - Contains 1 calculator:
- Unit economics calculator (pricing tier impact analysis)
business-growth-strategy.md - Contains 1 calculator:
- Content marketing ROI (content production investment returns)

File Organization Pattern:

docs/05-business-model/
├── calculators/
│   ├── infrastructure-cost-calculator.html
│   ├── headcount-cost-calculator.html
│   ├── support-cost-calculator.html
│   ├── unit-economics-calculator.html
│   └── content-roi-calculator.html
├── business-cost-structure.md          (4 calculators embedded)
├── business-pricing-strategy.md        (1 calculator embedded)
└── business-growth-strategy.md         (1 calculator embedded)

Python to JavaScript Conversion Process:

When converting Python financial models to JavaScript calculators:

Identify Python Code Blocks: Search markdown files for Python classes and functions with financial calculations
Extract Core Logic: Convert Python mathematical operations to JavaScript equivalently
Preserve Variable Names: Maintain consistent naming between Python and JavaScript versions
Add Interactive Elements: Create HTML form inputs for each Python function parameter
Real-time Updates: Implement input event listeners with debouncing for smooth UX
Visual Enhancements: Use Chart.js for data visualization and gradient styling for professional appearance

Replacement Strategy: After creating JavaScript calculators, replace Python code blocks in markdown with iframe embeds:

<div style="background: #f9fafb; border: 1px solid #e5e7eb; border-radius: 8px; padding: 4px; margin: 20px 0;">
    <iframe 
        id="calculator-name"
        src="./calculators/calculator-name.html" 
        width="100%" 
        height="800"
        frameborder="0"
        style="border: none; border-radius: 4px; background: white; transition: height 0.3s ease; min-height: 600px;">
    </iframe>
</div>

Each calculator should convert Python financial models found in markdown documents into interactive JavaScript tools that allow users to experiment with different scenarios and immediately see the financial impact of their decisions.

Calculator Testing and Debugging Protocol:

Development Testing:
- Test each calculator in isolation using test-calculator.html wrapper
- Verify auto-resize functionality works without infinite loops
- Check input validation and edge cases (zero values, negative numbers)
- Ensure chart rendering and responsive design on mobile devices
Integration Testing:
- Embed calculators in actual markdown documents
- Test multiple calculators on same page (business-cost-structure.md has 4)
- Verify only one resize event listener exists per page
- Check console for resize events and height changes
Debugging Common Issues:
- Infinite resize loops: Check for multiple script tags with addEventListener
- Calculator not visible: Verify iframe src path and calculator HTML exists
- Height not updating: Check iframe ID matches calculator postMessage ID
- JavaScript errors: Open browser dev tools and check console for errors
Performance Optimization:
- Use 500ms debouncing on input changes to prevent excessive calculations
- Cache calculation results when inputs haven't changed
- Minimize DOM manipulation during resize operations
- Use ResizeObserver API when available for better performance

Interactive Documentation Standards

Based on the successful implementation of interactive calculators and UI pattern examples, all design and UX documentation should now include live, interactive examples following these standards:

When to Create Interactive Examples

REQUIRED for:

UI Component Patterns - Button states, form interactions, loading animations
User Interface Behaviors - Modal overlays, notification patterns, micro-interactions
Financial/Business Models - Calculators, ROI projections, cost analysis tools
User Experience Flows - Onboarding sequences, workflow demonstrations
Design System Components - Color palettes, typography scales, spacing guides

OPTIONAL for:

Static reference information (documentation, specifications)
Purely informational content without interactive elements
Technical architecture diagrams (unless demonstrating data flow)

Implementation Architecture

File Structure Pattern:

docs/[phase-number]-[section-name]/
├── patterns/                     # Interactive examples directory
│   ├── component-name.html       # Self-contained interactive examples
│   ├── another-pattern.html      # Each with auto-resize functionality
│   └── micro-interactions.html   # Following consistent naming
├── main-document.md              # Primary documentation
└── _images/                      # Supporting static assets

HTML Interactive Example Requirements:

Self-contained: Complete HTML file with embedded CSS and JavaScript
Auto-resize: Implement iframe postMessage height communication
Next.js Compatible: Use vanilla JS patterns that translate to React
Mobile-first: Responsive design with proper touch targets
Accessible: ARIA labels, keyboard navigation, screen reader support

Embedding Standards

Iframe Wrapper Pattern:

<div style="background: #f0f9ff; border: 1px solid #0ea5e9; border-radius: 8px; padding: 4px; margin: 20px 0;">
    <iframe 
        id="unique-pattern-id"
        src="./patterns/pattern-name.html" 
        width="100%" 
        height="800"
        frameborder="0"
        style="border: none; border-radius: 4px; background: white; transition: height 0.3s ease; min-height: 600px;">
    </iframe>
</div>

Consolidated Resize Handler:

<script>
// SINGLE script tag at end of document
window.addEventListener('message', function(e) {
    if (e.data && e.data.type === 'resize-iframe' && e.data.height) {
        const patternIds = ['pattern1-id', 'pattern2-id', 'pattern3-id'];
        const targetId = e.data.id;
        if (targetId && patternIds.includes(targetId)) {
            const iframe = document.getElementById(targetId);
            if (iframe) {
                const newHeight = Math.max(600, e.data.height);
                iframe.style.height = newHeight + 'px';
            }
        }
    }
});
</script>

Visual Design Standards

Color-coded Borders by Category:

UI Components: Blue border (#0ea5e9) with light blue background (#f0f9ff)
Form Patterns: Green border (#22c55e) with light green background (#f0fdf4)
Loading States: Purple border (#a855f7) with light purple background (#faf5ff)
Modals/Overlays: Amber border (#f59e0b) with light amber background (#fffbeb)
Notifications: Red border (#ef4444) with light red background (#fef2f2)
Micro-interactions: Cyan border (#06b6d4) with light cyan background (#ecfeff)

Contextual Descriptions:

Add descriptive callouts before each interactive example
Use action-oriented language: "Try it live", "Experience the interaction", "Test the behavior"
Include brief explanation of what users can do with the example

Technical Implementation

Auto-Resize Communication Protocol:

// In embedded HTML file
function sendHeightToParent() {
    const height = Math.max(
        document.documentElement.scrollHeight,
        document.documentElement.offsetHeight,
        document.body.scrollHeight,
        document.body.offsetHeight
    ) + 20; // Buffer for safe margin
    
    if (window.parent !== window) {
        window.parent.postMessage({
            type: 'resize-iframe',
            height: height,
            id: 'specific-pattern-id' // Must match iframe ID
        }, '*');
    }
}

Integration with Next.js Components:

Include React/Next.js implementation examples alongside interactive demos
Show how to convert vanilla JavaScript patterns to React hooks and components
Provide TypeScript interfaces for props and state management
Include performance optimization notes (debouncing, memoization, lazy loading)

Success Metrics for Interactive Documentation

User Engagement:

Time spent on pages with interactive examples vs. static pages
Click-through rates on interactive elements
Developer adoption of patterns in actual implementations

Implementation Quality:

Consistency of UI patterns across actual product development
Reduction in design system questions and clarifications
Speed of component development using documented patterns

Maintenance Standards:

Update interactive examples when design system changes
Verify examples work across browsers and devices
Keep Next.js integration examples current with latest React patterns

5.4 Market-Driven Growth Model (`business-growth-model.md`)

Design growth engine based on research:

Customer acquisition channels validated through competitor analysis
CAC estimates based on industry benchmark research
LTV calculations using market retention data research
Viral/referral mechanisms discovered through successful competitor analysis
Content marketing strategy informed by competitor content research
Partnership opportunities identified through ecosystem research

Validation Gate: Before proceeding to Phase 6, ensure you have:

Unit economics validated against industry benchmarks through research
CAC < LTV with assumptions validated through market research
Path to profitability realistic based on competitor timeline research
Funding requirements benchmarked against market standards
Growth model sustainable based on competitor success pattern research

PHASE 7: IMPLEMENTATION PLANNING PROMPT

Implementation Parameters (After Business Validation)

# Validated Scope
MVP_FEATURES: "[Final feature list validated through research]"
TECH_STACK: "[Technologies chosen through market analysis]"
TEAM_SIZE: "[Available developers]"
LAUNCH_DATE: "[Target date based on market timing research]"
BUDGET: "[Total budget validated through cost research]"

# Success Criteria
LAUNCH_METRICS: "[Metrics benchmarked against competitor launches]"
QUALITY_STANDARDS: "[Standards researched from industry best practices]"
PERFORMANCE_TARGETS: "[Targets based on competitor performance research]"

Phase 6 Generation Prompt

Create detailed implementation plan for building ${MVP_FEATURES} with ${TEAM_SIZE} team by ${LAUNCH_DATE} within ${BUDGET} budget, all validated through comprehensive market research.

CITATION REQUIREMENTS: All development timelines, resource allocations, project methodologies, risk assessments, and implementation strategies MUST be sourced from WebSearch results with exact URLs. Include links to project management resources, development case studies, and industry best practices.

6.1 Research-Informed Development Roadmap (`implementation-roadmap.md`)

Create sprint-by-sprint plan based on research:

Epic breakdown informed by competitor feature development patterns
Sprint goals aligned with market-validated priorities
Dependency management based on industry best practice research
Risk mitigation strategies discovered through competitor failure analysis
Buffer time allocation based on industry development timeline research
Release planning aligned with market readiness research

6.2 Market-Validated Testing Strategy (`implementation-testing-strategy.md`)

Define quality assurance based on research:

Test pyramid approach validated through industry standard research
Unit test requirements based on competitor quality analysis
Integration test scenarios informed by user workflow research
E2E test automation aligned with industry best practice research
Performance testing benchmarked against competitor standards
Security testing checklist based on industry compliance research

6.3 Research-Based DevOps Plan (`implementation-devops-plan.md`)

Setup development operations informed by research:

Environment setup based on industry standard research
CI/CD pipeline stages aligned with competitor best practices
Deployment strategies validated through market analysis
Monitoring and alerting based on industry benchmark research
Logging and debugging approaches from competitor analysis
Rollback procedures based on industry incident research

6.4 Market-Informed Launch Preparation (`implementation-launch-prep.md`)

Pre-launch checklist based on research:

Infrastructure scaling tests benchmarked against competitor loads
Security audit completion aligned with industry standards research
Documentation readiness based on user expectation research
Support system setup informed by competitor support analysis
Legal compliance check based on regulatory research
Backup and recovery test aligned with industry standard research

Validation Gate: Before proceeding to Phase 7, ensure you have:

Realistic timeline validated through industry development research
All dependencies identified through competitor analysis
Testing strategy comprehensive based on industry standard research
Team aligned on plan validated through project success research
Launch criteria benchmarked against successful competitor launches

PHASE 8: GO-TO-MARKET PROMPT

Launch Parameters (After Implementation Planning)

# Product Reality
LAUNCH_FEATURES: "[Features validated through market research]"
TARGET_AUDIENCE: "[Early adopters identified through community research]"
UNIQUE_VALUE: "[Differentiator validated through competitive analysis]"
PRICING: "[Final pricing validated through market research]"

# Marketing Resources
MARKETING_BUDGET: "[Budget benchmarked against competitor marketing spend]"
CONTENT_READY: "[Content strategy based on competitor content analysis]"
PARTNERSHIPS: "[Partnerships identified through ecosystem research]"
BETA_USERS: "[Beta user strategy based on successful launch research]"

Phase 7 Generation Prompt

Create go-to-market strategy for launching ${LAUNCH_FEATURES} to ${TARGET_AUDIENCE} with ${MARKETING_BUDGET} budget, all informed by comprehensive competitor launch analysis and market research.

CITATION REQUIREMENTS: All marketing strategies, launch tactics, channel effectiveness data, budget allocations, and competitive positioning MUST be sourced from WebSearch results with exact URLs. Include links to marketing case studies, industry launch analyses, and promotional strategy resources.

7.1 Research-Based Launch Strategy (`marketing-launch-strategy.md`)

Define launch approach based on market intelligence:

Soft launch vs public launch decision informed by competitor analysis
Beta to GA transition plan based on successful launch research
Press release and PR strategy validated through media analysis
Launch day activities based on competitor launch research
First week/month goals benchmarked against industry standards
Success metrics aligned with competitor launch performance research

7.2 Market-Validated Content Marketing Plan (`marketing-content-plan.md`)

Create content strategy based on research:

SEO keyword research using competitor content gap analysis
Blog post calendar based on competitor content performance research
Documentation plan informed by user expectation research
Video/demo scripts based on successful competitor content analysis
Social media strategy validated through platform research
Email sequences based on competitor marketing automation research

7.3 Research-Informed Customer Acquisition Plan (`marketing-acquisition-plan.md`)

Design acquisition funnel based on market research:

Channel prioritization based on competitor acquisition channel research
Channel-specific strategies validated through competitor success analysis
Referral program design based on successful competitor program research
Partnership activation informed by ecosystem research
Community building plan based on competitor community success research
Paid acquisition testing strategy informed by competitor ad research

7.4 Market-Benchmarked Analytics Implementation (`marketing-analytics-setup.md`)

Setup measurement based on industry research:

KPI dashboard design aligned with competitor metric research
Event tracking plan based on industry standard research
Conversion funnel setup informed by competitor funnel analysis
Attribution model validated through industry best practice research
Reporting cadence based on competitor reporting research
Optimization process informed by successful competitor optimization research

PROGRESSIVE DOCUMENTATION APPROACH

How Research-Based Documentation Builds Over Time

Phase 1 Output (Week 1)

Digital problem discovery plan
Online research methodology guide
Problem statement validation template
Market signals research framework

Phase 2 Output (Week 2)

Competitive intelligence analysis
Market sizing through digital research
Digital user persona development
Pricing intelligence analysis

Phase 3 Output (Week 3)

Research-informed MVP requirements
UX specifications from research
Value proposition from market intelligence
Technical feasibility through research

Phase 4 Output (Week 4)

Research-informed system architecture
Infrastructure design from market analysis
Security architecture from research
Development plan based on research

Phase 5 Output (Week 5)

Research-based business model canvas
Market-validated financial projections
Research-informed pricing strategy
Market-driven growth model

Phase 6 Output (Week 6)

Research-informed development roadmap
Market-validated testing strategy
Research-based DevOps plan
Market-informed launch preparation

Phase 7 Output (Week 7)

Research-based launch strategy
Market-validated content plan
Research-informed acquisition plan
Market-benchmarked analytics setup

Meta-Documentation

Decision Log (`decisions/decision-log.md`)

Track all major decisions with research backing:

Date and research context
Options discovered through market analysis
Decision made based on research findings
Rationale supported by market intelligence
Success criteria benchmarked against competitors

Research Validation Tracker (`research/validation-tracker.md`)

Document research findings and validation:

Research hypothesis
Validation methodology (digital research technique used)
Current status and confidence level
Sources and data quality assessment
Impact if research proves incorrect
Additional research required

Market Intelligence Repository (`research/market-intelligence.md`)

Capture research insights:

Competitive intelligence discoveries
Market trend insights from search and social data
User behavior patterns from forum and review analysis
Technology trends from industry research
Regulatory and compliance insights
Failed research paths and lessons learned

Using This Research-Based Template Effectively

Comprehensive Digital Research: Use multiple research methodologies to triangulate findings
Validate Through Multiple Sources: Confirm insights across platforms and communities
Document Research Sources: Maintain detailed source tracking for validation
Stay Current: Research markets change rapidly, update findings regularly
Focus on User Signals: Every decision should be supported by observable user behavior online

Conclusion

This research-based approach ensures you:

Build solutions validated by comprehensive market intelligence
Understand competitive landscape through systematic analysis
Create documentation reflecting real market conditions
Maintain agility based on continuous market monitoring
Reduce risk through research-driven validation at each stage

Remember: The goal isn't to follow the research process perfectly, but to increase your odds of building something people want and will pay for based on comprehensive market intelligence and competitive analysis.

PHASE 10: UI/UX WIREFRAMES & MOCKUP SYSTEM

Context (Building on Phases 1-9)

With validated market research, user personas, technical architecture, and business model complete, create comprehensive wireframe system that translates research insights into actionable interface designs.

# Research Foundation from Previous Phases
MVP_FEATURES: "Validated feature set from Phase 3"
USER_PERSONAS: "Target user types and pain points from Phase 2"
TECHNICAL_CONSTRAINTS: "Architecture decisions from Phase 4"
DESIGN_PARADIGM: "Interface approach validated in earlier phases"
BRAND_STRATEGY: "Visual positioning from competitor analysis"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 10

Claude Code Instructions: Create a comprehensive wireframe system with 7-20 high-quality SVG wireframes and supporting documentation that reflects the specific product insights discovered in Phases 1-9.

WIREFRAME SCOPE DETERMINATION

Dynamic Scope Based on Product Complexity:

7 Wireframes Minimum: Core user flows (onboarding, main interface, key actions)
20 Wireframes Maximum: Complex products with multiple user types and workflows
Scope Factors: Number of MVP features, user types, interface complexity from Phase 3

SVG WIREFRAME TECHNICAL STANDARDS

Universal Technical Requirements

Desktop ViewBox: viewBox="0 0 1440 900" for consistent desktop wireframes
Mobile Optimization: Responsive design with minimum 44px (iOS) / 48px (Android) touch targets
Color System: Consistent hex palette reflecting brand strategy
Typography: SF Pro Display or system fonts for cross-platform compatibility
Animation Framework: CSS animations for loading states, transitions, interactions
File Organization: _images/wireframes/ directory with sequential naming (01-main-interface.svg, 02-onboarding.svg, etc.)
Image Link Format: Use relative paths _images/wireframes/filename.svg (no leading slash) for markdown image references

Adaptive Design Architecture

Header Standards: Logo + primary navigation + user account (consistent 60px height)
Content Layout: Flexible grid system adapting to product needs (sidebar, full-width, dashboard)
Footer Elements: Context-appropriate actions (forms, CTAs, navigation)
Responsive Breakpoints: Mobile-first approach with tablet and desktop variants

Interface Paradigm Integration

Apply the specific design approach validated in earlier phases:

Traditional UI: Forms, menus, standard web patterns
AI-First/Conversational: Chat interfaces, voice input, natural language
Dashboard-Heavy: Metrics, analytics, data visualization
Mobile-First: Touch-optimized, gesture-based navigation
E-commerce: Product-focused, conversion-optimized flows

DELIVERABLE SPECIFICATIONS - CREATE 9 MARKDOWN FILES

10.1 Wireframe Overview Gallery (`overview-mockups.md`)

PURPOSE: Visual gallery document displaying all generated wireframe SVG files
WORD COUNT: 500-1,000 words (brief descriptions, not lengthy narrative)
STRUCTURE REQUIREMENTS:

Introduction: Overview of wireframe system and design approach (200 words)
Wireframe Gallery: Grid layout showing all SVG wireframes with titles (600 words)
Design Rationale: Brief explanation of how wireframes reflect Phase 1-9 insights (200 words)

MANDATORY CONTENT:

Embedded display of all generated SVG wireframes
Brief description of functionality for each wireframe
Logical organization from onboarding → main features → advanced functionality
Integration summary showing how earlier research influenced design decisions

10.2 Primary Interface Wireframes (`wireframe-dashboard-overview.md`)

WORD COUNT: Exactly 2,500+ words
SVG REQUIREMENTS: 2-4 wireframes showing main application interface
STRUCTURE REQUIREMENTS:

Section 1: Main Interface Design (600 words) - Primary user dashboard/workspace
Section 2: Navigation Architecture (500 words) - Menu structure and information hierarchy
Section 3: Layout Responsive Behavior (400 words) - Mobile/tablet/desktop adaptations
Section 4: User Persona Integration (400 words) - How interface serves different user types
Section 5: Feature Access Patterns (400 words) - How users access core MVP features
Section 6: Performance Considerations (200 words) - Load time and interaction optimization

10.3 User Onboarding Experience (`wireframe-onboarding-experience.md`)

WORD COUNT: Exactly 2,500+ words
SVG REQUIREMENTS: 2-3 wireframes showing complete onboarding flow
STRUCTURE REQUIREMENTS:

Section 1: First-Time User Journey (600 words) - Account creation to first value
Section 2: Progressive Disclosure Strategy (500 words) - Feature introduction sequence
Section 3: Setup Wizard Design (500 words) - Guided configuration process
Section 4: Empty State Handling (400 words) - Zero-data experience design
Section 5: Success Milestone Tracking (300 words) - User achievement progression
Section 6: Accessibility Compliance (200 words) - WCAG 2.1 AA standards

10.4 Core Feature Workflows (`wireframe-campaign-creation.md`, `wireframe-automation-builder.md`, `wireframe-contact-management.md`, `wireframe-analytics-reporting.md`)

WORD COUNT: Exactly 2,500+ words each
SVG REQUIREMENTS: 1-2 wireframes per file showing specific feature interfaces
STRUCTURE REQUIREMENTS (per file):

Section 1: Feature Interface Design (600 words) - Main interaction patterns
Section 2: User Task Flow (500 words) - Step-by-step workflow completion
Section 3: Data Input/Output Patterns (400 words) - Forms, displays, interactions
Section 4: Error Handling & Validation (400 words) - Edge cases and user guidance
Section 5: Mobile Adaptation (400 words) - Touch-optimized feature access
Section 6: Integration Touchpoints (200 words) - How feature connects to others

NOTE: Create 3-5 feature wireframe files based on MVP feature complexity from Phase 3

10.5 Information Architecture (`information-architecture.md`)

WORD COUNT: Exactly 2,500+ words
IMPLEMENTATION GUIDE: For detailed step-by-step procedures, refer to @docs/private/guides/design/information-architecture-guide.md - Systematic IA design and user mental model research with card sorting and navigation optimization techniques.

STRUCTURE REQUIREMENTS:

Section 1: Content Organization Strategy (600 words) - Information hierarchy and grouping
Section 2: Navigation Design Patterns (500 words) - Menu structures and user pathways
Section 3: Search and Discovery (400 words) - Content findability mechanisms
Section 4: User Mental Models (400 words) - Aligning interface with user expectations
Section 5: Content Prioritization (400 words) - Feature prominence and accessibility
Section 6: Scalability Considerations (200 words) - Growth accommodation in IA

10.6 Interaction Design Patterns (`interaction-design-patterns.md`)

WORD COUNT: Exactly 2,500+ words
STRUCTURE REQUIREMENTS:

Section 1: Interface Interaction Standards (600 words) - Click, hover, touch patterns
Section 2: Form Design and Validation (500 words) - Input handling and user feedback
Section 3: Loading States and Transitions (400 words) - Micro-interactions and animations
Section 4: Feedback and Notification Systems (400 words) - Success, error, and info messaging
Section 5: Accessibility Interaction Design (400 words) - Keyboard navigation and screen readers
Section 6: Performance Optimization (200 words) - Efficient interaction implementation

QUALITY ASSURANCE FRAMEWORK

SVG Validation Requirements

Code Quality: Clean, optimized SVG markup with proper structure
Responsive Design: Scalable layouts that work across all device sizes
Accessibility: WCAG 2.1 AA compliance with proper alt text and structure
Brand Consistency: Aligned with visual strategy and design paradigm
Performance: Optimized file sizes and efficient rendering

Phase Integration Validation

Research Alignment: Wireframes directly address pain points identified in Phase 1-2
Feature Coverage: All MVP features from Phase 3 are wireframed appropriately
User Journey Support: Complete workflows for all primary user personas
Technical Feasibility: Designs align with architecture decisions from Phase 4
Business Model Integration: Interface supports monetization strategy from Phase 6

PHASE 10 COMPLETION CHECKLIST

Before proceeding to Phase 11:

7-20 high-quality SVG wireframes created based on product complexity
All SVG files saved in _images/wireframes/ directory with sequential naming
9 comprehensive markdown files created (22,500+ total words)
Overview gallery document displays all wireframes visually
Wireframes directly reflect insights from Phases 1-9 research
Design paradigm consistently applied across all wireframes
All MVP features from Phase 3 are adequately wireframed
Mobile responsiveness designed with appropriate touch targets
Accessibility compliance verified (WCAG 2.1 AA standards)
Information architecture supports user mental models from persona research
Interaction patterns align with user preferences discovered in earlier phases

PROGRESSION TRIGGER: Phase 10 Complete - Proceed to Phase 11

PHASE 11: VISUAL COMPETITOR ANALYSIS & UI/UX RESEARCH

Context (Building on Phases 1-9 Research)

With validated market research, user personas, and technical specifications complete, now conduct visual analysis of competitor interfaces and UI/UX patterns to inform design decisions.

# Research Foundation from Previous Phases
VALIDATED_COMPETITORS: "ActiveCampaign, Mailchimp, ConvertKit, Drip, Klaviyo"
USER_PRIORITIES: "Intuitive interface, drag-and-drop simplicity, visual automation"
DESIGN_GOALS: "Reduce complexity while maintaining professional capabilities"
TARGET_USERS: "Small businesses, SaaS marketers, e-commerce owners"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 10

Claude Code Instructions: Execute ALL 10 WebSearch queries below. Use @knowcode/imgfetch tool to capture competitor screenshots. Create 4 comprehensive markdown documents with visual examples.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. UI Pattern Research

Query 1: "ActiveCampaign interface" screenshots user experience review 2024
Query 2: "Mailchimp email editor" drag drop interface examples
Query 3: "ConvertKit automation builder" visual workflow screenshots
Query 4: "email marketing UX best practices" interface design patterns

2. Design System Research

Query 5: "email marketing dashboard design" UI patterns examples
Query 6: "SaaS onboarding flow" best practices email marketing
Query 7: "email template builder" interface comparison screenshots

3. User Feedback on Design

Query 8: "email marketing tool" interface complaints "too complex"
Query 9: "simple email automation" UI preferences user feedback
Query 10: "email marketing mobile interface" responsive design examples

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

8.1 Visual Competitor UI Analysis (`analysis-competitor-ui-patterns.md`)

WORD COUNT: Exactly 3,500+ words
VISUAL REQUIREMENTS: 15+ competitor screenshots with annotations

STRUCTURE REQUIREMENTS:

Section 1: Competitor Interface Audit (800 words) - Screenshot analysis of top 5 competitors
Section 2: Email Editor Comparison (700 words) - Side-by-side editor interface analysis
Section 3: Automation Builder Patterns (700 words) - Visual workflow interface analysis
Section 4: Dashboard & Analytics Design (600 words) - Data visualization approaches
Section 5: Mobile Experience Analysis (400 words) - Responsive design patterns
Section 6: Design Pattern Synthesis (300 words) - Common patterns and opportunities

MANDATORY CONTENT:

Screenshots from ActiveCampaign, Mailchimp, ConvertKit, Drip, Klaviyo
Annotated interface elements highlighting pain points
Side-by-side comparisons of key features
Mobile vs desktop interface analysis
Color schemes, typography, spacing patterns
Navigation structures and information architecture

8.2 UX Flow Documentation (`design-ux-flows-visual.md`)

WORD COUNT: Exactly 3,500+ words
VISUAL REQUIREMENTS: 10+ user flow diagrams with screenshots

STRUCTURE REQUIREMENTS:

Section 1: Onboarding Flow Analysis (700 words) - Competitor onboarding screenshot walkthroughs
Section 2: Campaign Creation Flows (700 words) - Step-by-step interface analysis
Section 3: Automation Setup Patterns (700 words) - Visual workflow creation analysis
Section 4: Contact Management Interfaces (600 words) - List and segment UI patterns
Section 5: Analytics & Reporting Flows (500 words) - Data presentation approaches
Section 6: Flow Optimization Opportunities (300 words) - Simplification recommendations

8.3 Design System Recommendations (`design-system-components.md`)

WORD COUNT: Exactly 3,500+ words
VISUAL REQUIREMENTS: 20+ component mockups and examples

STRUCTURE REQUIREMENTS:

Section 1: Component Library Definition (700 words) - Buttons, forms, cards, modals
Section 2: Color & Typography System (600 words) - Based on competitor analysis
Section 3: Layout Grid & Spacing (600 words) - Responsive design framework
Section 4: Interactive Elements (700 words) - Drag-drop, tooltips, animations
Section 5: Accessibility Standards (500 words) - WCAG compliance in design
Section 6: Design Token Specifications (400 words) - Systematic design values

8.4 Visual Brand Strategy (`design-brand-visual-strategy.md`)

WORD COUNT: Exactly 3,500+ words
VISUAL REQUIREMENTS: 15+ mood boards and style examples

STRUCTURE REQUIREMENTS:

Section 1: Competitive Visual Positioning (700 words) - How competitors present visually
Section 2: Brand Personality Definition (600 words) - Visual tone and messaging
Section 3: Logo & Identity Concepts (600 words) - Based on market positioning
Section 4: Marketing Site Design (700 words) - Homepage and conversion patterns
Section 5: Product Interface Alignment (500 words) - Consistency between marketing/product
Section 6: Visual Differentiation Strategy (400 words) - Standing out in the market

PHASE 8 COMPLETION CHECKLIST

Before proceeding to Phase 9:

ALL 10 WebSearch queries executed with visual results
4 markdown files created (14,000+ total words)
60+ screenshots captured using @knowcode/imgfetch
Competitor interfaces analyzed and annotated
Design patterns documented with visual examples
UX flows mapped with screenshot sequences
Design system components specified
Visual differentiation strategy defined

PHASE 12: DETAILED FEATURE SPECIFICATIONS & TECHNICAL PRD

Context (Building on Phases 1-10)

With visual competitor analysis complete, create detailed technical specifications and comprehensive PRD for MVP development.

# Foundation from Previous Research
MVP_FEATURES: "Validated feature set from Phase 3"
UI_PATTERNS: "Best practices identified in Phase 8"
TECHNICAL_ARCHITECTURE: "Defined in Phase 4"
USER_STORIES: "Developed from persona research"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 13

Claude Code Instructions: Execute ALL 8 WebSearch queries below. Create 4 comprehensive technical specification documents.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Technical Specification Research

Query 1: "email marketing API" technical documentation examples best practices
Query 2: "drag drop editor" technical implementation React Vue
Query 3: "email automation engine" architecture patterns workflows
Query 4: "email deliverability" technical requirements SPF DKIM

2. Feature Implementation Research

Query 5: "contact segmentation" database schema design patterns
Query 6: "email template system" technical architecture multi-tenant
Query 7: "real-time analytics" email marketing technical stack
Query 8: "webhook system" event-driven architecture email platform

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

9.1 Technical Product Requirements (`prd-technical-specifications.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: API Specification (800 words) - RESTful API design for all features
Section 2: Data Model Definition (800 words) - Complete database schema
Section 3: Integration Architecture (700 words) - Third-party service specifications
Section 4: Performance Requirements (700 words) - Load, speed, scalability specs
Section 5: Security Specifications (600 words) - Authentication, encryption, compliance
Section 6: Technical Constraints (400 words) - Limitations and boundaries

9.2 Feature Implementation Guide (`prd-feature-implementation.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Email Editor Specifications (800 words) - Drag-drop implementation details
Section 2: Automation Engine Design (800 words) - Workflow execution architecture
Section 3: Contact Management System (700 words) - Segmentation and list logic
Section 4: Analytics Implementation (700 words) - Tracking and reporting specs
Section 5: Template System Architecture (600 words) - Storage and rendering
Section 6: Delivery Infrastructure (400 words) - Email sending specifications

9.3 User Story Specifications (`prd-user-stories-detailed.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Epic Breakdown (800 words) - High-level feature epics
Section 2: User Story Details (800 words) - Acceptance criteria for each story
Section 3: Edge Cases & Error Handling (700 words) - Comprehensive scenarios
Section 4: User Flow Specifications (700 words) - Detailed interaction patterns
Section 5: Accessibility Requirements (600 words) - WCAG compliance specs
Section 6: Localization Considerations (400 words) - Multi-language support

9.4 Testing & Quality Specifications (`prd-testing-specifications.md`)

WORD COUNT: Exactly 4,000+ words
IMPLEMENTATION GUIDE: For detailed step-by-step procedures, refer to @docs/private/guides/development/testing-framework-guide.md - Comprehensive testing implementation following testing pyramid methodology with Jest, React Testing Library, and Cypress E2E testing.

STRUCTURE REQUIREMENTS:

Section 1: Test Strategy Overview (800 words) - Comprehensive testing approach
Section 2: Unit Test Requirements (700 words) - Coverage and standards
Section 3: Integration Test Scenarios (700 words) - API and service testing
Section 4: E2E Test Specifications (700 words) - User journey testing
Section 5: Performance Test Plans (600 words) - Load and stress testing
Section 6: Security Test Requirements (500 words) - Penetration testing specs

9.5 Data Migration & Import Specifications (`prd-migration-specifications.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Migration Strategy Overview (800 words) - Competitor platform migration approach
Section 2: CSV Import Specifications (700 words) - Contact list import with field mapping
Section 3: API Migration Tools (700 words) - ActiveCampaign, Mailchimp API connectors
Section 4: Campaign Template Conversion (700 words) - Email template migration
Section 5: Automation Workflow Import (600 words) - Converting competitor workflows
Section 6: Data Validation & Cleanup (500 words) - Ensuring data integrity

9.6 Email Deliverability Infrastructure (`prd-deliverability-specifications.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Deliverability Architecture (800 words) - SPF, DKIM, DMARC setup
Section 2: IP Warming Strategy (700 words) - Gradual sending volume increase
Section 3: Bounce Handling System (700 words) - Hard/soft bounce management
Section 4: Spam Score Optimization (700 words) - Content analysis and scoring
Section 5: Reputation Monitoring (600 words) - Blacklist monitoring, sender score
Section 6: ISP Relationship Management (500 words) - Feedback loops, whitelisting

9.7 Compliance & Legal Framework (`prd-compliance-specifications.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: GDPR Compliance (800 words) - Data protection, consent management
Section 2: CAN-SPAM Requirements (700 words) - US email law compliance
Section 3: CASL Implementation (700 words) - Canadian anti-spam legislation
Section 4: Consent Management System (700 words) - Double opt-in, preference centers
Section 5: Data Retention Policies (600 words) - Storage limits, deletion procedures
Section 6: Privacy & Legal Documentation (500 words) - Terms, privacy policy, DPA

9.8 Performance Benchmarks & SLAs (`prd-performance-specifications.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Performance Targets (800 words) - Load times, response times
Section 2: Email Send Speed (700 words) - Throughput benchmarks vs competitors
Section 3: Dashboard Performance (700 words) - Analytics loading, real-time updates
Section 4: API Response Times (700 words) - Endpoint performance requirements
Section 5: Uptime Commitments (600 words) - 99.9% SLA specifications
Section 6: Scalability Metrics (500 words) - Growth handling capabilities

PHASE 13: UX/UI DESIGN & MOCKUPS

Context (Building on Phases 1-11)

Transform research and specifications into concrete design mockups and interactive prototypes.

# Design Foundation
UI_PATTERNS: "Best practices from Phase 10 visual analysis"
USER_FLOWS: "Optimized flows from competitor research"
BRAND_STRATEGY: "Visual positioning from Phase 8"
SPECIFICATIONS: "Detailed requirements from Phase 9"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 10

Claude Code Instructions: Execute ALL 8 WebSearch queries below. Create 4 comprehensive design documents with mockup descriptions.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Design Tool Research

Query 1: "email marketing mockups" Figma Sketch design examples
Query 2: "SaaS dashboard design" templates mockups best practices
Query 3: "drag drop interface" design patterns mockup examples
Query 4: "email builder UI" design mockups templates

2. Interaction Design Research

Query 5: "micro-interactions" SaaS design animation examples
Query 6: "empty states" design patterns email marketing
Query 7: "responsive design" email marketing mobile first
Query 8: "design handoff" developer specifications documentation

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

10.1 High-Fidelity Mockup Specifications (`design-mockups-specifications.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Dashboard Mockups (800 words) - Main dashboard and navigation
Section 2: Email Editor Mockups (800 words) - Drag-drop interface designs
Section 3: Automation Builder Mockups (700 words) - Visual workflow interface
Section 4: Contact Management Mockups (700 words) - Lists and segments UI
Section 5: Analytics View Mockups (600 words) - Reports and insights
Section 6: Mobile Responsive Mockups (400 words) - Key mobile screens

10.2 Interactive Prototype Plan (`design-prototype-specifications.md`)

WORD COUNT: Exactly 4,000+ words
IMPLEMENTATION GUIDE: For detailed step-by-step procedures, refer to @docs/private/guides/design/prototyping-workflow-guide.md - Interactive prototype creation and testing procedures with Figma prototyping, A/B testing frameworks, and user validation methodologies.

STRUCTURE REQUIREMENTS:

Section 1: Prototype Scope (800 words) - What to prototype and why
Section 2: Key Interactions (800 words) - Click-through specifications
Section 3: Animation & Transitions (700 words) - Micro-interaction details
Section 4: User Testing Scenarios (700 words) - Prototype testing plan
Section 5: Responsive Behaviors (600 words) - Breakpoint specifications
Section 6: Handoff Documentation (400 words) - Designer to developer specs

10.3 Design Pattern Library (`design-pattern-library.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Form Patterns (800 words) - Input, validation, submission
Section 2: Navigation Patterns (700 words) - Menu, breadcrumbs, tabs
Section 3: Data Display Patterns (700 words) - Tables, charts, cards
Section 4: Feedback Patterns (700 words) - Alerts, toasts, modals
Section 5: Empty State Patterns (600 words) - Onboarding and zero-data
Section 6: Loading & Error Patterns (500 words) - States and messages

10.4 Accessibility Design Guide (`design-accessibility-guide.md`)

WORD COUNT: Exactly 4,000+ words
IMPLEMENTATION GUIDE: For detailed step-by-step procedures, refer to @docs/private/guides/design/accessibility-implementation-guide.md - WCAG 2.1 AA compliance implementation procedures with color contrast validation, keyboard navigation, and ARIA patterns.

STRUCTURE REQUIREMENTS:

Section 1: Color & Contrast Standards (800 words) - WCAG AA compliance
Section 2: Keyboard Navigation Design (700 words) - Focus states and tab order
Section 3: Screen Reader Optimization (700 words) - ARIA labels and structure
Section 4: Touch Target Guidelines (700 words) - Mobile accessibility
Section 5: Cognitive Load Reduction (600 words) - Simplification strategies
Section 6: Testing & Validation (500 words) - Accessibility testing plan

10.5 Onboarding Flow & Tutorial Design (`design-onboarding-flows.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: First-Time User Experience (800 words) - Account setup to first campaign
Section 2: Interactive Product Tours (700 words) - Guided walkthroughs with tooltips
Section 3: Progressive Disclosure (700 words) - Feature introduction strategy
Section 4: Video Tutorial Specifications (700 words) - Embedded help content
Section 5: Contextual Help System (600 words) - In-app assistance design
Section 6: Success Milestones (500 words) - User achievement tracking

10.6 Email Template Gallery Design (`design-template-gallery.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Template Categories (800 words) - Industry-specific organization
Section 2: Template Preview System (700 words) - Thumbnail and live preview design
Section 3: Customization Interface (700 words) - Template editing workflow
Section 4: Template Search & Filter (700 words) - Discovery mechanisms
Section 5: Template Ratings & Reviews (600 words) - Community feedback system
Section 6: Template Import/Export (500 words) - Sharing and distribution

PHASE 14: DESIGN SYSTEM & COMPONENT LIBRARY

Context (Building on Phases 1-12)

Create comprehensive design system and reusable component library for consistent MVP implementation.

# Design Foundation
MOCKUPS: "High-fidelity designs from Phase 10"
PATTERNS: "UI patterns from competitor analysis"
BRAND: "Visual strategy defined in Phase 8"
TECHNICAL_STACK: "Frontend framework from Phase 4"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 13

Claude Code Instructions: Execute ALL 8 WebSearch queries below. Create 4 comprehensive design system documents.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Design System Research

Query 1: "design system" SaaS companies examples documentation
Query 2: "component library" React Vue best practices 2024
Query 3: "design tokens" system typography color spacing
Query 4: "Storybook" component documentation examples

2. Implementation Research

Query 5: "CSS-in-JS" design system implementation patterns
Query 6: "component testing" visual regression Chromatic
Query 7: "design system versioning" maintenance best practices
Query 8: "component API design" props interface documentation

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

13.1 Design System Architecture (`design-system-architecture.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Design Token Structure (800 words) - Colors, typography, spacing, shadows
Section 2: Component Hierarchy (800 words) - Atomic design methodology
Section 3: Theming Architecture (700 words) - Light/dark mode support
Section 4: Responsive Framework (700 words) - Breakpoints and grid system
Section 5: Animation Standards (600 words) - Transitions and interactions
Section 6: Documentation Standards (400 words) - Component documentation

13.2 Core Component Specifications (`design-system-components.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Form Components (800 words) - Inputs, selects, checkboxes
Section 2: Layout Components (700 words) - Grid, container, spacer
Section 3: Navigation Components (700 words) - Nav, tabs, breadcrumbs
Section 4: Feedback Components (700 words) - Alerts, toasts, modals
Section 5: Data Components (600 words) - Tables, lists, cards
Section 6: Utility Components (500 words) - Tooltips, popovers, badges

13.3 Component Implementation Guide (`design-system-implementation.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Development Setup (800 words) - Tooling and environment
Section 2: Component API Design (700 words) - Props and interfaces
Section 3: Styling Methodology (700 words) - CSS-in-JS approach
Section 4: Testing Strategy (700 words) - Unit and visual tests
Section 5: Documentation Approach (600 words) - Storybook setup
Section 6: Versioning & Distribution (500 words) - NPM publishing

13.4 Design System Governance (`design-system-governance.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Contribution Guidelines (800 words) - How to add components
Section 2: Review Process (700 words) - Design and code review
Section 3: Deprecation Strategy (700 words) - Handling breaking changes
Section 4: Adoption Playbook (700 words) - Team onboarding
Section 5: Maintenance Schedule (600 words) - Update cycles
Section 6: Success Metrics (500 words) - Measuring adoption

13.5 Email Template Components (`design-system-email-components.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Email Building Blocks (800 words) - Headers, footers, content blocks
Section 2: Responsive Email Patterns (700 words) - Mobile-first email design
Section 3: Dynamic Content Components (700 words) - Personalization tokens, conditionals
Section 4: Email Typography System (700 words) - Web-safe fonts, fallbacks
Section 5: Email-Safe Colors (600 words) - Dark mode support, accessibility
Section 6: Testing Framework (500 words) - Email client compatibility

13.6 Automation Visual Elements (`design-system-automation-components.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Workflow Node Library (800 words) - Triggers, actions, conditions
Section 2: Connection Patterns (700 words) - Visual flow connectors, paths
Section 3: State Visualization (700 words) - Active, paused, error states
Section 4: Drag-Drop Interactions (700 words) - Canvas manipulation patterns
Section 5: Workflow Templates UI (600 words) - Pre-built automation displays
Section 6: Performance Indicators (500 words) - Real-time execution feedback

PHASE 15: MVP IMPLEMENTATION WITH CLAUDE CODE

Context (Building on Phases 1-13)

Execute actual MVP implementation using Claude Code prompts to transform designs and specifications into working software. This phase focuses on hands-on development rather than documentation, providing specific executable instructions for building the email marketing platform.

# Implementation Foundation from Previous Phases
DESIGN_SYSTEM: "Component library from Phase 13"
UI_MOCKUPS: "High-fidelity designs from Phase 12"
WIREFRAMES: "UI/UX specifications from Phase 9"
TECHNICAL_ARCHITECTURE: "System design from Phase 4"
FEATURE_SPECIFICATIONS: "Detailed PRDs from Phase 11"
IMPLEMENTATION_TARGET: "Working MVP with core email marketing features"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 14

Claude Code Instructions: Execute ALL 8 WebSearch queries below sequentially for implementation research. Use results to create 4 comprehensive implementation guides with executable Claude Code prompts. CRITICAL: Each guide must contain working Claude Code prompts that produce actual implemented code, not just documentation. DO NOT PROCEED to Phase 15 until Phase 14 Complete checklist is satisfied with working MVP implementation.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Implementation Framework Research

Query 1: "Next.js 14" production setup email marketing SaaS implementation
Query 2: "Supabase integration" email marketing platform database schema implementation
Query 3: "React email editor" drag drop implementation tutorial code examples
Query 4: "email automation builder" visual workflow React implementation

2. Code Implementation Research

Query 5: "Claude Code development" prompts software implementation best practices
Query 6: "progressive web app" email marketing platform implementation patterns
Query 7: "SaaS authentication" Supabase implementation user management code
Query 8: "email marketing API" implementation SendGrid Postmark integration code

DELIVERABLE SPECIFICATIONS - CREATE 4 IMPLEMENTATION GUIDES

After executing ALL 8 WebSearch queries above, create these implementation files with executable Claude Code prompts:

14.1 Implementation Environment Setup (`implementation-environment-setup.md`)

WORD COUNT: Exactly 4,000+ words
IMPLEMENTATION FOCUS: Executable Claude Code prompts for project setup
CODE EXAMPLES: Complete file creation and configuration commands

STRUCTURE REQUIREMENTS:

Section 1: Project Initialization Commands (800 words) - Next.js 14 creation with exact terminal commands
Section 2: Supabase Integration Setup (800 words) - Database connection with actual code and SQL schemas
Section 3: Authentication Implementation (700 words) - Complete auth setup with Supabase Auth code
Section 4: Development Environment Configuration (700 words) - TypeScript, ESLint, Tailwind exact setup
Section 5: Component Library Integration (600 words) - Design system installation with import examples
Section 6: Validation & Testing Setup (400 words) - Verify working environment with test commands

MANDATORY CLAUDE CODE PROMPTS:

Project Creation Prompt: "Create a Next.js 14 email marketing platform with TypeScript, Tailwind, and Supabase integration. Include specific file structure and initial components."
Database Schema Prompt: "Create Supabase database schema for email marketing platform with campaigns, contacts, templates, and automation tables."
Authentication Prompt: "Implement Supabase authentication with user registration, login, and protected routes in Next.js 14."
Environment Validation Prompt: "Create validation scripts to verify all components are working correctly."

14.2 Component Implementation Development (`implementation-component-development.md`)

WORD COUNT: Exactly 4,000+ words
IMPLEMENTATION FOCUS: Executable Claude Code prompts for component creation
CODE EXAMPLES: Complete React component implementations with TypeScript

STRUCTURE REQUIREMENTS:

Section 1: Dashboard Component Implementation (800 words) - Campaign dashboard with real data integration
Section 2: Email Editor Component Development (800 words) - Drag-and-drop email builder implementation
Section 3: Automation Builder Implementation (700 words) - Visual workflow builder with React Flow
Section 4: Contact Management Components (700 words) - List management, segmentation, import/export
Section 5: Template Gallery Implementation (600 words) - Template browsing, preview, and selection
Section 6: Component Testing & Validation (400 words) - Unit tests and Storybook setup

MANDATORY CLAUDE CODE PROMPTS:

Dashboard Creation Prompt: "Create a comprehensive email marketing dashboard component showing campaign metrics, recent activity, and quick actions. Include TypeScript interfaces and Tailwind styling."
Email Editor Prompt: "Implement a drag-and-drop email editor using React with components for text, images, buttons, and layouts. Include real-time preview functionality."
Automation Builder Prompt: "Create a visual automation workflow builder using React Flow with trigger nodes, action nodes, and condition logic."
Contact Management Prompt: "Build contact list management with search, filtering, segmentation, and bulk operations using React and Supabase."

14.3 API Integration Implementation (`implementation-api-integration.md`)

WORD COUNT: Exactly 4,000+ words
IMPLEMENTATION FOCUS: Executable Claude Code prompts for API and service integration
CODE EXAMPLES: Complete API routes, database queries, and third-party integrations

STRUCTURE REQUIREMENTS:

Section 1: RESTful API Routes Implementation (800 words) - Campaign, contact, template API endpoints
Section 2: Supabase Database Integration (800 words) - Real-time queries, subscriptions, and data operations
Section 3: Email Service Integration (700 words) - SendGrid/Postmark setup for email delivery
Section 4: Real-Time Features Implementation (700 words) - Live updates, notifications, websockets
Section 5: Authentication & Authorization (600 words) - Protected routes, user roles, session management
Section 6: Error Handling & Validation (400 words) - Comprehensive error management and data validation

MANDATORY CLAUDE CODE PROMPTS:

API Routes Prompt: "Create comprehensive Next.js API routes for email marketing platform including campaigns, contacts, templates, and automation endpoints with full CRUD operations."
Database Integration Prompt: "Implement Supabase database integration with real-time subscriptions, complex queries, and data relationships for email marketing platform."
Email Service Prompt: "Integrate SendGrid/Postmark email delivery service with queue processing, template rendering, and delivery tracking."
Real-Time Features Prompt: "Implement real-time features using Supabase subscriptions for live dashboard updates, notifications, and collaborative editing."

14.4 Testing & Validation Implementation (`implementation-testing-validation.md`)

WORD COUNT: Exactly 4,000+ words
IMPLEMENTATION FOCUS: Executable Claude Code prompts for testing setup and validation
CODE EXAMPLES: Complete testing configurations, test files, and validation scripts

STRUCTURE REQUIREMENTS:

Section 1: Unit Testing Implementation (800 words) - Jest, React Testing Library setup with component tests
Section 2: Integration Testing Setup (800 words) - API testing, database operations, service integration tests
Section 3: End-to-End Testing Framework (700 words) - Playwright/Cypress for complete user workflow testing
Section 4: Performance Testing & Monitoring (700 words) - Performance benchmarks, optimization validation
Section 5: Code Quality & Standards (600 words) - ESLint, TypeScript, code coverage, quality gates
Section 6: Deployment Validation (400 words) - Production readiness checks and validation scripts

MANDATORY CLAUDE CODE PROMPTS:

Unit Testing Prompt: "Create comprehensive unit tests for all React components using Jest and React Testing Library. Include test utilities, mocks, and coverage configuration."
Integration Testing Prompt: "Implement integration tests for API routes, database operations, and third-party service integrations using Jest and Supertest."
E2E Testing Prompt: "Set up end-to-end testing with Playwright covering complete user workflows: registration, campaign creation, email sending, and analytics viewing."
Quality Validation Prompt: "Implement code quality checks, performance monitoring, and deployment validation scripts to ensure production readiness."

PHASE 14 COMPLETION CHECKLIST

Before proceeding to Phase 15 (Development Environment & Project Setup), Claude Code must verify:

Research & Documentation Complete

ALL 8 WebSearch queries executed for implementation research
4 implementation guides created with exact word counts (16,000+ total words)
Each guide contains specific Claude Code execution prompts
Implementation instructions are executable and testable
TECHNICAL SOURCES VERIFIED: All code examples and best practices sourced from official documentation URLs
FRAMEWORK SPECIFICATIONS SOURCED: All Next.js, Supabase, and tool requirements verified from official sites
IMPLEMENTATION PATTERNS VERIFIED: All coding patterns sourced from verified technical resources with URLs

Working MVP Implementation Complete

Environment Setup: Next.js 14 project created with Supabase integration
Database Schema: Email marketing tables created and populated with test data
Authentication System: User registration, login, and protected routes working
Dashboard Component: Campaign overview with real data display
Email Editor: Drag-and-drop email builder with template functionality
Automation Builder: Visual workflow creator with node-based interface
Contact Management: List management with import/export capabilities
API Endpoints: RESTful API routes for all major features operational
Real-Time Features: Live updates and notifications implemented
Email Integration: SendGrid/Postmark email delivery working
Testing Suite: Unit, integration, and E2E tests passing
Performance Validation: Core features meet speed requirements

Production Readiness Validation

Code Quality: TypeScript strict mode, ESLint, Prettier configured
Security: Authentication, authorization, data validation implemented
Error Handling: Comprehensive error management and user feedback
Responsive Design: Mobile-first design working across breakpoints
Accessibility: WCAG compliance for key user flows
Documentation: Code comments and API documentation complete

PROGRESSION TRIGGER: Phase 14 Complete - Working MVP Ready for Enhancement

PHASE 16: DEVELOPMENT ENVIRONMENT & PROJECT SETUP

Context (Building on Phases 1-11)

Set up complete development environment and project structure for MVP implementation.

# Technical Foundation
TECH_STACK: "Next.js, TypeScript, Supabase from Phase 4"
DESIGN_SYSTEM: "Component library from Phase 13"
ARCHITECTURE: "System design from Phase 4"
INFRASTRUCTURE: "Cloud setup from Phase 4"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 15

Claude Code Instructions: Execute ALL 8 WebSearch queries below. Create 4 comprehensive setup documents.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Development Setup Research

Query 1: "Next.js 14" TypeScript Supabase starter template 2024
Query 2: "monorepo setup" Turborepo email marketing platform
Query 3: "Supabase" authentication email marketing best practices
Query 4: "development environment" Docker local setup Next.js

2. Tooling Research

Query 5: "ESLint Prettier" Next.js configuration best practices
Query 6: "GitHub Actions" CI/CD Next.js Supabase deployment
Query 7: "testing setup" Jest Cypress Next.js email platform
Query 8: "developer productivity" VS Code extensions SaaS development

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

15.1 Project Setup Guide (`setup-project-initialization.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Repository Structure (800 words) - Monorepo organization
Section 2: Next.js Configuration (800 words) - App router, middleware
Section 3: TypeScript Setup (700 words) - Strict configuration
Section 4: Supabase Integration (700 words) - Database, auth, storage
Section 5: Environment Configuration (600 words) - Env variables, secrets
Section 6: Initial Deployment (400 words) - Vercel/AWS setup

15.2 Development Workflow (`setup-development-workflow.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Git Workflow (800 words) - Branching strategy, commits
Section 2: Code Standards (700 words) - Linting, formatting, conventions
Section 3: Testing Workflow (700 words) - Unit, integration, E2E
Section 4: CI/CD Pipeline (700 words) - Automated testing, deployment
Section 5: Code Review Process (600 words) - PR templates, checklists
Section 6: Release Management (500 words) - Versioning, changelogs

15.3 Local Development Guide (`setup-local-development.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Docker Setup (800 words) - Containerized development
Section 2: Database Setup (700 words) - Local Supabase instance
Section 3: Email Testing (700 words) - Local SMTP, Mailhog
Section 4: API Development (700 words) - Routes, middleware
Section 5: Frontend Development (600 words) - Hot reload, debugging
Section 6: Performance Monitoring (500 words) - Local profiling

15.4 Team Onboarding Guide (`setup-team-onboarding.md`)

WORD COUNT: Exactly 4,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Getting Started (800 words) - First day setup
Section 2: Architecture Overview (700 words) - System understanding
Section 3: Development Tools (700 words) - IDE setup, extensions
Section 4: Common Tasks (700 words) - How-to guides
Section 5: Troubleshooting (600 words) - Common issues
Section 6: Resources & Support (500 words) - Documentation, help

PHASE 17: MVP DEVELOPMENT

Context (Building on Phases 1-15)

Execute MVP development with all research, design, and setup complete.

# Development Foundation
SPECIFICATIONS: "Complete PRDs from Phase 11"
DESIGN_SYSTEM: "Component library from Phase 13"
ENVIRONMENT: "Development setup from Phase 15"
ARCHITECTURE: "Technical design from Phase 4"
LOCAL_DEVELOPMENT: "Wireframe implementation from Phase 14"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 16

Claude Code Instructions: Execute ALL 10 WebSearch queries below. Create 4 comprehensive development guides.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Implementation Pattern Research

Query 1: "Next.js email editor" implementation drag drop tutorial
Query 2: "Supabase real-time" subscriptions email marketing
Query 3: "email automation engine" Node.js implementation patterns
Query 4: "React email templates" dynamic rendering MJML
Query 5: "webhook implementation" Next.js queue processing

2. Integration Research

Query 6: "SendGrid integration" Next.js transactional email
Query 7: "Stripe subscription" SaaS billing Next.js
Query 8: "file upload" Supabase storage email attachments
Query 9: "analytics implementation" Mixpanel email marketing
Query 10: "rate limiting" Next.js API protection

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

16.1 Core Feature Implementation (`development-core-features.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Email Editor Implementation (1000 words) - Drag-drop functionality
Section 2: Automation Engine Build (1000 words) - Workflow execution
Section 3: Contact Management System (800 words) - CRUD operations
Section 4: Template System (800 words) - Storage and rendering
Section 5: Analytics Dashboard (700 words) - Real-time metrics
Section 6: API Development (700 words) - RESTful endpoints

16.2 Integration Implementation (`development-integrations.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Email Delivery Service (1000 words) - SendGrid/SES setup
Section 2: Payment Processing (1000 words) - Stripe subscriptions
Section 3: Authentication System (800 words) - Supabase auth
Section 4: File Storage (800 words) - Image/attachment handling
Section 5: Third-party Webhooks (700 words) - External integrations
Section 6: Analytics Services (700 words) - Tracking implementation

16.3 Frontend Implementation (`development-frontend-guide.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Dashboard Components (1000 words) - Main interface build
Section 2: Editor Interface (1000 words) - Drag-drop implementation
Section 3: Automation Builder UI (800 words) - Visual workflow
Section 4: Responsive Implementation (800 words) - Mobile optimization
Section 5: State Management (700 words) - Redux/Zustand setup
Section 6: Performance Optimization (700 words) - Code splitting

16.4 Backend Implementation (`development-backend-guide.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: API Architecture (1000 words) - Route structure
Section 2: Database Operations (1000 words) - Supabase queries
Section 3: Queue Processing (800 words) - Background jobs
Section 4: Email Processing (800 words) - Sending logic
Section 5: Security Implementation (700 words) - Auth, validation
Section 6: Monitoring Setup (700 words) - Logging, alerts

16.5 Automation Template Library (`development-automation-templates.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Welcome Series Templates (1000 words) - New subscriber onboarding
Section 2: E-commerce Automations (1000 words) - Cart abandonment, post-purchase
Section 3: SaaS User Journeys (800 words) - Trial conversion, onboarding
Section 4: Re-engagement Campaigns (800 words) - Win-back sequences
Section 5: Event-Based Triggers (700 words) - Birthday, anniversary automations
Section 6: Template Customization (700 words) - Modification framework

16.6 Customer Support System (`development-support-system.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Help Desk Integration (1000 words) - Ticket system implementation
Section 2: Knowledge Base Structure (1000 words) - Self-service documentation
Section 3: Live Chat Implementation (800 words) - Real-time support
Section 4: Support Analytics (800 words) - Response times, satisfaction
Section 5: Escalation Workflows (700 words) - Tier 1/2/3 support
Section 6: Community Forums (700 words) - User-to-user help

PHASE 19: TESTING & MVP VALIDATION

Context (Building on Phases 1-16)

Comprehensive testing and validation before MVP launch.

# Testing Foundation
TEST_SPECIFICATIONS: "Test plans from Phase 11"
LOCAL_TESTING: "Testing framework from Phase 14"
IMPLEMENTATION: "Completed MVP from Phase 16"
QUALITY_STANDARDS: "Standards from Phase 6"
SUCCESS_METRICS: "KPIs from Phase 7"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 17

Claude Code Instructions: Execute ALL 8 WebSearch queries below. Create 4 comprehensive testing documents.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Testing Strategy Research

Query 1: "email marketing platform" testing strategy best practices
Query 2: "Next.js testing" Jest React Testing Library guide
Query 3: "Cypress E2E testing" email marketing workflows
Query 4: "load testing" email platform K6 Artillery

2. Validation Research

Query 5: "MVP validation" metrics email marketing success
Query 6: "user acceptance testing" SaaS platform checklist
Query 7: "email deliverability testing" spam score validation
Query 8: "performance benchmarks" email marketing platform

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

17.1 Testing Execution Guide (`testing-execution-guide.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Unit Test Implementation (1000 words) - Component testing
Section 2: Integration Testing (1000 words) - API and service tests
Section 3: E2E Test Scenarios (800 words) - User journey tests
Section 4: Performance Testing (800 words) - Load and stress tests
Section 5: Security Testing (700 words) - Vulnerability scans
Section 6: Accessibility Testing (700 words) - WCAG validation

17.2 Quality Assurance Plan (`testing-qa-plan.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: QA Process Overview (1000 words) - Testing methodology
Section 2: Test Case Management (900 words) - Organization and tracking
Section 3: Bug Management (800 words) - Tracking and prioritization
Section 4: Regression Testing (800 words) - Automated suites
Section 5: Release Testing (800 words) - Pre-launch checklist
Section 6: Post-Release Monitoring (700 words) - Production validation

17.3 User Acceptance Testing (`testing-uat-guide.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: UAT Planning (1000 words) - Test scenarios and users
Section 2: Beta Program Setup (900 words) - Recruitment and onboarding
Section 3: Feedback Collection (800 words) - Surveys and interviews
Section 4: Issue Prioritization (800 words) - Triage and fixes
Section 5: Success Criteria (800 words) - Go/no-go decisions
Section 6: Launch Readiness (700 words) - Final validation

17.4 MVP Validation Report (`testing-validation-report.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Feature Completeness (1000 words) - Requirements coverage
Section 2: Performance Validation (900 words) - Speed and scale tests
Section 3: Security Validation (800 words) - Vulnerability assessment
Section 4: Usability Validation (800 words) - User testing results
Section 5: Market Readiness (800 words) - Competitive comparison
Section 6: Launch Recommendation (700 words) - Final assessment

PHASE 17 COMPLETION CHECKLIST

MVP Ready for Launch:

All test suites passing with >90% coverage
Performance benchmarks met or exceeded
Security audit completed and issues resolved
Beta user feedback incorporated
Documentation complete and reviewed
Production environment configured
Support processes established
Launch plan finalized

COMPREHENSIVE MVP DOCUMENTATION SUMMARY

Total Phase 10-17 Output (8 Phases, 50 Files, 202,500+ Words)

Phase 10: UI/UX Wireframes (9 files, 22,500+ total words)

Comprehensive wireframe system with 7-20 high-quality SVG wireframes
Information architecture and interaction design patterns
User journey mapping and interface specifications
Mobile experience design and responsive behavior
Accessibility standards and usability requirements

Phase 11: Visual Competitor Analysis (4 files, 14,000 words)

Visual UI/UX patterns from competitors
Design system recommendations
Brand visual strategy

Phase 12: Feature Specifications (8 files, 32,000 words)

Complete technical PRD
Detailed feature specifications
Testing requirements
Data migration tools
Email deliverability infrastructure
Compliance framework
Performance benchmarks

Phase 13: UX/UI Design (6 files, 24,000 words)

High-fidelity mockup specifications
Interactive prototype plans
Accessibility guidelines
Onboarding flow design
Email template gallery

Phase 14: Design System (6 files, 24,000 words)

Component library architecture
Implementation guidelines
Governance framework
Email template components
Automation visual elements

Phase 15: MVP Implementation (4 files, 16,000 words)

Local environment setup and configuration
Wireframe to working component conversion
Integration development and testing
Local validation framework

Phase 16: Development Setup (4 files, 16,000 words)

Project initialization
Development workflows
Team onboarding

Phase 17: MVP Development (6 files, 30,000 words)

Core feature implementation
Integration guides
Frontend/backend development
Automation template library
Customer support system

USING THIS EXTENDED FRAMEWORK

Sequential Execution: Complete phases 1-7 for research and planning before starting phase 8
Visual Documentation: Phase 10 requires @knowcode/imgfetch for competitor screenshots
Progressive Detail: Each phase builds on previous findings
MVP Focus: Phases 8-18 specifically target working MVP delivery
Quality Gates: Each phase has completion criteria before progression
Local Development: Phase 14 bridges design and full implementation

The extended framework ensures a research-driven approach to MVP development, with visual competitor analysis informing design decisions, local wireframe implementation providing practical prototypes, and comprehensive documentation supporting the entire development lifecycle.

PHASE 18: SUPPORT MATERIALS PRODUCTION

Context (Building on Phases 1-16)

Create comprehensive support materials and sales assets for successful product launch and customer acquisition.

# Foundation from MVP Development
MVP_COMPLETE: "Fully developed and tested platform from Phase 16"
DESIGN_SYSTEM: "Consistent brand and UI framework from Phase 13"
FEATURE_SPECS: "Complete functionality documentation from Phase 11"
USER_PERSONAS: "Target customer profiles from Phase 2"
VALUE_PROPOSITIONS: "Clear messaging from Phase 3"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 17

Claude Code Instructions: Execute ALL 10 WebSearch queries below sequentially. Use results to create 6 comprehensive markdown documents. DO NOT PROCEED to Phase 18 until Phase 17 Complete checklist is satisfied.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Sales Materials Research

Query 1: "SaaS sales kit" templates best practices 2024 2025
Query 2: "email marketing platform" sales presentations competitor analysis
Query 3: "product demo scripts" SaaS software live demonstration

2. Marketing Collateral Research

Query 4: "marketing collateral examples" SaaS email marketing platforms
Query 5: "case study templates" customer success stories email marketing
Query 6: "product comparison sheets" competitive analysis templates

3. Support Documentation Research

Query 7: "SaaS documentation examples" help center knowledge base
Query 8: "customer onboarding" best practices email marketing tools
Query 9: "FAQ templates" SaaS support common questions
Query 10: "customer success frameworks" SaaS retention strategies

DELIVERABLE SPECIFICATIONS - CREATE 6 MARKDOWN FILES

17.1 Sales Materials Kit (`sales-materials-kit.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Sales Deck Template (1000 words) - Complete presentation framework
Section 2: Product Demo Scripts (800 words) - Live demonstration guides
Section 3: Pricing Proposal Templates (800 words) - Customizable sales proposals
Section 4: ROI Calculator Templates (700 words) - Customer value calculations
Section 5: Objection Handling Guide (800 words) - Common concerns and responses
Section 6: Sales Process Documentation (900 words) - End-to-end sales workflow

MANDATORY CONTENT:

Slide-by-slide sales deck with speaker notes
15-minute demo script with key feature highlights
Pricing comparison vs ActiveCampaign/Mailchimp
ROI calculation templates for different customer sizes
Top 20 sales objections with proven responses
CRM integration and lead tracking processes

17.2 Marketing Collateral System (`marketing-collateral-system.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Brand Asset Library (800 words) - Logos, colors, fonts, guidelines
Section 2: Website Copy Templates (1000 words) - Landing pages, features, about
Section 3: Social Media Templates (700 words) - Posts, campaigns, ads
Section 4: Email Marketing Templates (800 words) - Newsletters, drip campaigns
Section 5: Case Study Framework (900 words) - Customer success story template
Section 6: Competitive Comparison Materials (800 words) - Feature comparison charts

MANDATORY CONTENT:

Complete brand guidelines with visual examples
Conversion-optimized landing page copy variations
Social media content calendar with 30+ post ideas
Email sequences for lead nurturing and conversion
Case study template with before/after metrics
Feature comparison charts vs top 5 competitors

17.3 Demo Presentation Guide (`demo-presentation-guide.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Demo Environment Setup (800 words) - Technical preparation
Section 2: Persona-Based Demo Flows (1200 words) - Customized demonstrations
Section 3: Interactive Demo Scripts (1000 words) - Step-by-step walkthroughs
Section 4: Feature Showcase Templates (800 words) - Key functionality highlights
Section 5: Q&A Preparation Guide (700 words) - Common questions and answers
Section 6: Follow-up Action Plans (500 words) - Post-demo engagement

MANDATORY CONTENT:

Demo account setup with realistic sample data
Separate demo flows for small business vs enterprise
Screen-by-screen walkthrough with talking points
Feature comparison during demo vs competitor tools
Technical Q&A covering integrations and security
Demo feedback collection and follow-up templates

17.4 Support Documentation System (`support-documentation-system.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Help Center Architecture (800 words) - Documentation structure
Section 2: Getting Started Guides (1000 words) - Onboarding documentation
Section 3: Feature Documentation (1200 words) - Complete functionality guides
Section 4: Integration Guides (800 words) - Third-party service setup
Section 5: Troubleshooting Library (700 words) - Common issues and solutions
Section 6: Video Tutorial Scripts (500 words) - Screencast content plans

MANDATORY CONTENT:

Searchable knowledge base structure with categories
Step-by-step setup guides with screenshots
Feature tutorials for email editor, automation, analytics
Integration guides for SendGrid, Stripe, Zapier
Troubleshooting for delivery issues, authentication, billing
Video tutorial outlines for visual learners

17.5 User Onboarding Materials (`user-onboarding-materials.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Welcome Sequence Design (800 words) - First-time user experience
Section 2: Progressive Onboarding Framework (1000 words) - Feature introduction
Section 3: Interactive Tutorial System (900 words) - In-app guidance
Section 4: Onboarding Email Sequences (800 words) - Educational drip campaigns
Section 5: Success Milestone Tracking (700 words) - User progress metrics
Section 6: Onboarding Optimization Plan (800 words) - Continuous improvement

MANDATORY CONTENT:

Day 0-30 onboarding journey with key milestones
In-app tooltips and guided tours for main features
Progressive feature unlocking based on user competence
Email sequence with tutorials, tips, and best practices
Success metrics: first campaign sent, automation created
A/B testing framework for onboarding optimization

17.6 Customer Success Frameworks (`customer-success-frameworks.md`)

WORD COUNT: Exactly 5,000+ words

STRUCTURE REQUIREMENTS:

Section 1: Customer Health Scoring (800 words) - Engagement metrics
Section 2: Success Milestone Framework (900 words) - Customer journey stages
Section 3: Retention Strategy Playbook (1000 words) - Churn prevention
Section 4: Expansion Opportunity Identification (800 words) - Upselling framework
Section 5: Customer Feedback Systems (700 words) - Satisfaction measurement
Section 6: Success Team Processes (800 words) - Team workflows and KPIs

MANDATORY CONTENT:

Health score calculation based on usage, engagement, support tickets
Success milestones: first campaign, 100 contacts, automation setup
Churn risk identification and intervention strategies
Upselling triggers based on usage patterns and growth
NPS surveys, feedback collection, and feature request tracking
Customer success team playbooks and performance metrics

Phase 17 Complete - Progression Checklist

DO NOT PROCEED to Phase 18 until ALL items below are verified:

Sales Materials Kit Complete: 5,000+ word comprehensive sales enablement guide
Marketing Collateral System Complete: 5,000+ word brand and marketing asset library
Demo Presentation Guide Complete: 5,000+ word demonstration framework
Support Documentation System Complete: 5,000+ word help center architecture
User Onboarding Materials Complete: 5,000+ word onboarding experience design
Customer Success Frameworks Complete: 5,000+ word retention and growth strategy
SALES METHODOLOGY SOURCED: All sales techniques and frameworks verified from industry sources with URLs
MARKETING BEST PRACTICES VERIFIED: All marketing strategies sourced from verified marketing resources with URLs
ONBOARDING PATTERNS SOURCED: All user onboarding flows verified from UX research and case studies with URLs

QUALITY VALIDATION:

Each document cites specific WebSearch research findings
All materials align with brand guidelines from Phase 13
Content addresses user personas identified in Phase 2
Materials support launch strategy from Phase 7
Documentation integrates with technical architecture from Phase 4

PROGRESSION TRIGGER: When ALL 6 deliverables are complete and validated, automatically proceed to Phase 18: Payment Integration.

POST-LAUNCH EXECUTION PHASES (18-28)

Post-Launch Context (Building on MVP Completion)

With MVP tested and validated through Phase 17, now execute post-launch phases focused on payment integration, customer acquisition, growth, and market leadership.

# MVP Foundation from Phases 1-17
MVP_LAUNCHED: "Feature-complete platform validated through comprehensive testing"
MARKET_RESEARCH: "Deep competitive intelligence and user persona understanding"
TECHNICAL_FOUNDATION: "Scalable architecture ready for growth"
DESIGN_SYSTEM: "Comprehensive UI/UX framework for consistent experience"
VALIDATION_COMPLETE: "Beta testing and quality assurance processes completed"

PHASE 20: SECURITY COMPLIANCE & MEASUREMENT EXECUTION PROTOCOL

Security Validation Context (After MVP Implementation)

With MVP implementation complete from Phases 15-19, now validate and measure security implementation against design requirements from Phase 5.

# Implementation Foundation
SECURITY_ARCHITECTURE: "[Security design from Phase 5]"
MVP_COMPONENTS: "[Built system from Phases 15-17]"
DEPLOYMENT_ENVIRONMENT: "[Production setup from implementation phases]"
COMPLIANCE_TARGETS: "[Certification goals from Phase 5 planning]"

# Validation Requirements
TESTING_SCOPE: "[Security testing requirements from Phase 5]"
AUDIT_REQUIREMENTS: "[Compliance audit needs from regulatory research]"
MONITORING_NEEDS: "[Security monitoring requirements from threat modeling]"
CERTIFICATION_GOALS: "[Target certifications and timelines from compliance planning]"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 20

Claude Code Instructions: Execute ALL 10 WebSearch queries below sequentially. Use results to create 4 comprehensive security validation documents. DO NOT PROCEED to Phase 21 until Phase 20 Complete checklist is satisfied.

CITATION REQUIREMENTS: All testing methodologies, compliance procedures, monitoring tools, and certification requirements MUST be sourced from WebSearch results with exact URLs. Include links to security testing resources, audit frameworks, and certification guidelines.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Security Testing & Validation Research

Query 1: "security testing methodology" SAST DAST vulnerability assessment SaaS platform
Query 2: "penetration testing" web application security testing automated scanning
Query 3: "security code review" static analysis tools best practices implementation

2. Compliance Audit Research

Query 4: "SOC 2 audit preparation" controls testing evidence documentation process
Query 5: "GDPR compliance audit" checklist requirements verification assessment
Query 6: "security compliance framework" ISO 27001 NIST cybersecurity audit

3. Security Monitoring Implementation Research

Query 7: "security monitoring implementation" SIEM logging threat detection alerting
Query 8: "vulnerability management" patch management security operations continuous monitoring

4. Security Certification Research

Query 9: "security certification preparation" SOC 2 ISO 27001 documentation requirements
Query 10: "incident response testing" tabletop exercises security drill procedures validation

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

20.1 Security Testing & Validation (`security-testing-validation.md`)

WORD COUNT: Exactly 5,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Security Testing Strategy (1,000 words) - Comprehensive testing approach and methodology
Section 2: Vulnerability Assessment Execution (1,200 words) - SAST, DAST, and penetration testing implementation
Section 3: Security Code Review Process (800 words) - Static analysis and manual review procedures
Section 4: Infrastructure Security Testing (1,000 words) - Cloud security, network security, configuration testing
Section 5: Application Security Validation (600 words) - Authentication, authorization, input validation testing
Section 6: Security Testing Reporting (400 words) - Results documentation and remediation tracking

MANDATORY CONTENT:

Automated security scanning tool implementation and configuration
Penetration testing scope, methodology, and execution procedures
Code review checklist and security-focused review criteria
Infrastructure security assessment including cloud configuration review
Web application security testing including OWASP Top 10 validation
Security testing metrics and success criteria with remediation timelines

20.2 Compliance Audit & Verification (`security-compliance-audit.md`)

WORD COUNT: Exactly 5,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Audit Preparation Strategy (1,000 words) - Readiness assessment and preparation methodology
Section 2: SOC 2 Audit Implementation (1,200 words) - Trust Services Criteria validation and evidence collection
Section 3: GDPR Compliance Verification (1,000 words) - Data protection regulation compliance validation
Section 4: Additional Compliance Audits (800 words) - ISO 27001, industry-specific requirements
Section 5: Documentation & Evidence Management (600 words) - Audit trail creation and maintenance
Section 6: Continuous Compliance Monitoring (400 words) - Ongoing compliance validation processes

MANDATORY CONTENT:

SOC 2 Type II readiness assessment and control implementation validation
GDPR compliance audit including data processing, consent, and subject rights validation
Compliance documentation repository and evidence collection procedures
Internal audit procedures and self-assessment frameworks
External audit coordination and vendor management processes
Compliance monitoring dashboards and reporting mechanisms

20.3 Security Monitoring Implementation (`security-monitoring-implementation.md`)

WORD COUNT: Exactly 5,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Monitoring Architecture Design (1,000 words) - Security monitoring system architecture and integration
Section 2: Threat Detection Implementation (1,200 words) - Real-time threat detection and alerting systems
Section 3: Security Information Management (800 words) - Log aggregation, analysis, and retention
Section 4: Incident Detection & Response (1,000 words) - Automated detection and response procedures
Section 5: Security Metrics & Reporting (600 words) - KPIs, dashboards, and executive reporting
Section 6: Monitoring Operations & Maintenance (400 words) - Ongoing monitoring operations and optimization

MANDATORY CONTENT:

SIEM implementation including log sources, parsing rules, and correlation logic
Threat intelligence integration and automated threat hunting capabilities
Security alerting framework with escalation procedures and notification systems
Incident response automation and security orchestration implementation
Security dashboard design with real-time monitoring and historical analysis
Security operations procedures including monitoring, analysis, and response workflows

20.4 Security Certification Preparation (`security-certification-preparation.md`)

WORD COUNT: Exactly 5,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Certification Strategy & Planning (800 words) - Target certifications and implementation roadmap
Section 2: SOC 2 Type II Preparation (1,200 words) - Detailed preparation procedures and control implementation
Section 3: ISO 27001 Readiness Assessment (1,000 words) - Information security management system preparation
Section 4: Additional Security Certifications (800 words) - Industry-specific or regional certification requirements
Section 5: Certification Documentation Management (600 words) - Evidence collection and documentation organization
Section 6: Certification Maintenance & Renewal (600 words) - Ongoing certification management and improvement

MANDATORY CONTENT:

Certification timeline and milestone planning with resource allocation
Control implementation validation and testing procedures
Documentation requirements and evidence collection frameworks
Internal readiness assessment and gap analysis procedures
External auditor coordination and vendor management processes
Certification maintenance procedures and continuous improvement frameworks

PHASE 20 COMPLETION CHECKLIST

Before proceeding to Phase 21, Claude Code must verify:

ALL 10 WebSearch queries executed and documented with citations
4 markdown files created with exact word counts (20,000+ total words)
Security testing strategy implemented with automated scanning tools
Vulnerability assessment completed with remediation plan
Compliance audit procedures documented for SOC 2 and GDPR
Security monitoring system implemented with threat detection
Incident response procedures tested and validated
Security certification preparation roadmap completed
TESTING METHODOLOGY VERIFIED: All security testing approaches sourced from industry standards with URLs
COMPLIANCE PROCEDURES SOURCED: All audit requirements verified from official regulatory documentation
MONITORING TOOLS VERIFIED: All security monitoring implementations sourced from vendor documentation
CERTIFICATION REQUIREMENTS SOURCED: All certification procedures verified from official certification body URLs

PROGRESSION TRIGGER: Phase 20 Complete - Proceed to Phase 21

PHASE 21: BETA CUSTOMER ACQUISITION & VALIDATION

Post-MVP Context (Built on Phase 18 Testing & Validation)

With MVP testing complete, now acquire beta customers and validate product-market fit in live market conditions.

# MVP Reality from Phase 18
TESTED_FEATURES: "All core features validated through comprehensive testing"
PERFORMANCE_BENCHMARKS: "Speed and scale requirements met"
SECURITY_VALIDATION: "Vulnerability assessment completed"
LAUNCH_READINESS: "Production environment configured and validated"
EARLY_FEEDBACK: "Initial user testing insights documented"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 18

Claude Code Instructions: Execute ALL 10 WebSearch queries below sequentially. Use results to create 4 comprehensive markdown documents. DO NOT PROCEED to Phase 19 until Phase 18 Complete checklist is satisfied.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Beta Customer Research

Query 1: "SaaS beta testing" customer acquisition best practices 2024 2025
Query 2: "email marketing beta users" recruitment strategies early adopters
Query 3: "product hunt launch" beta customer strategies community building

2. Early Adopter Communities Research

Query 4: "email marketing communities" Reddit Discord Slack groups
Query 5: "small business communities" beta testing recruitment forums
Query 6: "indie hackers" email marketing tool discussions feedback

3. Validation Framework Research

Query 7: "product market fit" validation metrics SaaS email marketing
Query 8: "customer feedback collection" beta testing tools surveys
Query 9: "beta testing KPIs" success metrics email marketing platform
Query 10: "early customer success" case studies email marketing startups

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

18.1 Beta Customer Acquisition Strategy (`beta-customer-acquisition-strategy.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Early Adopter Identification (800 words) - Target customer profiles and community research
Section 2: Acquisition Channel Strategy (800 words) - Community outreach, content marketing, partnerships
Section 3: Beta Program Structure (700 words) - Pricing, features, timeline, expectations
Section 4: Recruitment Campaign Plan (700 words) - Messaging, channels, conversion funnels
Section 5: Community Building Approach (600 words) - Engagement strategies and feedback loops
Section 6: Success Metrics & Tracking (400 words) - KPIs and measurement framework

MANDATORY CONTENT:

Reddit communities: r/entrepreneur, r/smallbusiness, r/marketing, r/SaaS, r/emailmarketing
Discord servers: Indie Hackers, SaaS Growth, Email Marketing Pros, Startup Grind
Industry forums: Hacker News, IndieHackers.com, ProductHunt makers community
Professional networks: LinkedIn groups, Twitter communities, marketing Slack groups
Beta program structure: free vs paid beta, feature limitations, support levels
Specific messaging for each persona identified in Phase 2

18.2 Product-Market Fit Validation Framework (`pmf-validation-framework.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: PMF Metrics Definition (800 words) - Quantitative indicators and benchmarks
Section 2: Customer Interview Framework (800 words) - Structured feedback collection methodology
Section 3: Usage Analytics Setup (700 words) - Behavioral tracking and analysis
Section 4: Retention Analysis System (700 words) - Cohort analysis and churn metrics
Section 5: Feature Adoption Tracking (600 words) - Core feature usage patterns
Section 6: Validation Decision Framework (400 words) - Go/no-go criteria for full launch

MANDATORY CONTENT:

Sean Ellis PMF survey methodology with email marketing industry adaptations
Net Promoter Score benchmarks for SaaS email marketing tools
Customer retention benchmarks: 90% month 1, 80% month 3, 70% month 6
Feature adoption metrics: email editor usage, automation setup rates, template usage
Customer interview scripts for different personas (small business, SaaS, e-commerce)
Competitive benchmarking against ActiveCampaign, Mailchimp user satisfaction

18.3 Feedback Collection & Analysis System (`feedback-collection-analysis.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Multi-Channel Feedback Strategy (800 words) - In-app, email, calls, surveys
Section 2: Feedback Categorization Framework (800 words) - Feature requests, bugs, UX issues
Section 3: Customer Interview Process (700 words) - Scheduling, scripts, analysis methods
Section 4: Data Analysis & Pattern Recognition (700 words) - Qualitative and quantitative insights
Section 5: Feedback Prioritization System (600 words) - Impact vs effort scoring
Section 6: Action Planning & Communication (400 words) - Response strategies and roadmap updates

MANDATORY CONTENT:

In-app feedback widgets with context-sensitive prompts
NPS surveys timed to user onboarding milestones
Email drip campaigns requesting specific feedback on key features
Video call interview scheduling integrated with calendar booking
Feedback tagging system: UI/UX, features, performance, integrations, pricing
Response time commitments and customer communication templates

18.4 Early Customer Success Program (`early-customer-success.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Customer Onboarding Optimization (800 words) - Guided setup and first success
Section 2: Proactive Support Strategy (800 words) - Early intervention and success enablement
Section 3: Customer Health Monitoring (700 words) - Usage patterns and risk indicators
Section 4: Success Milestone Framework (700 words) - Achievement tracking and celebration
Section 5: Customer Advocacy Development (600 words) - Case studies and referral programs
Section 6: Retention & Expansion Strategy (400 words) - Upgrade paths and feature adoption

MANDATORY CONTENT:

30-60-90 day customer journey maps with intervention points
Customer health scores based on login frequency, feature usage, support tickets
Success milestones: first email sent, first automation created, first campaign results
Proactive outreach triggers: low usage, support ticket patterns, billing issues
Case study development process for successful early customers
Referral program structure with incentives for beta customers

PHASE 20 COMPLETION CHECKLIST

Before proceeding to Phase 26, Claude Code must verify:

ALL 10 WebSearch queries executed and documented with citations
4 markdown files created with exact word counts (16,000+ total words)
Beta customer acquisition channels identified and validated through research
Product-market fit validation framework established with industry benchmarks
Feedback collection system designed with multi-channel approach
Early customer success program defined with proactive intervention points
Community outreach strategies researched and documented (Reddit, Discord, etc.)
Success metrics benchmarked against competitor performance research
Customer interview frameworks adapted for email marketing personas

PROGRESSION TRIGGER: Phase 21 Complete - Proceed to Phase 22

PHASE 22: PAYMENT INTEGRATION & MONETIZATION (STRIPE)

Monetization Context (Built on Phase 19 Beta Validation)

With beta customers acquired and initial validation complete, now implement comprehensive payment system and monetization strategy.

# Beta Validation from Phase 19
BETA_CUSTOMERS: "Early adopters acquired and providing feedback"
PMF_VALIDATION: "Product-market fit signals identified and measured"
CUSTOMER_FEEDBACK: "Feature requests and pricing insights collected"
SUCCESS_PATTERNS: "Early customer success milestones documented"
MARKET_READINESS: "Validation framework confirms market demand"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 19

Claude Code Instructions: Execute ALL 10 WebSearch queries below sequentially. Use results to create 4 comprehensive markdown documents. DO NOT PROCEED to Phase 20 until Phase 19 Complete checklist is satisfied.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Stripe Integration Research

Query 1: "Stripe integration" Next.js React best practices 2024 implementation
Query 2: "SaaS billing system" Stripe webhooks subscription management
Query 3: "email marketing platform" Stripe pricing tiers usage-based billing

2. Pricing Strategy Research

Query 4: "SaaS pricing strategy" email marketing freemium vs paid tiers
Query 5: "email marketing pricing" ActiveCampaign Mailchimp ConvertKit models
Query 6: "usage-based billing" email platform subscriber limits send volume

3. Revenue Optimization Research

Query 7: "subscription revenue optimization" SaaS metrics churn reduction
Query 8: "payment flow optimization" conversion rate checkout abandonment
Query 9: "billing automation" dunning management failed payment recovery
Query 10: "revenue analytics" MRR ARR cohort analysis subscription metrics

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

19.1 Stripe Integration Technical Specifications (`stripe-integration-specs.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Stripe Architecture Design (800 words) - API integration and webhook handling
Section 2: Subscription Management System (800 words) - Plan creation, upgrades, downgrades
Section 3: Payment Flow Implementation (700 words) - Checkout, billing portal, payment methods
Section 4: Webhook Event Handling (700 words) - Real-time subscription status updates
Section 5: Security & Compliance (600 words) - PCI compliance, data protection
Section 6: Testing & Validation Framework (400 words) - Payment testing and error handling

MANDATORY CONTENT:

Stripe Elements integration for secure payment collection
Subscription lifecycle management: trial, active, past_due, canceled
Webhook endpoints for invoice.payment_succeeded, subscription.updated events
Customer portal integration for self-service billing management
Multi-currency support for international markets
Failed payment handling and dunning management automation

19.2 Monetization Strategy & Pricing Tiers (`monetization-pricing-strategy.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Pricing Model Research & Selection (800 words) - Freemium vs paid, usage vs flat rate
Section 2: Tier Structure Definition (800 words) - Feature differentiation and subscriber limits
Section 3: Competitive Pricing Analysis (700 words) - Market positioning vs ActiveCampaign/Mailchimp
Section 4: Value-Based Pricing Framework (700 words) - ROI justification and price anchoring
Section 5: Revenue Forecasting Models (600 words) - Growth projections and unit economics
Section 6: Pricing Testing & Optimization (400 words) - A/B testing framework for pricing

MANDATORY CONTENT:

Freemium tier: 500 contacts, 2,000 emails/month, basic templates
Starter tier: $25/month, 2,500 contacts, 15,000 emails/month, automation
Professional tier: $49/month, 10,000 contacts, unlimited emails, advanced features
Enterprise tier: $99/month+, unlimited contacts, white-label, priority support
Usage overage pricing: $10 per 1,000 additional contacts
Annual discount: 20% off monthly pricing for annual plans

19.3 Revenue Analytics & Business Intelligence (`revenue-analytics-system.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Revenue Metrics Dashboard (800 words) - MRR, ARR, churn, LTV tracking
Section 2: Customer Analytics Framework (800 words) - Cohort analysis and segmentation
Section 3: Subscription Analytics (700 words) - Upgrade/downgrade patterns, retention
Section 4: Payment Success Optimization (700 words) - Failed payment analysis and recovery
Section 5: Financial Reporting Automation (600 words) - Automated reports and alerts
Section 6: Business Intelligence Integration (400 words) - Data warehouse and analysis tools

MANDATORY CONTENT:

Real-time MRR tracking with growth rate calculations
Cohort retention analysis by acquisition channel and plan type
Customer lifetime value calculations with segment breakdowns
Churn analysis: voluntary vs involuntary, reasons and patterns
Revenue forecasting models based on historical data
Integration with accounting systems for automated revenue recognition

19.4 Billing Automation & Customer Portal (`billing-automation-portal.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Automated Billing Workflows (800 words) - Invoice generation and payment processing
Section 2: Customer Self-Service Portal (800 words) - Account management and billing history
Section 3: Dunning Management System (700 words) - Failed payment recovery automation
Section 4: Usage Monitoring & Limits (700 words) - Real-time usage tracking and notifications
Section 5: Account Management Features (600 words) - Plan changes, cancellation, reactivation
Section 6: Support Integration (400 words) - Billing support tools and escalation

MANDATORY CONTENT:

Automated invoice generation with custom branding
Usage limit enforcement with overage billing
Failed payment retry logic: 3 attempts over 10 days
Cancellation flow with exit survey and retention offers
Proration calculations for mid-cycle plan changes
Integration with customer support system for billing inquiries

PHASE 20 COMPLETION CHECKLIST

Before proceeding to Phase 26, Claude Code must verify:

ALL 10 WebSearch queries executed and documented with citations
4 markdown files created with exact word counts (16,000+ total words)
Stripe integration architecture defined with webhook handling
Pricing tiers established with competitive market positioning
Revenue analytics system designed with MRR/ARR tracking
Billing automation workflows specified with dunning management
Customer portal features defined for self-service account management
Payment security and PCI compliance requirements documented
Pricing testing framework established for optimization
Financial reporting automation specified for business intelligence

PROGRESSION TRIGGER: Phase 22 Complete - Proceed to Phase 23

PHASE 23: SEO & CONTENT MARKETING FOUNDATION

Content Marketing Context (Built on Phase 19 Monetization & Phase 20 Production Readiness)

With payment system implemented and revenue streams established, now build comprehensive SEO and content marketing foundation for sustainable organic growth.

# Monetization Foundation from Phase 20
PAYMENT_SYSTEM: "Stripe integration with subscription management"
PRICING_STRATEGY: "Tiered pricing model validated and implemented"
REVENUE_TRACKING: "MRR/ARR analytics and business intelligence"
CUSTOMER_PORTAL: "Self-service billing and account management"
MONETIZATION_READY: "Revenue optimization and billing automation"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 20

Claude Code Instructions: Execute ALL 10 WebSearch queries below sequentially. Use results to create 4 comprehensive markdown documents. DO NOT PROCEED to Phase 21 until Phase 20 Complete checklist is satisfied.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. SEO Strategy Research

Query 1: "email marketing SEO" keyword research strategy content optimization
Query 2: "SaaS content marketing" SEO best practices organic growth 2024
Query 3: "competitor content analysis" ActiveCampaign Mailchimp blog strategy

2. Content Foundation Research

Query 4: "email marketing blog" content calendar topics small business
Query 5: "SaaS documentation SEO" help center optimization strategy
Query 6: "marketing automation content" educational resources lead generation

3. Technical SEO Research

Query 7: "Next.js SEO optimization" technical SEO implementation guide
Query 8: "SaaS website SEO" page speed Core Web Vitals optimization
Query 9: "content management system" headless CMS SEO Next.js
Query 10: "email marketing keywords" search volume competition analysis

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

20.1 SEO Strategy & Keyword Research (`seo-strategy-keyword-research.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: SEO Competitive Analysis (800 words) - Competitor keyword rankings and content gaps
Section 2: Keyword Research & Strategy (800 words) - Primary and long-tail keyword identification
Section 3: Technical SEO Implementation (700 words) - On-page optimization and site structure
Section 4: Content Strategy for SEO (700 words) - Content themes and keyword targeting
Section 5: Local & Niche SEO Opportunities (600 words) - Small business and industry-specific SEO
Section 6: SEO Measurement & Analytics (400 words) - Ranking tracking and performance metrics

MANDATORY CONTENT:

Primary keywords: "email marketing", "email automation", "newsletter software"
Long-tail keywords: "best email marketing for small business", "affordable email automation"
Competitor analysis: ActiveCampaign, Mailchimp, ConvertKit content performance
Technical SEO checklist: meta tags, schema markup, site speed optimization
Content cluster strategy around email marketing themes
Google Search Console and rank tracking setup

20.2 Content Marketing System & Editorial Calendar (`content-marketing-system.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Content Strategy Framework (800 words) - Goals, audience, messaging pillars
Section 2: Editorial Calendar & Production (800 words) - Content planning and workflow
Section 3: Content Types & Distribution (700 words) - Blog posts, guides, videos, social
Section 4: Content Creation Workflows (700 words) - Writing, editing, approval processes
Section 5: Content Promotion Strategy (600 words) - Distribution channels and amplification
Section 6: Content Performance Analytics (400 words) - Metrics tracking and optimization

MANDATORY CONTENT:

Content pillars: email marketing tips, small business growth, automation best practices
12-month editorial calendar with 48+ blog post topics
Content creation templates and style guide
Distribution strategy: organic social, email newsletter, community sharing
Guest posting targets and partnership opportunities
Content ROI measurement and optimization framework

20.3 Help Center & Documentation SEO (`help-center-documentation-seo.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Help Center Architecture (800 words) - Information structure and navigation
Section 2: SEO-Optimized Documentation (800 words) - Keyword-targeted help articles
Section 3: Video & Visual Content Strategy (700 words) - Tutorial videos and screenshots
Section 4: User-Generated Content Integration (700 words) - Community Q&A and feedback
Section 5: Help Center Analytics & Optimization (600 words) - Usage tracking and improvements
Section 6: Support Content Automation (400 words) - AI-powered suggestions and chatbots

MANDATORY CONTENT:

Help article topics targeting support keywords: "how to send email", "create automation"
Video tutorial series for major features with SEO-optimized titles
FAQ section targeting common email marketing questions
Community forum integration for user-generated content
Search functionality within help center for improved UX
Help center analytics dashboard for content performance tracking

20.4 Organic Growth & Lead Generation (`organic-growth-lead-generation.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Organic Traffic Acquisition (800 words) - SEO, content, and referral strategies
Section 2: Lead Magnet Development (800 words) - Free resources and email capture
Section 3: Content-Driven Conversion Optimization (700 words) - Landing pages and CTAs
Section 4: Community Building & Engagement (700 words) - Social media and forum participation
Section 5: Partnership & Collaboration Strategy (600 words) - Guest posting and co-marketing
Section 6: Organic Growth Measurement (400 words) - Traffic, leads, and conversion tracking

MANDATORY CONTENT:

Lead magnets: email marketing templates, automation playbooks, industry reports
Content upgrade strategy for blog posts with relevant opt-ins
Social media content calendar aligned with SEO content
Community engagement plan: Reddit, Discord, LinkedIn groups
Guest posting target list with 20+ relevant publications
Organic growth funnel tracking: traffic → leads → trials → customers

PHASE 20 COMPLETION CHECKLIST

Before proceeding to Phase 26, Claude Code must verify:

ALL 10 WebSearch queries executed and documented with citations
4 markdown files created with exact word counts (16,000+ total words)
SEO keyword strategy developed with competitive analysis
Content marketing system established with editorial calendar
Help center architecture designed for SEO optimization
Organic growth strategy defined with lead generation framework
Technical SEO implementation plan specified for Next.js
Content creation workflows and templates documented
Community engagement strategy researched and planned
Organic growth measurement framework established

PROGRESSION TRIGGER: Phase 23 Complete - Proceed to Phase 24

PHASE 24: MARKETING LAUNCH & PROMOTION

Launch Marketing Context (Built on Phase 21 Content Foundation)

With SEO and content marketing foundation established, now execute comprehensive marketing launch campaign for maximum visibility and customer acquisition.

# Content Foundation from Phase 20
SEO_STRATEGY: "Keyword research and optimization framework established"
CONTENT_SYSTEM: "Editorial calendar and content creation workflows"
HELP_CENTER: "SEO-optimized documentation and tutorial content"
ORGANIC_GROWTH: "Lead generation and community engagement strategy"
CONTENT_READY: "Launch-ready content and promotional materials"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 21

Claude Code Instructions: Execute ALL 10 WebSearch queries below sequentially. Use results to create 4 comprehensive markdown documents. DO NOT PROCEED to Phase 22 until Phase 21 Complete checklist is satisfied.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Launch Campaign Research

Query 1: "SaaS product launch" marketing campaign strategy 2024 best practices
Query 2: "email marketing platform launch" case studies success stories
Query 3: "ProductHunt launch" strategy email marketing tools promotion

2. PR & Media Outreach Research

Query 4: "SaaS PR strategy" media outreach email marketing industry
Query 5: "startup press release" template email marketing platform launch
Query 6: "tech journalism" SaaS media list email marketing reporters

3. Community & Social Marketing Research

Query 7: "email marketing communities" Reddit Discord Slack promotion strategy
Query 8: "social media marketing" SaaS launch Twitter LinkedIn strategy
Query 9: "influencer marketing" email marketing industry partnerships
Query 10: "launch metrics" SaaS marketing campaign KPIs tracking

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

21.1 Product Launch Campaign Strategy (`product-launch-campaign-strategy.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Launch Strategy Overview (800 words) - Timeline, goals, and success metrics
Section 2: Pre-Launch Phase Planning (800 words) - Beta feedback, testimonials, waiting list
Section 3: Launch Week Execution (700 words) - Daily activities and promotional calendar
Section 4: Post-Launch Momentum (700 words) - Sustained marketing and growth activities
Section 5: Launch Asset Development (600 words) - Videos, graphics, copy, and materials
Section 6: Crisis Management & Contingency (400 words) - Backup plans and issue response

MANDATORY CONTENT:

30-day launch timeline with daily tasks and milestones
ProductHunt launch strategy with community preparation
Beta customer testimonial collection and case study development
Launch week social media calendar with platform-specific content
Email launch sequence for existing subscribers and waitlist
Launch day PR blitz with coordinated announcements

21.2 PR & Media Outreach Campaign (`pr-media-outreach-campaign.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Media Strategy & Positioning (800 words) - Key messages and story angles
Section 2: Media List & Journalist Outreach (800 words) - Target publications and contacts
Section 3: Press Release & Media Kit (700 words) - Professional PR materials development
Section 4: Influencer Partnership Strategy (700 words) - Industry expert collaboration
Section 5: Thought Leadership Content (600 words) - Expert positioning and commentary
Section 6: Media Relationship Building (400 words) - Long-term PR strategy

MANDATORY CONTENT:

Media target list: TechCrunch, VentureBeat, SaaS Magazine, MarTech Today
Press release template with NudgeCampaign launch announcement
Media kit with company info, founder bios, product screenshots
Influencer target list: email marketing experts, SaaS thought leaders
Podcast pitch strategy for marketing and entrepreneurship shows
Awards and recognition opportunities in SaaS and marketing categories

21.3 Community Marketing & Social Engagement (`community-marketing-social.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Community Engagement Strategy (800 words) - Platform-specific approaches
Section 2: Social Media Launch Campaign (800 words) - Content calendar and engagement
Section 3: Reddit & Forum Marketing (700 words) - Community participation and value-first approach
Section 4: Professional Network Activation (700 words) - LinkedIn, Twitter, industry groups
Section 5: User-Generated Content Campaign (600 words) - Customer stories and social proof
Section 6: Community Building & Moderation (400 words) - Long-term engagement strategy

MANDATORY CONTENT:

Reddit communities: r/entrepreneur, r/smallbusiness, r/SaaS, r/emailmarketing
Discord servers: Indie Hackers, SaaS Growth, Marketing communities
LinkedIn strategy: founder content, company page, group participation
Twitter launch campaign with hashtag strategy and engagement
Customer success story campaign with social sharing incentives
Community guidelines and moderation policies for brand communities

21.4 Launch Analytics & Performance Tracking (`launch-analytics-tracking.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Launch Metrics Framework (800 words) - KPIs and success measurement
Section 2: Analytics Implementation (800 words) - Tracking setup and attribution
Section 3: Campaign Performance Analysis (700 words) - Real-time monitoring and optimization
Section 4: Media Mention & Sentiment Tracking (700 words) - Brand awareness measurement
Section 5: Customer Acquisition Attribution (600 words) - Channel performance and ROI
Section 6: Launch Report & Optimization (400 words) - Post-launch analysis and learnings

MANDATORY CONTENT:

Launch KPIs: website traffic, trial signups, media mentions, social engagement
Google Analytics setup with UTM tracking for all campaign links
Social media analytics dashboard for engagement and reach tracking
Brand mention monitoring tools: Google Alerts, Mention, Brand24
Customer acquisition cost (CAC) tracking by channel and campaign
Launch performance report template with actionable insights

PHASE 21 COMPLETION CHECKLIST

Before proceeding to Phase 26, Claude Code must verify:

ALL 10 WebSearch queries executed and documented with citations
4 markdown files created with exact word counts (16,000+ total words)
Product launch campaign strategy developed with detailed timeline
PR and media outreach plan established with target list
Community marketing strategy designed for platform-specific engagement
Launch analytics framework implemented with tracking setup
Media kit and press materials developed for professional outreach
Social media launch campaign planned with content calendar
Influencer partnership strategy researched and documented
Launch performance measurement system established

PROGRESSION TRIGGER: Phase 24 Complete - Proceed to Phase 25

PHASE 25: CUSTOMER SUCCESS & RETENTION

Customer Success Context (Built on Phase 22 Launch Campaign)

With marketing launch campaign executed, now focus on customer success optimization and retention strategies to maximize customer lifetime value.

# Launch Campaign from Phase 21
LAUNCH_EXECUTED: "Marketing campaign completed with customer acquisition"
MEDIA_COVERAGE: "PR outreach and brand awareness campaign"
COMMUNITY_ENGAGEMENT: "Social media and community marketing active"
PERFORMANCE_TRACKING: "Launch analytics and attribution measurement"
CUSTOMER_ACQUISITION: "Initial customer base established through launch"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 22

Claude Code Instructions: Execute ALL 10 WebSearch queries below sequentially. Use results to create 4 comprehensive markdown documents. DO NOT PROCEED to Phase 23 until Phase 22 Complete checklist is satisfied.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Customer Success Strategy Research

Query 1: "SaaS customer success" best practices onboarding retention 2024
Query 2: "email marketing customer success" user adoption strategies
Query 3: "customer health scoring" SaaS metrics retention prediction

2. Retention Optimization Research

Query 4: "SaaS churn reduction" strategies email marketing platform
Query 5: "customer retention metrics" lifecycle management best practices
Query 6: "proactive customer success" intervention strategies SaaS

3. Customer Experience Research

Query 7: "customer onboarding optimization" SaaS email marketing tools
Query 8: "customer support" help desk integration success metrics
Query 9: "customer feedback loop" product improvement strategies
Query 10: "customer advocacy" referral programs SaaS case studies

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

22.1 Customer Success Strategy & Framework (`customer-success-strategy.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Customer Success Philosophy (800 words) - Strategy and organizational approach
Section 2: Customer Journey Mapping (800 words) - Lifecycle stages and touchpoints
Section 3: Success Metrics & KPIs (700 words) - Health scoring and retention indicators
Section 4: Customer Segmentation Strategy (700 words) - Tiered success approaches
Section 5: Success Team Structure (600 words) - Roles, responsibilities, and workflows
Section 6: Technology & Tool Integration (400 words) - Customer success platform setup

MANDATORY CONTENT:

Customer lifecycle stages: onboarding, adoption, expansion, renewal, advocacy
Health score components: login frequency, feature usage, support tickets, billing status
Customer segmentation: enterprise, SMB, startup, industry-specific approaches
Success milestones: first email sent, automation created, campaign results
Proactive outreach triggers and intervention strategies
Customer success metrics benchmarked against industry standards

22.2 Advanced Onboarding & User Adoption (`advanced-onboarding-adoption.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Onboarding Experience Optimization (800 words) - First 30 days journey design
Section 2: Progressive Feature Introduction (800 words) - Gradual complexity and capability
Section 3: Personalized Learning Paths (700 words) - Role-based and industry-specific guidance
Section 4: Interactive Tutorial System (700 words) - In-app guidance and video training
Section 5: Onboarding Success Measurement (600 words) - Completion rates and time-to-value
Section 6: Onboarding Optimization Testing (400 words) - A/B testing and improvement cycles

MANDATORY CONTENT:

Day 1: Account setup, first email template selection, contact import
Week 1: First email campaign creation and sending
Week 2: Automation workflow setup and basic segmentation
Month 1: Advanced features introduction and optimization
Personalized paths for small business, SaaS, e-commerce personas
Video tutorial library with progress tracking and completion metrics

22.3 Retention Analytics & Churn Prevention (`retention-analytics-churn-prevention.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Churn Analysis & Prediction (800 words) - Risk identification and early warning systems
Section 2: Retention Metrics Dashboard (800 words) - Cohort analysis and retention curves
Section 3: Proactive Intervention Strategies (700 words) - At-risk customer engagement
Section 4: Win-Back Campaign Framework (700 words) - Re-engagement and reactivation
Section 5: Retention Optimization Testing (600 words) - Experimental approaches to improve retention
Section 6: Churn Feedback Analysis (400 words) - Exit interview insights and product improvements

MANDATORY CONTENT:

Churn prediction model using usage patterns and engagement metrics
Monthly cohort retention analysis with benchmarks (month 1: 90%, month 6: 70%)
At-risk customer identification: declining usage, support tickets, billing issues
Win-back email sequences for churned customers with special offers
Retention A/B tests: onboarding variations, feature announcements, support touchpoints
Churn reason categorization: price, features, complexity, competition, company changes

22.4 Customer Advocacy & Referral Programs (`customer-advocacy-referrals.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Customer Advocacy Strategy (800 words) - Identification and cultivation of advocates
Section 2: Referral Program Design (800 words) - Incentive structure and program mechanics
Section 3: Case Study Development Process (700 words) - Success story documentation and promotion
Section 4: Review & Testimonial Campaign (700 words) - Social proof collection and display
Section 5: Community Building & Engagement (600 words) - User groups and peer-to-peer support
Section 6: Advocacy ROI Measurement (400 words) - Program effectiveness and optimization

MANDATORY CONTENT:

Advocate identification criteria: product usage, satisfaction scores, engagement levels
Referral incentives: account credits, extended trials, premium features
Case study template with before/after metrics and specific results
Review collection automation for G2, Capterra, Trustpilot
Customer community platform with peer support and networking
Advocacy program metrics: referral conversion, case study impact, review scores

PHASE 22 COMPLETION CHECKLIST

Before proceeding to Phase 26, Claude Code must verify:

ALL 10 WebSearch queries executed and documented with citations
4 markdown files created with exact word counts (16,000+ total words)
Customer success strategy framework established with lifecycle mapping
Advanced onboarding system designed with progressive feature introduction
Retention analytics and churn prevention strategies documented
Customer advocacy and referral programs designed with incentive structure
Customer health scoring system defined with proactive intervention triggers
Onboarding optimization framework established with A/B testing approach
Churn analysis model developed with prediction and prevention strategies
Case study development process and review collection campaigns planned

PROGRESSION TRIGGER: Phase 25 Complete - Proceed to Phase 26

PHASE 26: GROWTH & SCALING OPERATIONS

Scaling Context (Built on Phase 23 Customer Success)

With customer success and retention systems operational, now focus on sustainable growth strategies and operational scaling to handle increased demand.

# Customer Success Foundation from Phase 22
CUSTOMER_SUCCESS: "Success strategy and framework operational"
ONBOARDING_OPTIMIZED: "Advanced onboarding with user adoption tracking"
RETENTION_ANALYTICS: "Churn prevention and retention optimization"
ADVOCACY_PROGRAMS: "Customer advocacy and referral systems active"
CUSTOMER_LIFETIME_VALUE: "Retention strategies maximizing CLV"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 23

Claude Code Instructions: Execute ALL 10 WebSearch queries below sequentially. Use results to create 4 comprehensive markdown documents. DO NOT PROCEED to Phase 24 until Phase 23 Complete checklist is satisfied.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Growth Strategy Research

Query 1: "SaaS growth hacking" strategies email marketing platform scaling
Query 2: "viral growth loops" SaaS referral program optimization
Query 3: "product-led growth" email marketing tool strategies

2. Operational Scaling Research

Query 4: "SaaS operations scaling" team growth infrastructure automation
Query 5: "customer support scaling" help desk automation SaaS
Query 6: "infrastructure scaling" cloud architecture performance optimization

3. Performance & Efficiency Research

Query 7: "SaaS team scaling" hiring remote development operations
Query 8: "process automation" workflow optimization SaaS operations
Query 9: "performance monitoring" SaaS platform scalability metrics
Query 10: "growth metrics" SaaS KPIs scaling benchmarks optimization

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

23.1 Growth Hacking & Viral Mechanics (`growth-hacking-viral-mechanics.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Growth Hacking Strategy Framework (800 words) - Systematic approach to growth experiments
Section 2: Viral Loop Design & Implementation (800 words) - Self-reinforcing growth mechanisms
Section 3: Product-Led Growth Optimization (700 words) - In-product growth features and hooks
Section 4: Growth Experiment Framework (700 words) - Testing and optimization methodology
Section 5: Channel Optimization & Expansion (600 words) - Multi-channel growth strategies
Section 6: Growth Analytics & Attribution (400 words) - Measuring and optimizing growth channels

MANDATORY CONTENT:

Growth loop mechanics: invite flows, referral tracking, network effects
Product-led growth features: sharing capabilities, collaboration tools, public profiles
Growth experiment pipeline: hypothesis, test design, measurement, iteration
Channel expansion: paid advertising, partnership marketing, affiliate programs
Growth metrics: K-factor, viral coefficient, time to activation, growth rate
A/B testing framework for growth features and conversion optimization

23.2 Team & Infrastructure Scaling (`team-infrastructure-scaling.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Team Scaling Strategy (800 words) - Hiring plan and organizational structure
Section 2: Infrastructure Scaling Architecture (800 words) - Technical scalability and performance
Section 3: Development Team Expansion (700 words) - Engineering hiring and onboarding
Section 4: Customer Success Team Growth (700 words) - Support and success team scaling
Section 5: Process Automation & Efficiency (600 words) - Workflow optimization and tooling
Section 6: Quality Assurance & Compliance (400 words) - Maintaining standards during growth

MANDATORY CONTENT:

12-month hiring plan: engineering, customer success, marketing, sales roles
Infrastructure auto-scaling: cloud resources, database optimization, CDN
Remote team management: collaboration tools, communication protocols
Customer support scaling: ticket automation, knowledge base, self-service
Process documentation: development workflows, customer success playbooks
Performance monitoring: application metrics, infrastructure alerts, SLA tracking

23.3 Process Automation & Operational Efficiency (`process-automation-efficiency.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Workflow Automation Strategy (800 words) - Business process optimization
Section 2: Customer Success Automation (800 words) - Automated onboarding and health monitoring
Section 3: Marketing & Sales Automation (700 words) - Lead nurturing and conversion optimization
Section 4: Development Process Automation (700 words) - CI/CD optimization and testing automation
Section 5: Data & Analytics Automation (600 words) - Automated reporting and insights
Section 6: Compliance & Security Automation (400 words) - Automated security and compliance checks

MANDATORY CONTENT:

Automated customer health scoring and at-risk identification
Marketing automation: lead scoring, email sequences, campaign optimization
Development automation: code deployment, testing, monitoring, alerts
Reporting automation: business metrics, customer analytics, financial reports
Security automation: vulnerability scanning, access management, audit trails
Tool integration: Zapier workflows, API automation, data synchronization

23.4 Performance Monitoring & Optimization (`performance-monitoring-optimization.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Application Performance Monitoring (800 words) - Real-time performance tracking
Section 2: Infrastructure Performance Optimization (800 words) - Scalability and reliability
Section 3: Customer Experience Monitoring (700 words) - User experience and satisfaction tracking
Section 4: Business Performance Analytics (700 words) - KPI tracking and optimization
Section 5: Predictive Performance Analysis (600 words) - Forecasting and capacity planning
Section 6: Performance Optimization Workflows (400 words) - Continuous improvement processes

MANDATORY CONTENT:

Application monitoring: response times, error rates, throughput, availability
Infrastructure metrics: CPU, memory, disk, network, database performance
User experience tracking: page load times, feature usage, error encounters
Business KPIs: growth rate, churn, CAC, LTV, feature adoption, support metrics
Capacity planning: traffic forecasting, resource allocation, scaling triggers
Performance optimization cycles: monitoring, analysis, implementation, validation

PHASE 23 COMPLETION CHECKLIST

Before proceeding to Phase 26, Claude Code must verify:

ALL 10 WebSearch queries executed and documented with citations
4 markdown files created with exact word counts (16,000+ total words)
Growth hacking strategy developed with viral mechanics and product-led features
Team and infrastructure scaling plan established with hiring roadmap
Process automation framework designed for operational efficiency
Performance monitoring system specified with optimization workflows
Growth experiment pipeline defined with testing and measurement
Team scaling strategy documented with role definitions and hiring plan
Automation tools and workflows identified for process optimization
Performance benchmarks and KPIs established for scaling monitoring

PROGRESSION TRIGGER: Phase 26 Complete - Proceed to Phase 27

PHASE 27: PRODUCT ITERATION & ENHANCEMENT

Product Evolution Context (Built on Phase 24 Scaling Operations)

With growth and scaling operations in place, now focus on continuous product iteration and enhancement based on user feedback and market demands.

# Scaling Foundation from Phase 23
GROWTH_STRATEGIES: "Growth hacking and viral mechanics operational"
TEAM_SCALING: "Infrastructure and team expansion framework"
AUTOMATION_SYSTEMS: "Process automation and operational efficiency"
PERFORMANCE_MONITORING: "Monitoring and optimization systems active"
OPERATIONAL_EXCELLENCE: "Scalable operations supporting growth"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 24

Claude Code Instructions: Execute ALL 10 WebSearch queries below sequentially. Use results to create 4 comprehensive markdown documents. DO NOT PROCEED to Phase 25 until Phase 24 Complete checklist is satisfied.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Product Management Research

Query 1: "product iteration" SaaS development cycle user feedback prioritization
Query 2: "feature prioritization" email marketing platform user requests roadmap
Query 3: "A/B testing" product features email marketing optimization

2. User Research & Feedback Research

Query 4: "user feedback analysis" SaaS product improvement insights
Query 5: "customer interview" product development email marketing tools
Query 6: "user behavior analytics" feature usage optimization SaaS

3. Competitive Enhancement Research

Query 7: "competitive feature analysis" email marketing ActiveCampaign Mailchimp
Query 8: "product roadmap" SaaS feature planning market trends
Query 9: "technical debt management" SaaS platform maintenance scaling
Query 10: "innovation pipeline" email marketing new features trends 2024

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

24.1 Product Iteration Framework & Roadmap (`product-iteration-roadmap.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Product Iteration Philosophy (800 words) - Continuous improvement approach
Section 2: Feature Prioritization Framework (800 words) - Decision-making process for feature development
Section 3: Quarterly Roadmap Planning (700 words) - Strategic planning and milestone setting
Section 4: Cross-Functional Collaboration (700 words) - Team coordination and communication
Section 5: Release Planning & Management (600 words) - Feature rollout and deployment strategy
Section 6: Roadmap Communication Strategy (400 words) - Customer and stakeholder updates

MANDATORY CONTENT:

RICE prioritization framework: Reach, Impact, Confidence, Effort scoring
Quarterly OKRs aligned with business goals and customer needs
Feature request tracking system with customer voting and feedback
Cross-functional sprint planning with engineering, design, and customer success
Feature flag system for gradual rollouts and A/B testing
Public roadmap communication with transparency and regular updates

24.2 User Feedback Analysis & Implementation (`user-feedback-analysis.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Feedback Collection System (800 words) - Multi-channel feedback gathering
Section 2: User Research Methodology (800 words) - Interviews, surveys, and behavioral analysis
Section 3: Feedback Analysis & Categorization (700 words) - Pattern recognition and insight extraction
Section 4: Feature Request Validation (700 words) - Market demand assessment and feasibility analysis
Section 5: Implementation Planning (600 words) - Design and development workflow
Section 6: Feedback Loop Closure (400 words) - Customer communication and follow-up

MANDATORY CONTENT:

In-app feedback widgets with context and feature-specific prompts
Customer interview program with monthly sessions and structured questions
Feedback categorization: bugs, feature requests, UX improvements, integrations
User story creation from feedback with acceptance criteria and success metrics
Feature validation through prototypes and user testing sessions
Closed-loop feedback communication with customers about implemented features

24.3 Competitive Feature Analysis & Innovation (`competitive-analysis-innovation.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Competitive Intelligence System (800 words) - Ongoing competitor monitoring
Section 2: Feature Gap Analysis (800 words) - Identifying opportunities and differentiators
Section 3: Innovation Pipeline Development (700 words) - Emerging trends and technology adoption
Section 4: Competitive Positioning Strategy (700 words) - Market differentiation and unique value
Section 5: Technology Trend Integration (600 words) - AI, automation, and industry innovations
Section 6: Innovation Validation Framework (400 words) - Testing new concepts and ideas

MANDATORY CONTENT:

Competitor feature matrix: ActiveCampaign, Mailchimp, ConvertKit, Klaviyo updates
Quarterly competitive analysis reports with feature comparisons
Innovation ideas: AI-powered email optimization, advanced personalization, predictive analytics
Market trend monitoring: email marketing regulations, privacy updates, technology shifts
Prototype development process for innovative features and concepts
Customer validation of innovative features through beta testing and feedback

24.4 Technical Debt Management & Platform Enhancement (`technical-debt-platform-enhancement.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Technical Debt Assessment (800 words) - Code quality and maintenance needs
Section 2: Platform Optimization Strategy (800 words) - Performance improvements and scalability
Section 3: Security Enhancement Program (700 words) - Ongoing security improvements and compliance
Section 4: Integration Expansion Plan (700 words) - New integrations and API enhancements
Section 5: Development Efficiency Improvements (600 words) - Tooling and workflow optimization
Section 6: Quality Assurance Evolution (400 words) - Testing improvements and automation

MANDATORY CONTENT:

Technical debt tracking: code complexity, test coverage, documentation gaps
Performance optimization: database queries, API response times, page load speeds
Security improvements: vulnerability patching, compliance updates, access controls
Integration roadmap: Shopify, WordPress, Zapier, CRM platforms, analytics tools
Development tooling: automated testing, code review processes, deployment automation
Quality metrics: code coverage, bug rates, performance benchmarks, security scores

PHASE 24 COMPLETION CHECKLIST

Before proceeding to Phase 26, Claude Code must verify:

ALL 10 WebSearch queries executed and documented with citations
4 markdown files created with exact word counts (16,000+ total words)
Product iteration framework established with prioritization methodology
User feedback analysis system designed with research and implementation workflows
Competitive analysis and innovation pipeline developed with trend monitoring
Technical debt management strategy documented with platform enhancement plan
Feature prioritization framework implemented with RICE scoring methodology
Customer feedback collection and analysis system established
Competitive intelligence monitoring and innovation validation processes defined
Technical debt tracking and quality improvement programs documented

PROGRESSION TRIGGER: Phase 27 Complete - Proceed to Phase 28

PHASE 28: MARKET LEADERSHIP & INNOVATION

Market Leadership Context (Built on Phase 25 Product Enhancement)

With continuous product iteration and enhancement systems operational, now establish market leadership position and drive industry innovation.

# Product Enhancement Foundation from Phase 24
ITERATION_FRAMEWORK: "Product improvement and roadmap planning system"
FEEDBACK_SYSTEMS: "User research and feedback analysis workflows"
COMPETITIVE_INTELLIGENCE: "Market monitoring and innovation pipeline"
TECHNICAL_EXCELLENCE: "Platform optimization and technical debt management"
CONTINUOUS_IMPROVEMENT: "Quality assurance and development efficiency"

AUTONOMOUS EXECUTION PROTOCOL FOR PHASE 25

Claude Code Instructions: Execute ALL 10 WebSearch queries below sequentially. Use results to create 4 comprehensive markdown documents. This is the FINAL PHASE of the autonomous research system.

MANDATORY WEBSEARCH QUERIES - EXECUTE IN ORDER

1. Market Leadership Research

Query 1: "SaaS market leadership" email marketing industry positioning strategies
Query 2: "thought leadership" email marketing expert positioning content strategy
Query 3: "industry awards" SaaS email marketing recognition programs

2. Innovation Strategy Research

Query 4: "email marketing innovation" AI automation future trends 2024 2025
Query 5: "SaaS innovation labs" R&D product development strategies
Query 6: "emerging technologies" email marketing blockchain AI machine learning

3. Strategic Expansion Research

Query 7: "SaaS market expansion" international growth strategies
Query 8: "enterprise sales" email marketing platform B2B strategies
Query 9: "strategic partnerships" email marketing ecosystem integrations
Query 10: "exit strategies" SaaS acquisition IPO preparation email marketing

DELIVERABLE SPECIFICATIONS - CREATE 4 MARKDOWN FILES

25.1 Market Leadership & Thought Leadership Strategy (`market-leadership-strategy.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Market Leadership Philosophy (800 words) - Vision for industry leadership and impact
Section 2: Thought Leadership Content Strategy (800 words) - Expert positioning and content creation
Section 3: Industry Recognition & Awards (700 words) - Award strategies and recognition programs
Section 4: Conference & Event Strategy (700 words) - Speaking engagements and event participation
Section 5: Media Relations & PR Strategy (600 words) - Ongoing media presence and expert positioning
Section 6: Leadership Measurement & Impact (400 words) - Tracking influence and market position

MANDATORY CONTENT:

Thought leadership topics: email marketing trends, privacy regulations, AI automation
Content strategy: research reports, industry whitepapers, trend predictions
Award targets: SaaS awards, marketing technology awards, startup competitions
Conference speaking strategy: MarTech, SaaStr, email marketing events
Media relationship building with industry publications and podcasts
Leadership KPIs: media mentions, speaking invitations, award recognition

25.2 Innovation Labs & Future Technology (`innovation-labs-future-tech.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: Innovation Lab Strategy (800 words) - R&D approach and experimental framework
Section 2: Emerging Technology Integration (800 words) - AI, ML, blockchain applications
Section 3: Future Email Marketing Trends (700 words) - Industry evolution and technology adoption
Section 4: Experimental Feature Development (700 words) - Beta features and innovation testing
Section 5: Technology Partnership Strategy (600 words) - Collaboration with tech companies and startups
Section 6: Innovation ROI & Measurement (400 words) - Measuring innovation impact and success

MANDATORY CONTENT:

AI-powered features: email optimization, send time prediction, content generation
Machine learning applications: customer behavior prediction, churn prevention, personalization
Emerging trends: voice email, interactive content, privacy-first marketing
Innovation pipeline: idea generation, prototyping, validation, implementation
Technology partnerships: AI companies, analytics platforms, emerging startups
Innovation metrics: feature adoption, customer satisfaction, competitive advantage

25.3 Strategic Market Expansion (`strategic-market-expansion.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: International Expansion Strategy (800 words) - Global market entry and localization
Section 2: Enterprise Market Penetration (800 words) - B2B sales and enterprise features
Section 3: Vertical Market Specialization (700 words) - Industry-specific solutions and targeting
Section 4: Strategic Partnership Development (700 words) - Ecosystem partnerships and integrations
Section 5: Acquisition & Merger Opportunities (600 words) - Growth through strategic acquisitions
Section 6: Expansion Risk Management (400 words) - Risk assessment and mitigation strategies

MANDATORY CONTENT:

International markets: Europe (GDPR compliance), Asia-Pacific, Latin America
Enterprise features: advanced automation, custom integrations, dedicated support
Vertical solutions: e-commerce, SaaS, professional services, non-profit
Partnership opportunities: agencies, consultants, technology integrators
Acquisition targets: complementary technologies, customer bases, talent
Expansion metrics: market penetration, revenue growth, customer acquisition

25.4 Long-Term Strategic Planning & Exit Strategy (`long-term-strategic-planning.md`)

WORD COUNT: Exactly 4,000+ words
STRUCTURE REQUIREMENTS:

Section 1: 5-Year Strategic Vision (800 words) - Long-term company direction and goals
Section 2: Competitive Moat Development (800 words) - Sustainable competitive advantages
Section 3: Financial Growth Projections (700 words) - Revenue forecasting and valuation modeling
Section 4: Exit Strategy Options (700 words) - IPO preparation vs acquisition scenarios
Section 5: Legacy & Impact Planning (600 words) - Industry influence and lasting contributions
Section 6: Succession & Leadership Development (400 words) - Leadership transition and continuity

MANDATORY CONTENT:

5-year vision: market position, revenue targets, customer base, team size
Competitive advantages: technology moat, customer loyalty, brand recognition
Financial projections: $100M ARR pathway, valuation scenarios, profitability timeline
Exit scenarios: IPO readiness checklist, acquisition preparation, strategic buyer analysis
Industry impact: email marketing evolution, best practices, thought leadership legacy
Leadership development: succession planning, team growth, company culture

PHASE 25 COMPLETION CHECKLIST

Final Phase - Market Leadership Established:

ALL 10 WebSearch queries executed and documented with citations
4 markdown files created with exact word counts (16,000+ total words)
Market leadership strategy developed with thought leadership positioning
Innovation labs framework established with future technology integration
Strategic market expansion plan documented with international and enterprise focus
Long-term strategic planning completed with exit strategy options
Thought leadership content strategy and industry recognition programs defined
Innovation pipeline and emerging technology adoption framework established
Market expansion risk assessment and partnership development strategies documented
5-year strategic vision and competitive moat development plans completed

FINAL PROGRESSION: Phase 25 Complete - Autonomous Research System Complete

COMPREHENSIVE POST-LAUNCH DOCUMENTATION SUMMARY

Total Phases 18-28 Output (11 Phases, 44+ Files, 176,000+ Words)

Phase 18: Payment Integration (4 files, 16,000 words)

Stripe integration with comprehensive billing automation
Monetization strategy with competitive pricing tiers
Revenue analytics and customer portal for self-service management

Phase 19: Support Materials Production (4 files, 16,000 words)

Customer support documentation and help center
Training materials and user onboarding resources
Knowledge base and FAQ system development

Phase 20: Testing & Validation (4 files, 16,000 words)

Comprehensive testing strategy and automation
Performance validation and load testing
Quality assurance and bug tracking systems

Phase 21: Security Compliance (4 files, 16,000 words)

Security compliance frameworks and certifications
Data protection and privacy policy implementation
Security monitoring and incident response procedures

Phase 22: Beta Customer Acquisition (4 files, 16,000 words)

Beta customer acquisition strategy and community engagement
Product-market fit validation framework with industry benchmarks
Feedback collection and early customer success programs

Phase 23: SEO & Content Marketing (4 files, 16,000 words)

SEO strategy with keyword research and competitor analysis
Content marketing system with editorial calendar and lead generation
Help center optimization and organic growth strategies

Phase 24: Marketing Launch (4 files, 16,000 words)

Product launch campaign with PR and media outreach
Community marketing and social engagement strategies
Launch analytics and performance tracking systems

Phase 25: Customer Success (4 files, 16,000 words)

Customer success framework with health scoring and lifecycle management
Advanced onboarding with personalized learning paths
Retention analytics with churn prevention and advocacy programs

Phase 26: Growth & Scaling (4 files, 16,000 words)

Growth hacking strategies with viral mechanics and product-led growth
Team and infrastructure scaling with process automation
Performance monitoring and operational efficiency optimization

Phase 27: Product Iteration (4 files, 16,000 words)

Product iteration framework with user feedback analysis
Competitive intelligence and innovation pipeline development
Technical debt management and platform enhancement strategies

Phase 28: Market Leadership (4 files, 16,000 words)

Market leadership and thought leadership positioning strategies
Innovation labs with emerging technology integration
Strategic market expansion and long-term planning with exit strategies

COMPLETE FRAMEWORK SUMMARY (28 Phases, 120+ Files, 480,000+ Words)

Pre-Launch Research & Development (Phases 1-17): 74 files, 299,500+ words

Comprehensive market research and competitive analysis
Technical architecture and MVP development
Design system and user experience optimization
Quality assurance and launch preparation

Post-Launch Growth & Leadership (Phases 18-28): 44+ files, 176,000+ words

Customer acquisition and monetization systems
Marketing and growth optimization strategies
Operational scaling and product enhancement
Market leadership and long-term strategic planning

USING THE COMPLETE 28-PHASE FRAMEWORK

Sequential Execution: Complete all phases 1-17 before launching, then execute phases 18-28 post-launch
Research-Driven Approach: Every decision backed by comprehensive WebSearch research and competitor analysis
Quality Gates: Each phase has completion criteria ensuring thoroughness before progression
Scalable Operations: Framework designed to support growth from startup to market leader
Continuous Improvement: Built-in feedback loops and optimization throughout all phases

This complete 28-phase framework provides a comprehensive roadmap from initial problem discovery through market leadership, ensuring research-validated decisions and systematic execution at every stage of company development.