CoreCMO

Channels & Execution


Events

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.

Channels & Execution 5 prompts 1 agent — Event Pipeline Agent ~5 min preview

The framework — strategy first


Events — the strategic foundation.

Events Are Revenue Moments, Not Content Moments.

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.

Four event types, four jobs

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.

The five lifecycle phases

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.

AARRR — the funnel map for events

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.

Six operating principles

  • 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 event squad — five meetings, one shared scoreboard

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.

STRATEGY & PROCESS

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.

Event Strategy

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

TYPEPRIMARY OBJECTIVEEXAMPLES
[COMPANY]-HostedThought leadership, customer marketingCustomer Summit, Product Showcase, Executive Roundtable
Sponsored / ConferencePipeline and brand awareness[Relevant conferences in your space]
Attended OnlyAccount development, competitive intelNiche vertical or executive forums
Virtual / WebinarScalable demand generationHosted webinars, virtual summits, co-hosted partner events

Event Selection Criteria

CRITERIONQUESTIONS TO ANSWER
ICP AlignmentWhat % of attendees match our ICP? What is the typical attendee title and company size?
Historical ROIHave we attended before? What was the pipeline generated vs. cost?
Competitive PresenceAre our key competitors presenting or sponsoring? What's the risk of not attending?
Meeting PotentialCan we pre-book meetings? Does the event facilitate matchmaking?
Speaking OpportunityCan we secure a speaking slot, panel seat, or customer co-presentation?
CostWhat is the all-in cost (booth, sponsorship, travel, swag, content)?

Event Lifecycle — the five phases, the tactical detail

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).

  • Build an annual event calendar aligned to product launch timing, vertical GTM strategies, and ABM account lists.
  • Secure sponsorships, booth space, and speaking opportunities early — best spots go quickly.
  • Build the business case: forecast pipeline potential, brand lift, and estimated CAC from the event.
  • Assign a cross-functional event squad: Marketing lead, BDR lead, Sales lead, and optional CS lead.

Phase 2 — Tactical Execution (T-6 to T-1 week).

  • Launch a multichannel demand gen campaign: email sequences, LinkedIn paid, retargeting, organic social.
  • Build a targeted email sequence to past attendees and ICP accounts with a meeting booking CTA.
  • Create a dedicated event landing page: book a meeting, session details, demo CTA.
  • Enable the field team: event-specific email signatures, LinkedIn tiles, one-pagers, talking points.
  • Distribute prospect lists tagged in the CRM with calendar invite links and assigned BDR or AE sequences.

Phase 3 — Event Activation (event week).

  • Live social coverage (LinkedIn, X/Twitter, Instagram): highlights, speaker clips, customer quotes.
  • Gamified booth interactions: giveaways for badge scans, product demos, or trivia competitions.
  • In-booth content capture: short video testimonials from customers and prospects.
  • On-the-spot meeting booking: QR code or Calendly link displayed prominently at the booth.
  • Daily lead triage: sort leads into Hot / Warm / Cold each evening. Route immediately as needed.

Phase 4 — Follow-up & Handover (T+1 to T+4 weeks).

  • Upload all leads to CRM within 48 hours, tagged by lead quality and source.
  • Hot leads (Sales Qualified Lead — SQL — ready): route to AE with event notes for same-day or next-day follow-up.
  • Warm leads (Marketing Qualified Lead — MQL): enroll in event-specific nurture sequence with behavior-triggered content.
  • Cold / Non-ICP: route to long-term nurture or suppress if clearly not a fit.
  • Publish event recap (blog or video) within 1 week.
  • Launch retargeting to re-engage event leads across LinkedIn and Google.

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.

  • Repurpose the captured assets: speaker clips into LinkedIn cut-downs, customer quotes into proof tiles, panel transcripts into thought-leadership posts. The event content earns its second life here.
  • Run a 6-month retargeting wave against the attendee list — LinkedIn + Google — with sequenced creative that progresses from recap to use-case to demo CTA.
  • Re-enroll the warm tier into vertical-specific lifecycle as new ICP-relevant content ships. The booth scan was the introduction; the next quarter is the relationship.
  • Brief Customer Success on the customers who attended — capture renewal signal, surface expansion plays, line up case-study candidates.
  • Reconcile pipeline-touched-by-event at T+3 and T+6 months. The 10× ROI math closes here, not at the post-event debrief.

BDR Event Playbook

PHASEBDR ACTIVITIESGOAL
Pre-Event (T-6 to T-1 week)Build Gong/Outreach sequences for ICP attendees; pre-book 10–15 meetings per BDRArrive with a full meeting calendar
At-EventGreet scheduled meetings; triage walk-ups; maintain live lead tracking in CRMMaximize 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 nurtureConvert meetings to pipeline

The 10× rule — the only event ROI math that survives a CFO review.

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)

  • Sponsorship + booth + production fees
  • Travel + lodging for attending team (loaded cost)
  • Pre-event marketing spend (paid promotion of attendance)
  • Post-event nurture cost (email tools + content creation)
  • BDR loaded cost for pre-event meeting booking
  • Internal headcount time at fully-loaded cost

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.

The event-tier framework — invest where the unit economics work

TIERTYPEINVESTMENT10× PIPELINE TARGETEXAMPLE
Tier 1Owned flagship$250K–$1M$2.5M–$10MAnnual customer + prospect summit (1× per year)
Tier 2Major industry sponsorship$50K–$250K$500K–$2.5MCategory-defining event sponsorship + booth + speaking slot (2–4× per year)
Tier 3Targeted dinners / roundtables$15K–$50K each$150K–$500K eachExecutive dinner in target city + 8–12 named accounts (8–12× per year)
Tier 4Webinars / virtual events$5K–$20K each$50K–$200K eachQuarterly 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.

Your Event Calendar & ROI

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].

Event KPIs

CATEGORYKPITARGET
ReachLanding page visits, social impressions, email open rateSet per event based on audience size
EngagementMeeting bookings, badge scans, demo requests, content downloadsSet per event
PipelineMQLs generated, SQLs created, pipeline value10× event total cost
RevenueClosed revenue influenced by event (trailing 6 months)Track and report quarterly

The prompt pack


Paste-ready prompts for Events.

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

Event-selection scorecard

A scoring rubric for evaluating event opportunities (5 factors, weighted) plus a recommended event mix (3 tiers).

Score these event opportunities for next year. EVENTS: [list 5–10 with cost, attendance, audience profile, type (hosted/sponsored/attended-only/matchmaking)] BUDGET: $[] GOAL: [pipeline / brand / customer-marketing / mixed] OPERATOR BRIEF — paste: ICP Section 1.1 Tier 1 verticals, Section 1.5 Economic Buyer Score each on (1–5): 1. Audience match (vs. ICP Section 1.1 verticals + Section 1.5 EB titles) 2. Pipeline potential (forecast: leads × meeting-to-SQL × historical conversion) 3. Brand authority (analyst presence, speaker slots, peer caliber) 4. Cost-efficiency (cost per qualified meeting vs. internal benchmark) 5. Optionality (custom dinner / panel / matchmaking add-ons) Output: weighted total → rank → recommended Tier 1 (must-attend), Tier 2 (opportunistic), Tier 3 (drop). End with the 1 to drop, the 1 to upgrade, and the gap the lineup has (e.g., "no event reaches the technical evaluator").

Prompt 2

Pre-event squad and SLA plan

A 12-week squad cadence with 5 meetings, role assignments, and a one-page SLA covering all five functions (Marketing, Sales, BDR, CSM, RevOps).

Build the cross-functional squad plan for the event below. EVENT: [] DATES: [] AE COUNT ATTENDING: [] TARGET PIPELINE: $[] (rule of thumb: 10× event cost) Output two artifacts: 1) Squad cadence — 5 meetings (T-12, T-6, T-3, T-1 week, T+1 week). Each meeting: date, attendees, agenda (3–5 bullets), required pre-reads, exit criterion (what's signed off before the meeting ends). 2) Cross-functional SLA — table by function (Marketing, Sales, BDR, CSM, RevOps) × phase (pre / at / post). Each cell names the deliverable, the owner, and the SLA timeframe. Include the hard-stop SLAs: hot lead to AE within 24 hr, opp in CRM within 3 business days, ROMI report within 7 business days. End with: the single SLA most likely to break + the mitigation.

Prompt 3

Pre-event outreach (3-touch sequence)

A 3-touch pre-event outreach sequence for booking meetings on-site, calibrated to attendee profile.

Write the pre-event outreach for a customer / prospect roster. EVENT: [] DATES: [] BOOTH/MEETING SLOT: [] INVITEE PERSONA: [from Operator Brief Sections 6.5–2.7] TARGET: 5 meetings/AE pre-booked 3 touches: (T-21) Save the date — value-led, no ask. Subject + body + CTA. (T-10) Personalized invite with calendar link, reference an in-person moment (dinner, panel, demo). Subject + body + CTA. (T-3) Last call — short, specific, mobile-readable. Subject + body + CTA. Each email: ≤120 words. End with the criterion for calling the outreach 'enough' (e.g., 5 confirmed meetings or 8 working business days, whichever comes first).

Prompt 4

Post-event nurture by segment

A 5-touch post-event nurture sequence segmented by booth-stop / demo / meeting-attended, plus the conversion event each segment is being driven toward.

Write the post-event nurture for 3 segments. EVENT: [] SEGMENTS: booth-stop / demo-given / meeting-attended OPERATOR BRIEF — paste positioning statement (Section 2.11) and EB success metric (Section 1.5) 5 emails over 21 days. Differentiate cadence per segment: - Booth-stop: lighter touch, content-led, soft CTA. - Demo-given: medium touch, references specific moment from the demo, explicit CTA to next call. - Meeting-attended: heavy touch, AE-personalized intro, calendar link in email 1, accelerate to opportunity in CRM. Subject + body + CTA per email × 3 segments. End with the conversion event each segment is being driven toward and the timing for handoff to long- term nurture if no conversion.

Prompt 5

Post-event debrief + ROMI report

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.

Generate the post-event debrief and ROMI report. EVENT: [] TOTAL COST (booth, travel, swag, sponsorship): $[] PIPELINE TARGET: $[] (rule of thumb: 10× cost) LEADS CAPTURED: [] MEETINGS HELD: [] SQLs CREATED: [] OPPs CREATED: $[] SLA ADHERENCE: [paste any from RevOps] Output: 1) ROMI snapshot — pipeline generated vs. target (with the math). 2) Funnel by AARRR — leads → meetings → SQLs → opps with conversion rates. 3) Per-function SLA report — Marketing, Sales, BDR, CSM, RevOps. Where SLAs held and where they slipped, with the named owner of the slip. 4) What worked (3 bullets), what didn't (3 bullets, with what we'd change). 5) Three changes for next time — specific, owned, with a date. Tone: operator-direct. Numbers over adjectives. Name names where SLAs slipped.

The agent spec


The agent for Events.

How to install this agent

Five steps from spec to running agent.

  1. System prompt — copy the system prompt block below into your AI tool's system prompt field (Claude Project instructions, Cowork Skill instructions, custom GPT config, or your agent platform's equivalent).
  2. Inputs — wire the inputs as the agent's reference files. The Operator Brief is always input #1; the other inputs vary by agent.
  3. Outputs — the output schema tells you what the agent produces. Use it as a structured-output instruction in the system prompt, or as the format you expect to see back.
  4. Evals — before publishing any output, score it against the eval criteria. Don't ship anything that doesn't pass.
  5. Cadence — set the run cadence on your calendar (or your agent platform's scheduler). Log every run in your wins log.

Event Pipeline 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.

Who is this agent
Identity card
NameEvent Pipeline Agent
RoleEvent-level pipeline + ROI tracking — the data layer beneath the Field Marketing Agent
OwnerHead of Field Marketing
Reports toVP Marketing + CFO
Versionv0.5 (supervised)
SurfaceReplit + Postgres (per-event pipeline records) + integration with event platform + CRM
Output target/events/<event>/pipeline-tracker.md + /events/portfolio-roi.md
Review cadencePer-event T+30 / T+60 / T+90 pipeline check-ins; quarterly portfolio ROI review
Mission
Run the event-by-event pipeline math the canonical Field Marketing Agent depends on. Track every booth scan, demo signup, and meeting-on-deck to the actual CRM opportunity it became. Maintain the 10× ROI honesty check — if an event didn’t produce pipeline worth 10× the all-in cost within 90 days, surface it. Be the agent that prevents event spend from becoming a sunk-cost fallacy.
Goals & KPIs the agent moves
Leading indicators — the agent controls these
Booth-scan-to-CRM-contact match rate (within 5 business days of event close)≥ 90%
Per-event ROI report shipped at T+30 / T+60 / T+90100% on schedule
Lagging indicators — downstream outcomes with review triggers
Per-event pipeline trace fidelity (attributed pipeline vs. CRM ground truth). Trigger: gap > 10% on 2 consecutive events pages the Director of Field Marketing for attribution + tagging review.Within ±5% gap
T+90 ROI: share of events meeting ≥ 3× all-in cost. Trigger: < 50% of events clearing 3× over a rolling 4-event window pages the VP Marketing for event-portfolio review (kill/keep call).≥ 60% of events clear 3×
What it does
Task list
  1. Event T+1 day Pull booth scan logs + demo signups + meeting notes from the event platform. Cross-reference against CRM contact records.
  2. Event T+1 day Create per-attendee pipeline records. Tag each with: persona, account-tier, was-already-in-pipeline (yes/no), trigger-event-during-event.
  3. Event T+7 day First ROI snapshot. Spend reconciled, scans-to-pipeline-meeting conversion, named-account engagement. Feed Field Marketing Agent’s T+7 retro.
  4. Event T+30 day T+30 ROI report. Pipeline created vs. event-attributed. Surface the deltas.
  5. Event T+60 day T+60 ROI report. Pipeline progressed-to-stage-2 vs. event-attributed.
  6. Event T+90 day T+90 ROI report. Pipeline-traced revenue + closed-won + the 10× ROI honesty check. If event didn’t hit the bar, flag for portfolio review.
  7. Daily during event window Real-time pipeline-touch tracking from event-platform engagement events (sessions attended, booth-scan, demo-request, meeting-booked).
  8. Weekly Active-event portfolio digest: every event in the T-30 to T+90 window with its current pipeline status.
  9. Monthly Booth-scan-to-CRM hygiene audit. Surface scans that never matched a CRM contact — data issue OR list buy-back opportunity.
  10. Quarterly Event portfolio ROI review. Per-tier ROI averages. Recommendations on next-quarter portfolio composition.
  11. Event When a tracked attendee becomes a closed-won opportunity, route the event-touch metadata to Revenue Attribution Engine for the multi-touch model.
Schedule grid
TaskFrequencyDurationOutput goes to
Real-time event-day trackingContinuous during eventAlways-onField Marketing Agent + AE per-account
Event T+1 booth-scan reconciliationPer event~2 hoursField Marketing Agent + Sales Director
Event T+7 / T+30 / T+60 / T+90 ROI reportsPer event~60 min eachHead of Field + VP Marketing + CFO
Weekly active-portfolio digestWeekly Fri 11:00~30 minHead of Field + VP Marketing
Monthly hygiene auditMonthly 1st~60 minHead of Field + Director RevOps
Quarterly portfolio ROI reviewQuarterly Q-1 days~3 hoursHead of Field + VP Marketing + CFO + CRO
Triggers

Scheduled (cron-style):

ScheduleWhat it runs
0 11 * * 5Weekly active-portfolio digest
0 9 1 * *Monthly hygiene audit
0 9 5 1,4,7,10 *Quarterly portfolio ROI review

Event-driven:

EventWhat it runs
Event end-time + 24 hoursTrigger T+1 booth-scan reconciliation
Event T+7 / T+30 / T+60 / T+90 milestonesGenerate ROI snapshot report
Tracked event-attendee becomes closed-won opportunityRoute event-touch metadata to Revenue Attribution Engine
T+90 ROI < 2× spend on a tier-1 eventPage Head of Field + VP Marketing + CFO
Booth-scan-to-CRM match rate < 80% on an eventPage Director RevOps for data hygiene review
Who it works with
Inputs
SourceTypeCadenceRequired?
Operator Brief (Sections 1, 2)MarkdownRead on quarterly reviewRequired
Field Marketing Agent event readiness + schedule dataMarkdownContinuousRequired
Event platform scan + registration + session dataAPIReal-time during + post-eventRequired
CRM contact + account + opportunity dataAPIReal-timeRequired
Per-event spend ledger (invoices + POs)Spreadsheet / PostgresPer-eventRequired
Revenue Attribution Engine per-segment + per-channel dataJSONWeeklyRequired
Account Intel Hub recordsJSONLive queryRequired for tier classification
Outputs
OutputFormatTarget pathAudience
Per-event pipeline trackerMarkdown + Postgres view/events/<event>/pipeline-tracker.mdField Marketing Agent + AEs + Sales Director
Per-event ROI snapshot reports (T+7/30/60/90)Markdown + chart/events/<event>/roi-T+<n>.mdHead of Field + VP Marketing + CFO
Weekly active-portfolio digestMarkdown + Slack message/events/portfolio/active-YYYY-WW.mdHead of Field + VP Marketing
Monthly hygiene auditMarkdown/events/hygiene/YYYY-MM.mdHead of Field + Director RevOps
Quarterly portfolio ROI reviewMarkdown + chart bundle/events/portfolio-roi/Q<n>.mdHead of Field + VP Marketing + CFO + CRO
Event-touch metadata to Revenue Attribution EngineJSON feed/attribution/event-touches.jsonlRevenue Attribution Engine
↑ Upstream — agents/sources that feed this one
  • Field Marketing Agent (canonical). Event schedule + readiness data + post-event retro context.
  • Signal Router. Routes CRM stage changes for tracked attendees.
  • Account Intel Hub. Per-account state + tier classification.
  • Revenue Attribution Engine. Per-channel pipeline-trace ground truth.
  • Operator Brief (human-maintained). KPI definitions anchor ROI math.
↓ Downstream — agents/humans that consume its output
  • Field Marketing Agent (canonical). Receives per-event pipeline data for the T+7 retrospective.
  • Head of Field Marketing (human). Reviews quarterly portfolio ROI; owns sunk-cost-event surfacing.
  • VP Marketing + CFO (humans). Receive ROI snapshots + quarterly review.
  • Revenue Attribution Engine. Receives event-touch metadata for the multi-touch attribution model.
  • Budget Allocation Agent. Uses ROI-by-event to validate next-cycle event budget asks.
  • ABM Account Researcher. Receives tier-1 event-attendance signal for dossier enrichment.
Human escalation paths
Trigger conditionEscalate toWithin
T+90 ROI < 2× on a tier-1 eventHead of Field + VP Marketing + CFOSame week (sunk-cost surfacing)
Booth-scan match rate < 80% on an eventDirector RevOps + Head of FieldSame 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 FieldSame quarter
ROI snapshot missed milestone deadline (T+7/30/60/90)Head of FieldImmediate
How to build it
System prompt
You are the Event Pipeline Agent for [COMPANY]. YOUR JOB Track every booth scan, demo signup, and meeting-on-deck to the actual CRM opportunity it became. Maintain the 10x ROI honesty check. Prevent event spend from becoming a sunk-cost fallacy. INPUTS (always read in this order) 1. /events/<event>/spec.yaml (from Field Marketing Agent) 2. /event-platform/scans.json (post-event) 3. /crm/contacts.json + /crm/opportunities.json (CRM state) 4. /events/<event>/spend-ledger.json (invoices + POs) 5. /attribution/per-channel.json (Revenue Attribution Engine) OUTPUTS - /events/<event>/pipeline-tracker.md (per event) - /events/<event>/roi-T+<n>.md (T+7/30/60/90 snapshots) - /events/portfolio/active-YYYY-WW.md (weekly digest) - /events/portfolio-roi/Q<n>.md (quarterly review) RULES 1. Every attributed pipeline cites: attendee, scan/event metadata, contact match in CRM, opportunity record ID. 2. ROI math is all-in: booth + travel + swag + sponsor fee + headcount opportunity cost. 3. T+90 ROI <2x = sunk-cost event. Surface it. 4. T+90 ROI 2-5x = acceptable. 5. T+90 ROI >=5x = recommend portfolio expansion of this type. 6. Booth-scan-to-CRM-contact match rate < 80% = data hygiene issue, not event quality issue. 7. Never compress attribution to single-touch. If the event was multi-touch, surface that. ESCALATION - T+90 <2x on tier-1: page Head Field + VPM + CFO same week. - Quarterly average <3x: page VPM + CFO same quarter.
Tools & integrations
Platform / toolUsed forRequired?
Replit + Postgres (per-event pipeline records)State + auditRequired
Event platform API (Bizzabo / Hopin / Cvent / Splash)Scan + registration + session dataRequired
Salesforce / HubSpot APICRM contact + opportunity matchingRequired
Spreadsheet (Google Sheets / Excel) for spend ledgerPer-event spend reconciliationRequired
Revenue Attribution Engine APIMulti-touch model integrationRequired
Slack APIWeekly digest + ROI escalationsRequired
Looker / Mode / TableauPortfolio ROI visualizationOptional but recommended
Guardrails — what it must not do
  • Never claim event-attributed pipeline without verified scan + CRM-contact match.
  • Never include cost-of-staff-time at zero — all-in cost is all-in cost.
  • Never share per-event ROI outside the marketing + finance scope without VP Marketing approval.
  • Honor data residency rules on attendee scan data.
  • Never modify the ROI threshold autonomously. Thresholds are quarterly portfolio decisions.
  • Never penalize tier-1 events for missing 10× on first-time events — surface trends across reps.
  • Never extrapolate from one event to forecast another’s ROI.
Evals + hallucination defense

Evals — output quality checks:

  1. Pipeline trace fidelity. Per-event: agent’s attributed pipeline vs. CRM’s ground truth. Target gap < 5%.
  2. Snapshot on-time delivery. Per-event: T+7/30/60/90 snapshots shipped on milestone. Target 100%.
  3. Scan-match rate. Per-event: % of booth scans matched to a CRM contact. Target ≥ 90%.
  4. Honesty check application. Quarterly: % of sunk-cost events (T+90 ROI < 2×) actually surfaced. Target 100% — no hidden flops.

Hallucination defense — specific checkpoints:

  • Pipeline attribution must cite specific scan IDs + CRM contact IDs + opportunity IDs.
  • ROI numerator must trace to specific opportunity revenue + close-date.
  • ROI denominator must trace to invoice / PO line items.
  • Match-rate claims must cite the raw scan count + the matched count.
  • When attribution is ambiguous (was attendee already in pipeline?), surface both interpretations.
Maturity curve + first-run checklist
v0.1 — Manual-assistPer-event tracker built on-demand. Head of Field runs ROI math by hand. Useful from day 1.
v0.5 — SupervisedPer-event automatic tracking + ROI snapshots + weekly digest. Head of Field reviews; signs off on portfolio recs. Default ship state.
v1.0 — Semi-autonomousAfter 90 days clean evals + match rate ≥ 90%, agent auto-publishes per-event ROI snapshots without HoF gate. Quarterly portfolio review stays human-led.

First-run checklist — 5 steps from spec to running agent:

  1. Wire event platform + CRM + spend-ledger inputs.
  2. Define ROI math + 10× threshold with Head of Field + CFO.
  3. Run on first event end-to-end in shadow mode. Head of Field validates every T+7/30/60/90 snapshot.
  4. Turn on live. Subscribe Head of Field + VP Marketing + CFO to per-event reports.
  5. Schedule the quarterly portfolio ROI review. Log every run in /events/tracker-agent-log.md.
Strategic · Creative · Data Driven · Revenue Accelerator