---
name: scaling-up-framework
description: Align People, Strategy, Execution, and Cash to scale a company past the founder-led stage. Use when the user asks about scaling a company, organizational alignment, Rockefeller habits, a one-page strategic plan, or growth bottlenecks.
triggers:
  - "scaling up"
  - "company scaling"
  - "organizational alignment"
  - "Rockefeller habits"
  - "one page strategic plan"
  - "growth bottlenecks"
disable-model-invocation: false
title: scaling-up-framework
canonical_url: https://skilld.dev/gh/salikshah/startup-agent-skills/scaling-up-framework
last_updated: 2026-10-29T10:46:09.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [evals/evals.json](https://skilld.dev/api/skills-raw/salikshah/startup-agent-skills/scaling-up-framework/evals/evals.json).
>
> If the user asked to install this Skill, run `npx skilld install salikshah/startup-agent-skills/scaling-up-framework`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/scaling-up-framework`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/salikshah/startup-agent-skills/scaling-up-framework) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/scaling-up-framework`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/scaling-up-framework --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/scaling-up-framework --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Scaling Up Framework

## Intent
Use Verne Harnish's Scaling Up framework (adapted from Mastering the Rockefeller Habits) to diagnose and resolve the four core challenges of scaling: People, Strategy, Execution, and Cash.

## Inputs
- Current company size and growth trajectory
- Organizational structure and leadership team composition
- Financial statements (P&L, cash flow, balance sheet)
- Existing strategic plans and meeting cadences
- Employee and customer satisfaction data

## Process (SOP)
1. Step 1: Diagnose which of the four scaling disciplines (People, Strategy, Execution, Cash) is your primary bottleneck — address them in that priority order.
2. Step 2 (People): Ensure you have the right people in the right seats — use a scorecard for every role tied to the company's core values and strategic priorities.
3. Step 3 (People): Establish a leadership team that meets weekly with a structured agenda — priorities, metrics, and accountability, not status updates.
4. Step 4 (Strategy): Define your company's core values, purpose, and brand promise — these must be observable, measurable, and reinforced in every decision.
5. Step 5 (Strategy): Build a One-Page Strategic Plan capturing your 3-5 year vision, 1-year plan, quarterly rocks, and the single biggest priority.
6. Step 6 (Execution): Set quarterly "rocks" (3-5 key priorities) for the company and each individual — no more, or focus fragments.
7. Step 7 (Execution): Establish a meeting rhythm — daily huddles (5-10 min), weekly tactical sessions, monthly strategic reviews, and quarterly offsites.
8. Step 8 (Execution): Create an accountability scorecard for every rock with a named owner and a red/yellow/green status.
9. Step 9 (Cash): Identify your "cash accelerator" — the single lever that speeds up cash collection (e.g., payment terms, deposits, inventory turns).
10. Step 10: Monitor cash weekly and forecast 13 weeks ahead at minimum; growth without cash flow management kills companies.

## Outputs
- A One-Page Strategic Plan aligned across the leadership team
- A quarterly rocks framework with named owners and status tracking
- A sustainable meeting cadence that scales accountability
- A 13-week rolling cash forecast

## Evidence
Source: "Scaling Up" by Verne Harnish. Key concepts: People/Strategy/Execution/Cash framework, One-Page Strategic Plan, quarterly rocks, Rockefeller Habits (meeting rhythm, red/yellow/green scorecards), cash accelerator, core values and purpose.

## Examples
A 40-person agency hits a growth plateau. They diagnose Execution as the bottleneck. They implement daily 8-minute stand-ups, weekly tactical meetings, and quarterly rocks. Within two quarters, project delivery slips drop by 60% and the company exceeds its revenue target for the first time.

## Metrics
- Percentage of rocks completed on time per quarter
- Employee engagement survey scores (people dimension)
- Cash conversion cycle length
- Revenue per employee trend
- Leadership meeting adherence to agenda/timebox

## Anti-Patterns
- Hiring for skills before ensuring cultural/values fit
- Letting the One-Page Plan gather dust — it must be reviewed and updated quarterly
- Holding meetings without clear owners, metrics, or accountability
- Trying to execute more than 5 rocks per quarter — this guarantees none get done
- Managing cash annually instead of weekly — cash crises emerge with no warning
- Copying another company's strategy without adapting to your market position
