Your Event Booth Scanned 340 Badges and Sales Followed Up on 22

It is Monday, September 8, 8:47 AM. Your CMO opens the badge-scan export from the Q3 industry summit. 340 unique badges captured across the four-day floor. The booth cost $84,000 in sponsorship, $22,000 in build and shipping, $18,000 in the pre-event dinner, and $34,000 in travel and hotel for the seven people on the roster. 22 personal follow-ups sent inside the seven-day window. Four warm demos booked. Two of them qualified opportunities. One in the CRO's Q4 forecast. 318 badges sitting in the CSV with nothing next to them but a job title and a partial phone number.

The scanner sync from the event vendor pushed 340 rows into HubSpot on the Friday of load-out. 84 rows landed with a duplicate contact ID against an existing account. 42 rows carry a competitor domain. 26 rows read as students or consultants against the ICP filter. 188 rows sit in the raw list with no owner, no sequence, no next step. The SDR team ran a bulk sequence on 96 of them on Tuesday morning against a generic post-event template. 4 replies. 2 unsubscribes. The AEs on the account list ran a personal note through Sales Navigator on the 22 badges that already had an opportunity open, and stopped.

Pull the trailing four field events. Count booth cost against sourced pipeline inside 90 days. Most Series B field programs run a 6x to 12x ratio in the operating plan and a 1.4x to 3x ratio in the actual numbers. Count badges captured against personal touches inside seven days. Most run 6 to 10 percent. Count sourced opportunities against booth spend and the payback window sits north of nine months on three events in four. Field is not a sponsorship problem. Field is a queue.

The 340 badges nobody staffed

Walk the queue. 22 badges had an existing open opportunity in the CRM and the AE ran the follow-up personally inside 48 hours. 96 badges hit the bulk post-event sequence Tuesday morning. 84 duplicates sit in a merge queue the RevOps analyst opens on the fifteenth. 42 competitor domains sit in a suppression list nobody reviewed. 26 non-ICP rows sit in the raw list flagged for exclusion the analyst never applied. 70 badges sit as fresh ICP contacts with no owner, no scoring pass, no sequence. Median days from scan to first personal touch reads 11.4. Median days from scan to CRM merge reads 27.

The team that should own this knows the shape. The demand gen lead built the pre-event target list against a scraped attendee roster and booked 34 booth meetings. Fourteen showed up. The field marketing manager ran the booth staffing rotation and the pre-event dinner invite list. The two SDRs on the field program worked the fourteen booth meetings inside 72 hours. The four AEs on the enterprise book worked the 22 badges that had an existing account, and let the rest fall to the bulk sequence. The RevOps analyst runs the CRM merge every other Friday against a report that already has 84 duplicates queued from the last event.

Five seats touch the queue and none of them own it end to end. The Q1 event ran a similar shape. 280 badges captured, 18 personal follow-ups, three warm demos, one closed-won opportunity worth $180K in first-year ACV against a $124,000 all-in event cost. The board deck last quarter listed field as a 1.9x pipeline ratio against a plan of 8x, and the CMO carried the slide without a fix.

Hiring a Field Ops lead is the slow answer

The textbook fix is a Field Marketing Operations Manager, a second SDR pod on the field program, or a Senior Manager of Event Marketing. Loaded comp in the US runs $140K to $190K a year for the field ops manager, $180K to $260K for the senior event lead, plus $2,400 monthly on the badge-scan platform expansion and $1,800 monthly on the sales engagement seat pack. Months one through three go to rebuilding the event playbook, cleaning the scanner-to-CRM sync, and refreshing the post-event sequence library against the four ICP segments. Months four through nine are when personal follow-up coverage moves from 6 percent to 42, median days from scan to first touch drops from 11.4 to 1, and sourced-pipeline ratio on the trailing four events lifts from 1.9x to 5x.

The fractional version buys 12 to 16 hours a week of senior field operations work at $7K to $14K a month. The first month refreshes the pre-event target list build and the post-event sequence library. The 340-badge queue keeps drifting because a fractional lead cannot personally research every ICP badge inside 24 hours of load-out, draft a per-badge outreach note against the session attendance and the booth conversation notes, merge the 84 duplicates against the account structure the same day the scan lands, score the 70 no-owner badges against the ICP model and route them by territory, and follow the four warm demos into a booked call inside seven days.

Both versions assume the work is a person opening a CSV on a cadence. The work is enriching every badge inside four hours of scanner sync against LinkedIn, Clearbit, and the CRM account structure, drafting a per-badge outreach note against the booth conversation log the staffer typed on the scanner tablet, merging the 84 duplicates against the master account map the same afternoon, running the ICP scoring pass and routing 70 fresh contacts to the right AE or SDR by territory, and following the four warm demos into a booked call inside seven days with a briefing pack in the AE inbox. On a 340-badge event scan that is 60 to 90 hours of senior field operations work compressed into the seven-day window where the buyer still remembers the booth. No single hire clears the pile inside the window and staffs the next event at the same time.

What a fractional AI field function owns

Hand the badge-scan export, the booth conversation log, the session attendance feed from the event vendor, the pre-event target list, the CRM account map, the enrichment stack, the four ICP segment definitions, and the post-event sequence library to a fractional AI agent. The agent does the work a Field Ops Manager, a Senior Event Marketing lead, and a post-event SDR pod would do together. The cadence is per-scan on enrichment, per-badge on the outreach draft, per-duplicate on the merge, per-territory on the routing, per-warm-demo on the booked-call follow.

Every badge enriched inside four hours of scanner sync. The Friday load-out pushes 340 rows into HubSpot at 2:14 PM. By 6:00 PM the queue joins each row against LinkedIn, Clearbit, and the CRM account structure, tags the ICP segment against the four segment definitions, pulls the last two funding rounds and the current tech stack against BuiltWith, flags the 42 competitor domains into suppression, and lands 188 no-owner badges in a scored list with an owner suggestion by territory.

Every badge gets a per-scan outreach draft. The booth staffer typed a two-line note on the tablet for 214 of the 340 scans, covering the product the badge asked about, the size of the account, and whether the conversation warranted a follow-up. By Sunday at 6:00 PM the queue drafts a personal outreach note per badge against the booth log, the ICP segment, and the trailing three months of the account's news and job posts. The two SDRs on the field program read the drafts and send inside 24 hours instead of running a bulk sequence against a generic template.

Every duplicate merges the same afternoon. The 84 duplicates land in a merge queue with the account and contact match evidence, the confidence score, and the suggested surviving record. The RevOps analyst approves the merge queue in 30 minutes Monday morning instead of opening the report on the fifteenth against a two-event backlog.

Every fresh ICP badge routes by territory. The 70 no-owner badges score against the ICP model, get an AE or SDR assignment against the territory book, land inside the CRM with an owner and a first-task due date inside seven days, and fire a Slack ping to the owner with the enriched profile and the booth conversation note. The four AEs on the enterprise book see fresh field pipeline in their queue Monday morning instead of hearing about it on the QBR three weeks later.

Every warm demo books inside seven days. The four warm demos identified in the booth log land in the AE calendar with a briefing pack covering the booth conversation, the account's news and hiring signals, the two comparable closed-won deals from the trailing four quarters, and the three questions the AE should open the call with. The buyer walks into the demo remembering the booth conversation instead of a form-fill from a month ago.

The unit economics of a $158,000 booth

A Series B company at $30M ARR running a 340-badge event queue against a five-person cross-functional bench is burning three specific things. The demand gen lead, the field marketing manager, the two SDRs, the four AEs, and the RevOps analyst spend a combined 40 to 70 hours in the seven days after load-out on triage, merges, bulk-sequence QA, and Slack chases against a fully loaded hour of $160 to $260. That is $6K to $18K of senior time on one event on work a live routing engine clears. Read the case studies for the shape of that trade on a similar bench.

The sourced-pipeline line is the second one. The Q3 summit cost $158,000 all in and sourced $300,000 in pipeline against a plan of $1.2M. Moving personal follow-up coverage from 6 percent to 42 across the trailing four events compounds against the same $158K spend on 60 to 100 booth-eligible ICP badges per event and a 22 to 34 percent meeting-to-opportunity conversion rate. Two ICP badges out of the 188 no-owner block from the Q1 event surfaced as inbound demos in July after a competitor renewal cycle. Neither of them remembered the booth. Both of them named the competitor.

The window line is the third one. A buyer who remembers the booth conversation converts on a meeting request inside seven days at two to four times the rate of the same buyer contacted on day 30 through a generic sequence. Every day past seven collapses the memory window and pushes the badge into the same cold funnel the SDR team already runs against a purchased list. A 14-day sprint to stand up the field agent runs in the low to mid five figures. Ongoing cost lands closer to two badge-scan seats than a Field Ops Manager hire. The enrichment and the per-badge outreach draft ship in week one. The duplicate merge and the territory routing land off a live feed in week two. The warm-demo booking loop closes before the sprint hands off.

What changes after the sprint

Picture the same Monday, 8:47 AM moment, thirty days after the sprint ships. The CMO is not scrolling a badge-scan CSV. The 340 rows enriched by Friday at 6:00 PM. The 214 booth-log badges shipped a personal outreach note in the SDRs' outboxes by Sunday night. The 84 duplicates merged Monday morning. The 70 fresh ICP contacts sit in the four AEs' queues with a first-task due date inside seven days. Four warm demos booked. Two qualified opportunities in the CRO's forecast by day fourteen.

By Monday the digest reads 340 badges, zero past the four-hour enrichment SLA, 96 personal outreach notes sent inside seven days, 22 warm demos booked against the four ICP segments, and one merged account list ready for the RevOps analyst to approve in 30 minutes. The two SDRs on the field program spend Monday working the six replies from the per-badge outreach instead of QAing a bulk sequence. The four AEs walk into their warm demos with a briefing pack instead of a badge photo.

If your last event captured 340 badges, shipped 22 personal follow-ups, and booked four warm demos against $158,000 in booth spend, the version where every badge enriches in four hours and every warm demo books inside seven days is fourteen days away. Field is a function. You can hire against it, retain a fractional field ops partner for it, or you can scope a sprint and have it running before the next event. The 340 badges are already in the queue. The math is whether the SDRs ship 96 personal notes this week or read about the payback window in November.