Preseed Workflow
Transform your rough idea into comprehensive documentation before writing a single line of code.
Overview#
The Preseed workflow is the foundational first step in building any product. It takes a rough idea and systematically transforms it into structured documentation that serves as the foundation for everything that follows.
Preseed → Seed → Launch → Growth → Scale
Most projects fail not because of bad code, but because of unclear foundations:
- Problem not validated
- Audience undefined
- Market unknown
- Business model unclear
- Requirements scattered
Preseed solves this by generating all foundational documents from minimal input.
What You'll Create#
By completing the Preseed workflow, you'll have:
| Document | Purpose | Time Invested |
|---|---|---|
| Vision Document | Problem/solution foundation | Essential |
| Target Audience | Personas and ICP definition | Essential |
| Market Analysis | TAM/SAM/SOM sizing | Recommended |
| Competitive Analysis | Landscape and positioning | Recommended |
| Business Model | Revenue model and pricing | Essential |
| Product Requirements | User stories and MVP scope | Essential |
| Technical Spec | Architecture decisions | Optional |
| Roadmap | Development phases | Recommended |
Quick Start#
Recommended: Use the smart entry point:
This will:
- Check for files in your drop zone
- Offer to analyze existing materials
- Guide you to the appropriate next step
Alternative approaches:
The Drop Zone#
Don't know where to start? Use the drop zone:
The drop zone accepts any file type - PDFs, notes, screenshots, spreadsheets. Bootspring generates an AI-ready prompt that categorizes and extracts relevant information.
Learn more about the Drop Zone
Workflow Phases#
Phase 1: Idea Capture#
Duration: 15-30 minutes
The interactive wizard guides you through 8 structured sections:
- Project Identity - Name, tagline, category
- Problem Statement - Pain points and timing
- Solution Overview - Features and differentiation
- Target Audience - Segments and personas
- Market Opportunity - TAM/SAM/SOM
- Competitive Landscape - Direct and indirect competitors
- Business Model - Revenue streams and pricing
- Product Vision - MVP features and roadmap
Phase 2: Document Generation#
Duration: Automatic
Once you complete the wizard, Bootspring generates all documents:
.bootspring/
└── preseed/
├── PRESEED_CONFIG.json # Source of truth
├── VISION.md # Generated
├── AUDIENCE.md # Generated
├── MARKET.md # Generated
├── COMPETITORS.md # Generated
├── BUSINESS_MODEL.md # Generated
├── PRD.md # Generated
├── TECHNICAL_SPEC.md # Generated
└── ROADMAP.md # Generated
Phase 3: Refinement#
Duration: 1-2 hours
Review and refine your generated documents:
Phase 4: Validation#
Duration: 1-2 days
Validate your assumptions with real users before building:
- Share documents with potential users
- Conduct problem interviews
- Test pricing assumptions
- Refine based on feedback
Document Presets#
Choose the right preset for your needs:
| Preset | Documents | Best For |
|---|---|---|
essential | 4 | Quick validation, internal projects |
startup | 7 | Standard startup (default) |
full | 8 | Comprehensive documentation |
technical | 4 | Developer tools, API products |
investor | 6 | Fundraising preparation |
Preset Contents#
essential: vision, audience, business-model, prd
startup: vision, audience, market, competitors, business-model, prd, roadmap
full: all 8 documents
technical: vision, prd, technical-spec, roadmap
investor: vision, audience, market, competitors, business-model, roadmap
Living Documents#
Preseed creates "living documents" that evolve with your understanding:
- Config-driven: All data stored in
PRESEED_CONFIG.json - Regeneratable: Run
preseed syncanytime - Version tracked: Git-friendly format
- AI-friendly: Structured for Claude Code integration
Update Flow#
Integration with Seed#
Preseed flows seamlessly into the Seed workflow:
The Seed workflow will automatically:
- Import your PRD for feature generation
- Use your technical spec for architecture
- Apply your business model for pricing pages
- Reference your audience for UX decisions
Example Session#
Generated Document Examples#
Vision Document (VISION.md)#
Business Model (BUSINESS_MODEL.md)#
CLI Reference#
See the complete Preseed CLI Reference for all commands and options.
Essential Commands#
Best Practices#
1. Take Your Time on Phase 1#
The wizard questions are designed to extract clarity. Don't rush:
- Answer honestly, even if uncomfortable
- "I don't know" is a valid answer that gets addressed later
- Think from your customer's perspective
2. Review Before Refinement#
Read all generated documents before making changes:
- See how answers connect across documents
- Identify inconsistencies to fix
- Note gaps in your thinking
3. Version Control Your Preseed#
Track changes over time as your understanding evolves.
4. Validate Before Building#
Don't skip Phase 4:
- Share documents with 5+ potential users
- Conduct problem interviews
- Test willingness to pay
- Iterate on preseed before seed
Phase Guides#
Features#
- Drop Zone - Universal file inbox
- Context Folders - Organized input structure
- AI Prompts - Free tier prompt generation
- Cloud Sync - Dashboard synchronization
- Workflow Approval - Document approval process
Related#
- Seed Workflow - Build from your preseed
- Synthesize from Preseed - Create SEED.md
- Scaffold Presets - Framework presets
- CLI Preseed Reference - Full command reference