Outbound

Turn a Luma guest list into booked meetings

Databar collect. Enrich. Swarm decides intro vs cold. Email goes to Amplemarket. LinkedIn-only goes to Aimfox.

The loop

  1. 01Pick a high-signal Luma eventPull attendee full names and LinkedIn profiles. The guest list is the TAM for the night, not a badge scan you forget.
  2. 02Collect the list in DatabarL key grabs links. You want names and profiles in one table before anyone enriches.
  3. 03Enrich across four providersLeadMagic, Findymail, Prospeo, ContactOut. Export the full list. Missing contact data is what the next gate reads.
  4. 04Score proximity in The SwarmIf someone on the team is already connected, route the intro. Cold is the leftover path, not the default.
  5. 05Split the send, book on HubSpotEmail only → Amplemarket. LinkedIn profile only → Aimfox. The meeting lands on a HubSpot calendar. That is how an event becomes pipeline.
linkedin.com ↗Guest list in. Calendar out. Channel depends on the data.Identify a high-signal event on Luma, pull attendee names and LinkedIn profiles, collect in Databar.ai (L key grabs links), enrich through LeadMagic, Findymail, Prospeo, and ContactOut, score relationship proximity in The Swarm so connected teammates take the intro, then route email-only into Amplemarket and LinkedIn-only into Aimfox and book on a HubSpot calendar.

Most teams treat the attendee list as a leftover. Dave’s version is a routing machine: collect, enrich, then decide intro vs cold before anyone writes a line.

The interesting constraint is the split, not the scrape. Swarm proximity picks the intro. Contact data picks the channel. Email-only and LinkedIn-only do not share a sequencer. HubSpot is only the last mile — the calendar.