Runs on the stack you already own.

HubSpot or Salesforce as the system of record, plus Clay for research and enrichment, Instantly, Dripify and ZeroBounce for sending, Customer.io for lifecycle, Gong, Granola and Nooks for calls, Snowflake for product usage, Slack, n8n and Zapier for alerts and workflow, and Claude and ChatGPT as models.

Yes. Either can be the system of record, including custom objects and properties.

Usually. If your team relies on it, your GTM Engineers connect it during the build.

Only where agreed. We map existing automation in the workshop so nothing collides.

You keep your existing licenses. Canopy works with the tools you already own rather than reselling them.

Clay handles account and contact research, enrichment waterfalls and buying signals. Canopy turns that research into target lists and personal first touches, screens every list against your HubSpot or Salesforce records and exclusion lists, and writes every touch, reply and meeting back to the CRM.

Product usage from Snowflake is synced into your CRM as account and usage records, refreshed daily. The Customers workspace uses it for health scores, churn alerts and expansion signals, so CSMs and AEs see usage on the account record where they already work.

Yes. Lifecycle sends from HubSpot or the sender you already use, such as Customer.io, and Outbound sends through your existing infrastructure, such as Instantly. Consent, suppression and reporting stay in the tools that hold them today.

Only what each workspace needs. Read and write scopes are agreed per workspace in the workshop and documented, credentials are stored only in your private instance, and every write to the CRM is logged and can be reverted.

Every touch, reply, task, call summary and stage proposal, written against the right contact, company or deal. Stage changes are proposed for the rep to confirm, and every write is logged and revertible, so your CRM stays the complete record.