The ten-minute section with Naveen: the problem, the engine, six and a half minutes of it working, and the numbers. Present opens the slides.
Ten to fifteen minutes, Jason Dowden moderating. The split below is a starting point to shape together.
| Min | Segment | Who | What happens |
|---|---|---|---|
| 0:00 | Intro | Dallas | Name, role, department. One line on what GTM engineering is. |
| 1:00 | The problem | Naveen + Dallas | The mandate, and why outbound doesn't scale by hand. |
| 3:00 | Demo, recorded | Dallas narrates | Six and a half minutes of the engine working: Claude Code, Clay, then lemlist. |
| 9:30 | Results | Dallas | The numbers, and the hours of manual work they replace. |
| 11:30 | Questions | Jason moderates | Answers prepped for the likely ten. |
One recording, 6:30. Claude Code is the brain, Clay carries the data and the AI research, lemlist carries the send.
| Time | Beat | On screen |
|---|---|---|
| 0:00 | The brain | Claude Code: agents that ran overnight, and a strike plan built live from one ask. |
| 1:10 | The database | Clay: every contact and account we know, synced from Salesforce. A live segment built in seconds, at zero cost. |
| 2:10 | AI research + drafts | Rows enriching live: person found, work email verified, research written, a personalized five-touch sequence drafted per contact. |
| 3:40 | Automation | A published workflow runs end to end: registrant in, enriched, classified, routed. No one at the desk. |
| 4:30 | The send layer | A loaded lemlist campaign: email, LinkedIn, and call steps per lead, every variable rendered, AI voice note on the sequence. |
| 5:40 | The loop, beyond outbound | Replies route back to the owner, every motion measured on cost per meeting. Closer: the twelve back-office account maps built with the AM team, live as a page. |