The chilled-water lead nobody called
A pipe fabrication subcontractor is hiring someone to run its trade shows and get every contact to sales within two business days. Here is how a booth conversation goes cold, what went wrong for others who automated the follow-up, and a build that holds up.
How to use this page
Read the story, then the map. If no one in your business holds the middle square, start there, not with the build. If someone does, read what went wrong for others, then copy the build kit into your AI agent.
On 14 October 2026 a merit-shop pipe fabrication and installation subcontractor with about 140 people and four shops in Georgia posted for a marketing and events coordinator. The lines that carry the job: “Capture every contact met at an event and get the list to the business development team within two business days”, “Close out each event with a short recap: total cost, contacts made, and what to change next time”, and “Attend events with the VP and account manager.” Pay: “Competitive hourly pay based on experience and qualifications.” Travel up to 20%.
Here is how it goes today. On the show's first afternoon a project manager at a mechanical contractor stops at the booth: a new plant, a chilled-water loop, a spring start, and a question about fabrication lead times. The account manager talks with him for five minutes. The coordinator scans his badge on the rented scanner and writes “chilled water, spring” on the back of a card.
The show closes Thursday. Monday is the typing: 25 scans into a spreadsheet, the card still in the booth crate. At 4:45 the list reaches the VP and the account manager, two business days after the show closed, on the dot: 25 names, titles and companies. No notes.
The account manager opens it the next week, between two bids. Which of the 25 was the chilled-water one? He emails the four names he remembers. On day 14 the project manager sends his drawings to two competing fabricators, the ones who emailed him the day after the show. A contact the show cost about $320 to meet, on one benchmark's numbers, went with the project.
Nobody here is careless. The two-business-day standard is in the job description, and the list met it. What the list could not carry was the conversation: the note stayed on a card, the badge gave a name and a company, and the follow-up waited on the one person who also had the bids. Hand the whole list to an automated sequence instead and you get the other failure: a reply rate near zero from people who scanned a badge while walking past.
The project manager, the 25 contacts, the days and the counts are an example built from the posting, which gives no counts. The $320 a contact and the $18,000 a year are estimates from published show costs, badge-scan medians and a 2015 follow-up survey.
The map: the same job as a system
The judgment it all runs on sits in the middle square, held by a person. Around it, the work in the order it moves, each square run by the machine or by a person. Along the bottom, what it runs on.
The middle is who is worth a call: which contact is a real prospect for the shop, and what the next step is. The VP of business development holds it with the account manager.
The same job as a system. The middle is the call on who is worth a conversation, held by the VP with the account manager. The badge is scanned on the left by the person who met them; across the top the machine saves the contact, finds the email and drafts the thank-you; on the right the person who met them sends it and makes the call. Along the bottom is what it runs on: the switch and the alert, the counts, and the tags and the one email it drafts from.
- Runs on its own
- A person does it
- The judgment it all depends on
- What it runs on
Who holds the middle square
The VP of business development, with the account manager. Which contact met at a booth is a real prospect for the shop, a mechanical contractor, an engineer or a plant owner with a project, and what the next step with each one is.
Before you build, these must already be true in your business:
- Every event has a name, a budget and a tag set in the app before anyone leaves for it.
- The company keeps one CRM, and every contact from an event lands there, never in a spreadsheet.
- The person who met the contact owns the first email and the call, and sends it under their own name.
Still deciding whether to do this, or no one holds this judgment yet? See the verdict: what it costs today, what to hand over, the bill and the owner
What went wrong for others, and the rules it gives the build
Five things that went wrong for people who did this job, or that tripped them up, and the rule each one gives the build.
“they all just put a junk email address in their badges, and the phone number is either blank or a number straight to their hospital”; and marketing ops “supposed to have leads loaded into the CRM within a few days and it ends up taking them 2 weeks.”
A BDR at a healthcare software company, April 2026. Read it
The rule: Treat a found email as a guess until a person confirms it, and put every contact in the CRM within a minute of the scan, never in a batch weeks later.
“every time we come back with a stack of badge scans and business cards and the follow-up sequence goes nowhere. reply rates are near zero. the contacts are real but they're cold as hell, they scanned our badge while walking past.”
A B2B software marketer, three shows at about $18,000 all in, March 2026. Read it
The rule: Only a contact a person tagged at the booth gets a first email; a bare scan with no tag and no note gets nothing.
“I have lost count of how many times we have come back from a show and someone says 'wait, which guy was this?'. Only scanning badges does nothing anymore.”
An exhibitor, May 2026. Read it
The rule: Every scan carries a spoken note from the person who met them, written on the record at the booth, and the draft email quotes it.
“We had 1,100 scans on the booth. Went through the spreadsheet after, and I counted 8 decent customers for follow up.”
A salesperson after a London show, June 2025. Read it
The rule: Count contacts worth a call, emails sent and visits booked, never scans.
“attendees may have opted out of sharing their organization, email address and/or phone number with you. However, if they give verbal permission, you may enter their contact information into the notes field.”
One conference's own exhibitor guide. Read it
The rule: Expect scans with no email; the alert lists them the morning after, and a person decides whether to find the address or let the contact go.
What it costs to run
About $4 with the app at $9.99 a seat for five seats over about 150 contacts a year; about $0.50 if built, in email finder credits and model usage, plus the workflow runner's plan.
Estimate. The cost per contact assumes six shows and 150 contacts a year. The baseline replaces both.
The build kit
One prompt to paste into Claude, ChatGPT or any AI agent that can build. It checks the middle square before anything else, builds the map square by square, carries the 5 rules above, and has the whole build: what starts it, every step, the data, the review, the alerts, what to do when it breaks, and what to count before you switch it on.
Before you build
- It may never, on its own: Send an email; email anyone whose address a person has not confirmed; write a note the booth team did not say; add a contact to a marketing list; or contact anyone who asked us not to.
- Keep with a person: The tag at the booth (hot, warm, pass) and the ten-second note; reading and sending every first email, under the name of the person who had the conversation; the call and the visit; and what to change next time.
- Not yet: Emailing anyone whose badge gave no address, until a person has confirmed the found one; any second or third touch to the whole list; adding anyone to a marketing list; and anything to a contact who asked not to be contacted.
Help me build this in my business: Everything after a conference, trade show or expo: capturing every contact met at the booth, getting the list to the business development team within two business days, and closing the event out with a recap of what it cost, who was met and what to change next time. Plus the calendar and the budget the shows run on. The contacts belong in the CRM, the customer list the company already keeps. Before you build anything: this runs on one person's judgment, "Who is worth a call", held by the VP of business development, with the account manager. Ask me whether each of these is true in my business, one at a time: 1. Every event has a name, a budget and a tag set in the app before anyone leaves for it. 2. The company keeps one CRM, and every contact from an event lands there, never in a spreadsheet. 3. The person who met the contact owns the first email and the call, and sends it under their own name. If any is not true, stop and tell me which, and what I need in place first. Do not build around it. Rules from others who built this and got it wrong. Keep every one: - Treat a found email as a guess until a person confirms it, and put every contact in the CRM within a minute of the scan, never in a batch weeks later. - Only a contact a person tagged at the booth gets a first email; a bare scan with no tag and no note gets nothing. - Every scan carries a spoken note from the person who met them, written on the record at the booth, and the draft email quotes it. - Count contacts worth a call, emails sent and visits booked, never scans. - Expect scans with no email; the alert lists them the morning after, and a person decides whether to find the address or let the contact go. The map of this system, a 3x3: - The middle square, the judgment it all runs on: Who is worth a call (Which contact is a real prospect for the shop, and what the next step is. Held by the VP of business development with the account manager.). It stays with a person. - The work, in the order it moves: 1. Scan the badge (a person does it: Whoever met them, with the tag and the ten-second note); 2. Save the contact (runs on its own: Show, tag and note on the CRM record within a minute); 3. Find the work email (runs on its own: Marked found until a person confirms); 4. Draft the thank-you (runs on its own: In the sender's name, from the note); 5. Send it and call (a person does it: The one who met them; the Hot ones the same evening). - Along the bottom, what it runs on: Automation (The CRM connection switch and the no-email alert.); Measure (Hours from show close to the list, emails sent within two business days, replies, visits, cost per contact.); Build (The three tags defined (Hot, Warm, Pass), the one email it drafts from, the opt-out line.). Build the squares in that order, and keep the person's squares with a person. The working set to build from: - Trigger: A badge, business card or name tag photographed in the app at a show, tagged with the event; or the organizer's scanner export dropped in after the show. - Steps: Read the name, company and title from the photo; match the contact in the CRM or create it, with the show, the tag and who met them; transcribe the spoken note onto the record; find the work email and title where the badge left them out, marked found until a person confirms; draft the first email in the name of the person who met them, from the note, with one next step, the opt-out line and the postal address; put the draft in that person's queue; log the send, the reply and any bounce; the morning after the show, the list to business development, hot first; the Friday after, the recap draft from the budget and the records. - Data: One record per contact: event, date, who met them, tag, note, name, company, title, email (from the badge or found), phone, draft text, final text, sent at, replied, bounced, meeting booked, and the show's cost per contact. - Review step: The person who met them sends every first email; the coordinator confirms every found email the machine flagged; the VP reads the recap. - Alerts: A contact with no email 24 hours after the show; a draft waiting more than two business days; a bounce; a reply asking to stop (everything to that contact stops the same day); an organizer export whose columns changed; and the wrong-but-green count, the drafts their sender rewrote by more than half. - If it breaks: What you see: contacts missing from the CRM, a draft with the wrong note, or bounces. Check first: the app's CRM connection is still authorized; the event was created in the app before the show; the phones were offline and the queue has not synced. Safe fix: turn the CRM connection off, export the scans, and type the list as today. - Baseline to count before switch-on: The last two shows: contacts captured, contacts with a note, hours from the show closing to the list reaching sales, first emails sent and when, replies, meetings, and each show's total cost. - Tools by name: Lemontaps Business Connect ($9.99 a user a month annual, 5 to 19 users; badge and QR scanner, CRM sync, AI enrichment); Tendro ($499 a show, unlimited team); Blinq Business ($4.99 a seat annual plus $9.99 a captured lead); BoothMaven (Capture $49 a month for 3 staff, no CRM sync; Essential $149 with CRM sync and sequences); the organizer's scanner (2026 BOMA Expo: $459 advance, $559 after, $99 insurance); HubSpot's business card scanner (free) and Sales Hub Professional ($90 a seat annual, $1,500 onboarding) for sequences; built: Claude Haiku 5.5, n8n Starter (20 euros a month), Apollo Basic ($49 a seat annual, one credit a verified email, as third parties report it). It may never, on its own: Send an email; email anyone whose address a person has not confirmed; write a note the booth team did not say; add a contact to a marketing list; or contact anyone who asked us not to. Keep with a person: The tag at the booth (hot, warm, pass) and the ten-second note; reading and sending every first email, under the name of the person who had the conversation; the call and the visit; and what to change next time. Not yet: Emailing anyone whose badge gave no address, until a person has confirmed the found one; any second or third touch to the whole list; adding anyone to a marketing list; and anything to a contact who asked not to be contacted. Ask me for the tools and numbers you need from my business before you start. Then build it one step at a time, and show me each step working before the next.
No one in your business holds this judgment?
Then the first step is the expertise, not the build. Konstellation, Nick's advisory firm, judges one of your jobs with you, free: what it costs today, the verdict, the bill and who owns it.
Get the verdict on one jobKnow someone doing this job by hand? Send them this page.
Free, for one email
One email opens every job and every system.
Everything on instig8.ai is free. Your email, once, unlocks all of it on this device, and you hear when the next job is out.
Unsubscribe any time.