Your AI Policy Is a Competitive Disadvantage [65]
This episode explores why AI policies in revenue organizations are often competitive disadvantages, arguing that centralized corporate AI strategies neglect go-to-market needs and that most bans are outdated decisions rather than informed risk assessments. The hosts advocate for department-specific AI governance owned by RevOps, with explicit review dates that force legal to re-evaluate restrictions.
Summary
The episode begins with Tim's observation from a GTM leadership dinner where only 2 of 20 revenue leaders knew about EU AI Act labeling requirements, despite all having AI mentions in board decks. This illustrates a gap between "loud ambition" and "thin fundamentals" in how companies approach AI strategy.
Nate and Ava then discuss how AI policies, typically created by product and data science departments, fail to address go-to-market-specific challenges. Product AI is framed as a build question, contract AI as a liability question, but go-to-market AI is fundamentally a conversation question involving customer voices, recordings, and buyer data. The hosts argue that policies created outside revenue functions are inadequate because they don't account for the unique compliance and operational needs of sales and pre-sales teams.
They identify a critical pattern: centralized strategies allocate only a paragraph to go-to-market while requiring substantial legal infrastructure around consent, data retention, and regional compliance (like EU requirements for participant consent). Rather than accept blanket bans on call transcription, the hosts argue that compliant solutions are achievable—demonstrating a 12-person SE team's successful setup in three weeks.
On governance structure, they debate ownership, settling on RevOps as the "translator" between legal's rules and what SEs can execute operationally. They also distinguish between strategy (governance, approval workflows, vendor flexibility, monitoring) and use-case shopping lists.
The hosts defend legitimate brakes by sharing a cautionary story: an AI-drafted response fabricated a non-existent contract clause, which the customer's procurement found first. This reinforces mandatory human review as permanent policy, not a phase to outgrow.
The core recommendation is a one-page departmental AI position with three lists (allowed by default, allowed with review, blocked), one named owner, and crucially, review dates on blocked items. The strategic insight is that most bans persist not from active decisions but from decisions never revisited—and that forcing legal to defend blocks in writing nine times out of ten results in approval.
About this episode
Ava comes back from a GTM leadership dinner where almost nobody knew the new AI labeling rules — and where one leader used AI as a sparring partner while another had ten agents calling prospects. She and Nate argue about blanket transcription bans, who should own AI for the revenue org, and where corporate brakes actually earn their keep.
Key Insights
- Most corporate AI bans on call transcription are not informed risk decisions but outdated decisions that were never revisited—forcing legal to explicitly re-authorize them in writing results in approval nine times out of ten.
- Centralized AI strategies created by product and data science departments fail go-to-market functions because they treat AI as a build or liability question, when revenue operations face a unique 'conversation question' involving customer data, recordings, and buyer intelligence.
- An SE director's AI-generated response fabricated a non-existent contract clause with confident formatting, which was caught by the customer's procurement team first—demonstrating that permanent mandatory human review is required for anything customer-facing, not a temporary safeguard to phase out.
Topics
Transcript
Hey there and welcome to Leading Pre-Sales, the show for solution engineering leaders who want to build teams that drive revenue and not just demos. My name is Tim and I'm the co-founder of SE Rockstars and together with Jan, we've coached over 350 solution engineers and their leaders across several dozens of companies. Every conversation you hear on this show is based on real coaching situations, real challenges, real problems that SE leaders like you are dealing with right now. None of this is made up. We use AI to bring these stories to life through our two hosts, Nate and Ava, but the insights come straight from the trenches. Each episode gives you one actionable takeaway you can…
Full transcript available for MurmurCast members
Sign Up to AccessMore from Leading PreSales | The Solution Engineering Leadership Show
ROI on Token: Stop Rewarding AI Usage [64]
AI usage metrics are vanity metrics that mask whether AI tools actually produce business value. Leaders must shift focus from measuring token consumption to defining specific outcomes and explicitly allocating reclaimed time, or efficiency gains will disappear into building more tools.
Your First 30 Days of AI: The Activation Playbook [63]
Leading Pre-Sales episode on AI adoption in solution engineering teams within the first 30 days. The hosts present four critical decisions leaders must make: selecting one standard environment, prioritizing data access (email, calendar, CRM), conducting a mixed bootcamp with AEs and SEs, and establishing a bi-weekly rhythm with named ownership to prevent tool sprawl and ensure sustainable, reusable implementations.
Clash of Titans: Getting Your SE and Sales First-Liners on the Same Side [62]
SE managers and sales managers are structurally wired to conflict due to different optimization pressures and incentives, but this can be designed out through pre-deal alignment meetings, shared CRM records, joint qualification vetoes, and explicit acknowledgment of their different accountability timelines.
Spot the Super-IC Before the Numbers Do [61]
The episode discusses three diagnostic signals to identify managers who are individual contributors rather than developing leaders: closed-door one-on-ones only, rhetorical patterns of blame or over-ownership, and escalation emails with excessive CC'd recipients. The hosts emphasize that these behavioral patterns appear months before performance numbers decline, allowing early intervention.
Fifty Leaders, One Borrowed Office [60]
SE Rockstars hosts in-person leadership events across European cities featuring keynotes, breakout sessions voted on by attendees, and networking dinners. The community uses a member portal with recordings, directories, and event management tools to connect 250+ solutions engineering leaders who face similar challenges.