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
Core vs. Context: When Your SEs Should Let a Build Deal Go [92]
The episode teaches solution engineering leaders to distinguish between core and context business functions when customers consider building custom solutions versus buying software. SEs should let lightweight, context-focused builds go while fighting harder for core capabilities, and leaders must publicly validate this approach to change team culture.
The Iceberg Under Every Build Deal [91]
Solution engineering leaders need a standardized five-year cost model to evaluate Build vs. Buy decisions in the AI era, grounded in hidden maintenance costs and opportunity expenses rather than vendor pitches. The key is creating an 'iceberg checklist' of often-overlooked costs and having customers co-create the financial analysis rather than presenting a pre-built case.
Leaderboards, Not Cameras [89]
The episode examines why AI adoption dashboards and leaderboards often fail to drive behavior change, and proposes an alternative approach: publicly sharing AI workflows that actually shipped on real deals, ranked by peer reuse rather than usage metrics.
Your SEs Just Inherited the Customer's Bill [88]
Solution engineers must own usage estimation and sizing in consumption-based pricing models, even though they don't set prices. When SEs fail to accurately estimate how often workflows trigger, customers face billing surprises that damage relationships and renewals.
Rebrand or Real Role? The FDE Test [86]
The episode examines whether Forward Deployed Engineers (FDEs) represent a genuinely different role from Solution Engineers or merely a rebranding strategy. Through analysis of real job postings and market trends, the hosts present a three-question test to distinguish authentic FDE positions from SE roles with inflated titles.