--- name: scale-launch description: S.C.A.L.E. step 4, Launch. Scopes one pilot (one problem, a hypothesis, 30 to 90 days, a team or a solo path, three to five criteria, a stop trigger) and writes the 60-second leadership pitch plus the weekly update template. Use when the user says "launch my pilot", "step 4", "scope the pilot", "tiger team", "pitch this to my exec team", "60 second plan", or after step 3. --- # scale-launch Write `SCALE/4-launch-pilot.md`. One problem per pilot. Two problems, two pilots. ## Preflight (every run) 1. Find the `SCALE/` folder (Desktop or Documents), or `GTM-AI-OS/artifacts/scale/` if the user runs the GTM AI OS. If neither exists, run `scale-start` first; it creates the folder and asks for access. 2. Read `SCALE/progress.md`: mode (quick or deep), AI experience level, which steps are done, the one-line context. 3. Talk short and direct. Say what each answer is for. Beginner: one question at a time, plain words. Advanced: batch questions, skip explanations. 4. Quick mode: ask only the questions marked (Q). Deep mode: ask all. Accept "skip" and "don't know"; record them as gaps. 5. If the previous step's artifact is missing, say so and offer: do that step now, or answer three questions and continue with a draft marked fast path. 6. When the user names a system (CRM, calls, email, spreadsheet), request access to that one or take an upload. Never assume a product. 7. On finish: write the artifact, update `progress.md`, say the next step in one sentence, and ask one open question if any remain. ## Part A: Scope 1. If no pilot is picked, recommend the GTM AI OS on one motion (scoped, measurable, governed). Otherwise take the step 3 decision. 2. (Q) The one problem, in a sentence tied to the step 1 charter. 3. (Q) Hypothesis: "We believe will produce because ." No "because," no charter. 4. (Q) Window: 30, 60, or 90 days. In scope, out of scope, OAR level. 5. (Q) "Team, or just you?" Team: business owner who can decide, ops lead, tech partner, two or three end users, change champion; RACI; pick growth-trajectory people respected by peers, not the top 10%; sponsor protects their time in writing. Solo: the user runs it on one to three accounts; write it that way. 6. (Q) Three to five success criteria across usage, performance, business outcome, learning; each with a baseline and target. 7. (Q) Stop trigger at the midpoint. Weekly red / yellow / green on usage, performance, impact, satisfaction, on a named day. 8. Sponsor drip cadence, weekly. Silence invites someone to reassign your people. ## Part B: The pitch Sixty seconds, spoken: the problem and its cost (step 2), the number (step 1), what and with whom (above), when we'll know, the one risk and how it's bounded (step 3 guardrails), the ask. Then a one-page memo with the evidence. Then a three-line weekly update template. Real numbers only. ## Write `4-launch-pilot.md` from `references/pilot-template.md`. Quality gate: two problems, no stop trigger, or a criterion without a baseline: don't write. ## Hand off Mark the step done in `progress.md` and set `resume at`. Fast mode: say "Step done. Moving to Evolve." and continue to the next step without waiting. In-depth mode: say "Step done. Say **next** when you're ready for Evolve."