Courses

Every course builds one thing end to end. You follow the lessons in order, and you finish with a working automation — a list you can send, a table that scores itself, or a prompt chain your reps can run every morning.

Start with GTM Engineering Foundations if you want the concepts before the clicks. The Core Concepts section is the reference behind all of it.

Start here

Pick by what you want to walk away with:

How a course is structured

Every course page follows the same shape, so you can judge fit before committing credits:

• About this course — what it covers, who it is for, what it costs, and any plan requirement
• Skills you will gain — the capabilities you leave with, stated as things you can do
• In this course — every lesson, grouped into blocks, with an outcome and a time estimate. Published lessons are links; unwritten ones stay listed so you can see the shape of what is coming
• What you will have built — the artefact at the end, described concretely
• Before you start — what you need in place first
• Reference behind this course — the Core Concepts and MCP tool pages the lessons link into

Lessons themselves open with a spec box — surface, level, actions used, credits, prerequisite — and never re-explain a feature. They link to the reference and move on.

The four-stage framework

Every course maps onto the same model, taught in full in GTM Engineering Foundations and applied in SyncGTM 101:

Find → Research → Enrich → Outreach

Find gets rows into a table. Research fills in what no database holds. Enrich fills in what they do hold. Outreach turns the result into something a prospect actually receives. Once you know which stage a problem lives in, you know which lesson you need.

Each stage costs more per row than the one before it. That single fact drives nearly every recommendation in the library: filter early, gate before the expensive step, and never personalize a row you have not verified.

All courses

Foundations

Concepts and mechanics. Do these once; they pay off in every course below.

Build the list

Getting the right rows, with a way to reach them.

Trigger on what changes

Plays that fire on an event instead of running against a static list.

Keep the system honest

The maintenance layer. Skip it and everything above decays.

Run it from an AI client

The same outcomes, driven by conversation instead of columns. Start with the mini course if you want the tool map before the workflows.

Suggested paths

If you would rather follow a track than pick individually:

What the levels mean

Levels describe the shape of what you build, not how long you have used the product. A beginner course still ships something usable.

Surface tells you where the work happens — in the Sync GTM app, through the MCP server from an AI client, or both. Courses marked App + MCP build the same outcome twice so you can pick the one that fits your team.

Credits

Courses that spend credits state a budget on the course page and a per-lesson estimate in each lesson’s spec box. Estimates assume a typical hit rate — waterfall enrichments only bill when a provider returns a result, so a run on a well-known segment costs less than the same run on a long tail.

Check your balance any time from Credits, or by asking your MCP client to run check_credits before an expensive lesson.

Where to next

• Core Concepts — the reference behind every course
• MCP Tools — inputs, outputs and credit cost for every tool
• Automation templates  — prebuilt versions of several course outcomes
• GTM agents  — installable skill files for the MCP workflows