Pattern: Sequential Pipeline | Team size: 5 agents
This team runs the campaign as a stage-gated pipeline from strategy through execution and measurement. A sequential structure reduces rework by ensuring each step (positioning, creative, channels, analytics) is validated before the next begins, which is ideal for a time-bound app launch.
Launch a marketing campaign for a new mobile fitness app
Create an agent team to launch a marketing campaign for a new mobile fitness app using a Sequential Pipeline called “Launch Assembly Line.” Operate stage-gated: each agent must complete and get sign-off from the next agent (via written review notes) before the pipeline proceeds. Maintain tight dependencies to reduce rework.
PROJECT NAME (use exactly for file paths): mobile_fitness_app_launch
GLOBAL RULES (applies to all agents)
- Write all deliverables as Markdown and save them in the specified file paths under: outputs/agent_teams_demo/mobile_fitness_app_launch/
- Do not assume the app name; use placeholder “AppName” unless explicitly defined inside the work.
- If any critical input is missing (platforms, countries, pricing, category, unique features), make explicit assumptions in an “Assumptions” section and keep them minimal. Do not block progress; proceed with reasonable defaults (US/UK, iOS+Android, English).
- Use consistent terminology across all files: the same segment names, value props, offer, and KPI definitions.
- Every agent must include a “Risks & Mitigations” subsection with 5 bullets minimum.
- Collaboration mechanic: at the end of each agent’s file, add a section called “Questions for Next Agent + Requested Decisions” with 5–10 precise questions. The next agent must answer these at the top of their file in a section called “Upstream Answers & Alignment Notes,” explicitly stating what they adopted/changed and why.
- Challenge mechanic: each downstream agent must include a “Challenge Upstream Assumptions” section with at least 3 challenges and suggested adjustments. If no changes, explicitly justify why.
- Stage gate: the downstream agent may not change upstream strategy silently; any proposed changes must be logged in “Proposed Strategy Deltas” with rationale and impact.
DELIVERABLES OVERVIEW (pipeline order and dependencies)
1) Go-to-Market Strategist
- Must complete before Messaging & Brand Copywriter begins.
2) Messaging & Brand Copywriter
- Must complete before Creative Producer begins.
3) Creative Producer
- Must complete before Channel Activation Manager begins.
4) Channel Activation Manager
- Must complete before Analytics & Growth Optimizer begins.
5) Analytics & Growth Optimizer
- Must complete before final synthesis/review begins.
6) Synthesis/Review (all agents contribute via a single consolidated final file authored by the Analytics & Growth Optimizer, incorporating feedback notes from others)
AGENT 1: GO-TO-MARKET STRATEGIST
Objective: Define target segments, positioning, core promise, pricing/offer, launch goals with success metrics, and the launch narrative.
Output file: outputs/agent_teams_demo/mobile_fitness_app_launch/01_gtm_strategy.md
Structure (must follow exactly; include headings in this order):
1. Executive Summary (120–180 words)
2. Assumptions (bullet list)
3. Market Context & Customer Problem (250–350 words)
4. Target Segments (define 3 primary + 2 secondary)
- For each segment, include: “Who,” “Job-to-be-done,” “Top 3 pains,” “Top 3 desired outcomes,” “Objections,” “Where they hang out (channels),” “Triggers to install”
5. Positioning
- Positioning statement (1 sentence)
- Category framing (2 options)
- Competitive differentiation (table with 5 rows: Differentiator | Why it matters | Proof idea)
6. Core Promise & Reasons to Believe
- Core promise (1 sentence)
- 5 reasons-to-believe (bullets)
- 3 proof assets to create (e.g., testimonials, benchmarks) with notes
7. Offer & Pricing Strategy (choose one primary offer + one alternate)
- Include: free trial length, intro offer, annual vs monthly angle, and a launch promo mechanic
8. Launch Goals & Success Metrics
- Define: North Star Metric, input metrics, guardrails
- Provide numeric targets for: installs, activation, trial start, trial-to-paid, CAC, ROAS (even if assumed)
9. Funnel Definition & Measurement Boundaries
- Define funnel stages from impression → paid subscriber with event names (high level)
10. Risks & Mitigations (>=5 bullets)
11. Questions for Next Agent + Requested Decisions (5–10 items)
AGENT 2: MESSAGING & BRAND COPYWRITER
Objective: Translate positioning into value props, taglines, ad copy, store listing copy, and lifecycle messaging frameworks.
Dependency: Must read and adhere to 01_gtm_strategy.md before writing. Must answer the GTM questions at top.
Output file: outputs/agent_teams_demo/mobile_fitness_app_launch/02_messaging_copy.md
Structure (must follow exactly):
1. Upstream Answers & Alignment Notes (answer each question from Agent 1; note adopted decisions)
2. Challenge Upstream Assumptions (>=3 challenges with suggested refinements)
3. Messaging Architecture
- Brand voice (5 traits + do/don’t table)
- Core narrative (120–160 words)
- 5 key value propositions (each: headline + 2 support bullets)
- Objection handling (table with 6 objections | response | proof cue)
4. Taglines & Hooks
- 15 tagline options (<=8 words each)
- 20 short hooks (<=6 words each) optimized for paid social
5. Paid Ad Copy Sets (channel-agnostic)
- Provide 6 themed copy sets; each set includes:
- 1 primary text (<=120 chars)
- 2 alternate primary texts (<=150 chars)
- 1 headline (<=35 chars)
- 1 description (<=60 chars)
- 1 CTA recommendation
6. App Store Listing Copy (ASO-ready)
- AppName short description (<=30 chars)
- Subtitle (<=30 chars)
- Promo text (<=170 chars)
- Long description (350–450 words)
- 10 keywords (comma-separated)
7. Landing Page Wire Copy (above-the-fold + sections)
- Hero headline + subhead + 3 bullets + CTA
- 4 section headers with 2–3 bullets each
- Social proof block copy (placeholders acceptable)
8. Lifecycle Messaging Frameworks
- Onboarding email series: 5 emails (subject line + 60–100 word body outline)
- Push notifications: 12 pushes grouped by lifecycle stage (new user, engaged, lapsing)
- In-app paywall microcopy: 8 lines (<=12 words each)
9. Risks & Mitigations (>=5 bullets)
10. Questions for Next Agent + Requested Decisions (5–10 items)
AGENT 3: CREATIVE PRODUCER
Objective: Develop creative concepts and production briefs for ad assets aligned to channel specs and messaging.
Dependency: Must read and adhere to 01_gtm_strategy.md and 02_messaging_copy.md before writing. Must answer Agent 2 questions at top.
Output file: outputs/agent_teams_demo/mobile_fitness_app_launch/03_creative_production.md
Structure (must follow exactly):
1. Upstream Answers & Alignment Notes (answer each question from Agent 2)
2. Challenge Upstream Assumptions (>=3 challenges; include creative implications)
3. Creative Strategy Snapshot (150–220 words)
- Creative objectives, target emotions, “what we must prove,” brand constraints
4. Concept Matrix (table)
- 10 concepts minimum; columns: Concept name | Segment | Hook | Story beats (3) | Proof element | CTA | Best channels
5. Asset List by Channel (must include: Meta, TikTok, YouTube Shorts, Apple Search Ads, Google UAC, Influencer/UGC)
- For each channel: formats, aspect ratios, max lengths, and “must-have” elements
6. Production Briefs
- 3 UGC creator briefs (each 180–250 words): persona, scenario, script beats, do/don’t, deliverables
- 2 motion/video ad briefs (each 180–250 words): storyboard frames (6 frames), supers, VO notes
- 3 static ad briefs (each 120–180 words): layout, copy placement, visual direction
7. Shot List & B-roll Checklist (>=20 items)
8. Creative QA Checklist (>=15 items)
9. Risks & Mitigations (>=5 bullets)
10. Questions for Next Agent + Requested Decisions (5–10 items)
AGENT 4: CHANNEL ACTIVATION MANAGER
Objective: Plan channel mix and execution (paid social, search, influencers, partnerships, ASO) with budgets, targeting, and flighting.
Dependency: Must read and adhere to 01_gtm_strategy.md, 02_messaging_copy.md, 03_creative_production.md before writing. Must answer Agent 3 questions at top.
Output file: outputs/agent_teams_demo/mobile_fitness_app_launch/04_channel_activation_plan.md
Structure (must follow exactly):
1. Upstream Answers & Alignment Notes (answer each question from Agent 3)
2. Challenge Upstream Assumptions (>=3 challenges; include budget/channel implications)
3. Channel Mix & Rationale (200–300 words)
4. Budget & Flighting Plan
- Assume a total launch budget (state it) and allocate by channel (table)
- 6-week flighting calendar (week-by-week table): objective, channels, creative focus, KPI focus
5. Paid Social Plan (Meta + TikTok)
- Targeting: prospecting segments + interest/behavior ideas
- Campaign structure: campaigns/ad sets, optimization events, exclusions
- Creative rotation rules and refresh cadence
6. Paid Search & App Campaigns (Apple Search Ads + Google UAC)
- Keyword themes (>=6), match types, negatives
- Creative set usage and mapping to intent
7. Influencer/UGC Activation
- Creator tiers, pricing assumptions, outreach script (120–160 words)
- Brief distribution and content usage rights notes
8. Partnerships & Community
- 5 partnership ideas (gyms, health brands, employers, etc.) with proposed value exchange
9. ASO Plan
- Metadata strategy, screenshot/storyboard plan (text-only), review generation plan
10. Pre-Launch & Launch Ops Checklist
- 20-item checklist, grouped by week
11. Risks & Mitigations (>=5 bullets)
12. Questions for Next Agent + Requested Decisions (5–10 items)
AGENT 5: ANALYTICS & GROWTH OPTIMIZER
Objective: Implement attribution/measurement, define test plans, monitor KPIs, and iterate creatives and spend based on performance.
Dependency: Must read and adhere to files 01–04 before writing. Must answer Agent 4 questions at top.
Output files:
- outputs/agent_teams_demo/mobile_fitness_app_launch/05_analytics_growth_plan.md
- outputs/agent_teams_demo/mobile_fitness_app_launch/06_final_synthesis_review.md (this is the required final synthesis step file)
File 05 structure (must follow exactly):
1. Upstream Answers & Alignment Notes (answer each question from Agent 4)
2. Challenge Upstream Assumptions (>=3 challenges; include measurement implications)
3. Measurement Strategy
- Attribution approach (MMP assumed or not), SKAN considerations, web-to-app if any
- Source-of-truth hierarchy (what tool answers what)
4. Event Taxonomy (table; >=20 events)
- Columns: Event name | Trigger | Properties | Funnel stage | Owner
5. KPI Framework
- Definitions and formulas for: CAC, CPI, CPA (trial start), activation rate, trial-to-paid, ROAS, retention (D1/D7/D30)
- Reporting cadence (daily/weekly) with owners
6. Dashboard Spec (wireframe in text)
- Sections, charts, filters, and required breakdowns (channel, creative, segment)
7. Experimentation Plan
- 10 experiments minimum; each with: hypothesis, change, metric, duration, pass/fail threshold
- Include at least: onboarding, paywall, creative hook, ASA keywords, TikTok iteration
8. Optimization Playbooks
- Paid social: 8 rules (when to scale/cut)
- Search/UAC: 6 rules
- Creative: 6 rules (fatigue detection + refresh triggers)
9. Risks & Mitigations (>=5 bullets)
10. Inputs Needed for Week-2 Iteration (bulleted list)
FINAL SYNTHESIS/REVIEW STEP (must be last; produce file 06)
Objective: Consolidate the entire pipeline into a single launch-ready campaign plan, reconcile conflicts, and list final decisions + next actions. This must incorporate quick feedback from other agents: before writing file 06, review files 01–05 and explicitly note any inconsistencies you resolved.
Output file: outputs/agent_teams_demo/mobile_fitness_app_launch/06_final_synthesis_review.md
File 06 structure (must follow exactly; obey word counts):
1. One-Page Launch Plan (350–450 words)
- Audience, promise, offer, channels, measurement in one cohesive narrative
2. Final Decisions Log (table; >=12 rows)
- Decision | Options considered | Final choice | Owner | Date/Phase | Notes
3. Integrated Asset Map (table)
- Channel | Asset type | Concept/Message | Format | Destination | KPI | Status (Planned)
4. Stage-Gate Reconciliation Notes (200–300 words)
- List at least 6 mismatches across earlier stages and how they were resolved
5. 6-Week Execution Timeline (table)
- Week | Key actions | Primary KPI | Owner
6. Top 10 Risks to Launch + Mitigations (bullets)
7. Immediate Next 15 Tasks (numbered list; each task has owner + due “Day X”)
COORDINATION INSTRUCTIONS (enforce throughout)
- Sequential pipeline enforcement: no downstream file may be drafted until upstream file(s) exist.
- Each agent must read all upstream files and reuse exact segment names and metric definitions unless formally changed via “Proposed Strategy Deltas.”
- Keep a “single source of truth” for strategy: if Agent 1 defines a segment as “Busy Professionals,” do not rename it later.
- If you must introduce new assumptions, log them clearly and propagate them forward.
- Maintain practical realism: timelines, budgets, and asset volumes must be plausible for a small launch team.
BEGIN NOW
- Instantiate the five agents with the exact roles/titles provided.
- Execute the pipeline in order, producing files 01–06 at the specified paths.
- End only when the synthesis/review file (06) is complete and internally consistent with the prior artifacts.
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.