Hey Scott, I've dealt with this exact tension. What worked well at a large tech company where I managed enterprise accounts: every quarter, each teamsubmitted their own bottom-up forecast based on their pipeline and deal-level assumptions. These rolled up to leadership, who then reconciled them against the top-down target, which factored in company growth goals, board expectations, and macro context. The top-down number became the single source of truth for the company. But the bottom-up versions didn't disappear, they lived as the operational forecast each team worked from day to day. When there was a gap between bottom-up and top-down, that gap became THE conversation in the forecast call. The key that made it work: one shared definition of what counts as a "committed" deal vs. "best case" vs. "pipeline." Without that shared language, Sales and Finance will never agree on a number because they're literally counting different things. To your specific question about centralized vs. varying logic: I'd push for centralized deal-stage definitions and win probability assumptions (the source of truth), but let each group layer their own lens on top. Not everyone will see the same number. That's fine, as long as everyone starts from the same data and the deviations are explicit, not hidden.
Retyan A. They did act on it! And the slack messages were not private messages, they went to a channel where all the sales org saw them, which increased accountability. Also this topic was included on the weekly meetings, so everyone had to have an answer for each client that was detected as potential churn.
We saw something similar at Fintech I worked at, on the post-sale side. Once deals closed, attention from AEs dropped, and churn signals only became visible when it was already too late. What helped wasn’t more check-ins, but making risk visible earlier. We identified early churn signals (engagement, inactivity, usage patterns) and pushed them via Slack to AEs with context on why the account might be at risk, so they could take action before it showed up in the numbers. Shift was basically from reactive → to signal-driven.
Hey Khalid J.! My instinct would be to fix the parts of the funnel where revenue is most likely getting lost before trying to do more. So the first 2–3 things I’d prioritize: 1. Clear qualification + routing logic If there’s decent inbound, I’d make sure the team is not treating all leads the same. I’d define what a high-value lead actually looks like, then build a simple scoring / prioritization model so the best opportunities get fast attention. And make sure everyone knows who the ICP is! 2. Tighter follow-up ownership and SLAs A lot of revenue gets lost not because of demand, but because no one is clearly accountable for speed-to-action, next steps, and persistence. I’d make ownership really explicit across handoffs and follow-up. 3. Basic funnel visibility before more experimentation I’d want a simple view of where things are breaking: response time, meeting booked rate, conversion by source/segment, and drop-off points. Not a perfect dashboard , just enough to see where execution is weak. One mistake I see a lot at this stage is trying to fix the problem by generating more top-of-funnel before the operating system is working. If inbound is already there, the biggest opportunity is usually better prioritization, cleaner execution, and stronger follow-through. I’ve seen this firsthand in a recent role where the biggest unlock wasn’t “more leads,” it was building better lead scoring, routing, and handoff discipline so the team could focus faster on the opportunities most likely to convert.
Speed matters, but only if you qualify well and bring the right stakeholders in early. Otherwise you’re just accelerating the wrong conversations.
