Where the number is stuck
A growth investment on the quarter’s clock.
AI transformation that lives outside the revenue plan dies there. The version that works is aimed by a revenue leader at the number itself - starting with which number is stuck, and why.
The transformation is a growth investment
Nobody keeps their job for bringing in AI. They keep it for hitting the number - and the AI work that survives contact with a revenue organization is the work that helps hit it. That rules out the side-project model: a separate initiative, a separate leader, a multi-year enablement arc with nothing on the board to show for it.
It has to run at go-to-market pacing, inside go-to-market priorities, led by someone who owns revenue. Which means it starts where revenue leaders start: with the metrics.
Behind every stuck metric is a constraint AI can reach
The numbers the board reads are symptoms. The work is naming the constraint underneath the one that is stuck:
A context problem
New sellers spend months rebuilding, one call at a time, what the organization already knows. Every week off ramp is pipeline pulled forward.
A propagation problem
The spread between your best rep and your median is the most expensive gap in the model. The playbook that closes it exists - in a few heads. Moving it into the system is what moves the metric.
A coverage-and-quality problem
What a program dollar returns in qualified coverage. The first place AI leverage shows up on the board, because research, personalization, and follow-through stop being headcount-bound.
“Adopt AI” is not a plan. Move this number by clearing this constraint is a plan - and a business case.
One bottleneck, one build, one quarter
Each phase of the transformation is scoped as a revenue-bottleneck project. Engineers deploy with your team, not beside it: the system gets built inside a program that moves one board metric, in the quarter it ships. The program’s return is the business case - no separate enablement budget waiting years to justify itself.
That pairing is the discipline. The transformation work and the revenue work are the same work, sequenced.
Each phase pays for the next
Clear the constraint holding the most revenue back and the next one comes into range - funded by the first, and faster to build, because the context and capability from each phase carry forward. The curve bends while the cost stays flat.
Name the number first.
We start from your board metrics, find the constraint the stuck one is waiting on, and scope the first build as the project that clears it.