Tech stack

The stack we build on

Most of this runs inside tools you already own. Where a layer is missing, we pick from the list below and set it up in your workspace, under your billing, so you keep it either way.

These are the platforms our systems are actually built on, grouped by the job each one does rather than by vendor.

The stack, by job

Core

The three we go deepest on. Most systems we build have all three in them.

ClayEnrichment and scoring
ClaudeResearch and messaging
HubSpotCRM and RevOps

Sourcing and contact data

Where target accounts come from. We pull from several rather than one, so coverage does not depend on a single database.

ApolloProspecting
AI ArkSourcing
ProspeoContact data
Ocean.ioLookalikes
Store LeadsE-commerce data
DiscolikeSourcing
ApifyScraping
LinkedInSales Navigator

Sending

Sequencers for email and LinkedIn. Which one we use depends on what you already run.

SmartleadCold email
InstantlyCold email
LemlistCold email
SalesforgeCold email
HeyReachLinkedIn
NooksDialler

Email infrastructure

Dedicated domains and inboxes, warmed and monitored, kept separate from your main domain.

ZapmailInboxes
MaildosoInboxes
Premium InboxesInboxes

Signals

Who is paying attention. Each of these writes onto the same record the sequencer reads from.

TrigifyPost engagement
RB2BSite visitors
Common RoomSignals
JunglerEngagement signals

CRM

The system of record. We build in whichever one you already run.

HubSpotCRM
SalesforceCRM
AttioCRM

Automation

What wires the stack together so each tool writes to the same record.

n8nAutomation
MakeAutomation
ZapierAutomation

AI

Research, qualification and copy written against enriched data rather than from a blank prompt.

ClaudeResearch and copy
ChatGPTAI
GeminiAI
PerplexityResearch
GrokAI

Data and build

For the AI agent and RAG work, where a system needs somewhere to keep what it knows.

PineconeVector search
SupabaseDatabase
SerperSearch API
PythonCustom scripts

Working tools

Where the content, the diagrams and the documentation live.

FigmaDesign
NotionDocs
MiroPlanning

Where each layer is used

Tool names and logos belong to their owners. Listing one here says we build with it, not that we are partnered with it.