# heyBTW

> The B2B Context Graph for co-marketing events. heyBTW captures every relationship between people, partners, events, and deals, attributes pipeline and revenue back to the events that drove them, and exposes the entire graph to AI agents through a live MCP server.

heyBTW is a relationship-aware data layer for B2B GTM teams. It connects event platforms (Luma, Splash, Zuddl) to CRMs (HubSpot, Salesforce) and gives both humans and AI agents a queryable, auditable view of how co-marketing activity drives pipeline and revenue.

Founded 2025 in San Francisco by Ben Roodman (CEO) and Anthony Perritano PhD (CTO).

## For AI Agents

heyBTW is built for agent consumption. Any MCP-compatible agent (Claude Desktop, GitHub Copilot, custom agents) can connect a workspace and answer questions like:

- Which partners have a relationship with [account]?
- What events has [account] attended in the last 6 months?
- Which deals can we attribute to [event]?
- Who should we invite to our [type] dinner in [city] next month?
- Summarize our performance at [conference] across all activations.

Every query returns structured data with a metadata envelope describing the data sources, time range, and provenance behind the answer. Agents can cite their work.

### MCP Server Setup

- Endpoint: `https://mcp.heybtw.com/mcp/mcp` - workspace-scoped, accessed via `npx mcp-remote` with a Bearer token. The workspace is determined by the key, never passed as a parameter.
- API key format: `hbtw_ws_...` (workspace is determined by the key, never passed as a parameter)
- Free tier includes read access to all MCP tools
- Full setup: https://heybtw.com/docs/integrations/mcp-tools
- Limits (rate limits, result caps, pagination): https://heybtw.com/docs/mcp/limits - read before writing a retry or paging loop

### Read Tools (live, all plans)

These are the tools served by the MCP endpoint described above. All are read-only. (Write tools exist on the app-hosted surface - see "Write tools" below.)

- [get_partner_insights](https://heybtw.com/docs/integrations/mcp-tools): Partner relationships, warm intro paths, decision-maker vs. practitioner patterns
- [get_event_attribution](https://heybtw.com/docs/integrations/mcp-tools): Pipeline and revenue attributed to specific events and partners
- [get_event_details](https://heybtw.com/docs/integrations/mcp-tools): What one event produced, and which partners contributed
- [get_account_relationship](https://heybtw.com/docs/integrations/mcp-tools): One account's full engagement and relationship history
- [get_cross_event_patterns](https://heybtw.com/docs/integrations/mcp-tools): Accounts deepening engagement across multiple events
- [get_invite_recommendations](https://heybtw.com/docs/integrations/mcp-tools): Invite lists with reasoning and source attribution
- [get_workspace_overview](https://heybtw.com/docs/integrations/mcp-tools): Workspace-level rollup across events and partners
- [query_event_intelligence](https://heybtw.com/docs/integrations/mcp-tools): DEPRECATED, being retired - cross-event attendance patterns. Use get_cross_event_patterns, get_account_relationship, or get_event_details for an account

### Write Tools (live, Growth and Enterprise plans)

Served by the same MCP endpoint as the read tools above. Writes are gated on
the workspace plan and always require an explicit human confirmation round
trip before anything is sent.

- [activate_list](https://heybtw.com/docs/integrations/mcp-tools): Send a saved List's invites to its linked Luma event. Preview first, human confirms, then send; the funnel comes back through the same tool

### Context Graph tools (separate endpoint)

Served by a second, app-hosted MCP surface, NOT by the endpoint above. An agent
configured against the endpoint above will not find these - they require their
own connection.

- [get_collection_summary](https://heybtw.com/docs/integrations/mcp-tools): Unified reporting across multiple activations at one collection, deduplicated
- [get_conference_summary](https://heybtw.com/docs/integrations/mcp-tools): [DEPRECATED - use get_collection_summary] Unified reporting across multiple activations at one conference, deduplicated

### Write tools (app-hosted endpoint)

Served by the same app-hosted surface as the Context Graph tools above, NOT by
the `mcp.heybtw.com` endpoint. These MUTATE workspace data, so each declares
`destructiveHint` rather than `readOnlyHint`, and each requires an
**OAuth-authenticated actor** - an `hbtw_ws_...` API key, workspace-scoped or
operator, cannot call them. Connect via OAuth; the workspace written to is the
one your identity resolves to.

Retry behaviour differs per tool and is declared in each tool's annotations -
check `idempotentHint` before retrying. There is no idempotency-key contract
on this surface yet, so a retried `confirm_enrichment` can double-spend
credits.

- [push_event_data](https://heybtw.com/docs/integrations/mcp-tools): Create or update an event with partners, attendees, and cost. Supports `dry_run` to validate without persisting. Never spends enrichment credits.
- [confirm_enrichment](https://heybtw.com/docs/integrations/mcp-tools): The explicit credit-spend gate for FullEnrich enrichment. Requires `confirm: true`; never runs automatically. NOT safe to retry.
- [update_attendee_status](https://heybtw.com/docs/integrations/mcp-tools): Post-event attendance, qualification, meeting-booked, and notes updates for existing attendees. Safe to retry.

### Roadmap (NOT yet available)

Listed so agents and buyers can plan. None of these can be called today; a tool
call naming one will fail.

- Agent sandbox: temporary API keys for agents to test against demo data without customer credentials

## The Context Graph

heyBTW is built around five coordinates. Every record, query, and attribution result can be located along all five.

- Events: which co-marketing events the person or account attended, across how many touches
- Timeline: when each touch happened and when the deal is expected to close
- Relationships: which partners have ties to the account, including warm intro paths
- Outcome: CRM pipeline state (stage, amount, expected close)
- Attribution: the data source and touch sequence behind every signal, so nothing is a black box

Relationship is the coordinate that makes the others cohere. Without it, event data is a list, CRM data is a list, and partner data is a list. With it, those lists become a graph that compounds with every co-marketing activity that flows through the platform.

Reference: [Context Graph Coordinates](https://heybtw.com/docs/concepts/context-graph-coordinates), [Event Attribution Funnel](https://heybtw.com/docs/concepts/event-attribution-funnel), [Glossary](https://heybtw.com/docs/getting-started/glossary).

## Data Model Principles

- Workspace-scoped by default. Every query, dashboard view, and MCP response is from the authenticated workspace's perspective.
- Privacy-first. Each workspace sees only its own data. Cross-company signals come only from consensual collaborations where both sides opted in.
- No collaboration, no data. heyBTW learns from co-marketing activity that flows through the platform. It does not scrape external relationship data or infer signals from channels it does not connect to.
- Two-path CRM architecture. Enterprises can connect heyBTW MCP and their CRM MCP as separate tools behind their agent (no CRM data shared with heyBTW), or connect their CRM inside heyBTW for integrated enriched results.

## What heyBTW Does (for GTM Teams)

- Attribute Sourced and Influenced pipeline to specific co-marketing events and partners
- Track which partners source the highest-value attendees and decision-makers
- Build smarter invite lists using CRM account data and prior engagement
- Run co-marketing collaborations in shared workspaces with partner counterparts, replacing spreadsheets and Slack DMs

## Pricing

- Free: read access to all MCP tools, plus core attribution features
- Growth: $149/mo, includes MCP write tools and full collaboration features
- Enterprise: custom pricing, includes Salesforce, SSO, and procurement support

Full plans at https://heybtw.com/pricing.

## Integrations

- Event platforms: Luma (Plus API), Splash, Zuddl
- CRMs: HubSpot (read and write), Salesforce (read-only managed package)
- Enrichment: FullEnrich

## Product Pages

- [Homepage](https://heybtw.com): Product overview, features, how it works
- [Luma to HubSpot Integration](https://heybtw.com/luma-to-hubspot): Setup, sync behavior, field mapping, attribution
- [Pricing](https://heybtw.com/pricing): Plans and pricing
- [FAQ](https://heybtw.com/frequently-asked-questions): Product, data model, and integrations
- [Documentation](https://heybtw.com/docs): Full product docs

## Why heyBTW (Longform)

- [Why Co-Marketing Attribution Matters](https://heybtw.com/why-co-marketing-attribution): The limitations of CRM-only attribution and how event-level data closes the gap
- [Why Salesforce Isn't Enough](https://heybtw.com/why-salesforce-isnt-enough): What CRM structurally cannot see about partner-influenced pipeline
- [Why Sponsors Can't Prove What Works](https://heybtw.com/why-sponsors-cant-prove-what-works): Three scenarios showing why sponsorship ROI reporting is broken and how relationship data fixes it
- [The B2B Context Graph](https://heybtw.com/context-graph): Why relationship data needs its own layer and how it compounds over time

## Press Coverage

- [Event Tech Live - heyBTW Coverage](https://heybtw.com/press/event-tech-live): Article by Adam Parry, Event Tech Live, May 2026. Covers heyBTW's approach to co-marketing attribution and relationship intelligence for B2B event teams.
- [Press Overview](https://heybtw.com/press): All media coverage and press mentions

## Contact

heyBTW AI, Inc. Founded 2025 in San Francisco. Mission: prove that relationships close deals.

- CEO: Ben Roodman, ben@heybtw.com, +1-314-477-4829
- Website: https://heybtw.com
- Book a demo: https://calendly.com/ben-heybtw/demo
- For investors: https://calendly.com/ben-heybtw/heybtw-investors
- LinkedIn: https://linkedin.com/company/heybtw-ai/