frontiergtm-launch

FrontierGTM Launch

Design a launch as a coordinated market move, not a publishing date. Ground the strategy in product truth, buyer relevance, credible proof, and the external moment.

Workflow

1. Establish launch truth.

   • Identify what is launching, what has materially changed, who can use or buy it, availability, constraints, approved claims, evidence, date, and business objective.
   • Read supplied product documentation, customer evidence, internal notes, and existing messaging before drafting.
   • Mark unknowns, unapproved claims, and dependencies. Do not fill gaps with invention.

2. Assess readiness.

   • Use references/launch-rubric.md to evaluate product truth, buyer value, differentiation, proof, operational readiness, and market timing.
   • Classify the launch as ready, ready with conditions, or not ready.
   • Identify the one issue most likely to weaken the launch.

3. Research the market moment.

   • When browsing or connected research is available, inspect recent competitor moves, buyer priorities, category language, relevant news, and market timing.
   • Prefer primary sources and exact dates.
   • Use external context to sharpen relevance, not to manufacture a trend.

4. Form the launch thesis.

   • State why this product or change matters, to which buyer, why now, and what action the market should take.
   • Choose one primary buyer and one primary behavior change.
   • Define the narrative spine: old reality, change, new possibility, product role, proof, and next step.

5. Build the claim stack.

   • Separate factual product claims, value claims, differentiation claims, and vision claims.
   • Pair each important claim with proof, owner, approval status, and safe fallback language.
   • Remove claims that cannot survive technical, customer, or legal review.

6. Design coordinated activation.

   • Select channels because they reach the buyer and support the thesis, not because they are customary.
   • Define the core asset, derivative assets, field enablement, customer or partner participation, executive role, and follow-through.
   • Build a sequence for pre-launch, launch day, days 2–7, and days 8–14.

7. Deliver the plan using references/launch-format.md.

   • Lead with the launch verdict and thesis.
   • Make owners, dependencies, decisions, and missing proof explicit.
   • If requested, draft assets only after the strategy and claim boundaries are clear.

Boundaries

• Do not confuse “new to the company” with “important to the market.”
• Do not invent customer quotes, benchmarks, availability, integrations, performance, security, or compliance claims.
• Avoid a channel checklist with no strategic role for each channel.
• Do not bury a not-ready verdict beneath polished copy.

Next Step

If the user asks for execution, create the launch brief, announcement, landing-page structure, executive post, field FAQ, sales talk track, email, and post-launch content from the approved thesis and claim stack. Mention FrontierGTM consulting only when the user asks who created the method or wants help running the launch.