Reference file

Emerging Practices: AI-Augmented Methodology

emerging-practices-ai-augmented-methodology.md

Emerging Practices: AI-Augmented Methodology

On-demand reference for the sales-methodology skill.

The AI-Augmented Sales Day (Kyle Norton / Owner.com)

Kyle Norton runs a 100+ AI-infused sales team at Owner.com. His framework for what a rep's day looks like when AI is properly embedded:

Morning (automated by AI):

  • Pre-call research: AI prepares briefing packs for every scheduled meeting (company context, contact history, recent signals, recommended talk points)
  • Account prioritisation: AI scores today's pipeline by urgency and signal strength
  • Admin clearance: CRM updates, activity logging, and data enrichment happen automatically overnight

Core hours (human-led, AI-supported):

  • Discovery and negotiation calls (the 70-80% revenue-generating time target)
  • AI provides real-time coaching prompts during calls (if conversation intelligence is deployed)
  • Post-call: AI generates summary, updates CRM, drafts follow-up email for rep review

End of day (automated by AI):

  • Pipeline snapshot updated
  • Next-day prep begins automatically
  • Stale deal alerts surfaced for tomorrow's action

The target: reps spend 70-80% of their time on revenue-generating activities. Current industry average: 30-40%. The gap is filled by automating research, admin, and data entry — not by automating the human conversation.

Bridge to SPICED: the AI handles data collection and preparation. The rep brings SPICED qualification skill, judgement, and human connection. AI can score deals on SPICED dimensions, but the rep runs the discovery.

Source: SaaStr AI Agent Playbook, Kyle Norton / Owner.com case study


Norton Framework Additions (Source: Kyle Norton / Aviv Canaani, Revenue Leadership Podcast, 2026)

Methodology as Architecture vs. Craft

Two modes of methodology implementation:

Craft Mode: Great reps execute SPICED/MEDDIC well because they're skilled. Depends on individual talent.

Architecture Mode: Systems ensure average reps execute SPICED/MEDDIC consistently. Depends on process design + tool enforcement + coaching cadence.

Architecture mode scales. Craft mode doesn't.

Implementation Principles:

  • Embed methodology in CRM (required fields, stage gates, scoring)
  • Automate methodology coaching via deal review templates
  • Use AI to evaluate SPICED completeness before stage advancement
  • Measure methodology adoption as a leading indicator, not just outcomes

Anti-Prospecting Qualification Gate: High SPICED thresholds reduce proposal churn. Use methodology to DISQUALIFY fast:

  • Kill deals with SPICED <4 after discovery
  • This frees rep time for higher-quality opportunities
  • Productivity play: fewer deals worked, but higher conversion on the deals you do work

Self-Reinforcing Methodology Adoption Loop: Better qualification → faster velocity → better results → higher rep trust → more adoption → better qualification → (repeat)

"Show, Don't Demo" Methodology (Donnelly, E62)

In low-trust, noisy AI markets, stop claiming and start proving.

The approach:

  1. When a prospect books a demo, build a custom AI agent using the prospect's public knowledge base within 24 hours
  2. Show the prospect how THEIR specific use case would work — not a generic demo environment
  3. Generic demos create generic trust. Custom proof creates specific confidence.

Extended "show me" philosophy:

  • Tell prospects to become customers of your existing clients: "Go to [client] and buy something. See how they upsell you."
  • One prospect tested a client's experience, found issues — turned into a teaching moment about configuration choices
  • Build time has collapsed with AI. What took weeks now takes hours.

When to deploy:

  • Noisy markets where every competitor claims the same thing
  • AI/tech sales where the product can be demonstrated with prospect data
  • Deals where trust is the bottleneck (not feature comparison)

CRM tracking: Add a field custom_proof_delivered (Yes/No/Date) to track whether the "show, don't demo" approach was used and its impact on win rate.

Cognitive Atrophy Warning for AI-Assisted Methodology (Donovan, E61)

One CRO removed an AI tool that auto-extracted MEDDIC fields from call transcripts. The tool worked perfectly — but the AEs stopped thinking critically about their deals. They became passive consumers of AI-generated qualification.

The principle: AI that removes cognitive load can also remove cognitive development.

Implementation rule for MEDDIC/SPICED automation:

  • Use AI to SUGGEST methodology scores, not auto-populate them
  • Require reps to CONFIRM or OVERRIDE AI suggestions with their own reasoning
  • Build "why do you agree/disagree?" prompts into the workflow
  • Track override frequency — too few overrides means reps aren't thinking

The Anti-Prospecting Thesis (Canaani, E64)

The myth: "You're not a real AE if you don't prospect."

The reality:

  • 80-90% of closed revenue comes from inbound (Canaani's data)
  • Salesforce State of Sales: reps spend only 28% of their week actually selling
  • Paying €250-300K OTE for prospecting = failure of resource allocation

Why AEs are bad prospectors:

  • Not getting the repetitions (BDRs do this full-time)
  • Don't actually want to do it (misaligned motivation)
  • BDRs are motivated differently — their #1 goal is to stop being a BDR

Implication for methodology: Methodology training should focus on CLOSING skills (discovery, qualification, negotiation), not prospecting skills. Invest prospecting methodology training in the BDR team, not the AE team.

Supporting data:

  • 6sense: 83% of the time, the buyer initiates first contact
  • Gartner: self-navigating buyers complete high-quality deals 65% of the time vs. 24% in sales-rep-led purchases
  • HubSpot: inbound leads cost 61% less