Leading PreSales · 2026-08-31 · 6 min
Key moments - from our scoring
Substance score
43 / 100
Five dimensions, 20 points each
Most SE teams confuse two different skills: knowing current prices (which SEs shouldn't do) and understanding the metric that drives pricing (which they absolutely should). Nate and Ava distinguish between these in practical terms. Price lists are unmaintainable and unlearnable - at large vendors, SKU catalogs are impossibly long. Instead, SEs need to internalize one-sentence metrics: cost per seat per month, per transaction, per automated conversation. The session covers teaching this through 40-minute whiteboard sessions per business model, asking three core questions: what are we selling, which line item does it land on, and how does the number get built. The critical muscle is consumption math - making SEs do arithmetic out loud on deal volumes so they can estimate realistic rollout costs. This matters increasingly because signature deals no longer end support; expansion revenue now requires SEs to understand upgrade paths from 5% to 30% adoption, forcing coverage model conversations about post-signature attachment. Leaders must ensure SEs give ranges, never precise quotes, reserving precision for AEs and finance.
No. Price lists are unlearnable and constantly changing - at large vendors they're impossibly long. SEs should instead understand the single metric behind pricing (per seat, per transaction, per credit) and how that metric gets built.
The number becomes an anchor and the sales team spends months negotiating against itself instead of with the customer, wasting time and reducing negotiation flexibility.
Make them do the arithmetic out loud on live deals: multiply tickets per month by the realistic automation share by the per-unit price, working through estimates in front of peers to build the volume muscle.
A price is a specific number (e.g., $9 per seat) that changes constantly and anchors negotiations; a metric is the formula or unit (per seat per month, per transaction) that SEs need to understand to design scalable solutions.
Expansion revenue increasingly depends on post-signature adoption modeling - moving customers from 5% to 30% usage - so SEs must stay attached after the deal closes and factor expansion support into capacity planning.
Our reviewer’s read on each dimension, with quotes from the episode.
For a 6-minute episode the insight-to-filler ratio is solid, with a clear central distinction (metric vs. price list) and supporting ideas like volume-muscle arithmetic and the anchor-pricing risk. However, several points (expansion matters, SEs shouldn't quote prices) are familiar enough to limit the ceiling.
That was a 10x volume question. Wearing a technical costume, my se heard capacity. The customer was asking about money and nobody came back to it.
The price list is unlearnable. The metric is one sentence
The price-list-vs-metric framing is a useful repackaging, and 'a 10x volume question wearing a technical costume' is a genuinely fresh articulation. But the underlying ideas - SEs shouldn't anchor pricing, expansion beats signature - circulate widely in presales discourse.
That was a 10x volume question. Wearing a technical costume
The price list is unlearnable. The metric is one sentence we charge per automated conversation or per seat per month or per million transactions.
There are no real guests - Nate and Eva are explicitly AI-generated personas, and the practitioner anecdotes are composite coaching constructs rather than testimony from operators who actually did the thing at scale. Tim's credentials exist but he barely appears in the episode itself.
We use AI to bring these stories to life through our, uh, two hosts, Nate and Eva. But the insights come straight from the trenches.
The episode makes good use of illustrative numbers - 100K ARR band, 5% adoption, 200 SEs vs 12, twice-a-year pricing cycles - but these are fictional coaching composites, not verified case studies, which limits their evidentiary weight.
A mid size customer lands around a hundred K a year. Not 8K, not 2 million.
We had a customer parked at 5% adoption for eight months.
The scripted dialogue does model genuine push-and-pull - Nate raises realistic scale objections and forces clarification - but it is fundamentally pre-written, meaning there are no real follow-up risks, no surprise, and no possibility of genuine productive disagreement.
Fair. Though at 200 SES, that reframe breaks my coverage model. If solutions stay attached after signature, somebody has to fund that time.
Draw me the line though. At my scale, that distinction has to survive contact with a catalog nobody has ever read. End to, uh, end.
Computed from the transcript - who did the talking, and the words that came up most.
Seats, credits, transactions - why pricing metric literacy decides your value story Ava's SE told a customer the product "just scales" - and missed a ten-x volume question. She and Nate split pricing knowledge into two very different skills and show which one every SE has to own. What Nate and Ava discuss Why knowing current prices isn't the SE's job - but knowing the metric behind them absolutely is A 40-minute, per-business-model session: what we sell, which line item, what moves the number Teaching the volume muscle for consumption models - and why signature is the kick-off, not the finish The move Pick one business model this week and run 40 minutes with your team: what we sell, which line item it lands on, what moves the number. Then have every SE estimate the volume math on one live deal out loud - in ranges, never precise figures. Resources & Links: paths.to/presales Book a Discovery Call: calendly.com/serockstars-tim/discovery-call
Transcribed and scored by The B2B Podcast Index.
Speaker A: Hey there and welcome to Leading Presales, 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, uh, two hosts, Nate and Eva. But the insights come straight from the trenches. Each episode gives you one actionable takeaway you can apply immediately whether you're already leading a team or working your way into that role. Alright, let's get into it.
Speaker B: A customer asked one of my SEs last month, what happens if we run this on every ticket, not just escalations? And she said cheerfully, oh, it just scales.
Speaker C: It does scale. The invoice scales magnificently. Did anyone in the room notice?
Speaker B: Nope. That was a 10x volume question. Wearing a technical costume, my se heard capacity. The customer was asking about money and nobody came back to it.
Speaker C: I've watched that land badly. One of my SE directors had a renewal go sideways last year. Usage nearly tripled. Nobody had modeled it and the customer's finance team found out from the invoice trust.
Speaker B: Gone in one PDF welcome to Leading Presales. I'm Ava.
Speaker C: And I'm Nate. One idea, five minutes. Part three of our money week today. Does your team actually understand the metric behind your price?
Speaker B: And I want to split that in two because leaders lump it together and then give up skill one knowing today's prices. That is not the SE's job. Never has been good.
Speaker C: When I was still running a team directly, I let SEs answer price questions. Thought it looked confident. It cost me twice. Once a number leaves an SE's mouth in front of procurement, it's an anchor and you spend three months negotiating against yourself.
Speaker B: Right? Skill two is completely different. Understanding the metric that produces the price, seats, credits, transactions, instances, whatever your unit is, that one is absolutely the SE's job and most enablement never touches it.
Speaker C: Draw me the line though. At my scale, that distinction has to survive contact with a catalog nobody has ever read. End to, uh, end.
Speaker B: Okay. Back when I was an SE at a mid market shop, the price list was one spreadsheet, one product and something like 50 line items behind a single license. Every time I opened it, something had moved. I once quoted off a Tab that was six weeks stale.
Speaker C: That's small. Honestly, at the large ERP vendor I came from, you could scroll the SKU list for a week and still be somewhere in the S's. Nobody memorizes that. Nobody should try.
Speaker B: Which is exactly my point. The price list is unlearnable. The metric is one sentence we charge per automated conversation or per seat per month or per million transactions.
Speaker C: And the order of magnitude per seat is useless. If your SE thinks a seat is $9 and it's 90.
Speaker B: Yes, my SE's should know. A mid size customer lands around a hundred K a year. Not 8K, not 2 million. Without that, every solution they design floats. They'll cheerfully architect something that costs more than the problem.
Speaker C: So how do you teach it? It has to work through my managers. And I can't put 200 people through anything artisanal.
Speaker B: 40 minutes per business model. Whiteboard, no slides. What are we actually selling here? And which line item does it land on?
Speaker C: That's two questions. The third has to be how the number gets built.
Speaker B: How the number gets built? Exactly. What pushes it up? What pulls it down? I rerun the session whenever pricing changes, which for us is about twice a year. And I drag an AE in to catch the lies.
Speaker C: Consumption is where minds struggle. My managers tell me their SES can recite the metric. Fine. Then go quiet when a customer asks what full rollout actually costs.
Speaker B: That's the volume muscle. And you build it by making people do arithmetic out loud. Tickets per month times the share we can realistically automate times what we earn per 1. Ugly estimates are fine. Silence is not.
Speaker A: Hmm.
Speaker C: And all of this only matters because Signature isn't the finish line anymore. A big slice of my number comes from expansion.
Speaker B: Now that's the whole thing. Signature is the kickoff. We had a customer parked at 5% adoption for eight months. And the story my team needed wasn't we automate support? It was. You're at 5. Here's the road to 30.
Speaker C: Fair. Though at 200 SES, that reframe breaks my coverage model. If solutions stay attached after signature, somebody has to fund that time. And my capacity plan assumes they roll off. I'd still rather have that argument than pretend the deal ends when the ink dries.
Speaker B: You're right. I haven't had to solve coverage at that size. 12 people, everyone stays attached by default. So the move this week. Pick one business model. 40 minutes. What we sell, which line item, what moves the number. Then every SE estimates the volume math on one live deal out loud in front of the others.
Speaker C: And one rule Ses give ranges, never precise figures. The word is roughly. Precision belongs to whoever owns the quote, because you can't argue a 20k solution if you're not convinced you're solving a 200k problem. I'm Nate.
Speaker B: And I'm Ava. See you next episode.
Speaker A: Thanks for listening to leading presales. If you've got a question, a topic you'd like us to cover, or you just want to connect, we reach out to me at Tim um at serockstars. Com. And if what you heard today hit home and you want to talk about how to develop your SE team, feel free to book a discovery call at serockstars. Com. No strings attached. The link is, of course, also in the show Notes until next time, and keep leading from the front.
Thirty Seconds That Sells [45]52 / 100The Seven-Figure Promotion [58]One Sentence: The Pricing Guardrail Every SE Team Needs [56]400 Licenses Is Not a Number [55]When 'Show Nothing Extra' Becomes Handcuffs [54]