The Launch Notes

Chapter 02 of 07

The Launch Notes · Vol. 01 No. 04

The Pack · 02

September 2026 · London

Inside the 14-day Launch Sprint · Inputs

If you cannot produce the file, work does not start

Day 0 is a gate, not a welcome brunch.

Kick-off is where Sprints go to die honestly. We ask for entity documents, named team, product evidence, token status, technical and security posture, legal posture, audience, brand, budget and named approvers. Then we lock objectives, geographies, owners, response-time SLA and exclusions. If those cannot be produced, we do not start the clock and “see how it goes.” How it goes is folklore.

Product evidence is the argument. A testnet URL, a pilot, a mainnet, a repo that is not a placeholder. A deck is not evidence of a product. Concept-only teams sometimes still have a future; they do not have a fourteen-day launch OS worth buying. The screen already prefers live, testnet or pilot. Kick-off enforces it.

Named approvers matter because the register will need signatures. If the only person who can approve a sentence is in a time zone they will not share, or is “the DAO,” we do not have an SLA. The default on this desk is forty-eight hours to respond on claims and twenty-four hours to take a piece down. That SLA is a staffing fact. Treat it as one.

Intake, condensed

  1. 01Entity — incorporated or incorporation in progress. Not a handle.
  2. 02Team — named founder who can decide budget and messaging.
  3. 03Product — URL, explorer, repo, or equivalent artefact.
  4. 04Security — independent review complete or booked, not “we have good ops.”
  5. 05Legal — counsel engaged or identified. We will not be your counsel.
  6. 06Audience — named geographies. “Global retail” is a flag.
  7. 07Approvers — humans with calendars.

Next step

If the company exists, apply today.

Four-step screen. A person replies. Fourteen days to a pack you can take to market. 0% of proceeds.