When you ask your employees how many inquiries they have "in progress," you might get three different answers. One counts only those who received a quote. Another counts every message they've read. A third counts any contact that ever came in, regardless of whether they responded. One inquiry, three different states — and none of them are lying. Nobody ever told them what each pipeline stage actually means. This article shows you how to build definitions and transition criteria so everyone counts the same way.
Why definitions matter
Picture this situation: a client calls on Monday, leaves a message. You call back on Tuesday, talk for 15 minutes, schedule a quote. On Wednesday you send the offer. The client doesn't respond. On Thursday you follow up. On Friday you call — no answer. On Saturday you send an SMS. On Sunday the client writes that they went with a competitor.
Now ask three employees what stage this inquiry is at:
- The first will say: "new" — because they haven't received a quote response.
- The second: "quote sent" — because the offer went out.
- The third: "lost" — because the client wrote that they chose someone else.
Each answer is logical. Each is different. And each makes your sales report a statistical average of temperatures — looks specific, means nothing.
The problem isn't that people are incompetent. It's that nobody defined what each stage means, what entering the stage requires, and what exiting the stage looks like. Without this, everyone forecasts based on their own criteria, and you don't see the real picture of your business.
This article gives you a ready-made pipeline structure for a service business. You can implement it today in your company — in a CRM, in a spreadsheet, or on a board on the wall. The principles are the same.
The basic sales pipeline for a service business
A service business pipeline consists of six stages. Each stage has its definition, entry event, owner, and maximum time an inquiry can spend there. The table below shows the full model.
| Stage | Definition | Entry event | Owner | Maximum time |
|---|---|---|---|---|
| New | Inquiry received and not yet acted upon | Entry in system / message from client | Dedicated operator | 4 hours |
| Contact made | Phone or in-person conversation occurred, during which client need was established | Conversation note in system | Salesperson | 24 hours |
| Need confirmed | Client confirmed they're interested and knows the work scope | Scope defined in system | Salesperson | 48 hours |
| Quote sent | Price offer sent to client | Document sent / email with quote | Salesperson / quoting department | 72 hours |
| Decision | Client is reviewing the offer, hasn't decided yet | Quote receipt confirmation / no response within 3 days | Salesperson | 5 days |
| Won / Lost | Inquiry ended with a deal or refusal | Contract signed / loss reason entered | Salesperson | — |
Entry events, not feelings
The most important rule: an inquiry moves to the next stage not when "it feels like the client is interested," but when something concrete happens. A phone call — that's an event. A quote sent — that's an event. Quote receipt confirmation — that's an event. Deposit paid — that's an event.
The event must be objective and verifiable. When you say "the client is interested," that's your opinion, not a fact. When you say "the client confirmed the appointment date," that's a fact — the date is in the system. The CRM automatically changes the stage at the moment of the event if you configure it to. In a spreadsheet, you do it manually. On a board, you move the card. The method doesn't matter. The principle does.
Why "client is interested" is not a criterion
When you say "the client is interested," you're operating on a subjective assessment. That assessment depends on how that particular salesperson interprets the word "interested." Does it mean the client didn't say "no"? That they nodded? That they asked for more information? Each of these signals is different, and you have no way to standardize them.
That's why transition criteria must be behavioral, not perceptual. Instead of "client is interested," say "client confirmed the service scope." Instead of "client is considering," say "3 days have passed since the quote was sent and the client hasn't responded." Instead of "client wants," say "client paid a deposit." Each of these criteria you can check in the system. Each is the same for all employees.
Lost reasons — a closed list
When an inquiry reaches the "Lost" stage, the system must require a reason to be entered. Without a reason, you can't close the inquiry. This reason must come from a closed list that you set once and apply consistently. Typical reasons in a service business are:
- Price — client found the offer too expensive.
- Timeline — client needed it faster than you could offer.
- No response — client stopped responding after the quote was sent.
- Not our profile — inquiry exceeds your service range.
- Duplicate — inquiry from the same client already in the database.
- Chose competitor — client chose another company but gave a reason.
- Client withdrew — project didn't happen for reasons unrelated to price.
A closed list serves two purposes. First, it forces the salesperson to think about why they lost the inquiry. Entering "lost" alone teaches you nothing. Entering "price — too expensive compared to the three other quotes the client received" — teaches you. Second, a closed list lets you aggregate data.
Without a closed list, every "other" and "don't know" blurs the picture. After a year, you have a report that's useless.
Pipeline variants by industry
Service business is a broad term. The pipeline looks different in a medical practice, differently in a beauty salon, differently in an auto repair shop, and differently for an installation crew. The table below shows how to adapt stages to industry specifics.
| Industry | Stage 1 | Stage 2 | Stage 3 | Stage 4 | Stage 5 | Stage 6 |
|---|---|---|---|---|---|---|
| Practice (consultation) | New | Consultation scheduled | Visit occurred | Treatment / service plan presented | First treatment visit | Contract signed |
| Salon (beauty, fitness) | New | Appointment scheduled | Visit occurred | Service performed | Re-appointment scheduled | Gift card / subscription |
| Auto service | New | Diagnosis scheduled | Diagnosis performed | Quote sent | Quote accepted | Repair completed |
| Installation crew | New | Quote inquiry | Measurement / site visit | Quote sent | Quote accepted | Installation completed |
The key principle is the same regardless of industry: each stage must have a definition based on an event, not a feeling. In a practice, you don't move to "treatment plan presented" because "it feels like the client understands." You move when you actually present the plan — and the system records it.
Conversion between stages — how to count honestly
Conversion between stages is the percentage of inquiries that move from one stage to the next.
That's true, but it doesn't show where the money are lost.
Example on illustrative numbers — substitute your own: you have 100 inquiries. From New to Contact made, 60 inquiries move. From Contact to Need confirmed — 30. From Need to Quote sent — 20. From Quote to Decision — 12. From Decision to Won — 6.
You can see now that the most inquiries drop out at the very beginning: 40 out of 100 are lost between New and Contact. That's not a price problem — the client hasn't even seen the price yet. That's a first-response problem. Someone didn't call back in time, didn't answer the phone, didn't reply to the message.
When you look at conversion, always start with the biggest drop, not the end. Fixing the first stage gives the biggest return. Fixing the last stage gives marginal effect.
How to count conversion honestly
You count only those inquiries that had a chance to move to the next stage. If an inquiry ended up in Lost with reason "not our profile," you don't count it toward conversion — it didn't have a chance to move forward because it wasn't for you. If the client chose a competitor because of timeline, you also don't count it — timeline is an external factor, not your fault.
You count only those inquiries that met your offer criteria and received a response. It's harder to calculate, but it gives you the true picture of your effectiveness, not external luck.
Time at stage — what to do with hanging inquiries
Each stage has a maximum time from the table above. When that time passes and the inquiry hasn't moved to the next stage, a task is created for the stage owner. This isn't optional — it's mandatory. Someone must do something: call, write, check if the client is still interested.
Action pattern:
- 01no contact 4h
- →02task for operator
- →03no need 24h
- →04task for salesperson
- →05no response 72h
- →06follow-up task
When you apply this consistently, you see two effects. First, inquiries don't hang for months without movement. Second, you see who isn't meeting deadlines — because tasks pile up. This isn't surveillance. It's process management.
Lost inquiry data — how long to keep it
When an inquiry goes to "Lost," you must decide what happens to the data. RODO imposes the storage limitation principle: you keep personal data no longer than necessary for the purposes for which it was collected (Article 5 RODO, source: UODO RODO guide). When the purpose — i.e., handling that specific inquiry — stops existing, the data should be deleted or anonymized, unless you have another legal basis (e.g., tax obligation).
The practical approach: keep lost inquiry data for a period allowing you to analyze loss reasons — typically 6–12 months. After that period, if there's no legal basis for further storage, delete the personal data. Keep only aggregated statistics: how many inquiries, what loss reason, what price threshold. This data doesn't allow identifying a specific person, so RODO doesn't apply.
Importantly, the decision on the storage period is yours — you must make it and document it. The principle is: if data no longer serves any business purpose, you must delete it (Article 17 RODO, source: UODO Right to erasure). Consult your DPO for doubts.
Context — CRM is not the norm, it's the exception
This means roughly three-quarters of such enterprises don't use a CRM system. Many of them run their pipeline in a spreadsheet, on a cork board, or in their heads.
For you, this is both a challenge and an opportunity. Challenge: you have to build the system yourself, without ready-made tools. Opportunity: when you do it, you gain an advantage over competitors who operate on gut feeling. You don't need an expensive system to start. You need definitions, criteria, and consistency.
Do it yourself in 2 hours
Grab a spreadsheet or a piece of paper. Pull from your system or inbox the last 20 inquiries you've handled this year. For each, record: entry date, first contact date, quote sent date, decision date, outcome (won/lost), loss reason.
Now spread these 20 inquiries across the six stages from the table above. Use the definitions, not your feelings. Which stage had the biggest outflow? Where were inquiries lost? How much time passed from first contact to quote sent? From quote to decision?
After this exercise, you'll know more about your business than after a month of looking at general reports. This exercise requires no system — just your time and honesty.
How it looks in a system
In the system, everything happens automatically. Call registered → stage changes to "Contact made." Quote sent → stage changes to "Quote sent." No response 72h → system creates follow-up task.
When you close an inquiry as lost, the system requires a reason from the closed list. Without a reason, you can't close. This enforces discipline and gives you data for analysis.
Once a week you get a conversion report between stages. You see how many inquiries entered each stage, how many left and where. You see which stage is the bottleneck. You see how long on average it takes to move from stage to stage. You see which loss reasons dominate.
That's the full picture of your pipeline — and that's why definitions matter.
To build such a system in your business, you need three layers: CRM for registering inquiries and contacts, sales funnels for managing stages and events, and AI follow-up for automatic reminders to clients who haven't replied. Together they create a closed loop: an event changes the stage, no event creates a task, closing requires a reason, report shows the result.
See how it works in practice — follow-up automation shows what happens to an inquiry after the first conversation, and reporting automation shows what numbers the owner actually sees. Also check query handling automation to see how one queue replaces five inboxes, and quote automation to understand why quoting takes three days or maybe an hour.
You also need a tasks system to track who needs to do what, and analytics dashboards to see all numbers on one screen.
Frequently asked questions
Does the pipeline need exactly six stages?
No. Six is the base model for a service business, but you can simplify it to five (skipping "need confirmed") or expand with additional ones specific to your industry. What matters isn't how many stages, but that each has a definition based on an event, not a feeling.
How often should I check conversion between stages?
Once a week is the minimum that lets you catch problems before they grow. Daily review makes sense only in businesses with very high inquiry volume — above 50 per week. For most service businesses, a weekly report is enough.
What if a salesperson doesn't enter the loss reason?
If the system requires a reason to close an inquiry, there's no way around it. If you run the pipeline in a spreadsheet, you must enforce this consistently — you don't accept closure without a reason. Without data, there's no report. Without report, there's no improvement.
Do I need to buy CRM to implement a pipeline?
No. You can start with a spreadsheet or a cork board. A system is needed only when manual management starts consuming more time than client handling. For most companies, the threshold is around 20–30 active inquiries monthly.
How to measure time at stage if I don't have a system?
Set a recurring reminder in your calendar — once a day, in the morning. Review active inquiries and check if any have exceeded the maximum time from the table. In a spreadsheet, record the entry date for each stage. The system automatically calculates days between stages if you configure it.
Can the pipeline change depending on inquiry source?
Yes. You handle inquiries from Google Maps differently than from referrals, differently than from ad campaigns. You can add a "source" field and differentiate maximum time at stage or transition criteria. But the base six-stage structure stays the same — only the handling method changes.