Pattern: Sequential Pipeline | Team size: 5 agents
This team moves the campaign from strategy to execution in a controlled handoff sequence, reducing rework and ensuring each stage has clear inputs/outputs. A pipeline fits a launch where positioning, creative, media, and measurement must align tightly before spend scales.
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 the “Launch Assembly Line” Sequential Pipeline. You will run work in strict stage order with explicit handoffs. Produce all deliverables as markdown files in the exact paths specified below. Assume no prior assets exist; make reasonable assumptions but label them clearly. Keep every stage aligned to the same target audiences, positioning, and measurement plan.
PROJECT NAME (use exactly): mobile_fitness_app_launch_campaign
GLOBAL RULES
- Sequential pipeline: Agent 1 must complete before Agent 2 begins; Agent 2 before Agent 3; Agent 3 before Agent 4; Agent 4 before Agent 5; then final synthesis.
- Each agent must:
- Read all prior outputs before starting.
- Start by listing “Inputs consumed” (bullet list referencing prior file sections) and “Open questions/assumptions” (max 10 bullets).
- End by writing “Handoff notes to next agent” (bullet list, max 12 bullets) including any decisions that must not be changed downstream.
- Add a “Risks & mitigations” section (3–6 bullets).
- Collaboration mechanics:
- At the end of each stage, write 5–8 “Challenges to assumptions” bullets where you critique your own work and call out what could be wrong (market, audience fit, creative feasibility, tracking feasibility, budget realism).
- Also write 3–5 “Requests to upstream/downstream” bullets: what you wish you had from previous stage and what you need the next stage to preserve.
- Use consistent naming: Segments must have stable IDs (e.g., S1, S2, S3) used across all files; personas must have stable IDs (P1, P2, etc.) and map to segments.
- Fitness app context constraints (assume unless otherwise stated):
- Product: iOS + Android mobile fitness app with on-demand workouts (strength, HIIT, yoga), personalized plans, habit tracking, and beginner-friendly programs.
- Monetization: freemium with subscription; assume $59.99/year or $9.99/month; 7-day free trial.
- Geography: US launch.
- Compliance: Do not use medical claims; avoid “guaranteed weight loss” language; be careful with sensitive attributes.
- Output formatting:
- Use clear headings, tables where helpful, and specific, executable details.
- Include word-count targets per file; stay within ±15%.
- No placeholder text like “TBD” except for items explicitly flagged as assumptions.
DELIVERABLE FILES (create all)
1) outputs/agent_teams_demo/mobile_fitness_app_launch_campaign/01_market_audience_strategy.md
2) outputs/agent_teams_demo/mobile_fitness_app_launch_campaign/02_messaging_offer_architecture.md
3) outputs/agent_teams_demo/mobile_fitness_app_launch_campaign/03_creative_direction_ads_appstore.md
4) outputs/agent_teams_demo/mobile_fitness_app_launch_campaign/04_media_plan_calendar.md
5) outputs/agent_teams_demo/mobile_fitness_app_launch_campaign/05_analytics_experimentation_plan.md
6) outputs/agent_teams_demo/mobile_fitness_app_launch_campaign/06_synthesis_launch_brief.md
AGENT 1: Market & Audience Strategist
Task: Define target segments, personas, key insights, and competitive positioning for the fitness app.
Dependency: This task must complete before Agent 2 begins.
Create: outputs/agent_teams_demo/mobile_fitness_app_launch_campaign/01_market_audience_strategy.md
Length target: 1,600–2,000 words.
Required sections (use exactly these headings):
1. Inputs consumed (for Agent 1, list only the global constraints above)
2. Open questions/assumptions
3. Market snapshot (US mobile fitness apps)
- Include: major demand drivers, seasonality notes, pricing norms, and 5 competitor archetypes (not just brand names; describe archetypes).
4. Competitive positioning map
- Provide a 2x2 matrix description (axes you choose) and place at least 6 competitors (by example brand) + “Our App”.
- Explain why the axes matter.
5. Target segments (3–5 segments; label S1–S5)
For each segment include a table with:
- Segment name + ID
- Core job-to-be-done
- Primary pain points (3–5)
- Motivators (3–5)
- Objections/barriers (3–5)
- Triggers (moments that prompt app download) (3–5)
- Channels they over-index on (ranked top 5)
- Message angles that tend to work (3–5)
- “What to avoid saying” (2–4)
6. Personas (2–4 personas; label P1–P4; map each to a segment)
For each persona include:
- Quick bio (age range, lifestyle, fitness context)
- Goals hierarchy (top 5)
- Decision criteria (top 5)
- Typical weekly routine constraints
- Most believable proof types (e.g., UGC, expert, before/after but compliant)
7. Primary insight & positioning
- One-sentence positioning statement (must be defensible vs competitors)
- 3 supporting pillars with evidence types (what proof we’ll use)
- Brand voice traits (5 traits + “do/don’t” examples)
8. Risks & mitigations
9. Challenges to assumptions
10. Requests to upstream/downstream
11. Handoff notes to next agent
AGENT 2: Messaging & Offer Architect
Task: Create value proposition, core messages, launch offer, and CTA hierarchy for each audience segment.
Dependency: Must not start until file 01_market_audience_strategy.md is complete.
Create: outputs/agent_teams_demo/mobile_fitness_app_launch_campaign/02_messaging_offer_architecture.md
Length target: 1,400–1,800 words.
Required sections:
1. Inputs consumed (cite S1–Sx and P1–Px from Agent 1)
2. Open questions/assumptions
3. Value proposition architecture
- Create: “Core value prop” (1 sentence), “Expanded value prop” (80–120 words), and “RTBs” (reasons to believe) list (8–12 bullets).
4. Messaging matrix by segment (must cover every segment S1–Sx)
Provide a table per segment with:
- Primary promise (1 sentence)
- 3 message pillars (each with 2 example lines)
- Objection handling lines (3)
- Proof points to use (3–5)
- Emotional tone (choose 3 adjectives)
- CTA hierarchy (Primary / Secondary / Tertiary)
5. Offer strategy (launch)
- Define: baseline pricing (use global assumption), launch incentive (choose ONE), eligibility, duration, and guardrails.
- Provide 3 offer variants to test (with hypotheses and which segment they target).
- Include compliant language notes.
6. Copy blocks (ready to use)
- 10 ad headlines (max 35 characters each)
- 10 primary texts (40–90 words each)
- 12 short hooks (max 8 words)
- 6 CTAs (2–4 words each)
Ensure each is tagged with the target segment ID(s).
7. Landing/App Store messaging alignment
- Provide: top-of-page hero headline options (5), subhead options (5), and “feature bullets” (10) mapped to message pillars.
8. Risks & mitigations
9. Challenges to assumptions
10. Requests to upstream/downstream
11. Handoff notes to next agent (must include: which messages are “non-negotiable”, and which are experimental)
AGENT 3: Creative Director (Ads + App Store)
Task: Translate messaging into ad concepts, visual direction, UGC scripts, and App Store screenshot/video briefs.
Dependency: Must not start until file 02_messaging_offer_architecture.md is complete.
Create: outputs/agent_teams_demo/mobile_fitness_app_launch_campaign/03_creative_direction_ads_appstore.md
Length target: 1,800–2,300 words.
Required sections:
1. Inputs consumed (cite specific pillars, offers, CTAs from Agent 2)
2. Open questions/assumptions
3. Creative strategy overview
- Define: creative north star (1 paragraph), 3 design principles, and 3 “performance creative rules” (e.g., hook by second 2).
4. Ad concept lineup (12 concepts total)
- Provide 12 concepts organized into 3 buckets: Problem/Solution, Social Proof, Product Demo (4 each).
For each concept include:
- Concept name
- Target segment IDs
- Hook (first 2 seconds) script (1–2 lines)
- Video storyboard beats (6–8 beats)
- On-screen text plan (5–7 frames)
- Voiceover (optional) (40–70 words)
- CTA + offer callout
- Production complexity (Low/Med/High) + rationale
- “Why it should work” (2–3 bullets)
5. UGC creator script pack (8 scripts)
- For each: creator profile, setting, script (120–180 words), b-roll list (6–10 shots), do/don’t notes.
6. Static ad system (for Meta + display-like placements)
- Provide 6 static ad templates described in words (layout, headline placement, imagery style).
- For each template: 3 headline options + 2 body options tagged by segment.
7. App Store creative brief
- Screenshot set: 8 screenshots
For each screenshot: title (max 30 chars), subtitle (max 45 chars), visual description, feature proof element.
- App Preview video: 15–30s outline with timestamps and on-screen text.
- Keywords/themes consistency notes.
8. Creative testing plan (creative-only)
- Define: 6 test cells (hook types x proof types), success metrics, and decision rules (keep/iterate/kill).
9. Risks & mitigations
10. Challenges to assumptions
11. Requests to upstream/downstream
12. Handoff notes to next agent (must specify: which concepts are priority for Week 1 vs Week 3)
AGENT 4: Media Planner & Channel Owner
Task: Select channels, build budget split, set targeting approach, and produce an executable media plan and calendar.
Dependency: Must not start until file 03_creative_direction_ads_appstore.md is complete.
Create: outputs/agent_teams_demo/mobile_fitness_app_launch_campaign/04_media_plan_calendar.md
Length target: 1,600–2,200 words.
Required sections:
1. Inputs consumed (cite segment-channel preferences, offer, and priority concepts)
2. Open questions/assumptions (must include a total launch budget assumption and CPI/CAC benchmark assumptions)
3. Channel strategy (selection + rationale)
- Must include at least: Meta (FB/IG), TikTok, Apple Search Ads, Google App Campaigns/YouTube.
- Optional: influencer/affiliate, Reddit, podcast, etc. (only if justified).
4. Budget & phasing plan
- 3 phases: Pre-launch (optional), Launch Weeks 1–2, Scale Weeks 3–8
- Provide a table with: channel, objective, weekly budget, KPI target, creative types needed.
5. Targeting & structure by channel
For each primary channel:
- Campaign structure (e.g., prospecting, retargeting, lookalikes)
- Targeting approach mapped to segments (interest/behavior/contextual/search intent)
- Placement notes
- Creative mapping (which 3–5 concepts/templates from Agent 3 to run)
- Frequency/control notes
6. Media calendar (8 weeks)
- Provide a week-by-week table with: channel focus, key creative drops, offer messaging, test focus, and decision checkpoint.
7. Operational runbook
- Naming conventions (campaign/ad set/ad)
- Asset checklist
- Launch checklist (10–15 bullets)
- Optimization cadence (daily/biweekly/weekly actions)
8. Risks & mitigations
9. Challenges to assumptions
10. Requests to upstream/downstream
11. Handoff notes to next agent (must include: what tracking is required per channel and which KPIs are decision-making)
AGENT 5: Analytics & Experimentation Lead
Task: Define KPIs, tracking plan, attribution approach, and a test-and-learn roadmap for launch and scale.
Dependency: Must not start until file 04_media_plan_calendar.md is complete.
Create: outputs/agent_teams_demo/mobile_fitness_app_launch_campaign/05_analytics_experimentation_plan.md
Length target: 1,700–2,300 words.
Required sections:
1. Inputs consumed (cite channels, KPI targets, campaign structure from Agent 4)
2. Open questions/assumptions (must include MMP assumption—e.g., AppsFlyer/Adjust/Branch—and analytics stack assumption)
3. KPI framework
- North Star metric definition
- Funnel metrics: Impression → Click → Install → Trial Start → Subscription → Week-4 retention
- Provide target ranges (not single numbers) for each funnel step with brief rationale.
4. Event taxonomy (app + web if any)
- Provide a table of events with: event name, trigger definition, properties, and why it matters.
- Must include: install, first_open, signup, onboarding_complete, workout_started, workout_completed, plan_created, trial_started, subscription_started, subscription_renewed, cancel, refund (if applicable).
5. Tracking implementation plan
- Per channel: required parameters, attribution windows assumptions, deep links, SKAN considerations (iOS).
- QA checklist (10–15 items).
6. Attribution & measurement approach
- Define: how you’ll triangulate (MMP + platform + SKAN + cohorting).
- Incrementality approach proposal (e.g., geo split or holdout) with feasibility notes.
7. Experimentation roadmap (8 weeks)
- Provide 12 experiments total across: creative, targeting, offer, onboarding, paywall.
- For each experiment: hypothesis, primary metric, secondary metric, sample size proxy/decision rule, duration, dependencies, and “what we do if it wins/loses”.
- Explicitly mark which experiments cannot begin until tracking items are implemented.
8. Dashboard spec
- List dashboard pages (3–5), charts per page, filters, and refresh cadence.
9. Risks & mitigations
10. Challenges to assumptions
11. Requests to upstream/downstream
12. Handoff notes (to synthesis lead): top 10 measurement “non-negotiables”
FINAL SYNTHESIS / REVIEW STEP (Team Lead: you)
Dependency: Must not start until files 01–05 are complete.
Create: outputs/agent_teams_demo/mobile_fitness_app_launch_campaign/06_synthesis_launch_brief.md
Length target: 1,200–1,600 words.
Synthesis requirements:
- Purpose: produce an exec-ready launch brief that aligns strategy, messaging, creative, media, and measurement with no contradictions.
- Required sections (use exactly):
1. Executive summary (150–220 words)
2. Target segments & positioning (must reference S1–Sx; 250–350 words)
3. Messaging & offer snapshot (must include the chosen launch incentive + CTA hierarchy; 200–300 words)
4. Creative plan (priority concepts Week 1 and Week 3; 200–300 words)
5. Media & budget plan (phase table summary + key calendar milestones; 250–350 words)
6. Measurement & experimentation (north star, tracking must-haves, 8-week test themes; 250–350 words)
7. Integrated risk register (top 8 risks with owner agent + mitigation)
8. Final consistency check (bullet list)
- List at least 10 checks verifying IDs, claims compliance, offer consistency, channel/creative fit, and KPI measurability.
- Include a “Decision log” table with 10–15 key decisions, the owner agent, and the file/section where it was decided.
- End with “Next 7 days action plan” (12–18 bullets) that is operational and sequenced.
EXECUTION INSTRUCTIONS
- Run Agent 1 → Agent 2 → Agent 3 → Agent 4 → Agent 5 → Final synthesis in order.
- After each agent finishes, ensure their file is saved to the specified path before starting the next agent.
- Preserve segment IDs and persona IDs consistently across all stages.
- Do not materially change upstream decisions downstream; if you believe a change is required, document it as a “Proposed change” in “Challenges to assumptions” and carry it into synthesis for resolution.
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.