Your Q3 Field Event Cost $184K and Sourced Six Sales Meetings

It is Tuesday, August 19th. Your CMO opens the SaaStr Annual recap deck on her second coffee. The wire out the door reads $184K: $62K on the 20x20 booth, $34K on the sponsorship tier, $28K on the dinner at Perry's, $18K on hotels for eight people, $22K on flights, $9K on shipping the booth and giveaways, $11K on the badge scanner rental and the pre-event ad boost. The scanner CSV holds 1,847 rows. The Salesforce campaign shows 41 tagged leads. The AE calendar shows six booked sales meetings. The board wants sourced pipeline against that $184K.

The CMO opens the exec channel and writes "SaaStr recap coming Friday, running the touch attribution now." The Friday recap never lands the number the board wants. The recap ships influenced pipeline, defined three different ways across three tabs of the sheet. The board opens the deck, scrolls to slide 4, and asks whether SaaStr belongs on the Q4 calendar.

The founders in this seat keep signing the next SaaStr contract and wondering why the same 1,847 scans keep converting to the same six meetings. Field marketing is not a booth. Field marketing is a five-stage queue that starts 45 days before the event and ends 90 days after, and nobody on the org chart owns it end to end. The queue has a shape, and an agent stack owns it.

The 1,847 scanned badges, by the numbers

Sort the scanner CSV. 214 duplicates from repeat booth visits. 340 rows with a personal Gmail address and no company field. 180 rows tagged "not a fit" by whoever was working the booth at 4 PM Wednesday. 47 rows are competitors, 34 are current customers, 62 are analysts and press, 88 are partners already in HubSpot. Strip the noise and the real target list is 882 net-new ICP-adjacent contacts.

Of those 882, the SDR team pulled 214 into Outreach in the two weeks after the event. Sequenced 189. Booked six meetings. The other 668 sat in a "post-event nurture" HubSpot list that nobody has opened since September 4th. Six months later the CMO runs the same recap format on the Dreamforce booth and lands the same six meetings against the same $184K.

The field marketing coordinator who owns the booth cost per meeting is not the person who owns the CRM enrichment. The sales development manager who owns the calendar bookings does not own the pre-event target account list. The RevOps analyst who owns the campaign hierarchy in Salesforce does not own the follow-up sequence library. Five owners across three teams, one queue, zero handoffs on cadence. The recap ships whatever number is left after the finger-pointing.

Stage one: the target account list nobody built in July

The Series B version of this event starts 45 days out with a target account list of 340 pre-registered attendees mapped against the ICP definition, 180 lookalikes from the closed-won book, and 80 penetration targets from Q2 CRO priorities. The 600-name target list ships to the AEs 21 days before the show with the two priority meetings pre-booked per rep and the pre-event email sequence approved by product marketing. Two AEs walk the aisle with a call sheet. Four AEs walk with a hunting license and a working list.

The version most Series B teams run: the field marketing coordinator asks for the attendee list on July 28th, the conference sends the raw CSV on August 3rd, the RevOps analyst is on vacation until August 10th, the enriched target list lands in the AE inbox on August 15th, three days before wheels up. Two AEs pre-book anything. The other four walk the booth cold and scan whoever stops for a shirt. The scanner works. The pipeline does not.

The stage-one function is queue-work on a fixed cadence. The agent reads the pre-registered attendee CSV, joins against ZoomInfo or Apollo for firmographics, joins against Salesforce for account tier and open opportunities, joins against the CRO's Q2 priority target list, ranks by ICP fit and account tier, and ships a prioritized meeting-worthy list of 340 names to the AE inbox 28 days before the event with the pre-drafted meeting-request emails already written. Sixteen hours of RevOps analyst time on the current path collapses to a nightly agent run and a 40-minute exception review. The AEs walk in with a plan.

Stage two: the on-floor scan queue

Wednesday 2:14 PM on the show floor. The field marketing coordinator watches the demo station. Two SEs work the demo queue. Four AEs work the aisle. One BDR runs the badge scanner. The BDR scans every badge that walks within four feet of the booth because the field team measures scan count, not scan quality.

The on-floor function scores every scan in real time against the target list from stage one, pings the working AE's phone the moment a tier-one target account swipes, and drops a Slack message into #field-live with the name, title, account, open pipeline, and the last product page they viewed. The 214-tool SaaS bill already has a badge scanner API. The function reads that API on a 30-second poll and routes the alert. The AE finishes the current conversation, walks four feet, and gets a warm handshake with a $340K in-flight account whose champion walked into the booth cold.

The stage-two function ships two things the current path never ships. It moves the conversion event from booth-scan to right-person-meeting on the show floor. It kills the "who was this person again" problem that guts every debrief on the flight home. The four AEs walk out of Wednesday with 22 qualified conversations logged in Salesforce with context, not 340 scanned badges dumped into a CSV. The recap reads differently on Friday.

Stage three: the 72-hour follow-up window

The buyer who scanned the booth Wednesday at 2:14 PM lands home Friday night. Opens the laptop Monday. If the follow-up email from the AE hits the inbox before 9 AM Monday with the specific product answer the buyer asked about at the booth, the meeting booking rate runs 14 to 22 percent. If the follow-up hits the following Wednesday with the generic "great meeting you at SaaStr" template, the booking rate runs 1 to 3 percent. Same buyer, same booth, different queue.

The current path: the scanner CSV drops to the RevOps analyst Friday night, the analyst runs the dedupe and the Salesforce upload Tuesday, the marketing ops manager builds the nurture list Wednesday, the SDR sequence launches Thursday. Nine days from scan to first touch. The buyer has already forgotten which of the 40 vendors at the show your booth was. The follow-up hits a cold inbox and dies.

The stage-three function reads the scan CSV every 90 minutes during the event, dedupes against Salesforce and HubSpot, joins against the target list from stage one, joins against the on-floor conversation notes from stage two, drafts a personalized follow-up email in the AE's voice with the specific product answer referenced, and drops the draft into the AE's Outreach queue with a suggested send time of Monday 8:14 AM local to the buyer. The AE reviews and hits send. The 72-hour follow-up window closes on 340 targeted emails, not 41 CRM-tagged leads and a generic nurture list. The meeting-booking rate holds in the 14 to 22 percent band.

The math against the next SaaStr contract

Run two paths against the $184K wire. Path A repeats the current SaaStr motion Q3 and books the same six meetings, sources one deal at $84K ACV, and calls it a wash for the fiscal year on a spreadsheet the board reads once. The sourced-pipeline number the CMO ships in October reads $84K against $184K spend. The board asks whether SaaStr belongs on the Q4 calendar. The field marketing coordinator opens the Dreamforce contract renewal Tuesday and does not know how to answer the CFO's follow-up email.

Path B ships a three-sprint fractional AI field marketing function at $84K to $132K in build across the first 90 days and $6K to $10K a month to run. The target account list function goes live 45 days before the next event. The on-floor scan routing function goes live at the next show. The 72-hour follow-up function goes live inside 14 days. The same $184K SaaStr spend, run through the three functions, moves the 1,847 scans through 340 personalized follow-ups on Monday morning, 22 booked conversations, and a working target list of 88 named accounts the AEs cover for the next two quarters.

The observed conversion range on this pattern across the Series B field-motion book: 6 to 14 sourced meetings on the flat show becomes 34 to 62 sourced meetings on the same booth cost, and the sourced-pipeline line the CMO ships in October reads $340K to $780K against the same $184K wire. Same P&L line, different recap. The three 14-day sprints that ship this function cost less than the dinner at Perry's.

The four numbers a CMO runs before the next event contract

The founders reading this signed a Dreamforce contract in April for the September show. Before the next wire goes out, run four numbers against the field function, not the booth spec. Score the queue, not the booth size.

Target list lead time. Measure the median days between the raw attendee list landing and the enriched prioritized list hitting the AE inbox. A healthy function runs under 21 days. A stuck function runs 3 days or lands after wheels up, and the AEs walk the aisle cold.

On-floor tier-one alert time. Measure the median seconds between a tier-one target account swiping the badge and the working AE getting a phone alert with context. A healthy function runs under 90 seconds. A stuck function runs never, and the AE finds out the account came by when the CSV lands Friday night.

Scan to first personalized touch. Measure the median hours between a booth scan and the first personalized follow-up email in the buyer's inbox. A healthy function runs under 60 hours. A stuck function runs 9 to 14 days, and the meeting-booking rate reads 1 to 3 percent.

Sourced meetings per $10K of event spend. Divide the sourced sales meetings tracked to the campaign by the total loaded event spend in units of $10K. A healthy function runs 2 to 4. A stuck function runs 0.3 to 0.7, and the board asks whether SaaStr belongs on the Q4 calendar. Any two numbers in the stuck zone means the queue is the problem, not the booth, and you can scope the field function in a 30-minute call this week.