NeuAIS Management Operations Plan: Marketing & Dev Teams

Date: December 5, 2025
Purpose: Operational structure for Marketing & Dev teams aligned with Platform Overhaul
Goal: Scale to 1000 agents, enterprise sales, and efficient operations

Executive Summary

The /mgmt directory currently has strong brand strategy and personas but lacks operational structure for marketing and dev teams to execute efficiently.

Proposal: Reorganize /mgmt into clear workflows, standardized processes, and automation-first operations that demonstrate our value proposition: eliminate toil.

Current State Analysis

What Exists ✅

• ✅ BRAND_STRATEGY.md - Excellent positioning (“minutes truth”)
• ✅ ENTERPRISE_PERSONAS.md - 5 detailed personas (CTO, CFO, VP Eng, CISO, Board)
• ✅ OPERATIONS_PLAN.md - Meeting frameworks, CRM structure, metrics
• ✅ EXECUTIVE_MESSAGING.md - Persona-specific messaging
• ⚠️ MARKETING_PLAN.md - Outdated (CloudNix focused, not neuais)

What’s Missing ❌

• ❌ Sales playbooks - /mgmt/sales/ is empty
• ❌ Marketing calendar - No content schedule
• ❌ Team operations - /mgmt/team-ops/ is empty
• ❌ Dev team processes - No engineering playbook
• ❌ CRM structure - /mgmt/crm/ is empty
• ❌ Customer tracking - No customer folders

Proposed Structure: /mgmt Reorganization

/mgmt/
├── README.md                          # Overview & navigation
├── TEAM_HANDBOOK.md                   # Combined team guide
│
├── brand/                             # Brand assets & strategy
│   ├── BRAND_STRATEGY.md             # ✅ Keep (excellent)
│   ├── ENTERPRISE_PERSONAS.md        # ✅ Keep (excellent)
│   ├── EXECUTIVE_MESSAGING.md        # ✅ Keep (excellent)
│   ├── brand-kit/
│   │   ├── BRAND_VOICE.md            # ✅ Keep
│   │   ├── logos/                    # Brand assets
│   │   ├── colors/                   # Color palette
│   │   └── templates/                # Pitch decks, one-pagers
│   └── messaging/                    # Persona-specific messaging
│       ├── cto-pitch.md
│       ├── cfo-pitch.md
│       ├── vp-eng-pitch.md
│       ├── ciso-pitch.md
│       └── board-pitch.md
│
├── marketing/                        # Marketing operations
│   ├── MARKETING_STRATEGY.md        # ⚠️ Update (neuais focus)
│   ├── CONTENT_CALENDAR.md          # NEW - Editorial calendar
│   ├── campaigns/                    # Campaign tracking
│   │   ├── 2025-q4-launch/
│   │   ├── 2026-q1-enterprise/
│   │   └── README.md
│   ├── content/                      # Content production
│   │   ├── blog/
│   │   ├── case-studies/
│   │   ├── whitepapers/
│   │   └── videos/
│   ├── analytics/                    # Performance tracking
│   │   ├── weekly-metrics.md
│   │   └── dashboard-config.yaml
│   └── tools/                        # Marketing tools & scripts
│       └── automation/
│
├── sales/                            # Sales operations
│   ├── SALES_PLAYBOOK.md            # NEW - Complete sales guide
│   ├── DEMO_SCRIPT.md               # NEW - Demo walkthrough
│   ├── OBJECTION_HANDLING.md        # NEW - Objections & responses
│   ├── PRICING.md                   # NEW - Pricing strategy
│   ├── demos/                        # Demo recordings & notes
│   │   └── COMPANY-DATE.md
│   ├── playbooks/                    # Persona-specific playbooks
│   │   ├── cto-playbook.md
│   │   ├── cfo-playbook.md
│   │   └── vp-eng-playbook.md
│   └── templates/                    # Email templates, proposals
│       ├── initial-outreach.md
│       ├── demo-followup.md
│       ├── pilot-proposal.md
│       └── contract-template.md
│
├── customers/                        # Customer tracking
│   ├── README.md                    # Customer folder guide
│   ├── COMPANY-A/
│   │   ├── overview.md              # Company info
│   │   ├── discovery-notes.md       # Initial conversations
│   │   ├── demo-YYYY-MM-DD.md      # Demo notes
│   │   ├── pilot/                   # Pilot program
│   │   │   ├── kickoff.md
│   │   │   ├── week-1-report.md
│   │   │   ├── week-2-report.md
│   │   │   ├── week-3-report.md
│   │   │   └── week-4-results.md
│   │   ├── contract.md              # Contract terms
│   │   └── ongoing/                 # Post-sale notes
│   └── TEMPLATE/                    # Template for new customers
│
├── dev-team/                        # Engineering operations
│   ├── ENGINEERING_HANDBOOK.md     # NEW - Dev processes
│   ├── ONBOARDING.md               # NEW - New engineer guide
│   ├── ARCHITECTURE_DECISIONS.md   # NEW - ADR log
│   ├── sprint-planning/             # Sprint docs
│   │   ├── 2025-w49/
│   │   └── README.md
│   ├── code-review/                 # Review guidelines
│   │   ├── GUIDELINES.md
│   │   └── CHECKLIST.md
│   ├── deployment/                  # Deployment docs
│   │   ├── RUNBOOK.md
│   │   └── ROLLBACK.md
│   └── incidents/                   # Incident postmortems
│       └── TEMPLATE.md
│
├── operations/                      # Business operations
│   ├── OPERATIONS_PLAN.md          # ✅ Keep (excellent)
│   ├── meetings/                    # Meeting notes
│   │   ├── weekly/
│   │   │   └── YYYY-MM-DD.md
│   │   ├── monthly-retro/
│   │   │   └── YYYY-MM.md
│   │   └── MEETING_GUIDELINES.md
│   ├── metrics/                     # Business metrics
│   │   ├── weekly-dashboard.md
│   │   ├── okrs/
│   │   └── targets.yaml
│   └── processes/                   # Standard processes
│       ├── hiring.md
│       ├── vendor-management.md
│       └── budget-planning.md
│
└── archive/                         # Old/deprecated docs
    ├── DOCS_OVERHAUL_STATUS.md     # Move here (outdated)
    ├── WEEK1_PROGRESS.md           # Move here (outdated)
    └── TEAM_BRIEFING.md            # Move here (outdated)

Marketing Team Operations

Team Structure

Current (Phase 1: Months 1-3)

• Marketing Lead (Founder role)
• Content Creator (Contractor, 20h/week)
• Designer (Contractor, 10h/week)

Growth (Phase 2: Months 4-6)

• Marketing Lead (Full-time)
• Content Marketing Manager (Full-time hire)
• Growth Marketer (Full-time hire)
• Designer (Contractor → Full-time)

Weekly Marketing Workflow

Monday: Planning

9:00 AM - Team standup (15 min, async)

• What shipped last week
• What ships this week
• Blockers

10:00 AM - Content planning (30 min)

• Review content calendar
• Assign pieces for the week
• Update campaign status

Actions:

• Update CONTENT_CALENDAR.md
• Assign content pieces in Linear
• Review analytics from last week

Tuesday-Thursday: Execution

Content Production Days

Daily routine:

• 9:00-12:00: Deep work (writing, design, video)
• 12:00-1:00: Review & feedback
• 1:00-5:00: Distribution & engagement

Outputs per week:

• 2 blog posts (1 technical, 1 thought leadership)
• 5 social posts (LinkedIn + Twitter)
• 1 newsletter
• 1 case study/video (monthly)

Friday: Analysis & Iteration

9:00 AM - Metrics review (30 min)

• Website traffic
• Demo requests
• Content performance
• Campaign ROI

10:00 AM - Next week prep (30 min)

• Schedule social posts
• Queue newsletter
• Prep campaign assets

Actions:

• Update weekly-metrics.md
• Schedule next week’s content
• Flag underperforming campaigns

Content Calendar (Rolling 4-Week View)

File: /mgmt/marketing/CONTENT_CALENDAR.md

# Content Calendar - Q4 2025

## Week of Dec 9-15, 2025

### Blog Posts
- [ ] **Mon Dec 9**: "The Minutes Truth: What Your Team Actually Spends Time On" 
  - Author: [Name]
  - Target: CTOs
  - CTA: Book demo
  - Distribution: LinkedIn, Twitter, Newsletter

- [ ] **Thu Dec 12**: "How 3 AI Agents Reduced Our Ops Costs by 71%"
  - Author: [Name]
  - Target: CFOs
  - CTA: ROI calculator
  - Distribution: LinkedIn, Hacker News, Newsletter

### Social Posts
- [ ] **Tue Dec 10**: LinkedIn - Share blog post with CTO messaging
- [ ] **Wed Dec 11**: Twitter - Thread on operational toil statistics
- [ ] **Thu Dec 12**: LinkedIn - Case study teaser
- [ ] **Fri Dec 13**: Twitter - Observatory 3D visualization demo GIF
- [ ] **Sat Dec 14**: LinkedIn - Weekend insight on minutes truth

### Other
- [ ] **Wed Dec 11**: Newsletter - "Weekly ops insights + blog roundup"
- [ ] **Fri Dec 13**: Record demo video for CTO persona

## Week of Dec 16-22, 2025
[Similar structure...]

## Performance Tracking
| Week | Blog Views | Demo Requests | Newsletter Opens |
|------|-----------|---------------|------------------|
| Dec 2-8 | 1,200 | 8 | 34% |
| Dec 9-15 | [TBD] | [TBD] | [TBD] |

Campaign Framework

File: /mgmt/marketing/campaigns/CAMPAIGN_TEMPLATE.md

# Campaign Name

**Duration**: [Start] - [End]  
**Goal**: [Specific measurable goal]  
**Budget**: $[X]  
**Owner**: [Name]

## Target Audience
- Primary: [Persona]
- Channels: [LinkedIn, Twitter, etc.]
- Expected reach: [X people]

## Assets Needed
- [ ] Landing page
- [ ] Email sequence (3 emails)
- [ ] Social creative (5 posts)
- [ ] Blog post
- [ ] Case study

## Distribution Schedule
| Date | Asset | Channel | Owner |
|------|-------|---------|-------|
| [Date] | Email 1 | Newsletter | [Name] |
| [Date] | Post 1 | LinkedIn | [Name] |

## Success Metrics
- Target: [X demo requests]
- Actual: [Y]
- ROI: $[cost per demo request]

## Learnings
[What worked, what didn't]

Dev Team Operations

Team Structure

Current (Phase 1: Months 1-3)

• Tech Lead (Founder)
• Full-Stack Engineer 1 (Full-time)
• Full-Stack Engineer 2 (Full-time)

Growth (Phase 2: Months 4-6)

• Tech Lead (Founder)
• Backend Team (2 engineers)
  • Focus: Services, API, agent runtime
• Frontend Team (2 engineers)
  • Focus: Dashboard, admin, docs site
• DevOps Engineer (1 engineer)
  • Focus: CI/CD, observability, scaling

Weekly Dev Workflow

Monday: Planning & Architecture

9:00 AM - Standup (15 min, async)

## [Engineer Name] - Week of [Date]

### Last Week Shipped
- [Feature X] - deployed to prod
- [Bug fix Y] - resolved

### This Week Plan
- [ ] [Feature A] - backend API
- [ ] [Feature B] - frontend UI
- [ ] [Refactor C] - improve performance

### Blockers
- Waiting on [X] from [person]
- Need design for [Y]

10:00 AM - Sprint planning (30 min)

• Review backlog
• Assign tickets
• Clarify requirements
• Update roadmap

Tuesday-Thursday: Execution & Code Review

Daily routine:

• 9:00-12:00: Deep work (feature development)
• 12:00-1:00: Code review (review others’ PRs)
• 1:00-4:00: Deep work (continued)
• 4:00-5:00: Testing & documentation

Code Review SLA:

• Small PRs (<200 lines): 2 hours
• Medium PRs (<500 lines): 4 hours
• Large PRs (>500 lines): 1 business day

Friday: Testing, Cleanup & Learning

9:00-11:00: Testing

• Integration tests
• E2E tests
• Performance testing

11:00-12:00: Code cleanup

• Fix clippy warnings
• Update documentation
• Refactor technical debt

1:00-3:00: Learning time

• Read RFCs/ADRs
• Experiment with new tools
• Contribute to open source
• Write blog posts

3:00-4:00: Week wrap-up

• Update sprint board
• Document decisions
• Plan next week

Engineering Processes

Pull Request Template

File: /mgmt/dev-team/code-review/PR_TEMPLATE.md

## Description
[What does this PR do?]

## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Refactoring
- [ ] Documentation
- [ ] Performance improvement

## Testing
- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manual testing completed
- [ ] Performance tested (if applicable)

## Checklist
- [ ] Code follows style guide
- [ ] Self-reviewed the code
- [ ] Added/updated documentation
- [ ] No clippy warnings
- [ ] Tests pass locally
- [ ] Ready for review

## Screenshots (if UI change)
[Add screenshots]

## Performance Impact
[Any performance considerations?]

## Deployment Notes
[Any special deployment steps?]

Architecture Decision Record (ADR) Template

File: /mgmt/dev-team/ARCHITECTURE_DECISIONS.md

# Architecture Decisions Log

## ADR-001: Split state.rs into Modular Components
**Date**: 2025-12-05  
**Status**: Implemented ✅  
**Context**: state.rs was 918 lines, hard to maintain and test  
**Decision**: Extract GraphicsContext, CameraControls into separate modules  
**Consequences**: 
- ✅ Better testability
- ✅ Clearer separation of concerns
- ⚠️ More files to navigate
**Result**: 13% code reduction, improved maintainability

---

## ADR-002: [Next Decision]
...

Sprint Planning Template

File: /mgmt/dev-team/sprint-planning/YYYY-WXX/sprint-plan.md

# Sprint W49 (Dec 2-8, 2025)

## Sprint Goal
Complete Observatory refactoring and begin Phase 3 data integration

## Team Capacity
- Engineer 1: 40 hours
- Engineer 2: 40 hours
- Tech Lead: 20 hours (50% on architecture)
**Total**: 100 engineering hours

## Committed Work

### High Priority (Must Ship)
- [ ] **[OBS-101]** Extract GraphicsContext module (8h) - @engineer1
- [ ] **[OBS-102]** Add CameraControls tests (4h) - @engineer2
- [ ] **[BACKEND-201]** Consolidate auth services (16h) - @techlead

### Medium Priority (Should Ship)
- [ ] **[DOCS-301]** Update docs.neuais.com structure (12h) - @engineer2
- [ ] **[OBS-103]** Fix clippy warnings (4h) - @engineer1

### Low Priority (Nice to Have)
- [ ] **[OBS-104]** Performance profiling (8h) - @engineer1

## Stretch Goals
- [ ] Begin WebSocket integration
- [ ] Add integration tests

## Risks
- Auth service migration might block dashboard dev
- Graphics refactoring might uncover bugs

## Retrospective (End of Sprint)
[What shipped, what didn't, why]

Team Collaboration Model

Marketing ↔ Dev Collaboration Points

Integration Point: /mgmt/operations/marketing-dev-sync.md

# Marketing ↔ Dev Sync - [Date]

## Upcoming Launches
- [Feature X] - Ready: [Date] - Marketing needs: [Assets]

## Content Needs
- [Blog post Y] - Dev to provide: [Code examples, metrics]

## Demo Status
- Demo environment: [Status]
- Known issues: [List]

## Actions
- [ ] Dev: Fix demo bug by [date]
- [ ] Marketing: Create launch assets by [date]

Automation Strategy (“Practice What We Preach”)

Phase 1: Manual Baseline (Month 1)

Establish processes, measure time spent

Phase 2: Semi-Automated (Months 2-3)

Automate repetitive tasks

Phase 3: Fully Automated (Months 4-6)

Deploy our own agents to manage operations

Result: From 42h/week → 16h/week operational work

This proves our thesis: We use our own agents to eliminate our own toil.

Marketing Strategy: neuais Focus (Updated)

Outdated: CloudNix Marketing Plan ❌

The current MARKETING_PLAN.md focuses on CloudNix (Nix-based cloud) which is not the current product.

Updated: neuais Marketing Strategy ✅

Product: Micro-AI agent platform for infrastructure cost reduction
Market: Enterprise DevOps (200-5000 employee companies)
Positioning: Autonomous operations (not monitoring, not cloud provider)

Marketing Channels (neuais-specific)

1. Enterprise Direct Sales (70% effort)

Target: CTO, CFO, VP Engineering at growth-stage companies

Tactics:

• LinkedIn outreach to target personas
• Conference speaking (KubeCon, DevOpsDays, SREcon)
• Thought leadership content (The Minutes Truth series)
• Executive roundtables
• Pilot programs with measurable ROI

KPIs:

• Demo requests: 20/month
• Pilot signups: 5/month
• Contracts signed: 2/month
• Average deal size: $120K/year

2. Technical Content (20% effort)

Target: DevOps engineers, SREs, platform engineers

Tactics:

• Technical blog posts (How Observatory works, Agent architecture)
• Open-source releases (Observatory, agent SDK)
• GitHub presence (stars, issues, community)
• Dev.to, Hacker News submissions
• Conference workshops

KPIs:

• GitHub stars: 500/month growth
• Blog traffic: 10K/month
• Developer signups: 100/month

3. Community Building (10% effort)

Target: Early adopters, champions, advocates

Tactics:

• Discord server (community support)
• Monthly webinars (deep dives)
• Customer case studies
• User conference (neuaisConf)

KPIs:

• Discord members: 1000
• Webinar attendees: 100/month
• Case studies published: 2/quarter

Content Themes & Cadence

Weekly Content (Published Every Week)

Monday: Technical Deep-Dive

• How agents work
• Architecture decisions
• Performance optimizations
• Code examples

Wednesday: Business Case

• ROI calculations
• Customer metrics
• Cost reduction stories
• Operational excellence

Friday: Philosophy

• The Minutes Truth
• The Sanctuary concept
• Work that matters vs. toil
• Leadership and legacy

Monthly Content (Once Per Month)

Week 1: Case Study

• Customer story
• Metrics (cost reduction, time saved)
• Before/after comparison
• Implementation guide

Week 2: Technical Guide

• How-to tutorial
• Best practices
• Common pitfalls
• Advanced techniques

Week 3: Research/Whitepaper

• Industry analysis
• Market trends
• Competitive analysis
• Future predictions

Week 4: Video/Webinar

• Product demo
• Customer interview
• Expert panel
• Q&A session

Campaign Calendar (Q4 2025 → Q2 2026)

Q4 2025: Foundation Launch

Dec 2025:

• ✅ Platform overhaul complete
• ✅ Documentation site live
• ✅ Observatory open-source release
• Launch campaign: “The Minutes Truth”

Goals:

• 20 demo requests
• 5 pilot signups
• 2 contracts signed
• $240K pipeline

Q1 2026: Enterprise Push

Jan-Mar 2026:

• Conference circuit (SREcon, DevOpsDays)
• Enterprise case studies (3 published)
• Thought leadership series
• Pilot program refinement

Goals:

• 60 demo requests
• 15 pilot signups
• 8 contracts signed
• $960K pipeline

Q2 2026: Scale & Expansion

Apr-Jun 2026:

• Open-source community growth
• Partner ecosystem development
• User conference (neuaisConf)
• International expansion (EU market)

Goals:

• 100 demo requests/month
• 25 pilot signups
• 15 contracts signed
• $1.8M pipeline

Dev Team Processes

Onboarding New Engineers

File: /mgmt/dev-team/ONBOARDING.md

# Engineering Onboarding - neuais

**Duration**: 2 weeks  
**Goal**: Ship first PR by end of Week 2

## Week 1: Foundation

### Day 1: Setup & Access
- [ ] GitHub access granted
- [ ] Slack invite sent
- [ ] 1Password vault access
- [ ] AWS/Cloudflare access
- [ ] Read: PLATFORM_OVERHAUL_PLAN.md
- [ ] Read: CODE_QUALITY_RULES.md
- [ ] Clone repos, run locally

### Day 2-3: Codebase Tour
- [ ] Pair with Tech Lead (2 hours)
- [ ] Read: All README files
- [ ] Read: ARCHITECTURE.md for each app
- [ ] Run full test suite
- [ ] Watch demo video
- [ ] Review recent PRs (understand patterns)

### Day 4-5: First Contribution
- [ ] Pick "good first issue" ticket
- [ ] Implement fix
- [ ] Write tests
- [ ] Submit PR
- [ ] Code review iteration

## Week 2: Real Work

### Day 6-10: Feature Development
- [ ] Assigned real feature from sprint
- [ ] Implement with guidance
- [ ] Write tests and docs
- [ ] Submit PR
- [ ] **Ship to production** ✅

### End of Week 2
- [ ] 1:1 with Tech Lead (feedback)
- [ ] Officially onboarded
- [ ] Full velocity next sprint

Sprint Cadence

2-week sprints (Wed → Tue)

Week 1 Wednesday:  Sprint Planning (30 min)
Week 1 Friday:     Mid-sprint check-in (15 min)
Week 2 Tuesday:    Sprint review & demo (30 min)
Week 2 Wednesday:  Retrospective (30 min) + Next sprint planning

Why Wednesday start:

• Avoid Monday planning (people need focus time)
• Friday retro = reflect before weekend
• Wednesday = natural work rhythm

Code Quality Enforcement

File: /mgmt/dev-team/code-review/GUIDELINES.md

# Code Review Guidelines

## Philosophy
"Code is read 10x more than it's written. Optimize for readers."

## Review Checklist

### Must Have (Block merge if missing)
- [ ] Tests pass (automated CI check)
- [ ] No clippy warnings (automated CI check)
- [ ] Code formatted (automated CI check)
- [ ] Changes match ticket description
- [ ] No obvious bugs or edge cases
- [ ] Error handling present

### Should Have (Request changes)
- [ ] Function length <50 lines
- [ ] Cyclomatic complexity <10
- [ ] Max 3 parameters per function
- [ ] No magic numbers (use constants)
- [ ] Clear variable names
- [ ] Comments explain "why", not "what"

### Nice to Have (Suggestions)
- [ ] Performance optimizations
- [ ] Better abstractions
- [ ] Additional test cases
- [ ] Documentation improvements

## Review Time Targets
- Small PR (<200 lines): Review within 2 hours
- Medium PR (<500 lines): Review within 4 hours
- Large PR (>500 lines): Review within 1 day

## Review Tone
✅ "Consider extracting this into a helper function"  
❌ "This is wrong"

✅ "Could we add a test for the error case?"  
❌ "Where are the tests?"

✅ "Suggestion: rename `x` to `node_position` for clarity"  
❌ "Bad variable name"

## Approval Criteria
- **Approve**: Code is good, minor suggestions optional
- **Request Changes**: Issues must be fixed before merge
- **Comment**: Just feedback, not blocking

Team Metrics & OKRs

Q4 2025 OKRs

Objective 1: Deliver Scalable Platform

Key Results:

• ✅ Platform overhaul plan complete
• ⏸️ Backend services consolidated (80% complete)
• ⏸️ docs.neuais.com live and comprehensive (60% complete)
• ⏸️ Observatory open-sourced (100% complete)

Objective 2: Achieve Enterprise Sales Traction

Key Results:

• ⏸️ 50 demo requests (current: 10)
• ⏸️ 10 pilot signups (current: 2)
• ⏸️ 5 contracts signed (current: 0)
• ⏸️ $600K ARR pipeline (current: $120K)

Objective 3: Build Technical Credibility

Key Results:

• ⏸️ 1000 GitHub stars on Observatory (current: 0, not launched)
• ⏸️ 2 conference talks accepted (current: 0)
• ⏸️ 10 technical blog posts published (current: 3)
• ⏸️ 500 docs.neuais.com monthly active users (current: 0)

Weekly Metrics Dashboard

File: /mgmt/operations/metrics/weekly-dashboard.md

# Weekly Metrics - Week of [Date]

## Engineering Velocity
- **Sprint points completed**: X/Y (Z% completion)
- **PRs merged**: X
- **Issues closed**: Y
- **Tests added**: Z
- **Code coverage**: A%
- **Build time**: B minutes
- **Deploy time**: C minutes

## Product Health
- **Agents deployed**: X (target: 50)
- **System uptime**: 99.X%
- **API response time p95**: Xms (target: <100ms)
- **Error rate**: Y% (target: <1%)

## Marketing Performance
- **Website visitors**: X (change: ±Y%)
- **Demo requests**: Z (conversion: A%)
- **Newsletter subscribers**: B (+C this week)
- **Social engagement**: D interactions

## Sales Pipeline
- **Total pipeline value**: $X
- **Demos this week**: Y
- **Pilots active**: Z
- **Contracts pending**: A
- **Expected close**: $B this month

## Team Happiness
- **No 3am pages this week**: ✅
- **Code quality score**: X/10
- **Team morale**: [High/Medium/Low]
- **Blockers removed**: Y

Crisis Management Playbook

Incident Response (Dev Team)

File: /mgmt/dev-team/incidents/INCIDENT_RESPONSE.md

# Incident Response Playbook

## Severity Levels

### SEV-1: Critical (Production Down)
- **Response time**: Immediate
- **Team**: All hands
- **Communication**: Update status page every 15 min
- **Postmortem**: Required within 24 hours

### SEV-2: Major (Degraded Performance)
- **Response time**: <30 minutes
- **Team**: On-call + relevant experts
- **Communication**: Update status page hourly
- **Postmortem**: Required within 48 hours

### SEV-3: Minor (Non-critical bug)
- **Response time**: <2 hours
- **Team**: Assigned engineer
- **Communication**: Internal only
- **Postmortem**: Optional

## Incident Workflow

1. **Detect** (automated alerts or customer report)
2. **Acknowledge** (update status page)
3. **Triage** (assess severity)
4. **Mobilize** (page relevant team)
5. **Diagnose** (root cause analysis)
6. **Fix** (deploy patch)
7. **Verify** (confirm resolution)
8. **Communicate** (close incident, notify customers)
9. **Postmortem** (learn and improve)

## Postmortem Template

### Incident: [Title]
**Date**: [YYYY-MM-DD]  
**Severity**: [SEV-1/2/3]  
**Duration**: [X hours]  
**Impact**: [Y customers affected]

### Timeline
- HH:MM - Incident began
- HH:MM - Detected
- HH:MM - Team mobilized
- HH:MM - Root cause identified
- HH:MM - Fix deployed
- HH:MM - Incident resolved

### Root Cause
[What actually happened]

### Contributing Factors
1. [Factor 1]
2. [Factor 2]

### Resolution
[How we fixed it]

### Action Items
- [ ] [Prevention measure 1] - @owner - Due: [date]
- [ ] [Prevention measure 2] - @owner - Due: [date]

### Lessons Learned
[What we learned, what we'll do differently]

Budget & Resource Allocation

Team Budget (Annual)

engineering:
  salaries: $600,000  # 3 engineers × $200K
  tools: $20,000      # GitHub, AWS, etc.
  training: $15,000   # Conferences, courses
  total: $635,000

marketing:
  salaries: $200,000  # 2 people × $100K (early stage)
  contractors: $60,000 # Content, design
  ads: $100,000       # LinkedIn, Google
  tools: $15,000      # HubSpot, Buffer, etc.
  events: $25,000     # Conferences, sponsorships
  total: $400,000

sales:
  salaries: $150,000  # 1 sales engineer
  travel: $30,000     # Customer visits, demos
  tools: $10,000      # CRM, sales enablement
  total: $190,000

operations:
  legal: $25,000
  accounting: $15,000
  insurance: $20,000
  office: $30,000
  tools: $20,000
  total: $110,000

grand_total: $1,335,000/year

Success Metrics by Team

Marketing Team Success

Dev Team Success

Business Success

Implementation Timeline

Week 1: Structure Setup

Actions:

• Create directory structure in /mgmt
• Move existing docs to correct locations
• Archive outdated docs
• Create all template files

Owners: Tech Lead (4 hours)

Week 2: Process Documentation

Actions:

• Write ENGINEERING_HANDBOOK.md
• Write SALES_PLAYBOOK.md
• Update MARKETING_STRATEGY.md (neuais focus)
• Create CONTENT_CALENDAR.md

Owners:

• Engineering Handbook: Tech Lead (4 hours)
• Sales Playbook: Operations Lead (4 hours)
• Marketing Strategy: Marketing Lead (4 hours)

Week 3: Tool Setup

Actions:

• Set up HubSpot CRM
• Configure Calendly for demos
• Set up Buffer for social media
• Create Grafana metrics dashboard
• Set up Linear for sprint planning

Owners: Operations Lead (8 hours)

Week 4: Launch & Iterate

Actions:

• First week using new processes
• Collect feedback
• Iterate on templates
• Document learnings

Owners: All teams

Next Steps (Immediate Actions)

This Week (Week of Dec 5):

1. Review and approve this plan
2. Assign owners to each section
3. Create /mgmt directory structure
4. Schedule Week 2 planning meeting

Next Week (Week of Dec 12):

5. Write all handbook/playbook docs
6. Update marketing plan to neuais focus
7. Create first customer folder (if applicable)
8. Set up CRM and tools

Week of Dec 19:

9. Launch new processes
10. First sprint using new structure
11. First week of new content calendar
12. Collect initial feedback

Conclusion

This plan transforms /mgmt from scattered docs into an operational command center for marketing and dev teams, ready to scale to 1000 agents and enterprise sales.

Key Improvements:

1. ✅ Clear directory structure (easy to find everything)
2. ✅ Standardized processes (everyone knows what to do)
3. ✅ Automation roadmap (practice what we preach)
4. ✅ Integrated workflows (marketing ↔ dev collaboration)
5. ✅ Measurable success (OKRs, metrics, targets)

Timeline: 4 weeks to full implementation
Effort: 20 hours setup + ongoing maintenance
Expected Impact: 40% reduction in operational toil by Month 6

Philosophy: We eliminate our own operational toil through structure, automation, and agents—proving our value prop while we scale.

Ready to execute!