Skip to main content

​
Context Graph Coordinates

The Context Graph is heyBTW’s core data layer. It connects events, CRM pipeline, partner relationships, and attribution into a single queryable graph that powers every agent, dashboard, and MCP response. Every recommendation the graph produces is grounded in five coordinates. Agents, users, and MCP consumers can trace any surfaced account, attendee, or deal back to the signals that put it there.

​
Events

Event attendance history. A record carries the Events coordinate when the person or account has attended one or more co-marketing events tracked in heyBTW. The signal includes which events, how many, and which sessions. Example: “Attended Berlin Fintech Dinner and NYC SaaS Summit in the last 90 days.”

​
Timeline

Recency and close-date proximity. A record carries the Timeline coordinate when engagement is recent or there is an open deal with a target close date. The signal captures when something last happened and when the next meaningful moment is expected. Example: “Deal closing in 12 days. Last event touch 3 weeks ago.”

​
Relationships

Partner and account connections. A record carries the Relationships coordinate when the account has partner relationships mapped, a customer or prospect classification, or co-attendance overlap with other target accounts. Example: “Two partners, Stripe and Chargebee, have mapped this account as a customer.” Relationship is the coordinate that makes the others cohere. Without it, event data is a list of attendees, CRM data is a list of accounts, and partner data is a list of logos. With it, those lists become a graph that compounds with every co-marketing activity that flows through the platform.

​
Outcome

CRM pipeline state. A record carries the Outcome coordinate when a deal exists in the connected CRM with stage, amount, and expected close. This is where the graph connects to revenue. Example: “$150K opportunity in Negotiation, stage weight high.”

​
Attribution

Data source and touch history. Always present. Attribution captures where a signal came from (CRM, event platform, partner upload, manual entry) and the sequence of touches that preceded it. This is what makes every recommendation auditable. Example: “First event touch March 4. Second touch May 12. Deal created May 20, classified as Sourced.”

​
How the coordinates compose

A single recommendation usually carries multiple coordinates. A high-priority account might carry Events, Timeline, Relationships, Outcome, and Attribution all at once. When reading an agent output or MCP response, the coordinates tell you why the account is on the list and what to do next. Events and Timeline tell you when. Relationships tell you who to route through. Outcome tells you what’s at stake. Attribution tells you how you got here. Relationship is the coordinate that ties the rest together: it turns four parallel signals into one connected path from a person to a partner to an event to a deal.