mogkit

Wedge · 4/5

GTM & Launch

Pre-flight interrogation specific to this launch.

knowledge engine: coming · standalone skills shipped

The problem

Most launch failures are visible in advance to anyone who asks the right questions about the specific launch — what is unowned, what the rollback actually rolls back, who heard about it and when, what breaks under 10x or 0.1x demand. Generic launch checklists don't help; they list everything and load-bear on nothing. The work is to identify the gaps in *this* launch, then close them.

The level-up path

GTM is a standalone-skills wedge. The load-bearing move is the pre-flight interrogation:

  • launch-readiness — paste a launch description (what’s launching, to whom, when, what’s already in place). Get back the gap-list: ownership gaps, rollback realism, comms & enablement gaps, the 10x / 0.1x demand stress test, and explicit kill criteria. Specific to your launch; never a generic checklist.
  • tradeoff-frame — for the launch-window and scope-cut calls that always show up the week before. Names the real axes; doesn’t pick.

A note on the knowledge engine

No GTM-side knowledge engine in v1. Launches are episodic, not corpus- shaped; a versioned graph would be solving the wrong problem. If a durable launch-history engine earns its place — e.g. a “what did we learn from the last six launches” surface — it lands in a later version. Until then, the gap-list from launch-readiness plus a versioned launches/<date>-<name>/ folder in your workspace is more than most teams have.

Visual setup walkthrough

  1. npx mogkit init my-launch-workspace.
  2. In Claude Code, run launch-readiness against a written launch description. Get the gap list.
  3. Close the gaps in your launch plan — ownership, rollback, comms, kill criteria.
  4. Keep launches/<date>-<name>/ as a versioned record. The next launch has the prior launch’s notes to learn from.

Skills to install

launch-readiness

intermediate
standalone gtm

Interrogates a planned launch — what is unowned, the rollback plan, the comms and enablement gaps, what breaks if adoption is 10x or 0.1x of expectation, and the explicit kill criteria. Produces the gap list specific to this launch; never a generic checklist.

tradeoff-frame

intermediate
standalone conflict

Frames a contested decision honestly — names the real axes of disagreement, what each option optimizes versus sacrifices, whether the decision is a one-way or two-way door, and the evidence that would actually move a reasonable person. Frames; does not pick.

All of these install automatically when you run npx mogkit init.

Material

A curated path. Not a link dump.

    Climbing the wrong hill essay
    by Chris Dixon

    Short essay on local maxima and why GTM motions get stuck optimizing the wrong loop. Useful frame for launch decisions.

    High Output Management book
    by Andy Grove

    Operating cadence, decision quality, and what it means to actually launch something inside a company. Pre-dates SaaS; ages better than most PM books.