Skip to content

STRATEGIC_BLUEPRINT.md

Latest commit

 

History

History
90 lines (58 loc) · 2.54 KB

STRATEGIC_BLUEPRINT.md

File metadata and controls

90 lines (58 loc) · 2.54 KB

STRATEGIC BLUEPRINT: [Project Name]

Phase 1 Deliverable — This document must be 100% complete before writing any code. Use with the 7 Phase 1 Questions to validate completion.

1. THE CORE

  • Problem: [Specific, painful, measurable problem]
  • User: [Precise persona—e.g., "Solo SaaS Founders," not "Developers"]
  • Value Prop: [One sentence: How you solve it differently]

Implementation Implication: [How this constrains technical decisions]

2. ECONOMIC ENGINE

  • Pricing Model: [e.g., Freemium / Seat-based / Usage-based]
  • Unit Economics: [Cost per user vs. Revenue per user]
  • Distribution: [How you get your first 10 and first 100 users]

Implementation Implication: [How this affects architecture—e.g., "Client-side processing to minimize server costs"]

3. TECHNICAL ARCHITECTURE

  • The "Big Decision": [The one architectural choice that defines the system]
  • Stack Rationale: [Why these tools specifically?]
  • Data Model: [Core entities and their relationships]

Implementation Implication: [Specific technical constraints this creates]

4. EXECUTION SCOPE

  • MVP Must-Haves: [3-5 features only]

    1. [Feature 1]
    2. [Feature 2]
    3. [Feature 3]

  • Explicitly Deferred: [What you are NOT building yet—and why]

  • Risks: [Top 3 risks and mitigation strategies]

Implementation Implication: [What this means for Phase 2 specifications]

5. REFERENCES

Implementation Details Location

Content Type Location
Anti-patterns [Technical Spec, Section #]
Test Case Specifications [Testing Doc, Section #]
Error Handling Matrix [Error Handling Doc, Section #]

Replace with actual section numbers and add markdown anchor links.

Schema References

Topic Location Anchor
[Topic] [Path] [Anchor]

VALIDATION CHECKLIST

Before proceeding to Phase 2, verify:

  • All 7 Phase 1 Questions answered at "Require" level
  • Every section has an Implementation Implication
  • MVP scope is 3-5 features maximum
  • Deferred items are explicit with rationale
  • References point to (not duplicate) implementation details

Template from Stream Coding by Francesco Marinoni Moretto — CC BY 4.0