roi-modelerlisted
Install: claude install-skill jonwoods79-sys/woodsco-team-os
# ROI Modeler
**[DATA GUARD]**: Never invent Salary or ARR data. Use `[TBD - REQUIRES FINANCE INPUT]` for sensitive numbers. If confidence is low, output a **Range** (Best/Worst case) rather than a single number.
## Execution Logic
1. **Investment (Cost):**
- [Engineer Hours] × [Average Hourly Rate] = **Build Cost**.
- [Annual Maintenance %] = **Run Cost**.
2. **Return (Revenue/Savings):**
- **New ARR:** [New Customers] × [ACV].
- **Churn Reduction:** [Customers Saved] × [LTV].
- **Efficiency:** [Ops Hours Saved/Year] × [Rate].
3. **The Math:**
- **Payback Period:** [Build Cost] ÷ ([Annual Return] ÷ 12).
- **ROI (12-month):** ([Annual Return] - [Build Cost]) ÷ [Build Cost].
4. **The Gate:** If Payback Period > 6 months (Startups) or > 12 months (Enterprise), flag as `[HIGH-VIABILITY-RISK]`.
## Output Format
```markdown
## ROI Estimate: [Feature Name] | Verdict: [VIABLE / AT-RISK]
### 1. Investment (The Spend)
- **Estimated Effort:** [Weeks/Sprints]
- **Total Build Cost:** $[Amount] `[HYPOTHESIS]`
- **Annual Run Cost:** $[Amount]
### 2. The Return (The Gain)
- **Primary Lever:** [ARR / Churn / Efficiency]
- **Target Lift:** [X%]
- **Annualised Value:** $[Amount]
### 3. Commercial Verdict
- **Payback Period:** [X] Months
- **12-Month ROI:** [X]%
### Success Threshold for Experiment
"This feature must prove a **[X]% lift** in **[Metric]** to meet the ROI target. If the experiment yields less, we kill the feature."
```
## Quality gate
Before sharin