A Simple CRM Pipeline for a Home Service Business
A plain-language pipeline for tracking an inquiry from first contact through estimate, scheduled work, completion, and follow-up.
Build stages around customer commitments
A pipeline is a shared view of where an opportunity stands. It should describe meaningful changes in the relationship, not every internal activity. New inquiry, contacted, visit or estimate scheduled, estimate sent, decision pending, won, and closed are often enough to start.
Stage names should answer the same question for everyone. If contacted means one person left a voicemail and another completed a discovery call, the stage is too vague. Write a short entry condition and exit condition for each stage so reporting and follow-up rules have a stable meaning.
- New: captured but not yet reviewed
- Contacting: an owner is actively trying to reach the customer
- Qualified: service, location, timing, and fit are understood
- Estimate or visit scheduled: a date and responsibility are confirmed
- Decision pending: the customer has what they need to decide
- Won, lost, or not a fit: the open loop is closed with a reason
Separate status from the next action
A stage shows the broad position, but it does not tell a team member what to do today. Every open lead should also have a next action, due date, and owner. This prevents a clean-looking pipeline from hiding opportunities that have stopped moving.
The next action can be simple: call, send estimate, confirm access, request photos, or follow up after a stated decision date. If no action is appropriate, document why and when the lead should be reviewed again.
Capture only data that changes a decision
Start with fields the team will actually use: contact details, service location, requested service, urgency, source, preferred contact method, assigned owner, and notes. Add trade-specific details when they affect routing or preparation.
Do not turn the CRM into a second estimate form or a warehouse for every possible fact. Long forms increase incomplete records and inconsistent shortcuts. Keep operational documents in their proper system and link them to the CRM when needed.
- Required for routing
- Required for customer communication
- Required for service eligibility
- Required for reporting the owner already uses
- Required for consent or compliance records
Use automation to support ownership
Automation can create records, acknowledge an inquiry, assign a lead, set a task, and alert a manager when something is overdue. It should not hide responsibility. A team member still needs to know which exceptions require judgment and how to correct a bad assignment.
Start with visible, reversible rules. For example, a website form can create a new lead and notify a coordinator, while urgent terms flag the request for review instead of automatically promising emergency service. Log what the workflow changed and provide a manual path when an integration fails.
Review the pipeline as an operating habit
A short recurring review keeps the pipeline trustworthy. Look for unassigned leads, overdue actions, estimates without a decision date, duplicate customers, and records sitting in a stage without explanation. Correct the process as well as the individual record.
Retire fields and stages that do not support a decision. Add complexity only after the team can explain the recurring case it solves. A small pipeline used consistently is more useful than an elaborate one maintained only before a meeting.
Starter pipeline with clear exit conditions
| Stage | Entry condition | Exit condition |
|---|---|---|
| New | Inquiry is captured | Owner reviews and begins contact |
| Contacting | A named owner is attempting contact | Fit is understood or contact policy is completed |
| Qualified | Service, location, timing, and fit are known | Visit, estimate, or next step is scheduled |
| Decision pending | Customer has an estimate or proposed next step | Customer accepts, declines, or is closed under the follow-up policy |
| Won | Customer commits | Job or onboarding record is created |
| Closed | Opportunity will not proceed | Reason is recorded |
Working checklist
Use this before the next decision.
- Every stage has a written entry and exit condition.
- Every open lead has an owner, next action, and due date.
- Required fields support routing, service, communication, or reporting.
- Automations log changes and expose failures.
- Closed records include a useful reason.
- The team reviews exceptions on a predictable cadence.
Common questions
Put the guidance into context.
Should scheduled jobs stay in the sales pipeline?
They can move to a separate job workflow once the customer commits. Keeping sales and fulfillment distinct makes it easier to see open opportunities without losing the relationship between records.
How many pipeline stages are enough?
Use enough to represent meaningful commitments and ownership changes. If the team cannot agree on what a stage means, simplify it or define it more clearly.
What should happen to leads that stop responding?
Follow a documented contact policy, record each attempt, and close or defer the lead with a reason when the policy is complete. Do not leave it open indefinitely.