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.
Summary
The episode explores why first-line SE managers and first-line sales managers predictably clash, despite both genuinely wanting the same customer outcomes. The root cause lies in how they're wired: SE managers typically step up to fix broken processes and protect their teams from overwork, while sales managers are driven by closing deals and hitting quarterly numbers. Sales managers face visible, public 90-day accountability that SE managers don't experience, creating different urgency levels. This structural difference gets misinterpreted as disrespect rather than legitimate pressure. The speaker describes how one organization redesigned their approach by implementing a declared tandem model where a sales first-liner and SE first-liner run deals together as partners, starting their collaboration before deal kick-off with 15-minute alignment meetings covering win theory and contingency planning. They maintained standing cadences throughout the deal cycle and, crucially, kept a single shared CRM record rather than separate notes, which prevented the creation of conflicting narratives about the same customer. The most impactful change was giving pre-sales a real qualification veto at eye level—both managers must jointly agree to pursue or drop a deal. To prevent the veto from becoming a hiding place for risk-averse behavior, the drop decision must be documented with both names and reasoning. The organization then reviews dropped deals 90 days later to determine if competitors actually won them, creating calibration without shame. The speaker emphasizes that temperature changes came from structural design, not hoping for chemistry, and warns against allowing poisonous language (like 'I'll never win with that SE') to fester, as it quickly escalates into operational routing-around and extended dysfunction.
About this episode
First-line PreSales and first-line Sales sit on the same org level but got there for opposite reasons, so the friction is structural, not personal. Nate shares the tandem model and qualification vote that cooled things down across his regions, and Ava stress-tests both until they hold up.
Key Insights
- SE managers become first-liners because they want to fix broken processes and protect teams, while sales managers got there by pushing, chasing, and closing deals—creating fundamentally different optimization targets for the same outcomes.
- Sales managers face visible, public 90-day accountability that SE managers don't encounter, which explains the volume and urgency of their pressure but doesn't excuse poor behavior; SE managers who don't understand this structural asymmetry interpret urgency as disrespect.
- Separate CRM documentation between sales and pre-sales causes each function to build conflicting narratives about the same customer, leading to disagreement in front of customers; a shared record is load-bearing infrastructure, not a boring administrative detail.
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
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.
No Quota, Still Commercial [85]
Forward Deployed Engineers (FDEs) should be measured on time-to-first-value and usage ramp rather than traditional sales quotas, with compensation tied to commercial outcomes that directly correlate to revenue under consumption pricing models. Success requires a disciplined 10x cost-recovery model, a defined pilot-to-contract path, and mandatory product feedback loops to prevent FDE teams from becoming expensive consulting operations.
Engineering Is the Entry Ticket [84]
Forward-deployed engineering engagements often fail due to poor discovery, scoping, and stakeholder management rather than technical deficiencies. Engineering skills are necessary to enter the room, but success depends on identifying success criteria, mapping stakeholders (especially those who lose if the project succeeds), and having leadership cover to push back on misguided requests.