One Sentence: The Pricing Guardrail Every SE Team Needs [56]
SE leaders should implement a single scripted sentence when customers ask about pricing to prevent misstated numbers from anchoring negotiations. The sentence should deflect to the AE while offering value, reference published pricing when available, and be rehearsed by the team rather than just distributed in writing.
Summary
The episode discusses a critical pricing guardrail for solution engineering teams. The hosts open with a real example where an SE quoted outdated pricing ($90/seat instead of $120), forcing the AE to send multiple correction emails and damaging credibility. Another anecdote illustrates how one misstated price correction—from roughly $X to double that amount—destroyed trust in the room and couldn't be recovered.
The core recommendation is implementing one consistent sentence that SEs use when asked for pricing: 'I'll get you a binding number from my AE, and while we're here, let's pin down which of these three modules you actually need, because that's what moves the price.' This approach accomplishes three things: it prevents improvisation on numbers, it redirects without being evasive by offering value in return, and it removes the temptation for SEs to quote without current pricing information.
The hosts debate whether this approach undercuts the SE's role as a trusted advisor, but one argues that removing improvisation from pricing discussions is different from banning pricing conversations altogether. A key practical constraint is acknowledged: most organizations cannot guarantee every SE has current pricing at all times, especially across large teams or after recent packaging changes. The conversation identifies a critical problem—stale figures circulate for months and get embedded in customer presentations as established facts.
The episode emphasizes that spoken numbers anchor negotiations in ways that are hard to undo, and in enterprise deals, throwaway figures from early workshops can resurface months later in procurement committee presentations. The hosts add an important nuance: published pricing (website, approved decks) can be referenced directly, as that's not improvising but being useful. Beyond published prices, everything goes to the AE.
Another key point is maintaining role separation: SEs own value and feasibility conversations; AEs own commercial discomfort. This protects the SE relationship—the customer won't resent the technical person if the AE is the one who named and later adjusted the hard number. Finally, the hosts emphasize that the sentence must be rehearsed live in team meetings, not just distributed in writing, because reading a line and delivering it under customer pressure are different skills.
About this episode
Ava's SE quoted an eight-month-old price with no AE on the call, and the walk-back cost more than the number ever could. She and Nate work out the one sentence every SE should say — and the directory that keeps it from sounding like a dodge.
Key Insights
- The hosts argue that a single stale number spoken in a customer conversation can anchor negotiations for months or years—even resurfacing in procurement committee slides nine months later—making correction nearly impossible and justifying strict guardrails on SE pricing statements.
- The speaker claims that most SE organizations cannot guarantee current pricing across their entire team at all times, particularly after packaging changes, making price improvisation by SEs an inevitable accuracy problem unless constrained by process.
- The hosts contend that role separation between SEs (who own value and feasibility) and AEs (who own commercial discomfort) protects the customer relationship by ensuring the technical contact is not also the person who names and later retracts hard numbers.
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.