Scale Exec Pitch

• Source: Built by Jonathan Kvarfordt. Standalone bundle v0.2.
• Frameworks applied: Step 4. Launch

It covers a job one of the eight revenue seats has to finish, and it states its process, decision rules, and output format clearly enough for an agent to follow.

1. 1.Copy the SKILL.md text below, or download the raw file.
2. 2.Create a folder named exactly scale-exec-pitch in your agent's skills directory.
3. 3.Save the file inside that folder as SKILL.md.
4. 4.Ask the agent one of the trigger requests below.
5. 5.Check the output against what you already know before it leaves your desk.

• pitch this to my exec team
• 60 second version
• board update

---
name: scale-exec-pitch
description: Turns the charter, friction map, capability decision, and pilot into a 60-second leadership pitch plus a one-page memo the sponsor can forward. Use when the user says "pitch this to my exec team", "60 second version", "board update", "explain the pilot to my CEO", "one pager for leadership", or after the pilot has a week of data.
---

# scale-exec-pitch

Produce `artifacts/scale-pitch.md`. Problem, number, plan, team, timeline, risk, ask. Sixty seconds, then a page.

## Preflight (every run)
1. Confirm `GTM-AI-OS/` is accessible. If not: "I need access to your GTM-AI-OS folder. Select it in Cowork's folder picker, or run `os-install` from the core plugin." Stop until it is.
2. Read `CLAUDE.md`, `INDEX.md`, and the last 20 lines of `signals/log.md`.
3. Check the prerequisites below. For anything missing, ask the cold-start questions and offer: (a) run the earlier skill now, or (b) fast path: answer the questions and this skill writes a minimal version of the missing artifact marked `status: draft (fast path)`.
4. On finish, update the artifact row in `INDEX.md` and append one line to `signals/log.md`: `<date> | <skill> | <produced> | <human changed> | <open question>`.

## Prerequisites
- `artifacts/scale-charter.md`, `artifacts/scale-friction-map.md`, `artifacts/scale-capability-decision.md`, `artifacts/scale-pilot.md`.
Cold-start: "In five lines: the problem with a number, what you're trying, with whom, by when, and what you need from leadership." Continue; mark the pitch draft (fast path).

## Step 1: Sixty seconds
Write it to be spoken in under a minute:
- The problem and what it costs (from the friction map)
- The number we're moving (from the charter)
- What we're doing and with whom (from the pilot)
- When we'll know (stop trigger date, end date)
- The one risk and how we've bounded it (guardrails, cancel trigger)
- The ask (time protection, budget, a decision)

## Step 2: The page
One page under the same headings with the evidence: baseline, target, hypothesis, success criteria, team, weekly control, reversal trigger. Pull real numbers from the artifacts; never invent.

## Step 3: Drip version
A three-line weekly update template for `~~chat` or `~~email`: what we learned, what moved, what we need.

## Step 4: Write
Save the file. Update `INDEX.md`.

## Hand off
Say: "Module 4 is running. When the pilot has data, install `scale-evolve / os-learn` and run `scale-exec-dashboard`."

What does the Scale Exec Pitch skill do?

Turns the charter, friction map, capability decision, and pilot into a 60-second leadership pitch plus a one-page memo the sponsor can forward.

Where does the Scale Exec Pitch skill come from?

Built by Jonathan Kvarfordt. Standalone bundle v0.2.. The source and included files are shown on this page and in the package download.

Why was the Scale Exec Pitch skill chosen for this library?

It covers a job one of the eight revenue seats has to finish, and it states its process, decision rules, and output format clearly enough for an agent to follow.

When should the Scale Exec Pitch skill not be used?

Use it only for the job named above. A skill applied outside its scope produces confident output on the wrong question.

How do I install the Scale Exec Pitch SKILL.md file?

Download the file, create a folder named exactly scale-exec-pitch inside your agent's skills directory, and save the file inside it as SKILL.md. The agent loads it when a request matches the description.