GTM Uncensored
← All episodes

Episode · Nov 18, 2026

The Playbook Your Best Rep Is Hiding From You

Your team can explain every deal it lost, but nobody can tell you why you win. Fiona Covington, founder of ReflectPath, has spent the past decade inside more than a dozen sales teams as a revenue enablement leader, and she joins Adam Jay and Dale Zwizinski to break down why winning teams still can’t explain their wins.

Discussed in this episode

  • Why most sales teams run loss reviews and skip win analysis
  • How to use your competency matrix and call transcripts to find what your best reps do differently
  • What your org loses when a top rep leaves and nobody wrote down how they win
  • Where AI helps with win-loss analysis and why change management still needs a human
  • Using jobs to be done to decide what to automate before you hire

Episode highlights

Full transcriptRead

[What kind of question is that, man?]

GTM Uncensored.

I feel like I'm on Hot Ones and you just asked me like the most in-depth question ever after I just ate like the bomb beyond insanity.

All right, Fiona, in a typical GTM Uncensored fashion, I'm going to drop you into a scenario and I want your take. Vantly Picture Systems. They are a $42 million ARR enablement platform that just missed forecast by four points even though their win rate climbed by two points in the very same quarter.

Their VP of sales pulled up 18 months of call recordings and asked every rep one question: What did we do right on the deals that we won? No one, shockingly, could answer past good chemistry with the champion and salesmanship. I love seeing that salesmanship.

The company has more transcripts and CRM notes than it could read in a decade and not one document that says why it wins. You built Reflect Path because you've watched this exact blind spot for years. When a VP of sales says that there's so much data and they still can't answer the one question that would fix next quarter, where the hell do you tell them to start?

Oh, well, if it was 10 years ago, I'd be like, you're screwed.

Can I curse?

Yes, absolutely.

[laughter]

Welcome to GTM Uncensored.

I forgot I'm with my people. Like a sailor. Have fun.

Perfect. If it were 10 years ago, I'd say you're screwed because without going through the data, you can't figure these things out. But thankfully, in the year of AI of 2026, we have a lot of solutions to address exactly that problem. I think we're really good at looking at numeric data because it's right there, right? The win rate goes up, we miss the forecast, right? Like we can see those numbers very easily and we can assign trends to them and all that stuff. But what we are very bad at because of the way human brains work is finding pattern in words. And so there's a bunch of tools out there, but it's as simple as you could take all those transcripts and drop them in Claude and ask the right questions of whatever AI tool. Gong has this built in, et cetera. But finding the patterns—not just what did the customers do or say or what competitors came up, right? We all know how to do those things with all the conversation intelligence tools out there, but what are the behaviors, the questions that were asked, or the skills that were on display for our best reps on the deals that we won? And how do we look at that gap across the rest of the team, identify it, and then work on fixing it?

So a great example would be: You have a top rep who won a ton of deals and they consistently brought in three to four additional contacts every time they spoke to their champion. Now, I could tell my sales manager, "Oh yeah, I'm really good at multi-threading." But to see that pattern or the gap of that pattern across the entire team is really hard to do because frontline managers only have so much time. They only have the view of their team and all those things. So you really need to look at it from a 30,000-foot view of what's going well on our best calls and who needs help filling in those skills.

What's going well, I think, is a very broad question, right? So I don't think—and maybe you can—I don't think you could go to Claude or I won't say the G-word—ChatGPT or another platform and say "what's going well." I think you have to be more specific than that. So give me two or three examples. Like, what very specifically would you tell people to put into your AI or conversational intelligence platform to understand what's going well?

Yeah, that's a great question. I would say any sales team worth their salt has some sort of competencies matrix. Hopefully you do. If you don't, there's some people on this call that you could call. But taking, for example, your competencies matrix or even your job description—because that's pretty much what a job description is.

Oh, you mean the job description they wrote on ChatGPT that has nothing to do with the expectations they want to execute on? Okay. Yeah.

Yes, that exact one.

Dale loves JDs. They're his favorite.

Yeah. But in an ideal world, or at least take a best guess: What are the skills that we want our salespeople to have? That is a great place to start. So, for example, if you're working in an enterprise space and you know that it is really important for your sellers to have executive presence and be able to communicate clearly with VPs and up, that is a skill that you can find—if it's going well or not—through something like your transcripts. That would be a great example. I think starting with competencies or job descriptions or something like that to get a baseline.

And then the other area to look at is: When we do our loss analysis, which we're great at—we love taking ourselves down a peg—

What are the things?

Don't look at wins. Let's just look at losses.

Right? And you can kind of reverse engineer what's going well or the skills that get you to wins by looking at where you fell down on your face in your losses.

Yeah, love that. So great segue right into my next question. So you said—Salesforce pick apart—you prepared. You prepared a question.

Yeah.

Well, I prepared a question to make sure that we can get some great answers, Adam. So in blown deals, we pull in our manager, sometimes the CEO. We're pulling in all these people, right? But on closed deals, it never gets the treatment. We were just talking about this two seconds ago. Highspot's latest GTM data said that 96% of leaders say they have a clear strategy, and only 50%, 53% say it's actually delivering ROI.

Question: Is this a strategy problem or is it a wins problem nobody's writing down?

That's a great question, and I'm just chuckling because the statistic where almost everybody says, "Yeah, of course we have a strategy," just makes me laugh because all three of—

I'm surprised 53% delivers ROI. Like that was—I would have expected it to be much lower, to be honest.

2% delivers ROI on the strategy that they say they have, you know? I think where a lot of sales leaders call something a strategy, it's really a wish, a hope, and a prayer. And if we've all read the book, hope is not a strategy, right? So I think a lot of folks identify a strategy as, "Here's where we want to be, and here's our rough guess as to how we could maybe get there." And that's about as far as strategy goes. The problem is you're not examining any of the data that got you there last time, which would be your wins, right? Most people just do the high five on Slack, right? The rep has to put in like, "Here's everything that I did," and blah, blah, blah—like a whole life story never to be seen or heard from again. Just like all my notes from conferences that live in a notebook somewhere that I've never looked at ever again. I feel like all of the information around why we won just goes into the ether and is never utilized or looked at ever again.

And the teams that do use that information and create repeatable success—that is the strategy. It worked in these contexts, these were the parameters, this is how we know we're successful, let's do it again.

That's a strategy in my mind.

So that is a strategy, and that ties to your framework, right? So your framework has five steps, if memory serves me correctly.

You have a memory.

I listen, it's just—plug in a USB device every morning. No, he actually says to Chat or Claude, "Hey, restore this in memory."

Remind me what I'm supposed to know.

[laughter]

Yes, tell me what I need to know for this conversation. I love that Dale gives me so much credit, but I do have a memory. And as I was saying, your fifth portion of your framework is called Reflect. And you said that it's the one that everybody skips once a deal closes. So if a manager can't explain how their best rep keeps winning six-figure deals, what does the org lose by leaving that as a mystery—more than just revenue? Obviously, you know, they lose revenue, but what else is lost?

Well, the obvious one is: Man, if I'm a rep and I keep closing six-figure deals, I am a hot ticket commodity, and I'm going to go find me another job. And so if you can't identify what that rep was doing so well, and they walk out the door, that team knowledge evaporates immediately. So that in and of itself—and we know that especially great reps, they're going to pop around, they're going to change jobs, they're going to move to another company, and you're going to lose all that institutional knowledge and the ability to transfer those skills to other people on the team.

I am always challenged by the idea of letting—especially sales reps, especially in bigger arenas, enterprise, all of that—like, letting the winners just go be winners in a silo and not ever taking them out of the field for just a minute to work with their colleagues on why what they do works. Because sales managers, VPs, enablement, all these other folks can tell other reps, "This is what Adam's doing that's working so well." But hearing it from Adam has such a different absorption rate for the rest of the reps on the team.

And it usually is Adam who's doing well.

Dale, let's just bear with this. Adam is obviously the best, and we'll test this theory later in the podcast. But the point is, what you're missing is being able to take that knowledge or those skills and disseminate them across the rest of the team.

What about hiring? How much does this cost you in hiring? When you're looking for new people and you can't even figure out what good reps are doing? How many times are you continuing to hire shitty reps who don't have the same skill set or experience as what's working?

Well, don't they say I always get this stat backwards, but I think it costs one and a half times as much as you're paying a rep to replace them.

Yeah, so at minimum. And that doesn't even count ramp time, their first six months that they screw up, all the deals that leave because of rep turnover. Oh god, I could go on and on and on about what rep turnover does to active deals. But I think that number is not even calculable because there are so many factors. But the bottom line is you're going to lose a shitload of money by losing a rep that you can't replicate. And you're missing the opportunity to give the rep who's doing well their flowers, right? Like identify and say, "This is what you excel at and are great at." And not only that, I want you to teach the rest of the team how to do that, or I want to work with you to teach the rest of the team how to do that. You miss that part of the conversation if you don't know what their skills are. And then if you have to replace them, you don't even know what you're looking for. So it's a compounding problem for sure.

Yeah.

Craziness. It's craziness. There's no other nice way to say it. Well, and I think it goes back to the same thing you all deal with all the time when folks are transitioning from founder sales to hiring some hotshot VP of Sales that they have no business hiring. It's the same issue. The founder has no idea how they got to their first two and a half million or whatever it was. They just stumbled their way in the dark and got some people to write them checks. That's usually what happens. They can't identify how they got there, and then they try to turn around and get someone else to sell their thing for them. That VP of Sales. They always hire a VP of Sales first, which makes all of us crazy, but that person doesn't know anything about the product. They don't know the history of the company. They don't know what little nuances that the founder brought into the conversation. It happens at that level too. It's not just your team.

And they don't have the passion. They don't have the passion that the founder has. That's never going to happen. And I don't know when we realize that someone you hire will never have the passion that you have for the same thing you're trying to sell. It's just not going to happen.

Never.

Let's move to technology for a little bit. You told Doc's Grow and Tell podcast that you pointed Gong's AI builder at 100 QBR calls and got back a 15-page gap analysis report on what was wrong. Same tool, same data aimed only at loss. Why hasn't anyone started to run these queries on wins? Like how can we get people to look at this as a perspective that you will get more out of the wins and the losses together?

How do we get them? Why haven't they done that? Is it just ingrained?

Yes. I think it's a combination of one, it's our niceness, right? Like we don't want to brag, and our natural instinct is to just say, "High five, you won, good job. Let's not talk about it anymore," because then we're getting caught up in that whole social thing like don't brag too much. So I think part of it is sociological.

Some of us kind of miss that gene.

Yeah, there are some of us who don't have that gene. Some of us have no problem celebrating our wins as much as we need to, but the rest of us tend to have that problem.

The second piece of it is it's time consuming, to be honest. It's time consuming, and at face value it seems like, okay, we want—who cares? We got the revenue in the door. Let's move on. The next deal is right there. Let's go. And it seems like there's a potential that you might be wasting time by overindexing on win analysis. It's very easy to do loss analysis. It's simple, right? This went wrong. This went wrong. This went wrong. Here was a problem. This didn't go well. It's very easy for us to identify. I think it's just human nature. And people get quick at it because we're so used to doing it. But what a lot of people miss is that when you only look at the losses, you're only seeing half of the coin.

Yeah. And so that's the second part you said was really interesting, that it's time consuming. Why do you believe it's time consuming to do the win analysis?

Well, let me rephrase that. So I think there's a perception that it's time consuming because it doesn't come as naturally to folks, but it takes the same amount of time. And when, like I was saying in the first piece of this, when you have a win, the revenue comes in the door and it's on to the next. It seems like slowing down or stopping to look at that win could potentially take up a lot of time that you don't quote-unquote have because you need to move on to the next deal. But the reality is if you do take the time, which doesn't take any longer than a loss analysis, if you do take the time and you start to identify the patterns in what's working, what customers are responding well to, what are the things that got the deal closed faster or at a higher price point or whatever it is—when you do stop to find those things, it's building you a shortcut in the next deal. So it is actually completely worth the time.

I think it's totally worth the time. I do think maybe we just have a deals analysis and not a win or loss analysis. Like, maybe we just say on a weekly basis, depending on how your deal cycles are, or on a monthly basis we have a deals analysis. And it's maybe wins and losses. So we're not just like, yeah, so it's not just like you're getting beat down or you have this great perspective, but you kind of combine them together. So there's probably, especially with using LLMs now, there's probably a good report to be like, "These are why you won. This is the win compared to the loss," and then do that comparison analysis.

Yeah, I've been inside of over a dozen sales teams in the past decade, and exactly one of those teams did win-loss analysis. The rest of them only did the fire and brimstone tear someone a new one at the QBR loss analysis. But yeah, exactly one company that I've ever worked with actually did win-loss analysis, and it helped. I mean, not only did it elevate really successful deals to the CEO for his awareness and gave people their dues when they earned them, but it also helped drive the strategy. Like taking it back to strategy, it helped drive the strategy, especially when new products were being introduced or moving into new markets. Understanding what worked is super important in those contexts, not just in the day-to-day running of the business.

Let's tie that in. Right. So you're on the RevFest main stage this year, and you're arguing that the most valuable data set in a revenue org has no numbers in it. So companies like Rally are already feeding raw call recordings into AI to reconstruct win-loss patterns without a human interview. We all know there are companies out there like Closed and others that will tell you, "Pay us this and we'll do human interviews, and we're going to get you better responses because it's not the company asking. It's this third party," and blah blah blah. If a machine can actually mine that signal at scale, what's left for Reflect Path, what's left for us when it comes to win-loss, what's left for the Gongs, the Attentions of the world? Like what's left to do there?

Yeah, that's a great question. And I think just like with any technology, whether it's your Salesforce trend dashboards and your forecasting tools and all of those things, at a certain level there has to be a layer of human analysis. It's like, great, this tool is fantastic. Thank you, Rally, for making everyone's jobs a lot easier on that front. This tool has surfaced those patterns. What are you going to do about it? So the whole point of doing this analysis is not to just put a shiny 15-page report on the shelf. It's to actually go and do something with it. Whether that's building enablement programs around what's working and what the top reps are doing, whether that is using that strategy to break into the next thing—like we were talking about a new product, a new market, whatever it might be—you have to actually use the analysis, right? And I think that's where I am not afraid of AI taking all of what folks like myself, folks like you all do. There has to be a noggin somewhere in there to take what comes out of the analysis, put it in context, fold in all of the layers of experience and everything else, and actually go.

Do something about it and create the motivation inside of that organization to make that change. And I don't think that Claude is ever going to be really good at change management.

No, I would imagine Claude is not going to be good at change management. We can't even get people to be good at change management. So I literally built—it's so funny we're talking change management—I built a resource this morning on our website specific to change management and I'll link it in the show notes. But when you look at a pirate ship, there's like 15 different areas where people fall when it comes to change management. And if you don't know how to address most of those, any change that you try to put in place is gonna go nowhere, to be very honest.

Did you say there's 15 different places on a pirate ship where people will fall off the pirate ship?

There's 15 different places related to change management.

I'm actually about pirate ships and fall like—

No. So let's see if I could do this. So we've never screen shared on a podcast before. But while we're talking about change management, let's see if I can make this work.

Boom. And let's make sure we share the right thing because we know how that works when you don't. Here we go.

Look at that.

So every reaction, so there's 15 different places you can be. And when you look at it, you have people who are rowing, right? So it's going to break out every single one of those, but you know where people are—all the way to on the ship but not in the work. And then you just have your people who are quietly working against it. And I think this is what we see more often than not, right? Like these are the people who are literally like they are off the boat. This isn't going to work. I'm going to—

Number 20.

20. I was going to say 20 is my favorite. Like LA the dah.

You guys have fun with that. See you never.

Right. Figure it out. But change management is hard. And I think very few people do it well.

Yeah. And I think, you know, taking it back to the reason I'm not worried that Claude is going to take that over or AI is going to be able to do change management is because the number one thing that change management requires is empathy. And you can't program that. There's no algorithm for empathy. And like people in my neck of the woods and the enablement space get tired of talking about this, but I often realize we don't talk about it enough. If you don't start with, especially with reps or people who are kind of not part of the decision-making process, if you don't talk with them about what's in it for me—like why bother changing? What is this new sales process or using this new tool or going back from remote to in office? Like whatever the change is, if you can't articulate from jump street why somebody should care, then everyone's going to be number 20 sitting on that island reading the newspaper because they don't give a damn.

But if you could say, "Dale, this new sales process is going to get your close rate up by 10 percent." Dale's like, "Hell yeah, let's go. I would like to make more money, please."

So Dale's gonna have a close rate of 10 percent? That's awesome.

Yeah. It's going to take Dale's close rate from zero to 10, guaranteed.

I love it. I love it. Listen, if we could do that, that's a win.

Oh yeah. Exactly. Adam's like getting dollar signs in his eyes because all of a sudden you guys are going to be able to retire. It's going to be magical. So let's do that. That's the change reason. Now everybody's on board and actually wants to start rowing in the right direction.

I'm curious your perspective on this because we've talked a lot about this recently. People are hiring people. We talked about job descriptions. We've talked about—we haven't talked about onboarding, which I think is a whole different can of worms, but—

I'm making sound for those that don't see me, that aren't watching. But for prior to even job descriptions, now one of the things we've been working with clients on are jobs to be done. Because I don't know if you can get to a job description unless you identify all the jobs to be done for an individual person.

Yeah.

It's super boring. It's super monotonous. It's super like, okay, what are all the things? And then like after they go through them, they're like four or five other things. Then what we started talking to clients about is of those jobs to be done, what can be automated? Like what are those things that can be automated and what are those things that truly need humans? And then we can go build the job descriptions, the onboarding, the scorecarding, all the stuff that you need to do. I'm curious your perspective on jobs to be done. What you like—before you go hire somebody, how do you identify what should be automated? Like do you really need a human being in that place or can you automate it? And what you're seeing when you talk with your clients?

Yeah, that's a great question. I think first and foremost, if you're going to sit down to do a jobs to be done analysis, it should require a bottle of wine or tequila or whatever you need, because it sucks. You're absolutely right. It's not fun. But it's one of those things that I think is crucial to creating a good environment for any team member, whether it's a VP or a BDR, right? I think identifying this is what you're responsible for and this is what good looks like in this role is crucial. Going about the process takes a couple of things. One, it's understanding where success comes from. So like what are the things that actually drive success in that role? What are the activities? If you're a BDR, right, it's outreach to customers, it's booking meetings, it's understanding the product, right? There's very specific things that we know create the outcomes that we need from this role. So that's part one—it's got to be an analysis of what builds to success.

When it comes to the automation side of it, I think we can start to look at what are things that are repeated and just ongoing tasks that have to happen regularly because AI is very good at repeatable tasks. What are things that do not require decision-making or the decision-making is very binary or linear, right? So something like—I'm just coming up with something—okay, so like a qualification disqualification framework. If we can get information about the prospect to a degree that it's a checkbox of do they have this, do they have this, do they match our ICP? Like very linear decisions—yes or no—gating. Are they qualified or not? Something simple like that I think is an easy area to automate. So again, it's something that's either task repeatable, task driven, or the decision-making elements are super simple.

When the decision-making elements get more complicated—like discounting, probably better to have a human in the loop on that one—or I like to say AI in the loop, human-driven decisions for something like that.

And then the last piece, when it comes to jobs to be done, I think we miss an opportunity once we've done that work. A lot of times a job description which comes out of that work will just say here's what you need to do. It doesn't actually incentivize the potential rep or whoever we're hiring with here's what you don't have to do. If I knew that a company had a bunch of tools in place or the right tools in place and had automated A, B, C, and D that I don't have to worry about, I'd be like heck yeah, I want to work for that company. That's almost like a job benefit. Like we're investing in making your job more focused, more strategic, more straightforward. You don't have to do all this minutia stuff because we have Rally to do our win loss analysis and help you understand what's working in your own book of business.

That is enticing for potential reps, especially the good ones. And I think that if you're going to go through the exercise of jobs to be done and you're going to use that to leverage—you're going to leverage that to create your job descriptions—tell them what they don't have to do because you've invested in the tools.

Love that. Couldn't agree more.

Love that.

All right, let's shift gears. We are going to go to the Monday morning move. Dale's favorite part of the show. I am going to share a practical takeaway that listeners can test this week. You have two jobs. Job number one, Fiona, you're going to rate me one to 10. Ten being the best, one being the worst. You can imagine where I want to be, and you can imagine where Dale wants me to be. Number two, anything that you want to add, change, or push back on.

Okay.

All right. Here we go.

Before your next pipeline review, pull the call transcripts from your three biggest wins this quarter the same way you pulled the transcripts for a blown deal or a loss review. Run them through whatever AI builder your stack already has and ask what the rep did in the first two calls that never shows up in the lost column. Then have your newest rep guess the answer before you show them the transcript. A close guess means that you've got a repeatable pattern. A miss means you found a training gap. The real problem.

It isn't the lack of data on what's working. It's that nobody has ever been told that studying a win is part of the job. I feel like Adam went into my enablement diary of like, "Dear diary, in my greatest dreams, this is what would happen every Monday morning on a team call." Dale, please don't hate me. You know, I adore you very much, but Adam pretty much nailed that. I would give that a ten.

Oh, let's go. No, let's go. Winner. I won.

My twenty bucks will be hitting Venmo in about five minutes, right? No, no, no. I think that's brilliant. And here's why I think that's brilliant. One, because right back to what we talked about earlier where taking what a great rep is doing and bringing it into the team conversation and working with the rest of the team to help understand what it is that that person is doing is crucial. And the idea of a little game like that of "guess what the thing is that helped them be successful" is spot on. And it's a great way to do that as a team. So I thought that was brilliant, Adam. Thank you for making my enablement dreams come true. Now, let's go implement that with every sales team on the planet.

Dale hates you right now.

But it made my day. That was great.

I guess he has to do good once in a while. I have never scored below a seven.

We are going to fix that.

I mean, unless you're starting them.

He's cutting me off. It's like I'm not talking about this anymore. Next, Fiona, as we start wrapping up, we do something called uncensored questions. A bit more of a rapid-fire type scenario. So let's jump in with Rally and Gong are setting, or are now selling AI chunks that are a bit of what Reflect Path does framework does minus the coaching. Are they wrong about what matters? Are they just explaining what they're already doing?

That's a great question. I think that most of the tools out there are on the right path. They're identifying good things. The AI is doing what it does. The reason why I do training workshops around this, I speak about this at events and conferences and SCOs and stuff like that. The reason why I do it the way that I do it is because just like anything else that you hand off to AI, if you don't understand the mechanics of it and how it works—I mean, I literally in my workshops, we do pen and paper. I make them do it—because you have to understand the pathways and the concepts and what makes sense. It's like something we've all gone through, right? You get something back from an AI tool and you're like, "That's not right." You have to understand it beforehand to be able to identify that it's wrong. And so I think there's a lot of value, especially for organizations where this might be the first time that they're doing some sort of win analysis. You can't just hand it off to AI and hope for the best and then go, "Okay, AI said we need to practice more negotiation skills," and then you waste all this time hiring John Barrows to come in and do negotiation training. But if you go down the wrong rabbit hole because AI told you to and nobody understood the situation enough to fact-check it, then you've just wasted a bunch of cycles. So that's why I really focus on doing this with your own brain without using AI on paper so that as an individual and as a team you understand what it is you're looking for. And then you can hand it off to the Rallies and the Gongs of the world. But you need to have that baseline understanding of what am I even looking for? AI is a thought partner, not a thought leader, y'all.

So, let me ask you a question. In your last seat inside of GTMorg, you were pointing AI at losses for a living, right? So if Reflect Path is right and studying wins is the missing piece, was that the wrong half of the problem to be spending your day job on?

That's a great question. So I actually went through this whole exercise and came up with the framework and kind of got to where I am now and what I'm doing now. And it's kind of the reason I jumped ship. I had access to all these tools and I just started playing around, right? Like I was working for an organization that had the primo, primo of all of the tech stack and I was like, let me get in here and find out what I can find. And that was actually where I figured this whole thing out. I was using Gong to look at QBR calls for our CSMs and I was expecting a lot of here's what went wrong, here's the patterns from all the losses, and it gave me back here's all the successes and here's what good looks like. And that was kind of an aha moment for me. And so I started quietly doing things on the side until I was ready to put together the framework and jump out the door and not be that guy sitting on the islands but like swimming away from the boat more. Going to go build my own boat.

I like that. Build your own boat.

You told podcast lately that repetition is a whole game on LinkedIn and pointed to a friend that we all know, Lindsay, known as the poopy pipeline girl for saying the same thing for years. Doesn't that turn thought leadership into a loop where consistency matters more than like being right or giving the right information?

That's a great question. I point back to there is a woman who wrote a book called "Her First 100K." Her name is escaping me right now, but that's okay. I followed her on LinkedIn for a long time. And I used to go nuts because she would post the same stuff over and over and over again. And I was like, "Girl, we know. You've told us the story about blah, blah, blah like seven times." And I realized, because I went and looked because I was curious, she was gaining like ten thousand followers a month. And I was like, "Oh, I've seen this a bunch of times, but they haven't." And her potential new audience hasn't seen this yet because they weren't here three weeks ago or six months ago or whatever the last time she posted this was. And so I think there's a balance between being known—like Lindsay is a perfect example. Being known for something, right? She understands pipeline analysis really well. We all know that because of the content that she puts out about poopy pipelines, and it's also catchy and it's memorable, right? So there's a degree to which repetition in your content is helpful because you become known for something. I talk about my framework all the time because people now know me for it and they might go, "Oh, this is something that we want to bring to our team." So there's a certain level of it's like billboards, right? Like you see the same Coca-Cola billboard essentially all the time, right? There's nothing new about their billboards. But then you have to add in the other layers of new ideas, new things that you've experienced. I think both of you are great at this. Like this is what's happening out there in the field today, this is what's happening with our customers, our clients today. But you still go back to the basics, right? So I think there's balance.

Balance is hard. Balance is hard. Fiona, in Doc's Grow and Tell podcast in May of 2026, you called the central nervous system the fastest supercomputer that existed before AI came along. And you built a coaching step around trusting that signal. Is that a finding or is that just a story that sells better than run more A/B tests on your talk track?

What kind of question is that, man? GTM uncensored.

I feel like I'm on Hot Ones and he just asked me like the most in-depth question ever after I just ate like the bomb beyond insanity.

Dale will tell a Hot Ones story, but we won't let him. So just go ahead and answer the question, please. Otherwise Dale's going to go on a tangent here about Hot Ones.

Oh, I could talk about Hot Ones all day, but anyway, we won't do that. I will answer the question. Okay. I did in fact do some research about that particular piece of information. When supercomputing surpassed the central nervous system is a little bit tricky to identify from what I have read. I'm not an expert. It is a really nice kind of like tagline quote though. But it is true that our central nervous system works really, really, really, really fast. I mean, think about the last time you saw a spider, right? Or the last time—like, your spider's a good example. My six-foot-two fifteen-year-old came in my office the other day and told me he couldn't go in his bathroom because there was a spider in there.

Right. And what happened inside of his brain the moment that out of the corner of his eye he saw that spider, which his brain interpreted as a threat, like the amount of things that took place inside his body in microseconds, nanoseconds in terms of his adrenaline spiked, his body probably tensed up like fight or flight, right?

All those things happen so fast they're not even noticeable. And that's what I'm talking about when I talk about the central nervous system being as fast as a supercomputer because all these things happen to us all the time, right? Outside stimuli or past context. All this stuff is going on in our brains all the time and we don't even know about it because it's happening so quickly.

But it's actually a lot of data that you can go back and that's why the last step in my framework is reflect. Because if you go back and realize, oh, I freaked out because there was a spider in the bathroom and here's the subsequent things that happened and that's why my heart rate was at 150 or whatever, you can go back and look at that data to help you make better decisions in the future.

I talk a lot more about that with leaders, especially around decision-making, like why did we hire this person? Why did we not do that? And we forget that there's all this information coming into our bodies and into our brains that is part of what we're basing our decisions on. And if you don't look back and figure out what it was—like, oh, we were going to hire this guy named Dale and I got this lump in the pit of my stomach when we talked about hiring him. And then we were going to hire this guy, Adam. And I leaned forward. I got excited. I was talking in a higher voice pitch.

Fiona Simpson, y'all, my new favorite guest on the GTM Uncensored podcast. But all that information that's flowing through your body is actually telling you, hey, this is a good idea or this is a bad idea. Hiring that Dale guy is going to be a disaster. And I didn't listen and I hired Dale anyway. And then I think back, oh, I had a pit in my stomach the whole time I thought about hiring him.

Now you can pay Adam. Now you can pay Adam. I'm here for it. I'm here for it. Dale, take us home. I think Fiona had a very good podcast. Brought a lot of great points, a lot of great advice. Fiona, you're welcome back on the show anytime you'd like.

This was fantastic. I'm so glad I could do this. You've gone through the GTM gauntlet. We've done a bunch of stuff. It's almost like the hop lens. We'll give you a layup for the last one. Where's your dream vacation destination? Tell the people what you've got.

Where's your dream vacation destination?

Oh, okay. Well, I'm spoiled because last summer my fiancé and I went to the Exumas in the Bahamas and we were actually going back in 13 days. It is the first place that we have ever gone where we said we should come back here and we really meant it and we are really going back. So yeah, I think as of right now, the vacation that I'm going on in two weeks is the dream vacation. But that could change. I love to travel, so I'm always open.

I love it. Any place is good. Dale loves to travel on his boat. But I guess if I had a boat, that's all I would use as well.

Fiona, thank you so much for joining the show. Where can people do some business with you? Shameless plug.

Yeah. So my website is reflectpath.com. It is going over a slight makeover. But all the information you need to get a hold of me is there. I'm also on LinkedIn all the time. Like, if you slide into my DMs during normal hours, I will probably respond immediately. That's how much time I spend on LinkedIn. The other day, I actually realized that I had LinkedIn open on my computer, my phone, and my iPad in the kitchen all at the same time. It's psychotic, but somebody's got to do it.

I'm with you, Fiona. Thank you so much for joining the show and thank you for being our most insightful, accurate, best guest ever.

I'm going to print that out from the transcript and frame it and put it in my office. Like, there's a spot for it right there. Adam J says, "I'm the best guest ever. That's all I need in my life." I love it. I'm here for it. Thanks, Fiona.

Thanks, fellas.