GTM Role + Workflow Specs: What Each Factory Role Actually Does¶

A GTM factory is only as good as the people running it. This document defines what each role actually does day-to-day — not the job description version, but the operational reality. It covers five roles that appear in modern revenue-driven companies: GTM Manager / Head of Growth, GTM Engineer, Growth Ops / Marketing Ops, Content Strategist / Content Machine Operator, and Outbound / SDR.

Research basis: Analysis of 1,000+ GTM Engineer job postings (Bloomberry, Jan 2026), Clay's internal GTM engineering function, GitLab's Marketing Ops handbook, Growth Operations Manager role specs, and modern SDR workflow playbooks. Sources are cited inline.

1. GTM Manager / Head of Growth¶

What they own: The revenue engine. Strategy, pipeline, team, and cross-functional coordination.

Core Responsibilities¶

• Own the GTM strategy — define ICP, targeting, messaging frameworks, and channel mix. Make the call on when to add or kill channels.
• Drive pipeline generation — accountable for MQL → SQL → opportunity → revenue conversion. Own the numbers, not just the activity.
• Coordinate cross-functional launches — product marketing, sales, customer success, and sometimes product. The GTM Manager is the connective tissue.
• Manage the GTM team — hire, coach, and hold SDRs, GTM Engineers, and Growth Ops accountable to weekly/monthly targets.
• Report to founders/executives — own the GTM dashboard. Present pipeline reviews, forecast accuracy, and ROI on GTM spend.

Key Workflows¶

Weekly:
- Pipeline review: examine stage-by-stage conversion, identify bottlenecks, adjust cadence or targeting.
- ICP/messaging check: review what's working in outreach and update messaging briefs.
- Team performance 1:1s: review SDR activity metrics, GTM Engineer sprint progress, Growth Ops data quality.
- Content/sequence review: assess active campaigns, kill low-performers, approve new plays.

Monthly:
- Pipeline forecasting: update monthly/quarterly targets, reallocate budget across channels.
- Campaign retrospective: post-mortem on launches — what drove pipeline, what didn't.
- ICP refinement: revisit ICP definition based on win/loss data and CAC by segment.
- Tool stack audit: review tool usage, credit consumption, and ROI on paid tools.

Quarterly:
- GTM strategy reset: update segments, messaging, and channel investment based on results.
- Hiring plan: grow the team based on pipeline needs.
- Cross-functional alignment: sync with product on roadmap and with CS on expansion plays.

Time Allocation (How They Spend vs. Delegate)¶

Key insight: The best GTM Managers protect their time for strategy, ICP decisions, and cross-functional alignment. They build systems and delegate execution. If they're building workflows in Clay every day, something is wrong.

Tools They Touch¶

• CRM (Salesforce or HubSpot) — pipeline views, forecasting, account management
• BI/reporting (Looker, Tableau, built-in dashboards) — pipeline analytics
• Sales engagement (Outreach, Salesloft, Apollo) — sequence oversight
• GTM platform (Clay) — occasionally, to understand what's being built
• Intent signal platforms (6Sense, Koala, DreamData) — for ICP research and targeting
• Communication (Slack, Notion) — cross-functional coordination

2. GTM Engineer¶

The newer role — what makes it different from traditional RevOps. The GTM Engineer role emerged around 2023–2024, popularized by Clay (which coined the term). Analysis of 1,000 job postings shows it's functionally similar to RevOps in many ways, but with key differences in emphasis and tooling philosophy.

What makes it different from RevOps:

The role exploded: GTM Engineering job postings were up 205% year-over-year as of early 2026 (Bloomberry, Jan 2026). The median salary is $127,500, with top-paying companies (Vercel, OpenAI, LILT AI, Air, Ramp) paying $180K–$252K for the role.

Core Responsibilities¶

• Build and automate GTM workflows — the #1 stated responsibility in GTM Engineer job postings. This means enrichment pipelines, lead scoring, sequence automation, and CRM integrations.
• Integrate the GTM tech stack — connect Clay, CRM, sales engagement, intent signals, and AI tools into coherent workflows.
• Own and optimize the CRM — while ranked3rd–4th in GTM Engineer JDs (vs. 1st for RevOps), CRM ownership is still central. Keep data clean, structure fields, and build automation on top of it.
• Optimize outbound and prospecting — this is the distinctive GTM Engineer focus. Build workflows that surface ICP accounts, enrich them, score them, and trigger personalized outreach at scale.
• Orchestrate AI agents — increasingly, GTM Engineers are building and managing Claygent workflows, AI-driven research agents, and LLM-powered personalization at scale.

What They Actually Build (Day-to-Day)¶

From the Bloomberry analysis of 1,000 job postings, plus Clay's internal documentation:

1. Enrichment workflows — pull firmographic, technographic, and contact data from multiple providers (Clearbit, Apollo, ZoomInfo) via waterfall approaches, deduplicate, and write to CRM.
2. Lead scoring systems — build formulas that rank prospects by fit + engagement, often combining intent signals, hiring data, funding events, and CRM behavior.
3. Sequence automation — build multi-channel outreach sequences (email → LinkedIn → call) that trigger based on CRM state or enrichment results.
4. CRM integrations — connect new tools, build custom sync logic, and maintain data pipelines between systems.
5. Signal-based outbound — build workflows that trigger outreach when accounts show buying signals (job postings, funding, product launches, etc.).
6. Bulk enrichment — run large-scale enrichment passes on CRM records, often millions at a time for enterprise teams.
7. Reverse demos and personalized content at scale — build Clay workflows that generate per-account or per-contact personalized content (custom mockups, tailored case studies).

Skills Required¶

From job posting analysis (Bloomberry, Jan 2026):

• SQL — appears in 38% of GTM Engineer job postings. Used constantly for CRM queries, data warehouse pulls, pipeline diagnostics, and integration validation.
• Python — appears in 38% of postings. Used for automation scripts, custom integrations, and increasingly for LLM/AI agent orchestration.
• No-code automation tools — Zapier (39% of postings), n8n (28%), Clay itself. GTM Engineers live in these tools.
• CRM fluency — HubSpot (52%) or Salesforce (45%). You need to know both, or at least one deeply.
• AI prompting — increasingly required. GTM Engineers write prompts for Claygent, GPT, and Claude to do research, classification, and content generation at scale.
• API knowledge — understand REST APIs, webhooks, and how to connect systems. Not software engineer level, but comfortable enough to build custom integrations.

Career paths into the role (from LinkedIn analysis of 100 GTM Engineers):
- SDR/BDR path (most common) — started in sales, learned automation to hit quota, built workflows that the team adopted, formalized into GTM Engineering.
- RevOps/Sales Ops path — CRM admin and reporting background, expanded into automation and AI.
- Early startup generalist — wore multiple hats at a seed/Series A startup, built tools out of necessity.
- Marketing/Growth path — started in demand gen, developed technical skills over time.

Tools They Touch Daily¶

How They Fit Into the Factory System¶

GTM Engineers are the builders of the factory. They take the GTM Manager's strategy and the ICP definition and translate them into automated systems. They sit between strategy and execution — they don't do outreach themselves, but they build the machine that makes outreach effective. They report to the GTM Manager or Head of Growth in most structures.

3. Growth Ops / Marketing Ops¶

Pipeline management, data quality, and reporting. Growth Ops is the backbone of the factory — the role that keeps data clean, reports accurate, and tools running.

Core Responsibilities¶

• Pipeline management and data quality — own the CRM data model. Ensure fields are populated, duplicates are removed, and lifecycle stages are accurate. "Garbage in, garbage decisions" is the Growth Ops mantra.
• Attribution and reporting — build and maintain dashboards that show pipeline by channel, campaign, and segment. Own the attribution model (first-touch, last-touch, or multi-touch) and present it to leadership.
• Tool management and stack maintenance — own the MarTech stack. Manage licenses, evaluate new tools, handle integrations, and ensure tools are connected and working.
• Workflow automation — build and maintain operational workflows: lead routing, CRM workflows, lifecycle triggers, and handoff logic between marketing and sales.
• Process documentation and optimization — document the handoffs between marketing, sales, product, and customer success. Find and fix bottlenecks.

Key Workflows¶

Daily:
- CRM data quality checks — review new leads, flag incomplete records, monitor for duplicates.
- Pipeline dashboard review — check for anomalies in stage progression or drop-offs.
- Tool health monitoring — ensure enrichment credits, email sending limits, and integrations are functioning.

Weekly:
- Attribution report — pull pipeline by source/medium/campaign, present to GTM Manager.
- Lead routing audit — verify leads are routing to correct owners and sequences are triggering.
- Tool license review — flag underutilized seats, plan for renewals or cancellations.

Monthly:
- Full funnel analysis — MQL → SQL → opportunity → close rates by segment and channel.
- Marketing/sales handoff review — assess lead quality at handoff, identify friction points.
- Stack ROI assessment — evaluate each tool's contribution to pipeline and recommend changes.

Tools They Touch¶

• CRM (HubSpot or Salesforce) — data model, dashboards, workflow automation
• Marketing automation (HubSpot, Marketo, ActiveCampaign) — nurture workflows, lead scoring, campaign execution
• BI/reporting (Looker, Tableau, Google Data Studio) — attribution dashboards, funnel analytics
• Attribution tools (HubSpot attribution, Attribution, Northbeam) — multi-touch attribution modeling
• Project management (Notion, Asana) — process documentation, campaign tracking
• Data enrichment (Clearbit, ZoomInfo) — used by Growth Ops to clean and enrich records

How They Fit Into the Factory System¶

Growth Ops is the operational glue. They ensure the GTM Manager has accurate data to make decisions, the GTM Engineer has clean data to build on, and the outbound team has good records to work from. Without Growth Ops, the factory's data degrades and decisions are based on bad information. They typically report to the GTM Manager or Head of Growth, or sometimes to the CFO/COO in smaller companies.

4. Content Strategist / Content Machine Operator¶

How content production fits into the factory. The Content Strategist role has evolved from pure creation to becoming an operator of an AI-assisted content machine — research, create, distribute, and repurpose at scale.

Core Responsibilities¶

• Content strategy and editorial planning — define what content gets made, for which ICP segment, and at which stage of the buyer journey. Own the content calendar and editorial calendar.
• AI-assisted content production — operate AI writing tools (Claude, GPT, Copy.ai, etc.) to generate first drafts, repurpose existing content, and scale output without sacrificing quality. The "operator" part means knowing how to prompt, review, and edit AI output.
• Distribution and repurposing — take one piece of long-form content (e.g., a case study or whitepaper) and break it into 10–20 derivative assets: LinkedIn posts, Twitter threads, email sequences, blog sections, and ad copy.
• Content-performance loop — track which content drives pipeline, feed that data back into editorial planning. Work with Growth Ops to connect content touchpoints to CRM records.
• ICP-aligned messaging — ensure all content reflects the current ICP, messaging framework, and buyer pain points defined by GTM Manager.

AI-Assisted Content Workflow¶

Modern content machines look like this (per Copy.ai and Distribution.ai frameworks):

1. Research — AI tools scan existing content, competitor content, and buyer signals to identify what to write about.
2. First draft — AI generates a draft from a structured brief (topic, ICP, tone, CTA). Human reviews and edits.
3. Distribution planning — AI determines optimal posting times and channel fit based on historical performance data.
4. Repurposing — one long-form piece →10–20 derivative short-form pieces. AI adapts tone and format for each channel.
5. Scheduling and publishing — automated queuing across LinkedIn, Twitter, email, and blog with approval workflows.
6. Performance measurement — track engagement and pipeline impact per asset. Feed back into brief refinement.

Key Workflows¶

Weekly:
- Editorial calendar review — confirm content is planned for the week/month, aligned to active campaigns.
- AI draft review — review AI-generated content, edit for voice and accuracy, approve for publishing.
- Distribution audit — verify scheduled posts went live, track performance.
- Repurposing sprint — identify one high-performing piece and generate derivatives.

Monthly:
- Content performance review — analyze which assets drove pipeline vs. engagement. Update ICP messaging if needed.
- Content inventory — audit existing content for accuracy, update outdated pieces.
- Repurposing roadmap — plan next month's repurposing from top-performing content.

Tools They Touch¶

• AI writing tools (Claude, GPT-4, Copy.ai, Jasper) — first-draft generation, repurposing
• Content management (Notion, Confluence) — editorial planning, content calendar
• Distribution (Distribution.ai, Buffer, Hootsuite) — scheduling, multi-channel publishing
• LinkedIn / Twitter — organic distribution and engagement
• CRM (HubSpot, Salesforce) — content-to-pipeline attribution
• Analytics (Google Analytics, built-in analytics) — content performance tracking
• SEO tools (Semrush, Ahrefs) — keyword research, content gap analysis

How They Fit Into the Factory System¶

Content is the fuel for outbound and inbound. The Content Strategist creates the assets that the outbound team uses in sequences (case studies, whitepapers, social proof) and the inbound team uses for SEO and thought leadership. They work closely with the GTM Manager on messaging and with the GTM Engineer on content automation workflows. The factory model requires content to be systematized and repurposed — not created fresh every time.

5. Outbound / SDR¶

What the outbound machine looks like day-to-day. The SDR (Sales Development Representative) role is the most activity-intensive in the factory. But modern outbound is a system, not a person — the SDR is the human in the loop that converts, while the system handles research, list building, and sequencing.

Core Responsibilities¶

• ICP research and list building — identify target accounts and contacts that match the ICP. Use B2B database tools (Apollo, ZoomInfo, LinkedIn Sales Navigator) to build qualified prospect lists.
• Multi-channel outreach sequencing — execute outbound sequences across email, LinkedIn, and cold calling. Modern SDR workflows stack channels: email warms and qualifies, LinkedIn builds familiarity, calls convert.
• Response handling and qualification — respond to inbound replies, handle objections, and qualify prospects for AEs. The goal is a held meeting, not just a reply.
• CRM hygiene — log all activities, update contact records, and maintain accurate pipeline stage data. CRM data quality is a shared responsibility with Growth Ops.
• Continuous ICP refinement — feed market feedback (objections, competitor mentions, buyer language) back to the GTM Manager to sharpen targeting and messaging.

ICP Research + List Building Workflow¶

Per the modern SDR workflow framework (Outbound Sales Pro, 2025):

1. Define ICP segments — industry × company size × motion (PLG/SLG) × tech stack.
2. Identify triggers — hiring bursts, tech installs, funding events, product changes, leadership moves.
3. Build verified contact lists — pull from enrichment tools, verify emails and direct dials, flag opt-outs.
4. Prioritize by intent — use intent signals (opens, multi-opens, page dwell) to rank the list. Call warmed accounts2–3× more effectively than cold.
5. Personalize at the right level — light personalization (10–20 seconds) for top accounts, segment-level relevance for the rest.

Sequence Management¶

Recommended 12-step starter sequence (28–32 days):

Daily SDR Rhythm¶

• 08:30 — Inbox health check, reply triage, calendar cleanup
• 09:00 — Parallel dialing block #1 (executive hours)
• 10:30 — Personalization sprints for top accounts
• 11:30 — LinkedIn touches on opened sequences
• 13:00 — Parallel dialing block #2 (timezone matching)
• 15:00 — Follow-ups, booking details, AE handoffs
• 16:00 — QA: call review, objection library update, next-day list build

Tools They Touch¶

• Sales engagement (Outreach, Salesloft, Apollo) — sequence management, cadence, email/LinkedIn/call logging
• Dialer (Coincall, Callchaser, or built-in) — parallel dialing for call blocks
• B2B data platforms (Apollo, ZoomInfo, LinkedIn Sales Navigator) — prospecting, list building
• CRM (HubSpot, Salesforce) — activity logging, pipeline management
• Deliverability tools (Parakeet, MX Defender) — domain health, warmup, spam testing
• Intent signal platforms (6Sense, Warmly) — account-based targeting and routing

How They Fit Into the Factory System¶

SDRs are the front line of revenue. They execute the outbound motion that the GTM Manager designs and the GTM Engineer builds. They turn ICP lists into conversations and conversations into pipeline. The factory model has shifted their role from "researcher and list builder" to "human qualifier and conversation driver" — because the system handles the research, enrichment, and sequencing. This is why AI SDR tools (Artisan's Ava, Apollo's Outbound Copilot) are increasingly common: they automate the research and sequence management, leaving the SDR to focus on live calls and relationship building.

Bonus: Real Job Descriptions — What Companies Actually Look For¶

GTM Engineer (from Clay Labs job posting)¶

Clay coined the term and built the role internally. Their GTM Engineer role is described as:

"Build revenue engines using AI and automation. Part AE, part SDR, part sales engineer, full-on Clay expert."

The key signal: being technically agile and creative enough to grok any use case. Clay's early hires ran "reverse demos" — solving a customer's data enrichment problem in 30 minutes or less — and realized the most fundamental skill was technical agility, not sales experience.

What they look for:
- Clay proficiency (expected given they invented the role)
- SQL and Python (38% of GTM Engineer JDs explicitly require coding)
- CRM fluency (HubSpot or Salesforce)
- No-code automation (Zapier, n8n)
- AI prompting ability
- Willingness to learn by tinkering

Growth Ops Manager (from GrowthTalent.org, 2026)¶

"Automation: shipping workflows that eliminate repetitive manual work, like lead routing, deal sync, lifecycle triggers. Data quality: making sure the CRM data is clean, structured, and useful. Reporting: building dashboards and metrics the team uses to make decisions, not the ones they ignore. Process: documenting and optimizing the handoffs between marketing, sales, product, and customer success."

What they look for:
- Marketing automation platform experience (HubSpot, Marketo)
- CRM administration and data modeling
- SQL for reporting and data extraction
- Attribution and analytics experience
- Process documentation skills

SDR (from SyncGTM, 2026)¶

"Core daily tasks: cold calls, outbound email sequences, LinkedIn outreach, lead research, CRM logging. Primary KPI: qualified meetings booked per week (benchmark: 4–6 for mid-market). Key handoff: SDR qualifies the prospect → passes to AE."

What they look for:
- Comfort with multi-channel outreach (email, LinkedIn, phone)
- CRM proficiency
- Objection handling and qualification skills
- Persistence and resilience (rejection rate is high)
- Ability to learn and iterate on messaging

How the Roles Connect in the Factory System¶

GTM Manager / Head of Growth
├── Owns strategy, ICP, pipeline targets
├── Delegates to:
│
├── GTM Engineer
│   ├── Builds workflows, automation, integrations
│   └── Feeds: enriched/profiled accounts to SDR
│
├── Growth Ops / Marketing Ops
│   ├── Maintains CRM, reporting, data quality
│   └── Feeds: clean data + pipeline analytics to GTM Manager
│
├── Content Strategist
│   ├── Creates and repurposes content assets
│   └── Feeds: content for sequences, inbound, social proof
│
└── Outbound / SDR
    ├── Executes multi-channel outreach
    └── Feeds: qualified meetings to AE, market feedback to GTM Manager

The factory works when each role operates in its lane and the handoffs between roles are clean. GTM Manager sets direction. GTM Engineer builds the machine. Growth Ops keeps the data honest. Content Strategist fuels the machine with assets. SDRs convert the output into revenue.

Sources¶

• Bloomberry, "I analyzed 1000 GTM Engineering jobs — here is what I learned," January 25, 2026. https://bloomberry.com/blog/i-analyzed-1000-gtm-engineering-jobs-here-is-what-i-learned/
• Clay, "GTM Engineering: What It Is and How to Hire in 2026." https://www.clay.com/blog/gtm-engineering
• Clay, "Sales GTM Engineering: How Clay Built the Role From Scratch." https://www.clay.com/blog/sales-gtm-engineering
• Clay, "How We Built Clay's GTM Engineering Function." https://www.clay.com/blog/how-we-built-gtm-engineering-function
• GrowthTalent.org, "Growth Operations Manager: Role, Salary, Skills (2026)." https://www.growthtalent.org/guides/role/growth-operations
• GitLab Handbook, "Marketing Operations Roles." https://handbook.gitlab.com/job-families/marketing/marketing-operations-manager/
• Outbound Sales Pro, "SDR Workflow (2025): Complete Playbook to Book More Meetings." https://outboundsalespro.com/sdr-workflow/
• SyncGTM, "What Do Sales Development Reps Do? SDR Role Explained." https://syncgtm.com/blog/what-do-sales-development-reps-do
• Copy.ai, "AI Content for B2B Marketing: Complete Guide." https://www.copy.ai/blog/ai-content-for-b2b-marketing
• Distribution.ai, "AI Content Repurposing & Distribution." https://www.distribution.ai/
• 6sense, "Marketing Operations Manager Role." https://6sense.com/guides/marketing-ops-manager/
• VisionEdge Marketing, "The Evolving Role of Marketing Operations," February 2026. https://visionedgemarketing.com/the-evolving-role-of-marketing-operations/