This is a design for a modern GTM stack, not a claim of 35 integrations. I have personally implemented Supabase/Postgres, Resend, Vercel, Meta and TikTok Lead Ads, HMAC webhook intake, and Claude APIs. The rest are here to show how the pieces fit together.
Connected stack

35 connectors.
One record in the middle.

Every tool here does one of three things: it feeds data in, it holds the record, or it acts on the outside world. Click a cluster on the map to jump to what each app actually does.

13feed data in
6hold the record
16act outward
DATA FLOWING INACTION FLOWING OUTCLICK ANY CLUSTER
THE RECORD CRM & records RESEARCH & DATA PRODUCT & REVENUE SIGNALS DOCS & FILES OUTREACH & SOCIAL MEETINGS & CALLS INBOX & TEAM COMMS

Connector groups

FEEDS IN

Research & data

Who the buyers are and what is true about them.

  • ApolloContact database: filter buyers by title, size, industry
  • People Data LabsBulk person and company data via API for enrichment at scale
  • BetterContactWaterfall email and phone finder, tries 20+ providers per contact
  • ExaAI web search API: research any company from live pages
Verified people, companies and context written onto the record.
FEEDS IN

Product & revenue signals

What customers actually do and pay.

  • SupabaseYour product database: query usage and account growth
  • StripePayments, MRR, failed charges, upgrade and churn events
  • CoinbaseCrypto payments and balances, for web3 revenue
  • GitHubRepo activity, a signal for dev-tool buyers
  • LinearIssues and roadmap: what ships and when
  • JiraTickets and sprints for larger engineering orgs
Usage spikes, new signups and payments become buying signals.
FEEDS IN

Docs & files

The knowledge the engine reads from.

  • Google DocsPlaybooks, ICP definitions, messaging docs
  • Google SheetsLists, scoring tables, exports and imports
  • Google DriveEvery file the team shares, searchable
ICP definitions, playbooks and lists that feed every workflow.
THE HUB

CRM & records

One record every tool writes to and reads from.

  • HubSpotCRM for most growing companies: deals, sequences, reporting
  • SalesforceEnterprise CRM that holds the master customer record
  • AttioModern, flexible CRM built around your own data model
  • PipedriveLightweight pipeline CRM for small sales teams
  • AirtableStaging tables and ops databases beside the CRM
  • NotionWiki, project tracking and the team knowledge base
If a tool never touches the record, it is not part of the engine.
ACTS OUT

Outreach & social

Where the message reaches people.

  • LinkedInWhere B2B buyers are: profiles, DMs, Sales Navigator
  • XFounder and operator audiences; fast signal on launches
  • InstagramCreator and consumer reach, DMs and story replies
  • FacebookGroups, pages and the widest paid reach
  • TikTokShort-form demand generation at the top of funnel
  • YouTubeLong-form proof: demos, teardowns, customer stories
  • Meta AdsPush scored lists in as custom audiences for retargeting
Sequences, DMs, content and paid audiences built from the record.
ACTS OUT

Meetings & calls

Where the conversation happens.

  • CalendlyTurns a yes into a booked slot with reminders
  • Google CalendarAvailability and the actual meeting record
  • ZoomThe call itself, recorded and shareable
  • FathomAI notetaker: summaries and action items per call
  • FirefliesTranscribes and searches every call across the team
A yes becomes a held meeting; the transcript comes back as data.
ACTS OUT

Inbox & team comms

Where humans get told what to do.

  • GmailSend, receive and classify every reply
  • OutlookThe same, for Microsoft-shop buyers
  • SlackWhere alerts land and the team acts from
  • DiscordCommunity-led motions and developer audiences
Replies land, alerts fire, and someone acts within minutes.