Latest / Sales Leadership with Fexingo: Quota Carriers, Sales Managers, and Revenue Teams / How Sales Teams Turn Pipeline Into Predictable Revenue
Transcript
- Lucas: Look, if you are listening to this while staring at a CRM dashboard that looks like a graveyard of stuck opportunities, you are not alone. The problem is not that your reps cannot sell; it is that your pipeline is lying to you about when those deals will actually close. Luna: I see this all the time. A team reports four million in pipeline for the quarter, but half of it has been sitting in stage two for six weeks with zero movement. Lucas: Exactly. And the rep tells the manager it is still alive because they do not want to admit it is dead. So the manager includes it in the forecast, the executive believes the forecast, and then everyone gets blindsided when the quarter ends. This is what I call the velocity gap. It is the difference between what the numbers say and what the behavior shows. Luna: So you are saying the issue is not volume, it is the speed at which deals move through the stages? Lucas: Precisely. Volume is easy. You can always find more leads. But velocity requires discipline. Most sales organizations measure how many deals they have, not how long those deals stay stagnant. If a deal sits in negotiation for thirty days, it is not a negotiation anymore. It is a ghost. Luna: That is a sharp way to put it. Why do you think reps let them sit there instead of marking them closed lost? Lucas: Fear. They fear that closing a deal as lost makes them look bad to their manager. So they hope the buyer will come back next month. But that hope costs the company real revenue certainty. When you have a hundred ghosts in your pipeline, your forecast is just a wish list. Luna: So how do you fix the culture so reps feel safe killing bad deals? Lucas: You reward the kill. I know that sounds counterintuitive, but top performing teams celebrate when a rep marks a deal closed lost early. It frees up capacity. It stops the rep from wasting time on a zombie opportunity. It also gives the manager accurate data to adjust the rest of the pipeline. Luna: That feels risky though. If a rep kills too many deals, won't the manager panic about missing quota? Lucas: Only if the pipeline was already thin. If you have a healthy pipeline, killing bad deals strengthens the good ones. It forces the team to focus energy where it matters. But most managers are addicted to the vanity metric of total pipeline value. They would rather have five million in garbage than four million in gold. Luna: Right. Because five million looks better on a slide deck than four million, even if the four million closes faster. Lucas: Spot on. So the first step is stage hygiene. Every stage in your CRM needs a clear definition of what progress looks like. If a deal moves from stage two to stage three, there must be a specific artifact. A signed proposal. A technical demo completed. A stakeholder map. No artifacts, no movement. Luna: So you are tying stage progression to tangible evidence rather than hope. Lucas: Yes. Hope is not a strategy. Evidence is. If a rep says the deal is moving, show me the email from the champion. Show me the budget approval. If you cannot produce the evidence, the deal stays in its current stage. Period. Luna: This sounds like it requires a lot of micromanagement from the manager though. Lucas: It requires less micromanagement in the long run. When you review deals based on evidence, you stop guessing. You spend your time helping reps who have the evidence but lack the skill, rather than chasing reps who have neither. It makes coaching much more targeted. Luna: I like that. Targeted coaching versus general encouragement. Lucas: Exactly. Now, let us talk about the financial side of this. When deals stall, the cost of acquisition goes up. You have spent months nurturing a lead, doing demos, sending proposals. If that deal dies after ten months, your return on investment is terrible. Luna: So velocity is actually a margin play, not just a revenue play. Lucas: It is both. Faster deals mean lower customer acquisition cost. That improves your gross margin. And it also means you can reinvest that saved capital into finding new prospects sooner. It creates a flywheel effect. Good velocity breeds more resources, which breeds more velocity. Luna: But what about the large enterprise deals that naturally take longer? Does this approach punish complex sales? Lucas: No, it adapts. Enterprise deals have longer cycles, but they still need milestones. You might have twelve stages instead of six. But each stage still requires proof of progress. You cannot go from discovery to procurement in one leap. There must be legal review, security audit, executive alignment. Each step needs an artifact. Luna: So the principle is the same, just the granularity changes. Lucas: Correct. The devil is in the details of those definitions. If your legal review stage does not require a redlined contract, your team will skip it. Then you get surprises later. Specificity prevents surprises. Luna: This reminds me of how product teams manage software releases. They have strict criteria for moving from beta to production. Lucas: That is a great analogy. Sales should be treated with the same rigor. It is a product delivery process, just with people involved. You do not ship buggy code, so you should not ship deals that haven't passed quality checks. Luna: I think some sales leaders struggle to implement this because it feels like extra work for the reps. Lucas: It is extra work upfront, but it saves hours later. Imagine a rep spending twenty minutes updating the CRM with proper notes versus spending two hours trying to revive a dead deal that never had a chance. Which is more efficient? The former. Reps will embrace it if they see it protects their time. Luna: So positioning it as time protection rather than compliance is key. Lucas: Absolutely. Frame it as: do this now so you do not waste your afternoon on a dead end. That resonates with smart professionals. Nobody likes wasted effort. Luna: Before we go deeper into the metrics, I want to pause here for a moment. These conversations rely on listener support to keep running ad-free. If these insights have moved your work forward in some small way, consider buying me a coffee dot com slash fexingo. A couple of dollars a month is genuinely what keeps these going. It helps us keep producing high-quality analysis without selling your attention to advertisers. Lucas: Thank you for that. It really does make a difference in our ability to dig into these specifics. Luna: Yeah, and it lets us focus on the substance rather than the sponsors. Lucas: Let us get back to the metrics then. Once you have clean pipeline and stage hygiene, you can start measuring velocity accurately. The key metric is average days in stage. If your average days in negotiation is forty-five, but your industry benchmark is twenty, you have a problem. Luna: Where do you find those benchmarks? Are they available publicly? Lucas: Not always perfectly matched to your niche, but general SaaS and B2B benchmarks exist. For mid-market software, average cycle length is often around ninety to one hundred twenty days. If you are seeing two hundred, you need to investigate. Look at the top quartile of your team. How fast are they closing? What are they doing differently? Luna: So you benchmark against your own best performers, not just external averages. Lucas: Always. Your internal best practices are more relevant than external generic data. If your top rep closes in sixty days, ask them how they got there. Did they engage the CFO earlier? Did they run a pilot program? Replicate that success across the team. Luna: This shifts the focus from individual heroics to systematic replication. Lucas: Exactly. You want to build a machine that works regardless of who is holding the phone. Velocity is the heartbeat of that machine. When the heart beats strong, the body thrives. Luna: What happens when a rep consistently stalls deals across multiple accounts? Lucas: That is a performance issue. If they have the skills but not the discipline, they need coaching on process. If they lack the skills, they may need reassignment or exit. You cannot let one person drag down the team's overall velocity. It affects morale and forecast accuracy. Luna: So velocity acts as an early warning system for talent issues too. Lucas: It does. Slow movers are often disengaged or struggling. Catching it early allows you to intervene before the rep burns out or quits. It is a retention tool as much as a productivity tool. Luna: I had not thought about it that way. Keeping reps engaged by giving them wins. Lucas: Right. Wins create momentum. Dead deals create fatigue. Fast tracks keep the energy high. High energy leads to higher closure rates. It is a positive feedback loop. Luna: So the ultimate goal is to make the pipeline transparent, honest, and fast-moving. Lucas: Transparent, honest, and fast. Those are the three pillars. If you master those, your forecast becomes reliable. Your reps become happier. Your customers get served faster. It is a win win win scenario. Luna: It seems like the hardest part is getting the initial buy-in to change the culture. Lucas: It is. But once you show the data, the resistance fades. Show the team that cleaning up the pipeline results in more accurate forecasts and less firefighting. People love certainty. Give them certainty, and they will follow you. Luna: Do you think this approach scales well as companies grow from startup to enterprise? Lucas: It scales better than any other approach. Startups can survive on chaos, but enterprises cannot. As you add layers of management, chaos becomes expensive. Discipline becomes essential. Velocity frameworks provide the structure needed for scale. Luna: So it is not just a best practice, it is a survival mechanism for growing sales orgs. Lucas: Without a doubt. If you want to build a lasting revenue engine, start with velocity. Treat your pipeline like the valuable asset it is, not just a number on a screen. Luna: Agreed. Clean pipeline, clear evidence, fast movement. Lucas: Exactly. And if you implement just one thing today, make it the artifact rule. No proof, no progress. See how your forecast changes in thirty days. Luna: A simple rule with massive impact. I am curious to hear how listeners apply this to their own teams. Lucas: We will be watching for those stories. Until then, keep your pipeline clean and your velocity high.