Events Are a Targeting Problem

Most event calendars are built the same way. Someone lists the shows the company went to last year, adds the two a board member mentioned, and fills the budget until it runs out. Nobody asks who, specifically, needs to be in the room, or what the company needs from them.

That is how a seed-stage company ends up spending a third of its marketing budget on one booth at a show where the people who matter walked past it on the way to a meeting somewhere else. It is also how a $50 million company ends up with a $2 million event line that produces photos and no pattern, because nobody ever asked the same question at that scale.

This is the methodology I use to decide which events a company should do, in what format, and why. How to align an event to the buying committee and not just the company profile. What the different event types are actually for. When to spend on an event that will not return, and how to say so out loud. And the decision I get asked about most: whether to buy the booth at the big show, or skip it and send executives with a full meeting calendar instead. The answer changes with stage, and I will walk it from seed to pre-IPO, because the mistake at each stage is different.

Start with the ICP, then go one level deeper

Everyone says they pick events by ICP. What they usually mean is they check the attendee list for company size and industry. That is the company profile, and it is necessary, but it is the shallow version of the question.

An enterprise security deal is closed by a committee, not a company. In my experience across IAM, endpoint, network security, SaaS security, and identity intelligence, the committee looks roughly like this:

• The economic buyer. CISO, sometimes CIO. Owns the budget, signs the contract, and is the hardest person to reach at scale.
• The technical evaluator. Security architect, senior engineer, SOC lead. Decides whether the product actually works and whether it will be a nightmare to run.
• The champion. Usually a director or senior manager who owns the problem day to day and will carry the deal internally if you give them a reason.
• The influencers. IT, compliance, risk, sometimes legal and procurement. They rarely start a deal but they can stop one.
• The executive sponsor. Sometimes the CFO, sometimes a board member, sometimes the CEO in a smaller company. Shows up in the last mile.

Every one of those people goes to different events, for different reasons, and behaves differently when they get there. The CISO goes to a Gartner summit or an invitation-only regional dinner and does not walk the expo floor. The architect goes to BSides and to the deep-technical tracks at the big shows and will happily spend twenty minutes at your booth if you can answer a hard question. The champion goes to whatever their budget allows, which is often the regional summit or the vendor-hosted roundtable. The compliance influencer is at a vertical event with the letters ISAC in it, not at a security conference at all. The economic buyer with a funded project in the next two quarters is at a curated executive program where the organizer screened for exactly that. And if you sell through partners, there is a sixth seat that is not on the customer's org chart at all: the partner rep who decides whether your product is the one they bring into the account, and who is at the partner's kickoff, not yours.

The committee also grows as your deals grow. At $30,000 a CISO can sign alone. At $300,000 there is a security architecture review board, a procurement team with its own calendar, a legal reviewer, and often a business unit sponsor who cares about an outcome and not about security at all. Companies that move upmarket keep running the events that reached the committee they used to sell to. Redraw the map every time the average deal size doubles.

So the alignment question is not "does this event reach our ICP." It is "which seat on the buying committee does this event reach, and is that the seat we need right now."

That reframing changes the calendar. If your deals are stalling because the architect cannot get comfortable, you do not need another CISO dinner. You need to be on a technical stage or in a hands-on lab. If you have champions who love you and cannot get budget, you need the economic buyer in a room with a customer who already spent it. If you keep losing late to procurement, an influencer-heavy vertical event might be the highest-return event on your calendar, even though nobody there has the word security in their title.

Build the map before you build the calendar. One row per committee seat, one column per candidate event, a mark where the seat actually attends. Then look at which seats you are over-serving and which you have never once put a person in front of.

What the event types are actually for

The word event covers a dozen different things. They reach different seats and they do different jobs.

Mega trade shows. RSAC and Black Hat USA in the States, Infosecurity Europe in London, it-sa in Nuremberg, GISEC in Dubai, Black Hat MEA in Riyadh, and the regional Black Hat and GITEX editions across Asia and the Gulf. Everyone is there, which is the point and the problem. Reach is enormous and attention is scarce. They work as a meeting venue for a startup and as a brand statement for a scaled company. They do not work as a lead source for a startup with two sellers.

Industry conferences. Gartner Security and Risk, Forrester, the large regional shows. Skew senior. Expensive per attendee, but the attendee is often the economic buyer, and analysts are in the building.

Curated executive programs. This is the category most calendars miss, and it is the one I lean on hardest when the goal is pipeline with the economic buyer. Evanta, Argyle, CDM Media, Apex Assembly, Richmond Events, Executive Platforms, and the hosted-buyer formats run by some of the larger organizers. The model is different from a conference: attendees are vetted for title and budget authority, many are screened for an active project in the next twelve months, and the organizer contracts a set number of one-on-one meetings with named attendees as part of the sponsorship. You pay per meeting, in effect, not per badge. The cost per attendee looks alarming next to a trade show until you notice that every attendee is a CISO or a VP with money and a project. For a startup with a $100,000 average deal and two sellers, eight contracted meetings with qualified economic buyers is worth more than any booth. Ask for last year's attendee list by title and company, ask how the project screen works, and ask what happens if the contracted meetings do not materialize. The good organizers have an answer for all three.

Regional CISO summits. Half-day or one-day formats in a city, often with a smaller version of the contracted meeting model built in. Less rigorous screening than the curated programs, lower cost, broader mix of seniority. This is where the champion and the economic buyer overlap most reliably at a price a Series A can carry. My default anchor for pipeline volume from Series A through the point where a company has regional sales teams, with the curated programs above it for the accounts that matter most. Past that point the regional summits become a territory tool that each regional marketer runs, not a headquarters decision.

Community and practitioner events. BSides, ISSA and ISACA chapters, OWASP, local meetups. Cheap, credible, technical. The architect lives here. A speaking slot at one of these does more for the technical evaluator than a booth anywhere.

Vertical events. FS-ISAC for financial services, HIMSS for healthcare, NASCIO or the law enforcement conferences for public sector. Nobody there is a security buyer first; they are a banker or a hospital CIO or a state official. If your deals live in a vertical, this is where the influencers and sponsors are, and there is almost no vendor noise.

Thought leadership stages. A Black Hat Briefing, an RSAC track session, a SANS Summit talk, a Gartner or Forrester speaking slot, a keynote at a vertical event, a hosted CISO panel. Speaking is a different instrument from sponsoring, and it is the one that builds the credibility every other event trades on. A CISO who saw your CTO explain a problem well on a peer-reviewed stage takes the meeting. A CISO who saw your logo on a floor plan does not. The submission process is competitive and the lead times are long, six to nine months for the big programs, so speaking has to be planned a year out and treated as a program, not a hope. Reaches every seat at once, because the recording and the deck keep working long after the room empties. Measure it in briefings requested, inbound lift, sales use of the clip, and whether the analysts start quoting you.

Analyst and press events. Not pipeline. Category. Where positioning gets validated or corrected by the people who write the reports your buyers read. Pairs with the speaking program above: a stage gets you the briefing, the briefing gets you into the report.

Channel partner events. Reseller and distributor sales kickoffs, distributor roadshows, CRN and channel-community conferences, partner QBRs run as events, co-hosted regional dinners where the partner brings their customers and you bring the story. If resellers are how you sell, this is the calendar. I have run events across the US, Europe, Israel, the Middle East, and Latin America, and the channel-first markets are where this matters most. In the Gulf and in much of Latin America the channel is the sales force, and a booth at a third-party show does nothing for a partner rep who was not there. I built a Middle East go-to-market on partner events for exactly that reason. The measure is partner-sourced pipeline and partner reps who can pitch you without help.

Technology partner events. The ecosystem conferences of the platforms you integrate with: Microsoft Ignite, AWS re:Inforce, Google Cloud Next, Oktane, Fal.Con, ServiceNow Knowledge, and the smaller partner summits those companies run by region. Different economics from a security show. The attendees already bought the platform, your integration is the reason to talk, and the platform vendor often subsidizes partner presence or gives you stage time in exchange for the joint story. The technical evaluator and the champion are here in numbers, and the platform's own sellers are a second audience worth as much as the attendees. The measure is co-sell opportunities registered and integration adoption, not badge scans.

Owned events. Executive dinners, roundtables, customer advisory boards, user conferences. You control the guest list, the agenda, and the follow-up. The highest-return format on the calendar once you can fill the room, and the only format where the economic buyer will give you two uninterrupted hours.

Virtual. Webinars and virtual roundtables. Low cost, high frequency, the right tool for follow-up and for regions you cannot fly to. The wrong tool for a first impression with a CISO.

The mistake is treating these as interchangeable line items competing for the same budget. They are different instruments. A calendar with three mega shows and nothing else is a brand plan pretending to be a pipeline plan. A calendar of eight dinners and no stage time will produce meetings and no market awareness. A calendar with no partner events at a company that sells through partners is a calendar for a different company. The mix is the strategy.

The reasons to do an event, and why you have to pick one

Every event has to have one primary goal, written down before the contract, with the metric that goes with it. Not two goals. One. Secondary benefits are welcome, but the renewal decision gets made on the primary.

Pipeline. Meetings, MQLs, SQLs, closed won at nine months. This is the default and the only goal where return on marketing spend is the right yardstick.

Visibility and category. Share of voice, analyst mentions, inbound lift in the four weeks after, branded search volume. Measurable, but not in pipeline terms, and you have to say so before you spend or someone will measure it in pipeline terms afterward.

Credibility. Analyst briefings held, press coverage, a keynote that gets clipped. Often a precondition for pipeline six months later. Hard to attribute, real all the same.

Partner and channel. Partner-sourced pipeline, new partners signed, partner reps trained. Different funnel entirely.

Customer retention and expansion. Renewal rate for attendees versus non-attendees, expansion pipeline, references generated. Owned events do this best.

Recruiting, investor signaling, competitive intelligence. Legitimate reasons, small budgets, honest labels. Never let them become the unstated justification for a pipeline event that missed.

When I ask a team why they are going to a show and get four answers, I know the event will fail on all four. Pick one. Measure that one. Let the rest be upside.

When an event makes strategic sense even though the ROI will not be there

Some events will not pay back in pipeline and should happen anyway. The methodology does not forbid them. It requires you to name them.

Category creation. If you are building a category that does not have a name yet, you need to be on stages where the analysts and the press are, saying the name until they repeat it. That is a visibility and credibility spend, budgeted as such, measured in mentions and in whether the analysts start using your language.

Entering a new vertical or geography. The first year in public sector or financial services or the Middle East is a learning year. You are there to understand the buyer, meet the partners, and be seen to have shown up. Pipeline follows in year two if you did year one properly.

Funding proximity. In the two quarters before a raise, a credible presence at the flagship show of your category is part of the story investors will check. Not a booth necessarily, but a presence, a stage, a dinner with logos in the room.

Table stakes. In some categories, enterprise buyers assume that a vendor absent from the flagship show is either too small or in trouble. If your buyers think that way, absence has a cost too. But be honest about whether your buyers actually think that way, or whether your sales team does. This one scales with stage: nobody expects a seed company on the RSAC floor, and everybody expects a company that just raised a $100 million round to be there.

Analyst and press days. These will never show up in pipeline attribution and they shape every deal you run for the next year.

The rules for strategic events are simple. State the goal in writing. Cap the spend at a number that will not starve the pipeline events. Choose the cheapest format that achieves the goal, which is almost never a booth. And still measure something, even if it is only "we met the six analysts on the list and three of them asked for a follow-up."

What is not allowed is the strategic label applied after the fact to an event that was sold as pipeline and did not deliver. That is how calendars fill with events nobody can defend.

The booth question: RSAC and shows like it

The booth decision is the one that exposes whether a team has a methodology or a habit. It also changes completely with stage, so I will take it stage by stage. The reference show is RSAC, but the logic holds for Black Hat, Infosecurity Europe, GISEC, or whichever show is the flagship in your category and region.

First, the cost of being on the floor, because most people underestimate it. A 10 by 20 booth in the main hall at RSAC, once you add the build, drayage, electricity, internet, lead retrieval, four people for four nights in San Francisco in April, swag, and a dinner, lands between $120,000 and $200,000. A 10 by 10 in the early stage expo is cheaper, perhaps $40,000 to $70,000 all in, and it is in a part of the building the economic buyers do not visit. A 20 by 30 island with a proper build, a meeting room, and a staff of ten runs $400,000 to $700,000. The big vendors on the main aisle are spending well over a million.

Second, who is on the floor. Practitioners, students, other vendors, partners, some champions, architects with a shopping list. The economic buyers are in the building, but they are in hotel suites, invitation-only dinners, and analyst meetings, not walking the aisles. This is true at every stage. What changes by stage is whether you can afford to be visible to the floor anyway.

Seed and pre-seed

No booth. Not the kiosk either. The entire programs budget might be $150,000 to $400,000, and the founders are the sales team. Send the two founders and, if there is one, the first seller. Book meetings for six weeks beforehand from the registration list and from your own target accounts, using the founders' networks and a scrappy outreach sequence. Borrow a corner of a partner's booth for the meetings that need a badge. Host one dinner for eight. Walk the floor for competitive intelligence and to meet the analysts at their sessions. Cost: $12,000 to $25,000. Goal: meetings and learning. Measure: meetings held, opportunities created, and what you learned about how buyers describe the problem.

Series A

Still no booth, and this is where the pressure to buy one starts, because a board member went to RSAC and did not see you. Programs budget is somewhere between $400,000 and $1.2 million. A main-hall booth is 15% to 40% of the year. Instead, run the no-booth play properly: two executives who can carry a CISO conversation and one BDR who owns the calendar. Rent a meeting room in a hotel within walking distance of the Moscone. Pull every target account that has registered, have the BDR book 25 to 40 meetings before anyone gets on a plane, and host a dinner on night one for the ten most important people in the city that week. All in, $25,000 to $45,000.

Run the math the way the Event ROI Planner does. Thirty pre-booked meetings with target accounts, treated as SQLs, closing above the general MQL rate because they were qualified before they were booked. Against that, a booth producing 250 scans, of which perhaps 60 are qualified, 12 become MQLs, and six become SQLs. The no-booth program generates more SQLs at a quarter of the cost, and the pipeline is with accounts you chose.

Then take $30,000 of the money you did not spend and put it into one curated executive program in the same quarter, where the organizer contracts eight to ten meetings with screened CISOs. RSAC week produced thirty chosen meetings and the following month produced ten more with buyers who have a project, for less than the booth alone.

The visible cost of the no-booth play is that you are not visible. If your primary goal for the show is pipeline, that cost is irrelevant. If your primary goal is category visibility, it is the whole problem, and you should be looking at a speaking submission and a press day rather than a booth anyway.

Series B

Now the answer is usually a small booth, and the question is what you put around it. You have five to fifteen sellers, a few customers who will speak, and a programs budget of $1.5 million to $4 million, so a $60,000 to $100,000 presence is within reason. The hybrid works here: take the smallest booth that gets you on the floor plan and a badge allotment, spend nothing on the build beyond a clean backdrop and a demo screen, and put the savings into a meeting suite upstairs, a dinner, and a speaking submission filed nine months earlier. The booth is a landmark and a place to leave collateral. The business happens upstairs. Measure both halves separately: the booth on qualified scans and cost per MQL, the suite on meetings and SQLs. One of them will win, and that tells you what to do next year.

Buy a bigger booth only when at least three of these are true. You have five or more sellers on the floor who can work the leads. You have a customer who will stand at the booth and tell their story. Brand visibility is the stated primary goal and is budgeted as such. The booth has a private meeting room inside it. The whole thing is under 10% of the programs budget.

Series C, D, and pre-IPO

The booth is no longer the question. You will have one, it will be substantial, and the economic buyers in your target accounts expect to find it. The questions become how large, what it is for, and what else happens that week. The programs budget is $5 million to $20 million and the flagship show can reasonably take 5% to 8% of it. At this stage the show is a brand statement and a customer event as much as a pipeline event, and it should be planned that way: a customer appreciation dinner or reception with a hundred logos in the room, an analyst day the Monday before the hall opens, a press briefing schedule, an executive suite running twenty meetings a day with pre-booked accounts, a partner track where your technology and channel partners meet your sellers, and yes, a booth with a stage and a demo bar where the technical evaluators can spend twenty minutes with an engineer. The measure is a scorecard, not a single number: pipeline from the suite, qualified scans from the floor, analyst and press outcomes, customer renewal and expansion signals from the dinner, and partner-sourced opportunities from the partner track. Each has its own owner. The mistake at this stage is the opposite of the seed mistake: the booth gets so much attention that the suite, the analysts, and the customers get the leftover planning.

After the IPO

Nothing about the methodology changes, but the risk does. Public companies drift into doing every flagship show at the same scale every year because cutting one looks like weakness to investors and competitors. The buying-committee map and the one-goal rule are what keep a $10 million event line honest. Every show still gets a goal, a forecast, and a nine-month review, and the review has to be allowed to conclude that the island can be a peninsula next year.

The rule that holds at every stage

The floor reaches the practitioner and the champion. The suite, the dinner, and the curated program reach the economic buyer. The stage reaches everyone. Decide which seat you need, put the money there first, and let the booth be whatever is left over. At seed that means no booth. At pre-IPO it means the booth is the smallest part of the plan even when it is the largest line on the invoice.

How to forecast an event, and the number that decides renewal

Every event gets a forecast before the contract. The arithmetic is simple. The discipline is doing it before the money moves and checking it after.

Start with total spend, not the sponsorship fee. Booth services alone can add 40% to a mid-size show once you count electricity, internet, drayage, and lead retrieval. Add travel, swag, printing, and the dinner. Then walk the funnel:

• Raw leads = attendees x capture rate. A booth captures 5% to 12% of the floor. A hosted dinner captures nearly everyone in the room. A curated program hands you the list.
• Qualified leads = raw leads with students, vendors, and wrong titles removed. Plan on keeping about 70%.
• MQLs = qualified leads x your lead to MQL rate. I use 20% as a default for enterprise security.
• SQLs = MQLs x your MQL to SQL rate, plus every meeting booked before or during the event. Those meetings are already SQLs. Count them.
• Closed won = MQLs x your MQL to closed won rate. My default is 13.3%. Pre-booked meetings close at roughly double that.
• Added pipeline = SQLs x average deal size. Forecast revenue = closed won x average deal size. Return on marketing spend = forecast revenue divided by total spend.

A worked example. A 600-person regional summit at $18,000 all in, 8% capture, 70% qualification, 20% to MQL, 50% to SQL, 13.3% to closed won, six meetings booked on site, $60,000 average deal. That produces 48 raw leads, 34 qualified, about 7 MQLs, about 9 SQLs, and 2.5 forecast closed won deals. Forecast revenue is roughly $149,000 against $18,000 spent, an 8.3x return. Cost per MQL is about $2,700, which looks high until the deal size carries it. Run the same math on the no-booth RSAC play and on a curated program and the formats sort themselves out.

Then the part most teams skip. Measure actuals at nine months, not the Monday after the show when badge scans look like leads. Nine months is roughly one enterprise security sales cycle and the first honest moment to say what the event produced. Put the reminder on the calendar the day you sign. Compare spend, MQLs, SQLs, closed won, and revenue to the forecast. If the actual return is under 3x at nine months on a pipeline event, it is not paying. Renew it only if the goal is rewritten as visibility or credibility, out loud, with a smaller number attached.

What a good field marketer actually does

The role gets treated as logistics with a marketing budget. Ship the booth, order the carpet, count the scans. That is an event coordinator. A field marketer runs a pipeline program that happens to take place in a convention center, and the ones who do it well share four habits.

They vet like a buyer. Attendee list by title and company first, agenda second, brand names last. No list, no signature.

They forecast before they spend. Every event has a number before the contract, and the number is the argument for the budget and the yardstick at nine months.

They build the meeting machine around the event. The pre-registration list scrubbed six weeks out, BDR outreach three weeks out, ABM on the registered accounts, a dinner for the ten who matter, follow-up sequences loaded before the flight home. The booth is one part of the program and often the least productive part.

They run the floor like operations. Shipping tracked, services ordered before the late fees, staff briefed on the two questions that qualify a visitor, lead capture tested on setup day. Half strategist, half stage manager, and they know which half the moment calls for.

If you are hiring for the role, screen for the first two. Logistics can be taught. Judgment about where the money goes is harder.

The methodology, step by step

Pulling it together into the sequence I run for every event on a calendar.

1. Map the buying committee. Five seats, and for each one: where they go, what they read, what they want from a vendor conversation. Do this once a year, revisit when deals start stalling in a new place.

2. Diagnose the pipeline. Where are deals getting stuck, and which seat is the blocker? That tells you which seat this year's events need to reach. Events are a targeting problem before they are a logistics problem. Redo this when the average deal size doubles or the company moves upmarket, because the committee changed and the calendar did not.

3. Set one goal per event. Pipeline, visibility, credibility, channel, expansion, or one of the small ones. Write the metric next to it. If the goal is not pipeline, cap the spend and write the cap down too.

4. Set the date from the goal, not the calendar. When an event should happen depends on what it is for. If the goal is pipeline that closes in a particular quarter, count backward by the length of your sales cycle: a nine-month enterprise cycle means the event that feeds Q4 happens in Q1, and the show in October is feeding next year whether anyone admits it or not. If the goal is visibility, the event belongs in the four to six weeks before the thing you want people to notice, a launch, a raise, a category report. If the goal is credibility through speaking, the date is set by the call for papers, which closes six to nine months before the stage. If the goal is expansion, the owned customer event sits sixty to ninety days before renewal season. Two companies can go to the same show for the right reasons and the wrong reasons, and the difference is often only the month.

5. Score the event. Nine factors: audience fit, seniority, speaking slot, guaranteed meetings, competitor density, cost per ICP attendee, territory coverage, series pricing, timing. Book at 70, negotiate at 50 to 69, pass under 50 unless the organizer can move the number.

6. Choose the format. Booth, no-booth meetings program, curated executive program with contracted meetings, dinner, speaking submission, partner co-presence, walk the floor, or some combination. The format follows the seat and the goal, not the other way around. The default for a startup at a mega show is no booth and a full meeting calendar. The default for reaching economic buyers with budget is a curated program, not a conference. The default for credibility is a stage, planned a year out.

7. Forecast. Attendees, capture rate, qualification, MQL, SQL, closed won, deal size. Return on marketing spend before the contract, break-even leads written down.

8. Build the machine around the event. Pre-registration list vetted six weeks out. BDR outreach three weeks out. ABM display on registered accounts. Dinner invitations. Follow-up sequences loaded before the flight. This is where most of the return comes from, and it costs almost nothing.

9. Run the floor like operations. Deadlines, shipping, services, staff briefs, lead capture tested on setup day. A dossier per event, one workbook, ten tabs.

10. Measure at 30, 90, and 270 days. Meetings held and opportunities created at 30. SQLs and pipeline at 90. Closed won and the renewal decision at nine months. Compare to the forecast. Decide.

Success, defined

An event is successful when it did the one thing it was booked to do, at or below the cost it was forecast to take, with the committee seat it was meant to reach. A pipeline event that returned 5x is a success. A category event that produced three analyst inquiries and a keynote clip that sales uses for a year is a success. A booth that produced 400 scans and no meetings with anyone who can sign is not, no matter how good the photos were.

The methodology is not complicated, and it does not change from a $200,000 event budget to a $20 million one. It is a discipline about who, why, and how much, decided before the money moves, and checked after. The teams that run it stop arguing about events, because the events either paid or they were labeled honestly as something other than pipeline. Either way the renewal decision writes itself.

If you want the scoring, the forecast, and the stage-based mix done for you, the Event ROI Planner runs all three and exports the dossier with every date already on the calendar. If you want the buying-committee map built for your company and your pipeline, that is the work I do with clients.