CRM for service businesses
Three sales follow-up examples from service firms
An inquiry from a web form, a proposal a committee decides and a client who asks for more: how each one is followed in a CRM.
A sales CRM makes sure every live deal has one person in charge, a next action with a date and a stage that says what happened with the client. In a service business that comes down to three situations that keep repeating: a new inquiry that arrives on its own, a proposal that more than one person decides, and an existing client who asks for an extra service. Below are three sales CRM examples, one per situation, with what each person does so the deal moves forward without relying on their memory.
The three cases are typical scenes, not real clients. They are told with what the AgentticCRM sales pipeline does today, so you can compare them with what happens on your team.
Example 1: the inquiry that comes in through the website form
An audit firm publishes a quote request form on its website. On a Tuesday night, the finance manager of a distribution company fills it in: she needs her financial statements audited before year end.
Without a CRM, that email lands in the general mailbox and someone sees it on Thursday. With the form connected to the pipeline, the submission creates a card in the Intake stage with the answers inside. The firm chose to share inquiries out by turns, so the card already has an owner: an audit manager who gets a notification and a first task to reply the next day.
On Wednesday he calls her, confirms the scope and shares his booking link for the scoping meeting. He moves the card to the stage the firm uses for scoping, enters the expected value and sets the next action to "prepare document checklist for the meeting", with a date. If he forgot, the board counts the deals with no next action and the ones that are overdue, and that number is the first thing reviewed in the Monday meeting.
Nobody had to remember to check the general mailbox: the inquiry had an owner from the moment it arrived.
Example 2: the proposal a committee decides
A technology consultancy sells the rollout of an inventory system to a chain of clinics. The person who asked for the quote is the operations manager, but the general director signs, and the purchasing team reviews it first.
The deal starts with the manager's details. When it is time to prepare the proposal, the consultancy creates the client from the deal itself and adds its people: the manager, the director and the head of purchasing, each as a contact on the client record. The proposal goes out from the card and, once it is sent, the deal moves on its own to the proposal stage.
The manager says purchasing will answer "in two weeks". That phrase becomes the next action, a task with the exact date the client gave. When the day comes and there is no answer, the consultant writes to the head of purchasing, who is already on the record. For the pace and tone of those messages, use the guide to proposals with no reply.
In the end the chain decides to push the project to next year. The consultant closes the deal as lost with the reason "timing" and a note with the month the director said she would pick it up again. The stage history keeps how long the proposal sat waiting, and that figure helps with the next quote for a similar client.
Because all three people were on the record, the consultant knew whom to write to when the manager stopped answering.
Example 3: the existing client who asks for more on WhatsApp
A marketing agency runs social media for a restaurant chain on a monthly fee. One Friday, the owner writes on WhatsApp: she wants videos shot for the opening of a new location.
In many agencies that request is settled in the chat, someone sends a price and nobody records it as a sale. From the shared inbox and WhatsApp, the account executive creates the deal from the same thread, with its owner and its follow-up task. She links it to the chain's account, which already exists in the CRM, so the request sits next to the monthly fee and the rest of its history.
The video proposal goes out separately from the monthly fee, with its own price. The owner accepts it on Tuesday, the deal moves to Won and the accepted proposal becomes an invoice. The agency opens the production project with what was sold.
Had that request stayed in the chat, the month's forecast would not show it and nobody would know how much the account grew this year.
What the three examples have in common
In all three cases the follow-up rests on the same pieces:
- an owner from day one, assigned by hand or by turns;
- a next action saved as a task with a date;
- a stage that changes when something happens with the client, such as receiving the proposal or accepting it;
- a reason when the deal is lost, to review later.
If your stages do not reflect those events yet, start by reviewing which stages a service business pipeline needs.
Frequently asked questions
What is a sales CRM?
It is the part of a CRM that follows sales: inquiries, deals, proposals and their outcome. In a service business it helps to have it in the same system as projects and invoices, so a won deal carries on without copying data.
Do I have to create the client before recording the deal?
No. The deal can start with the name, email and phone of the person who asked. The client is created from the deal when it is needed, usually when you prepare the proposal, and the two stay linked.
Do sales to existing clients go in the same pipeline?
They can go in the same one or another. If you sell two things with different processes, each can have its own pipeline with its own stages. What matters is that the request is recorded as a deal and not only in the chat.