Why forecasts fail when pipeline hygiene drifts
Deals sit in the same stage for six weeks because nobody logged the buyer’s real blocker. Managers rebuild forecast slides from memory. Pipeline Management is the daily operating view that keeps stage, next action, and owner honest before Ben or leadership reads revenue numbers.
What Sal does in pipeline management
Sal tracks deals across your configured revenue motion, highlights stale opportunities, and proposes next actions grounded in CRM fields you authorize. He accelerates reviews; he does not sign forecasts or commit discount terms.
A familiar example: end-of-quarter stage cleanup
Imagine a SaaS team ten days from quarter close with forty opportunities still marked “proposal sent.” Sal groups deals missing next meetings, flags accounts without executive sponsor notes, and suggests activity plans: schedule validation calls, confirm legal review, or move lost deals out of commit. Zed can open a Mission Log item for the rev ops owner to audit stage rules before leadership reads the commit number.
Pipeline views leadership actually uses
Views emphasize motion, not decorative charts. You see stage distribution, aging, and recommended focus areas for the week. The intent is a sales OS dashboard reps and managers share, not a static export emailed on Fridays.
Stage recommendations with human judgment
Sal may suggest stage changes when activity patterns match your playbook. Reps and managers confirm before customer-visible fields change. Sal explains why a deal looks stalled instead of silently moving cards.
Activity plans that match your playbook
Activity plans translate strategy into sequenced tasks: research, multi-threading, proposal follow-up, or executive alignment. They link to outreach and calling capabilities when you approve those motions separately.
Approvals when CRM touches customers
Updating an opportunity note internally differs from triggering a customer email from CRM automation. Product policy requires approval when CRM updates notify customers. Sal respects that boundary.
A credible first mission
Run a weekly pipeline review on one business unit: identify top ten stale deals, assign Sal-suggested next actions, and measure stage movement after two weeks. Fix CRM connector health with Ian before blaming the recommendations.