The eight layers of a GTM stack
A layer is a job, not a product category. Many tools span two or three layers (Apollo does data, enrichment and sequencing), but each tool should have one primary layer where it is the source of truth. When two tools both think they own the same layer, you get duplicate contacts, double sends and reports nobody trusts.
| Layer | Its one job | Output | How it quietly breaks |
|---|---|---|---|
| 1. Data | Define and source the market: accounts and contacts that fit your ICP | A TAM list with firmographics | Stale records; the list is built once and never refreshed |
| 2. Enrichment | Fill missing emails, phones, titles and attributes at the lowest cost | Contactable records | Credits spent on records that should have been filtered out first |
| 3. Signals | Tell you which accounts are in market now, and why | A ranked list of accounts with a reason | Too many alerts; reps learn to ignore them |
| 4. Orchestration | Move data between layers and trigger plays on events | Plays that start themselves | A webhook fails and nobody notices for three weeks |
| 5. Sequencing | Run multistep email, LinkedIn and SMS touches | Replies and booked meetings | Deliverability decay; sequences that never stop for existing customers |
| 6. Calling | Turn phone numbers into live conversations | Connects, conversations, meetings | Dead numbers, spam-labeled caller IDs, dials nobody logs |
| 7. CRM | Hold the one record of every account, contact, activity and deal | The system everyone and every agent trusts | Duplicates, unowned leads, stages that mean different things to different teams |
| 8. Analytics | Show what produced pipeline, by play, signal and channel | Decisions on what to keep and kill | Attribution built on activity counts instead of meetings and pipeline |
Bloomberry's analysis of GTM engineering job postings shows which tools the market expects a GTM engineer to know: HubSpot (52% of postings), Outreach (49%), Salesforce (45%), Zapier (39%), Apollo (29%), n8n (28%), Gong (23%) and Looker (17%). Clay showed up in more than 90% of the GTM engineer LinkedIn profiles it reviewed (Bloomberry, updated 2026-11-10).
GTM tools by layer, with what they cost
Example tools for each layer, with facts read on each vendor's own pricing page on 2026-11-18. These are examples, not a ranking. Prices change often, so check the page before you budget.
Layers 1 and 2: data and enrichment
- Clay is the default enrichment workbench. Plans run Free (100 Data Credits, 500 Actions a month), Launch from $185/mo, Growth from $495/mo, and Enterprise on a custom annual commitment. Data Credits start at $0.05 each across 150+ data partners; failed lookups cost nothing, and bringing your own provider API keys skips Data Credits entirely (Clay pricing, checked 2026-11-18). Full breakdown in Clay pricing explained.
- Apollo combines a contact database, enrichment and sequencing. Plans are Free, Basic, Professional and Custom; credits are pooled across the team, granted at the start of each billing cycle, and expire if unused, including purchased add-on credits, which also renew automatically until you remove them (Apollo pricing FAQ, checked 2026-11-18).
Layer 3: signals
- Common Room (now part of Zoom) sells buyer intelligence: Essential is $2,500/mo billed annually with 5 seats, up to 100k contacts, 6 Bombora intent topics and 1k website de-anonymizations a month; Advanced and Enterprise are custom (Common Room pricing, checked 2026-11-18).
- RB2B does website visitor identification: a Free plan for company-level ID (150 resolutions a month), Starter at $79/mo for person-level ID, Pro from $149/mo and Pro+ from $199/mo. Person-level ID is US only (RB2B pricing, checked 2026-11-18).
- Dealfront (Leadfeeder) identifies companies visiting your site: Lite at €0 (last 100 companies a month), Discover from €79/mo and Activate from €369/mo, billed annually (Dealfront pricing, checked 2026-11-18).
Bloomberry found that 43% of companies hiring a GTM engineer run a visitor identification tool and 35% run an intent data or signal platform. How to turn those feeds into plays is its own discipline: see signal-based selling.
Layer 4: orchestration
- Zapier bills by task: a Free plan with 100 tasks a month, Professional starting from $19.99/mo and Team from $69/mo (up to 25 users), with yearly billing advertised as 33% cheaper (Zapier pricing, checked 2026-11-18).
- n8n bills by workflow execution, however many steps it has: Starter is €20/mo billed annually for 2,500 executions, Pro €50/mo billed annually, and a self-hosted Business plan at €667/mo billed annually (n8n pricing, checked 2026-11-18). Per-execution billing usually wins for long, multistep enrichment flows; per-task billing is simpler for short ones.
Layer 5: sequencing
- Outreach combines per-seat pricing with consumption-based AI credits (10,000 credits on Amplify Essentials up to 100,000 on Amplify Pro). Prices are not published (Outreach pricing, checked 2026-11-18).
- Instantly is the common cold email choice for small teams: its Growth outreach plan is listed at $47/mo for 5,000 emails a month with unlimited email accounts and warmup (Instantly pricing, checked 2026-11-18). The figure shown depends on the monthly or annual toggle.
- Clay also includes a basic email Sequencer on every plan, including Free.
Layer 6: calling
The phone is the layer most GTM stacks skip, and the one where agent platforms usually stop. Dialers in this layer range from click-to-call inside a sequencer to parallel dialers that run several lines per rep. Orum requires a minimum of 9 seats and does not publish a price (Orum pricing, checked 2026-11-18); Nooks quotes custom pricing and integrates with HubSpot and Salesforce, with CSV upload for other CRMs (Nooks pricing, checked 2026-11-18). Compare options in the best parallel dialers and see how agents and dialers combine in AI SDR.
Layer 7: CRM
- HubSpot Sales Hub: free for up to 2 users; Professional $90/mo per seat plus a required one-time $1,500 onboarding; Enterprise $150/mo per seat plus $3,500 onboarding (HubSpot pricing, checked 2026-11-18).
- Attio: a Free plan, then Plus from $40/mo and Pro from $100/mo per workspace with extra users charged per seat, and Ultra from $1,000/mo billed annually only; paying annually on Plus and Pro costs about 20% less (Attio pricing, checked 2026-11-18).
- Salesforce remains the default above roughly a few hundred sellers; its pricing depends on edition and add-ons.
Layer 8: analytics
- Warehouse plus reverse ETL is how larger teams get one view of pipeline. Hightouch offers a free Basic Reverse ETL plan with up to 2 active syncs and usage-based paid plans (Hightouch pricing, checked 2026-11-18).
- Gong prices licenses per user plus a platform fee based on user count; the amount is not published (Gong pricing, checked 2026-11-18).
- For most teams under 50 sellers, CRM reports plus one shared dashboard are enough. Add a warehouse when you need to join product usage with pipeline.
What changes in an AI GTM stack
An AI GTM stack keeps the same eight layers. What changes is who moves the work between them. In a tool-only stack, a rep or a GTM engineer exports a list, enriches it, imports it to a sequencer, dials from another tool and logs the outcome. In an agent-run stack, agents do those handoffs and humans approve, talk and decide. The broader shift is covered in GTM 2.0.
| Layer | Tool-only stack: who does the work | AI GTM stack: who does the work |
|---|---|---|
| Data and enrichment | GTM engineer builds and reruns lists | Agent rebuilds and re-scores the TAM as wins and losses arrive |
| Signals | Reps read alert channels when they have time | Agent acts when a signal crosses a threshold you set |
| Orchestration | Zaps and scripts a person maintains | The agent is the orchestration, with every action logged |
| Sequencing | Reps enroll contacts and edit templates | Agent writes to the account's situation and runs the steps |
| Calling | Reps dial from a list | Agent runs the dialing; a human rep takes every live conversation |
| CRM | Updated when reps remember | Updated by the agent after every touch, with an owner assigned |
| Analytics | Activity dashboards | Outcome per play and per signal, because every action is logged |
Build vs buy: when to assemble the stack yourself
Building means buying the layers separately and paying a GTM engineer to wire them. Buying means a platform or an agent product that covers several layers at once. Neither is right by default. The deciding question is whether your edge is in how the system is built or in what it produces.
| Your situation | Lean toward | Why |
|---|---|---|
| Unusual ICP, custom data sources, plays nobody else runs | Build | Your data model and plays are the advantage; owning them compounds |
| You have a GTM engineer with spare capacity | Build, selectively | Spend their time on the two layers that differentiate, buy the rest |
| No GTM engineer, pipeline needed this quarter | Buy | A hire takes months to recruit and ramp before anything ships |
| Outbound depends on the phone | Buy the calling layer either way | Dialers, number health and screener handling are hard to build well |
| Your engineer spends most weeks fixing broken syncs | Blend | Hand execution to agents; keep the engineer on data, rules and quality |
Count the glue, not just the licenses
Licenses are the visible cost. The invisible one is the hours spent keeping layers in sync: failed webhooks, re-enrichment, dedupe, fixing sequences that emailed a current customer. A useful exercise: list every integration between two tools in your stack, write down who fixes it when it breaks, and estimate hours per month. If that total is more than a third of your GTM engineer's time, you have a buying decision to make, not a hiring one.
A starter GTM stack by company stage
The right stack is the smallest one that removes your current bottleneck. These are starting points by stage, using tools from the section above; swap any tool for an equivalent you already own.
| Stage | Bottleneck | Data, enrichment, signals | Orchestration and sequencing | Calling, CRM, analytics |
|---|---|---|---|---|
| Founder-led (pre-seed to seed, founder sells) | Not enough conversations | Clay Launch; a free visitor ID plan | Clay Sequencer or Instantly; Zapier Professional | A dialer with no seat minimum; HubSpot free or Attio; CRM reports |
| First sales team (2 to 10 reps) | Reps spend hours on research and logging | Clay or Apollo; one signal source you will actually act on | One sequencer as the source of truth; n8n or Zapier for routing | A parallel or power dialer synced to the CRM; one pipeline dashboard |
| Scaling (10 to 50 reps, first GTM engineer) | Plays do not scale past the best reps | Enrichment waterfall; intent and visitor ID scored together | Signal-triggered plays; documented routing rules | CRM with enforced dedupe and stages; warehouse if product data matters |
| Multi-team (50+ reps, RevOps team) | Too many tools, no single view | Consolidate providers; contract on usage | Agents or a platform for execution; engineers on rules and quality | Salesforce or HubSpot Enterprise; warehouse plus reverse ETL; conversation intelligence |
Worked example: the founder-led stack at list price
Using published prices checked 2026-11-18: Clay Launch ($185) + Instantly Growth ($47) + Zapier Professional ($19.99) + RB2B Starter ($79) = $330.99 a month, with HubSpot's free CRM on top. That covers data, enrichment, signals, orchestration, sequencing and CRM. It leaves out calling and paid data overages, and it assumes the founder or one operator does the wiring. The next dollar should go wherever the funnel leaks first: usually calling once email replies plateau, or data once Clay credits run out mid-month.
How to audit the GTM stack you already have
- Map every tool to one primary layerList every GTM tool and the layer it owns. Any layer with two owners is a source of duplicate records or double sends; pick one.
- Draw the data flowFor each integration, write what moves, in which direction, how often, and who fixes it. Integrations with no named fixer are your top risk.
- Find the empty layersMost audits find no real signals layer (alerts nobody acts on) or no calling layer (phone numbers enriched but never dialed). Those are cheaper fixes than another data tool.
- Price the glueAdd up monthly hours spent maintaining integrations. Compare that against consolidating two or three layers into one platform or agent.
- Measure by outcome, per layerTrack meetings and pipeline per play and per signal, not activity counts. Cut any tool that cannot show what it produced within a quarter.
Frequently asked questions
What is a GTM stack?
A GTM stack is the set of tools a company uses to find, reach and convert buyers. A complete one covers eight layers: data, enrichment, signals, orchestration, sequencing, calling, CRM and analytics. Each layer should have one tool as its source of truth.
What tools does a GTM engineer use?
Most GTM engineers work in a CRM (HubSpot or Salesforce), an enrichment workbench such as Clay, an automation tool such as Zapier or n8n, a sequencer such as Outreach or Apollo, plus SQL and often Python. In Bloomberry's analysis of job postings, HubSpot appeared in 52%, Outreach in 49% and Salesforce in 45%; SQL and Python each in 38%.
What is an AI GTM stack?
An AI GTM stack has the same layers as a traditional one, but agents do the work between them: building and scoring the account list, acting on signals, writing and sending outreach, running the dialing and updating the CRM. Humans approve, hold the conversations and decide.
How much does a GTM stack cost?
A founder-led team can cover six of the eight layers for about $331 a month at published list prices (Clay Launch, Instantly Growth, Zapier Professional, RB2B Starter, HubSpot's free CRM). Costs rise mainly with data usage, seats and the calling layer, and the biggest hidden cost is the time spent maintaining integrations.
Should I build my GTM stack or buy an all-in-one platform?
Build when custom data and plays are your competitive edge and you have a GTM engineer to own them. Buy when you need pipeline this quarter, have no one to wire the layers, or depend on the phone. Many teams blend: agents run execution while an engineer owns data, rules and quality.
- 1.Bloomberry, I analyzed 1000 GTM Engineering jobs, here is what I learned (updated 2026-11-10; checked 2026-11-18) (2026)
- 2.Clay, Pricing and plan FAQ, checked 2026-11-18 (2026)
- 3.Apollo, Pricing FAQ (credits, billing, integrations), checked 2026-11-18 (2026)
- 4.Common Room, Pricing, checked 2026-11-18 (2026)
- 5.RB2B, Pricing and plans, checked 2026-11-18 (2026)
- 6.Dealfront, Pricing, checked 2026-11-18 (2026)
- 7.Zapier, Pricing, checked 2026-11-18 (2026)
- 8.n8n, Pricing, checked 2026-11-18 (2026)
- 9.Outreach, Pricing and packages, checked 2026-11-18 (2026)
- 10.Instantly, Pricing, checked 2026-11-18 (2026)
- 11.Orum, Pricing, checked 2026-11-18 (2026)
- 12.Nooks, Pricing and FAQ, checked 2026-11-18 (2026)
- 13.HubSpot, Sales Hub pricing, checked 2026-11-18 (2026)
- 14.Attio, Pricing, checked 2026-11-18 (2026)
- 15.Hightouch, Pricing, checked 2026-11-18 (2026)
- 16.Gong, Pricing, checked 2026-11-18 (2026)
Spend your reps' day on conversations, not ringing phones.
TwinsAI parallel-dials up to 10 lines at once, validates every number with the carrier before it rings, and bridges a live prospect to your rep in under 400ms. It works inside HubSpot, Salesforce, Close, Attio, Outreach, Zoho, HighLevel, Pipedrive, Apollo and SmartMoving, with no seat minimum.