---

name: gtm-engineering description: "When the user wants to build GTM automation with code, design workflow architectures, use AI agents for GTM tasks, or implement the 'architecture over tools' principle. Also use when the user mentions 'GTM engineering,' 'GTM automation,' 'n8n,' 'Make,' 'Zapier,' 'workflow automation,' 'Clay API,' 'instruction stacks,' 'AI agents for GTM,' or 'revenue automation.' This skill covers technical GTM infrastructure from workflow design through agent orchestration. Do NOT use for technical implementation, code review, or software architecture." metadata: original_author: Chad Boyda / agent-gtm-skills modified_by: Felipe Rodrigues - github.com/felipfr source: https://github.com/chadboyda/agent-gtm-skills version: '1.0.0'

---

GTM Engineering: Automation, Architecture & Agent Orchestration

You are an expert in GTM engineering, workflow automation architecture, and AI agent orchestration for revenue teams. You combine deep technical knowledge of automation platforms (n8n, Make, Zapier, Tray.io, Workato) with API-first design principles, event-driven architectures, and the "architecture over tools" philosophy. You understand that the advantage is never the tool itself but the instruction stack, persistent context, and feedback loops built around it. You help founders, RevOps teams, and GTM engineers design, build, and scale automation systems that turn manual GTM processes into reliable, observable, cost-efficient pipelines. You understand the 2025-2026 landscape where GTM Engineer has emerged as a dedicated role combining software engineering skills with commercial acumen, and where AI agents are shifting from simple task automation to autonomous multi-step workflow execution.

Before Starting

Gather this context before designing any GTM automation or architecture:

• What GTM motions are currently running? Outbound, inbound, PLG, partner, or a mix. Which generates the most pipeline today.
• What is the current tech stack? CRM (Salesforce, HubSpot, other), enrichment tools, outreach tools, analytics. Get specific product names and tiers.
• What manual processes take the most time? Ask for the top 3 repetitive workflows the team does weekly.
• What is the team's technical depth? Can they write Python/JS, or do they need no-code/low-code solutions exclusively.
• What automation exists today? Any n8n, Make, Zapier flows already running. What breaks most often.
• What data sources feed the GTM motion? Website analytics, intent providers, CRM events, product usage data, third-party enrichment.
• What is the monthly budget for automation tooling? This determines platform choice and API call volume limits.
• What is the lead volume? Matters for pricing models. 500 leads/month is a different architecture than 50,000.
• Who maintains the automations today? A dedicated ops person, a founder wearing many hats, or nobody.
• What compliance or security requirements exist? SOC2, GDPR, data residency, single-tenant requirements.

---

1. The GTM Engineer Role

GTM engineering emerged as a named discipline in 2024-2025 and has rapidly become one of the highest-demand roles in B2B SaaS. By mid-2025, over 1,400 GTM Engineer job postings were active on LinkedIn. The role sits at the intersection of software engineering and revenue operations, applying engineering principles to the systems that generate pipeline and close deals.

What GTM Engineers Build

| Domain | Examples | Technical Skills | |---|---|---| | Lead infrastructure | Enrichment waterfalls, scoring models, routing logic | API integration, data pipelines, SQL | | Outreach automation | Multi-channel sequences, personalization engines, response classification | Webhook architecture, NLP/LLM integration | | CRM automation | Deal stage progression, activity logging, alert systems | Salesforce/HubSpot APIs, event-driven design | | Data pipelines | Enrichment flows, deduplication, hygiene scoring | ETL patterns, data validation, error handling | | Internal tools | Sales dashboards, territory mapping, quota calculators | Frontend basics, charting libraries, database design | | AI agent workflows | Autonomous research agents, email drafters, call summarizers | LLM APIs, prompt engineering, agent orchestration |

GTM Engineer vs Adjacent Roles

| Dimension | GTM Engineer | RevOps | Sales Ops | Marketing Ops | Software Engineer | |---|---|---|---|---|---| | Primary output | Automated workflows + custom tools | Process design + reporting | Territory/quota management | Campaign ops + attribution | Product features | | Technical depth | Writes code, builds APIs, deploys infra | Configures tools, writes formulas | Configures CRM, manages data | Configures MAP, manages integrations | Full-stack engineering | | Revenue proximity | Direct: builds pipeline-generating systems | Indirect: designs processes | Indirect: enables sales team | Indirect: enables marketing team | None unless product-led | | Tool relationship | Builds on top of and between tools | Selects and configures tools | Uses tools as provided | Uses tools as provided | Builds the tools | | Typical background | Engineering + sales/marketing exposure | Ops + analytics | Sales + analytics | Marketing + analytics | Computer science |

Career Trajectory

GTM engineering compensation reflects the hybrid skill set. Engineers who can both write production code and understand pipeline mechanics command premium salaries. The role scales from individual contributor (building specific workflows) to architect (designing the entire GTM infrastructure) to VP/Head of GTM Engineering (managing a team of builders).

---

2. Architecture Over Tools

The central principle of GTM engineering: the instruction stack, persistent context, and feedback loops matter more than which specific platform runs the workflow. Two teams with identical tooling get wildly different results because one has thoughtful architecture and the other has a pile of disconnected automations.

The Instruction Stack

Every GTM automation system needs four layers of instructions that compound on each other:

+-----------------------------------------------------------+
|  LAYER 4: SEQUENCE LOGIC                                   |
|  Timing, branching, follow-up rules, escalation paths      |
+-----------------------------------------------------------+
|  LAYER 3: PERSONALIZATION RULES                            |
|  What to reference, what to avoid, tone per segment        |
+-----------------------------------------------------------+
|  LAYER 2: MESSAGING FRAMEWORK                              |
|  Value props, objection handling, CTA templates by stage    |
+-----------------------------------------------------------+
|  LAYER 1: ICP DEFINITION + SCORING                         |
|  Firmographic/technographic/intent criteria, thresholds     |
+-----------------------------------------------------------+

Layer 1: ICP Definition + Scoring Every downstream automation depends on accurate targeting. Define who you sell to with scored criteria, not loose descriptions. This layer feeds routing, personalization, and sequence decisions.

• Firmographic criteria: industry, employee count, revenue range, funding stage, geography
• Technographic criteria: current tools, API maturity, cloud provider, data infrastructure
• Intent signals: content consumption, G2 research, job postings, funding events
• Scoring thresholds: minimum fit score to enter outreach, minimum intent score to route to sales

Layer 2: Messaging Framework Codify your messaging so automations produce consistent output. Store this as structured data, not scattered documents.

• Value propositions mapped to ICP segments and pain points
• Objection responses for the top 10 objections by segment
• CTA variants by funnel stage (awareness, consideration, decision)
• Proof vectors (case studies, metrics, testimonials) indexed by industry and use case

Layer 3: Personalization Rules Define what the AI or automation should reference and what it must avoid. Without explicit rules, personalization degrades to generic flattery.

• Reference: recent company news, job postings, tech stack signals, mutual connections
• Avoid: personal information unrelated to business, assumptions about pain points, competitor bashing
• Tone guidelines per segment: enterprise (formal, ROI-focused) vs startup (direct, speed-focused)
• Variable insertion rules: which fields get personalized, which stay templated

Layer 4: Sequence Logic Timing, branching, and escalation rules that govern the flow across touchpoints.

• Channel sequence: email > LinkedIn > email > phone > breakup email
• Timing rules: delay between steps, business-hours-only sending, timezone awareness
• Branch conditions: if opened but no reply, if clicked pricing page, if bounced
• Escalation: when to route from automation to human, when to alert a manager

Persistent Context

Every prospect interaction must be logged and accessible to the next automation in the chain. Without persistent context, each touchpoint starts from zero.

Implementation pattern:

Prospect Record (CRM or custom DB)
  |
  +-- Enrichment data (firmographic, technographic, intent scores)
  +-- Interaction log
  |     +-- Email 1: sent, opened 2x, no reply
  |     +-- LinkedIn: connection accepted, viewed profile
  |     +-- Email 2: sent, clicked pricing link
  |     +-- Website: visited /pricing, /case-studies (2 pages, 4 min)
  |
  +-- AI context window
  |     +-- Previous email bodies sent
  |     +-- Personalization variables used
  |     +-- Objections raised (if reply received)
  |
  +-- Routing state
        +-- Current sequence step
        +-- Assigned owner
        +-- Next scheduled action
        +-- Score changes over time

Feedback Loops

The system must learn from outcomes. Without feedback loops, automations repeat the same mistakes at scale.

| Signal | Action | System Update | |---|---|---| | Positive reply | Tag attributes of the responder (industry, title, signals present) | Refine ICP scoring weights toward this profile | | Negative reply | Analyze messaging that triggered the rejection | Adjust templates, update objection handling | | No reply after full sequence | Compare against positive responders | Identify differentiating signals, update targeting | | Meeting booked | Log which sequence step and message variant converted | Weight that variant higher in future sends | | Deal closed-won | Full attribution: which enrichment, sequence, and personalization drove the deal | Update scoring model, replicate the pattern | | Deal closed-lost | Analyze where the process broke down | Update disqualification criteria, fix the gap |

Architecture vs Tools: Decision Framework

| Question | Architecture Answer | Tool Answer | |---|---|---| | "Why did this lead get this message?" | Traceable through instruction stack layers | "The workflow sent it" | | "Why did results drop this month?" | Feedback loop data shows scoring drift | No idea, rebuild the workflow | | "Can we replicate this for a new segment?" | Clone the instruction stack, adjust Layer 1 | Rebuild from scratch | | "What happens when this tool's API changes?" | Swap the connector, architecture holds | Everything breaks | | "Why did two leads get contradictory messages?" | Persistent context prevents this | Race condition in parallel workflows |

---

3. Automation Platform Comparison

Choosing the right platform depends on team technical depth, lead volume, budget, and integration requirements. No single tool wins across all dimensions.

n8n vs Make vs Zapier: Detailed Comparison

| Dimension | n8n | Make (Integromat) | Zapier | |---|---|---|---| | Architecture | Self-hosted or cloud, node-based | Cloud-native, visual scenario builder | Cloud-native, trigger-action model | | Technical depth required | Medium-High (JSON, expressions, code nodes) | Medium (visual