---
type: brd
title: Roadcrew Freemium Business Model
feature_id: freemium
status: Draft
version: 1.0
related_prd: ../prds/freemium-prd.md
roadcrew_last_updated: "2025-10-28"
---

# 💡 Business Requirements Document: Roadcrew Freemium Model

## 1. Executive Summary (≤40 words)

Developer-first AI automation platform with tier-based freemium model. FREE tier for solo developers, STARTER for small teams, ENTERPRISE for organizations. Monetize hands-off time freedom, not feature removal.

## 2. Business Context

**Market Opportunity:**
Roadcrew targets developers frustrated with manual software development workflows. The market spans from indie developers to enterprises managing multiple repositories. Success requires adoption-first strategy before monetization.

**Customer Segments:**
- **Solo Developers**: Single-repository workflows, zero infrastructure cost tolerance
- **Small Teams**: Monorepo coordination, batch processing, modest automation budgets
- **Enterprises**: Multi-repo orchestration, team coordination, compliance requirements

**Distribution Strategy:**
- **Pre-API Phase (v1.6.x)**: Download/clone model, client-side validation, zero backend costs
- **Post-API Phase (v1.7.0+)**: API-based access, server-side validation, Roadcrew-managed infrastructure

## 3. Business Goals

1. Achieve 5K+ active users within 18 months (adoption focus, pre-monetization)
2. Convert 3-5% of FREE users to STARTER tier by month 12
3. Establish ENTERPRISE tier revenue stream ($2K+ MRR) by month 18
4. Reduce support burden through self-service features and comprehensive documentation
5. Build community contributions and ecosystem around core commands

## 4. Pricing Model

| Tier | Price | Key Features | Target Audience |
|------|-------|--------------|-----------------|
| **FREE** | $0/month | Single repo, 0 min hands-off, user-provided LLM API | Indie developers, hobbyists |
| **STARTER** | $49/month | Monorepo, 1-15 min hands-off, AI optimization hints | Small teams, fast founders |
| **ENTERPRISE** | $999+/month | Multi-repo, 60 min hands-off, cross-repo coordination, team management | Large organizations, compliance-focused |

**Key Insight:** Users pay for hands-off time freedom and repo scope expansion, not feature removal. All tiers get the same commands; tier determines scope access.

## 5. Go-To-Market Roadmap

### Phase 1: Pre-API Adoption (v1.6.x - Now)
- **Duration:** Q4 2025 → Q2 2026
- **Focus:** Build adoption through open/compiled code distribution
- **Validation:** Client-side license checks, honor system enforcement
- **Revenue:** GitHub license key sales, optional sponsorship model
- **Hands-Off Times:** Measure empirically via instrumentation

### Phase 2: API-Based Infrastructure (v1.7.0+ - Mid 2026)
- **Duration:** Q3 2026 → End 2026
- **Focus:** Transition to server-side validation, introduce optional Roadcrew LLM budgets
- **Validation:** Server-side authoritative checks, API rate limiting
- **Revenue:** Subscription-based API access, optional LLM budgets
- **Hands-Off Times:** Enforced via API, parallel processing enables longer windows

### Phase 3: Monetization Optimization (v1.8.0+ - 2027+)
- **Duration:** Q1 2027 onward
- **Focus:** Dynamic pricing based on resource usage, volume discounts
- **Validation:** Quota-based enforcement, team-level management
- **Revenue:** Usage-based + subscription hybrid model

## 6. Key Metrics

### Product/Customer Metrics
- **Active Users (Monthly)**: Target 5K by month 18
- **FREE → STARTER Conversion**: 3-5% by month 12

### Financial Metrics
- **STARTER ARR**: $29.4K (600 users × $49/yr)
- **ENTERPRISE ARR**: $24K (2 customers × $999+/yr)
- **Gross Margin**: >75% (minimal infrastructure in pre-API phase)

### Usage/Technical Metrics
- **Hands-Off Time Accuracy**: Actual measured (not estimated)
- **Pause Enforcement Compliance**: >95% on STARTER/ENTERPRISE
- **Command Success Rate**: >90% across all tiers

## 7. Business Risks & Mitigations

| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|-----------|
| Free users don't convert to paid | High | Revenue risk | Emphasize hands-off time value, offer generous trial period |
| Users modify code to bypass licenses | Medium | Revenue loss (pre-API only) | Compiled distribution makes modification harder; server-side validation eliminates in v1.7.0+ |
| Competitors copy open-source code | Medium | Market competition | Focus on execution (orchestration quality), not code alone. Build community moat. |
| Pre-API phase requires 18+ months | High | Runway burn | Manage costs, consider sponsorship revenue during adoption phase |

---

## Strategic Principles

### 1. One Tier Structure, Two Deployment Models
The tier structure (FREE/STARTER/ENTERPRISE) remains identical across pre-API and post-API phases. Only the validation mechanism and backend infrastructure change.

### 2. Pause Enforcement, Not Feature Removal
Users in STARTER/ENTERPRISE don't lose features—they experience pause/rate limits that encourage review. Override via `--force` flag available. Respects user autonomy while preventing chaos.

### 3. Hands-Off Time = Monetization Vector
The true value differentiation is how much time a human can step away while automation runs:
- **FREE**: 0 min (must watch)
- **STARTER**: 1-15 min (quick break)
- **ENTERPRISE**: Up to 60 min (full break)

### 4. Repo Scope as Clear Boundary
The upgrade path (Single → Monorepo → Multi-repo) is intuitive and well-understood:
- **FREE**: One repository at a time
- **STARTER**: Multiple packages within one repository
- **ENTERPRISE**: Multiple separate repositories with cross-repo coordination

### 5. Users Control Costs (Pre-API) or Choose Budget (Post-API)
In pre-API phase, users provide their own LLM API keys. Roadcrew has zero AI infrastructure costs. In post-API, users can bring their own API or use optional Roadcrew-managed budgets.

---

## Implementation Phases

### Pre-API Phase (v1.6.x)
- ✅ Client-side license validation
- ✅ Pause enforcement at CLI level  
- ✅ Classification display (STARTER+ only)
- ✅ User-provided LLM APIs
- ✅ Timer instrumentation for hands-off time measurement

### Post-API Phase (v1.7.0+)
- 🔄 Server-side validation (authoritative)
- 🔄 API rate limiting (pause enforcement)
- 🔄 Optional Roadcrew LLM budgets
- 🔄 Team audit logs and tracking
- 🔄 Parallel processing for faster execution

### Monetization Optimization (v1.8.0+)
- 📅 Dynamic pricing based on resource usage
- 📅 Volume discounts for ENTERPRISE
- 📅 Custom tier support

---

## Success Criteria

- [ ] v1.6.x achieves 5K active users by month 18
- [ ] Pause enforcement measured at >95% compliance on STARTER/ENTERPRISE  
- [ ] Hands-off time measurements align with promised values (±10% variance)
- [ ] FREE → STARTER conversion rate reaches 3-5% by month 12
- [ ] ENTERPRISE customers represent <10% of users but >20% of revenue
- [ ] Community contributions increase month-over-month
- [ ] Support requests per user remain flat as user base grows (scaling efficiency)

---

## Decision Framework for Feature Placement

**When deciding if a feature should be FREE, STARTER, or ENTERPRISE:**

1. **Resource Consumption**: How much infrastructure/LLM cost does this require?
   - Free: Zero infrastructure cost (user's machine/API)
   - STARTER: Moderate coordination cost
   - ENTERPRISE: High coordination cost

2. **Scope Limitation**: What's the repo scope needed?
   - Free: Single repo only
   - STARTER: One repo, multiple packages (monorepo)
   - ENTERPRISE: Multiple repos (multi-repo)

3. **Automation Level**: How much autonomy does the user need?
   - Free: User provides LLM API, no Roadcrew overhead
   - STARTER: Coordinated batch processing
   - ENTERPRISE: Full orchestration with team coordination

4. **Hands-Off Time**: Can this feature deliver on promised hands-off time?
   - Free: Feature must complete before break (0 min hands-off)
   - STARTER: Feature completes in batch mode (1-15 min hands-off)
   - ENTERPRISE: Feature orchestrates multi-step workflows (up to 60 min hands-off)