Sales for service teams
Selling for people who would rather be fixing things. Five lessons on finding the real need on site, offering clear options, and following up without being pushy.
Discovery on site
Most techs do not think of themselves as salespeople, and that is an advantage. Customers trust the person who diagnosed the problem more than anyone with a sales title. Discovery is simply the part of the visit where you learn what the customer actually needs, beyond the immediate repair.
Start by listening. Ask what prompted the call, how long the problem has been going on, and what the customer has already tried. Then ask about what matters to them: keeping costs predictable, avoiding another breakdown, comfort, uptime, compliance, or selling the property soon. The same repair can be the right answer for one customer and the wrong one for another.
Look before you recommend. Note the age and condition of the equipment, related systems, and anything that will become a problem soon. Take photos of what you see, especially nameplates and visible wear. Photos let you explain the situation later without asking the customer to take your word for it.
Separate what you found from what you recommend. Describe the condition first, in plain words, then explain the options. Customers push back when they feel steered. They lean in when they understand the situation and feel the decision is theirs.
Do not try to close everything on the spot. Some customers need to talk to a partner, a manager, or a budget. Your job in discovery is to leave with a clear picture and an agreed next step, such as a written quote by a specific day.
- What prompted the call, in the customer's words
- What the customer cares about most
- Equipment age, condition, and nameplate photo
- Related issues you noticed
- Who else is involved in the decision
- Agreed next step and date
Scoping and options
Once you know the need, scope the work. Scoping means writing down exactly what is included, what is not, and what assumptions you are making. A tight scope protects your margin and avoids the conversation where the customer thought something was included and you did not.
Write the scope in terms the customer can check. List the work, the materials or equipment, and the result they should expect. Call out exclusions directly, such as permits, patching, disposal, or after-hours work, so they are not discovered on the invoice.
Then offer options. A single price invites a yes or no. Two or three options invite a choice, and customers like having a choice. The common structure is good, better, best. Good solves the immediate problem at the lowest reasonable cost. Better solves it more durably or adds something the customer said they cared about. Best is the most complete answer, often with longer coverage or replacement instead of repair.
Every option should be one you would be comfortable doing. Do not include a bare minimum option you know will fail, and do not pad the top option with extras the customer has no use for. Options only build trust if each one is honest.
Explain the difference between options in terms of outcomes, not part numbers. "This one fixes today's problem. This one also replaces the part most likely to fail next." The customer should be able to repeat back why they chose what they chose.
In Servora, estimates support line items, discounts, tax, a deposit, and an expiry date, so each option can be written out with the same level of detail.
- 1Write the scope as included, excluded, and assumptions.
- 2Build a good option that solves the immediate problem.
- 3Build better and best options tied to what the customer said mattered.
- 4Describe each option in one sentence about the outcome.
Writing a quote or proposal customers can say yes to
A quote is a document the customer reads without you in the room. It has to stand on its own. If it needs a phone call to make sense, it will sit in an inbox until the customer forgets why they wanted it.
Lead with the customer's problem, stated the way they described it. Then the recommended work, then the options, then price, then terms. Keep each line item understandable. A customer should not need a parts catalog to follow along.
Use a short quote for simple work and a fuller proposal for larger projects. A proposal adds context: what you found, photos, why you recommend what you recommend, the timeline, and what happens after they accept. Either way, keep it as short as it can be while still being clear.
Be explicit about terms. When does the price expire? Is a deposit required? What happens if you find something unexpected once the work starts? Clear terms prevent disputes, and an expiry date gives a gentle reason to decide.
Make accepting easy. If the customer has to print, sign, scan, and email, some will not bother. A link they can open on a phone and accept from removes that friction.
Send the quote while the visit is still fresh, ideally the same day. Speed signals that you are organized and that you want the work.
In Servora, customers can accept an estimate through a share link by typing their name. Proposals use a block editor with reusable templates and a public accept page.
- Customer's problem stated in their words
- Plain-language line items
- Options clearly labeled
- Exclusions and assumptions listed
- Expiry date and deposit terms
- One clear way to accept
Follow-up cadence
Many quotes are not lost to a competitor. They are lost to silence. The customer meant to decide, got busy, and the quote slipped down the list. A steady follow-up habit wins work that would otherwise just fade away.
Decide on a cadence and use it every time, so follow-up does not depend on whether someone remembers. A simple version: a quick check the day after sending to confirm it arrived, a follow-up a few days later to answer questions, another about a week after that, and a final note shortly before the quote expires. Adjust the timing to the size of the job. Emergency repairs move in hours, larger projects in weeks.
Every follow-up should be useful. Instead of asking whether they have decided, offer something: an answer to a likely question, a clarification about an option, or a reminder of what happens if the problem is left alone. Keep it short and friendly.
Match the channel to the customer. Some respond to a call, some only to a text or email. Note what works for each customer and use it.
Know when to stop. After the final follow-up, close the opportunity and record why. A clear "not now" is better than an open quote that clutters your pipeline and your attention.
In Servora, opportunities in the CRM pipeline carry tasks and activities, so each follow-up can be scheduled as a task and logged as an activity once it happens.
- 1Write your default follow-up schedule for small jobs and for larger projects.
- 2Draft a short, useful message for each follow-up step.
- 3Schedule the follow-ups as tasks when the quote is sent.
- 4Close and record a reason after the final follow-up.
Tracking the pipeline
A pipeline is a list of every potential job, organized by how close it is to becoming work. It answers simple questions that are hard to answer from memory: what are we waiting on, what is likely to close soon, and where are deals getting stuck.
Keep the stages few and clearly defined. A typical set for a service team: new lead, site visit scheduled, quote sent, follow-up, won, lost. Each stage should mean something specific. "Quote sent" means the customer has a written quote in hand, not that someone plans to write one.
Every opportunity should have a next action and a date. An opportunity without a next step is not really in the pipeline, it is just stored there. When you review the pipeline, the first thing to look for is anything missing a next action.
Record won and lost reasons every time, with a short fixed list so they can be compared. Common choices include price, timing, chose a competitor, did not respond, and decided not to proceed. Over months, these reasons tell you more than any single deal. If many quotes are lost to timing, faster quotes may matter more than lower prices.
Review the pipeline weekly, alongside the operating review if you hold one. Look at what moved, what stalled, and what was won or lost and why.
In Servora, the CRM opportunity pipeline supports custom stages, tasks, activities, and won or lost outcomes, so the stages above can be set up to match how your team actually sells.
- Five to seven pipeline stages with written definitions
- Next action and date on every open opportunity
- A fixed list of won and lost reasons
- Weekly pipeline review on the calendar