---
name: event-strategy-brief
description: Writes a one-page strategy brief for a B2B event before money is committed. Sets the primary goal (pipeline, meetings, expansion, brand, customer retention), target audience and accounts, event motion (attend to meet, exhibit, sponsor, field event, own conference, webinar), KPIs with targets and the math behind them, budget range, owners, timeline and risks. Use when planning a new event, getting budget approval, aligning sales and marketing on goals, or setting KPIs before a show.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: strategy-and-budget
  source: https://eventmarketingsoftware.com/skills/event-strategy-brief
---

# Event Strategy Brief

Events that try to do everything measure nothing. This skill turns a request like "we should be at that show" or a messy planning doc into a one-page brief: one primary goal, the audience, the motion, KPIs with targets worked back from the goal, a budget range, owners, a timeline and risks. It's the document the ROI report will later be judged against.

## Intake

If the user has an `event-context.md` file (ICP, average deal size, sales cycle, conversion rates, team, budget norms), read it first.

Ask for whatever is missing in ONE message:

1. The event or idea: name, dates, location, format, who asked for it and why. Paste any notes, invitation or prospectus.
2. ICP and the target accounts or segment this event is for.
3. Average deal size, sales cycle, and the team's own conversion rates if known (meeting to opportunity, opportunity to win).
4. Budget range, or "help me estimate".
5. Team: who owns it, who staffs it, which sales leaders are involved.
6. Who approves the brief (CMO, sales VP, finance).

If the user doesn't know conversion rates, don't invent them. Set targets in meetings and opportunities directly, mark the rates "to be measured", and say the pipeline target is a hypothesis.

## Connectors (all optional)

- If a Salesforce or HubSpot connector is available, read average deal size, cycle length and past event results to ground the targets. Read only.
- If a Google Sheets connector is available, read a budget or write the KPI table to a sheet after a preview.
- If a Slack connector is available, offer a short summary post for the approval channel as a draft; post only after a yes.
- Otherwise, work from pasted text or files and return the brief as Markdown.

## Method

```
- [ ] 1. Pick ONE primary goal (and at most one secondary)
- [ ] 2. Define audience and target accounts
- [ ] 3. Choose the motion and role
- [ ] 4. Work KPI targets back from the goal; show the math
- [ ] 5. Budget range and cost per outcome
- [ ] 6. Owners, timeline, risks
- [ ] 7. Validate and write the one-pager
```

1. **Goal.** Choose one: net-new pipeline, meetings with target accounts, expansion of existing customers, customer retention and advocacy, brand and category presence, or recruiting partners. If the request mixes several, pick the primary with the requester and park the rest as secondary or out of scope. Brand-only goals still need a measurable proxy (target-account attendance, session attendance, share of voice the user can actually measure).
2. **Audience.** Industries, company size, titles (buyers and influencers), number of target accounts expected, customers vs prospects.
3. **Motion.** Attend to meet, exhibit, sponsor, speak, host a side dinner or field event, own conference, or webinar. Pick the cheapest motion that reaches the audience and serves the goal, and say why the others were rejected.
4. **KPIs.** Use [references/kpi-math.md](references/kpi-math.md). Work backwards: pipeline target, then opportunities needed (target / average deal size), then meetings needed (opportunities / meeting-to-opportunity rate), then outreach or invites needed. Include leading indicators (meetings booked before the event, target accounts registered) and lagging ones (sourced and influenced pipeline at 90 and 180 days, closed won). Use lead tier A/B/C and campaign member statuses (Registered, Attended, Visited Booth, Meeting Held, No Show) so KPIs map to the CRM.
5. **Budget.** A range with the main lines, and the implied cost per meeting and pipeline per dollar at target. If the implied cost per meeting is far above the user's past events, say so.
6. **Owners and timeline.** One accountable owner, plus owners for sales outreach, logistics, content and follow-up. Work the timeline back from the event date: approval, booking, pre-show outreach (typically starting 6 to 8 weeks before), staff briefing, follow-up within 24 to 48 hours after, ROI reads at 90 and 180 days.
7. **Risks.** Top 3 to 5 with a mitigation each (for example "no attendee list: book meetings from the speaker and sponsor lists"; "sales doesn't follow up: agree tier A owners before the show").

## Output template

Keep the brief to one page. Put supporting math in an appendix.

```
# [Event]: Strategy Brief
Owner: [role] | Decision needed by: [date] | Status: Draft

## Why this event
2 to 3 sentences.

## Goal
Primary: ... Secondary: ... Out of scope: ...

## Audience and target accounts
## Motion and role
## KPIs and targets
## Budget
## Team and owners
## Timeline
## Risks and mitigations
## Decision requested

## Appendix: KPI math and assumptions
```

Table columns:

- **KPIs:** KPI | Type (leading or lagging) | Target | How measured (CRM field or status) | When measured
- **Budget:** Line | Low | High | Note
- **Timeline:** Milestone | Date | Owner
- **Risks:** Risk | Likelihood (low, medium, high) | Mitigation | Owner

Worked examples (a trade show for budget approval and a 12-city dinner series): [references/examples.md](references/examples.md).

## Rewriting a messy doc

When the user pastes notes, keep every decision and number they contain, mark contradictions ("budget says $80k on page 1 and $120k in the table"), and list open questions at the end instead of guessing. `assets/sample-planning-notes.txt` is a test input.

## Validation checklist

- [ ] Exactly one primary goal
- [ ] Every KPI has a target, a measurement source and a date
- [ ] KPI math is shown, and every assumed rate is labeled as the user's or "to be measured"
- [ ] Budget range implies a cost per meeting and pipeline per dollar
- [ ] Every timeline item and risk has an owner
- [ ] Fits on one page (appendix aside)
- [ ] No invented statistics

## Approval gates

The brief is a draft until the user says otherwise. Don't post to Slack, send for approval, or write to shared sheets without showing the exact content and getting a yes.

## Related skills

event-portfolio-scorer (is this event worth it compared with others), trade-show-budget (line-item budget), event-roi-report (judges the event against this brief), event-debrief (next edition).
