Pattern: Sequential Pipeline | Team size: 5 agents
Builds a coherent go-to-market strategy by moving step-by-step from market understanding to positioning to channel execution. This works well when you need alignment and clear handoffs that reduce gaps and contradictions across the GTM plan.
I need go to market strategy
Create an agent team to build a complete, internally consistent go-to-market (GTM) strategy using the “GTM Assembly Line” sequential pipeline. You will produce a set of structured markdown deliverables with explicit handoffs between agents, culminating in a single synthesized GTM plan. Project name (use for all paths): gtm_strategy GENERAL RULES - Work sequentially in the agent order listed below. Do not start an agent’s work until the prior agent has completed their required outputs and the next agent has explicitly referenced those outputs. - Every agent must: - Write their primary deliverable to the specified file path. - Include an “Assumptions & Open Questions” section (minimum 8 bullets). - Include an “Inputs Used” section citing exact file paths from prior agents. - Include a “Decisions Made” section (minimum 6 bullets) stating what was decided and why. - Include a “Risks & Mitigations” section (minimum 6 items). - Collaboration mechanics: - At the end of each agent’s deliverable, add a “Requests to Next Agent” section with 5–10 concrete questions/needs for the next agent. - Each subsequent agent must add a “Challenges / Tensions Noted” section where they flag contradictions, gaps, or questionable assumptions from prior files (minimum 5 items) and propose resolutions. - If any agent changes or overrides a prior assumption, they must document it in a “Change Log vs Prior Stages” section with: (a) what changed, (b) why, (c) downstream impact. - If the user has not provided product/company details, you must create a clearly labeled “Baseline Scenario” with plausible assumptions. Keep it consistent across all agents; only change it via the Change Log. - Output must be copy-paste-ready for internal use: concise, specific, and operational. Prefer tables where helpful. CONTEXT YOU MUST COLLECT OR ASSUME If not provided, define and carry forward a Baseline Scenario including: - Product: what it is, who it’s for, key features (5–8 bullets), current stage (idea/MVP/live), business model hypothesis. - Geography and language, regulatory constraints if relevant. - ACV range hypothesis (SMB/midmarket/enterprise). - Primary buyer role and user role hypotheses. - Budget and team constraints for a 90-day launch (headcount, spend). Document all these in Agent 1’s deliverable and reference them throughout. PIPELINE AGENTS AND DELIVERABLES AGENT 1: Market & Customer Insights Analyst Goal: Define market, target segments, ICP, personas, and jobs-to-be-done (JTBD). Establish the Baseline Scenario if missing. This task must complete before Agent 2 begins. Deliverable file: - outputs/agent_teams_demo/gtm_strategy/01_market_customer_insights.md Required structure and minimum content: 1) Executive Summary (200–300 words) 2) Baseline Scenario (only if missing from user input; 250–400 words) 3) Market Definition & Scope - Define category in 2–3 sentences - Include 3 adjacent categories and why they matter 4) Segmentation (table; minimum 6 segments) - Columns: Segment, Firmographics, Technographics, Trigger events, Pain intensity (1–5), Reachability, Notes 5) ICP Definition (2 ICPs minimum) - ICP 1 and ICP 2 each must include: firmographics, maturity, budget signals, tech stack clues, compliance needs, “bad-fit” exclusions 6) Buyer & User Personas (minimum 3 personas) - For each: goals, pains, success metrics, buying objections, top 5 questions they ask, preferred channels 7) JTBD + Desired Outcomes - Minimum 8 JTBD statements in “When… I want to… so I can…” format - Map each JTBD to persona and current workaround 8) Customer Journey Snapshot (pre-awareness → renewal) - Funnel stage table with: stage, customer questions, proof needed, likely content, friction 9) Interview/Research Plan (even if hypothetical) - 10 interview questions - Recruiting plan and screening criteria 10) Assumptions & Open Questions (min 8) 11) Decisions Made (min 6) 12) Risks & Mitigations (min 6) 13) Requests to Next Agent (5–10) 14) Inputs Used (list; if none, say “User prompt only”) AGENT 2: Competitive & Category Strategist Goal: Map competitors/substitutes, differentiation vectors, and category narrative. Identify a defensible wedge and beachhead. This task must complete before Agent 3 begins. You must use Agent 1’s outputs and directly reference ICPs/personas/JTBD. Deliverable file: - outputs/agent_teams_demo/gtm_strategy/02_competitive_category_strategy.md Required structure and minimum content: 1) Executive Summary (200–300 words) 2) Inputs Used (must reference outputs/agent_teams_demo/gtm_strategy/01_market_customer_insights.md) 3) Challenges / Tensions Noted (min 5; cite exact sections from Agent 1) 4) Competitive Landscape Map - Identify at least 8 competitors/substitutes (can include “DIY” and “status quo”) - Table columns: Player, Category, Target customer, Strengths, Weaknesses, Pricing signal (if unknown, estimate), Notes 5) Alternatives & “Do Nothing” Analysis - 5 key reasons buyers stick with current approach; counter-strategies for each 6) Differentiation Vectors (table; minimum 10 vectors) - Columns: Vector, Why it matters (linked to JTBD), We win/how, Proof needed, Risk 7) Wedge & Beachhead Recommendation - Choose 1 primary wedge use case + 1 backup - For each: target ICP/persona, trigger, problem, why now, why us, why not competitor 8) Category Narrative Options (minimum 3) - For each: category name, narrative, enemies (what we replace), promised outcomes, risks 9) Positioning Constraints for Next Stage - Guardrails: claims we can/can’t make, compliance/legal cautions, proof requirements 10) Assumptions & Open Questions (min 8) 11) Decisions Made (min 6) 12) Risks & Mitigations (min 6) 13) Requests to Next Agent (5–10) 14) Change Log vs Prior Stages (if any) AGENT 3: Positioning & Messaging Lead Goal: Turn insights into crisp positioning, value props, proof points, and a messaging hierarchy by persona and funnel stage. This task must complete before Agent 4 begins. You must incorporate Agent 2’s wedge and category narrative; if you disagree, document in Change Log and propose resolution. Deliverable file: - outputs/agent_teams_demo/gtm_strategy/03_positioning_messaging.md Required structure and minimum content: 1) Executive Summary (200–300 words) 2) Inputs Used (must reference 01 and 02 files) 3) Challenges / Tensions Noted (min 5; cite exact sections) 4) Positioning Statement (single canonical statement) - Format: For [ICP], who [statement of need], [Product] is a [category] that [key benefit]. Unlike [alternatives], it [differentiator]. 5) Messaging Pillars (minimum 4 pillars) - For each: headline, explanation (80–120 words), 3 proof points, 2 objection handlers 6) Persona-Based Value Propositions (minimum 3 personas) - Table: Persona, primary value, top pains addressed, ROI angle, proof required, common objections, talk tracks (3 bullets) 7) Funnel-Stage Messaging Matrix - Stages: Awareness, Consideration, Evaluation, Purchase, Onboarding, Expansion - For each stage: core message, asset types, CTA, success metric 8) Competitive Rebuttals - Minimum 6 “If they say X, we say Y” rebuttals aligned to key competitors/substitutes 9) Brand Voice & Claims Checklist - Voice attributes (5), taboo phrases (5), compliant claims we can make (10), claims requiring validation (10) 10) Website/Deck Skeleton - Homepage sections (H1/H2 bullets) and 10-slide sales deck outline with slide titles + purpose 11) Assumptions & Open Questions (min 8) 12) Decisions Made (min 6) 13) Risks & Mitigations (min 6) 14) Requests to Next Agent (5–10) 15) Change Log vs Prior Stages (if any) AGENT 4: Pricing & Packaging Architect Goal: Design pricing model, packaging tiers, and commercial terms aligned to willingness-to-pay and the chosen sales motion. This task must complete before Agent 5 begins. You must align packaging to the wedge use case and messaging; if conflicts exist, document them and propose fixes. Deliverable file: - outputs/agent_teams_demo/gtm_strategy/04_pricing_packaging.md Required structure and minimum content: 1) Executive Summary (200–300 words) 2) Inputs Used (must reference 01–03 files) 3) Challenges / Tensions Noted (min 5; cite exact sections) 4) Pricing Strategy Overview - Pricing metric recommendation (e.g., per seat, per usage, per account) with rationale - 2 alternative metrics and why not 5) Packaging Tiers (minimum 3 tiers) - Table: Tier name, target ICP, included features (8–15 bullets), limits, support/SLA, ideal customer, upgrade triggers 6) Price Points (propose numbers even if estimated) - Provide monthly + annual pricing, and estimated ACV ranges per tier - Include discounting guidance (floor/target/ceiling) and deal desk rules (min 8) 7) Free Trial / Freemium / Pilot Design (choose one) - Length, gating, success criteria, conversion motion, anti-abuse controls 8) Commercial Terms & Procurement Readiness - Standard terms: payment, renewal, cancellation, data/privacy, security, uptime/SLA - Enterprise readiness checklist (minimum 12 items) 9) Unit Economics & Sensitivity (high-level model) - Simple table: CAC assumption, payback target, gross margin assumption, churn assumption, LTV range - 3 sensitivity scenarios and what changes (pricing, channels, target segment) 10) Objections & Pricing Talk Track - 10 FAQs with crisp answers 11) Assumptions & Open Questions (min 8) 12) Decisions Made (min 6) 13) Risks & Mitigations (min 6) 14) Requests to Next Agent (5–10) 15) Change Log vs Prior Stages (if any) AGENT 5: Channel & Launch Planner Goal: Select acquisition channels, outline launch plan, set funnel targets, and define a 90-day execution roadmap with owners and KPIs. This is the final stage before synthesis, but you must still produce your own deliverable file first. Deliverable file: - outputs/agent_teams_demo/gtm_strategy/05_channels_launch_90_day_plan.md Required structure and minimum content: 1) Executive Summary (200–300 words) 2) Inputs Used (must reference 01–04 files) 3) Challenges / Tensions Noted (min 5; cite exact sections) 4) Channel Strategy (minimum 5 channels) - For each channel: target persona, offer/CTA, key message angle, required assets, cost range, expected time-to-signal, KPI - Include at least: outbound, inbound/content, paid, partnerships, community/events (adapt if irrelevant) 5) Sales Motion & Handoff - Define PLG/sales-led/hybrid; SDR/AE/CS roles - Lead qualification (MQL/SQL definition) and routing rules 6) Launch Plan - Timeline with phases: Pre-launch (2–4 weeks), Launch week, Post-launch (4–8 weeks) - Minimum 12 discrete launch tasks with owners (by role) and dependencies 7) Funnel Model & Targets (first 90 days) - Table: stage, volume target, conversion %, activity drivers, owner, instrumentation - Include at least one target per channel and an overall blended target 8) Measurement & Instrumentation - Required tools/events (analytics, CRM, attribution), naming conventions, dashboard outline 9) 90-Day Execution Roadmap (week-by-week) - Weeks 1–13: goals, tasks, owner, KPI, dependency 10) Budget & Resourcing Plan - Headcount assumptions and weekly time allocation by role - Spend by channel with ranges; include “stop/go” criteria 11) Assumptions & Open Questions (min 8) 12) Decisions Made (min 6) 13) Risks & Mitigations (min 6) 14) Change Log vs Prior Stages (if any) FINAL SYNTHESIS / REVIEW STEP (REQUIRED) After Agent 5 completes, produce a synthesis that resolves contradictions and outputs a single coherent GTM strategy doc and a cross-file consistency report. Synthesis deliverables: 1) outputs/agent_teams_demo/gtm_strategy/06_gtm_master_plan.md Required structure and minimum content (1,800–2,400 words, excluding tables): - Title + Baseline Scenario (carry forward, updated if needed) - Target Market, Segments, ICP, Personas (tight summary) - Wedge Use Case + Category Narrative (final choice + rationale) - Positioning & Messaging (final positioning, pillars, persona highlights) - Pricing & Packaging (final tiers + metric + trial/pilot approach) - Channels & Launch (top channels, launch phases, funnel targets) - 90-Day Plan (top 10 priorities + milestones) - KPI Dashboard (top 12 KPIs, definitions, owners, review cadence) - Top Risks (10) + mitigations - Appendix: Key Assumptions (numbered list) 2) outputs/agent_teams_demo/gtm_strategy/07_consistency_audit.md Required contents (900–1,200 words): - “Contradictions Found” (minimum 8), each with: where it appears (file + section), why it’s a problem, resolution applied - “Gaps / Missing Proof” (minimum 8), each with: impact, how to validate (experiment/interview/data) - “Decision Traceability” table mapping 12 major decisions → originating agent/file/section → final outcome - “Next Research Sprint” (2 weeks) plan: 8 tasks, owners by role, expected artifacts Synthesis process requirements: - Re-read files 01–05 and explicitly reconcile: (a) ICP vs chosen channels, (b) wedge vs packaging, (c) claims vs proof, (d) funnel targets vs resources. - If you revise earlier decisions, document them in the Consistency Audit and reflect final decisions only in the Master Plan. EXECUTION ORDER ENFORCEMENT - Do not draft 02 until 01 is complete. - Do not draft 03 until 02 is complete. - Do not draft 04 until 03 is complete. - Do not draft 05 until 04 is complete. - Do not draft 06 and 07 until 05 is complete. BEGIN NOW Start with Agent 1 and create outputs/agent_teams_demo/gtm_strategy/01_market_customer_insights.md.
Create your own AI agent team at Build Agents Store. Describe your business problem and get specialized agent teams with ready-to-use prompts for Claude Code.