You asked your sales leader what next year looks like and got a number nobody can defend. The pipeline is "strong." The CRM went in a year ago and half the team only touches it when they feel like it.
Kim and I are on Milestone 15, the last stop in Module 5, and Kim's frame ran the whole episode: systems give you clear line of sight into the handful of data points that build a forecast, and governance is the guardrails, the business norms you can depend on, so "I want to grow 20 percent" has to survive the question of whether you have ever done it. The unlock for me was the difference between stages and influencers. The stages are the road. The opportunity is the car. Every podcast download, trade show, and phone call is an influencer pushing that car left to right. Confuse the two and you drown in data and still can't forecast. Then Kim gets into what most owners skip: making required fields required, reading close rates by rep instead of in total, and closing your pipeline every month the way your bookkeeper closes the books. I opened this one with the story of putting a new CRM on a screen in front of 30 people and asking what our stages should be. Don't do that.
This is a Ryan and Kim teaching episode, closing Module 5 (Predictable Revenue). Ep. 499 set the revenue architecture (Milestone 13), Ep. 502 mapped the user journey and what a customer costs (Milestone 14), and this one installs the systems that track it and the governance that keeps it honest (Milestone 15).
Kim takes the CRO seat and gets specific: her own arc from Excel to a custom-built CRM she calls a hot mess to a template system set up the implementer's way, which changed what she could see as a sales leader; the required-fields discipline she calls being "the asterisk queen"; why salespeople hating data entry is legitimate and the enforcement framing still has to be service, not policing; the activity-versus-opportunity tripwire that tells you which rep is hiding pipeline; and the monthly CRM close she named "start of month activities." Ryan runs the ownership frame: the meeting where he put a new CRM on a screen in front of 30 people with no ICP done and opened Pandora's box; the road-and-car model that separates stages from influencers; and the analogy that landed the episode, that closing your pipeline is exactly what closing the books is.
One thing this episode does not do: the ground-up forecast math. Ryan and Kim deferred it on air to a Q4 episode tied to budgeting season. This one is about the data and the guardrails that make a forecast possible in the first place.
Top 10 Takeaways
Systems come last. Lock your ICP and your user journey first, or you automate chaos.
"Grow 20 percent" is a wish until you check whether you have ever done it before.
You're the leader. Design your sales stages yourself. Don't put them to a vote.
Build stages from how you actually close deals, and deal in averages, not exceptions.
Stages are the road. The opportunity is the car. Every touchpoint is an influencer.
Three numbers build a forecast: conversion rate, average deal size, sales cycle length.
Make required fields required. It's service to the rep, not policing.
Read every number by sales rep. The team average hides your best and your worst.
Close your pipeline every month the way your bookkeeper closes the books.
Write down how revenue should work. Then you can tell a process problem from a people problem.
Chapters: (00:00) Welcome to milestone 15, closing out systems and governance
(03:11) Ryan's story: 30 people vote on new CRM stages
(13:18) Build sales stages from how you actually close deals
Podden och tillhörande omslagsbild på den här sidan tillhör
Ryan Tansom. Innehållet i podden är skapat av Ryan Tansom och inte av,
eller tillsammans med, Poddtoppen.
