Sales Pipeline Template: A Working Setup You Can Build in 20 Minutes

Search "sales pipeline template" and you get one of two things. Free download forms that exchange an email for a Google Sheet you will open once and forget about, or vendor blog posts that describe a 14-stage pipeline so elaborate that nobody on your team will ever maintain it. Neither is what you actually need.

A sales pipeline template is not a download. It is a structure: the stages, fields, and views that make a CRM behave like a pipeline instead of a contact dump. This guide walks through the template that actually works for small and mid-size sales teams: the six stages every B2B pipeline needs, the eight to ten fields per deal that earn their seat, the three views that turn the structure into a working tool, and the choice between building it in HubSpot, Notion, or a hybrid of both. Build it in 20 minutes, ship deals through it next week.

What a sales pipeline template actually is

A sales pipeline template is the schema and structure you drop into a CRM (or a spreadsheet, or Notion) to start tracking deals on day one. At minimum it includes a list of stages, a small set of fields on each deal, and at least one view that lets a rep or manager see the pipeline at a glance.

The thing that separates a useful template from a useless one is restraint. The 14-stage pipelines that show up in vendor blog posts are usually built by people who have never had to update them on a Tuesday afternoon between calls. A template that requires a rep to think for ten seconds about which of three similar-looking stages a deal belongs to is a template the rep will eventually stop updating, and a pipeline that nobody updates is worse than no pipeline at all.

The template below is deliberately small. Six stages, nine fields per deal, three views. Add complexity only when the team genuinely needs it.

The six stages every B2B pipeline needs

Most B2B sales motions fit cleanly into six stages. Different teams use different names for the same stages, but the underlying shape is the same.

1. New. A deal has been created. You have a contact, a company, and a reason to believe there is something to talk about, but nothing is scheduled yet.

2. Discovery. A qualification conversation is booked or completed. You have either spoken to the prospect about their needs or have a meeting on the calendar where you will. The deal sits here until you decide whether there is real fit.

3. Demo or Scope. You have shown the product, walked the prospect through your service offering, or scoped the work. For SaaS this is the demo. For services and agencies this is the working session where you map the engagement.

4. Proposal. You have sent pricing, a statement of work, or a formal proposal. The ball is in the prospect's court.

5. Negotiation. The prospect has come back with redlines, pricing pushback, or stakeholder questions you need to work through. Not every deal lands here. Some skip from Proposal directly to Closed Won.

6. Closed Won or Closed Lost. The deal is decided. Most CRMs treat these as two distinct stages or as a single Closed stage with a Won or Lost flag. Either works.

Six stages is enough to model the meaningful transitions in a B2B sale and few enough that reps can update them without thinking. Templates that add stages like "Awareness" or "Engaged" or "Champion Identified" usually add update friction without producing better forecasts. The exception is teams with long enterprise cycles (12 plus month sales motions, six plus stakeholders), where an extra stage between Discovery and Demo can be earned. Almost no other team needs it.

The stage names matter less than the entry criteria. A pipeline where every rep agrees on what "Discovery" means is more valuable than a pipeline with twelve perfectly-named stages where two reps disagree on whether a given deal is in stage three or stage four. Write the entry criteria for each stage in one sentence, share it with the team, and revisit it once a quarter.

The fields that earn their seat on a deal

A deal record with 30 fields is a deal record that nobody fills in. The nine fields below cover what almost every sales team actually uses for forecasting, reporting, and pipeline reviews. Add anything else only when you have a specific reason.

• Deal Name (text). The format that works best is "Company Name, Engagement Type" so the pipeline view is scannable.
• Value (currency). The total deal value or, for retainers, the annualized value. Most CRMs handle one of these natively, but you usually have to add a custom property for the other.
• Stage (single select). The six stages above.
• Expected Close Date (date). The rep's best estimate. Forces reps to maintain a view of when the deal will close, which is the single most valuable input to a forecast.
• Probability (number or select). The chance the deal closes, expressed as a percentage. A clean default is 10 percent for Discovery, 25 for Demo, 50 for Proposal, 75 for Negotiation, 100 for Closed Won. Customize per team motion.
• Owner (person). Who is responsible for the deal. Required for any team with more than one rep.
• Primary Contact (relation to Contacts). The main champion or buyer at the prospect company.
• Company (relation to Companies). The account the deal belongs to.
• Lead Source (single select). Inbound, Outbound, Referral, Event, Partner. Required if you want to report on which channels are producing pipeline.

Nine fields, no fluff. Add a Notes field at the record level for freeform context, and resist the urge to create a separate property for every type of note. If "internal politics at the account" needs its own field, that means the activity log is not working, and the fix is the activity log, not another property.

The three views that turn the structure into a working tool

A pipeline without views is a list. The three views below cover the daily-use cases for almost every team.

Pipeline (Board view). Grouped by Stage, sorted within each stage by Expected Close Date ascending. This is the view your reps live in. Configure the column total to sum Value (or Weighted Pipeline if you have built that calculation) so the team can see the total opportunity at each stage at a glance.

Closing This Quarter (Table view). Filtered to Expected Close Date this quarter, sorted by Value descending. This is the view your sales manager opens during pipeline reviews. It surfaces the deals that matter most for the current period without forcing the manager to scroll past every Discovery-stage long shot.

My Deals (Board view). Same as the Pipeline view, but filtered to Owner equals current user. This is the view each rep makes their default. Removes the noise of everyone else's deals so the rep can focus on their own work.

That is three views. Most pipeline templates ship with eight to twelve, half of which nobody opens. Three is enough.

Building the template in HubSpot

HubSpot is the strongest place to build a sales pipeline template for any team with more than one rep, because the email logging, activity timeline, and reporting are built in.

The setup steps in HubSpot:

1. Go to Settings, Objects, Deals, Pipelines. Either edit the default pipeline or create a new one named after your motion (Sales, New Business, Renewals, depending on the team structure).
2. Configure the six stages above, with the probability defaults set on each stage so HubSpot's built-in forecast calculations work.
3. Add the custom properties the standard schema is missing. The Deal object ships with most of the nine fields above. Lead Source is usually the one you need to add.
4. Build the three views above. HubSpot calls them "deal views." Save them as team views so everyone gets the same defaults.
5. Configure the deal record layout so the nine fields appear in the order that matches the sales motion (Stage and Expected Close Date at the top, supporting fields below).

Total setup time: 15 to 20 minutes if you have HubSpot admin access. The result is a working pipeline that your team can start using the same day, and that will keep working as you add reps, contacts, and revenue.

For a deeper look at how HubSpot handles the structured side of selling, the HubSpot vs Notion comparison walks through where HubSpot's strengths actually sit.

Building the template in Notion

For solo founders or two-person teams that want to delay paying for a CRM, the same template can be built in Notion. The implementation looks like this:

A Deals database with the nine fields above. Single-select Stage, currency Value, date Expected Close Date, number Probability, person Owner, relations to Contacts and Companies databases, single-select Lead Source. A Board view grouped by Stage and a Table view filtered to Expected Close Date this quarter.

The full Notion CRM implementation, including the Contacts, Companies, and Activities databases that round it out, lives in the Notion CRM template guide. The bare pipeline above is the minimum viable version.

The trade-off is documented in how to use Notion as a CRM and why you still need HubSpot. The short version: a Notion pipeline works for solo operators tracking fewer than 20 active deals. Beyond that, the absence of automatic email logging, native automation, and a built-in activity timeline starts costing more than the CRM subscription would. Plan to migrate to HubSpot when you cross either threshold.

The notes that make the template work over time

A pipeline template covers the structured side of selling. The qualitative side (call summaries, account strategy, internal politics, deal narratives) does not fit in a Stage or a Value field. It lives in notes.

The teams that get the most out of their pipeline are the ones where every deal has a current, readable activity log. The team without that ends up with a pipeline that lists 40 deals and gives zero context about any of them. The pipeline review becomes a guessing game.

For teams running Notion as the writing layer alongside HubSpot, the bridge between them is what keeps the qualitative side alive in the pipeline. Reps write detailed call notes in Notion (because Notion is a better writing environment than any CRM), and a sync layer pushes the formatted note onto the matching HubSpot deal timeline. The pipeline stays clean, the notes stay rich, and the manager opening a deal for review sees both.

NoteLinker handles this specific bridge: a Sync to HubSpot checkbox in any Notion row pushes the formatted note onto the matching HubSpot contact or deal timeline, with headings, bullets, and bold text preserved. The two-minute setup guide covers it end to end.

Common sales pipeline template mistakes

Four patterns that consistently make pipeline templates worse rather than better.

Too many stages. Templates with 10 to 14 stages look thorough and update like quicksand. Six stages is the right answer for most B2B teams. The instinct to add stages usually comes from a manager who wants reporting precision the team's data volume cannot actually support.

Too many required fields. Marking fields as required at the CRM level forces reps to fill them in before they can save a deal. This produces two outcomes: reps put garbage data in the required fields to get past the validation, or reps stop creating deal records in the CRM and track them in a spreadsheet instead. Either outcome breaks the pipeline.

No entry criteria for stages. Every rep ends up using stage names slightly differently. The forecast becomes unreliable because "Discovery" means three different things across three reps. Write the entry criteria for each stage in one sentence and revisit it once a quarter.

Treating the template as fixed. A good pipeline template gets revisited every quarter. Stages get renamed as the motion evolves. Probability defaults get adjusted as the team builds a real conversion history. Fields get added (sparingly) or removed (more often) based on what actually informs decisions. A template that has not changed in two years is a template that is no longer matching the motion.

Adapting the template to your motion

The template above is a starting point, not a finished product. Common adjustments worth considering for specific sales motions:

For agencies, add a Retainer Renewal Date field and a Monthly Value field to model recurring engagements. The best CRM for agencies guide covers this in more depth.

For consultants, simplify the stage list to four stages (New, Conversation, Proposal, Closed) since most consulting sales motions are shorter than the six-stage template assumes. The best CRM for consultants guide walks through the consulting-specific adaptations.

For high-velocity SaaS teams running real outbound at volume, add a Pre-Discovery stage between New and Discovery to capture leads that have been contacted but not yet qualified. Beyond that, resist the urge to add more.

The best sales pipeline template is the one your team will actually update. Six stages, nine fields, three views, and a sync layer between your CRM and your writing tool is enough for the vast majority of B2B sales teams. Build it in 20 minutes, ship deals through it next week, and revisit it next quarter when you have real data to tune against.