Weekday live batch
8:30–9:30 AM EST
US Eastern · Mon–Fri
- Starts
- Monday
- Classes
- Mon–Fri5 days a week
- Seats
- 20Per batch
Next live batches start 4 Jan 2027
60 days to become a GTM engineer: 30 days of live training, then two 15-day build projects. Built for non-technical learners, with no code anywhere. US$200, or US$50 self-paced.
The system you’ll build, live
Illustrative simulation. In the program you build these checks yourself, layer by layer.
A 1-hour live session every weekday, then two portfolio projects.
For the full 60 days.
No Python, SQL, JavaScript, terminal or GitHub.
New live batches start every two months in 2027, with live, instructor-led classes five days a week. All times are US Eastern.
Weekday live batch
8:30–9:30 AM EST
US Eastern · Mon–Fri
Weekday live batch
10:30–11:30 AM EST
US Eastern · Mon–Fri
New batches start every two months. Times and dates are US Eastern. 20 seats per batch.
For anyone who can’t find a live batch that fits, or wants to start right away and learn at their own pace. 30 days of access.
US$50
Want to judge the quality first? Watch sample class recordings or read testimonials
Live every weekday, built around one real company, and judged on what you ship.
A 1-hour live session every weekday, Monday to Friday, plus 2 hours of homework. Five phases, each ending in a portfolio deliverable.
After training you build two complete systems: a beginner outbound system and an advanced AI-assisted engine with human approval.
When a step needs logic, a formula, a workflow or an integration, you describe it in plain English to an AI builder and check the result.
You adopt one real B2B company on Day 2 and build everything for it, so your portfolio tells one story with real numbers.
Tools change every 6–12 months; the layers don’t. You learn what each layer is for, then the tool that does it today.
Five phases, 30 live 1-hour sessions, five portfolio deliverables. Open any day to see what you learn, build and ship.
Every session0–5 homework review5–20 concepts20–35 live demo35–55 guided lab55–60 exit ticket
By Day 6 you have a company, a strategy and a context pack that every later AI step reads from.
ShipsStrategy brief + context pack
Here are 10 job descriptions. For each, list the tools named, map each responsibility to one of these layers [paste layers], and say whether the role can be done without coding. Return a table.
Pressure-test this company as a GTM practice target. Score 1–5 on: clear buyer, public pricing, observable signals, reachable decision-makers, US/EU market. Tell me the weakest point and whether to switch.
Here are 10 case studies from [company]. Find the patterns in company size, industry, tech stack, trigger event and buyer title. Propose an ICP, 3 segments and 5 disqualifiers. Quote the evidence for each.
For a company selling [product] to [persona], list 10 buying signals. For each: why it creates urgency, where it can be detected without code, how many days it stays relevant, and a one-line message angle.
Interview me one question at a time to build a context pack for [company]: ICP, personas, offers, proof points, competitors, voice rules and banned claims. When done, write each as a separate section of no more than 200 words.
Act as a skeptical VP of Sales at [company]. Read this strategy brief and give me the 5 hardest questions you’d ask before funding this outbound motion.
By Day 13 you have 300 scored accounts and 600 verified contacts, with a cost report. Every formula, filter and research column is written by describing it to Clay’s AI tools.
ShipsScored account intelligence table
Here is a benchmark of 4 providers on 50 contacts [paste]. Calculate coverage, verified rate and cost per verified email for each, recommend a waterfall order, and explain the trade-off in 3 sentences.
(Clay formula generator) Return ‘Tier A’ if employee count is 50–500 and country is US, UK or Germany and the tech stack includes HubSpot; ‘Tier B’ if only two of these are true; otherwise ‘Exclude’.
I’ll paste my Clay waterfall settings and results. Find where I’m wasting credits, suggest a cheaper order and the ‘run only if’ conditions to add, in plain English I can copy into Clay.
(Claygent) Visit {{domain}}. Answer only from the website. 1) Does the company show public pricing? Yes/No/Unknown. 2) Pricing model: per seat / usage / flat / unknown. 3) Paste the URL where you found it. If not found, answer Unknown. Do not guess.
Score this account 0–100 for fit using this rubric [paste]. Return: score, the 3 strongest reasons, the biggest risk, and one sentence a sales rep can read.
Build me an automation: when [trigger] in [tool], do [action] in [tool]. Match records on [field]. If the record exists, update it; never create a duplicate. Tell me exactly which steps to click and what to test.
Audit this table export [paste sample]. Find duplicates, missing fields, suspicious emails and rows that break my ICP rules. Return a fix list sorted by impact.
By Day 19 you have warm sending infrastructure, three signal-based sequences that passed an AI quality check, and a multichannel plan with risk limits.
ShipsDeliverability runbook + launch-ready campaign
I want to contact [N] people a month over [X] working days. Calculate domains and mailboxes needed at 25 sends per mailbox per day, and give me a warmup and ramp schedule week by week.
Review these sequencer settings [paste or screenshot]. Flag anything that risks deliverability: volume, timing, tracking, links, signatures, unsubscribe. Rank by risk.
Using our context pack, write a 4-step sequence for [persona] triggered by [signal]. Email 1 under 80 words: observation, implication, offer, one easy question. No flattery, no feature lists, no ‘quick call’. Give 2 subject lines per email.
(Grader) You are a strict reviewer. Grade this email against the rubric [paste]. Check every factual claim against the research data [paste]. Return: PASS or FAIL, failed criteria, the exact sentence that failed, and a fix.
Design a 14-day multichannel cadence for [persona] after [signal]: email, LinkedIn and one call. For each touch give day, channel, goal and a one-line message. Keep LinkedIn under 20 actions per day.
Turn my notes [paste] into a deliverability runbook a new team member could follow: setup checklist, daily checks, weekly checks, and an incident plan with exact thresholds.
By Day 25 you have a signal-triggered play that runs on its own, writes to HubSpot and alerts Slack, all built without code.
ShipsSignal-triggered play with CRM write-back
Here are 30 signal events [paste]. For each, decide: real buying signal, false positive, or too old to use. Explain in one line and give me the precision rate.
(Sculptor) Build a workflow: when an account joins the ‘Tier A – Hiring SDRs’ segment, find the VP Sales and Head of RevOps, verify emails with the waterfall, write a first email using the Knowledge Hub, and stop if no verified email is found.
I don’t code. Walk me step by step through building this in [n8n/Zapier]: [describe flow]. For each step tell me the node or app, what to fill in each field, and how to test it. Add a step that checks for an existing record before creating one.
Design a HubSpot property dictionary for an outbound program at [company]: property name, type, allowed values, who/what writes it, and whether automation may overwrite it. Keep it under 25 properties.
Write routing rules for inbound leads at [company] in plain English: by region, company size and existing owner, with a fallback. Then turn them into a decision table I can paste into a Sheet.
Here is my play’s architecture [paste]. List every handoff, what could fail at each one, how I’d notice, and the fix. Return a table.
You build AI agents and rep-facing tools entirely through prompts, Claude Projects, Skills and connectors, then put them into production safely.
ShipsPortfolio page + Project 1 plan
Here is my prompt and 5 outputs where it failed [paste]. Diagnose why each failed, rewrite the prompt using role / context / task / rules / format / examples, and give me 3 test cases to check the fix.
Create a Claude Skill called ‘account-brief’. When given a company domain, pull the company and contacts from HubSpot, add Clay research, and write a one-page brief using our context pack: why now, likely pains, who to contact, opening line, 3 discovery questions. Never invent data; mark gaps as Unknown.
Here are 20 drafts my team rejected, with their reasons [paste]. Group the reasons into patterns, then propose specific changes to my writer prompt and grader rubric to prevent each pattern.
Here are this week’s campaign numbers [paste]. Write a 150-word update for a client: what happened, what it cost per meeting, what we’ll change next week, and one risk. No vanity metrics.
Act as a hiring manager for a GTM engineer role. Review my portfolio page [paste]. Tell me what would make you invite me to interview and what would make you skip me.
Days 31–60. Two 15-day projects for your adopted company, each with written pass criteria and a 100-point rubric.
For your adopted company (or a real client who agrees in writing), build and launch one complete outbound system for one segment and one signal: accounts that are actively hiring for the role your product helps. Built in Clay, the sequencer, HubSpot and Claude, with no code.
It forces every fundamental into one chain (strategy → data → signal → copy → deliverability → CRM → results) and ends in real numbers. Hiring signals are free to detect with Claygent on careers pages, so no paid signal tool is needed.
Rubric (100 points) Strategy 20 · Data quality 20 · Deliverability 15 · Copy and grader 15 · CRM integrity 10 · Measurement 10 · Communication 10
Stretch goals A/B test two signals (hiring vs recent funding); add a manual-assisted LinkedIn step; compare Clay Sequencer with Instantly/Smartlead on the same list.
Build an always-on engine that watches 3 signal sources, researches and scores each account, drafts multichannel outreach with AI, checks every draft with an AI grader, sends it to a human in Slack for approval, then writes everything to HubSpot and a cost ledger and produces a weekly learning report.
It is what generic “AI SDR” products promised and failed to deliver safely. It proves the skills Clay’s hiring guide values most: reliable handoffs, AI output you can check, human control and cost awareness, and mirrors the “signal engine” take-home that 2026 interview guides benchmark.
Rubric (100 points) Architecture and handoffs 20 · Reliability 20 · Prompt and grader quality 20 · Human approval and governance 10 · Cost control 10 · Learning loop 10 · Communication 10
Stretch goals Add the inbound path with under-5-minute response; package the research step as a Claude Skill reps use on demand; compare the same play built in Clay Workflows vs n8n.
Every tool is used through its interface or by prompting. Most run on free plans or trials.
Pick a third portfolio project. Each ends in a number a hiring manager or client cares about.
Hiring and client work are decided by systems with numbers, not certificates. So ours require both.
All 5 training deliverables + Project 1 pass.
Project 2 pass.
Project 2 score of 85 or more + a live result for a real company or client.
A Loom of 5 minutes or less, a one-page case study with real numbers, the architecture map, the prompt library with versions and pass rates, and the logs.
Every learner who passes gets a Stable GTM certificate with their name, their tier and a certificate ID they can share on LinkedIn.
Included with every live batch, not the self-paced plan. We help you get hired; we don’t promise a job.
We review and sharpen your LinkedIn profile so it presents you as a GTM engineer, with your projects and results up front.
We prepare you for GTM engineering interviews: how to walk through your portfolio, explain your systems and handle take-home tasks.
You get our list of companies and agencies that typically hire GTM engineers, so you can reach out to them directly.
We run a community where we post every GTM engineering job we find posted online, with direct links to apply, so you can keep applying after the program.

Founder and instructor, Stable GTM
Yogesh teaches every live class himself. He spent 4+ years in sales at companies like Freshworks, Razorpay and Glider AI, so he knows what a sales team needs from a GTM system.
For the past two years he has worked as a GTM engineer with 30+ companies, startups and agencies across the US and Europe, building the kind of systems you build in this program.
Sales experience atFreshworksRazorpayGlider AI
Follow @gtmwithyogesh on InstagramEvery batch gets far more inquiries than seats, so we choose who joins. We work only with people who are passionate about GTM engineering and bring real energy to learning it.
If that sounds like you, you’re in the right place. We work with serious people, and that’s why our learners deliver good results. No coding experience needed.
Join a live batch for the full program, or learn self-paced from the class recordings. Prices in US dollars.
US$200 Price in US dollars
30 weekdays of live training and two 15-day build projects. The full curriculum, nothing held back.
Only 20 seats per batch. No refunds once your seat is booked, except in special cases before the program starts. ·
US$50 Price in US dollars
For anyone who can’t find a live batch that fits, or wants to start right away and learn at their own pace. 30 days of access.
Start any time. Non-refundable once you get access.
Non-technical learners who want to become GTM engineers. The best-fit roles are outbound, growth, campaign and agency GTM engineering, fractional work and in-house “GTM operator” roles. About 41% of postings ask for SQL; we don’t teach it, and we say so upfront. You win these roles with a portfolio that shows strategy, clean data, safe deliverability, tested AI prompts and measured results.
Something else on your mind? Click Inquire now and our team will get back to you.
Choose a live batch or self-paced, then share your name, email and LinkedIn profile. Our team will get back to you with everything you need to join.
Live batches: US$200
·