Why Your Sales Pipeline Isn’t Closing Deals
A pipeline full of deals in the CRM shows how much has been entered and says very little about how much will close. Max Bevan, our principal account executive at Fast Slow Motion, talks with growing businesses about this problem every day, and he worked through it with Eric Housh on a recent episode of The Fast Slow Motion Podcast. This post draws on that conversation: what a working pipeline looks like at the deal level, why the process breaks as sellers are added, where to start fixing it, how to bring a sales team along, and what changes once it works.
A Stage Name Tells You Very Little About the Deal
Max’s starting point is that a deal sitting at discovery or proposal doesn’t tell you much until you look at what’s underneath it. He pointed to recent activity, upcoming meetings, the products the buyer wants, and the context around the deal, along with whether the rep knows the buyer’s business objectives, whether discovery was done properly, and whether anyone understands the timing and impact for the buyer if they move forward. We go deeper on this in Stuck Deals Look Healthy Until You Check the Details.
He also offered a simple test: ask a rep off the top of their head what the pipeline looks like and what is closing this week, and watch whether they need to open the CRM to answer. The healthy version is a CRM that matches the story the rep already carries in their head, which we cover in A Healthy Sales Pipeline Is One Reps Can Explain From Memory.
Deal Velocity Is the Number to Watch
Max said the goal is always deal velocity, meaning how fast the pipeline moves and how its pieces connect. Sales leaders need to understand, at the individual level, which stages a deal has to pass through, while executives need the KPIs that show actuals against forecast. Both views should come from the same system, and both depend on people looking at the data and having real conversations about it. Deal Velocity Matters More Than Deal Count covers how to track it.
Why the Process Breaks as You Add Sellers
Max described the early stage as a time when a little tape and glue holds things together, and at scale all of it comes apart. What works for ten salespeople won’t hold up for twenty, and it won’t come close for a hundred. He said you have to be intentional about what you’re scaling, starting with your average deal size or contract value and what has to be true to hit your targets. The CRM then needs to support your deal model, with required stages, defined information for reps to capture, and AI enriching deal data from meeting notes and other documentation so the context doesn’t depend on one person.
The Hero Model Has a Ceiling
With only a few sellers, Max said, businesses end up relying on a hero model, where the systems are anchored to one proficient person and nobody steps back to ask what process the business needs. The founder is often that person, the first seller with the original idea, and what got the founder to that point won’t necessarily get the next seller there. Adding salespeople to an unchanged process makes the existing problem larger, and we wrote about that transition in Founder Led Sales Got You Here and Won’t Scale.
Max’s reasoning is that a hero does things you can’t hire for and improvises outside the lines, so the process ends up shaped around the 10, 20, or 1 percent case, and outliers don’t scale. A hero can also push a deal through alone, while the scalable version loops in procurement and additional approvals. Once the CRM supports those steps, more sellers can follow the same path, and the numbers stop depending on personalities: one rep logs optimistic close dates, another logs conservative ones, and the objective metrics of the deal should be what tells you how much confidence the pipeline deserves.
Where to Start When Everything Feels Broken
The pull in a broken pipeline is to fix everything at once, and Max said the goal is to avoid boiling the ocean. You can’t jump from A to Z, but you can move from A to B to C to D, so the question becomes which quick wins are available given where the business stands today. His examples were standardizing the sales process, building automation around reminders, tasks, and follow-up, setting up a clean sales-to-service handoff after a deal closes, and improving visibility into invoicing and receivables. HubSpot Automation That Keeps Deals Moving covers the automation piece, and Fixing a Broken Sales Process Without Starting Over covers how to sequence the rest.
Where you begin depends on where you stand. Max said the questions include whether the business already has a CRM, whether people are trained on it, and whether the infrastructure is solid and needs adoption and training instead of a rebuild. Our job on those calls is to say what a prospect needs to hear, and sometimes that means telling them the tooling and process look solid and the real issue is culture, a rogue leader, or a lone-wolf mentality. The right first step varies by company, and some businesses need no rebuild at all.
Define What Done Looks Like
Max also pushes for an objective definition of done. A client might say they just need reps to close more revenue, and he treats that as a fine high-level goal that still needs a step back to ask which habits produce it, such as activity levels, outbound outreach, automation, shared calendars, or deal rooms. From there he asks what difference it would make if the team did that consistently, and the answers tend to be a higher close rate, a larger average deal size, and better-quality deals. Then the work is to implement it, test it through UAT and training, watch the data, and keep refining, aiming for 1 percent better each day in place of overhauling tooling, process, and culture overnight. Find the Sales Habits That Produce Revenue shows how to find those habits.
Getting the Sales Team to Change
Max said salespeople tend to be motivated by money, so tying process to commission gets attention quickly. His example was a rep who closes a deal without filling in the fields required for the sales-to-service handoff and doesn’t get paid until the process is followed. He called it extreme and a last resort, and said it works remarkably well. The gentler route is to communicate early, set expectations for the rollout, and connect each person’s own motivation to the process, since those habits make their job easier.
The harder case is the rep who jots notes on paper, takes calls on a cell phone, and never logs anything because the value isn’t visible to them. Max reframes the question for that person: what would change once logging into HubSpot, checking a dashboard, and working from a sales workspace showed them where and how to spend their time, with AI making the job easier? In his view the people and culture may not be the actual problem, since they just haven’t seen value in the tools introduced so far. There is no single silver bullet, and the fix combines training, adoption, process, and motivation. How to Get Reps to Use a CRM They Don’t Like goes into this.
Leadership carries part of it. Max described companies that roll out a new CRM and never change their own behavior, so leaders keep pinging people on Slack for deal updates in place of holding the team accountable for keeping the CRM current as the source of truth. He asked listeners to picture micromanagement going away because the data is trustworthy.
What Changes Once the CRM Works
Asked what’s different six months in, Max said he honestly doesn’t know what doesn’t change. He ties it to a scalable business framework: a business built on a platform with process, visibility, and automation. Once the CRM is adopted and built out properly, you have the data you need, you make objective decisions in place of gut-feel ones, and you have the tooling to scale. Habits produce results, and the data tells you which habits to adjust. Emotion, political maneuvering, and cultural friction fade because everyone is looking at the same scoreboard.
He described the effect across departments too. Each role keeps its own morning routine based on its KPIs while working from the same playbook, finance benefits downstream, and customer service works from the same contact record sales used, with the contract date, onboarding date, and any current support issues in view. The customer experiences one brand across marketing, support, billing, and sales. Max added that fixing this part of the business can expose problems elsewhere in the customer experience, and the data gives you a way to address them. What Changes Six Months After Your CRM Finally Works goes further on what six months in looks like.
The Cost of Waiting
On The Fast Slow Motion Podcast episode, Max answered the question of what it costs to wait another six months by saying the opportunity cost becomes almost impossible to calculate. Without consistent automation, task management, reporting, and objective KPIs, a team can’t set itself up for success. He compared it to a grocery checkout that asks every customer for a dollar donation: the ask comes every time, so plenty of people say yes, and tipping works the same way. Building automation so the CRM works for the team removes human error and gets the right steps followed each time, and the numbers climb as a result.
Listen to the full podcast episode here.