Staging environment
Free Lesson

Four months changed GTM engineering. The stack I run now.

Part of Building an AI GTM Engine

Hosted by Jared Waxman

Mon, Sep 28, 2026

6:00 PM UTC (30 minutes)

Virtual (Zoom)

Free to join

Invite your network

What you'll learn

Run outbound that researches between touches

Set up context, reach, judgment, scheduled routines and surfaces, starting with one repo every agent reads.

Build the five layers in the right order

Skip the agent org chart and the hundred skills, and keep a person on send for every outbound message.

Know what to leave out

Skip the agent org chart and the hundred skills, and keep a person on send for every outbound message.

Why this topic matters

In May, a campaign meant list, enrich, score, then a three-step sequence written before anyone had replied. Now agents research each lead between touches and draft every reply for a person to review. Clay, Lemlist and the CRM are still in the stack, working behind Claude. None of it works without a deep context layer, and most teams skip straight to agents. This is the setup I've run for four months, and the order to build it in.

You'll learn from

Jared Waxman

Founder, GTM Engineer School · Growth at Auth0, Okta, PubNub, Yahoo

Jared Waxman is the founder of GTM Engineer School, which has trained 265 paid students across four cohorts and is running its fifth. He spent 2016 to 2024 in developer-first GTM as VP Growth at PubNub, Head of Growth at Auth0, and in demand generation at Okta after it acquired Auth0. Before that he ran growth and ecommerce at Intuit, Adobe, LegalZoom and Yahoo. He writes the GTM Engineer Pulse, a newsletter with about 6,000 subscribers, and is an Operating Partner at Unusual Ventures.

See all products from Jared

Sign up to join this lesson

By continuing, you agree to Maven's Terms and Privacy Policy.