Skip to content
FlowForge Logo FlowForge

FFT-Paid-Media-Architect - Paid Media Strategy

Overview

Section titled “Overview”

FFT-Paid-Media-Architect is the strategy head of FlowForge’s paid-media pair — the tráfego pago discipline. It designs the campaign end to end — audience research, positioning, offer, funnel, channel mix, campaign and creative architecture, budgets and bidding, and the measurement plan with named success metrics and kill/scale thresholds — and hands fft-media-buyer a campaign brief to build and operate inside the actual ad consoles. It never touches the consoles itself; the buyer leaf does, and escalates when performance data contradicts the brief.

Capabilities

Section titled “Capabilities”
  • Market + audience research: ICP definition, jobs-to-be-done, awareness-stage mapping (Schwartz’s five stages), qualitative mining of reviews and sales calls as creative raw material
  • Positioning + offer design: Dunford-style positioning, offer architecture with honest risk reversal and urgency, lead-magnet→core-offer ladders
  • Funnel design: TOFU/MOFU/BOFU roles, cold-traffic funnels (landing page, VSL, webinar, trial, demo-call), message-to-page congruence, CRO fundamentals
  • Channel mix: Meta (creative-led discovery) vs Google Search (intent capture) vs YouTube and Demand Gen — with prospecting/retargeting budget splits
  • Campaign architecture: Meta CBO/ABO and Advantage+ decisions, broad-vs-interest-vs-lookalike in the post-ATT era; Google Search structure (brand/non-brand, match types, negatives), PMax guardrails
  • Creative direction: hook-first short-form, UGC vs polished mix, angle matrices, creative-testing velocity, fatigue math and refresh cadence
  • Budget + bidding: learning-phase mechanics, lowest-cost vs cost-cap vs bid-cap, tCPA/tROAS, vertical and horizontal scaling rules, minimum viable test budgets
  • Measurement plan: CPM/CPC/CTR/hook-rate/CVR/CPA/ROAS vs blended MER, attribution windows, CAPI + pixel redundancy, UTM discipline, incrementality thinking — and why platform-reported ROAS overstates

When to Use

Section titled “When to Use”
  • Routing rule: campaign strategy, funnel, offer, channel-mix, or measurement questions → dispatch fft-paid-media-architect FIRST; it authors the campaign brief fft-media-buyer operates
  • Planning a paid-acquisition program from scratch for a product launch
  • Auditing a funnel where traffic converts poorly (offer/page/message diagnosis before spend)
  • Designing the measurement plan and kill/scale thresholds before any budget is committed

Do NOT dispatch for console work — account setup, campaign build, launch QA, and optimisation belong to fft-media-buyer, against this agent’s brief.

Example Prompts

Section titled “Example Prompts”
"Design the paid-acquisition program for this developer tool: ICP and awareness-stage map, offer and funnel per stage, Meta vs Google/YouTube split, campaign architecture, test budget, and a measurement plan with kill/scale thresholds."
"Platform ROAS says 4.2 but revenue is flat. Audit the measurement plan — attribution windows, double counting, blended MER — and rewrite it so the numbers we act on are business truth."