Most small businesses inherit their sales pipeline stages from a template: Lead, Qualified, Proposal, Negotiation, Closed. Those labels come from enterprise software sales, and they describe a salesperson’s opinion more than a customer’s progress. A pressure washing crew in Des Moines does not negotiate for three weeks. It gets a request, looks at the house, sends a price and waits.

This guide shows how to build sales pipeline stages for a small business that match how your jobs actually get won, using an exterior cleaning estimate as the example.

Step 1: Write down how a job gets won today

Before you open any software, pull up your last five won jobs and your last five lost ones. For each, write the sequence of events from first contact to booked date. Use what happened, not what you felt: “customer filled out the form,” “owner called back,” “photos of the house arrived,” “estimate emailed,” “customer replied yes.”

Your real process will have fewer steps than a template, and a few events happen every time. Those repeating events are your stages.

Step 2: Name five to seven stages by observable events

A stage should be a fact someone could verify by looking at a record. “Interested” is a feeling. “Estimate sent” is an event with a date. If two people would disagree about whether a deal is in a stage, the name is wrong.

For an exterior cleaning business, six stages cover the whole sale:

New request. The customer has asked for a quote by form, phone or text.
Contacted. A person has replied and talked to the customer. An automated confirmation does not count.
Scope confirmed. You have photos, measurements or a site visit for the specific job.
Estimate sent. A written price has gone to the customer.
Accepted. The customer has said yes in writing.
Scheduled. A date is on the calendar.

Fewer than five stages hides where deals stall. More than seven means people stop updating them.

Step 3: Define entry and exit criteria

Each stage needs one sentence for how a deal gets in and one for how it gets out. Keep them on one page everyone can see.

Contacted: enter when a person sends the first reply; exit when the customer has described the job.
Scope confirmed: enter when you hold photos or have visited; exit when you can price it without guessing.
Estimate sent: enter when the estimate leaves your outbox; exit when the customer accepts or declines in writing.

The exit criterion is what prevents a deal from sitting in a stage forever. If you cannot say how a deal leaves “Estimate sent,” you do not yet have a stage, only a pile.

Step 4: Set one next action per deal

Every open deal carries exactly one next action with an owner and a date: “Owner texts photos request, Thursday,” or “Follow up on estimate, Monday.” No date means no next action, and a deal with no next action is a deal nobody is working.

This rule matters more than the stage names. It is also the gap the earlier article “Your CRM Is Not a Contact List” addresses. That article explains why a CRM must track what happens next, not only who the customer is. This how-to builds the structure for it.

Step 5: Define your lost reasons

When a deal dies, record why, from a short fixed list. Free text becomes unsearchable within a month. A usable list for an exterior cleaning business:

Price
Timing (customer wants a date you cannot meet)
Chose another company
No response
Outside service area
Not a fit for the work

After a quarter, the counts tell you where to act. A lot of “no response” points to your follow-up or first-reply speed. A lot of “price” after the estimate suggests a scoping or pricing conversation to have earlier.

Step 6: Review weekly and prune

Set a recurring 20-minute review, same day each week. Walk the pipeline from the last stage backward, because deals closest to a booked job come first. For each deal ask one question: is the next action still right?

Then prune. A reasonable rule is that any deal with no customer response after 14 days of follow-up gets marked lost with the reason “No response.” A cluttered pipeline overstates your work in progress and hides the deals that need you. The customer can re-enter at New request later.

Choosing a tool

A spreadsheet with a stage column, a next-action column and a date column is enough to start. When volume outgrows it, a CRM keeps the stages, dates and notes together. More guides like this one are in our how-to library.

Frequently asked questions

How many stages should a small business sales pipeline have?

Between five and seven. Fewer stages hide where deals stall, and more stages go stale because no one updates them. Count the repeatable events in your last ten jobs.

What is the difference between a stage and a next action?

A stage describes where a deal stands, such as “Estimate sent.” A next action is the specific thing someone will do next, with a date. The stage tells you where the deal is, and the next action tells you whether anyone is moving it.

How often should I clean up my pipeline?

Review it weekly and prune on the same schedule. Mark deals with no response after your follow-up window as lost, with a reason, so your counts stay honest.

This article was written by SPARK, the CRM and marketing automation platform from Intelligent Analytics and Data Management.