How to Build a Sales Pipeline From Scratch

What is a sales pipeline?

A sales pipeline is a visual representation of every active deal in your business and exactly where each one is in the sales process — from first inquiry to closed-won. Built right, it shows you in 30 seconds which deals are moving, which are stuck, and where in the process you're losing the most. Built wrong, it's a database your team avoids opening.

The point of building a pipeline isn't reporting; it's discipline. A pipeline forces every deal to have a stage, an owner, and a next step. Deals without those three drop out, which is exactly what should happen.

This guide walks through building a 5-stage pipeline from scratch in about an afternoon. For broader context on lead management, see the lead management guide.

The 5 standard pipeline stages (with criteria)

Most small-business pipelines work cleanly with five stages. The names can change to fit your industry, but the underlying structure stays the same.

Service businesses often add a "Scheduled" stage between Quoted and Closed (for trades that book the job before payment). E-commerce-ish businesses might collapse Quoted and Negotiation into one. Tune to your sales cycle.

Stage 1 — New / Inquiry

Every lead lands here. Source-tagged, owned by automation initially, and either advanced (after the first conversation) or dropped (after 5 contact attempts with no response).

Entry: lead form fill, inbound call, referral logged.

Exit: confirmed live conversation OR documented 5-attempt outreach.

The mistake to avoid: leaving leads in this stage forever. After 5 attempts with no response, mark them lost (with reason "no response"). Don't let them clog the pipeline.

Stage 2 — Qualified

You've confirmed three things: the prospect has a real need, has a budget that fits your service, and has a realistic timeline. Without those, no quote should be issued.

Entry: confirmed need + budget + timeline.

Exit: quote/proposal in progress.

The mistake to avoid: skipping qualification because "they seem interested." Reps who skip this stage spend hours quoting people who were never going to buy.

Stage 3 — Quoted / Proposal

The quote or proposal is in the prospect's hands. The next move belongs to them, not you — but that doesn't mean you sit idle.

Entry: quote sent.

Exit: prospect responds (yes, no, negotiate) OR the deal is marked stalled after 14 days of no response.

The mistake to avoid: letting quotes sit unanswered without follow-up. A quote with no follow-up is a lost sale waiting to happen. Auto-trigger a 3-touch follow-up sequence on day 1, 3, 7 after the quote goes out.

Tip: Need to send a one-off quote or invoice fast? Use our free Invoice Generator — it produces a print-ready PDF in 60 seconds. Once your pipeline lives in a CRM, you'll automate this end-to-end with Easyly Payments & Invoicing.

Stage 4 — Negotiation

The prospect is engaged but pushing on price, scope, or timing. This stage often takes the longest in B2B; in B2C service it's often hours, not days.

Entry: prospect actively negotiating.

Exit: signed agreement OR explicit walk-away.

The mistake to avoid: discounting too easily. The first counter-offer should rarely be the discount — it should be a scope change. "We can hit that price by removing X."

Stage 5 — Closed

Won (signed and paid) or lost (with a documented reason). Don't conflate "Won" with "completed work" — those are operational stages, not pipeline stages.

Entry: signed agreement / payment initiated.

Exit: deal removed from active pipeline.

The mistake to avoid: not requiring a "lost reason" on close-lost. Without it, you can't see patterns. Make it a required dropdown: too expensive, lost to competitor, no budget, timing, no response, other.

Picking stage names that fit your business

The 5-stage template uses generic names. Most teams customize them. Three patterns:

Service business pattern:

1. New Inquiry
2. Qualified
3. Estimate Sent
4. Booked
5. Completed (or Won)

B2B SaaS pattern:

1. Lead
2. Qualified Lead
3. Discovery Done
4. Proposal Sent
5. Negotiation
6. Closed

Real estate pattern:

1. New Lead
2. Showing Scheduled
3. Showing Done
4. Offer
5. Under Contract
6. Closed

The rule: name each stage after a state, not an action. "Quoted" is a state (the quote has been sent and is awaiting response). "Send Quote" is an action (which doesn't belong on a stage label).

What to track on every deal card

Each card in the pipeline needs the same fields. Five at minimum:

1. Deal name. What is this deal about? Not "John Smith" — that's a contact. "Smith — 4 BR Boston-Austin move."
2. Value ($). Even rough. Without a value, you can't forecast or prioritize.
3. Probability (%). Either by stage default or rep estimate. Used for weighted forecast.
4. Expected close date. A real date, not "soon." Used to flag stalled deals.
5. Next step. One concrete next action with a date. The single most-skipped field, and the single most-important one for keeping deals moving.

Bonus fields that pay off: source (lead source, for marketing attribution), lost reason (when applicable), product/service tags (for segmentation reporting).

The "no zombies" rule

The most-broken pipelines have a zombie problem: deals that haven't moved in months, sitting in stages with no owner-next-action, slowly becoming a graveyard.

The fix is mechanical:

• Any deal with no activity in 14 days → flag.
• Any deal with no next-step set → flag.
• Any deal past its expected close date → flag.
• Flagged deals must be reviewed weekly: advance, push out, or close-lost.

A clean 30-deal pipeline beats a messy 200-deal pipeline. Most "200-deal pipelines" actually have 30 real deals and 170 zombies.

How to automate the boring parts

Once the pipeline is built, automation removes most of the manual work. Five high-leverage automations every CRM should support:

1. New lead → automatic stage 1 + first email. Inbound form creates a card in "New," sends the first follow-up email, assigns to a rep.
2. Stage change → notification. When a deal moves to "Quoted," the rep gets a reminder to schedule the follow-up. When it moves to "Closed-Won," the operations team gets a Slack message.
3. Inactivity → flag. Deals not updated in 14 days surface in a daily digest.
4. Quote sent → follow-up sequence. Automatic 3-touch follow-up on days 1, 3, 7 after a quote.
5. Closed-Won → next-customer playbook. Welcome email, onboarding task, NPS request scheduled for day 30.

For deeper automation patterns, see How to automate sales follow-up.

How to read your pipeline

Three views, each useful for a different question.

Kanban (board view)

The default. One column per stage, deal cards in each. Best for "what's in progress?" Your team should live in this view.

List view

All deals in a sortable table. Best for filtering ("show me all deals worth >$5K assigned to Sarah"). Used by managers more than reps.

Forecast view

Weighted by probability and grouped by close date. Best for "how much will close this month?" Used for revenue projections.

A small-business CRM should support all three from the same data. If yours can't, that's a sign of a thin product.

Pipeline metrics that matter

Track these weekly. Don't track more.

A pipeline review every Monday morning takes 15 minutes once you're in rhythm: which deals advanced, which stalled, what's the action this week.

Common pipeline mistakes

Too many stages. 12 stages = nobody updates anything. 5 stages = clear visibility. Cut ruthlessly.

Stages that aren't states. "Send Proposal" is a task, not a stage. "Proposal Sent" is a state.

No probability or close date. Without these, you can't forecast or prioritize.

Deals stuck in "Negotiation" for months. That's not negotiation; that's stalling. After 30 days, push to close or close-lost.

Zombie deals from 6 months ago. Clean them out. They make every metric look worse than it is.

No "lost reason" required. You can't fix what you can't see.

Custom fields nobody fills out. If a field isn't required and isn't used, kill it. CRMs get cluttered fast; ruthless field hygiene keeps them usable.

Building a pipeline in a CRM: step-by-step

Time required: about 2 hours for the initial setup, plus a week of usage to refine.

1. Hour 1 — Stage definitions. Decide on your 5 stage names. Write down entry/exit criteria for each. Don't over-think; this is iterative.
2. Hour 1.5 — Required fields. Set: deal name, value, probability, expected close, next step, source, owner. Make probability default per stage.
3. Hour 2 — Build automations. New lead → stage 1. Stage move → notifications. 14-day inactivity → flag.
4. Day 1 — Live with it. Add 5 real deals. See what's awkward.
5. Week 1 — Adjust. What stage names felt wrong? What fields were over- or under-used? Refine.
6. Day 30 — Audit. Are the stages actually distinct? Are deals moving? Adjust again.

By day 30, the pipeline should be self-sustaining: reps update it because it makes their job easier, not because they're told to.

The bottom line

A sales pipeline is the operating system of your sales team. Build it with 5 stages, clear entry/exit criteria, required fields, and a "no zombies" rule, and it will pay for itself in three months by surfacing deals that would otherwise have gone quietly cold.

The mistake isn't picking the wrong template. It's not having a pipeline at all — or having one nobody opens. Build it. Use it daily. Adjust it monthly. The discipline is the whole game.

Want a CRM that comes with all of this built in? Try Easyly free for 14 days — kanban pipeline, custom stages, automations, and weekly metric digests in one workspace.