Skip to main content
ClaudeWave
ES, Spanish
Skill2.1k estrellas del repoactualizado 10d ago

business-growth-consultant

Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everything that could be improved. Use this when growth has stalled or slowed, when deciding where to spend limited time or budget, when revenue rises but profit does not, when prioritizing growth initiatives, or when a business feels busy without compounding.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/cbrock84/headcount /tmp/business-growth-consultant && cp -r /tmp/business-growth-consultant/plugins/executive/skills/business-growth-consultant ~/.claude/skills/business-growth-consultant
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Business growth consultant

One thing limits growth at any moment. Work on anything else and the effort is absorbed with no
output. The entire value of this skill is finding which one.

## Diagnose the constraint first

Walk the chain in order and find the first place it breaks:

1. **Awareness** — do enough of the right people know this exists?
2. **Interest** — do they understand why it matters to them?
3. **Conversion** — do they act?
4. **Delivery** — do they get the value promised?
5. **Retention** — do they stay?
6. **Economics** — does each customer leave the business better off?

The constraint is usually not where attention is. Teams work on acquisition because it is visible
and measurable, when the leak is at delivery or retention.

Two tells worth watching for:

- **Rising revenue, flat profit** — the constraint is economics, and growth is making it worse.
- **Good conversion, poor retention** — the constraint is upstream of where it appears. You are
  acquiring the wrong customers, and no retention work fixes an acquisition problem.

## Then find the leverage

Against the identified constraint only, generate moves and rank them by **impact ÷ effort ×
confidence**. Be specific about all three; a plan where everything scores high is unranked.

Prefer moves that compound over moves that add. A referral loop that improves with volume beats a
campaign that must be repeated at the same cost.

## Sequencing

- Fix the constraint before scaling anything. Scaling a leaky funnel multiplies the leak.
- One initiative at a time when you cannot attribute results. Parallel initiatives with shared
  metrics teach you nothing about which worked.
- Set a read-by date and a kill threshold before starting.

## Scaling readiness

Before recommending growth spend, check the business can absorb it: delivery capacity, support load,
cash to fund the gap between acquisition and payback, and whether unit economics hold at volume.
Growth that outruns delivery converts customers into detractors at scale.

## Choosing what to measure

Track few numbers, chosen against the constraint. A dashboard of twenty metrics is a dashboard
nobody reads and cannot act on.

For each stage of the chain above, one leading indicator that moves early and one lagging number
that confirms it. Leading indicators are what you steer by; lagging ones are what you report.

Two rules that prevent most dashboard failures:

- **Every metric needs a comparison** — a prior period, a target, or a cohort. A number alone is not
  information.
- **Every metric needs an owner** who can act on it. Metrics nobody can move are trivia, however
  interesting.

Watch for metrics that improve while the business worsens: revenue up with margin down, signups up
with activation down, traffic up with conversion down. Each means the mix shifted, and the headline
number is hiding it.

## Never

- Recommend tactics before naming the constraint. Effort applied away from the constraint does nothing.
- Stack initiatives until none of them gets the attention it needs to work.
- Present a plan with no way to tell within a quarter whether it is working.
- Recommend more spend into a funnel that does not convert what it already receives.

## Return contract

1. **The constraint**, named, with the evidence.
2. **Why the obvious candidates are not it.**
3. **Three moves**, ranked, with impact, effort, and confidence stated.
4. **What to do first** and the metric that will show it working.
5. **What to stop doing** — a growth plan with no subtraction is a wish list.
account-based-marketingSkill

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

agent-hierarchySkill

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

ai-ml-governanceSkill

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

ai-research-analystSkill

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

ai-search-optimizationSkill

Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.

app-store-optimizationSkill

Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.

backup-and-recoverySkill

Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or recover from data loss.

budgeting-and-forecastingSkill

Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.