Chapter 02 of 12
Response objectives, goals, and jobs
What the event must produce, who owes what, and how it gets measured. Locked before logistics spend — objectives set at the airport are decoration.
The objectives hierarchy (why "leads" is not a goal)
The serious measurement schools (Phillips ROI Methodology; Elling Hamso's Event ROI Institute pyramid — see research-foundations) agree on the shape: set objectives top-down before the event, measure bottom-up after. Adapted to INTO's motion:
Right people in the room → right conversations held → behaviour changed → business impact → ROI
(target audience) (P1) (P2/P3: meetings) (P4/P5: opps, pipeline)The middle level is the one teams skip: behaviour objectives — the concrete act a prospect performs after the event that signals movement. For INTO these are observable and worth writing per event: accepts a follow-up working session, shares an internal AI-readiness doc, introduces us to the budget holder, asks for a Path A scope conversation. Pipeline is the lagging result of these acts; the acts are what your follow-up plan is engineered to trigger.
Writing response objectives
Rules:
- Named count + named audience-class + deadline. "Meet people" fails. "12 held conversations with Heads of Product/Ops at mid-market B2B firms, 6 meetings held by T+21" passes. (Format per the SMART-goal pattern the practitioner literature converges on — see research-foundations.)
- Primary objectives are pipeline objectives (P1–P5). Everything else — content captured, social reach, client hospitality — is secondary. Secondary objectives are counted, never substituted: an event that nails S1–S4 and misses P1–P3 failed.
- One event, one primary intent. Deal acceleration, new pipeline, expansion, market intelligence, or brand/authority — pick per event; a dinner trying to do all five does none (SignalFire's dinner doctrine, 2025). The scorecard's "business objective served" field forces this.
- 90-day windows for pipeline objectives, with the caveat written in. Consulting's 6–16 week cycle means T+90 shows opportunities, not closed revenue; the T+180 view completes the picture (chapter 11).
- ROO (return on objectives) is allowed for at most the CMO-named brand exceptions (chapter 03) — scored achievement of pre-declared objectives, never a retroactive story.
Default targets (starting points, replaced by our own CRM history as it accrues)
| Objective | Sponsored/attended conference | Owned dinner (10–12 seats) | Owned workshop (12–20) |
|---|---|---|---|
| P1 qualified conversations | 8–12 per attending exec | every guest = a conversation | every participant |
| P2 meetings booked | ≥5 pre-booked per exec before travel approved; +3–5 on-site | 3–5 follow-up meetings | 4–8 assessment offers accepted |
| P3 held by T+21 | 60–75% of booked | 80%+ | 70%+ |
| P4 opportunities by T+90 | 2–4 | 3–5 per dinner (30–50% of guests is the published vendor range — treat as ceiling) | 2–4 |
Benchmark sources + caveats in research-foundations §Benchmarks. Mark targets built on vendor ranges as Inference in the pack until our own data replaces them (SOP §12).
Per-person quotas — everyone travels with a number
The published booth benchmark is 3–5 qualified interactions per staffer per hour; the transferable version for a boothless consultancy is meetings and conversations per exec (memo-02 synthesis): 8–12 held ICP conversations per attending exec per conference, of which ≥5 pre-booked before travel is approved. The pre-book gate is the tooth: if pre-booked meetings sit under 50% of quota at T-3w, downgrade attendance — fewer people, cheaper mode (chapter 03 kill criteria).
Quotas are per person, visible to everyone, and reconciled at the evening debrief. The point is not surveillance — it's that a quota converts "attending" into "hunting", and it surfaces early when the event itself is the problem (nobody hitting quota on day one = wrong room; trigger the kill condition, refocus on side-meetings).
The crew manifest — jobs, not vibes
Every event names one DRI per job before committed (pack file 02). The jobs that actually decide outcomes:
| Job | Why it's load-bearing |
|---|---|
| Event lead | One throat to choke for the whole pack; runs the countdown; Event Manager by default |
| Exec sponsor | The calendar meetings are booked against; the signature on exec-to-exec invites |
| Sales captain | Owns quotas, the daily standup, capture discipline, same-day CRM |
| Comms owner | Runs the segment matrix (chapter 07); protects clients from prospect-grade messaging |
| Social/content owner | Runs the shot list + posting cadence (chapter 08); named or it doesn't happen |
| Logistics owner | Runs bookings + the travel manifest (chapter 05); one owner per manifest, always |
| Follow-up owner | Named before the event. The single most predictive staffing decision in the research: follow-up dies when it's "sales, eventually" (chapter 10) |
| Capture (photo/video) | Producer-owned; content value is created live or never |
One person can hold several jobs at INTO's size — but each job has exactly one name, and the follow-up owner's calendar is protected for T+0→T+21 like a delivery sprint.
On-site operating cadence
- Morning standup (15 min, fixed time/place): each person states yesterday's highlight, today's plan, today's number. The SaaStr-school discipline; cheap and it works.
- Evening debrief (15 min): capture sheet reconciled, CRM entries done, promise ledger extracted, quota pace vs plan, next-day adjustments. CRM entry SLA is same-day because context decays in hours, not days (memo-05: HBR 2011 response-decay evidence; capture-context evidence in memo-04).
- Intel is a deliverable too: session insights, competitor presence, and market signals go to the Researcher via the log, not into a notebook that never gets opened.