You run the room. heyBTW handles the work around it.
heyBTW connects the events you already run, and the partners you run them with, to your go-to-market team. Get started over MCP: connect it to Claude and ask who to invite, who registered, who came and who needs a follow-up.
https://mcp.heybtw.com/mcpCopyPaste it into Claude as a custom connector. It also works with ChatGPT and any assistant or custom build that supports MCP.
Read the setup guideGet started today. No API key, no setup call.
Your events and your partners, connected to your go-to-market team
The events you already run
Dinners, meetups, open houses and partner events, on the event platform or spreadsheet you use today. Nothing to migrate.
The partners you run them with
Co-hosts and partners: which accounts each one is inviting and who they brought. Nobody has to hand over a full list.
Aligned inside your company
Marketing, sales and partnerships work from one record: who was invited, who came, who owns the follow-up and what it did to pipeline in your CRM.
Aligned with your partners
You and each partner work the same room. Each company sees its own side, and the record of who met whom outlasts the night.
Know who's in the room. Fill it with the right people. Follow up and prove it.
Ask the way you would ask a teammate.
Claude shows the room against your target account list: who is in, who each co-host brought and which accounts are still missing.
Every invite comes from the person who already knows them, drafted in your own email and logged in heyBTW.
Claude lists what was committed, what is done and what is overdue, by name.
Claude joins the event record with your CRM: event-sourced and event-influenced pipeline, and what each partner brought.
What heyBTW keeps, and what stays in your tools
heyBTW keeps the record of your events
- Who was invited
- Who registered
- Who came
- Which partner brought them
- Who on your team followed up
Your tools stay where they are
- Your event platform runs the event.
- Your CRM runs the deal. heyBTW does not copy it. Your assistant reads both and joins them by email and company.
- heyBTW does not send email or write to your CRM. Those go through the tools you already have connected, with your approval.
- The one exception is a send you ask for and confirm: Luma invites to an event, and an invitation email to a co-host.
What is free
Free
Connecting, adding events, recording registrations and attendance, saving lists and saving tasks.
Paid plan
Sending Luma invites through heyBTW. See pricing
Event and partner ROI, connected to the CRM you already run
Your CRM stays the source of truth for the deal. heyBTW keeps the touches the CRM never sees: who was invited, which partner brought them, who came and who followed up. Claude reads both, so every answer ties back to the pipeline your revenue team already reports.
What your events touched
Event-sourced and event-influenced pipeline, by event, with the dates behind each one.
What each partner brought
Partner-sourced and partner-influenced deals, each with the touch that earned the credit. Credit for every partner, never a ranking.
Your rules, your systems
Your attribution window, applied to your own pipeline. heyBTW never writes an opportunity or contests your CRM's original source.
Works with HubSpot, Salesforce, Attio and other CRMs through the connector you already have in your assistant.
Test it on your next event
Add the connector, paste a link to your event page and attach the guest list. Claude, or the assistant you use, takes it from there.
Read the setup guide