BuildStackFlow
Menu
How-To Guides

How to Set Up Your First Sales Pipeline

A step-by-step guide to building a sales pipeline that reflects how you actually sell — defining stages, adding deals, and keeping it honest so nothing slips.

By BuildStackFlow · 8 min read · Updated July 28, 2026

A sales pipeline is just a shared, visual answer to one question: where is every potential deal right now, and what needs to happen next? Most small teams run this in their heads or in a spreadsheet that only one person understands. That works until it doesn't — a follow-up gets forgotten, two people email the same lead, and you can't say what this month is likely to close. This guide walks through building your first pipeline from scratch: the stages, the data, and the habits that keep it from turning into a graveyard of stale deals.

Map your sales process before you touch a tool

A pipeline is a picture of how you already sell, not a template you adopt. Before you open any software, write down the real steps a stranger goes through to become a paying customer. For most SMBs that's some version of: a lead shows up, you qualify whether they're a fit, you have a real conversation or send a proposal, and then they say yes or no. Keep it to five or six stages. If you can't describe what has to be true for a deal to move from one stage to the next, the stage probably shouldn't exist.

Define stages as buyer actions, not internal tasks

The most common mistake is naming stages after what you do ('sent email', 'made call') instead of where the buyer is ('qualified', 'proposal sent', 'negotiating'). Stages should describe the buyer's commitment, because that's what tells you how likely a deal is to close. A good default set looks like: New lead, Qualified, Meeting or demo, Proposal sent, Won, and Lost. Adjust the wording to your business, but resist adding a stage for every internal step.

Choose where the pipeline will live

You can start a pipeline in a spreadsheet, and for a dozen active deals that's fine. But the moment you want automatic reminders, email capture, and a view the whole team shares, a dedicated CRM earns its keep. Pipeline-first tools like Pipedrive are built around exactly this drag-a-card-forward view and are hard to beat for lean teams. If you want a free place to start that grows into marketing later, HubSpot has a genuine free tier. Teams that live in their inbox and want the CRM to do the data entry often reach for Close or Salesflare instead.

Build the pipeline, step by step

  • Create your stages in order, using the buyer-action names you defined. Most tools let you rename and reorder stages freely, so get them roughly right and refine later.
  • Add your current open deals first. Don't import your whole contact history on day one — just the live opportunities you're actually working, so the pipeline reflects reality immediately.
  • For each deal, capture the essentials: contact, estimated value, expected close date, and the source it came from. Source is easy to skip and the first thing you'll wish you had when you review what's working.
  • Set a clear owner on every deal. Even solo, this habit pays off the moment you hire; on a team it's what prevents two people chasing the same lead.
  • Add a next step with a date on every open deal. A deal with no scheduled next action is how things quietly go cold.

Automate data entry so the pipeline stays alive

The best pipeline is the one your team will actually update, and the surest way to kill adoption is manual retyping after every call. Connect the sources leads come from — your web forms, your inbox, your calendar — so new deals land in the pipeline without anyone copying them over. Two-way email sync means conversations attach themselves to the right deal automatically. If a connection you need isn't built into your CRM, an automation platform like Zapier can usually bridge it.

Set the rules that keep it honest

A pipeline is only useful if you trust the numbers, and trust comes from a few small agreements everyone follows. Decide when a deal is allowed to enter the pipeline (only once it's qualified), what has to be true to move it forward, and how quickly a dead deal gets marked lost. That last one matters more than it sounds: a pipeline full of deals nobody will admit are dead is worse than no pipeline at all, because it inflates every forecast you make.

Review the pipeline on a schedule

A pipeline you don't review is just a to-do list. Block fifteen minutes once a week to walk every open deal: what moved, what's stuck, and what has no next step. Stalled deals are the signal to look for — a deal sitting in the same stage for weeks usually needs a decision, not another gentle nudge. This weekly pass is also where you'll spot which lead sources are worth more of your time.

Know when to level up

Start simple and add sophistication only when a real problem demands it. You're ready for more — multiple pipelines, deeper automation, tighter reporting — when you're running distinct sales motions that don't fit one set of stages, when handoffs between people get messy, or when you outgrow your current tool's limits. If you reach that point, it's worth weighing a focused pipeline tool against an all-in-one platform; the HubSpot vs Pipedrive comparison is a clean lens for that exact trade-off.

Not sure which CRM fits how your team actually sells? Answer a few questions in build your stack and we'll suggest a pipeline tool — and the tools around it — based on your size and process. When you're torn between two specific options, head to compare and put them head to head.

Frequently asked questions

How many stages should my first sales pipeline have?
Aim for five or six. Enough to see meaningful progress between stages, few enough that everyone remembers what each one means. A common starting set is New lead, Qualified, Meeting, Proposal sent, Won, and Lost. You can always split a stage later if you find deals genuinely stall in the middle of it.
Can I run a pipeline in a spreadsheet instead of a CRM?
Yes, and for a handful of active deals a spreadsheet is a perfectly reasonable start. The trade-offs show up as you grow: no automatic reminders, no email capture, and no easy way for a team to share one live view. Once you're forgetting follow-ups or can't quickly see your pipeline's value, a lightweight CRM pays for itself.
What information should I capture on every deal?
At minimum: the contact, an estimated value, an expected close date, the lead source, and a next step with a date. Source is the one people skip and later regret, because it's what tells you which channels are actually generating revenue. Keep required fields light so the pipeline stays easy to update.
How often should I update and review the pipeline?
Update deals as things happen — ideally the CRM captures most of it automatically from your email and forms. Then do a dedicated review once a week to move deals, mark dead ones lost, and confirm every open deal has a next step. Fifteen minutes weekly is enough for most small teams and keeps your forecast trustworthy.
How do I stop my pipeline from filling with dead deals?
Two habits do most of the work: only let qualified deals enter the pipeline, and mark deals lost promptly instead of letting them linger in hope. A pipeline padded with deals nobody will close inflates every forecast and makes the whole thing less useful. Being honest about losses is what keeps the numbers worth trusting.

Not sure which tools you need?

Answer a few questions and get a recommended stack for your business.

Build your stack