launch-to-qualified-pipeline

Launch to Qualified Pipeline

Outcome

Produce a sourced launch brief, reviewed channel action ledger, linked inbound signals, and a qualified pipeline decision backed by Sales records. Draft, approved, published, lead captured, qualified, contacted, and booked are distinct states.

When to use

Use when a B2B company wants one accountable route from a new offer and site to qualified enquiries. A simple strategy question can stay in one Crew. Use the existing Sales Playbook for its qualification, follow-up, and meeting subroute.

Discovery and user direction

Inspect current Crews, site and offer, customer evidence, approved claims, assets, channels, campaign IDs, form and CRM records, contact policy, budget, owners, and meeting source. Propose reuse or reviewed creation. Show the exact plan before Builder applies it; selection changes nothing.

Required inputs

Bind launch and offer version, audience and market, source-backed message, channel and budget bounds, visitor action, qualification and contact policy, attribution rule, baseline or baseline-first choice, and review owners. An export supports a manual first route.

Plan and AgentWorks tools

Reuse or propose GTM Strategy Analyst, Launch Coordinator, Lead Intake & Qualifier, and Sales Follow-up Coordinator. Add Website Growth Starter only for needed site work. Builder may use `create_crew` with stable keys. Strategy emits `gtm-launch-brief/v1`; validate it before Launch reads it. Launch emits `launch-signal-register/v1`; validate it and match an exact event/lead before Qualification. Then use Inbound Lead-to-Meeting Review and its validator for the qualification-to-follow-up route. Publishing, spend, and contact each require separate authorized action routes.

Knowledge and persistence

Save offer, launch, asset, campaign, source, event, lead, action, Crew, and run IDs; approvals; provider receipts; metric definitions; source times; and prior decisions. Re-read current states and deduplicate before every repeat.