Fifty Times Faster, Fifty Times Wrong
Nate shares an experiment from one of his SE Managers: two teams used the same AI demo tool with identical timelines. The team that did structured discovery first booked next meetings every time. The team that skipped it shipped polished demos that went nowhere.
What Nate and Ava discuss
- Why AI amplifies bad discovery instead of replacing it
- The pain chain: a fifteen-minute gate that transforms demo quality
- How the AI productivity race is quietly killing the discovery skill
The move
Before your SEs touch any AI demo tool, require a one-page pain chain. Start with the surface complaint and walk it up until you land on a metric the CFO actually cares about. No artifact, no demo.
🔗 Resources & Links: paths.to/presales
📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call
TranscriptRead the conversation →Hide ↑
Ava: Nate, before we get going... do you sound a little different today?
Nate: I was about to ask you the same. Apparently we've had a bit of a tune-up under the hood.
Ava: A tune-up?
Nate: New voice engine. We've moved from ElevenLabs over to Google Gemini. For the curious listener, that's the switch under the hood. The team tells me we're meant to sound a bit more... natural.
Ava: Ha. As opposed to what — charmingly robotic?
Nate: Charmingly synthetic, I think was the phrase. Same conversation. Hopefully a little easier on the ears.
Ava: So if either of us breathes weird or pauses in odd places — that's why. And if it lands, tell us. Email, LinkedIn, however you find us. We want to hear what you make of it.
Nate: Right. Now... back to the actual show.
Nate: One of my SE Managers ran an experiment last quarter. Two teams. Same AI demo tool, same product, identical two weeks to build.
Ava: Okay.
Nate: One team had been through a structured discovery program the quarter before. The other hadn't. Both shipped demos using the tool.
Ava: Let me guess... different results.
Nate: Wildly different. The team that skipped the discovery work shipped gorgeous demos. Beautiful dashboards, polished storytelling, wrong data model underneath. Prospects were polite and ghosted.
Ava: Oof. Brutal.
Nate: The other team? Aesthetically WORSE demos, rougher edges. Every single one ended with a next meeting booked.
Ava: So the ugly demos won.
Nate: Every time. Because they answered a real question.
Ava: Welcome to Leading PreSales. I'm Ava.
Nate: And I'm Nate. One idea, five minutes. Today... why AI is making your discovery gaps BIGGER, not smaller.
Nate: Look, I've spent this whole quarter watching my managers push their SEs through forty, sixty, eighty hours of mandatory AI training. Every company's doing it right now.
Ava: Yep. Same pressure here, except I don't have the layers. I feel it directly in my calendar.
Nate: How many hours are your SEs burning on AI tooling this quarter?
Ava: About six a week. New tools, new prompts, new integrations. I've been telling myself it's an investment.
Nate: Is it?
Ava: When I look at what actually moved our win rate... not as much as I hoped.
Nate: Right. And the pitch is always the same. Fifty times more productive, ten times faster, pick your multiplier. I had a conversation last week where someone quoted me fifty-x on demo build time.
Ava: Hm. Fifty-x is a big number.
Nate: It is. But fifty times faster at what? If the demo's off the mark, you just scaled a bad assumption fifty times.
Ava: Okay... keep going.
Nate: Discovery is the constraint. It always was. AI just made the cost of skipping it louder.
Ava: I hear you. But here's the pushback. My SEs run a four-week cycle. Sometimes less. If I tell them "pause and do proper discovery," I lose the deal to the vendor who shipped a demo on Thursday.
Nate: Fair. I'm not saying ninety-day discovery. I'm saying STRUCTURED discovery. Fifteen minutes of actual thinking before you prompt the tool.
Ava: What does that look like? Walk me through the fifteen minutes.
Nate: A pain chain. You start with the surface complaint and keep asking "what does that lead to?" Every answer is the next link. Stakeholders describe the symptom; you climb until you land on something a CFO would actually fund a decision on. Revenue, cost, time to value — that altitude. My best managers require it as an artifact before any SE touches the AI demo builder.
Ava: So it's a gate.
Nate: It's a gate. And it's cheap. Fifteen minutes, written down, the SE has to think in actual sentences.
Ava: And the AI gets the artifact as input. Not the SE's vague notes.
Nate: Exactly.
Ava: Why a pain chain specifically? Why not a persona, a stakeholder map, something richer?
Nate: Because it has to be cheap enough that the SE actually DOES it. Persona maps are a research project. The pain chain is one question, walked up four or five times. Sticky-note territory. If it costs more than fifteen minutes, nobody does it before a demo.
Ava: Okay, THAT I can work with. That's an interesting reframe. The AI isn't replacing discovery. It's consuming it. Bad input, bad output.
Nate: Good input, fifty-x output.
Ava: And the SEs who skip the gate, what happens?
Nate: Exactly what you'd expect. My manager pulled the numbers. Gated team got double the qualified next-steps. Same tool, same product, twice the conversion.
Ava: Because the tool is only as sharp as the question you walked in with.
Nate: And I'll admit something. A year ago I thought AI would commoditize discovery. Make it skippable.
Ava: And now?
Nate: Now I think AI widens the gap between good and bad SEs. The sharp SE becomes fifty times sharper. The mediocre SE just ships more mediocrity, faster.
Ava: Hm. So the AI doesn't level the playing field. It tilts it harder.
Nate: It does. And here's the uncomfortable part. The temptation right now is to pour hours into the tool, not into discovery. Everyone's worried about being left behind on AI.
Ava: Which means discovery becomes the forgotten lever. Nobody's getting promoted for "I got better at discovery this quarter."
Nate: No. They're getting promoted for "I automated our demo pipeline."
Ava: Ugh. And in two years we'll have teams of SEs who can generate fifty demos a day and none of them land.
Nate: That's the risk. It's what keeps me up about this cycle.
Ava: What if the AI gets so good it can do the discovery too?
Nate: It can help. It can't replace. The room where the customer tells you what really broke last quarter? No model gets invited to that room. Not yet. Maybe not ever.
Ava: Yeah. That's still human work. The pain has to be felt before it can be heard.
Nate: And the SE who can sit with it, ask the next question, then the one after — worth five of the demo-pipeline operators.
Ava: Okay. The move.
Nate: Before your SEs touch any AI demo tool, require a one-page pain chain. Start with the surface complaint and walk it up — what does that lead to, what does THAT lead to — until you land on a metric the CFO actually cares about. The artifact feeds the tool. No artifact, no demo. You'll be shocked what happens to your win rate.
Ava: And as a leader, don't let the AI training budget eat your discovery budget. Those aren't the same skill. One makes the other worth something.
Nate: I'm Nate.
Ava: And I'm Ava. See you next episode!
Auto-generated from the episode script and lightly cleaned for reading.
Your hosts
Nate Hargrove — The Seasoned Pragmatist
Ava Vasquez — The Modern Builder