Campaign Brief: Agency Intelligence — Tech Ops Adoption Outreach
Service line: Agency Intelligence — AI Knowledge Infrastructure
Gate date: 2026-03-17 (2 weeks from first send)
Brief owner: Luke Scorziell
Last updated: 2026-02-25
Use this brief to run the campaign and to score it against the Campaign Launch Checklist at the gate. Keep the checklist section updated so go/no-go is obvious.
1. Launch checklist progress (gate at 2 weeks)
Beta Test (must all be ✅ to advance)
- Enriched Tier 1 list built (link: _________)
- 3 SOWs created and sent
- 1 signed contract secured
- Delivery started
- 1 milestone reached
Market Ready (commit when we go)
- Service posted on website
- Lead gen underway (this campaign)
- Supporting content calendar in execution (see Content below)
- Partners updated
- 5 customers attracted to a meeting
SOW & meeting tracking
| # | Company / contact | SOW sent | Signed | Meeting booked | Notes |
|---|---|---|---|---|---|
| 1 | |||||
| 2 | |||||
| 3 | |||||
| 4 | |||||
| 5 |
Target: 3 SOWs sent, 1 signed, 5 total prospects to a meeting.
2. Positioning & hypothesis
Value Proposition: “Best in the world at solving AI adoption failure for agency technology leaders using custom-built knowledge infrastructure that maps to how teams already work — not on top of existing systems.”
Problem: Agency AI implementations fail at adoption. Tools get bought, teams get trained, and 60–90 days later most people are back to their old workflows. The AI investment never sticks — not because of the tool, but because it wasn’t built around how the team actually works.
Customer (title / segment): Director of Technology Operations, VP of Technology, Head of Technology, or equivalent at creative/integrated ad agencies — US, 50–500 employees, with at least one dedicated tech or operations leader. Profile: Josh Dent (Executive Director of Technology Operations, David & Goliath).
Solution (service name / approach): Agency Intelligence — custom AI knowledge infrastructure including knowledge bases, AI-powered workflows, and MCP-connected tools, built around how the team works across client accounts. Output: teams that actually use the tools, not just have access to them.
One-line test hypothesis: “Agency tech ops leaders at mid-sized creative agencies will book a discovery call when shown that AI adoption failure is a solvable build problem — not a people problem — backed by a 100% adoption case study.”
One-pager / narrative: (link TBD — StackBlitz one-pager to be added to vault)
Pricing: (link to pricing guide — TBD per scope)
3. Campaign overview
What we’re testing: Cold email outreach to tech ops leaders at mid-sized creative and integrated ad agencies — leading with an adoption stat (100% adoption, 80% reduction in manual reporting, 3x more decisions/week) to validate demand for the Agency Intelligence service line. Success = 2+ discovery calls booked, 1 MQL advanced within 2 weeks of first send.
Target audience:
- Creative/integrated/brand agencies — NOT pure media buying or performance marketing
- 50–500 employees, US
- Has a dedicated technology or operations leader (Director, VP, or Head of Technology)
- Signal: agency is investing in or evaluating AI tooling; has multiple internal teams working across client accounts in silos
Strategy: Email-first, quality over volume. Max 30 Tier 1 contacts for the test. Tone is peer-to-peer and curious — Luke as sender, not a coordinator alias. Sequence is 3 touches over 11 days. Email 1 leads with the adoption result and offers a white paper. Email 2 follows up with pain-specific framing and a call ask. Email 3 closes the loop with a resource offer.
Dependency: Email 3 references a white paper (“Why Agency AI Implementations Fail”). This must be ready before the first send. See §4.
4. Execution: Outreach & leadgen
Execution stack
| Layer | Tool | Role |
|---|---|---|
| Enrichment | Clay | Account + contact data (company, headcount, revenue, LinkedIn URL, work email). Ryan builds. |
| Manual / HeyReach | Not the primary channel for this campaign. Optional warm connection alongside email. | |
| Instantly | Primary channel. 3-email sequence. Luke as sender. |
List-building criteria (Ryan to build in Clay)
Cap at 30 Tier 1 contacts for the test.
Required filters:
- Industry: Creative, integrated, or brand advertising agencies (NOT media buying, NOT performance-only shops)
- Headcount: 50–500 employees
- Geography: US
- Has a visible technology or operations leader on LinkedIn (Director, VP, or Head of Technology / IT / Operations)
Titles to target (LinkedIn Sales Navigator):
- Director of Technology Operations
- VP of Technology
- Head of Technology / Head of IT
- Director of Operations (at agencies, where tech falls under ops)
- Chief of Staff (at agencies without a dedicated tech director, where this person owns tool decisions)
Exclude:
- Media buying or pure performance agencies
- Holding company mega-agencies (WPP, Publicis, IPG — enterprise procurement blocks outreach)
- Freelance/boutique shops under 20 people (no tech ops role exists)
- Agencies already in pipeline or as active clients
Target account list
(Ryan to populate after Clay build. Max 30 Tier 1 accounts.)
| # | Company | Category | Headcount | Annual Revenue | Source | Prospect identified |
|---|---|---|---|---|---|---|
| 1 | LinkedIn Sales Nav | |||||
| 2 | LinkedIn Sales Nav | |||||
| 3 | LinkedIn Sales Nav |
ICP titles
- Director of Technology Operations
- VP of Technology
- Head of Technology / Head of IT
- Director of Operations (tech scope)
- Chief of Staff (small-to-mid agencies)
Order of operations & rules
- Ryan builds list in Clay (criteria above) — complete by Feb 28
- Luke reviews and approves list before upload
- Rico loads approved list into Instantly and builds sequence
- Luke reviews sequence in Instantly before launch — approve before first send
- First send: March 3 (contingent on white paper being ready)
- All replies route to Luke within 24h — Rico flags, Luke responds
Sequence definition (Instantly)
| Step | Channel | Action | Template | Delay |
|---|---|---|---|---|
| 1 | Send Email 1 | Adoption stat + playbook offer | Day 0 | |
| 2 | Send Email 2 | Follow-up + call ask | Day 4 | |
| 3 | Send Email 3 | Breakup + resource | Day 11 |
Message layer
Email 1 — Cold (Day 0)
Subject: AI adoption at [Agency Name]
Hi [First Name],
Saw you’re in [X role] at [Y]. Curious if your team has struggled to adopt new AI initiatives? We recently helped a client (StackBlitz) achieve 100% adoption across their GTM and leadership team. They’ve sped up reporting to seconds, not hours.
We’ve been doing the same thing with agencies. I’d love to hear how you’re implementing AI.
Would you be open to a 20-minute call next week?
Best, Luke Scorziell GTM Lead
Email 2 — Follow-up (Day 4) Send as reply in same thread.
Wanted to bump this up in your inbox. We’ve been building custom solutions for agency clients that speed up brief times, connect disparate SaaS to Copilot, and more.
Would love to jump on a quick 20-minute call to learn how you’re thinking about AI! Would you have time this week or next?
Best, Luke Scorziell
Email 3 — Breakup (Day 11) Send as reply in same thread.
Just checking in one last time. Attaching our white paper that speaks to how our agency clients have been empowered to use tech to lead in their roles.
Happy to connect if you’re ever interested!
(Attach: Why Agency AI Implementations Fail — white paper)
Dependencies before launch
⚠️ White paper required before first send. Email 3 references a white paper. Ryan + Luke to produce before March 3. Working title: “Why Agency AI Implementations Fail: An Adoption Playbook for Tech Ops Leaders” Content: StackBlitz stats (100% adoption, 80% manual reporting reduction, 3x decisions/week) reframed through an agency lens. 1–2 pages max. Owner: Ryan (draft) → Luke (review + approve) Due: Feb 28
⚠️ StackBlitz one-pager to be added to vault. Path:
/knowledge../marketing-assets/case-studies/stackblitz-case-study.mdCan be named in Email 2 as an optional credibility layer once available.
Outreach checklist (per prospect)
- ICP fit confirmed (title, agency type, headcount)
- Enriched (name, work email, company confirmed via Clay)
- Loaded into Instantly
- Email 1 sent
- Email 2 sent (Day 4)
- Email 3 sent (Day 11)
- Outcome logged (reply / no reply / booked)
- Reply flagged to Luke within 24h
5. Execution: Content
Goal: Supporting post to warm up the ICP and provide credibility when prospects research Brainforge after receiving the email. Not the primary lead gen channel for this campaign.
Planned supporting post: Agency Intelligence / AI adoption thought leadership post (Luke’s LinkedIn — W08/W09). This post should be live before or during the email sequence so inbound traffic reinforces the outreach.
Content lives in: (link to Notion content queue when created)
| # | Pillar | Topic / hook | Notion / link |
|---|---|---|---|
| 1 | Thought leadership | Why AI adoption fails at agencies — and what we did differently | TBD |
| 2 | Service proof | StackBlitz: 100% adoption, 3x decisions/week | TBD (post once one-pager is ready) |
6. Roles & owners
| Action | Owner |
|---|---|
| Brief owner / gate decision | Luke Scorziell |
| List build + Clay enrichment | Ryan |
| Tier 1 list approval | Luke Scorziell |
| Sequence build in Instantly | Rico |
| Sequence approval before send | Luke Scorziell |
| Sender account | Luke Scorziell |
| Reply flag (within 24h) | Rico |
| All reply conversations | Luke Scorziell |
| White paper (draft) | Ryan |
| White paper (review + approve) | Luke Scorziell |
| Content publish (LinkedIn) | Luke Scorziell |
7. Gate decision (fill at gate date)
Gate date: 2026-03-17
- Go — Beta criteria met; proceeding to full rollout (website, leadgen, content, partners, 5 to meeting).
- Conditional go — Beta met; Market Ready actions committed with follow-up date.
- No-go — Beta not met; iterate or pause. Next test date: _______________
Notes: