Build an Event ROI Report
Turns your event cost sheet and CRM opportunity export into an ROI report with sourced vs influenced pipeline, cost per meeting and a clear keep, change or cut verdict.
- Measurement
- intermediate
- CSV
- Google Sheets
- HubSpot
- Salesforce
- Slack
Example prompts
Once the skill is added, start a chat with one of these and attach your file if you have one.
Here's our cost sheet and the Salesforce opp export for the show. Build the ROI report for my CMO.
Compare our five trade shows this year on cost per meeting and pipeline per dollar, and tell me which to cut.
We only have leads and meetings so far. Build an early ROI read now and a template to update at 90 and 180 days.
What this skill does
This skill takes the three things most teams already have after an event (a budget vs actual sheet, a campaign member or badge scan list, and an opportunity export) and assembles them into one report. It cleans amounts and dates, classifies every opportunity as sourced, influenced or excluded with a written reason, and calculates cost per lead, cost per meeting held, pipeline per dollar and ROI.
Sourced and influenced pipeline are always reported separately, with the attribution window and engaged statuses stated at the top, so finance can check the logic. It finishes with a keep, change or cut call and the specific changes for next time.
When to use it
- "Build the ROI report for the show"
- Your CMO or CFO asks whether an event paid off
- Quarterly or annual event program reviews
- Comparing several trade shows on cost per meeting
- Setting up a report to refresh at 90, 180 and 365 days
How it works
- 1IntakeAsks once for costs, campaign members, opportunities and your attribution rules, or offers sensible defaults (9-month window, engaged = attended, visited booth or meeting held).
- 2CleanFixes currency and date formats, removes duplicate opportunities and members, and drops competitors and students from lead counts, listing each change.
- 3ClassifyLabels every opportunity as sourced, influenced only or excluded using a written decision table, so each number traces back to a row.
- 4CalculateWorks out cost per lead, per A lead, per meeting and per sourced opportunity, pipeline per dollar, ROI on closed won and sales cycle.
- 5RecommendWrites a one-screen summary, a keep, change or cut verdict and next-edition changes, then runs a validation checklist.
What you'll need
- Event costs, ideally budget vs actual by line item
- Campaign members or badge scans with campaign member status and lead tier A/B/C
- Opportunity export with account, amount, stage, created and close dates, primary campaign source and event touch
- Your attribution rules, or approval to use the defaults
What you get
A Markdown report (or Google Sheet tab, after your approval) with a summary, attribution rules and assumptions, budget vs actual, funnel, sourced vs influenced pipeline, cost metrics, a comparison table when you have several events, recommendations, data gaps, and an appendix classifying every opportunity with its reason.
Tips
- Agree the attribution rules with finance before the event, not after the results come in.
- Run it at 90, 180 and 365 days. Early reads can say on track or at risk, not cut.
- Make sure meetings held are logged as a campaign member status, or cost per meeting can't be calculated.
- Include travel and lead retrieval in costs, or say clearly that they're excluded.
- Use the sample files in assets to see the output before running it on your own data.
What's in the download
event-roi-report/SKILL.md10.0 KBevent-roi-report/assets/sample-campaign-members.csv2.7 KBevent-roi-report/assets/sample-event-costs.csv947 Bevent-roi-report/assets/sample-opportunities.csv2.7 KBevent-roi-report/references/attribution-rules.md3.4 KBevent-roi-report/references/benchmarks.md1.5 KBevent-roi-report/references/examples.md3.2 KB
Read the SKILL.md
---
name: event-roi-report
description: Builds a post-event ROI report for trade shows, conferences, sponsorships, field events and webinars. Combines the cost breakdown with lead, meeting and opportunity data from a CSV or CRM, reports sourced and influenced pipeline separately with a stated attribution window, cost per lead, per meeting and per opportunity, and ends with a keep, change or cut call. Use for event ROI, post-show reports, proving event value, pipeline per dollar or a quarterly event program review.
license: MIT
metadata:
author: eventmarketingsoftware.com
version: "1.0"
category: measurement
source: https://eventmarketingsoftware.com/skills/event-roi-report
---
# Event ROI Report
Turn a cost sheet and CRM exports into an ROI report a CMO or CFO can trust: every number traceable to a row, sourced and influenced pipeline kept apart, assumptions written down, and a clear keep, change or cut recommendation.
Works for one event or a comparison of several (a portfolio review). Works at any point after the event: an early read at 30 days, an update at 90 and 180 days, a final read at 12 months.
## Intake
If the user has an `event-context.md` file (ICP, CRM, campaign naming, tier definitions, default attribution window), read it first and don't ask for anything it already answers.
Then ask for whatever is missing in ONE message:
1. Event name(s), dates, and motion (exhibit, sponsor, attend to meet, field event, own conference, webinar).
2. Costs: a budget vs actual sheet, or at least the actual total. Ask whether staff travel and lead retrieval are included.
3. Lead and meeting data: campaign members (or badge scans) with campaign member status and lead tier A/B/C if they have them.
4. Opportunity export: ID, account, amount, stage, created date, close date, primary campaign source, and the event touch (which contact engaged and how).
5. Attribution rules. If they have none, offer the defaults below and confirm.
6. Audience for the report (CMO, CFO, sales leader, board) and the goal set before the event, if any (from an event strategy brief).
If something isn't available, proceed with what exists and list the gap in the Assumptions section. Never invent numbers.
## Connectors (all optional)
- If a Salesforce or HubSpot connector is available, read the campaign, its members and opportunities with the event as primary campaign source or with an engaged contact. Read only; don't write.
- If a Google Sheets connector is available, read the cost sheet there and offer to write the report tables to a new tab (preview first).
- Otherwise, work from pasted tables or uploaded CSV/XLSX files and return Markdown tables plus a downloadable CSV of the funnel and cost tables.
## Default attribution rules
State the rules at the top of every report. Defaults, unless the user's rules differ:
- **Engaged contact:** campaign member status of Attended, Visited Booth or Meeting Held (not Registered, Invited or No Show).
- **Sourced pipeline:** opportunities created on or after the event start date and within the window, where the event is the primary campaign source (or the first recorded touch in the CRM), the account had no open opportunity before the event, and at least one contact on the account engaged. If the event is the primary campaign source but nobody engaged (only Registered, No Show or no member at all), exclude it and flag it for review.
- **Influenced pipeline:** opportunities where at least one engaged contact from the opportunity's account touched the event before the opportunity closed and within the window. Influenced includes sourced. Never add sourced and influenced together.
- **Window:** 6 to 12 months from the event, default 9 months for influence; report status at 90, 180 and 365 days. Opportunities created more than the window after the event are excluded and listed.
- **Revenue:** closed-won amount only for ROI. Open pipeline is reported, never counted as return.
- **Costs:** all-in actual cost (space or sponsorship, booth, show services, shipping, travel, lead retrieval, promotion, hospitality). If staff time is excluded, say so.
Full definitions, edge cases and a decision table are in [references/attribution-rules.md](references/attribution-rules.md).
## Method
Copy this checklist and tick it off in the reply:
```
- [ ] 1. Clean inputs (amounts, dates, duplicates, stages)
- [ ] 2. Totals: actual cost and budget variance
- [ ] 3. Funnel: members by status, leads by tier, meetings held
- [ ] 4. Classify each opportunity: sourced, influenced only, excluded (with reason)
- [ ] 5. Compute cost metrics and ROI
- [ ] 6. Compare (prior edition, other events, or company averages) if data exists
- [ ] 7. Verdict: keep, change or cut, with the reason
- [ ] 8. Validate (checklist below)
```
1. **Clean.** Strip currency symbols and commas from amounts; flag blanks. Parse mixed date formats and say which format you assumed for ambiguous ones like 04/05/2026. Remove exact duplicate opportunity IDs (keep one, list it). Map stages to Open, Closed Won, Closed Lost.
2. **Costs.** Sum actual by line; show budget, actual, variance and variance %. If only budget exists, label the report "estimated cost".
3. **Funnel.** Count campaign members by status, engaged contacts, leads by tier A/B/C, meetings held, and engaged accounts (distinct companies).
4. **Classify opportunities** using the rules. Give every opportunity a row with its class and the reason ("created 2026-05-02, primary campaign = event, no prior open opp" or "created 14 months after event, outside window").
5. **Compute:**
- Cost per lead = actual cost / leads captured (engaged members, after dedupe)
- Cost per A lead = actual cost / tier A leads
- Cost per meeting held = actual cost / meetings held
- Cost per sourced opportunity = actual cost / sourced opportunities
- Sourced pipeline per dollar = sourced pipeline / actual cost (write as "3.4x")
- Influenced pipeline per dollar, same way, labeled as influenced
- Sourced ROI = (sourced closed-won revenue minus actual cost) / actual cost. If the user gives gross margin, also show margin ROI.
- Win rate and average sales cycle (created to close, days) for sourced closed opportunities, next to the company average if provided
6. **Compare.** For several events, use one row per event with the same columns. Rank by cost per meeting held and sourced pipeline per dollar, not by lead volume.
7. **Verdict.** Keep (met or beat its goal, or pipeline per dollar above the program average), Change (fit is right but execution or cost is off; say what to change), Cut (weak fit and weak results across two read points). An early read (under 90 days) can only say "on track" or "at risk", never "cut".
## Output template
Produce this document. Keep the summary to one screen.
```
# [Event] ROI Report ([read point: 30 / 90 / 180 / 365 days])
## Summary
- Actual cost: $X (budget $Y, variance Z%)
- Engaged contacts: N from M accounts; meetings held: N; A leads: N
- Sourced pipeline: $X (N opps), closed-won $X
- Influenced pipeline: $X (N opps), includes sourced
- Cost per meeting held: $X; sourced pipeline per dollar: X.Xx
- Verdict: Keep / Change / Cut / On track / At risk, because ...
## Attribution rules and assumptions
## Cost breakdown (budget vs actual)
## Funnel
## Pipeline (sourced vs influenced)
## Cost metrics
## Comparison (if available)
## Recommendation and next-edition changes
## Data gaps and how to close them
## Appendix: opportunity classification table
```
Table columns:
- **Cost breakdown:** Line item | Budget | Actual | Variance | Variance % | Note
- **Funnel:** Stage | Count | Conversion from previous | Note (stages: Registered or Scanned, Engaged, Tier A, Meetings held, Sourced opps, Closed won)
- **Pipeline:** Class | Opps | Pipeline $ | Open $ | Closed won $ | Closed lost $ | Win rate
- **Cost metrics:** Metric | Value | Formula | Comparison
- **Opportunity classification:** Opp ID | Account | Amount | Stage | Created | Class (Sourced, Influenced, Excluded) | Reason
- **Multi-event comparison:** Event | Motion | Actual cost | Meetings held | Cost per meeting | Sourced pipeline | Sourced $ per $1 | Influenced pipeline | Closed won | Verdict
For a "template to update later" request, also return the tables as a CSV layout with blank columns for the 90, 180 and 365 day reads. A worked example is in [references/examples.md](references/examples.md). Context statistics for the narrative (sourced and dated) are in [references/benchmarks.md](references/benchmarks.md); don't present them as targets.
## Writing rules
- Lead with the money: cost, sourced pipeline, closed won, verdict.
- Every number in the summary must appear in a table below it.
- Call influenced pipeline "influenced", never "generated".
- If sample sizes are small (under 10 opportunities), say the win rate and cycle time are directional.
- Plain words, no hype. Don't claim the event "drove" a deal unless it's sourced.
## Validation checklist
Run before sending:
- [ ] Rows in vs rows used: every opportunity is in the classification table, including excluded ones
- [ ] Sourced pipeline is less than or equal to influenced pipeline
- [ ] No open pipeline counted as return in ROI
- [ ] Cost total matches the sum of line items
- [ ] Attribution window and engaged statuses are stated
- [ ] Duplicates and blanks are listed, not silently dropped
- [ ] Ambiguous dates and currency assumptions are stated
## Approval gates
- Never update opportunities, campaigns or fields in the CRM. If the user wants campaign influence fixed in the CRM, list the proposed changes as a table and stop for a yes.
- Before writing to a Google Sheet or posting a summary to Slack, show the exact content and wait for approval. Default to a draft.
## Privacy
Opportunity and contact exports hold personal data. Keep the analysis in the user's own tools, and leave contact names out of the report unless the user asks; use account names and counts. Don't paste personal data into anything outside the conversation.
## Related skills
event-strategy-brief (sets the goals this report is judged on), event-attribution-analysis (deeper account-level lift analysis), event-debrief, event-portfolio-scorer.
FAQ
How do I calculate event ROI?
What's the difference between sourced and influenced pipeline?
What attribution window should I use for trade show ROI?
Can I build an ROI report without a CRM connector?
More measurement skills
intermediate
Analyze Post-Event Survey Results
Codes open-ended survey comments into themes, calculates NPS by segment, ranks sessions and speakers, and lists the five fixes that matter most for next time.
advanced
Explain Event Influence on Pipeline
Matches event attendees to accounts and opportunities, compares win rate, deal size and cycle time for engaged vs non-engaged accounts, and writes an honest narrative for leadership.
easy
Run a Post-Event Debrief
Collects team feedback, Slack threads and the numbers into a keep, change, cut debrief with owners and dates, then drafts a starter brief for the next edition.