04 / AI AND THE GTM STACK
Most teams bought the tools before they defined the work. The tools then did the undefined work faster.
SOUNDS LIKE YOUR TEAM
“We bought AI tools and nothing measurably changed”
“Reps still keep the real pipeline in a spreadsheet”
“Half the stack goes unused and I cannot say which half”
“I cannot tell the board what is working, what is not, or why”
WHAT IS ACTUALLY BROKEN
Where AI genuinely earns its place, where a human still carries more weight, how to put it in without automating your existing mess, and what the stack should look like once the process is defined.
AI does not fix a short column. It loads it faster.
Artifacts, not recommendations. Every one of these is a thing your team holds and runs after I am gone.
THE FRAMEWORK
none yet.
THE ARTICLES THAT PROVE IT
none yet. This is the newest part of the practice and the writing is still coming.
BEST FOR
Teams who have tried the tools and suspect the problem is upstream of them.
NOT FOR
Teams looking for a tool recommendation. The recommendation is downstream of the process, and the process is the work.
Thirty minutes, no deck. Or score your own go-to-market first and find out which of the five systems is carrying the number.
You will speak with me, not a partner who hands you to someone else afterwards.
THE OTHER THREE COMPONENTS
01
GTM Architecture
Who you target, how you reach them, what a stage means, and whether the forecast is a number or a feeling.
02
GTM Enablement
Product fluency that holds under pressure, the motion written down, and the assets that stop getting rebuilt every week.
03
The Leader Layer
You were promoted for selling. Running a team is a different job, and most companies hand it over with a title and a dashboard.