How to Build a Sales Pipeline in Your CRM: Essential Stages for Service Businesses

Many service businesses have customers, messages, and estimates.

But they do not have a clear sales process.

New inquiries arrive through text messages, WhatsApp, forms, phone calls, and email.

Some customers receive a fast response.

Others wait.

A proposal is sent.

Then nobody knows whether the customer reviewed it.

A service is approved, but it takes too long to reach the schedule.

A customer decides not to move forward, but the reason is never recorded.

At the end of the month, the owner tries to understand:

• How many leads came in?
• How many received proposals?
• How many received follow-up?
• How many approved?
• How many became Jobs?
• How many were lost?

The answers are scattered across conversations, spreadsheets, calendars, and personal memory.

A sales pipeline turns this confusion into a visual process.

With a CRM Pipeline, every lead belongs to a clear stage.

Your team can look at the board and understand:

• who just contacted the business;
• who still needs a reply;
• who needs to provide information;
• who received a proposal;
• who needs follow-up;
• who approved the work;
• who needs to be scheduled;
• who has already been served;
• who was lost.

The goal of a pipeline is not to make sales more complicated.

It is to make the next step visible.

What is a sales pipeline?

A sales pipeline is a visual representation of the stages an opportunity moves through.

It begins when a potential customer shows interest and ends when the opportunity is completed, approved, or lost.

A simple service-business pipeline may include:

1. New Lead;
2. Contacted;
3. Information Needed;
4. Proposal Sent;
5. Follow-Up;
6. Approved;
7. Job Scheduled;
8. Completed;
9. Lost.

Each lead appears as a card inside one stage.

When the situation changes, the card moves.

Example:

New Lead → Contacted → Proposal Sent → Approved → Job Scheduled

That movement shows the progress of the opportunity.

What is the difference between a pipeline and a sales funnel?

The concepts are related, but they are not exactly the same.

A sales funnel represents the reduction in the number of opportunities as they move toward a purchase.

Many contacts enter.

A smaller group receives proposals.

An even smaller group approves.

The pipeline shows where each individual opportunity is and what action needs to happen next.

In practical terms:

• the funnel helps analyze volume and conversion;
• the pipeline helps the team manage daily sales activity.

For small service businesses, the pipeline is often more useful in daily operations.

Why do service businesses need a sales pipeline?

Service businesses rarely complete a sale in one instant.

The customer usually goes through several steps.

They may:

• request information;
• send photos;
• provide an address;
• request a site visit;
• receive an estimate;
• review the scope;
• ask questions;
• approve;
• schedule;
• receive the service;
• pay;
• leave a review.

Without a pipeline, all of that becomes a series of disconnected messages.

With a pipeline, the business can see the customer journey.

This is useful for businesses such as:

• cleaning companies;
• electricians;
• HVAC contractors;
• landscapers;
• painters;
• maintenance teams;
• repair companies;
• beauty businesses;
• clinics;
• consultants;
• remodelers;
• residential service companies;
• commercial service providers.

The problem with using only text messages

Text messaging is great for communication.

But it is not enough to organize the sales process.

Inside a regular message list, your business cannot clearly see:

• which conversations are new leads;
• who received a proposal;
• who needs follow-up;
• who approved;
• who needs to be scheduled;
• who was lost;
• who has been waiting for several days.

The newest conversation moves to the top.

An important opportunity can move down the list and be forgotten.

SMS, WhatsApp, and email should continue to be used as communication channels.

The CRM should organize the sales process behind those conversations.

The problem with using a spreadsheet as a pipeline

Spreadsheets can help in the beginning.

But they require constant manual updates.

If the team stops updating the file, it no longer reflects reality.

Other problems include:

• duplicate contacts;
• forgotten rows;
• difficulty visualizing stages;
• limited customer history;
• no connection to messages;
• unclear ownership;
• difficulty turning an approval into a scheduled Job.

A Kanban pipeline is more visual.

The lead card moves as the customer advances.

How many stages should a pipeline have?

There is no single correct number.

But a common mistake is creating too many stages.

A pipeline with 20 or 30 columns may look detailed, but it becomes difficult to maintain.

For most small service businesses, six to ten main stages are usually enough.

Each stage should represent a real change in the customer process.

Do not create a new column for every small task.

Complicated example:

• New;
• New Reviewed;
• First Contact;
• First Contact Completed;
• Waiting for First Reply;
• Replied;
• Partially Replied;
• Waiting for Details;
• Waiting for Photos;
• Waiting for Address.

This pipeline will probably be abandoned.

A simpler model:

• New Lead;
• Contacted;
• Information Needed;
• Proposal Sent;
• Follow-Up;
• Approved;
• Scheduled;
• Completed;
• Lost.

Stage 1: New Lead

This stage receives all new inquiries.

They may come from:

• SMS;
• WhatsApp;
• phone calls;
• public forms;
• website;
• referrals;
• Instagram;
• Google;
• ads;
• email;
• online booking.

A lead should stay in this stage for as little time as possible.

The expected actions are:

• read the request;
• verify the information;
• assign an owner;
• set the priority;
• respond;
• move the lead to the next stage.

A new lead without a reply is an opportunity at risk.

Stage 2: Contacted

The lead has received an initial response and the conversation has started.

The team is now trying to understand:

• which service is needed;
• where the service will happen;
• the expected timeline;
• which information is missing;
• whether the business serves the area;
• whether a site visit is needed;
• whether the request is urgent.

The objective is qualification.

From here, the lead may move to:

• Information Needed;
• Proposal Sent;
• Site Visit Scheduled;
• Lost.

Stage 3: Information Needed

Use this stage when the business is waiting for information from the customer.

Examples:

• address;
• photos;
• measurements;
• documents;
• quantity;
• equipment model;
• preferred date;
• service details.

Possible message:

Hi {{lead.name}}, we still need the service address and a few photos before we can prepare the proposal. You can send them here when available.

This stage prevents incomplete leads from disappearing.

The team knows exactly who needs another reminder.

Optional stage: Site Visit Scheduled

Some businesses need an in-person assessment before preparing a proposal.

In that case, separate stages may help:

• Site Visit Scheduled;
• Site Visit Completed.

This can be useful for:

• remodeling;
• electrical work;
• HVAC;
• landscaping;
• painting;
• technical services;
• customized projects.

Not every business needs these stages.

If most estimates can be prepared from photos, measurements, or remote information, a separate site-visit stage may be unnecessary.

Stage 4: Proposal Sent

The proposal has been prepared and delivered.

This is a critical stage.

Many businesses act as though the sales work ends here.

But the customer still needs to:

• open the proposal;
• understand it;
• compare it;
• ask questions;
• approve it;
• choose a date.

The team should record:

• date sent;
• value;
• scope;
• channel;
• expected follow-up date;
• next action.

DunaHub Visual Proposals help organize line items, pricing, status, and approval.

Stage 5: Follow-Up

The customer received the proposal but has not made a decision.

This stage includes opportunities that need another contact.

A lead should not enter this stage without a defined next step.

Decide:

• when to contact the customer;
• which channel to use;
• which message to send;
• how many attempts to make;
• when to close the opportunity.

Example:

Hi {{lead.name}}, I wanted to check whether you had a chance to review the proposal. I’m happy to answer any questions.

With Stage Automations, businesses on eligible plans can reduce forgotten follow-up.

Stage 6: Approved

The customer accepted the proposal.

Now the company needs to turn the sale into service delivery.

Expected actions:

• confirm the scope;
• verify the address;
• choose the date;
• assign a technician or crew;
• record the value;
• create the Job;
• send confirmation.

Do not leave an approved customer sitting in this stage for several days.

The customer already bought.

Now they expect organization.

Stage 7: Job Scheduled

The service has been added to the schedule.

DunaHub Job Scheduling can organize:

• date;
• time;
• address;
• service;
• value;
• assigned technician;
• status.

At this point, the focus shifts from sales to operations.

Communication may include:

• appointment confirmation;
• preparation instructions;
• rescheduling;
• technician on-the-way updates;
• status updates;
• post-service guidance.

Stage 8: Completed

The service is finished.

But the customer process may still include important actions:

• create the invoice;
• confirm payment;
• record notes;
• share the Customer Portal;
• request a review;
• schedule maintenance;
• plan a future return.

Online Invoices and Google Review Requests can be connected to this stage.

Completed does not mean forgotten.

It means the post-service process begins.

Stage 9: Lost

Not every opportunity will close.

That is normal.

The important part is recording the result.

Possible lost reasons:

• price;
• no response;
• competitor selected;
• outside service area;
• service not offered;
• no availability;
• project canceled;
• incompatible timeline;
• customer postponed;
• invalid contact details.

The lost lead can remain in the history and may even be reactivated later.

But it should not stay indefinitely in an active sales stage.

Do you really need a Lost stage?

Yes.

Without it, the pipeline becomes full of opportunities that no longer exist.

That makes the board misleading.

It also prevents the business from learning.

When lost reasons are recorded, patterns may appear.

Examples:

• too many opportunities lost because of slow response;
• too many outside the service area;
• too many lost on price;
• too many lost because of scheduling.

These patterns help improve the business.

How should you name pipeline stages?

Use names the team understands immediately.

Avoid overly technical language.

Good options:

• New Lead;
• Contacted;
• Information Needed;
• Proposal Sent;
• Follow-Up;
• Approved;
• Scheduled;
• Completed;
• Lost.

A clinic or consulting firm may use different names:

• New Inquiry;
• Consultation Scheduled;
• Consultation Completed;
• Proposal;
• Decision;
• Scheduled;
• Completed.

The pipeline should reflect the real customer process.

How to customize the pipeline for your business

Start by mapping your process on paper.

Ask:

1. How does the lead enter?
2. What is the first action?
3. Which information is needed?
4. Is a site visit required?
5. When is the proposal sent?
6. How does follow-up happen?
7. What happens after approval?
8. How is the service scheduled?
9. When is the opportunity considered completed?
10. How are losses recorded?

The answers become your pipeline stages.

Pipeline example for a cleaning company

A simple model:

• New Lead;
• Property Information;
• Proposal Sent;
• Follow-Up;
• Approved;
• Cleaning Scheduled;
• Completed;
• Recurring Service;
• Lost.

The Recurring Service stage may be useful for weekly, biweekly, or monthly customers.

Pipeline example for an electrical contractor

Possible model:

• New Service Request;
• Initial Review;
• Site Visit Needed;
• Site Visit Completed;
• Proposal Sent;
• Approved;
• Job Scheduled;
• Completed;
• Lost.

Electrical hazards and emergencies still require proper technical and safety procedures.

The CRM organizes the commercial workflow, but it does not replace professional judgment.

Pipeline example for an HVAC company

• New Lead;
• Initial Diagnosis;
• Site Visit Scheduled;
• Proposal Sent;
• Follow-Up;
• Approved;
• Installation or Maintenance Scheduled;
• Completed;
• Future Maintenance;
• Lost.

The Future Maintenance stage can help create repeat business.

Pipeline example for landscaping

• New Project;
• Information and Photos;
• Site Visit;
• Proposal;
• Changes Requested;
• Approved;
• Work Scheduled;
• In Progress;
• Completed;
• Maintenance;
• Lost.

Larger projects may benefit from a Changes Requested stage.

Pipeline example for a consulting business

• New Inquiry;
• Qualified;
• Discovery Call Scheduled;
• Diagnosis;
• Proposal Sent;
• Negotiation;
• Approved;
• Active Project;
• Completed;
• Renewal;
• Lost.

Pipeline example for a repair company

• New Service Request;
• Equipment Information;
• Evaluation;
• Estimate;
• Approved;
• Repair Scheduled;
• In Repair;
• Ready;
• Delivered;
• Lost.

How do you know whether a stage should exist?

Ask three questions:

1. Does this stage represent a real change?
2. Is there a different action in this stage?
3. Does the team need to see it separately?

If the answer is no, the stage may not be necessary.

For example:

Proposal Sent Yesterday and Proposal Sent Three Days Ago do not need to be separate stages.

The date and follow-up process can handle that difference.

How to use colors

Colors make the pipeline easier to scan.

A simple approach:

• blue for entry and contact;
• yellow for missing information;
• purple for proposals;
• orange for follow-up;
• green for approval and completion;
• red for lost.

Do not use too many colors without a clear system.

The team should understand the meaning immediately.

How to assign lead owners

Every lead needs an owner.

Even when several people can access the customer record, one person should be responsible for the next action.

The owner may be:

• salesperson;
• customer service representative;
• manager;
• business owner;
• technician;
• administrator.

An unassigned lead is more likely to be forgotten.

How to use lead scoring with the pipeline

Stage and score are different pieces of information.

The stage shows where the lead is.

The score shows the priority.

In DunaHub, leads can be classified as:

• Hot;
• Warm;
• Cold.

Example:

Two leads are in Proposal Sent.

The first is Hot because the customer wants to start this week.

The second is Warm because the customer is planning for next month.

Same stage.

Different urgency.

How to use filters

Filters turn the pipeline into a practical action list.

Your team can filter by:

• stage;
• score;
• owner;
• date.

Examples:

• show only Hot leads;
• show proposals sent;
• show leads owned by one salesperson;
• show older opportunities;
• show today’s new inquiries.

Filters become especially useful as lead volume increases.

How long should a lead stay in each stage?

Create internal expectations.

Example:

Stage	Suggested time
New Lead	A few hours
Contacted	Up to one business day
Information Needed	Follow up in 1–2 days
Proposal Sent	First follow-up in 2–3 days
Follow-Up	Based on your defined sequence
Approved	Schedule quickly
Scheduled	Until service date
Completed	Invoice and post-service actions

These timelines depend on the business.

But having an internal standard helps identify stalled leads.

What is a stalled lead?

A stalled lead remains in the same stage without action or a defined next step.

Examples:

• new lead without a reply;
• customer waiting for a proposal;
• proposal sent with no follow-up;
• approved customer not scheduled;
• completed Job without an invoice.

A stalled lead shows a bottleneck.

The pipeline makes it visible.

How to review the pipeline every day

A simple routine:

Morning

• review new leads;
• respond to Hot opportunities;
• check today’s Jobs;
• identify proposals without follow-up;
• assign owners.

During the day

• move cards;
• record customer information;
• send proposals;
• update lead scores;
• create approved Jobs.

End of the day

• check unanswered leads;
• review missing information;
• prepare follow-ups;
• record losses;
• organize tomorrow’s actions.

An updated pipeline does not require hours.

It requires consistency.

How to review the pipeline weekly

A short weekly review can cover:

• new leads;
• proposals sent;
• approvals;
• lost opportunities;
• Jobs created;
• stalled leads;
• lost reasons;
• first response time.

The team can also ask:

• Which stage is overloaded?
• Which leads need a decision?
• Who is unassigned?
• Which proposals need follow-up?
• Which past customers could be reactivated?

How Public Forms connect to the pipeline

DunaHub Public Forms can create leads automatically.

The contact enters New Lead.

Then the team:

1. reviews the submission;
2. scores the lead;
3. responds;
4. moves the card to the correct stage.

This prevents form submissions from becoming forgotten emails.

How the Auto Website connects to the pipeline

The DunaHub Auto Website includes a lead form connected to the CRM.

When a visitor submits a request, it enters the pipeline.

The website captures.

The pipeline organizes.

How the Unified Inbox connects to the pipeline

The Unified Inbox keeps customer conversations attached to the lead.

The team can see:

• what the customer said;
• the current stage;
• whether a proposal was sent;
• whether a Job exists;
• whether an invoice exists.

The inbox shows the conversation.

The pipeline shows the process.

How proposals connect to the pipeline

When the team sends a proposal, move the lead to Proposal Sent.

Then:

• monitor the customer response;
• define the next contact;
• record objections;
• move the lead to Approved or Lost.

The stage should reflect reality.

How automations connect to the pipeline

On eligible plans, a stage change can trigger a message.

Examples:

• New Lead: confirmation;
• Information Needed: reminder;
• Proposal Sent: follow-up;
• Approved: booking link;
• Past Customer: reactivation.

Automation depends on well-organized stages.

A confusing pipeline creates inappropriate messages.

How Jobs connect to the pipeline

When the customer approves, create the Job.

Do not leave service delivery inside a message thread.

The Job should contain the operational details.

The lead may move to Scheduled.

As the work progresses, Job status can move through:

• Scheduled;
• On the way;
• In progress;
• Completed.

How invoices connect to the pipeline

After completion, create the operational invoice.

The workflow becomes:

Lead → Proposal → Approved → Job → Completed → Invoice

DunaHub invoices do not replace accounting, bookkeeping, tax documents, or professional financial systems.

How review requests connect to the pipeline

After a Job is completed, the Google Review Engine can request feedback.

The sales process may be complete, but the customer relationship continues.

Reviews help build reputation and support future lead generation.

How to stop the pipeline from becoming an abandoned list

Use a few simple practices:

• keep the number of stages low;
• assign every lead;
• update cards daily;
• record the next step;
• close unrealistic opportunities;
• use filters;
• hold a short weekly review;
• create rules for each stage;
• organize before automating;
• train the whole team.

Software without routine does not create organization.

What should be recorded inside each lead?

Useful information includes:

• name;
• phone;
• email;
• service requested;
• address;
• lead source;
• score;
• stage;
• owner;
• last interaction;
• next step;
• proposal;
• Job;
• invoice;
• notes;
• lost reason.

Do not collect unnecessary or sensitive information without a real business need.

How to create rules for each stage

Write a short internal definition.

Example:

New Lead

Enters when: a new contact arrives. Leaves when: the first reply is sent. Owner: customer service. Expected time: same business day.

Information Needed

Enters when: details are missing. Leaves when: the customer provides the information or the opportunity is closed. Action: request and follow up.

Proposal Sent

Enters when: the proposal link is delivered. Leaves when: the customer approves, declines, or moves into follow-up. Action: monitor and contact again.

This document can be simple.

But it helps every team member use the stages the same way.

Which pipeline metrics should you track?

Useful metrics include:

New leads

How many contacts entered?

Proposals sent

How many opportunities reached the offer stage?

Approval rate

How many proposals were accepted?

First response time

How quickly does the team reply?

Time in each stage

Where are leads getting stuck?

Jobs created

How many sales became scheduled work?

Lost reasons

Why did opportunities fail to close?

Pipeline value

What is the potential value of active proposals?

You do not need dozens of reports.

Start with metrics that help you make decisions.

How to improve pipeline conversion

Respond quickly

New leads lose interest.

Ask only for necessary information

Avoid unnecessary friction.

Send clear proposals

Make the offer easy to understand.

Define follow-up

Do not wait forever.

Update lead priority

Contact Hot leads first.

Make approval and scheduling easy

Reduce the number of steps.

Record objections

Learn why customers hesitate.

Review lost opportunities

Look for patterns.

Train the team

Everyone should use the same process.

How much does DunaHub’s CRM Pipeline cost?

DunaHub uses flat company pricing.

Plan	Monthly price	Leads	Users
Free	$0	Up to 50 total	3
Starter	$9.90/month	Unlimited	5
Pro	$49/month	Unlimited	Unlimited

The visual CRM Pipeline is available across the plans, with additional capacity and features depending on the selected plan.

Which plan should you choose?

Free

May be enough for:

• owner-operators;
• small businesses;
• up to 50 leads;
• initial organization;
• three users;
• basic pipeline management.

Starter

May be a fit for:

• small teams;
• unlimited leads;
• five users;
• basic automations;
• higher sales volume.

Pro

May be a fit for:

• growing companies;
• unlimited users;
• multi-step automations;
• more complex processes;
• larger sales and service operations.

Common pipeline mistakes

Creating too many stages

The team stops updating them.

Using confusing names

Each person interprets them differently.

Not assigning owners

Leads receive no action.

Mixing sales and operations without rules

Approved opportunities do not become Jobs correctly.

Never marking leads Lost

The pipeline becomes inflated.

Not recording the next step

The card exists, but nobody knows what to do.

Skipping follow-up

Proposals remain stalled.

Automating before organizing

Messages go out at the wrong time.

Maintaining a duplicate spreadsheet

The business creates two versions of the truth.

Never reviewing the pipeline

Problems stay hidden.

Sales pipeline checklist

• Map the current sales process;
• Identify every lead source;
• Define the main stages;
• Use clear names;
• Remove unnecessary columns;
• Assign stage responsibilities;
• Set expected timing;
• Define entry and exit rules;
• Configure colors;
• Define Hot, Warm, and Cold scoring;
• Create lost reasons;
• Connect Public Forms;
• Connect the Auto Website;
• Connect the Unified Inbox;
• Create proposals through the CRM;
• Turn approvals into Jobs;
• Create invoices after completion;
• Configure follow-up;
• Train the team;
• Review daily;
• Analyze weekly;
• Simplify when necessary.

Recommended pipeline model

For a small service business:

Stage	Objective
New Lead	Receive and respond
Contacted	Understand the request
Information Needed	Collect missing details
Proposal Sent	Present the offer
Follow-Up	Support the decision
Approved	Confirm the sale
Scheduled	Organize service delivery
Completed	Finish, invoice, and follow up
Lost	Close and record the reason

This model can be customized.

The best pipeline is the one your team actually uses.

Summary: every lead needs a stage and a next step

A sales pipeline should not be complicated.

It needs to answer three questions:

1. Where is the lead?
2. Who is responsible?
3. What is the next step?

When those answers are clear, the business reduces forgotten opportunities.

The process becomes:

Lead enters → Team responds → Information is collected → Proposal is sent → Follow-up happens → Customer approves → Job is scheduled → Service is completed → Invoice and post-service actions happen

With DunaHub, the pipeline can work together with:

• Unified Inbox;
• Public Forms;
• Auto Website;
• Visual Proposals;
• Stage Automations;
• Job Scheduling;
• Invoices;
• Customer Portal;
• Google Reviews.

The CRM stops being just a contact database.

It becomes the path every opportunity follows.

Frequently Asked Questions

What is a sales pipeline?

A sales pipeline is a visual representation of the stages a lead moves through before becoming a customer or being marked Lost.

Are pipeline and funnel the same?

Not exactly. The funnel shows the reduction in opportunities. The pipeline shows where each lead is and what action needs to happen.

How many stages should a pipeline have?

It depends on the business, but six to ten main stages are usually enough for a small service company.

Which stages should I use?

A simple model is New Lead, Contacted, Information Needed, Proposal Sent, Follow-Up, Approved, Scheduled, Completed, and Lost.

Can I customize stages in DunaHub?

Yes. DunaHub pipeline stages are customizable.

Can I change the stage order?

Yes. Stages can be arranged to match the business process.

Is the pipeline Kanban-based?

Yes. DunaHub uses a visual Kanban pipeline.

Can I drag leads between stages?

Yes. Lead cards can be moved across the pipeline.

Is the pipeline included on Free?

Yes. The CRM Pipeline is available on Free.

How many leads does Free allow?

Up to 50 total leads.

Can I score leads as Hot, Warm, and Cold?

Yes. DunaHub includes lead scoring.

Are stage and score the same?

No. The stage shows the process position. The score shows priority.

Can I filter leads?

Yes. Filters can be used for stage, score, owner, and date.

Do I need a Lost stage?

Yes. It keeps the pipeline accurate and helps record why opportunities did not close.

When should a lead move to Proposal Sent?

After the proposal has actually been delivered.

When should a lead move to Approved?

When the customer confirms acceptance.

What happens after approval?

Create the Job and organize the schedule.

Can I automate follow-up?

Yes, on eligible plans.

Does the pipeline replace text messaging?

No. Messaging is a communication channel. The pipeline organizes the sales process.

Does the pipeline replace scheduling?

No. It works together with Job Scheduling.

Does a pipeline guarantee more sales?

No. It improves organization and follow-up, but the team remains responsible for customer service, proposals, and delivery.

Which businesses should use a CRM Pipeline?

Cleaning companies, HVAC contractors, electricians, plumbers, landscapers, pressure washing companies, gutter businesses, painters, maintenance teams, repair companies, consultants, and other service businesses.

Turn scattered customer inquiries into a clear sales process

Your team should know where every customer is and what action needs to happen next.

Create your free DunaHub account, customize your sales pipeline, and manage every lead from first contact to completed Job.