agentleFS
donatassimkusdonatassimkus/claude-ai-skills/skills/scaling/SKILL.md

scaling

Skill1 starsChanged 4 months agoMITView on GitHub

Operational scaling: org design, hiring sequences, management layers, SOPs, team structure, and performance management. Use when asked about when to hire, how to scale ops, team design, revenue stage planning, or what breaks at each growth stage.

The file

Show its rules and text

We split this skill into the rules it gives an agent

43 rules. About 0 are common, 43 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈43

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every business hits predictable constraints as it grows.

    line 14
  2. Distinctive:

    Keep personal and business money separate from day one

    line 47
  3. Distinctive:

    Use freelancers for tasks outside your core skill

    line 51
  4. Distinctive:

    Put agreements in writing before work starts

    line 52
  5. Distinctive:

    Check finances weekly at minimum

    line 63
  6. Distinctive:

    Keep a simple sales pipeline — even a spreadsheet works

    line 64
  7. Distinctive:

    Create basic training: write down how key tasks are done

    line 69
  8. Distinctive:

    Write job descriptions before posting.

    line 83
  9. Distinctive:

    Document how key tasks are done — this becomes your training material

    line 84
  10. Distinctive:

    Create an onboarding process for new customers — what do they need in the first week?

    line 88
  11. Distinctive:

    Create an employee handbook with basic policies

    line 109
  12. Distinctive:

    Run monthly P&L statements

    line 115
  13. Distinctive:

    Create sales materials any rep can use, not just your best one

    line 131
  14. Distinctive:

    Create visible career paths.

    line 161
  15. Distinctive:

    Constraint: Every system is overwhelmed.

    line 172
  16. Distinctive:

    Graduate by: All functions triaged and organized.

    line 173
  17. Distinctive:

    Create a clear IT request process — ad hoc tech support does not scale past 50 people

    line 181
  18. Distinctive:

    Use professional recruiting firms when speed is critical

    line 185
  19. Distinctive:

    Constraint: No one person can know everything.

    line 197
  20. Distinctive:

    Verify the issue before assuming you understood it correctly.

    line 260
  21. Distinctive:

    Call them by name throughout the interaction.

    line 265
  22. Distinctive:

    Use a professional but warm tone.

    line 266
  23. Distinctive:

    Ask follow-up questions to find the root issue, not just the surface complaint.

    line 267
  24. Distinctive:

    Ask if anything else needs resolving before ending the interaction.

    line 272
  25. Distinctive:

    4. Educate & Empower: Do not just solve — teach.

    line 274
  26. Distinctive:

    Add anyone from a struggling department to accelerate training

    line 299
  27. Distinctive:

    Default rotation: sales call → onboarding call → service call

    line 302
  28. Distinctive:

    If a department is broken: watch only that department's calls for 4 consecutive weeks

    line 303
  29. Distinctive:

    5. Act: Document the action item. Monitor in future reviews.

    line 312
  30. Distinctive:

    Create cross-team projects where two departments collaborate even when not strictly necessary.

    line 337
  31. Distinctive:

    Leave buffer for unexpected requests.

    line 374
  32. Distinctive:

    Use distinct colors for: recurring meetings, admin tasks, one-off meetings, project work, break/personal time.

    line 378
  33. Distinctive:

    No more than once per calendar year unless promotion or major scope change.

    line 399
  34. Distinctive:

    If declining: state what would qualify them and when to revisit.

    line 406
  35. Distinctive:

    Verify it is an operational constraint — not a product or market problem.

    line 448
  36. Distinctive:

    When someone underperforms, diagnose the cause before choosing the fix.

    line 484
  37. Distinctive:

    Document: Write down exactly how you do the task.

    line 499
  38. Distinctive:

    Demonstrate: Do the task while they watch.

    line 500
  39. Distinctive:

    If your calendar has no Maker blocks, you are not building.

    line 517
  40. Distinctive:

    Document before you hire. Undocumented processes break when handed to someone new.

    line 525
  41. Distinctive:

    Channel sequencing rule: Start with warm audiences (outreach, referrals, network).

    line 551
  42. Distinctive:

    Every business produces "sawdust" — unused capacity, side effects of delivery, by-products of the core operation that are discarded or …

    line 557
  43. Distinctive:

    Ask: who else would pay for this?

    line 569

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Scaling Skill — How to Build a Business That Runs Without You

What Scaling Actually Is

Scaling is not just making a business bigger. It is making it more effective at each size.

Every business hits predictable constraints as it grows. The constraint at 5 employees is different from the constraint at 50. Scaling means diagnosing which stage you are in, solving the constraint at that stage, and graduating to the next.

The single biggest scaling mistake: applying Stage 8 solutions to Stage 3 problems, or Stage 3 solutions to Stage 8 problems.


The 10-Stage Scaling Roadmap

Ten stages total (Stage 0 through Stage 9). Each has a name, headcount range, founder role, main constraint, and graduation milestone. For the full cross-functional Problem/Solution matrix at each stage (Product, Marketing, Sales, Customer Service, IT, Recruiting, HR, Finance), see references/stage-matrix.md.

Stage Overview

StageNameHeadcountYour RoleMain ConstraintGraduate By
0Improvise1ExplorerNo product yetMake something people want
1Monetize1StarterBusiness makes no moneyMake first sale
2Advertise1 + freelancersDoerCustomer flow is inconsistentConsistent quality + regular new customers
3Stabilize1–4TrainerToo much work for one personGet real help
4Prioritize5–9ManagerServing too many customer typesNiche down to ideal customer
5Productize10–19DirectorLow LTV, one productBuild second premium product
6Optimize20–49LeaderEverything inefficientDo things better, not more
7Categorize50–99ExecutiveEvery system overwhelmedTriage and organize
8Specialize100–249PresidentNo one can know everythingBuild specialist teams
9Capitalize250–500ChairmanGrowth plateauedMake a big bet

Stage 1: Monetize

Constraint: Product is not reliable enough for people to consistently pay. Graduate by: First paying customer. First payment processed and received.

Operations:

  • Set up payment processing
  • Keep personal and business money separate from day one
  • Track who has paid and who has not

Getting help:

  • Use freelancers for tasks outside your core skill
  • Put agreements in writing before work starts
  • Be specific about deliverables and deadlines

Stage 2: Advertise

Constraint: Customer flow is unpredictable. Graduate by: Consistent product quality, regular new customers, reliable part-time help, working financial tracking.

Operations:

  • Get accounting software — track every transaction
  • Check finances weekly at minimum
  • Keep a simple sales pipeline — even a spreadsheet works

Getting help:

  • Convert reliable freelancers to part-time employees
  • Set up payroll processing
  • Create basic training: write down how key tasks are done
  • Make responsibilities explicit — never assume a new person knows their scope

Stage 3: Stabilize

Constraint: There is too much for one person to handle. Graduate by: 1–4 employees carrying real responsibility. You are no longer the only one doing the work.

The core shift: You stop doing. You start teaching.

Operations:

  • Get a payroll service — do not process taxes manually
  • Set up basic bookkeeping: track money in and out monthly
  • Write job descriptions before posting. Know exactly what you are hiring for.
  • Document how key tasks are done — this becomes your training material

People:

  • Find the single biggest customer complaint. Fix that first, not everything.
  • Create an onboarding process for new customers — what do they need in the first week?
  • Train team members. Give them tools. Check their work.
  • Give feedback regularly. Do not wait for problems to compound.

Common mistake: Hiring to solve pain instead of constraint. Fix the biggest bottleneck, not the loudest complaint.


Stage 4: Prioritize

Constraint: Saying yes to too many customer types is pulling the product in multiple directions. Graduate by: Clear ideal customer definition. Product focused. Unqualified customers declined.

The core shift: You stop managing tasks. You manage people.

Operations:

  • Implement a CRM — track every customer interaction in one place
  • Get project management tooling — teams need visibility
  • Consolidate everyone onto the same communication platforms
  • Set up basic data and password protection

People:

  • Create an employee handbook with basic policies
  • Interview properly: check references, ask for work samples
  • Track basic sales metrics: call volume, conversion rate, follow-up rate
  • Define who qualifies as a customer before taking money from them

Finance:

  • Run monthly P&L statements
  • Get basic business insurance
  • Know your top 10 expense categories

Stage 5: Productize

Constraint: Low LTV. Customers have nothing else to buy after first purchase. Graduate by: Second product built and selling. LTV measurably increased.

The core shift: You stop managing people directly. You manage managers.

Operations:

  • Move everything to organized cloud storage
  • CRM with dashboards — every pipeline stage visible to managers
  • Record sales and delivery calls for training
  • Create sales materials any rep can use, not just your best one

People:

  • Promote from within first before hiring externally
  • Connect customer service directly to product development — complaints should influence the roadmap
  • Build a proper termination process before you need it
  • Encourage employee referrals — your team attracts people like themselves

Finance:

  • Build a real budget before the month starts
  • Simple financial forecast: revenue, expenses, profit projection
  • Know exactly how much can be reinvested without breaking cash flow

Stage 6: Optimize

Constraint: More headcount is not making things faster or better. Inefficiency compounds. Graduate by: Core systems working better. Throughput improved without adding people.

The core shift: You move from managing managers to leading a leadership team.

Operations:

  • Separate tech by department — one tool doing too many jobs creates bottlenecks
  • Build performance management systems — track output, not just activity
  • Implement cybersecurity — at 20+ people, data exposure becomes a real risk
  • Build training systems that scale: documentation, video, onboarding tracks

People:

  • Train existing people before hiring new ones. Adding headcount to a broken process makes it worse.
  • Offer better benefits — retirement plans, health coverage. Retention starts costing real money if skipped.
  • Create visible career paths. Good people leave when growth is invisible.
  • Promote from within systematically.

Finance:

  • Review balance sheet monthly
  • Plan taxes quarterly
  • Track metrics beyond P&L: gross margin by product, cash position, days sales outstanding

Stage 7: Categorize

Constraint: Every system is overwhelmed. The org feels disorganized. Graduate by: All functions triaged and organized. Clear accountability at every level.

The core shift: You stop running the business. You run the executives who run the business.

Operations:

  • Move everything to cloud — physical infrastructure is a scale liability
  • Centralized data storage with access controls
  • Build a proper applicant tracking system (ATS)
  • Create a clear IT request process — ad hoc tech support does not scale past 50 people

People:

  • Get an HRIS — employee data must be in one place
  • Use professional recruiting firms when speed is critical
  • Standardize the interview process — inconsistent hiring is a culture killer
  • Build a proper HR function: benefits, compliance, performance reviews

Finance:

  • Quarterly budgets by department — each department head owns their numbers
  • Spending limits and approval workflows
  • Internal audits to catch waste before it compounds

Stage 8: Specialize

Constraint: No one person can know everything. Generalists are hitting their ceiling. Graduate by: Dedicated specialist teams in every function.

The core shift: You move from operational involvement to strategic leadership only.

Operations:

  • Specialized software for each department — no more one tool for everything
  • Dedicated IT people by function, not one IT person for the whole company
  • Standardized hiring process across the company — founder reviews critical hires only

People:

  • Training software for groups, not just individuals
  • Reinforce culture deliberately — at 100+ people, it dilutes without active effort
  • Promote specialists, not generalists
  • Performance management systems tied to compensation

Finance:

  • Renegotiate vendor contracts — volume gives leverage
  • Tax specialists, not just general accountants
  • Regular internal audits for waste and fraud prevention

Stage 9: Capitalize

Constraint: Growth has plateaued. Core products are mature. Graduate by: Big bet placed — acquisition, new product line, or major market expansion.

The core shift: You own vision, capital allocation, and the big bets. Everything else is delegated to CEOs.

Operations:

  • Enterprise-level software with multi-entity support
  • Systems for distinct product lines operating semi-independently
  • Strategic workforce planning — 6–12 month hiring horizons, not reactive gap-filling

People:

  • Plan for senior turnover — every critical role has a backup
  • Founder/CEO personally recruits the top 10 roles
  • Senior hiring takes 6+ months — start earlier than feels necessary

Finance:

  • Get books audited
  • Capital strategy: M&A or R&D for next growth phase
  • Protect against concentration risk — single customer, single product, single market

The 5 Operational Frameworks

These frameworks are designed to be handed directly to your team. Each solves a specific breakdown that happens as headcount grows.


Framework 1: 5 Star Service

When to use: Customer satisfaction is dropping or service quality is inconsistent.

What it is: Five standards that govern every customer interaction. Every touchpoint either strengthens or weakens the business. This framework makes every interaction net positive.

The Five Standards:

1. Concern: Show genuine care.

  • Thank and personalise: "Hi [name], thank you for reaching out."
  • Reassure: "Not to worry — I am happy to help resolve this."
  • Verify the issue before assuming you understood it correctly.
  • At the end: confirm resolution was reached.

2. Courtesy: Listen actively.

  • Rephrase back what they said to confirm understanding.
  • Call them by name throughout the interaction.
  • Use a professional but warm tone. Say please and thank you.
  • Ask follow-up questions to find the root issue, not just the surface complaint.

3. One & Done: Resolve fully the first time. No leftovers.

  • Summarise steps taken to confirm the issue is closed.
  • Educate on how to prevent the same issue recurring.
  • Ask if anything else needs resolving before ending the interaction.

4. Educate & Empower: Do not just solve — teach.

  • Show where the answer was found so they can find it next time.
  • Explain what caused the issue and how to avoid it in the future.
  • Goal: a more capable customer, not a dependent one.

5. Timeliness: Respond immediately, resolve fast.

  • Acknowledge even if you cannot resolve right away: "I will be with you in two minutes."
  • Resolve one inquiry before opening another.

Grading: 5-question post-interaction survey. One question per standard. Rate 1–5. Aggregate by rep. Coach lowest-scoring category first. Track trend over time.


Framework 2: Gametape Review

When to use: Marketing, sales, and customer success operate in silos. Churn is rising. Expectations set on sales calls that delivery cannot meet.

What it is: A weekly 60–90 minute session where marketing, sales, and CS watch a call together and align on one improvement.

The 5-Step Process:

1. Arrange: Set a recurring weekly calendar block.

  • Host: Head of Sales
  • Attendees: Head of Marketing, Head of Customer Success
  • Add anyone from a struggling department to accelerate training

2. Assemble: One day prior, Head of Sales selects the call to review.

  • Default rotation: sales call → onboarding call → service call
  • If a department is broken: watch only that department's calls for 4 consecutive weeks

3. Assess: Watch together at 1.5x speed. Each stakeholder watches for different things:

  • Sales Leader: What went right? What should improve?
  • Marketing Leader: What objections could be overcome before the call in ads or content? What objections belong in sales training?
  • CS Leader: What was promised that delivery cannot meet? What handoff needs improving?

4. Analyze: Share observations. Identify ONE big domino — the highest-leverage single change. Do not pick multiple. Fragmented execution is worse than one focused improvement.

5. Act: Document the action item. Monitor in future reviews.

Why this matters: Customers do not experience departments. They experience a journey. This meeting costs 60–90 minutes per week and compounds into a coherent customer experience over months.


Framework 3: High Performance Communication

When to use: Team productivity is inconsistent. Some people seem disengaged. Communication is slow or unclear.

What it is: A diagnostic and improvement framework based on MIT research showing communication patterns predict team success better than individual intelligence or skill.

Three Components:

Energy — Volume and quality of interactions between teammates.

  • Fast response time has the highest correlation with team energy. Slow communicators drain teams.
  • Publicly acknowledge good work. Never let a good gesture go unnoticed.
  • Vary communication channels — email, voice, chat, comments, all work. Mix them.

Engagement — Whether all team members contribute, or only some dominate.

  • In meetings: use private messages to feed quieter members lines to say until they are comfortable contributing publicly.
  • Give each team member something to present in every team meeting — distribute talk time by design.
  • Pair low-interacting teammates on shared projects to build communication habits.

Exploration — Communication that happens across teams, not just within them.

  • Create cross-team projects where two departments collaborate even when not strictly necessary.
  • Host informal events where teams mix. Shuffle seating deliberately.

How to deploy:

  1. Share with team leaders.
  2. Each leader grades their team: Energy (1–10), Engagement (1–10), Exploration (1–10).
  3. Focus on the single lowest-scoring area first.
  4. Let the team propose how to improve it — they will own what they designed.

Framework 4: Monday Hour One

When to use: Team is stretched, distracted, or managers cannot see what their people are working on.

What it is: One hour of structured planning at the start of each week. Saves 10–12 hours of wasted or misdirected work. Output: a fully time-blocked calendar visible to the manager.

6-Step Process:

1. Look Back: Review last week.

  • What did not get done? What is unresolved?
  • Scan sent messages for anything not followed up on.
  • Review last week's constraints: what process or document would prevent each constraint from recurring?

2. Look Forward: Review the next 1–3 months.

  • What projects are coming that need preparation now?
  • What is on the calendar in the next month requiring lead time?
  • Review EOW reports: what actions are needed?

3. Prioritize: From everything identified, rank by business impact.

  • Schedule priorities first. Do not schedule priorities around other items.

4. Schedule Priorities:

  • Time-block every project with its specific name — "project work" is not a block, it is avoidance.
  • Include lunch, breaks, personal commitments. Realistic calendars beat optimistic ones.

5. Schedule Overflow/Ad Hoc Time:

  • Leave buffer for unexpected requests.
  • Bounded time actually increases efficiency — people move faster when time is constrained.

6. Color Code: Use distinct colors for: recurring meetings, admin tasks, one-off meetings, project work, break/personal time.

Manager benefit: Review the whole team's week in one glance. Overloaded people are visible. Underloaded people are visible. Misalignment is visible.


Framework 5: Pay Increase Framework

When to use: Scaling a team and need a transparent, consistent process for compensation decisions.

The 4 Performance Categories:

CategoryDescriptionRaise Range
Not meeting criteriaRegular performance, no exceptional results1–3%
Consistent and reliableMeets expectations, dependable contributor4–5%
High performance / added responsibilitiesConsistently exceeds, takes on more5–10%
Promotion / new skills / major scope changeNew role or dramatically expanded responsibilities10–20%

Principles:

  • Raises are individual, not blanket. No annual percentage applied uniformly.
  • No more than once per calendar year unless promotion or major scope change.
  • People talk about pay. Transparent criteria prevent resentment. Publish criteria, not individual numbers.
  • Lead with data. Any raise request should include: market rate research, quantified contributions, and evidence of scope change.

How managers handle requests:

  1. Evaluate against the 4 categories.
  2. Communicate the decision with reasoning, not just the outcome.
  3. If declining: state what would qualify them and when to revisit.

Role Evolution at Every Stage

The biggest scaling failures come from founders who keep doing the job that worked at the previous stage.

HeadcountRoleWhat You Actually Do
1Starter/DoerEverything — product, sales, delivery, admin
1–4TrainerTeach others to do what you do
5–9ManagerManage people, not tasks
10–19DirectorManage managers, not individual contributors
20–49LeaderSet strategy, build culture, clear bottlenecks
50–99ExecutiveRun the leadership team, not the departments
100–249PresidentAllocate capital, set direction, hire for critical roles
250–500ChairmanOwn vision, deploy capital, make the big bets

The pattern: At each stage, the founder moves one layer up. If they do not, they become the bottleneck.


Hiring Sequence by Stage

What to hire for first before adding any other headcount:

  • Stage 1–2: Freelancers for tasks clearly outside your skill set
  • Stage 3: First full-time generalist — someone who can do multiple things
  • Stage 4: First department lead in whichever area consumes the most founder time
  • Stage 5: First middle managers — people who own a function end-to-end
  • Stage 6: Dedicated HR — at 20+ people, people management is a full-time job
  • Stage 7: HRIS, dedicated recruiter, finance controller
  • Stage 8: Functional chiefs (CTO, CMO, CFO) who then hire their own specialists
  • Stage 9: CEO(s) for operating units — founder becomes Chairman

Scaling Diagnostic

  1. Find your current stage by headcount.
  2. Confirm the main constraint matches the stage description.
  3. Verify it is an operational constraint — not a product or market problem.
  4. Apply only the solutions for your current stage.
  5. Define your graduation milestone. Know what "done" looks like before you start.

Checklist

Foundation:

  • Current stage identified
  • Single biggest operational constraint named
  • Working on the constraint, not the loudest complaint

Team:

  • Org chart exists — everyone knows who they report to
  • Everyone has a clear, written job description
  • New hires have a documented onboarding process

Systems:

  • Monday Hour One deployed for weekly planning
  • Gametape Review running weekly (once sales and CS exist)
  • 5 Star Service standards in place (once customer-facing team exists)
  • High Performance Communication graded, lowest area being improved
  • Pay Increase Framework documented and shared with team

Finance:

  • Books reconciled monthly
  • Budget exists and is tracked
  • Payroll processed correctly and on time

People Management Frameworks

Performance Diamond

When someone underperforms, diagnose the cause before choosing the fix. Four categories, each requiring a different response:

CategoryThe ProblemThe Fix
CommunicationThey do not know what to doClarify expectations. Restate the outcome, deadline, and standard.
TrainingThey do not know how to do itTeach the skill. Pair them with someone who can. Provide resources.
MotivationThey do not want to do itFind out why. Misaligned role, burnout, or mismatched incentives. Address the root cause.
CircumstancesSomething external is blocking themRemove the obstacle. Tools, access, dependencies, personal situation.

Most managers default to assuming motivation. More often, the real issue is circumstances or communication. Diagnose before you prescribe.

3Ds Training Model

Three steps for transferring any task from yourself to someone else:

  1. Document: Write down exactly how you do the task. Step by step checklist. Include what "done" looks like.
  2. Demonstrate: Do the task while they watch. Record yourself doing it so the recording becomes permanent training material.
  3. Duplicate: They do the task while you watch. Correct in real time. Repeat until output matches the standard.

Skip any step and the transfer fails. Most founders skip Document and wonder why the new person does it differently.

Maker or Manager Time

Founders and senior operators toggle between two modes of work:

  • Maker time: Deep work. Building, writing, creating. Requires long uninterrupted blocks (2+ hours minimum).
  • Manager time: Meetings, decisions, check-ins, communication. Works in 30-minute increments.

Mixing them destroys both. A single 30-minute meeting in the middle of a 4-hour maker block kills the block.

How to apply:

  1. Decide at the start of each week which blocks are Maker and which are Manager.
  2. Schedule all meetings into Manager blocks. Protect Maker blocks completely.
  3. If your calendar has no Maker blocks, you are not building. You are only reacting.

Key Principles

  1. The constraint at each stage is predictable. Diagnose first, prescribe second.
  2. The founder's job changes completely every 2–3 stages. Clinging to old roles creates the bottleneck.
  3. Document before you hire. Undocumented processes break when handed to someone new.
  4. Train before you hire more. Adding headcount to a broken process makes it worse faster.
  5. Promote from within first. Hire outside only for skills the team genuinely does not have.
  6. Teams do not scale through talent alone. Systems and communication infrastructure determine whether talented people compound or cancel each other out.
  7. Transparency in pay prevents compounding resentment. Publish criteria, not individual numbers.
  8. One delivery quality metric tracked consistently beats ten metrics tracked inconsistently.

Revenue Stage Scaling Ladder: Products and Channels

What you should sell and how you should acquire customers is not static. It changes by revenue stage. The wrong product or channel at the wrong stage either wastes resources or limits growth.

Revenue StageWhat to Focus OnWhy
0 to 6 figuresOne product, one audience, one channelValidation. Prove the core offer works before diversifying.
6 to 7 figuresDeepen the core product. Improve quality and repeatability. Add one upsell.At this stage, quality improvements generate more revenue than new products.
7 to 8 figuresAdd a second product sold to existing customers.Acquisition is working. LTV is now the constraint.
8 figures+Add second acquisition channel. Build second audience segment.Core channel is maxed or expensive. Need diversification to grow.

The common mistake at each transition:

  • 0→6 figures: trying multiple products or audiences before proving any one
  • 6→7 figures: launching new products before the core product is excellent
  • 7→8 figures: adding a second acquisition channel before LTV is high enough to justify it
  • 8 figures+: not adding a second channel and getting over-dependent on one platform

Channel sequencing rule: Start with warm audiences (outreach, referrals, network). Move to content (owned audience). Add paid only after CAC:LTV is proven. B2B businesses often stay in warm/content for much longer than they expect before paid becomes necessary.


The Sawdust Strategy

Every business produces "sawdust" — unused capacity, side effects of delivery, by-products of the core operation that are discarded or ignored.

The principle: What is waste to you may be valuable to someone else. Packaging sawdust as a product generates additional revenue from resources already being consumed.

Examples of sawdust:

  • An education company produces recorded sessions while delivering live training. The recordings are sawdust. Packaged as a self-study tier, they become a downsell or continuity product.
  • A consulting business produces internal frameworks while delivering client work. The frameworks are sawdust. Packaged as a course, they become a lead magnet or lower-ticket product.
  • A service business produces team training and SOPs while scaling delivery. Those SOPs are sawdust. Sold or licensed to similar businesses, they become a product.
  • A SaaS business produces customer success playbooks while onboarding customers. Packaged as a consulting offer, they become an upsell.

How to find your sawdust:

  1. List everything your business already produces as a side effect of delivering the core offer
  2. Ask: who else would pay for this? Why is it valuable to them even if it's routine to you?
  3. The bar is not that it's perfect — it just needs to be genuinely useful to someone outside

Why it matters at scale: Sawdust products have near-zero marginal cost (already produced), high margin, and often appeal to a complementary audience that becomes a new acquisition channel.


Adjacent disciplines (where this skill stops)

  • Offer design — the offer and revenue implications per stage (what to sell at Stage 3 vs Stage 7), and offer sequencing by stage (scaling uses headcount stages; offers sequence by offer type)
  • Lead generation — acquisition constraints shift by stage (warm outreach at Stage 1–3, paid media at Stage 5+)
  • Retention and nurture — becomes the dominant growth lever once acquisition works; applies from Stage 4 onward
  • Growth strategy — scaling ops is the infrastructure layer; growth strategy is what the infrastructure serves
  • Sales closing — at Stage 5+, scaling a sales team requires Gametape Review and structured closing training
  • Finance — financial benchmarks and KPIs by revenue stage
  • Sales management — sales org design and hiring sales reps at each stage
  • Fundraising — stage-appropriate capital raises and fundraising timing

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.