Fieldstone Events Converts Conference Chaos Into Account Follow-Up
A fictional case study of how a B2B events team used Dench to turn trade show meetings, badge scans, and notes into CRM actions.
This is a fictional case study based on common patterns we see in event-driven B2B teams.
Fieldstone Events is a 50-person compliance software company that relies on industry conferences for pipeline creation. The team was good at meeting prospects in person. The problem came after the booth was packed up.
Conference follow-up was inconsistent.
The Problem#
At a typical event, Fieldstone collected badge scans, business cards, meeting notes, dinner conversations, and informal promises.
Some of that context made it into the CRM. Much of it did not.
Reps returned from conferences tired, opened a spreadsheet of leads, and tried to remember which conversations mattered. High-intent prospects waited days for follow-up. Existing customers who stopped by the booth were treated like new leads. Strategic accounts got buried next to casual visitors.
The team needed a better post-event operating system.
What Changed With Dench#
Fieldstone used Dench to connect event notes with CRM records.
After each conference day, reps sent quick summaries into the workspace. Dench matched people to existing accounts where possible, created new records when needed, and grouped follow-up by priority.
The agent surfaced which conversations were connected to open opportunities, which accounts had executive interest, and which leads needed same-day outreach.
The New Workflow#
Fieldstone created an event debrief ritual.
At the end of each day, the team spent 20 minutes adding rough notes. Dench turned those notes into account context and next actions. The next morning, reps received a follow-up queue instead of a raw lead list.
After the event, marketing and sales reviewed the event summary together: high-priority accounts, customer conversations, partner opportunities, and nurture contacts.
The Results#
Fieldstone reduced the lag between event conversation and first follow-up.
Reps spent less time sorting lists and more time writing relevant messages. Existing account context prevented awkward outreach. Leadership got a clearer read on whether the event created real pipeline or just activity.
The conference stopped ending when the booth closed. The follow-up motion continued cleanly.
Why It Worked#
Events create valuable but fragile context.
Dench helped Fieldstone capture that context while it was still fresh and connect it to the CRM before it decayed. The result was better follow-up, cleaner account history, and a more useful view of event ROI.
The win was not more leads. It was better memory after the leads arrived.