B2B sales pipeline stages: a practical template you can copy

Published 3 November 2026 · 7 min read

Short answer: A B2B sales pipeline works when every stage is defined by something the buyer has done, not by how the salesperson feels. A simple six-stage template (qualified, requirements received, quote sent, negotiation, commitment, won) with a clear entry rule and a next action for each stage is enough for most small and mid-size teams.

In this guide

What a pipeline stage actually is
A six-stage template you can copy
Define stages by buyer actions, not seller feelings
Goods and services need different pipelines
Track deals, not just companies
Pipeline hygiene: stale deals and lost reasons
How to read a pipeline report
How Melal CRM handles pipeline stages
Common mistakes to avoid
Frequently asked questions

What a pipeline stage actually is

A sales pipeline is the list of open opportunities your team is working on, grouped by how far each one has progressed. A stage is one step on that path. In many companies, though, stages are just labels that every salesperson reads differently: one rep calls a friendly phone call "negotiation", another waits for a written discount request. The report adds both together, and the total means nothing.

A useful stage has three parts: a name, an entry rule that anyone on the team can check, and a typical next action. If you cannot write both, the stage is probably not needed. If you are new to the wider idea of a CRM, our guide What is a CRM? explains where the pipeline fits.

A six-stage template you can copy

This template fits a typical B2B sale where the buyer receives a quote or proforma before ordering. Rename the stages freely, but keep each entry rule tied to an event you could show a manager: an email, a document or a payment.

Stage	Entry rule (observable event)	Typical next action
1. Qualified	The buyer has confirmed a real need, who decides, and a rough timeframe in a call or meeting.	Book a meeting or visit to collect detailed requirements.
2. Requirements received	The buyer has sent specifications, quantities or a scope of work you can price.	Prepare and check the quote internally.
3. Quote sent	A formal quote or proforma has been delivered to the buyer.	Call within a few working days to walk through it and answer questions.
4. Negotiation	The buyer has replied with questions on price, terms or delivery, or asked for changes.	Agree revised terms and confirm who signs off on the buyer side.
5. Commitment	The buyer has issued a purchase order, signed, or paid a deposit.	Hand over to operations and confirm the delivery date.
6. Won	Goods or services have been delivered and the invoice has been paid.	Schedule an after-sales check and the next reorder conversation.

"Lost" is not a stage: a lost deal leaves the pipeline with a reason attached.

Define stages by buyer actions, not seller feelings

Pipeline reports usually fail because stages describe the salesperson's confidence instead of the buyer's behavior. "Hot lead", "very interested" and "almost closed" are feelings. They change with mood, and two people will never agree on them. "Sent specifications", "received proforma" and "issued purchase order" are events. Either they happened or they did not.

When stages follow buyer actions, forecasts become more honest because a late-stage deal needs evidence, coaching gets easier because a manager can ask "what did the buyer do?", and new staff learn the process faster. The only way to move a deal is to get the buyer to take the next step.

Goods and services need different pipelines

A company that sells both products and services often tries to push everything through one pipeline. It rarely fits. A goods sale usually runs through quote, order, shipment, delivery and payment, and the important events are around stock and logistics. A services sale often involves a longer discovery phase, a proposal, a pilot or trial, contract review and then onboarding.

One shared pipeline forces stages vague enough to cover both, and the report stops telling you anything specific. Run two pipelines with their own stages instead; the organization and its contacts stay the same, only the path of the deal differs. Repeat orders from existing buyers can also deserve their own short pipeline, because they skip qualification and move straight to a quote.

Track deals, not just companies

In B2B, one customer organization often has several things going on at once: a repeat order for one product line, a new quote for another, and a service contract under discussion. If your system tracks only the company's overall status, you lose sight of each opportunity. If it tracks deals under each organization, you can see every open opportunity, its stage, its value and its owner, while still keeping all conversations with that company in one place.

It also makes handovers cleaner: the next person sees each deal with its history and next step, not a vague note that the account is "warm". Our guide to the sales follow-up process covers how to write next steps that survive a handover.

Pipeline hygiene: stale deals and lost reasons

Pipelines fill up with deals nobody is working on, which make the total look healthy. Three habits keep it clean.

Agree on a staleness rule. For each stage, decide how long a deal can sit without any recorded activity before it must be reviewed. When a deal crosses that line, the owner either logs a real next step or closes it.
Close lost deals with a reason. Keep the list of reasons short and fixed, for example price, delivery time, chose a competitor, no budget, no response. A short list is easy to count.
Every open deal has a next step with a date. A deal without a scheduled next action is not really open, and finding those is the fastest weekly cleanup a manager can do.

How to read a pipeline report

With clean stages, the report becomes a management tool. Ask these questions regularly:

Where do deals pile up? A crowded "quote sent" stage can point to pricing or slow follow-up.
Where do deals drop out? A sharp drop between two stages shows where to focus.
How long does each stage take? A deal far past the usual time in a stage needs attention.
What do the lost reasons say? A cluster of the same reason is a message about your offer, not just about one salesperson.

Read it by person as well as in total, but use it to start conversations, not to rank people; rankings push reps to move deals forward early.

How Melal CRM handles pipeline stages

In Melal CRM, deals sit under organizations, and one organization can have several open deals at the same time. You can set up more than one sales model, each with your own stages, so a goods pipeline and a services pipeline can run side by side. Stages can also advance automatically on document events: when a proforma is issued or approved, an invoice is issued, goods are shipped or delivered, or the invoice is paid. That links several entry rules in the template above to real documents rather than to someone remembering to update the deal.

Separately from deal stages, each customer has a journey status (Potential, Actual, In follow-up, Satisfied, Dissatisfied, Loyal) that changes mostly automatically from real activity, not by hand. Conversations are logged with a channel, a description and a next follow-up date and time, and reminders ring on the day for items with a set time. Admins see pending approvals and team work on a management desk, and reports include sales and receivables charts. Existing deals can be brought in through Excel import with a preview and an all-or-nothing rule, and the import never deletes data.

Honest limitations: the English and Arabic translation of the interface is in progress, so menus, the top bar with its notification bells and parts of the screens are translated while other screens are still in Persian. Date entry currently uses the Persian (Solar Hijri) calendar. There is no published price list; the Melal team sets up a 14-day trial account on request.

To see it with your own stages, request a demo or browse the features overview.

Common mistakes to avoid

Too many stages. Ten or more stages usually means some of them cannot be told apart. Merge them.
Stages nobody can verify. If the entry rule is not an observable event, the stage will drift.
Skipping the lost reason. Without it, you lose the best feedback your market gives you.
One pipeline for everything. Separate goods, services and repeat orders when their paths really differ.
Changing stages every month. Give a template a full quarter before you redesign it, or you will never have comparable data.

Frequently asked questions

How many stages should a B2B sales pipeline have?

Most small and mid-size B2B teams work well with five to seven stages. Fewer than that hides where deals stall; more than that creates stages nobody can tell apart. Start with six, use them for a full quarter, and merge or split a stage only when your own data shows a real need.

What is the difference between a pipeline stage and a customer status?

A stage describes where one specific deal stands, such as quote sent or negotiation. A customer status describes your relationship with the whole organization, such as potential, actual or loyal. One customer can have several deals in different stages at the same time.

When should a deal be marked as lost?

Mark it lost when the buyer says no, chooses another supplier, or stops responding after the number of follow-up attempts you agreed on in advance. Always record a short reason. Lost reasons are one of the most useful inputs for improving pricing, product range and follow-up.

Can Melal CRM use my own pipeline stages?

Yes. Melal CRM supports several sales models, each with stages you define, and stages can advance automatically when a proforma is issued or approved, an invoice is issued, goods are shipped or delivered, or the invoice is paid.