The In-House Event Planner's SF/EU Corridor Playbook (2026)

You, as Camila, do not look like a traditional corporate travel manager. You report to VP Marketing, not procurement. You have no purchasing department to escalate to. The contracts you sign go through your legal team only if they cross a dollar threshold you set yourself, because nobody told you what the threshold should be. And every quarter the CFO asks the same question: what did the event return? And every quarter you sweat the answer, because you instinctively know cost-per-attendee is not the right frame, but you have not yet found the slide that wins the room.

This playbook is how I run the role today, written as a working document I would hand to a new in-house event lead on day one at any growth-stage US SaaS company shipping events to the EU. It has six parts: the five-stage maturity diagnostic, the three-city EU portfolio, the finance narrative that wins the CFO, the change-management runbook for the inevitable last-minute pivot, the procurement-replacement decision tree, and the year-end review that gets you the budget you actually need.

What is an in-house event planner at a growth-stage SaaS? (50-word answer)

An in-house event planner at a growth-stage SaaS owns 8 to 16 events per year — sales kickoffs, customer summits, exec offsites — typically for 50 to 300 attendees, reporting to VP Marketing with no dedicated procurement support. The role lives or dies on the finance narrative: pipeline influenced, not cost per attendee.

Why this role is not a corporate travel manager role

The closest job description to yours is "corporate travel manager," and almost none of the public playbooks for that role apply cleanly. A CTM at a 5,000-person European corporate runs 100 to 200 hotel RFPs a year, sits inside procurement, has finance partners and legal review built into the process, and reports through a chain that ends at a Chief Procurement Officer. You, Camila, run 12 events a year for a 600-person SF SaaS, you sit inside marketing, you have no procurement function, and your slide reviews go to a CFO who reads pipeline as fluently as cost.

The role is also not pure event marketing. Event marketing leads at a growth-stage SaaS run demand-generation field events, often dozens per quarter, with a heavy bias to virtual and hybrid. Your events are the flagship ones — the customer summit, the SKO, the exec offsite — where the stakes are board-visible and the failure modes are personal. You are operating in a category of one inside the org chart, which is part of why this playbook exists.

Score your maturity: the 5-stage in-house event lead diagnostic

Run this on yourself honestly. Most in-house event leads at growth-stage SaaS sit at stage 2 or 3. The point is not to be defensive about it; it is to know which habit to build next.

The three-city EU portfolio: London, Paris, Amsterdam

I, as Camila, run a three-city EU portfolio that covers roughly 80% of my US-EU corridor demand. London handles the customer summits where the largest cluster of EU customers sits and where US executives can fly in on a single overnight. Paris handles the prestige event — the customer advisory board, the keynote launch — where the venue itself is part of the message. Amsterdam handles the working summit — the 2-day product council, the partner conference — where the brief is execution, not theater.

The fourth city slot rotates. In 2025 it was Barcelona for a Q2 customer summit; in 2026 it is Lisbon for the same event. Adding a fourth city every year keeps the portfolio honest and gives you a benchmark against the established three. The London corporate event venues, Paris AGM venues, and Amsterdam AGM venues guides are the starting point for the per-city shortlist.

The finance narrative: pipeline influenced, not cost per attendee

The single biggest mistake in-house event leads make at growth-stage SaaS is leading with cost per attendee in finance reviews. The CFO is not buying a per-head metric; the CFO is buying pipeline. If your post-event slide opens with "we spent $487 per attendee," you have already lost the room. If it opens with "this event touched $14.2M in pipeline across 41 opportunities, with a blended cost-of-pipeline of 3.4%," you are speaking the CFO's language.

The three numbers I put on the finance slide every time: (a) pipeline influenced in dollars, with the attribution window defined (typically 90 days post-event), (b) cost per qualified attendee, where qualified is a job-title filter agreed with sales ops in advance, and (c) post-event NPS. The first wins the CFO; the second is the operational benchmark; the third is for VP Marketing. The event ROI methodology piece covers the broader attribution framework.

The change-management runbook: T-60, T-30, T-15 days

Sales leadership will move something at T-30 days. Plan for it. The three changes that come up, in order of frequency: headcount (the sales team added 40 people, the deal team grew, the partner program wants seats), the date (a board offsite, a competitor launch, an exec calendar conflict), the format (a 3-day summit shrinks to 2 days, or hybrid attendees get added late). The runbook is what protects margin on each.

1. T-60 days: lock the headcount band. Get sales leadership to commit to a +/-15% headcount range in writing. Inside the band, no contract change; outside, attrition clause triggers. The attrition clause explainer is the language to use.
2. T-30 days: format and date freeze. Any format change after T-30 requires VP Marketing sign-off and a written cost delta. Any date change after T-30 requires CFO sign-off because cancellation fees on the EU side typically kick in at this window.
3. T-15 days: only headcount, only inside the band. Inside the +/-15% band, F&B and room blocks flex. Outside the band, the event is renegotiated, not modified.

The procurement-replacement decision tree

You, as Camila, have no procurement function. That is not a bug; it is the structure of the role at growth-stage SaaS. But you do need a replacement decision tree for the three things procurement would otherwise do: vendor selection, contract review, and supplier consolidation.

For vendor selection: a 4-criteria scorecard (capacity fit, prior reference at a similar-stage SaaS, contract flexibility, total cost), applied to a shortlist of 4 to 6 venues per event. For contract review: a written dollar threshold (typically $50k for legal review, $250k for CFO sign-off, $500k for board notification). For supplier consolidation: a year-end review of which venues, AV partners, and DMCs you used twice or more, and which can be put on a standing agreement. The agency vs in-house piece covers the broader build-versus-buy decision.

The year-end review slide that wins the budget

The year-end review is the one slide that determines next year's budget. The structure I use: a single horizontal stack showing each event in the calendar year as a column, with three rows underneath — pipeline influenced (dollars), cost per qualified attendee (dollars), NPS (number). A fourth row, optional, shows year-over-year delta on each metric. The slide is dense but it answers the only three questions the CFO is going to ask: did the portfolio return, was it efficient, did attendees value it.

The narrative that surrounds the slide matters as much. I open with "this year the event portfolio touched $X in pipeline at a blended cost-of-pipeline of Y%, against an internal benchmark of Z%." If Y is below Z, you are asking for budget expansion. If Y is at Z, you are defending current budget. If Y is above Z, you are negotiating which events to cut and which to reinvest. The event budget template is the structure I use to back into the numbers.