# Sales Pipeline Templates in 2026, The Operator's Field Guide > Canonical: https://www.yalc.ai/blog/sales-pipeline-templates/ The stages, fields, and forecast math a real sales pipeline template carries, plus the operating system that runs it after you download the file. Sales pipeline templates are prebuilt stage models that give a sales team a shared way to move deals from first touch to closed won. The strong ones set stage entry criteria, deal owners, required fields, and weighted forecast math, so the pipeline you review on Monday reflects what reps actually did, not what they hoped. Every template gallery online looks the same. A stage list from Lead to Closed Won, probability weights, a color coded status column. The template is not the problem. The problem is what nobody ships alongside it. Entry criteria, owners, next step rules, and the review rhythm that turn a spreadsheet into a working operating system. This guide sorts sales pipeline templates by format and by fit. Spreadsheet, CRM, and kanban board. Then it walks the fields and math that actually change behavior, and closes with what to do the moment the template stops answering your questions. ## What a sales pipeline template actually does A sales pipeline template is the front end of a sales process. It structures the way a deal enters the pipeline, moves stage by stage, and exits either closed won or closed lost. The columns matter less than the discipline they enforce. Anything that lets a rep drag a deal to the next stage without meeting a written criterion is not a template. It is a diary. The distinction shows up on Monday. In a template that works, a pipeline review is a five minute conversation about the three deals that broke a rule. In a template that does not, the review is a rescue mission on twenty stale opportunities that nobody wants to close out. The reason is not laziness. The template never told the rep what "Qualified" or "Proposal Sent" meant, so nobody ever agreed. If you want the operating layer around the template, most of it sits in [what sales operations owns](/blog/what-is-sales-operations/). Stage definitions, field enforcement, and forecast hygiene are ops work, and the template is the artifact ops publishes to sales. ## The 7 stage skeleton every sales pipeline template needs Five to seven stages is the sweet spot for a B2B pipeline. Fewer than five and you cannot see where deals stall. More than seven and reps skip stages to reduce clicks, which corrupts the report before the CRM even loads. The [seven stage pattern most operators land on](https://www.spekit.com/blog/sales-pipeline-stages) is a good starting point. - **Prospecting.** A named account matching the ICP has been identified. Entry criteria: fits the ICP filter, has a decision maker mapped, no active opportunity in the last 90 days. - **Contacted.** First outreach has landed. Entry criteria: at least one message sent through email or LinkedIn with a documented reason to reach out. - **Qualified.** A conversation confirmed budget, authority, need, and rough timeline. Entry criteria: qualification call notes filed, next step scheduled. - **Proposal.** A written proposal or scoped quote is in the buyer's hands. Entry criteria: proposal document linked on the deal, sent date logged. - **Negotiation.** Terms, price, or scope are being pushed on. Entry criteria: at least one written objection or redline documented. - **Closed Won.** Contract signed. Entry criteria: signed order form or subscription live, revenue tagged. - **Closed Lost.** Deal is over. Entry criteria: written reason for loss and competitor if any. The trick is not the stage names. Every stage carries a written entry criterion. The moment you can hand your template to a new rep and they move deals correctly on day one without asking a manager what stage anything belongs in, the template is doing its job. For the qualification step specifically, the [Yalc lead qualification skill](/skills/qualify-leads/) runs the criteria as a checklist, so a rep or an agent moves a deal into Qualified only when the four boxes are ticked. That is the difference between a stage that means something and a stage anyone can drag deals into. ## Sales pipeline templates by format Every pipeline template lives in one of three formats. Which one fits depends on team size, ops maturity, and how tightly the pipeline needs to talk to the rest of the stack. ### Spreadsheet templates for Excel and Google Sheets The starter format. One tab, one row per deal, columns for stage, deal size, close date, probability, and next step. Fits a founder led team of one to three sellers who need to prove a stage definition before buying a CRM. Options like the [Smartsheet sales pipeline template gallery](https://www.smartsheet.com/content/sales-pipeline-template), the [Close spreadsheet round up](https://close.com/blog/sales-pipeline-templates), and OnePageCRM's Excel model give you the columns and the weighted forecast formulas already wired. The tradeoff is manual upkeep. Every stage move is a hand edit. Every forecast refresh is a rebuild. Once the team crosses roughly fifty active deals or two full time sellers, the sheet becomes a full time job. ### CRM templates in HubSpot, Pipedrive, Zendesk, Salesforce The moment ownership rules, activity capture, and multi rep visibility matter more than portability, the pipeline belongs in a CRM. HubSpot ships a free lead tracker in Excel that maps cleanly into HubSpot CRM when you outgrow it. Pipedrive gives you a kanban style deal board that reps actually use because moving a card is one click. Zendesk and Salesforce ship the standard seven stage skeleton with permissioning built in. A CRM template pays off when three things line up. You have a dedicated ops owner who will enforce stage definitions. You have a reporting need beyond a single tab. And you have a manager who runs a pipeline review that references the CRM, not the personal notebook a rep keeps on the side. Miss any one and the CRM template becomes an expensive spreadsheet reps update once a week. Piping CRM data into a reporting layer is where most templates start to earn back their price. The [sales dashboard patterns leadership actually reads](/blog/sales-dashboard-examples/) all assume clean stage data underneath, and none of them survive a CRM where reps and ops disagree on what "Qualified" means. ### Kanban and workspace templates in Monday, Asana, Airtable, Notion The board formats fit when sales work has to sit next to project delivery, onboarding, or account expansion in the same workspace. Monday's pipeline template gives you a board view with integrations to marketing tools. Asana lets sales work sit next to onboarding tasks so a closed deal moves into implementation without an export. Airtable is a spreadsheet database hybrid that bridges the Excel to CRM gap. Notion works for teams that treat every deal as a doc with linked pages. The strength of these formats is cross functional visibility. The weakness is reporting. Board tools give you a great single deal view and a mediocre roll up view. Once you need weighted forecasts by rep by month, the board is fighting your finance team, not helping them. ## The fields every sales pipeline template must carry The stage list is the skeleton. The fields are the muscle. A template without required fields is a template reps will fill halfway and leadership cannot trust. - **Deal name** with a naming convention. Company plus product line beats freeform. - **Stage** with a written entry criterion attached in the template docs. - **Deal owner.** One name. Not a team. Not a channel. - **Deal size.** Annual contract value, not total contract value, unless your team has agreed on the math. - **Expected close date.** A date that must be updated when the deal slips. - **Probability weight.** Set per stage, not per deal, unless a rep can justify the override with notes. - **Next step** and a due date. This is the field that separates a live pipeline from a graveyard. - **Source.** Inbound, outbound, referral, partner. Feeds attribution. - **Loss reason** on Closed Lost. Feeds the ICP refinement loop. A template carrying these fields with required validation is the same template a small team runs in Sheets and a bigger team runs in HubSpot. The infrastructure changes. The contract with the rep does not. For the field level definition of who the deal is even for, the operator work of [tightening ICP before it hits the template](/blog/icp-definition/) sits upstream of every deal name and every source tag. ## Weighted forecasting and pipeline coverage math A template with weighted forecast math is what turns pipeline into a number the CFO trusts. The formula is unromantic. Weighted pipeline equals the sum of deal size multiplied by stage probability for every open deal. Assign a probability per stage in the template. Prospecting at 5 percent. Contacted at 10. Qualified at 25. Proposal at 50. Negotiation at 75. Closed Won at 100. Reps do not override the number unless they document why. Then compare the weighted total to the quarter's quota. Healthy B2B teams target a [3x to 4x pipeline coverage ratio versus quota](https://www.captivateiq.com/blog/sales-pipeline-metrics), because slip rates and loss rates carve the pipeline before the quarter closes. Coverage math is where most templates quietly break. A template that lets a rep hold a Proposal stage deal for ninety days with no next step is padding coverage, not building it. A template that hides stalled deals under a "Nurture" bucket is padding coverage. Run one filter monthly. Deals with no activity in fourteen days. If more than 20 percent of pipeline value sits in that filter, forecast accuracy is already broken and no template will save it. The [operator playbook for sales forecast accuracy](/blog/sales-forecast-accuracy/) covers the review rhythm that keeps the number honest. Probability is a scoring problem underneath. If your stage weights feel wrong, run [lead scoring against the deals that closed](/blog/what-is-lead-scoring/) and calibrate the stage percentages against what actually happened, not what the CRM defaulted to on install. ## Sales pipeline vs sales funnel, at the template level The two get confused because the templates look similar. A pipeline is what sellers do. A funnel is what buyers do. A pipeline template tracks stage moves, activity, and next steps for a specific deal. A funnel template tracks conversion rates from stage to stage across the whole book. You need both, but they answer different questions. A pipeline review asks which deals need action this week. A funnel review asks which stage is leaking and why. Running a pipeline template as if it were a funnel is how forecasts get inflated. Running a funnel template as if it were a pipeline is how deals stall. ## Where sales pipeline templates quietly fail Templates ship as static files. Real pipelines run as living systems. That gap is where every template gallery loses the reader. The failure modes are the same across formats. Stage definitions drift because no one updates the docs when the sales motion changes. Ownership fields drift because reps leave and the account never gets reassigned. Activity capture drifts because reps log calls after the fact, if at all. Signal capture is nonexistent because a spreadsheet cannot listen for a funding round or a leadership hire on its own. And forecast math drifts because probability weights get set once and never recalibrated against actual close rates. None of these are template problems in the strict sense. They are operating problems, and the template is the surface area where they show up. This is why teams that switch from Sheets to HubSpot to Monday to a shiny new AI CRM every eighteen months keep having the same conversation about pipeline hygiene. The template is not the leak. The operating layer around it is. For teams treating the pipeline as one input into a larger [GTM stack](/blog/gtm-stack/), the template needs to talk to enrichment, sending, and signal capture. If it does not, reps become the integration layer, and reps hate being the integration layer. ## Turning the template into a working operating system Yalc is the operating system that runs the pipeline the template describes. It sits on your machine, configured in markdown, talks to your data providers and CRMs through real APIs, and runs the middle mile work no template will run on its own. Sourcing, enrichment, activity capture, stage transitions when a rule matches, and reporting into the format leadership already reads. The point is not another CRM. The template you already use is fine. Yalc replaces the glue that keeps the template accurate. When a prospect matches ICP and gets a hiring signal, Yalc drafts the outreach and creates the deal in the right stage with the right owner. When [Crustdata](/tools/crustdata/) surfaces a new decision maker at an open account, Yalc updates the contact record without a manual export. When a reply comes back positive, Yalc moves the stage forward and stamps the next step. The CRM the template lives in stays the same. What changes is that the pipeline stops being a spreadsheet reps forget to update and starts being a system that updates itself. Three architectural properties matter for pipeline work. It is agnostic, so the same template logic runs whether the pipeline lives in HubSpot, Salesforce, Airtable, or Notion. It is interoperable, so the [HubSpot MCP](/mcps/hubspot/), [Notion MCP](/mcps/notion/), and [Airtable MCP](/mcps/airtable/) all plug in with equal weight. And it is modifiable, because every stage rule, every field mapping, and every notification lives in a markdown file you can read and edit like code. When ops changes what "Qualified" means, the change ships as a git commit, not a memo. That last property is what makes the template survive a hiring wave. New reps read the file that defines the stages. New AI agents read the same file. The pipeline template stops being tribal knowledge and starts being version controlled infrastructure. Signal driven entry criteria is the piece a static template cannot ship. Yalc reads [buying signals like hiring, funding, and technographic change](/blog/signal-based-outbound/) through providers like [PredictLeads](/tools/predictleads/), matches them against your ICP, and creates the deal in the Prospecting stage only when the signal is real. That is the difference between a template that fills with noise and a pipeline that only holds accounts worth working. ## What to do this week Open the sales pipeline template you use today. If it does not have a written entry criterion for every stage, that is the first hour. If a rep cannot tell you which two fields are required and which three are optional, that is the second. Once the contract with the rep is clear, run one pipeline review against the template and log every deal that broke a rule. That list is your operating manual for the next month. Then decide if the template is fighting you. If the stage moves you want cannot happen without an integration you do not own, the template is not the problem, the glue is. That is when a template becomes a starting point and the operating layer around it becomes the actual work. The [operator's guide to qualifying sales leads](/blog/how-to-qualify-sales-leads/) is a good place to start the audit, because a broken Qualified stage is where most templates first lose credibility. ## Frequently asked questions ### What is a sales pipeline template? A sales pipeline template is a prebuilt structure that defines the stages a deal moves through, the fields a rep must populate at each stage, and the forecast math the pipeline rolls up to. It can live in a spreadsheet, a CRM, or a kanban board. What makes it useful is the entry criteria attached to each stage, not the columns themselves. ### How many stages should a sales pipeline template have? Most B2B teams land on five to seven stages. Fewer than five and you lose visibility into where deals stall. More than seven and reps skip stages to reduce clicks, which corrupts the report. The most common skeleton is Prospecting, Contacted, Qualified, Proposal, Negotiation, Closed Won, and Closed Lost, each with a written entry criterion. ### What is the difference between a sales pipeline and a sales funnel? A pipeline tracks what sellers do on specific deals. A funnel tracks what buyers do across the whole book. A pipeline template shows stage, owner, activity, and next step for each opportunity. A funnel template shows conversion rates from stage to stage in aggregate. Teams need both. They answer different questions. ### Is Excel or Google Sheets good enough for a sales pipeline template? Yes, for a team of one to three sellers with under fifty active deals. Sheets forces you to make the stage definitions explicit before you buy a CRM, which is a healthy exercise. It stops working once ownership rules, activity capture, and multi rep reporting matter more than portability. That transition typically happens between the first and third full time seller. ### What fields should a sales pipeline template include? At minimum, deal name, stage, deal owner, deal size, expected close date, probability weight, next step with due date, source, and loss reason on Closed Lost. Anything less and the pipeline report becomes opinion. Anything more and reps stop filling the required fields. Required means required, and the template documentation should say which fields are enforced. ### How do I know if my sales pipeline template is working? Run one filter monthly. Deals with no activity in fourteen days. If more than 20 percent of pipeline value sits in that filter, the template is not doing its job. That failure is almost always upstream, in missing entry criteria or missing owner rules, not in the columns. Fix the operating layer, not the template.