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.
GTM ENGINEER

One engineer.
The workflows
wired together.

These diagrams describe reference workflows and the systems that support outreach. Vendor appearances are design examples unless marked implemented. Click any circle to inspect its role.

WORKFLOW 01

Four sources in. One scored row out.

ZoomInfo for org charts, 6sense for buying stage, Unify for first-party intent, Apollo for the people. Clay merges all four, runs the email waterfall, and scores every row.

WORKFLOW 02

Route by tier. One contact, one path.

Score 80+ goes to Outreach plus the Nooks dial list. 50 to 79 goes to Instantly and HeyReach. Below 50 becomes a nurture audience. The router refuses to enroll the same contact twice.

WORKFLOW 03

Every reply is read and acted on in minutes.

Replies, call outcomes and website revisits all land in one place. Claude classifies each one, n8n fires the next action, and objections get drafted for a human to approve rather than auto-sent.

WORKFLOW 04

Meetings become revenue, and the loop closes.

What happens in meetings is the most valuable data the engine produces. Win and loss reasons retrain the fit score, Gong objections rewrite step 2 of the sequence, and Friday's report posts itself, including every run that ended incomplete.

Connect the toolsAPI keys and native integrations
Describe the workflowPlain English rules and triggers
Automatedwith alerts in Slack
THE SKILLS BEHIND THE WORKFLOWS

Eleven skills. Four workflows.

Each skill is something you build, not something you know. The tag shows which workflow above it powers.