CRM for service businesses

Pipeline stages that fit how a service business sells

The stages an agency, consultancy or firm needs in its pipeline, and the event that moves each deal to the next one.

In an architecture studio overlooking the water, the partner points at a card on a column board on a blue wall, a colleague places another and a coworker watches from her chair.

A service business usually needs five to seven pipeline stages, and each one should name something that has already happened with the client: the inquiry came in, the discovery meeting took place, the proposal went out, the client asked for changes, the deal was won or lost. A deal moves to the next column when that event happens. If a stage depends on how the salesperson feels about the deal, the board stops telling you where each sale stands.

It happens often at a consultancy's Monday sales meeting. The partner opens the board and nearly every deal of the quarter sits in a column called "Interested". She asks which ones already have a proposal, and nobody can say without opening the cards one by one. One of them signed with another firm weeks ago; another is waiting for a discovery meeting nobody scheduled, and no column on the board showed it.

Why a product pipeline does not fit selling services

Many pipeline templates come from product sales: the buyer compares options, asks for a demo and buys something that already exists. In services, what you sell is not defined yet when the inquiry arrives. Before you quote, you have to understand the problem, agree on the scope and, quite often, win over someone who was not in the first meeting, such as the manager who signs or the purchasing department.

That changes the stages. You need a moment for discovery, because that is where you decide whether there is a fit and what it will cost. The proposal is written for that client, so a week can pass between "we are preparing it" and "they have it". And after it goes out there is usually a round of scope or timing changes before anyone signs.

Sales pipeline stages for a service business

This starting point works for an agency, a consultancy or a professional firm. Next to each stage is the event that opens it:

  1. Intake: an inquiry came in through a form, an email, a WhatsApp message, a call or a referral. Nobody has reviewed it yet.
  2. Qualified: someone on the team spoke with the person and confirmed that the service, the timeline and the rough budget make sense. The deal now has an owner and an expected value.
  3. Discovery: the meeting or site visit took place to understand the problem and agree on what is in scope.
  4. Proposal sent: the client has the proposal with its price, scope and validity date.
  5. Adjustments: the client asked for changes to the scope, timeline or price, and a new version is being prepared or reviewed.
  6. Won or Lost: the client accepted, or the deal was closed with its reason.

If your sales cycle is short and discovery happens on the first call, merge Qualified and Discovery. If you sell large contracts that a purchasing committee reviews, split "Proposal sent" from "Under committee review".

The event that moves a deal to the next stage

A column called "Hot" or "Very interested" depends on who is looking at it. Two salespeople put the same deal in different places, and the board can no longer help you decide where to spend the week. When the stage names an event, such as the discovery meeting taking place or the proposal going out, anyone in the company can look at the card and know whether it sits in the right place.

The same rule gives probability its meaning. A deal in Discovery is not worth the same as one where the client holds the proposal, and a forecast weighted by stage is only reliable if each stage always means the same thing. Write each stage's rule in one line and share it with the team before you move the first card.

How to set it up in AgentticCRM

The AgentticCRM sales pipeline starts with seven ready-made stages, from Intake to Won and Lost, and you can rename them, reorder them or add your own. Each stage supplies its probability and you enter what you expect to invoice, so the forecast shows open, weighted and won amounts separately.

The board applies several of the rules above on its own. When you create the proposal from the deal and send it, the card moves by itself to the stage you marked as the proposal stage. If the client accepts, the deal is marked as won. If you close it as lost, the system asks for the reason: price, timing, competition, no response or no budget. Each deal's next action is a task with a date and an owner, and the board counts how many deals have none and how many are overdue.

If you sell two things with different processes, for example custom projects and a monthly support fee, each one can have its own pipeline with its own stages. Your plan sets how many pipelines you can run. The proposal is prepared in Proposals from the same card, with the details the deal already holds.

Signs your stages need adjusting

Every stage change is stored with its date, and that history shows whether the pipeline describes how you actually sell. Once a month, check these three things:

  • A column where deals pile up and almost none leave. It is usually a stage without a clear exit event, or a step that depends on one person in your company.
  • Stages the team skips. If almost every deal goes straight from Qualified to Proposal sent, discovery already happens on the first call and that stage is unnecessary.
  • Deals lost for the same reason. Many "no response" losses after the proposal point to your follow-up, and that is what this rhythm for writing again is for. Many "price" losses in the Adjustments stage point to how the scope was put together.

Frequently asked questions

How many stages should a service business sales pipeline have?

Five to seven are usually enough, counting Won and Lost. With fewer, moments that call for different actions get mixed together. With more, the team stops moving cards because nobody remembers how one column differs from the next.

Do I have to create the client before putting the deal in the pipeline?

No. In AgentticCRM the deal holds the name, company, email and phone of whoever asked. The client is created from the deal when it is needed, usually when you prepare the proposal, and the two stay linked.

Can my clients see which stage their deal is in?

No. The board belongs to your team. In the portal, your client sees what you share with them: their proposals, their invoices and their projects.

Request a demo using a real case from your business.

We look together at where information gets lost today, which parts AgentticCRM can join up, and which ones are not its job.

Prefer to explore on your own? Work out your current costs, see how the Assistant works or use the CRM evaluation guide.