Trade show lead backlog revival agent for small agencies and consultancies on Salesforce, routed by partner capacity

What The Prospector does

A founder-led agency or consultancy of 11 to 50 people exhibits at a handful of trade shows a year. Badge scans and business cards end up as spreadsheets or bulk-imported Salesforce leads, and then client work takes over. Partners are billable, nobody owns follow-up, and by the time anyone looks, the leads have gone cold and the event looks like a waste. The Prospector owns event lead follow-up end to end for leadership. It first works the existing backlog from past shows, oldest-but-best first, then handles each new event within two days of close. For every lead it checks whether the firm already has a relationship (current client, past client, referral partner, alumni, open opportunity), researches the company and contact, enriches missing data, decides whether the lead is worth pursuing, and writes a first touch grounded in what the firm actually does and the work it has proven. It runs follow-up until there is a reply or a clean stop, and when someone shows interest it routes them to the partner whose practice and current utilization fit, books a scoping call, and hands over a brief that cuts the discovery work before a proposal. It also watches the website for event leads who come back to browse, and keeps a dashboard that shows leadership what each show actually produced in meetings and pipeline. Hacking Demand-style build and maintain means someone keeps the prompts, lists, deliverability and routing working as the firm's offer and team change.

Custom build

The firm runs Salesforce and should keep it as the system of record, so this is a custom AI build rather than HubSpot Breeze. A custom AI agent handles the judgement-heavy parts (reading booth notes, relationship checks, research, writing and reply classification), while n8n orchestrates the steps between Salesforce, FullEnrich, Warmly, Smartlead, Chili Piper and the partner capacity data, with every action logged back to Salesforce records and campaigns. This fits a small firm well: no new CRM, no rep seats for a sales engagement suite they will not use, and a setup that can be maintained by an outside team because the logic lives in readable workflows and a single context file rather than scattered across tools.

What starts it

• A trade show or conference ends and the badge scan export or business card photos are uploaded to a designated Salesforce campaign or shared folder
• Initial launch: the backlog of event leads older than two weeks with no logged activity is queued for revival in priority order
• A lead from a past event returns to the website and is identified on a services, case study or pricing page
• A prospect replies to any outreach, including out-of-office, referral to a colleague or a not-now answer
• A partner's weekly utilization snapshot changes, opening or closing capacity for new scoping calls

What it reads

• Salesforce leads, contacts, accounts, campaigns and opportunities, including event campaign membership and past client history
• An AI context file maintained with leadership: ICP by practice area, service offers, case studies and outcomes the firm can stand behind, common objections and the firm's tone
• Partner roster with practice areas, industries served, and weekly utilization or capacity pulled from the time tracking or resourcing tool
• FullEnrich waterfall enrichment for missing emails, titles and phone numbers, plus public company information (news, hiring, leadership changes)
• Warmly website visitor identification matched to Salesforce leads and accounts
• Smartlead sending, reply and deliverability data

When a person takes over

• Any lead tied to an existing client, past client, referral partner or open opportunity goes to the relationship owner as a personal follow-up task, because referrals and relationships are the firm's main revenue source and should never get automated email
• Every positive reply goes to the matched partner within one business day with the pre-scoping brief, since partners own discovery, scoping and the proposal
• When no qualified partner has capacity for a fit prospect, the founder decides whether to book anyway, delay the call, or refer the work out, rather than the agent overcommitting the team
• Pricing questions, RFP invitations, requests for references or anything that sounds like a contract or procurement question go straight to a partner with no agent reply

Rules it follows

• No automated outreach to current clients, past clients, referral partners, alumni or anyone a partner has flagged as a personal relationship; these are suppressed at the record and account level before any sequence starts
• The agent never promises scope, timelines, pricing, team members or availability; it only offers a conversation with a named partner, because proposals and scoping are where the firm makes or loses margin
• Case studies and outcomes cited must come from the approved context file, with client names only where the firm has permission to use them
• Sending runs on warmed secondary domains with daily volume caps, bounce thresholds and automatic pausing, so a large backlog push never damages the main domain partners use for client email
• Backlog leads older than the agreed cutoff, or whose contact has clearly left the company, get one revival attempt (or a new contact at the account), never a full sequence to someone who never asked to hear from the firm

How you know it works

• Percentage of event leads with a first touch within 48 hours of the show closing
• Backlog leads revived, replied and converted to scoping calls, tracked separately from new event leads
• Scoping calls booked and held per event, attributed in Salesforce to the source campaign
• Pipeline created and won revenue per event, so leadership can compare shows on actual return
• Partner hours spent on event follow-up and discovery prep, captured in a short monthly check-in

From pilot to live

1. Weeks 1 to 3: context, suppression and backlog pilotBuild the AI context file with leadership, load the partner roster and practice areas, and set up suppression rules for clients, referral partners and competitors. Warm sending domains. Run the agent on the best 100 to 150 backlog leads from the most recent show with every draft reviewed by a partner, and tune tone and tiering from their edits.
2. Weeks 4 to 8: full backlog and live event handlingWork through the remaining backlog in priority batches within deliverability limits. Turn on Warmly visitor signals, Chili Piper booking and capacity-aware routing. Run the next trade show live with the 48-hour target, with partners reviewing only Tier 1 drafts and positive replies.
3. Month 3 onward: steady operation and maintenanceEvery event flows through the agent by default. Databox reporting goes into the monthly leadership meeting to decide which shows to keep. Ongoing maintenance covers updating case studies and offers, adjusting ICP by practice area, monitoring deliverability, refreshing suppression lists and fixing broken integrations as the team and tools change.