Skills · GTM Engine · Open Source
A senior GTM engineer, written down.
GTM Engine is a Claude Code skill that designs the complete revenue machine for a specific brand — lead collection, enrichment, scoring, nurture, outbound infrastructure, demand layers, tool stack, budget, and a 90-day build order. Its operating beliefs: signals over static lists, systems over headcount, feedback loops over gut feel.
It ships as a skill file plus a 41KB engineering playbook, demand-layer modules, budget-tiered tool stacks, a plan template, a worked example, and a full B2C/DTC re-mapping.
Part of Proofstack · skills/gtm-engine
The premise
"Most GTM plans fail at the fork, not the execution — the wrong motion for the TAM, scaled diligently."
So the skill decides the shape of the motion before writing a single tactic. Five forks drive every downstream section — and they're the same forks a senior operator runs through in the first hour of any engagement:
01 · TAM size class
Under 2,000 accounts → low-volume high-touch. 2k–20k → hybrid. Over 20k → programmatic. The single most important fork — a small-TAM brand handed a volume plan is malpractice, and it's the most common mistake in outbound.
02 · Deal-size class
ACV under $3k → automation-only with PLG leanings. $3k–25k → hybrid. Over $25k → human-heavy fast lanes with a phone layer. Touch budget follows deal size, not ambition.
03 · Buyer geography
Compliance posture (GDPR/CASL) and channel choice follow where the buyers actually are — EU-heavy books shift toward LinkedIn-first motions and EU-native data providers.
04 · Signal map
The brand's 5–8 strongest buying signals — hiring, tech installs, funding, vertical-specific tells — because signals beat static lists everywhere, at every budget.
05 · Demand layers
Which modules beyond cold outbound apply: social listening, community-led growth, referrals and advocacy, partnerships, paid/ABM, PLG. An outbound-only plan is usually an incomplete plan.
What the plan contains
01
The volume math, chained
Goal → prospects needed → sends per day → inboxes → domains → cost. Every number derived from the one before it. Most GTM plans hand-wave this chain; this skill refuses to — if the math doesn't chain, the plan doesn't print.
02
Outbound infrastructure spec
Lookalike domains (actual name suggestions), inbox architecture, warm-up protocol, deliverability rules, and example sequences written in the brand's plausible voice — each email anchored to a specific signal, 50–90 words.
03
Tool stack with budget honesty
Every pick gets a brand-tied reason and a budget tier (bootstrap / funded / scale). Prices decay, so the skill spot-checks current pricing for the expensive picks — or labels the budget "verify current pricing" and dates it.
04
The 90-day roadmap
Sequenced build order that starts from what the brand already has — existing lists, traffic, content, burned domains included — instead of pretending everyone starts from zero.
05
B2C/DTC re-mapping
Consumer brands don't get force-fit into a B2B template: a dedicated reference re-maps every stage to list growth, zero-party data, RFM/lifecycle segmentation, creator and wholesale outbound, and retention ops.
Why trust it
Written by an operator, for the machine that replaced his team.
This skill encodes a decade of running growth systems at scale — and it's the same design discipline behind the pipeline layer of my one-person marketing function and the GTM machine being built at Grovio Labs. The benchmarks, anti-patterns, and volume math in the playbook are the ones I actually use.
Like everything else here, it's brand-agnostic and free. Point it at your brand, give it your goal and budget, and it produces the plan a senior GTM engineer would charge five figures for — with its assumptions labeled, so you can check them.
Newsletter
The Autonomous Marketer
The decade of marketing I wish someone had written down. Sent when I have something real to say — not on a schedule.
Subscribe on SubstackFree. Unsubscribe anytime.