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.
Summary
The episode opens with a real case where a customer received an unexpectedly high invoice due to incorrect usage estimation. The SE had scoped a workflow that synced records on deal stage changes, but the customer's integration updated deals constantly, causing the workflow to fire every few seconds instead of the intended few times daily. This burned through the customer's quarterly credit budget in one month.
The hosts explore the fundamental problem: in seat-based pricing models, sizing is straightforward (e.g., 40 users = 40 seats), but in credit-based consumption models, the bill depends entirely on trigger frequency and usage patterns. A use case firing once weekly versus every two seconds appears identical in a proposal but dramatically different on an invoice.
A key tension emerges around accountability. SE leaders worry about SEs freelancing on commercial terms, yet pricing analysts and account executives don't actually know trigger frequencies—only the SE who conducted discovery does. The solution proposed is a clear division: SEs don't price (that stays with sales and deal desk), but they absolutely own sizing and must communicate what usage estimates mean for customer spend.
The hosts discuss how slow-motion surprises are particularly damaging in enterprise deals where budget committees lock annual numbers months before contract signature. Usage estimate errors don't surface until quarter-end, at which point procurement is furious and renewals are jeopardized.
To operationalize this, the hosts recommend: (1) making sizing a team standard, not a hero skill; (2) integrating a sizing checklist into tech win criteria with assumptions clearly spelled out; (3) comparing estimates to actual usage 90 days post-launch to identify systematic estimation gaps (particularly with webhook-triggered integrations); and (4) explicitly communicating to SEs that while pricing isn't their job, the usage estimate is their responsibility.
About this episode
Ava brings a billing surprise from her scale-up's move to credit-based pricing and argues that SEs must own usage sizing, even if they never touch price. Nate pushes on deal desks, annual budget cycles, and how to turn one person's skill into a team standard.
Key Insights
- The hosts argue that in consumption pricing models, SEs unknowingly inherit responsibility for the customer's final bill through their usage estimates, even when they believe pricing is outside their scope.
- Slow-motion billing surprises in enterprise deals (where errors surface 90+ days post-signature) are more damaging than immediate surprises because procurement discovers them during renewal discussions, potentially killing the deal.
- SEs systematically underestimate usage for integrations and webhooks that trigger workflows automatically, suggesting that external system integrations create a blind spot in discovery conversations focused on user-initiated processes.
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.
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.