brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Diagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.
$ npx -y skills add getcrew44/crew44 --skill business-health-diagnostic --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/business-health-diagnosticContext preview
The summary Claude sees to decide when to auto-load this skill.
Diagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.
name: business-health-diagnostic description: Diagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes. intent: >- Diagnose overall SaaS business health by analyzing growth, retention, unit economics, and capital efficiency metrics together. Use this to identify problems early, prioritize actions by urgency, and deliver a comprehensive health scorecard for board meetings, quarterly reviews, or fundraising preparation. type: interactive theme: finance-metrics best_for: - "Getting a complete read on your SaaS business health across all dimensions" - "Identifying which metrics are red flags vs. leading indicators" - "Preparing for a board meeting or investor review" scenarios: - "Our growth is strong but we're burning cash fast — I need to understand our unit economics before the board meeting" - "I'm preparing for a Series A board meeting and need to assess our business health across growth, retention, and efficiency" estimated_time: "20-30 min"
Diagnose overall SaaS business health by analyzing growth, retention, unit economics, and capital efficiency metrics together. Use this to identify problems early, prioritize actions by urgency, and deliver a comprehensive health scorecard for board meetings, quarterly reviews, or fundraising preparation.
This is not a single-metric check—it's a holistic diagnostic that connects revenue, retention, economics, and efficiency to reveal systemic issues and opportunities.
A SaaS business is healthy when four dimensions work together:
1. **Growth & Retention** — Are you growing and keeping customers?
2. **Unit Economics** — Is the business model profitable at the customer level?
3. **Capital Efficiency** — Are you using cash efficiently?
4. **Strategic Position** — Are you positioned for sustainable success?
**Early Stage (Pre-$10M ARR):**
**Growth Stage ($10M-$50M ARR):**
**Scale Stage ($50M+ ARR):**
**Critical (Fix immediately):**
**High Priority (Fix within quarter):**
**Medium Priority (Address within 6 months):**
**Use this when:**
**Don't use this when:**
---
Use [`workshop-facilitation`](../workshop-facilitation/SKILL.md) as the default interaction protocol for this skill.
It defines:
This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.
This interactive skill asks **up to 4 adaptive questions**, then delivers a comprehensive diagnostic with prioritized recommendations.
---
**Agent asks:**
"Let's diagnose your business health. I'll need metrics across four dimensions: growth, retention, unit economics, and capital efficiency.
**Company context:**
**Why this matters:** Benchmarks vary by stage. Early-stage optimizes for growth; scale-stage optimizes for efficiency.
Please provide the following metrics. Use 'unknown' if you don't have a metric."
---
**Agent asks:**
"**Growth & Retention:**
1. **Revenue:**
Orchestrate a crew of specialist AI agents in one local-first workspace. Each role on its best model, with memory and skills that compound. Free, MIT.
Repo: getcrew44/crew44
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes