Your stack stays yours.
Bryn plugs into the stack you already run. It watches your site, product, and CRM, and lands Plays, rules you set once, in the tools your team works in all day. Nothing to replace, nothing to migrate.
Signals in, Plays out
Every integration sits in one of three lanes: the surfaces Bryn watches, the tools Plays land in, and the sequencer that carries your outbound.
Signals in
What Bryn watches
- Web beacon, including anonymous visitors
- Product telemetry
- Third-party intent
- Identity resolution via a data partner
Product, site, and CRM, together
Outputs out
Where Plays land
- Slack and Teams
- HubSpot, Salesforce, Pipedrive
- Landing-page personalization
- In-app prompts
Within the same minute ⬩ on the record
Sequencers
Your outbound, nudged
- 11x, Artisan
- Outreach, Salesloft
Partner posture: Bryn hands the account and the evidence to your sequencer.
Bring your own outbound
Wired to the tools you already run
Every tool on this board is live today or named next on the roadmap. The webhook connector covers the rest.
Live
10 connectors- Slack
- Discord
- Webhook
- Jira
- HubSpot
- Instantly
- Amazon SES
- Linear
- Resend
- Microsoft Teams
On the roadmap
10 named- Salesforce
- Clay
- Outreach
- Salesloft
- Apollo
- Pipedrive
- Attio
- Segment
- LinkedIn Ads
- Google Ads
Request an integration
Requests are roadmap signal, and we read every one. Name the tool and the lane it belongs in.
Bryn as tools, in any MCP client
Bryn exposes the scope, the scores, and the audit log over MCP. Ask from Claude desktop or Cursor and you get the same answers the product shows, from the same record.
Warehouse-native, from Growth up
Every signal, score, and run lands as a Snowflake row. Your analysts query Bryn's record next to everything else they query, in the warehouse you already govern.