Preview
What it is.
Alex Lindahl writes the GTM Engineering newsletter weekly, and the format is a playbook you can follow: replace this tool with that stack, wire this agent into that workflow.
Recent issues have covered replacing ZoomInfo with Clay, giving agents an email address, and cloning a competitor's programmatic SEO system.
It's free and the archive is open, which makes it a reference more than a read.
What you get.
- Weekly build playbooks with the tools named
- Clay workflows and prompts you can copy
- Tool replacement guides, including what gets worse as well as better
- His read on where agent tooling is heading for GTM teams
- Free access with an open archive
OUR PICKS
Editions we'd start with.
Playbook: how to replace ZoomInfo with Clay and Exportly ↗
The most-copied build on the list, and he says what gets worse as well as better.
31 learnings from 2 years in GTM Engineering ↗
The retrospective to read first if you're new to the discipline.
Agents now have an email address ↗
Use cases with Clay, and a good sample of how concrete the guides get.
Why every GTM org will need an AI skill marketplace ↗
His argument about how GTM teams will share reusable AI work.
Agents are growing up. They now need a phone line. ↗
Where voice fits into agent workflows, which most GTM writing skips.
Subscribe at the source.
Subscribe
Do the playbooks assume a stack?
Are the steps complete?
Can Clay replace a data vendor like ZoomInfo?
What should a GTM engineer build first?
How do agents fit into a GTM stack today?