Channels & Execution
Events compress months of pipeline work into a few days — when the lifecycle is run right. 5-phase lifecycle, AARRR funnel, squad cadence, SLAs, and the Event Pipeline Agent.
The framework — strategy first
Events compress months of pipeline acceleration and customer loyalty work into a few days — when the lifecycle is run right. They're also the single largest line item on most marketing budgets. The discipline below is what separates an event that returns 10× its cost in pipeline from one that returns a stack of badges and a credit-card statement.
Not every event does the same work. Pick the type before you pick the budget.
EVENT TYPES
Hosted — Customer Summits, Product Showcases. Thought leadership + customer marketing. You own the room.
Sponsored — Industry conferences (NRF, ATD, Shoptalk). Pipeline + brand awareness. You rent presence in someone else's room.
Attended-only — Niche vertical events, executive forums. Account development + competitive intel. You go to listen, not to be seen.
Meetings / matchmaking — Groceryshop-style programs. Pre-booked qualified meetings, no booth required. You buy the meetings, not the floor.
Every event runs the same five phases. The mistake most teams make is jumping into Phase 2 (campaign creation) before Phase 1 (strategy) is signed off, which is why most events under-perform their budget.
EVENT LIFECYCLE
Phase 1 — Strategic Planning (T-12 to T-6 months). Target event list, allocate budget, set objectives, build the business case (forecast pipeline, brand lift, Customer Acquisition Cost — CAC).
Phase 2 — Tactical Execution (T-6 to T-1 week). Design booth and creative, build campaigns, book meetings, prep the field team.
Phase 3 — Event Activation (event week). Execute with excellence, capture leads, log meetings in real time.
Phase 4 — Follow-up & Handover (T+1 to T+4 weeks). Hot leads to AEs within 24 hours, opportunities created within 3 business days, post-mortem within 10 days.
Phase 5 — Post-event Marketing (T+6 months). Repurpose assets, retarget leads, continue the conversation. Most teams skip this and lose 50%+ of potential pipeline.
Map every event to the AARRR (Pirate Metrics) framework so the funnel stage and the owner are explicit. Without this, marketing claims attribution and sales claims pipeline, and nobody owns the gap in between.
THE EVENT AARRR MAP
Acquisition — Leads captured (booth scans, RSVPs, landing-page submissions). Owner: Marketing.
Activation — Meetings held + qualified conversations. Owner: Sales.
Retention — Customer Net Promoter Score (NPS) from event + post-event Customer Success (CS) touchpoints. Owner: Customer Success.
Referral — Advocacy opt-ins, testimonials captured, video quotes. Owner: CS + Marketing.
Revenue — Pipeline generated, deals created, $ closed (target: 10× event cost). Owner: Sales + RevOps.
Revenue-Centric — Every function ties activity back to pipeline or retention impact. No exceptions.
Experience-Led — Don't "show up"; stand out. The booth is the brand.
Ownership at Every Touchpoint — Pre-committed targets per Account Executive (AE) — 5 meetings minimum — plus the Business Development Rep (BDR), Demand Gen, and the Customer Success Manager (CSM).
Data First — All leads tagged, scored, and routed within 48 hours. No more "the spreadsheet got lost."
Debrief Culture — Every event closes with a retro: what worked, what didn't, what's next.
Nurture-Forward — Post-event nurture continues for 6 months. The leads are the asset; the event is the moment.
The teams that get 10× return run an event squad: a cross-functional working group with five scheduled touchpoints leading up to the event. Marketing leads the squad. Each meeting has a defined output.
THE SQUAD CADENCE
Meeting 1 — T-12 weeks: Master plan. Time/date/location, who's attending, list acquisition strategy, sponsorship and booth requirements.
Meeting 2 — T-6 weeks: Logistics + targets. Pre-event meetings booked, sales cadence in flight, AE/BDR coverage assigned. Each AE commits to 5 minimum.
Meeting 3 — T-3 weeks: List flow. Attendee list received from organizer, cleaned, deduped, matched to the Customer Relationship Management system (CRM). Sales Development Rep (SDR) outreach moves to high gear.
Meeting 4 — T-1 week: Final readiness. Booth assets confirmed, talk tracks reviewed by Enablement, calendar invites sent, mobile numbers exchanged.
Meeting 5 — T+1 week: Debrief. Lead totals, meetings held, pipeline created, what worked, what didn't, what's repeatable.
Lead routing SLAs — the difference between an event that converts and one that doesn't
Most events fail in the 48 hours after the booth closes, not at the booth. The SLAs below are the hard rules — every team commits to them in writing before the event, and RevOps publishes adherence in the debrief.
POST-EVENT SLAS
Net new leads uploaded to CRM within 48 hours (owner: Revenue Operations — RevOps).
Hot leads (booked meetings + scanned booth visits with intent) → AE within 24 hours (owner: AE/BDR).
Opportunities created in CRM for Sales Qualified Leads (SQLs) within 3 business days (owner: AE).
Post-event marketing email to all attendees within 2 business days (owner: Marketing).
Customer follow-up with recap + next steps within 2 business days (owner: CSM).
Pipeline + Return on Marketing Investment (ROMI) report shared with leadership within 7 business days (owner: RevOps).
Marketing is responsible for getting the team there. Sales is responsible for bringing the business home. Both fail if Phase 1 is skipped.
Events compress months of pipeline acceleration and customer loyalty work into a few days — when the lifecycle below is run right. This work is the cross-functional playbook for every event [COMPANY NAME] participates in or hosts.
Strategic Objectives for Events
Pipeline generation through high-touch prospect engagements
Customer loyalty through relationship-building and recognition
Thought leadership positioning via speaking and panel opportunities
Multi-threading across buying committees in target accounts
Brand awareness among Ideal Customer Profile (ICP) audiences in concentrated venues
Event Taxonomy
| TYPE | PRIMARY OBJECTIVE | EXAMPLES |
|---|---|---|
| [COMPANY]-Hosted | Thought leadership, customer marketing | Customer Summit, Product Showcase, Executive Roundtable |
| Sponsored / Conference | Pipeline and brand awareness | [Relevant conferences in your space] |
| Attended Only | Account development, competitive intel | Niche vertical or executive forums |
| Virtual / Webinar | Scalable demand generation | Hosted webinars, virtual summits, co-hosted partner events |
| CRITERION | QUESTIONS TO ANSWER |
|---|---|
| ICP Alignment | What % of attendees match our ICP? What is the typical attendee title and company size? |
| Historical ROI | Have we attended before? What was the pipeline generated vs. cost? |
| Competitive Presence | Are our key competitors presenting or sponsoring? What's the risk of not attending? |
| Meeting Potential | Can we pre-book meetings? Does the event facilitate matchmaking? |
| Speaking Opportunity | Can we secure a speaking slot, panel seat, or customer co-presentation? |
| Cost | What is the all-in cost (booth, sponsorship, travel, swag, content)? |
The five phases above are the model. The tactical detail below is what runs inside each phase. Same lifecycle, full execution layer.
Phase 1 — Strategic Planning (T-12 to T-6 months).
Phase 2 — Tactical Execution (T-6 to T-1 week).
Phase 3 — Event Activation (event week).
Phase 4 — Follow-up & Handover (T+1 to T+4 weeks).
Phase 5 — Post-event Marketing (T+1 to T+6 months). The phase most teams skip — and the one that recovers 50%+ of the latent pipeline.
| PHASE | BDR ACTIVITIES | GOAL |
|---|---|---|
| Pre-Event (T-6 to T-1 week) | Build Gong/Outreach sequences for ICP attendees; pre-book 10–15 meetings per BDR | Arrive with a full meeting calendar |
| At-Event | Greet scheduled meetings; triage walk-ups; maintain live lead tracking in CRM | Maximize meeting count, qualify quickly |
| Post-Event (T+1 to T+2 weeks) | Hot hand-off to AE; Warm leads in nurture sequence; Cold to marketing nurture | Convert meetings to pipeline |
Events are the largest single line item in most B2B SaaS marketing budgets, and the least defensible if you can't show the math. The discipline that protects the line item: every event generates 10× its total cost in pipeline within 6 months, or it doesn't run again. No exceptions, no "but it's good for brand," no "the CEO loves it." Brand value is real but it's not the budget conversation. The 10× rule is the budget conversation.
Total cost (the denominator)
The pipeline number (the numerator) is marketing-sourced + marketing-influenced pipeline that touches the event in the trailing 6 months. Both flavors count — sourced because the event was first-touch; influenced because the deal velocity moved after the event. RevOps tags every opportunity at deal creation with an event-touched flag based on attendee list match.
| TIER | TYPE | INVESTMENT | 10× PIPELINE TARGET | EXAMPLE |
|---|---|---|---|---|
| Tier 1 | Owned flagship | $250K–$1M | $2.5M–$10M | Annual customer + prospect summit (1× per year) |
| Tier 2 | Major industry sponsorship | $50K–$250K | $500K–$2.5M | Category-defining event sponsorship + booth + speaking slot (2–4× per year) |
| Tier 3 | Targeted dinners / roundtables | $15K–$50K each | $150K–$500K each | Executive dinner in target city + 8–12 named accounts (8–12× per year) |
| Tier 4 | Webinars / virtual events | $5K–$20K each | $50K–$200K each | Quarterly thought-leadership webinar with industry partner (4–8× per year) |
The pattern at scale: 60–70% of event budget goes to Tier 1 + Tier 2 (the big-ROI bets), 20–30% goes to Tier 3 (the relationship-builders with named-account ROI), and the rest goes to Tier 4 (the always-on pipeline contributor). Anything that doesn't fit into one of these tiers usually doesn't pass the 10× test.
The events you actually run + the pipeline they need to produce. Every event prompt on the site uses these.
Saved as [ANNUAL EVENT BUDGET], [TIER 1 EVENT], [TIER 2 EVENTS], [TIER 3 EVENTS], [TIER 4 EVENTS].
| CATEGORY | KPI | TARGET |
|---|---|---|
| Reach | Landing page visits, social impressions, email open rate | Set per event based on audience size |
| Engagement | Meeting bookings, badge scans, demo requests, content downloads | Set per event |
| Pipeline | MQLs generated, SQLs created, pipeline value | 10× event total cost |
| Revenue | Closed revenue influenced by event (trailing 6 months) | Track and report quarterly |
The prompt pack
Each prompt is a named, named-by-what-it-does deliverable. Click any card to expand the paste-able body. Run against your Operator Brief.
Five copy-paste prompts. Open ChatGPT, Claude, or Gemini. Paste a prompt. Run it. The output of one prompt feeds into the next.
READ THIS ONCE BEFORE ANY PROMPT IN THIS BOOK
These prompts assume you've populated your Operator Brief (the worksheet that lives in /Operator-Brief-Worksheet.docx). When a prompt asks for OPERATOR BRIEF, paste the relevant Brief sections rather than typing context from scratch.
Your output then arrives in your voice, against your buyers, using your differentiators. Not [BRACKETED] generics. The Brief is the difference between an LLM helper and a tool that sounds like you.
Prompt 1
A scoring rubric for evaluating event opportunities (5 factors, weighted) plus a recommended event mix (3 tiers).
Prompt 2
A 12-week squad cadence with 5 meetings, role assignments, and a one-page SLA covering all five functions (Marketing, Sales, BDR, CSM, RevOps).
Prompt 3
A 3-touch pre-event outreach sequence for booking meetings on-site, calibrated to attendee profile.
Prompt 4
A 5-touch post-event nurture sequence segmented by booth-stop / demo / meeting-attended, plus the conversion event each segment is being driven toward.
Prompt 5
A one-page debrief covering pipeline generated vs. target (10× cost), per-function SLA adherence, what worked, what didn't, and the three things to change next time.
The agent spec
How to install this agent
Channel-specific event operations — the per-event tracker that complements the canonical Field Marketing Agent. Owns the event-by-event pipeline math, the booth-scan-to-opportunity attribution, and the 10× ROI honesty check.
| Task | Frequency | Duration | Output goes to |
|---|---|---|---|
| Real-time event-day tracking | Continuous during event | Always-on | Field Marketing Agent + AE per-account |
| Event T+1 booth-scan reconciliation | Per event | ~2 hours | Field Marketing Agent + Sales Director |
| Event T+7 / T+30 / T+60 / T+90 ROI reports | Per event | ~60 min each | Head of Field + VP Marketing + CFO |
| Weekly active-portfolio digest | Weekly Fri 11:00 | ~30 min | Head of Field + VP Marketing |
| Monthly hygiene audit | Monthly 1st | ~60 min | Head of Field + Director RevOps |
| Quarterly portfolio ROI review | Quarterly Q-1 days | ~3 hours | Head of Field + VP Marketing + CFO + CRO |
Scheduled (cron-style):
| Schedule | What it runs |
|---|---|
0 11 * * 5 | Weekly active-portfolio digest |
0 9 1 * * | Monthly hygiene audit |
0 9 5 1,4,7,10 * | Quarterly portfolio ROI review |
Event-driven:
| Event | What it runs |
|---|---|
| Event end-time + 24 hours | Trigger T+1 booth-scan reconciliation |
| Event T+7 / T+30 / T+60 / T+90 milestones | Generate ROI snapshot report |
| Tracked event-attendee becomes closed-won opportunity | Route event-touch metadata to Revenue Attribution Engine |
| T+90 ROI < 2× spend on a tier-1 event | Page Head of Field + VP Marketing + CFO |
| Booth-scan-to-CRM match rate < 80% on an event | Page Director RevOps for data hygiene review |
| Source | Type | Cadence | Required? |
|---|---|---|---|
| Operator Brief (Sections 1, 2) | Markdown | Read on quarterly review | Required |
| Field Marketing Agent event readiness + schedule data | Markdown | Continuous | Required |
| Event platform scan + registration + session data | API | Real-time during + post-event | Required |
| CRM contact + account + opportunity data | API | Real-time | Required |
| Per-event spend ledger (invoices + POs) | Spreadsheet / Postgres | Per-event | Required |
| Revenue Attribution Engine per-segment + per-channel data | JSON | Weekly | Required |
| Account Intel Hub records | JSON | Live query | Required for tier classification |
| Output | Format | Target path | Audience |
|---|---|---|---|
| Per-event pipeline tracker | Markdown + Postgres view | /events/<event>/pipeline-tracker.md | Field Marketing Agent + AEs + Sales Director |
| Per-event ROI snapshot reports (T+7/30/60/90) | Markdown + chart | /events/<event>/roi-T+<n>.md | Head of Field + VP Marketing + CFO |
| Weekly active-portfolio digest | Markdown + Slack message | /events/portfolio/active-YYYY-WW.md | Head of Field + VP Marketing |
| Monthly hygiene audit | Markdown | /events/hygiene/YYYY-MM.md | Head of Field + Director RevOps |
| Quarterly portfolio ROI review | Markdown + chart bundle | /events/portfolio-roi/Q<n>.md | Head of Field + VP Marketing + CFO + CRO |
| Event-touch metadata to Revenue Attribution Engine | JSON feed | /attribution/event-touches.jsonl | Revenue Attribution Engine |
| Trigger condition | Escalate to | Within |
|---|---|---|
| T+90 ROI < 2× on a tier-1 event | Head of Field + VP Marketing + CFO | Same week (sunk-cost surfacing) |
| Booth-scan match rate < 80% on an event | Director RevOps + Head of Field | Same week |
| Pipeline trace gap to CRM ground truth > 10% | Director MarOps + Head of Field | < 7 days |
| Quarterly portfolio average ROI < 3× | VP Marketing + CFO + Head of Field | Same quarter |
| ROI snapshot missed milestone deadline (T+7/30/60/90) | Head of Field | Immediate |
| Platform / tool | Used for | Required? |
|---|---|---|
| Replit + Postgres (per-event pipeline records) | State + audit | Required |
| Event platform API (Bizzabo / Hopin / Cvent / Splash) | Scan + registration + session data | Required |
| Salesforce / HubSpot API | CRM contact + opportunity matching | Required |
| Spreadsheet (Google Sheets / Excel) for spend ledger | Per-event spend reconciliation | Required |
| Revenue Attribution Engine API | Multi-touch model integration | Required |
| Slack API | Weekly digest + ROI escalations | Required |
| Looker / Mode / Tableau | Portfolio ROI visualization | Optional but recommended |
Evals — output quality checks:
Hallucination defense — specific checkpoints:
First-run checklist — 5 steps from spec to running agent: