mcpField
B
business-operator

business-operator

github.com/shipshitdevMarketing & growth38192 installsUpdated 2d ago
Repository

About business-operator

business-operator is a meta-skill for assessing and prioritizing a portfolio of businesses. It evaluates business inputs, recommends where to focus, and routes issues to specialized business skills.

Key features

  1. 01Portfolio inventory and health assessment
  2. 02Priority scoring across businesses
  3. 03Weekly time-allocation guidance
  4. 04Routing to specialized business skills
  5. 05Business-specific action plan generation
  6. 06Framework for evaluating business closure

Use cases

  1. 01Choosing which venture to focus on this week
  2. 02Identifying a business's main growth bottleneck
  3. 03Matching pricing or retention issues to a skill
  4. 04Reviewing whether to continue or close a venture

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/shipshitdev/skills --skill business-operator

After installing, type/business-operatorin Claude Code to confirm it loaded.

Bundled filesassets/output-template.mdplugin.json

Details

From the project README

Business Operator - Multi-Business Orchestrator

Overview

Orchestrates Hormozi business frameworks across a portfolio of ventures, identifying which business needs attention, what specific actions to take, and which specialized skill to deploy.

This is the meta-skill that coordinates: offer-architect, pricing-strategist, lead-channel-optimizer, retention-engine, constraint-eliminator, business-model-auditor, outbound-optimizer, and execution-accelerator.

The Framework

Hormozi Portfolio Principle: "Focus beats diversification, but the right portfolio multiplies returns."

The Business Priority Matrix

Score each business on:

  1. Revenue Potential (1-10): How much can this make?
  2. Current Traction (1-10): Is it already working?
  3. Effort Required (1-10, inverted): How much of YOUR time does it need?
  4. Leverage (1-10): Does it scale without you?

Priority Score = (Revenue × Traction × Leverage) / Effort

The Weekly Focus Rule
  • Primary Business (60% of time): Highest priority score
  • Secondary Business (30% of time): Growth potential or maintenance
  • Exploration (10% of time): New opportunities or experiments

Execution Workflow

Step 1: Business Inventory

Ask the user:

"List all your active businesses/products. For each one, tell me:

  1. What is it? (one sentence)
  2. Current monthly revenue (or $0 if pre-revenue)
  3. Growth trend (growing/flat/declining)
  4. Hours you spend per week on it"
Step 2: Health Metrics Assessment

For each business, gather:

  • Revenue: Current MRR/monthly revenue
  • Growth Rate: Month-over-month change
  • Customer Count: Active paying customers
  • Churn Rate: Monthly customer loss (if applicable)
  • Time Investment: Your hours per week
  • Biggest Bottleneck: What's limiting growth?
Step 3: Hormozi Audit

For each business, identify which Hormozi framework is needed most:

Problem DetectedRoute To
Weak/confusing offeroffer-architect
Underpriced, leaving money on tablepricing-strategist
Not enough leads/customerslead-channel-optimizer
High churn, low LTVretention-engine
Customers struggling to succeedconstraint-eliminator
Can't scale, you're the bottleneckbusiness-model-auditor
Outbound isn't convertingoutbound-optimizer
Stuck, can't decide, overthinkingexecution-accelerator
Step 4: Priority Matrix Calculation

Calculate priority score for each business:

Priority = (Revenue Potential × Current Traction × Leverage) / Effort Required

Where each factor is scored 1-10:
- Revenue Potential: Market size × pricing power
- Current Traction: Customers × growth rate × retention
- Leverage: Can it run without you? (10 = fully automated, 1 = you ARE the product)
- Effort Required: Your weekly hours (inverted: 1 hour = 10, 40 hours = 1)
Step 5: Action Plan Generation

For each business, output:

[Business Name]

  • Priority Score: X/100
  • Primary Issue: [Detected problem]
  • Recommended Skill: [Which Hormozi skill to deploy]
  • This Week's Action: [One specific thing to do]
  • Time Allocation: [% of your week]

Output Format

See assets/output-template.md for the full Portfolio Health Report template (load when generating the portfolio deliverable).

Skill Routing Logic

After analysis, route to the appropriate skill:

Offer Problems → offer-architect

Triggers:

  • "My offer isn't compelling"
  • "People don't understand what I sell"
  • "Conversions are low"
  • "Competitors seem more attractive"
Pricing Issues → pricing-strategist

Triggers:

  • "I think I'm too cheap"
  • "Competitors charge more"
  • "I'm scared to raise prices"
  • "Low revenue per customer"
Lead Generation Gaps → lead-channel-optimizer

Triggers:

  • "Not enough leads"
  • "Marketing isn't working"
  • "Don't know where to focus"
  • "Spreading myself too thin on channels"
Churn/Retention Issues → retention-engine

Triggers:

  • "Customers keep leaving"
  • "Low repeat purchases"
  • "High churn rate"
  • "No upsells or cross-sells"
Customer Success Friction → constraint-eliminator

Triggers:

  • "Customers struggle to get results"
  • "Too many support tickets"
  • "People don't use what they buy"
  • "High refund requests"
Scale Limitations → business-model-auditor

Triggers:

  • "I'm the bottleneck"
  • "Can't grow without hiring"
  • "Trading time for money"
  • "What breaks at 10x?"
Outbound Not Converting → outbound-optimizer

Triggers:

  • "Cold outreach isn't working"
  • "Low response rates"
  • "Can't get meetings"
  • "Outbound feels spammy"
Analysis Paralysis → execution-accelerator

Triggers:

  • "I'm stuck on a decision"
  • "Should I wait for..."
  • "I'm overthinking this"
  • "Too many options"

Integration with Other Skills

This skill orchestrates but doesn't replace the specialized skills:

SkillWhen Business-Operator Routes Here
offer-architectOffer clarity/conversion issues detected
pricing-strategistUnderpricing or pricing confidence issues
lead-channel-optimizerLead generation is the bottleneck
retention-engineChurn is killing growth
constraint-eliminatorCustomer success is blocked
business-model-auditorScale/leverage problems identified
outbound-optimizerDirect sales channel needs help
execution-acceleratorUser is stuck or overthinking

Also integrates with existing skills:

  • leads-researcher - For identifying new customer segments
  • copywriter - For messaging across businesses
  • stripe-implementer - For payment/billing implementation

Example Interaction

User: "I have 3 businesses and I'm stretched too thin. Help me figure out what to focus on."

Business Operator Response:

Let me help you prioritize. Tell me about each business:

For each business, share:

  1. What is it? (one sentence)
  2. Monthly revenue
  3. Growth trend (growing/flat/declining)
  4. Hours you spend per week
  5. Biggest current challenge

I'll run a Hormozi analysis on your portfolio and give you:

  • Priority rankings with scores
  • Which business gets focus this week
  • The specific skill/framework each business needs
  • A concrete action plan

The Kill Decision Framework

Sometimes the answer is to kill a business. Consider killing when:

  • Priority Score < 20/100 AND
  • No clear path to improvement AND
  • Opportunity cost of time is high

Before killing, ask:

  1. Could a single change (offer, price, channel) fix this?
  2. Would I start this business today knowing what I know?
  3. Is my emotional attachment clouding judgment?

Best Practices

  1. Weekly Reviews: Run a portfolio check every week
  2. One Primary: Never have two businesses at "primary focus"
  3. Time Tracking: Actually track hours to validate effort scores
  4. Quarterly Kills: Review what to kill every quarter
  5. Stack Rankings: Always rank, never tie - forces prioritization
  6. Exit Criteria: Define what would make you kill each business upfront

When to Escalate

Route to execution-accelerator if:

  • User can't decide which business to focus on after analysis
  • User is emotionally attached and can't see clearly
  • User needs to make a kill decision but is stuck

Comments

Markdown supported