GTM Engine · The stack

Claude in the middle. Your stack around it.

The engine is built on the tools you already run: Google or Microsoft, HubSpot, Salesforce or Dynamics 365, Slack or Teams. Each tool has one job and connects to Claude directly. Keep what connects; cut what doesn't.

Book a 30-minute engine reviewGet your GTM Engine score
KNOWLEDGEGoogle DriveCRMHubSpotRESEARCHClaySEQUENCESApolloEMAILGmail + CalendarAPPROVALSSlackSOCIALBufferAI SEARCHVISIBLDWEBSITEBase44
Same engine on:

Step 1 of 7

A target account visits your pricing page

  1. A target account visits your pricing page
  2. Claude researches the account in Clay
  3. It checks your knowledge base in Google Drive for the right proof
  4. It drafts the email in your voice
  5. The draft lands in Slack for approval
  6. Your rep approves it and it goes out from their own inbox
  7. HubSpot logs the signal, the play and the result
Each role's one job

Pick a role. See what Claude does through it.

The roles stay the same in every engine. The tools that fill them change with each company. Pick a role to see its job and the tools we commonly connect.

In the middle

Claude

Connected to every role below

The brain. It researches, writes, decides the next step, and runs skills, agents and scheduled tasks across every tool below. It reads your knowledge base before it does anything.

Role in the engine

Knowledge base

What Claude knows

Reads your ICP, positioning, pricing, proof, objections and voice before it does anything.

Filled by whichever you run, for example

  • Google Drive
  • SharePoint and OneDrive
  • Notion
  • Confluence

How Claude connects

Each tool connects to Claude through an official connector, an MCP server or the tool's API. Every connection is tested in the diagnostic, before the build starts.

Call recorders, data warehouses, billing and support tools connect the same way when a play needs them.

01.

Your CRM keeps the record

HubSpot, Salesforce or Dynamics 365. If it isn't logged in the CRM, it didn't happen.

02.

Your workspace holds the knowledge

Google Drive or SharePoint. The knowledge base lives in your account, not ours.

03.

People approve in your team chat

Slack or Teams. Agents draft. Nothing reaches a buyer until a person says yes.

Already have a stack?

Bring it to a 30-minute review. We'll tell you what to keep, what to connect and what to cut.

Book a 30-minute engine reviewGet your GTM Engine score