AI at work
I look for the manual handoffs between a show and a sales conversation, and turn them into workflows people actually use. Everything below runs on Claude, connected to the tools we already work in.
In regular use · ~15 shows since May 2026
Event lead processing: from badge scans to sales follow-up
Before
After every show, raw badge-scan exports were cleaned, deduplicated, scored and mapped to Salesforce by hand. Follow-up sequences, SDR briefings and Slack announcements were written separately.
How it works
- 01Remove staff and organizers→
- 02Deduplicate→
- 03Score intent from rep notes→
- 04Flag partners→
- 05Merge qualifier answers→
- 06Map to Salesforce campaign fields
What it produces
A clean Salesforce upload · Outreach sequences and email templates · An SDR context brief · A Slack announcement for the team
Lead processing per show went from about 3 days to about 3 hours, so follow-up starts the same day.
Who uses it
My team runs it. SDRs and AEs work from what it produces. It includes an onboarding section so other teams can adapt it to their own shows.
Sample data
Salesforce upload| Lead | Company | Intent tier |
|---|
| Demo Lead A | Example Company A | High |
| Demo Lead B | Example Company B | Medium |
| Demo Lead C | Example Company C | High |
| Demo Lead D | Example Company D | Low |
Built · Shared with Marketing
Field Marketing Briefings: my daily system, packaged for the team
I built a daily routine that turns email, Slack and meeting notes into Asana tasks, a 7:30 AM briefing and an afternoon digest. Then I packaged it as an installable plugin with guided onboarding, so any marketer can set it up in under 30 minutes.
Four modes
Morning briefing · Midday digest of urgent items and next-day prep · Focus: a one-page action list for one project · Surface: an overview of everything open
Sample data
Morning briefing · 7:30 AM
FocusExample event: review the invitation draft.
Next-day prepExample event: confirm the demo schedule.
Built
Event plans built straight from the exhibitor portal
Every show's exhibitor portal has its own deadlines, and copying them into a project plan by hand is slow and easy to get wrong. Claude reads the portal and builds an Asana project plan from our template, customized to that event, so planners spend their time on the experience instead of the admin.
Built
A spec-to-build method with security built in
Before anything gets built, it goes through eight phases, each with one deliverable. It helps non-technical colleagues turn an idea into something buildable.
- Problem definition
- Gap analysis
- First-version scope
- Data mapping
- Security reviewmandatory, before any build
- Product requirements
- Roadmap
- Stakeholder brief
Led
Bringing AI into Marketing
I led our Marketing team's Claude pilot, wrote up the first week's learnings, and recommended broad, tiered access over a few central power users. I also took our Asana connector through a 28-day security review, from writing the request (access scope, sign-in method) to approval. I've been on the requester side of an IT security review, and I know what those teams need before they say yes.
Designed · Paused
Next up: a Slack bot for in-person events
The next phase of the lead workflow: a Slack bot that uses those outputs to drive sales and marketing engagement around in-person events, automates event scouting and planning, and gets sales follow-up within about two hours of a show. I wrote the requirements, roadmap, prompt designs and a gated test plan (10, then 50, then 550 leads), and aligned Sales, Marketing Ops, RevOps and our vendor. It was paused for other priorities, and I plan to pick it back up.