---
type: brd
title: Roadcrew Submodule Isolation & Multi-Repo Business Strategy
feature_id: submodule-isolation
status: Draft
version: 1.0
owner: Roadcrew Business Team
created: 2025-01-24
updated: 2025-01-24
related_vision: ../vision.md
related_prd: ../prds/submodule-isolation-prd.md
related_spec: ../specs/submodule-isolation-spec.md
---

# 💡 Business Requirements Document: Roadcrew Submodule Isolation & Multi-Repo Business Strategy {#brd-submodule-isolation}

> This doc defines business context, value, goals, non-goals, solution boundaries, and success metrics. PRD and Spec must reference sections, not duplicate content.

## 1. Executive Summary (≤40 words)

Roadcrew employs freemium + consulting model targeting semi-technical founders. Submodule isolation eliminates namespace conflicts that caused customer churn. Premium tiers unlock AI automation, multi-repo orchestration, enterprise features.

## 2. Business Context (max 4 bullets per subsection)

### 2.1 Market & Target Segments
- Solo founders and early-stage startups (free tier, 2% conversion target)
- Small teams 2-5 people building SaaS (Starter $49/mo, 6% conversion)
- Growth teams 6-20 people (Enterprise $999+/mo, 8% conversion)
- Enterprises 50+ with compliance needs (Enterprise tier, 25% conversion)

### 2.2 Revenue Streams
- Freemium SaaS: Token-based AI automation pricing ($49-$999+/mo)
- Professional services: Implementation consulting ($7,500 per engagement)
- Custom templates: Industry-specific packages ($5k-$25k per project)

### 2.3 Differentiators
- Only spec-driven system with AI agent orchestration and cost tracking
- Eliminates namespace conflicts that competitors ignore (taxbuddy resolution)
- Multi-repo coordination for microservices (vs single-project tools like Linear)

## 3. Business Goals (≤5, each ≤15 words)

- Achieve $1.67M ARR by Year 1 end
- Convert 5% free users to paid within 90 days
- Maintain >75% gross margin on all tiers
- Reduce customer churn from namespace conflicts to <5% monthly
- Enable 500 free tier users, 150 Starter, 105 Enterprise

## 4. Non-Goals / Constraints (≤3, each ≤12 words)

- No immediate npm package distribution (submodule first, npm later)
- No auto-install on clone (manual prevents surprise changes)
- No Windows-only features (cross-platform via Node.js required)

## 5. Pricing Model (table, ≤3 tiers)

| Tier        | Price        | Key Features (≤6 words)                    | Audience              |
|-------------|--------------|--------------------------------------------|-----------------------|
| Free        | $0           | Manual commands, single repo               | Solo founders         |
| Starter     | $49/mo       | AI automation, 100k tokens/mo              | Small teams 1-3       |
| Enterprise  | $999+/mo     | Multi-repo, unlimited tokens, SLA          | Growth teams 50+      |

**Trial Period:** 30-day free trial before purchasing Starter tier (separate from paid features)

## 6. GTM Roadmap (max 3 phases, ≤20 words per goal)

- **Phase 1 (Q1):** Open source launch, 100 GitHub stars, 20 active users, community contributions
- **Phase 2 (Q2):** Freemium launch, 500 free users, 10 Starter customers, $500 MRR milestone
- **Phase 3 (Q3-Q4):** Enterprise tier, 2000 free users, 150 Starter, 5 Enterprise, $12,350 MRR

## 7. Metrics (≤6 total, split across categories)

### 7.1 Product/Customer Metrics
- MAU: 2,000 by Year 1 end
- Free-to-paid conversion: 5% target

### 7.2 Financial Metrics
- ARR: $1.67M Year 1 target
- CAC: <$500 with 3-month payback

### 7.3 Usage/Technical Metrics
- Token usage: 60k/mo avg (Starter tier)
- Commands automated: 65% (Enterprise agents vs manual)

## 8. Key Risks & Mitigations (table, ≤4 risks)

| Risk                            | Mitigation                                      |
|---------------------------------|-------------------------------------------------|
| AI costs increase unexpectedly  | Pass-through pricing with immediate adjustments |
| Low free-to-paid conversion     | 30-day trial of premium agent features          |
| Namespace conflicts persist     | Submodule isolation model (this feature)        |
| Consulting doesn't scale        | Standardize packages, create playbooks          |
| Unauthorized premium feature use| License validation with token quota enforcement |

## 9. References & Downstream

- **Product Vision:** [../vision.md](../vision.md)
- **PRD:** [../prds/submodule-isolation-prd.md](../prds/submodule-isolation-prd.md)
- **Spec:** [../specs/submodule-isolation-spec.md](../specs/submodule-isolation-spec.md)

---

## Editor Instructions:
- Update only as market conditions, pricing, or segment focus change—not for every feature.
- Downstream docs (PRD, Spec) must reference section numbers directly.
- Any redundant narrative, or exceeding bullet/word counts, invalidates the doc for automation or AI parsing.

<!--
DOWNSTREAM TEMPLATE MAPPING:

prd.template.md requirements:
- Business Goals (3) → PRD Business Objectives (1.1)
- Metrics (7) → PRD Success Metrics (3)
- Target Segments (2.1) → PRD User Goals context
- Differentiators (2.3) → PRD Problem Statement context

spec.template.md requirements:
- Pricing Model (5) → Spec NFRs (constraints on pricing/licensing)
- Metrics (7) → Spec Acceptance Criteria (performance targets)
- GTM Roadmap (6) → Spec Implementation Plan (phasing)

release.template.md requirements:
- Business Goals (3) → Release overview (business impact)
- GTM Roadmap phases → Release sequencing
-->