Skip to content
Portfolio/Capabilities

CAPABILITY 13 / 30

The launch operating system

A tracker with gates, a day-one playbook, a media plan, and the retention engine that runs afterwards.

IN PRODUCTION

This runs in client systems today. The sample below was regenerated for a fictional company.

Messaging is the part of a launch people picture. This is the rest of it: roughly 190 tracked items with owners and evidence, the gates that decide whether the launch goes, an hour-by-hour playbook for day one including what to say when something breaks, the media plan, and the touchpoints that run for the next ninety days.

TRY IT / RUNS IN YOUR BROWSER

Use it here.

The mechanism is the production one. The company, the catalogue, and every figure are fictional.

Loading the launch tracker.

THE OUTPUT / GENERATED FOR APEX INSTRUMENTS

What comes out.

JSON
The launch tracker, 190 itemsData · Seven phases from T-30 to T+30. Each item has an owner role, a due date, a dependency where one exists, a status, a gate flag, and the artifact that proves it is done.Open the file ↗
MJS
The tracker builder and its integrity checkData · Computes ids, due dates, and the readiness roll up, and refuses to write a tracker where an item is due before the item it depends on, or is done while its dependency is not.Open the file ↗
Day one playbook
Day one playbookPrint · 4 pages · Run of show, who is on call, the three decision points, the escalation ladder, the rollback criteria, and the six messages to send when something goes wrong.Open ↗PDF
MJS
The playbook generatorData · Generates page 1 from the day one items in tracker.json, so the printed run of show and the board cannot disagree.Open the file ↗
JSON
Media plan, as dataData · Ten channels with spend, dates, creative, owner, measure, target, and a month split. Totals are computed, not typed.Open the file ↗
Media plan
Media planPrint · 2 pages · Two Letter pages: the channel table with the total, the month split, spend by owner and kind, the creative each channel needs, and the rules the plan runs under.Open ↗PDF
MJS
The media plan and retention builderData · Adds the money up and stops the build if a month split does not match its channel or the plan exceeds the approved budget.Open the file ↗
JSON
The retention engineData · Six touchpoints across the first 90 days, each with its trigger, what it sends, what counts as a response, and the rule that takes an account out.Open the file ↗

THE MECHANISM / SHOW THE SHAPE, NOT THE SOURCE

How it works.

What a skill is
  1. 01Track everything

    Every item has an owner, a due date, and the artifact that proves it is done.

  2. 02Gate the launch

    A small number of items block the launch, and the board says go or no-go and why.

  3. 03Run day one

    An hour-by-hour playbook with named decision points, an escalation ladder, and rollback criteria.

  4. 04Buy the attention

    A media plan with spend, dates, creative, and measurement per channel.

  5. 05Keep them

    Six touchpoints over ninety days, each with a trigger, a message, and an exit rule.

WHAT IT READS

  • The task list with owners, dates, and dependencies
  • A gate definition for the items that block launch
  • The day-one run of show
  • The retention touchpoints and their triggers

WHAT IT CHECKS BEFORE IT SHIPS

  • Every gate names its evidence
  • A blocked item is visible on the board, not buried
  • The media plan totals add up
  • Every retention touchpoint has an exit rule
In production: a 191-item launch tracker with a day-one playbook, a media plan, and a retention engine, built for a launch that stays confidential until it ships.

The mechanism runs inside client systems. Everything on this page was regenerated for Apex Instruments, a company that does not exist. Client names, source files, and internal wording stay private.

What it producesWhat is being built next