Skip to content

Launch Motion — Decision Record

Status: RULING (Tim, 2026-07-06). Complete as a decision. Names the required follow-on rulings; does not pre-empt them. Settles the launch-timing fork from the CANON-TRAJECTORY-AUDIT-01 §5 triage (Q1/Q2). Proposed repo path: product/decisions/launch-motion.md (or an ADR, per Tim). Staged for Tim to move.

Decision

RTOpacks launches as a complete whole-product platform — "the fortress" — in a single coordinated release. No thin launch. No staged release of individual modules as small apps.

Rationale

Architectural — the spine is conjoined by design. People plugs into Studio; Studio draws from the spine (People + procedures + TGA), through to UCCA, output to a library layer not yet built. The modules consume each other. Canon states the consequence (audit §1.1): strip a module and Studio returns to the competitor category. A scaled-down release forfeits the differentiator.

Commercial — a displacement play, not an additive one. The value is the totality: one integrated platform that replaces several existing SaaS/offline subscriptions. That supports a high price. A $50 entry point does not upstack to $1,000 through expansion; landing high with the whole product is the correct motion. Dropped piecemeal, the signal is lost in the noise; dropped whole, it is "this changes everything."

Operational — the decisive constraint. Solo founder. At launch Tim runs live training, shows, and support simultaneously — cannot sell by day and dev by night. The product must run in totality at launch; there is no capacity to finish it afterward.

Pricing mechanic (declared; specifics pending recon)

Base subscription (annual-discount offered) + metered AI consumption ("Anthropic mode" — AI produces thinking in Studio; sub covers the rest of the suite). A limited-time year-one half-price admission as an embedding mechanic ("the flytrap"): discounted entry gets them in; a year of genuine embedding — killing their other subscriptions, becoming load-bearing in their compliance — makes full-price renewal retention, not a cliff.

Required follow-on rulings — in order

  1. FROZEN LAUNCH SCOPE. The exact minimum pond-owning fortress: which modules and capabilities ship at launch, and what is explicitly post-launch. Until this line is drawn, "whole" is undefined and the launch cannot be dated — and the scope is the speed throttle: every module past the line is time handed to a competitor. This is the next working session. [Tim ruling]

  2. BUILD-TIME vs COMPETITIVE WINDOW (amended — the binding clock is not runway). Tim can self-fund modestly and indefinitely, so money is not the constraint. The constraint is speed to market with a solid product: realistic build-time to the frozen scope, set against how long the market stays open before a competitor ships something comparable. If build-time exceeds the window, the fortress lands late into a contested pond. [fact/judgement to establish]

  3. PRICING RECON. Downstream of scope — you cannot price "carry the dev on price" without knowing how much dev there is. Folds in Q3 (tiers, base + metered), Q8 (per-tier free-course allowances), the AI-cost floor (metered rate must clear cost-per-generation with margin), and the flytrap/renewal design. [recon brief]

The positioning ruling that closes audit §1.1 falls out of ruling 1 — it can be written complete once the scope edge exists.

Risks the plan must be built to survive (recorded, not blocking)

  • Scope creep — the primary failure mode of go-big-launch-once. Mitigated only by ruling 1 being frozen and held.
  • Speed vs integration tension — the fortress is the slowest path to market, and speed is the binding constraint. Reconciled only by freezing the lightest fortress that still lands "this changes everything."
  • Big-bang fragility — everything must work on day one, in front of live customers, run by one person. No soft launch to catch cracks; a crack inverts the "changes everything" moment. Raises the pre-launch verification bar.
  • Renewal cliff — the year-one discount commits the product to deep embedding within twelve months, not just the sales motion. If embedding hasn't happened, the price jump is the churn trigger.
  • Unshipped moat — domain density is the real moat (tacit, regulatory, slow to replicate); tech-savvy-pre-AI is an accelerant that erodes as AI lowers the technical bar for everyone. But a moat that lives in specs and one founder's head is a head start, not a moat — shipping is what converts it into something a competitor must out-build and out-domain to touch. Reinforces: ship the minimum fortress, fast.
  • Untested thesis — building in silence puts first real market feedback after the largest spend. Compatible mitigation: design partners / letters of intent / pre-sale conversations with real RTOs during the build. (Audit's walked-away-buyer caveat: reasoned persona, not field data — a go-big motion amplifies the cost of leaving it untested.)