WFI Group Senior SDR & Marketing Ops Jun 2024 – ongoing
clayconferencephantumbusterlinkedin

Walking the Floor Is Not a Go-To-Market Plan

Most teams spend $10,000 to send one rep, then let them wing it on the floor. Here's the system I run instead.

Walking the Floor Is Not a Go-To-Market Plan cover
1,227
leads scored
30
target counties
2-3 day
roadshow plan

Let’s do quick math.

You send your best AE to a conference in the USA. Round-trip flight from Tel Aviv, hotel, the pass, meals, and a week of a senior rep’s time off everything else they could be doing. Add it up, and you are at roughly $10,000 for one person at one conference.

Now divide that by what they bring home. Fifteen business cards that actually fit your ICP. Ten thousand dollars, fifteen conversations. You just paid about $700 a meeting.

And how many of those fifteen turn into real pipeline? On a good day, maybe one. So here is what you actually bought: $10,000, plus four days your best rep could have spent on the pipeline he already has, for a single opportunity.

That is the line nobody puts on the expense report.

The conference is not the strategy

A conference is not a strategy. It is a room. A very expensive room, packed with the buyers you chase all year. You paid for the hard part, getting them into one building. Then you skipped the easy part: deciding who your rep meets before he walks in.

So he improvises. Works the floor, collects cards, hopes. Hope converts at one in fifteen.

Now run the same trip the other way. Same $10,000, same four days, except your rep lands with a full calendar. Twenty to thirty meetings, every one pre-qualified, every one already a “yes.” The cost did not move. The output did: eight or ten opportunities instead of one, and four days spent in real meetings instead of trawling a carpet for cards.

Same room, same money. The only variable is whether the meetings existed before takeoff. And if they don’t is it still worth sending him to the conference?

So how do you fill that calendar?

The four moves

Most technical guides fail one of two ways. Too philosophical, and I finish the page with no idea what to actually do. Too technical, and I can see every step but not how it fits me. I want both: the why and the how. So here is the thinking.

1. Source intent. Conferences leave a trail on LinkedIn. People announce they are going. They like the conference page. They comment on the agenda. Every one of those actions is a buyer raising their hand. You collect the hands.

2. Qualify cheap, before you spend. Most of that list is noise. Before you pay to enrich anyone, run a fast, cheap pass on what you already have, the name and the title, and drop everyone who is clearly not your buyer. You filter first, then you pay.

3. Enrich, then qualify again on the company. Now you spend. Pull the location, the company, the role. The first gate was about the person. The second gate is about the company. A perfect title at the wrong company is still a no.

4. Score, sequence, hand off. Whoever survives gets a score. The score decides two things: who your rep meets first, and who gets a personal LinkedIn touch before the event. The list flows into one short sequence, and the top names go straight to your AE.

The actual build

Now let me walk you how i build such a thing for every conference WFI is attending

What you need:

  • A source list: last year’s attendees, or PhantomBuster - LinkedIn scraper
  • A Clay table, for scoring and enrichment
  • Your sequencer1

Step 1. Scrape the intent. Point PhantomBuster at the conference post2 ,pull everyone who posted, liked, or commented. This is your raw list.

For the ACE conference i used to phantoms that ran simltinesly, one was targeting old post, and one that was targeting new posts.

Scraping the conference post

First AI qualification pass

Step 3. Enrich the survivors. Now pull the real data. Location, company, company type, current role. You are only paying for the people who passed step 2. Filiter first base on hared fact locitione for example, and only then pass to an AI qulfeciton, if your icp demeds that you will fliter base on cumpeny filiter base on this, then i like to add an ai qulficitione

Enriching the qualified list

Step 4. Second qualification, on the company. Add a second check. Is this the kind of company we want to meet, in a place we can reach. A great person at the wrong company drops out here.

Second qualification on company fit

Step 5. Score. Give every survivor a score. When the list is long, the score also tells you who to enrich first, so you spend credits on the best names before the budget runs out. this is one step, i want to explaine what to do and that they need to make it fit for there ICP, but that it all in one step, my qulfcaition and squring is base on my knowledge of my ICP and how can i save on credits in Clay

Scoring the final list

Step 6. Push to the sequence. Send the scored list into your sequencer. I use QuickMail.

Pushing to the sequencer

Here is the whole thing in one picture:

flowchart LR
    A[Scrape conference posts] --> B[Cheap AI qualify on title]
    B -->|keep the yes| C[Enrich: location, company, role]
    C --> D[Second qualify on company fit]
    D --> E[Score]
    E --> F[Push to 3-step sequence]
    E --> G[Top names to AE for LinkedIn touch]

The sequence: three touches, one goal

Every ICP has the type of email that workes for him so i will give my framework not templetes and the logic bhinde them

Email 1 -

The goal of the sequence is not to book a meeting. It is to get a reply. there were times that my sequance was just Subject line: {{confrance name}}? Body: are you attending {{confrance name}} this year? Once they reply, you send the link.

the subject line name of the confrince? to increse the chancen only pepel etha are gooing to the confrance will open it

then if i have a prisonalizition line base on specfic post i would use it or they were last year, but i rilized i dont need it

and then a qustione about if the are gooing to be

Protip: one of the things that i noticed is that as you get closer to the confrince, you will get more emails OOO this is somthing your AE needs to know about, they are probobly gooing to be in the confrance he needs there faces.

Email 2 -

15 min later after the firs email Shoret intrductione abou or a link to somthing in out website that is tie to the confrance and the icp i am after

Email 3 - 5 days later

a short email if anybody else from his team is gooing to show up

if they reply i will reserch the cumpeny for all relvent icp and pushe them into the campigen

Three messages. Reply-based. No calendar link until they raise their hand.

I once ran a campigen that after qulfing the lead i will find his diricet manger and add them as cc to the last email

Timing: three waves

You do not run this once. You run it in three waves, tied to the calendar.

Wave 1, six to eight weeks out. Go after last year’s attendees, the people you can still find from the previous event. They have the highest intent, because they already chose to attend once.

Wave 2, two to three weeks out. Go after this year’s announcers, the people posting that they will be there.

Wave 3, continuous. As new posts come in, they flow through the same machine on their own. Scrape, qualify, score, sequence. You built it once, and it keeps feeding itself.

Wave 4, optioneal: after the confrance if they want to jump on a call

A side benefit: you find out if the conference is even worth it

Run the scrape before you commit the budget. Count how many of the people actually attending fit your ICP. Not the attendance number the conference puts in its brochure, the real list, by title and company.

Sometimes the answer is uncomfortable. The conference looks relevant, the logos look right, but the people who actually show up are not your buyers. Better to learn that from a Clay table than from a $10,000 trip.

A second side benefit: your AE walks in knowing the room

Before the flight, hand your AE the top of the scored list with names and photos. Three hundred faces, ranked. Now your rep does not just have meetings on the calendar. He can recognize the people he most wants to meet when he passes them in a hallway, and open with “I think we are supposed to meet on Wednesday.”

The point

The conference is a venue, not a strategy. The teams that win did not win on the floor. They won in the three weeks before, when they decided exactly who was worth a seat on a senior rep’s calendar.

You are already paying for the room. Fill it before you land.

The build above is mine, in Clay. The logic underneath it is yours to take. Swap the tools, keep the order, and run it for any conference, in any industry, the next time someone books a flight.

Footnotes

  1. I am using QuickMail

  2. You can use Clay for this step to, but it will run you throgh a lot of credits

  3. I used GPT 4.1 Mini 0.2 credits, with this prompt: You are screening LinkedIn profiles for relevance to Water From Innovation (WFI), which sells decentralized wastewater treatment and water contaminant-removal systems to municipalities, water and wastewater utilities, public works, industrial facilities, and the engineering and consulting firms that serve them.

    You will see one person’s name and LinkedIn headline. Decide if they are clearly NOT relevant.

    Could be relevant (KEEP): water, wastewater, utilities, municipal, public works, water districts, civil or environmental engineering, treatment plants, plant operations, industrial operations, infrastructure, EHS, water treatment companies, or consultants serving any of these.

    Not relevant (DROP): students, IT or software, recruiters or HR, finance or accounting, marketing, retail or fashion, healthcare, pure academia, or anything with no link to water, infrastructure, municipal, or industrial work.

    Rules:

    • Only answer DROP if you are confident the person is not relevant.

    • If there is any reasonable chance they fit, or the headline is vague or empty, answer KEEP.

    • Output exactly one word: KEEP or DROP.

    Headline:

  4. If you really want to save credits you can add a fourmule berfor that will check for keywords,