◎
a state machine
ingests evidence, selects pointers, assembles a cadence, previews it, creates campaigns, polls the tools, enforces suppression and routes human tasks.
gtm engine architecture
a gtm engine that
a gtm engine that
keeps a human
in the loop.
it turns a company dossier + a chosen angle into a reviewed email cadence and linkedin sequence. the llm writes copy. the engine owns state, sequencing and suppression. nothing sends without a human.
01
what it is
a stateful pipeline, not an autonomous sdr. it owns the boring, dangerous parts: identity, sequencing, suppression and task routing.
⊘
not an autonomous sdr
no unapproved sends. no reply writing. not a crm. the tools are the sender of record; a human owns every manual step.
⇄
a handoff
the engine owns state and rules. the llm writes copy. instantly and heyreach send. a human approves the plan before anything is created.
02
system at a glance
evidence goes in; a reviewed sequence comes out; the feedback loop closes. no magic, just a narrow set of guarantees.
01 / evidence
dossier + context
notion intake, archive history, enrichment, and a versioned angle catalog.
02 / engine
identity → pointers → copy
one company per domain, evidence-backed pointer selection, then copy from approved proof only.
03 / tools
instantly + heyreach
campaigns are created, never launched without an explicit command. manual steps become tasks.
04 / loop
poll → suppress → audit
replies, meetings, bounces and unsubscribes stop the lead across both channels.
03
the decisions that matter
judgment lives in the constraints. these are the ones that keep the system honest.
evidence over vibes
every pointer cites a dossier path or a proof id. missing evidence means the pointer is dropped, not invented.
rules over prompts
pointer selection is deterministic. the model fills templates; a validator rejects digits and entities that are not in the evidence set.
one identity per company
domains are the anchor. aliases attach; conflicts are reported; nothing is silently merged.
human approval before push
preview shows every step, resolved variables and dropped pointers. v1 creates but never launches.
suppression is cross-channel
a reply or meeting on one channel stops both. a meeting pauses all of that company’s campaigns. a kill switch exists.
tools are the sender of record
the engine never assumes a send happened. it creates, then reads state back. external ids make re-runs idempotent.