Sales Pipeline

It follows active deals through qualification and discovery, solution validation, consensus and proposal, procurement and close, then handoff and learning. Milestones mark key exit decisions, while task lists organize work by stage. It supports collaboration around deals but does not replace a CRM’s account records, forecasting, or activity history.

The template includes a Weekly Monday Pipeline Review, a Wednesday Deal Execution Check-in, and a Last-Friday Quarterly Pipeline Retrospective. Use Monday to review coverage, stage movement, and risks; use Wednesday to resolve deal-specific execution issues. The retrospective is for reviewing outcomes and improving the next quarter’s process.

The Sales Manager or Pipeline Owner should set the review cadence and facilitate pipeline decisions. Each Account Executive is the DRI for their deals, with Sales Development, Solutions Engineering, Customer Success or Implementation, Revenue Operations, Legal, and Finance contributing when their work is needed. Keep role slots generic so the team cloning the template can assign its own members.

No. It provides a shared workspace for coordinating active-deal work, decisions, risks, and handoffs; it is not a system of record for customer data or sales reporting. Use it alongside a CRM when the team needs cross-functional execution around opportunities. Agree on which system holds the authoritative deal stage and value to avoid conflicting updates.

No workspace template can establish that a deal meets legal, privacy, security, or procurement requirements. The procurement and legal stage gives the team a place to coordinate review and identify readiness gaps, but your organization’s policies and authorized reviewers determine what approval is required. Add the applicable internal checkpoints and keep controlled contract records in approved systems.

A frequent problem is treating every stage as a status label without recording a decision, owner, and next action. Another is leaving the Account Executive’s DRI unclear or allowing deal risks to remain unresolved between reviews. Keep task lists tied to actual stage work, assign an owner to each action, and use the hill chart as a discussion aid rather than a substitute for evidence.

Start by adjusting stage tasks and milestone exit criteria to match your qualification method, approval path, and handoff process. Keep the five stage-based task lists if they reflect your workflow, and rename or split them only when teams have distinct, repeatable work. Set role slots to the functions involved in your deals and retain a specific cadence for each check-in.

Use the workspace to coordinate work and decisions, and use your CRM or approved sales systems for customer records and official forecast data. The template itself does not configure integrations, so define a manual update owner or follow your organization’s existing connected workflow. Avoid duplicating sensitive customer or contract details when a link or approved record reference is sufficient.

Clone the workspace at quarter kickoff, assign role slots, and confirm which active deals belong in scope. Set a DRI and next action for each deal, then use the Monday review to establish the initial view of coverage and risks. After the first quarter, use the retrospective to remove steps that did not support decisions and clarify any stage exit criteria that were repeatedly misunderstood.