60-Min Sales Training: Networking Events + Conferences

The Monday before SaaStr, and the $4,200 problem

A four-person team is flying to a two-day conference in nine days. Between airfare, hotel at conference rates, the ticket, ground transport, and meals, the fully loaded cost per rep lands in the low-to-mid four figures — call it $3,500 to $5,000 for a domestic North American event, more if the ticket is a premium pass or the venue is in a high-cost city. Four reps means the team is spending roughly the equivalent of a mid-market annual contract to be in a room for two days.

Ask the manager what came back from the last event and the answer is usually a spreadsheet with 180 scanned badges, a handful of "great meeting you" emails sent the Sunday after everyone got home, and one or two meetings that would probably have happened anyway because the account was already in cycle. Nobody can name which conversation produced which meeting. Nobody wrote down what the buyer actually said. The badge scans became a list, the list became a bulk upload, and the bulk upload became a sequence that got the same open rates as cold outbound — because functionally, that's what it is.

That is the specific failure this training targets. It is not a motivation problem and it is not a charisma problem. Reps who are excellent on Zoom go quiet at a booth because the environment removes every scaffold they normally lean on: no calendar invite framing the conversation, no agenda, no screen share, no discovery call structure, no CRM record open in another tab. A conference floor is 45 seconds of unstructured human contact with someone who is trying to get to a session, and most reps have never practiced that specific 45 seconds even once out loud.

The session runs 60 minutes on the Monday of the week before travel — early enough that reps still have four business days to do the pre-work, late enough that the event is real to them. Sixty minutes is the whole budget. You are not teaching everything about field marketing; you are installing four behaviors and one accountability metric. Anything that doesn't move one of those four behaviors gets cut.

Structure the hour like this: five minutes of setup, fifteen minutes teaching the loop, fifteen minutes on verbatim scripts, fifteen minutes of role-play, five minutes on failure modes, five minutes on action items and the metric. The role-play block is non-negotiable. Every manager who runs this session is tempted to trade the drills for more teaching, and every team that does that gets a room full of people who understood the framework and cannot execute it under social pressure. Understanding a script and being able to deliver it to a stranger holding a coffee are different skills.

Open with a ninety-second warm-up that costs you nothing and buys honesty: every rep says one sentence about the worst event they ever worked and what they personally did wrong. No coaching, no reactions, just around the table. You will hear "I scanned a hundred badges and followed up with none of them" and "I stood at the booth with my own team for two hours" and "I got into it at the reception and was useless on day two." That surfaced scar tissue is the curriculum. Write the three most common ones on the board and tell the team the next 55 minutes exist to close exactly those.

PREP, INTRO, SCAN, SHIP — the four phases and where teams actually break

Write four words on the whiteboard and teach each one as a phase with a hard entry condition. The framework is deliberately small because a rep on a conference floor with three drinks of social fatigue can hold four things in working memory, not eleven.

PREP runs seven days out. Before travel is finalized, the rep pulls the attendee or exhibitor list from the event app or the sponsor portal — most large B2B conferences publish a searchable attendee directory in the app once check-in opens, and sponsor packages often include a pre-event list. From that list the rep flags twelve named accounts. Twelve, not fifty. For each one they open LinkedIn and find one specific, recent signal: a promotion inside the last quarter, a funding announcement, a new VP of Sales, a public post about a tooling migration, a hiring spree for RevOps roles. That signal gets written into a shared doc in one sentence. The manager reads all twelve before the rep flies. The entry condition is blunt and it works: no flagged-twelve list reviewed by Friday, no travel approval. Teams that skip this step are running the event as a lottery and their results look like lottery results — high variance, no repeatability, nothing to coach.

Twelve is the right number for a reason. At a two-day event a rep can realistically have eight to fifteen substantive conversations, because each real conversation runs six to twelve minutes and the floor is only open a few hours a day around sessions. A fifty-name list guarantees the rep never actually looks for anyone; a twelve-name list is memorizable, which means the rep recognizes a target's name on a badge across a room. That recognition moment is the entire point of PREP.

INTRO is thirty seconds and exactly three sentences: who you are, who you help, the specific pain you remove. Then a question that hands the floor back. No company founding story, no product name in the first breath, no "we're a platform that." The rep rehearses this out loud roughly twenty times before travel, ideally recorded, because the goal is for it to sound unrehearsed — and the only path to unrehearsed is over-rehearsed.

SCAN happens in the five minutes after every badge scan. The rep records a thirty-second voice memo with three fields: who this was, what signal or pain they named, what the next step is. Every major lead-retrieval app supports notes on a scan, and the phone's own voice recorder works fine. The reason the memo has to happen inside five minutes rather than at the end of the day is that the specific detail — the espresso bar, the exact number they quoted, the name of the tool they hate — is what makes the follow-up email land. Batch-processing at 9pm produces "spoke to him, seemed interested," which is worth nothing on Monday.

SHIP means the follow-up email goes out within 24 hours of the scan. Not 24 hours after the conference ends. Someone you met Wednesday morning gets an email Wednesday night from the hotel room. The subject line references the specific conversation, the body is three sentences, and the ask is a twenty-minute meeting with two named time slots.

Pause the teach here and ask the room one question: which of the four phases does this team currently skip? In almost every session the answer is PREP and SHIP. Teams are fine at showing up and fine at talking. They are bad at deciding who to talk to in advance and bad at converting the conversation within the decay window. Write those two on the board and tell the team that the role-plays and the action items both target those two phases specifically.

The scripts reps memorize, then make sound human

Hand out a single index card with four blocks on it. Reps memorize the shapes, not the words — but they memorize the words first, because you cannot improvise a structure you have never executed.

The thirty-second intro, booth or session line: "Hi, I'm Sarah. I work with RevOps leaders at Series B and Series C SaaS companies whose forecast accuracy fell apart after their team stitched three pipeline tools together and started double-counting opportunities. Most of them are burning a day or two a week reconciling numbers by hand. What brought you here?"

Notice what that does. Sentence one is a name. Sentence two is a persona narrow enough that the listener instantly knows whether it is them. Sentence three is an operational pain described in the buyer's own vocabulary — hours lost, not features missing. Then a question, which returns the floor before the listener feels pitched. The vendor name never appears. If they're a fit, they'll ask what you do; if they're not, you've spent twenty-five seconds instead of six minutes.

The qualifier, two questions, asked after they answer: "When you say the forecast is off — are we talking five percent or twenty-five? And is that showing up in board meetings yet, or is it still internal?" The first question calibrates magnitude, the second calibrates urgency. Conference floors are dense with polite, curious, entirely non-urgent people, and the only way to distinguish a real opportunity from friendly interest is to ask about consequences. A director who says "it's twenty percent off and the CFO asked about it last month" is a different lead from one who says "eh, it's maybe five and nobody's noticed."

The exit, three variants. For a fit: "I'd love to keep this going. Can I scan your badge and send you twenty minutes Tuesday or Thursday?" For a non-fit with a network: "This isn't quite my lane, but I work with people it is exactly right for — mind if I scan you and send an intro Monday?" For a non-fit with nothing: "Appreciate the chat, enjoy the rest of it." Then leave. Four minutes is the hard ceiling on a non-fit conversation. At a two-thousand-person event, every extra minute with someone who will never buy is a minute stolen from someone who might.

The follow-up email, three sentences. Subject line names the specific thing discussed and the event. Body: reference the exact detail from the voice memo, name a comparable customer and the outcome in one clause, then offer two specific slots. No attachment, no deck, no "just following up." Something like: *"Great talking by the coffee line Wednesday — you mentioned your team is burning two days a week reconciling pipeline across tools and your CFO is asking why forecast accuracy slipped. We rebuilt exactly that workflow for a company at similar ARR and they're back inside their forecast band. Tuesday 2pm ET or Thursday 10am ET for twenty minutes? I'll bring the workflow, not a deck."*

The specificity is the whole mechanism. A generic post-event email is indistinguishable from cold outbound, and buyers treat it that way. An email that quotes the buyer back to themselves proves a human was present and paying attention, which is the only advantage in-person attendance actually confers. If the rep can't write that email, it means the voice memo never happened, which means SCAN broke — and you can trace every weak follow-up back to a missing memo.

Spend the last few minutes of this block having each rep read their own intro out loud once. Not a discussion — a read. You will immediately hear which ones lead with the product, which ones run past four sentences, and which ones end with a statement instead of a question. Red-pen those three failure shapes on the spot.

Numbers worth tracking, and the ones worth ignoring

Set targets in the room so the metric exists before the event rather than being invented afterward to justify the trip.

Scans per day: cap at 20. This is a ceiling, not a floor, and reps find it counterintuitive because scan count is the one number the booth staff can see going up in real time. A rep who scans eighty badges in a day did not have eighty conversations; they had eighty transactions. Twenty scans is roughly the number a person can follow up on individually within the decay window while also attending sessions and eating. Above that, follow-up quality collapses into templated bulk, and bulk post-event email is the single most reliable way to convert an expensive trip into nothing.

Substantive conversations per day: 8 to 15. Count only conversations where you learned something specific — a number, a tool name, a timeline, a person's actual problem. This is the number that predicts pipeline. Track it in the voice memos, not in a spreadsheet.

Meetings booked per rep per two-day event: target 5. For most teams the honest starting baseline is one or two, which is exactly why the trip looks unprofitable. Five is reachable specifically because of PREP: if twelve accounts were flagged and the rep found six of them on the floor, booking five is a matter of qualification discipline rather than luck. Under three triggers a Tuesday-morning coaching session, not a performance conversation — the goal is to diagnose which phase broke.

Follow-up latency: hours from scan to first email, measured per lead. This is the single most diagnostic number in the whole system because it is objective, it is timestamped, and it correlates with everything downstream. A team whose median latency is 18 hours is running the system. A team whose median is 96 hours is doing the old thing with a new vocabulary.

Ignore these: total badge scans, booth traffic, swag distributed, session attendance, and social impressions. Every one of them is an activity metric that a rep can maximize without generating a single conversation worth having, and every one of them will be in the post-event recap deck if you let it. The team's recap should have four numbers: scans, substantive conversations, meetings booked, and median follow-up latency.

On cost accounting: build a simple per-event model before you fly. Fully loaded cost per rep divided by meetings booked gives cost per meeting, and comparing that against your blended cost per meeting from outbound is the only honest way to decide whether the next conference is worth attending. If outbound produces meetings at a fraction of the cost, the event has to justify itself on something else — brand, customer retention, partner conversations, competitive intelligence — and you should say that out loud rather than pretending the pipeline math works.

One more measurement note: tag every event-sourced opportunity in the CRM with the event name at creation, not retroactively. Retroactive attribution after a deal closes is how events get credit for pipeline they didn't create and how genuinely productive events get no credit at all because nobody remembered to tag them. Make the lead source field required on any record created during event week.

Drills, and what to run instead when the hour isn't there

Fifteen minutes buys three drills at five minutes each, with a ninety-second debrief and a partner swap between them. Pair the team, half as reps and half as buyers, and swap roles between rounds so everyone plays both sides. Playing the buyer is underrated as a teaching tool — reps discover how a product-first opener feels from the receiving end faster than any amount of coaching can tell them.

Drill one, the drive-by. The buyer is walking past the booth toward a session and has about 45 seconds. The rep delivers the intro and either books or releases. Score three things: did they lead with persona and pain instead of product, did they end on a question, did they release a non-fit inside a minute?

Drill two, the coffee line. The buyer is a director at a company that matches the ICP, has a real but non-urgent problem, and is shopping casually. The rep runs the full intro, qualifier, and exit. Score: did they ask about magnitude *and* urgency, did they reference a comparable customer, did they propose two specific time slots rather than "let's connect"?

Drill three, the reception. The buyer is friendly, a few drinks in, talkative, and clearly not a fit — wrong function entirely. The rep must recognize the mismatch, exit warmly inside four minutes, and ask for one warm introduction. This is the drill everyone finds hardest and the one that recovers the most floor time.

Score one to five on five lines: opened with persona and pain, returned the floor with a question inside thirty seconds, calibrated both magnitude and urgency, released non-fits under four minutes, closed with specific slots. Anything under a three gets a fifteen-minute one-on-one before travel.

The trade-offs worth naming out loud. Twelve targets versus working the whole floor: a target list means you will walk past interesting strangers, and that is a real cost — some of the best conversations at any conference are unplanned. The list is a floor, not a ceiling; hit your twelve, then wander. Twenty scans versus maximum volume: if your motion is genuinely high-velocity and transactional with a short cycle, higher scan volume with a lighter templated follow-up may genuinely outperform. Know which motion you're running before you adopt the cap. Sixty minutes of live training versus async: live is better because the drills need bodies, but a distributed team can run a recorded teach plus submitted intro recordings plus a fifteen-minute live drill block, and that captures most of the value. Conferences versus small dinners: for enterprise motions, hosting a twelve-person dinner adjacent to a conference often outperforms the conference floor per dollar. If your data says that, run the same PREP-INTRO-SCAN-SHIP loop on the dinner guest list and skip the booth.

Virtual events change the tactics but not the loop. PREP is identical. INTRO becomes a written chat message with the same three-sentence structure. SCAN becomes a note logged the moment the session ends. SHIP compresses to same-day, because attention decays faster online. The failure modes are the same failure modes.

Where this falls apart, and the recovery line for each

The product monologue. The rep opens with "so we're a unified platform that uses AI to..." and watches the listener's eyes go to the exit. Recovery, said out loud and without embarrassment: "Sorry — let me start over. What brought you here?" Interrupting yourself to hand back the floor reads as confidence, not fumbling, and it salvages a conversation that was otherwise finished at second twelve.

The twelve-minute non-fit. Sunk cost is powerful and conference conversations are pleasant. Recovery: at the four-minute mark, "I want to be respectful of your time here — let me scan you and follow up properly." Then walk. The rep who does this six times a day recovers most of an hour of floor time, which is roughly two more real conversations.

Scanning everything, following up with almost nothing. This is the most common failure by a wide margin and it is a planning failure, not a discipline failure — the rep scanned 80 badges because nobody gave them a cap or a target list, and then physically could not write 80 personal emails. Recovery: the 20/day cap plus the five-minute voice memo. If there's no memo, don't scan.

The Sunday-night bulk send. Forty people get "great meeting you at the event," nobody replies, and the rep concludes that conferences don't work. Recovery: the email goes out within 24 hours of *the scan*. Wednesday morning's conversation gets Wednesday night's email, from the hotel. Block thirty minutes each evening of the event specifically for this and put it on the calendar before you fly.

The reception. Two drinks is the ceiling, and that ceiling exists because day-two and day-three performance is where the differentiated pipeline actually gets built — the field thins out considerably by the last afternoon, and the rep who is sharp then has near-exclusive access to the people still working.

Booth huddling. Reps stand with their own colleagues because it's comfortable, and a group of three teammates is functionally a closed door to anyone walking by. Rule: never more than one person from your company in a conversation with a prospect, and if two teammates end up talking to each other for more than a minute, one of them leaves.

No manager review of the target lists. Without the Friday check, the flagged-twelve becomes a compliance artifact filled in at 11:58 with whatever names were nearest. The review takes about ten minutes per rep and it's where the manager catches the two accounts that are actually worth a dinner.

The debrief that never happens. Everyone gets back, catches up on email, and the event dissolves. Put the day-plus-seven debrief on the calendar before you fly: four numbers, one thing to keep, one thing to change. Without it, the next event is run on vibes again and the whole Networking system decays inside two cycles.

Related questions

How far in advance should we run this session?

The Monday of the week before travel. That gives four business days for the flagged-twelve list, the manager review, and the intro rehearsal, while keeping the event close enough that reps take the pre-work seriously. Two weeks out and the homework slips.

What if a rep can't find twelve target accounts at the event?

Then the event probably isn't right for that rep's territory, and that's useful information. Six strong targets beat twelve forced ones — but a rep who can only find three should likely skip this event and put the budget into a different channel.

Should SDRs and AEs attend the same training?

Yes, same session, same scripts. The qualifier and the exit are identical; only the follow-up ask differs — SDRs book for someone else's calendar, AEs book for their own. Running one session keeps the handoff language consistent.

Does this work for a first-time exhibitor with no attendee list?

Partly. Without a list, PREP shifts to researching the speaker roster and sponsor logos, which are always public. You lose the recognition advantage, so raise the conversation target and lean harder on SHIP discipline to compensate.

How do we handle leads that go to a teammate's territory?

Scan, memo, and hand off within 24 hours with the memo attached. The receiving rep sends the follow-up referencing the original conversation by name. Latency matters more than ownership cleanliness — never let a routing question delay the email.

FAQ

How long does the training actually take to implement end to end?

The session itself is 60 minutes, but budget about 90 minutes of total rep time per event cycle: the hour of training, roughly twenty minutes building the flagged-twelve list, and ten minutes recording the intro rehearsal. Managers spend an additional ten minutes per rep reviewing lists. Most teams need two or three event cycles before the behaviors run without prompting — the first event usually improves follow-up latency, and the second is where meeting counts move.

Do reps need to be experienced for this to work?

No, and junior reps often improve fastest. The training installs repeatable behaviors — a memorized three-sentence intro, a target list, a voice memo, a 24-hour email — rather than teaching charisma. Experienced reps sometimes resist the scripts because they've been improvising for years; the honest counter is that improvisation is why nobody can explain last quarter's event results.

What if our team attends three or four events a quarter?

The system scales well because the framework is constant and only the target list changes. Run the full 60-minute session once, then run a 15-minute refresh before each subsequent event that covers only the flagged-twelve list and the follow-up block. High-frequency teams see the largest cumulative return because the intro gets genuinely polished through repetition rather than being rebuilt each time.

How do we know the training worked rather than the event being good?

Compare median follow-up latency and meetings-per-rep against your last comparable event, and check whether every event-sourced opportunity has a lead source tag. Latency is the cleanest signal because it's fully within the rep's control and unaffected by whether the conference happened to attract good accounts. If latency dropped and meetings didn't, the problem is in qualification, not follow-up.

Does any of this apply to virtual conferences?

Yes, with adjustments. PREP is unchanged. The intro becomes a written message in chat or DM using the same three-sentence structure. There is no badge to scan, so the memo is a note logged immediately after each session. SHIP compresses to same-day because online attention decays faster than in-person memory. The underlying loop — targeted pre-work, structured opener, immediate capture, fast follow-up — is identical.

Our team is already good at Conferences. Is this worth an hour?

Run the diagnostic before deciding: pull your last event's data and calculate median hours from scan to first email, and the percentage of scanned leads that got a personalized message. Teams who consider themselves strong are usually strong at the conversation and weak at the two phases nobody watches — pre-event targeting and post-event latency. If your median latency is already under 24 hours and every lead got a personal email, skip the session.

Sources

• RAIN Group — sales training and research library
• The Bridge Group — SDR and inside sales metrics research
• Cvent — event marketing and lead capture resources
• HubSpot — sales blog and event marketing guides
• Gartner — sales and CSO conference programming
• Pavilion — GTM community programming and events
• Harvard Business Review — sales and business development research
• LinkedIn Sales Blog — B2B selling research and practice

Related on PULSE

• [60-Min Sales Training: Timing Conversations + Compelling Events](/knowledge/st0448)
• [Prospecting on LinkedIn: Interactive Template for a 20-Minute Sales Session](/knowledge/st0795)
• [Sales Forecasting Accuracy: Template for a Team Meeting Focused on Data Hygiene](/knowledge/st0796)
• [Selling with Stories: Narrative Structure Template for a 45-Minute Sales Workshop](/knowledge/st0792)
• [Building a Sales Mentorship Program: Template for a Department-Wide Kickoff](/knowledge/st0790)
• [Sales Demo Best Practices: Agenda and Script for a Peer-Led Training Workshop](/knowledge/st0788)