after dozens of conversations with gtm leaders this year, here are 5 requirements to build an AI-native gtm org at an enterprise company:
1/ tops-down initiative (from the CEO).
sometimes it'll work to have the CRO driving it, but she *has* to have strong support from her CEO. otherwise, things fail.
doing a *truly* ai-native build touches so much (people, systems, incentives, everything) that it needs ceo support/oversight.
2/ you have to have all these departments involved or it'll fail:
- Sales leader (cro/vps)
- RevOps
- AI or GTM Eng lead
- SDR leader
- CS (if in scope)
they have to be invested, excited even! (see point 5 below)
3/ data (ugh, boring i know*)
*but truly the most important part. p0.
"the best time to plant a tree (or fix your gtm data/systems) was 20 years ago.
the second best time is today."
get started today.
4/ experiment. (9/10 things will fail)
try a bunch of things. know most won't work. don't quit, or you won't see the gains.
there is no playbook. so instead, just play and...
5/ ...have fun!
follow your curiosities. start somewhere that seems fun to *you*. personally. so many great projects in companies started as one person's personal pet project. be that person :)
––––––––––
the best example of an AI-native revenue org that i've seen lately is XBOW. we covered them on The Signal this week, give it a read (or skim the screenshots of what they've build, at least... you'll see what i mean): [
––––––––––
what would you add to the list of requirements to build (or rebuild) an AI-native enterprise revenue org?