← ClaudeAtlas

gtm-engineeringlisted

Designs the technical infrastructure that powers go-to-market - lead scoring models, CRM enrichment pipelines, lifecycle automation, attribution, and reverse ETL. Use when: gtm engineering, revops engineering, lead scoring, lead routing, CRM data pipeline, marketing automation architecture, attribution model, reverse ETL, customer data platform, growth engineering.
varunk130/claude-code-skills · ★ 1 · AI & Automation · score 72
Install: claude install-skill varunk130/claude-code-skills
# GTM Engineering Designs the technical and data infrastructure that powers a modern go-to-market motion - the systems behind lead scoring, routing, enrichment, lifecycle automation, attribution, and the data flows between product, CRM, marketing automation, and the warehouse. This is **not** GTM strategy (positioning, channels, messaging). This is the plumbing that makes GTM strategy actually executable at scale. ## When to Use This Skill - Designing a lead scoring or PQL/MQL model - Architecting CRM ↔ warehouse ↔ MAP data flows - Building lifecycle automation (onboarding, expansion, churn-risk) - Setting up multi-touch attribution - Planning reverse ETL from warehouse to Salesforce/HubSpot/Marketo - Auditing a broken or fragmented RevOps stack - Standing up the GTM data layer for a new company or motion ## The Problem Most GTM stacks are an accidental archaeology of point tools wired together with Zapier and hope. Lead scores don't reflect actual conversion data, attribution models contradict each other, sales reps work the wrong leads, and nobody can answer "what does a good lead actually look like?" The strategy doesn't fail - the execution layer does. GTM Engineering is the discipline of treating the revenue stack like a product: with schemas, contracts, observability, and tested logic. ## What You'll Need **Critical inputs (ask if not provided):** - Sales motion (PLG, sales-led, hybrid, channel) - Current stack (CRM, MAP, CDP, warehouse, product analytics) - Def