Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
shipshitdev avatar

Business Operator

  • 179 installs
  • 31 repo stars
  • Updated August 2, 2026
  • shipshitdev/library

Run day-to-day business operations: pricing tweaks, unit economics, vendor choices, support priorities, and roadmap tradeoffs that keep a live product profitable.

About

Business-operator acts as an execution-focused operator for running a shipped product. It helps teams manage pricing, finances, vendor relationships, support load, and iterative priorities for SaaS, ecommerce, and API businesses without losing sight of profitability and customer outcomes.

  • Tracks unit economics and runway implications
  • Guides pricing, packaging, and refund policy choices
  • Prioritizes ops work against customer impact
  • Coordinates vendors, billing, and support handoffs

Business Operator by the numbers

  • 179 all-time installs (skills.sh)
  • Ranked #1,095 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/shipshitdev/library --skill business-operator

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs179
repo stars31
Last updatedAugust 2, 2026
Repositoryshipshitdev/library

What it does

Run day-to-day business operations: pricing tweaks, unit economics, vendor choices, support priorities, and roadmap tradeoffs that keep a live product profitable.

Files

SKILL.mdMarkdownGitHub ↗

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

Related skills

Productivity & Planningpricingfinanceecommerce

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.