Pattern: Sequential Pipeline | Team size: 5 agents
This team moves step-by-step from positioning to copy to design to implementation, ensuring each stage has the right inputs before proceeding. A pipeline works well for a single high-conversion page because messaging consistency and CTA alignment depend on ordered decisions.
I want to generate a page for my revenue share model agency for meta ads (also offering other socials and Google. But mainly Meta) Should include Reviews, Brief Case studies and client logo area
Create an agent team to build a single high-conversion landing page for a revenue-share model performance marketing agency focused primarily on Meta Ads (with secondary support for Google and other social platforms). Use a Sequential Pipeline: each agent must finish and hand off outputs before the next agent begins. Optimize for lead capture (book a call / apply) and credibility (reviews, brief case studies, client logos).
PROJECT NAME (use exactly): revshare-meta-ads-landing
GLOBAL CONTEXT (applies to all agents)
- Business: Revenue-share model agency. Primary service: Meta Ads (Facebook/Instagram). Secondary: Google Ads + other socials (TikTok/LinkedIn/etc) but do not dilute Meta-first positioning.
- Landing page goal: Capture qualified leads (founders/ecom brands/info product/lead gen businesses—decide specifically in Positioning) into a “Book a Call” or “Apply” funnel.
- Compliance: Avoid unverifiable claims (“guaranteed”, “instant”, “double revenue in 7 days”). Use “examples”, “recent results”, “typical range varies”, “past performance not indicative”, etc. Do not mention Meta trademarks incorrectly; use “Meta” not “Facebook Business” unless accurate. No sensitive targeting claims.
- Voice: Confident, direct, performance-oriented, founder-friendly, minimal fluff.
- Output format: All deliverables must be written to the specified files under outputs/agent_teams_demo/revshare-meta-ads-landing/. Use Markdown with clear headings and tables where requested.
- Collaboration mechanics (required):
- At the end of each agent’s work, add a “Handoff Notes” section: what was decided, what assumptions were made, what’s uncertain, and 5 specific questions for the next agent.
- Each downstream agent must: (1) quote 3 key decisions from the upstream agent, (2) challenge at least 2 assumptions, and (3) propose 1 alternative option (clearly labeled) before proceeding with the chosen approach.
- Maintain a “Decision Log” (append-only) so changes are tracked and rationale is preserved.
STACK CHOICE
- If no stack is provided by the user, default to a stack-agnostic deliverable that can be implemented in Webflow or Framer. Provide structure, components, and tracking instructions that work for either.
- Do NOT require external assets. Use placeholders where needed (logos, headshots, screenshots). Provide copy that can ship today.
FILE OUTPUTS (write all of these)
1) outputs/agent_teams_demo/revshare-meta-ads-landing/00_decision_log.md
2) outputs/agent_teams_demo/revshare-meta-ads-landing/01_positioning_brief.md
3) outputs/agent_teams_demo/revshare-meta-ads-landing/02_landing_page_copy.md
4) outputs/agent_teams_demo/revshare-meta-ads-landing/03_social_proof_pack.md
5) outputs/agent_teams_demo/revshare-meta-ads-landing/04_wireframe_and_ui_spec.md
6) outputs/agent_teams_demo/revshare-meta-ads-landing/05_build_and_tracking_spec.md
7) outputs/agent_teams_demo/revshare-meta-ads-landing/06_final_review_and_launch_checklist.md
AGENT 1: Positioning Strategist
This task must complete before Agent 2 begins.
Create outputs/agent_teams_demo/revshare-meta-ads-landing/01_positioning_brief.md and initialize outputs/agent_teams_demo/revshare-meta-ads-landing/00_decision_log.md.
Deliverables for 01_positioning_brief.md (900–1,200 words, structured exactly with these sections):
1. Target Customer (define 1 primary ICP + 1 secondary ICP)
- Industry, size, monthly ad spend or revenue bands, buying triggers, dealbreakers
2. Core Problem + Desired Outcome
- 5 bullet pains, 5 bullet desired outcomes (business outcomes, not features)
3. Offer Architecture (Revenue Share Model)
- Define: who qualifies, how rev share is framed, what’s included/excluded, typical timelines, risk reversal options (if any)
- Include a “Plain-English Revenue Share Explanation” (80–120 words)
4. Unique Mechanism (Meta-first)
- Explain why Meta is the spearhead; how other channels support it without stealing focus
5. Competitive Differentiation
- “We are not…” list (5 bullets)
- “We win when…” list (5 bullets)
6. Primary Conversion Goal + Funnel
- Decide: Book a Call vs Application vs both (pick one primary)
- Outline steps post-conversion (confirmation, qualification, scheduling)
7. Messaging Pillars
- 3 pillars, each with: claim, proof type, objection it overcomes
8. Objections + Rebuttals
- Provide 8 objections and 1–2 sentence rebuttals each
9. Compliance/Claims Guardrails
- 10 “safe claim” rules for the copywriter
Decision Log initialization in 00_decision_log.md:
- Add entries for ICP, primary CTA, offer framing, tone, and proof strategy.
- Format: Date (YYYY-MM-DD), Decision, Rationale, Owner (Agent 1).
Handoff Notes (required at bottom):
- Assumptions (at least 5)
- Unknowns (at least 5)
- 5 questions for Agent 2
AGENT 2: Conversion Copywriter
This task must start only after Agent 1 completes and writes files 00 and 01.
Create outputs/agent_teams_demo/revshare-meta-ads-landing/02_landing_page_copy.md and append relevant decisions to 00_decision_log.md.
Before writing, do the required collaboration mechanics:
- Quote 3 key decisions from Agent 1’s positioning brief.
- Challenge at least 2 assumptions and resolve them (either accept or adjust; log any changes).
- Provide 1 alternative positioning angle (label “Alternative Option”), then proceed with the chosen approach.
Deliverables for 02_landing_page_copy.md:
A) Page Outline (in order, with intent)
- Provide exact section order for a single-page landing page.
B) Final Copy (1,000–1,600 words total), with these sections and constraints:
1. Top Bar (optional): 1 line + CTA label
2. Hero
- Headline (max 12 words)
- Subheadline (max 22 words)
- 3 benefit bullets (max 10 words each)
- Primary CTA button label (2–4 words) + secondary CTA (optional)
- Micro-trust line (max 12 words)
3. “How Revenue Share Works” section
- 120–180 words + 3-step mini breakdown
4. Offer/What You Get
- 6–9 bullets, grouped into 2–3 categories
5. Who This Is For / Not For
- 5 bullets each
6. Process (Meta-first)
- 5-step process with step names (2–4 words) and 1 sentence each
7. Results/Case Study Teasers (placeholders)
- 3 teaser blocks: Title, context line, 2 quantified metrics placeholders, 1 “what we did” line
8. Reviews/Testimonial section intro copy
- 60–90 words that frames credibility safely
9. Logos section microcopy
- 1 line above logos (max 10 words) + 1 compliance note (max 14 words)
10. FAQs
- 8 FAQs, 50–90 words per answer, include: rev share mechanics, contract length, spend minimum, creative, tracking, ownership, reporting, and “do you do Google?”
11. Final CTA Section
- Headline (max 10 words), subheadline (max 18 words), 3 bullets, CTA label, and a “what happens next” 3-step list
12. Footer copy
- Short disclaimer (40–70 words) about variability of results and data privacy
C) CTA Variants
- Provide 5 alternate headline/subheadline pairs for A/B testing (each headline <= 10 words, subheadline <= 18 words).
Append to Decision Log:
- Any copy-level decisions (CTA label, section order, key claims).
Handoff Notes:
- Assumptions (5+)
- Unknowns (5+)
- 5 questions for Agent 3
AGENT 3: Social Proof Curator
This task must start only after Agent 2 completes 02_landing_page_copy.md.
Create outputs/agent_teams_demo/revshare-meta-ads-landing/03_social_proof_pack.md and append proof-related decisions to 00_decision_log.md.
Before curating, do the required collaboration mechanics:
- Quote 3 key decisions from Agents 1–2 that affect proof.
- Challenge 2 assumptions about credibility/proof and resolve them.
- Provide 1 alternative proof strategy (label “Alternative Option”), then proceed with the chosen approach.
Deliverables for 03_social_proof_pack.md (structured exactly):
1. Reviews (8 total)
- Provide 8 testimonial drafts as placeholders that sound real but are clearly marked as “TEMPLATE—replace with real client quote”.
- Each: Name (placeholder), Role, Company type, 2–3 sentence quote, and “Credibility Enhancer” (e.g., timeframe, channel, constraint).
- Include 2 “objection-handling” testimonials (e.g., skeptical of rev share, burned by agencies).
2. Mini Case Studies (3 total, 120–160 words each)
- Structure: Snapshot (industry, spend level placeholder), Challenge, What We Did (Meta-first), Outcome (use placeholder ranges), Why It Worked.
- Add a “Proof Needed” checklist per case study (screenshots, dashboard export, Shopify, etc.).
3. Client Logos Area
- Provide guidance for 12 logo slots:
- Categories (e.g., DTC, Lead Gen, B2B, Info products—choose per ICP)
- Rules for permission, grayscale use, minimum size
- Provide placeholder list of 12 “Logo Slot Labels” (e.g., “Client Logo 1 (DTC Skincare)”)
4. Compliance-Safe Proof Guidelines (must-have)
- 12 bullet rules (e.g., no “guarantees”, use date ranges, anonymize if needed)
5. Placement Map
- Map each testimonial and case study to the page sections from Agent 2 (reference by section name).
Append to Decision Log:
- Proof placement and compliance decisions.
Handoff Notes:
- Assumptions (5+)
- Unknowns (5+)
- 5 questions for Agent 4
AGENT 4: UX/UI Page Designer
This task must start only after Agent 3 completes 03_social_proof_pack.md.
Create outputs/agent_teams_demo/revshare-meta-ads-landing/04_wireframe_and_ui_spec.md and append layout decisions to 00_decision_log.md.
Before designing, do the required collaboration mechanics:
- Quote 3 key decisions from Agents 1–3 that affect layout/hierarchy.
- Challenge 2 assumptions about user flow/sections and resolve them.
- Provide 1 alternative layout approach (label “Alternative Option”), then proceed with the chosen approach.
Deliverables for 04_wireframe_and_ui_spec.md:
1. Information Architecture (IA)
- Section-by-section hierarchy with rationale (1–2 sentences each)
2. Wireframe (text-based)
- Provide a desktop wireframe and mobile wireframe using labeled blocks.
- Must include: hero, how-it-works, offer, process, proof (reviews/case studies/logos), FAQ, final CTA, footer.
3. UI Spec (implementation-ready)
- Typography scale (H1/H2/H3/body/small) with suggested sizes (px) for desktop + mobile
- Color palette (primary, secondary, neutral, background, success/warning) with HEX placeholders
- Button styles (primary/secondary), states (default/hover/disabled)
- Spacing system (8px grid guidance)
- Component specs: testimonial card, case study card, logo grid, FAQ accordion, CTA band
4. Conversion UX Details
- Form placement(s) and fields (recommend exact fields; keep minimal)
- Trust elements near CTA (privacy line, response-time line)
- Sticky CTA behavior (mobile) recommendation
5. Accessibility Checklist (10 bullets)
- Contrast, focus states, tap targets, semantic headings, etc.
Append to Decision Log:
- Layout, form field choices, and mobile sticky CTA decision.
Handoff Notes:
- Assumptions (5+)
- Unknowns (5+)
- 5 questions for Agent 5
AGENT 5: Web Builder & Tracking Lead
This task must start only after Agent 4 completes 04_wireframe_and_ui_spec.md.
Create outputs/agent_teams_demo/revshare-meta-ads-landing/05_build_and_tracking_spec.md and append tracking/build decisions to 00_decision_log.md.
Before specifying build, do the required collaboration mechanics:
- Quote 3 key decisions from Agents 1–4 that affect build/tracking.
- Challenge 2 assumptions about tracking/measurement and resolve them.
- Provide 1 alternative tracking stack option (label “Alternative Option”), then proceed with the chosen approach.
Deliverables for 05_build_and_tracking_spec.md (implementation-ready, stack-agnostic):
1. Build Plan
- Page components list (matching Agent 4 components)
- Asset checklist (what needs to be provided, what can be placeholder)
- Responsive behavior notes
2. Forms + Routing
- Recommended form fields (exact list)
- Submission routing: email + CRM spreadsheet option
- Thank-you page vs inline confirmation (choose one and justify)
- Spam prevention approach
3. Tracking Plan (Meta-first)
- Events to implement: PageView, ViewContent (if used), Lead, CompleteRegistration (if used), Schedule (if applicable)
- Event firing rules (when exactly they trigger)
- UTM capture rules + storing UTMs with lead
- Meta Pixel + Conversions API note (explain requirements, even if not implemented)
- GA4 events mapping (name each event)
4. QA Checklist (15 bullets)
- Cross-browser, mobile, form tests, event tests, broken links, speed basics
5. Measurement & Reporting
- Define primary KPI, secondary KPIs, and weekly reporting snapshot fields
6. Launch Steps
- Step-by-step order of operations for go-live
Append to Decision Log:
- Tracking events, thank-you approach, and KPI definitions.
Handoff Notes:
- Assumptions (5+)
- Unknowns (5+)
- 5 questions for synthesis
FINAL SYNTHESIS / REVIEW STEP (must be done after Agent 5)
Create outputs/agent_teams_demo/revshare-meta-ads-landing/06_final_review_and_launch_checklist.md.
Deliverables for 06_final_review_and_launch_checklist.md (600–900 words, structured exactly):
1. One-Page Summary
- ICP, promise, offer, CTA, proof strategy (bullet list)
2. Consistency Review
- Identify any mismatches across positioning/copy/proof/design/tracking and resolve them (at least 5 items).
3. Risk & Compliance Review
- 10-point checklist applied to the actual copy/proof approach; list any red flags and fixes.
4. Pre-Launch Checklist
- 20 checkbox items grouped under: Content, Design, Technical, Tracking, Legal/Privacy.
5. Post-Launch Experiment Plan
- 5 experiments for the first 14 days (what to change, hypothesis, success metric).
6. Final Decision Log Audit
- List the 8 most important decisions and where they appear in the files.
SYNTHESIS COLLABORATION REQUIREMENTS
- Cross-reference exact section names from 02_landing_page_copy.md and component names from 04_wireframe_and_ui_spec.md.
- If any decision changed midstream, ensure 00_decision_log.md reflects the final state with a final entry: “FINAL—Approved for Launch” and the date.
EXECUTION ORDER (do not deviate)
1) Agent 1 -> writes 01_positioning_brief.md and starts 00_decision_log.md
2) Agent 2 -> writes 02_landing_page_copy.md and updates 00_decision_log.md
3) Agent 3 -> writes 03_social_proof_pack.md and updates 00_decision_log.md
4) Agent 4 -> writes 04_wireframe_and_ui_spec.md and updates 00_decision_log.md
5) Agent 5 -> writes 05_build_and_tracking_spec.md and updates 00_decision_log.md
6) Synthesis -> writes 06_final_review_and_launch_checklist.md and finalizes 00_decision_log.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.