Master Plan Quick Checklist
This Week (Phase 0 Decisions): π΄ CRITICAL PATH
Full Plan: See Master Project Plan in Projects section
Your Decisions This Week (Glytcht)
π΄ Decision 1: Brick's Technical Specialty
Why: Templates his first articles, determines his voice in depth
Options:
- Backend
- DevOps / Infrastructure
- Full-stack
- Architecture
- Database design
- Other?
Action: Pick one, ParzivalTD will finalize his profile
Deadline: TODAY if possible
π΄ Decision 2: Initial Persona Roster (Personas 2β10)
Why: Determines content calendar, arc participants, expertise mix
Options: 5β10 people (real people you know, or we recruit during Phase 1?)
Action: Sketch out 5β9 personas (name, expertise, rough voice idea)
Deadline: End of Week 1
π΄ Decision 3: First Narrative Arc
Why: Drives all content scheduling and engagement
Options:
- PHP vs Node debate (Brick + Frontend persona clash)
- Learning journey (new persona builds in public)
- Collaboration (multiple personas build something together)
- Other?
Action: Pick arc, ParzivalTD will plan beats and content calendar
Deadline: End of Week 2
π΄ Decision 4: Revenue Model
Why: Dev team needs this to build payment processing
Options:
- Membership tiers (Free / $5/mo / $15/mo)
- Courses ($29β$99 each)
- Persona revenue share (70/30? 80/20?)
- Sponsorships?
Action: Rough numbers, ParzivalTD will detail it
Deadline: End of Week 3
π΄ Decision 5: Launch Target
Why: Everything else is scheduled around this
Options:
- Q3 2026 (JulyβSeptember)
- Q4 2026 (OctoberβDecember)
- Q1 2027 (JanuaryβMarch)
- Other?
Action: Commit to date, ParzivalTD will build sprint plan
Deadline: End of Week 4
ParzivalTD's Deliverables This Week
- β TekDek-Strategy.md
- β Tool-Requirements.md
- β Brick-Profile.md (stub)
- β TekDek-Brainstorm-Reference.md
- β TekDek-Master-Project-Plan.md
- [ ] Finalize Brick-Profile.md (pending Decision #1)
- [ ] Persona Template (for personas 2β10)
- [ ] Narrative Arc Template
- [ ] Content Curation Workflow doc
- [ ] Persona Roster System spec (design)
Phase 0 Timeline
| Week | Decision / Deliverable | Status |
|---|---|---|
| Week 1 | Decisions 1β2 locked, Brick finalized, 5 personas sketched | π΄ Now |
| Week 2 | Decision 3 locked, Arc 1 planned, content calendar drafted | β³ Next |
| Week 3 | Decision 4 locked, revenue model detailed | β³ Later |
| Week 4 | Decision 5 locked, all templates + specs done, dev team sync | β³ Later |
Phase Overview (Reference)
| Phase | Timeframe | Goal | Team Lead |
|---|---|---|---|
| Phase 0 | NOW β Week 4 | Lock decisions, design systems | TekDek (Glytcht) |
| Phase 1 | Week 5β12 | Build personas, test narrative, publish content | TekDek + Dev |
| Phase 2 | Week 13β16 | MVP launch, public beta, validate model | Dev (Portal launch) |
| Phase 3 | Week 17β24 | Scale to 10 personas, 2 verticals | TekDek (narrative expansion) |
| Phase 4 | Week 25+ | 3β5 verticals, 50+ personas, enterprise scale | Both teams |
Critical Success Factors (Phase by Phase)
Phase 0 β (This Week)
- Decisions locked
- Personas defined
- Arc 1 planned
- Dev team aligned
Phase 1 β (Week 5β12)
- Brick voice test (2β3 articles)
- 3 personas live
- Arc 1 live with content tied to beats
- APIs operational
- Go/No-Go for Phase 2 (Week 12)
Phase 2 β (Week 13β16)
- Stack Legion MVP public
- 500+ users
- Arc 1 generating engagement
- Revenue streams working
- Go/No-Go for Phase 3 (Week 16)
Phase 3 β (Week 17β24)
- 10 personas across 2 verticals
- Multiple arcs in parallel
- 10K+ monthly users
- Replication template proven
Phase 4 (Week 25+)
- 3β5 verticals live
- 50+ personas
- $50K+ monthly recurring revenue
Questions for Dev Team (First Sync)
- Tech stack? (Rails? Node? Django?)
- Realistic MVP launch date?
- Can you design APIs for persona data, content sync, analytics?
- What's the user scaling limit before we need microservices?
- Payment processing / revenue sharing capability?
- How do we integrate management system (OpenClaw) with portal?