.svg)
Ignite Your GTM With AI, Chapter 7: Why Sales Execution is a "Chaotic Art Studio" (And How to Engineer a High-Performance Engine)
Welcome back to our deep dive into "Ignite Your GTM With AI." We have explored the landscape of 2025, the data maturity models, and the evolving role of RevOps. Now, we arrive at the heart of the revenue organization: the deal cycle itself.
In Chapter 7: Sales Execution & Deal Management, we strip away the veneer of the modern sales floor to reveal a messy truth. For decades, sales execution has operated less like a factory and more like a "chaotic art studio."
With insights from heavy hitters like Kyle Norton (CRO at Owner), Mark Turner (VP of RevOps at Demandbase), Brian Dietmeyer (CEO at Closestrong), Navin Persaud (VP of RevOps at 1Password), Oran Akron (Head of AI GTM at Monday), and Kevin Chu (Operations Engineering at ElevenLabs), this chapter argues that the "lone wolf" era is over.
We are moving toward a world where the deal cycle is not a series of subjective guesses, but a system of orchestrated data flows.
The Monday Morning Ritual (and Why It’s Broken)
We all know the rituals. The weekly forecast call, a subjective interrogation where confidence is currency. The pipeline review, often a painful exercise in data archaeology where a nervous rep updates CRM fields while leadership watches. And finally, the end-of-quarter scramble, a heroic attempt to salvage deals that actually went sideways six weeks ago.
This model is collapsing under its own weight.
The core of this breakdown is what Brian Dietmeyer identifies as the "strategy-to-tactics gap." It’s a story you’ve likely lived: The executive team announces a bold new strategy at the Sales Kickoff (SKO). Product marketing builds beautiful decks. Everyone cheers.
Then, on Monday morning, the reps go right back to selling exactly the same way they did on Friday.
The strategy evaporates the moment it hits the field. This isn’t because your reps are insubordinate; it’s because of a flawed architecture. We are operating under an "old school philosophy" that places an impossible burden on the individual rep to absorb complex strategic shifts while juggling a dozen other priorities.
The "Project Manager" Trap
Navin Persaud at 1Password pinpoints the most misunderstood part of the modern seller’s job: they aren't just selling; they are project managers navigating a labyrinth of internal and external processes.
Deals rarely fall apart because the rep couldn't pitch the value. They unravel in the treacherous terrain of commercials, legal reviews, procurement, and the notoriously time-consuming CPQ process. A rep might get a "verbal yes" from a VP, but because no one mapped the procurement process, the deal stalls for six weeks while three surprise approvals surface.
Mark Turner at Demandbase has quantified the cost of this friction. The average enterprise rep spends 65% of their week on non-selling activities—CRM hygiene, internal meetings, deal configuration, and approval workflows. Gartner and Forrester put that number even higher, at 75%.
We are asking reps to be strategic consultants, but we are burying them in administrative cement.
The "Michael Jordan" Fallacy
To solve this, most organizations try to hire better reps. They look for the "Michael Jordans"—the intuitive superstars who can carry the team with individual brilliance.
In the chapter, we compare this to the pre-Phil Jackson Chicago Bulls. Jordan’s brilliance got them to the playoffs, but not to the championships. It was only when Phil Jackson introduced the triangle offense—a system that amplified talent rather than depending on it—that they won six rings.
The same principle applies to your GTM motion. You can build a $20M ARR company on the backs of a few "Michael Jordans" who use relationship magic and improvisation. But to scale to $100M and beyond, you need the Phil Jackson approach.
You need a system where, if your best rep leaves, the revenue engine doesn't break.
Currently, our systems do the opposite. We explicitly reward ignoring the process. The rep who closes $3M but leaves their pipeline in shambles is celebrated; the rep who has perfect data hygiene but misses quota is put on a plan. As Kyle Norton points out, this creates a culture where the best storytellers win promotions while the best operators burn out.
The Intelligence Architecture Opportunity
Hiring more managers to pester reps about CRM updates won't solve this. The answer lies in Intelligence Architecture.
This is a shift from viewing the deal cycle as a series of human tasks to viewing it as a "system of data flows and decision points to be orchestrated." Kevin Chu describes the technical foundation for this: treating the entire GTM operation as a "data pipeline."
Because modern AI can transform unstructured conversation data into structured, high-fidelity information, the system itself becomes the source of truth. This creates a "neutral spinal cord" for the business.
Chapter 7 outlines four specific dimensions where this new architecture changes the game:
1. Context Engineering
Generic AI gives generic advice. To get reliable guidance, you need Context Engineering. This means feeding the AI a rich, precisely engineered diet of information. Brian Dietmeyer’s team uses a "Precision Guidance Layer." They interview a company's deal desk lead, codify their specific requirements and common pitfalls, and embed that logic into the AI. The result? The AI doesn't just know how to sell; it knows how to sell your product, in your market, using your strategy.
2. Human-AI Orchestration
We need to stop expecting AI to do everything and start using it for what it's good at. Kevin Chu introduces the "3 out of 5" concept. AI is perfect for tasks where "good enough" is better than nothing—admin work, filling out fields, capturing basic insights. This frees humans to focus on the "5 out of 5" work: negotiation, persuasion, and strategy. Brian Dietmeyer notes that his platform handles initial coaching for 80% of the pipeline, only looping in human managers for the top 20% of strategic deals. This makes manager 1:1s 3 to 5x more effective.
3. Signals Mapping
Traditional sales management is reactive. We find out a deal is dead weeks after the champion stopped replying. An intelligent system uses Signals Mapping to detect behavioral patterns. It’s not just about the "last contacted date." It’s about the subtle signs of decay: a pushed close date, a lack of two-way communication, or a missing stakeholder. Mark Turner is building systems that listen for risk flags within conversations—mentions of budget freezes or new competitors—triggering interventions while the deal can still be saved.
4. Transparent Reasoning
Black-box AI is useless in sales. If a system gives a deal a score of 72, the rep needs to know why. Transparent Reasoning means the system explains its logic: "Score is 72% because an economic buyer is confirmed... but it is penalized because no legal review has been initiated." This builds trust and turns the forecast from a guessing game into an evidence-based discussion.
The Engine for Your Intelligence Architecture
The insights in Chapter 7 make one thing clear: You cannot achieve this level of execution by simply buying a tool that records calls or a tool that helps with forecasting. You need an architecture that connects them.
This is where Momentum enters the picture.
Momentum is the execution layer described in this chapter. We are the "neutral spinal cord" that connects your disparate systems.
- We Automate the "3 out of 5" Work: Momentum captures the "high-cardinality structured data" Kevin Chu describes, automatically updating your CRM with granular details from calls and emails so your reps don't have to.
- We Bridge the Strategy-to-Tactics Gap: By embedding your specific methodologies (like MEDDIC or SPICED) directly into the workflow, Momentum ensures that the strategy announced at SKO is the one executed on Monday morning.
- We Enable Signals Mapping: Momentum listens for the risk flags—the stalled stages, the missing executive contacts—and routes those signals instantly to the people who can act on them.
As Kyle Norton asserts, evolving from a people manager to a "systems engineer" is no longer a niche skill; it is a "mandatory skill set" for any leader who intends to compete.
The competitive advantage of the future will not come from hiring a better "Michael Jordan." It will come from building a better Chicago Bulls—a system where reliable execution is the default, not the exception.