Lesson 5 of 7 · 7 min

Discovery questions: the pain is the pitch

Ask discovery questions that let the owner name the pain.

Read the lesson

Goal: Ask the questions that turn an owner's daily problems into numbers you both agree on.

You need: A booked audit meeting or reverse demo. Your own ServiceAgent account.

Why this matters

Owners do not buy software. They buy relief from a problem that costs them money, time or sleep. If you name the problem in their words, they sell themselves.

Most new Operators talk too much. They explain features before they know what hurts. The owner hears a list of things they never asked for. Good discovery reverses this. You ask, they talk, and you write down their exact words.

Their answers also give you the inputs for everything that follows. The leak math needs their calls per day, their miss rate and their average job. The proposal opens with their own numbers. The pilot measures what they care about. Without discovery, every later step rests on guesses.

The four question groups

Ask in this order. Each group builds on the last.

1. Situation: how it works today.

  • "Walk me through what happens when the phone rings at 2 pm on a Tuesday."
  • "Who answers after 5 pm and on weekends?"
  • "How do jobs get on the calendar today?"
  • "How do customers pay you, and when?"

2. Problem: where it breaks.

  • "When does the phone ring and nobody gets it?"
  • "What happens to a voicemail left on Saturday?"
  • "Which quotes go quiet after you send them?"
  • "Where do you lose the most time each week?"

3. Impact: what it costs.

  • "About how many calls do you get on a normal day?"
  • "What is a typical job worth to you?"
  • "How many hours a week do you spend on calls, scheduling and billing?"
  • "What did the last missed emergency cost you?"

4. Outcome: what good looks like.

  • "If the phones were handled, what would you do with that time?"
  • "What would make this worth it in 30 days?"
  • "Who else has to agree before you change how the phones work?"

The last question matters most for fleets and multi-location groups. It names every person who must say yes.

Fig 1

The four question groups

  1. 1SituationHow it works today
  2. 2ProblemWhere it breaks
  3. 3ImpactWhat it costs: calls, job value, hours
  4. 4OutcomeWhat good looks like, and who else must agree
Ask in order. Each group builds on the last.

How to listen

  • Ask one question at a time. Stop talking and wait. Silence brings out the real answer.
  • Listen most of the time. Aim for the owner to talk about 70% of the meeting.
  • Write their exact words. "We lose Saturday" is stronger in a proposal than "after-hours coverage gaps."
  • Repeat it back. "So Saturday calls go to voicemail, and you call back Monday. Is that right?"
  • Do not fix anything yet. If you jump to a solution, they stop telling you about the problem.
Fig 2Example numbers

Who talks in a good discovery meeting

  • The owner talksabout 70%
  • You talkabout 30%
Ask one question, then stop and wait. Silence brings out the real answer.

Owners often guess their numbers low. One study found owners believed they answered 97% of calls, while the real figure was about 66%. Treat their guesses as a starting point. Your audit calls and their call log give the real figures.

Fig 3Sourced figures

What owners believe vs what they answer

Answer rate owners believed97%
Answer rate measuredabout 66%
Treat their guesses as a starting point. The log gives the real figure.

By size. An owner-operator knows every number but rarely writes them down. Ask for a rough count and confirm it later. In a fleet, the office manager knows the call volume better than the owner. Ask them directly. In a multi-location group, ask for the numbers of one location first. Do not average across sites, because one strong site hides a weak one.

Map answers to the Job Loop

Sort each pain into a stage. This tells you which package fits later.

They sayStageFix you will offer later
"Saturday goes to voicemail"CatchAI voice agent, missed-call text-back
"Customers forget we're coming"BookReminders
"Quotes go quiet"CollectEstimate follow-up
"Nobody leaves reviews"KeepReview requests
"I do all of it from my head"RunWorkflows and tasks

Note how often each stage comes up. The stage they name first and most is the one to fix first.

Fig 4

Sort every pain into a stage

  1. Catch
  2. Book
  3. Collect
  4. Keep
Runthe back office under every stage
Provethe numbers for every stage
The stage they name first and most is the one to fix first.

Build it in ServiceAgent

Store discovery answers on the prospect's deal in your own account. Then every later step reads from one place.

  1. Open Settings → Contacts & Pipeline → Custom fields. Add three Number fields to Deal: Calls per day, Miss rate % and Average job. Add a Dropdown called After-hours handling with Voicemail, Answering service, Owner's cell and Nobody.
  2. Add Top pain (Long Text) for their exact words.
  3. During the meeting, take notes on paper or in a doc. Fill the fields right after, while the words are fresh.
  4. Add a note to the contact with the people who must say yes.
  5. Move the deal to Qualified if they agree the problem is worth fixing.
  6. Check it works. Open the deal. You should be able to compute the leak math from its fields alone.
Fig 5

Discovery fields on the deal

Add Field, applied to Deal

Calls per dayNumber
Miss rate %Number
Average jobNumber
After-hours handlingDropdown: Voicemail, Answering service, Owner's cell, Nobody
Top painLong Text, their exact words
Add Field
You should be able to compute the leak math from the deal's fields alone.

Worked example: Brightline Electric

Dev owns Brightline Electric, a 3-person shop on the roster. You ask the four groups in a 25-minute meeting.

  • Situation: Dev answers calls themselves. After 5 pm, calls go to their cell. They often cannot pick up from a job site.
  • Problem: "If I'm on a ladder, it rings out. Most don't leave a message."
  • Impact: about 8 calls a business day. They guess they miss "maybe two a week". A typical job is about $300.
  • Outcome: "I want to stop calling people back at 9 pm."

You repeat it back and they agree. Their full call log from the audit tells a different story: 44 of 176 calls missed, or 25%. You use the log, not the guess. Then you work the math with 22 business days.

  1. Calls a month: 8 × 22 = 176
  2. Missed calls: 176 × 25% = 44
  3. Jobs those callers would book: 44 × 42% = 18.48
  4. Revenue at risk: 18.48 × $300 = about $5,544 a month
  5. Pitch number: half, about $2,772 a month
Fig 6Example numbers

Brightline Electric's leak

Calls a month, 8 × 22176
×Miss rate25%
=Missed calls44
×Booking rate42%
×Average job$300
=At risk a monthabout $5,544
Pitch number, halfabout $2,772
Their own numbers make the case for you.

Dev's pain is Catch. Their words, "stop calling people back at 9 pm", go on page 1 of the proposal.

Common mistakes

  • Pitching in the first five minutes. They stop sharing. Fix: no feature names until the outcome questions are done.
  • Writing your own words. "Coverage gap" means nothing to them. Fix: write their exact words.
  • Taking their guesses as fact. Fix: confirm with the audit calls and their call log.
  • Missing the other decision makers. Fix: always ask who else must agree.

Do this now

Add the five discovery fields to deals in your own account. Write your own version of the 15 questions on one card. Practice them on a friend who owns any small business. Time: 25 minutes.

Practice the conversation

  1. Operator Dev, walk me through a Tuesday. What happens when the phone rings at 2 pm?
  2. Owner If I'm on a job, I let it ring. I check later.
  3. Operator And when you check later?
  4. Owner Half the time there's no message. Just a missed number.
  5. Operator What do you do with those numbers?
  6. Owner I call back at night. Most already found someone else.
  7. Operator About how many calls a day, would you say?
  8. Owner Maybe 8. I miss maybe two a week.
  9. Operator If the phones were handled, what changes for you?
  10. Owner I'd stop calling people back at 9 pm.
  11. Operator Let me write that down exactly as you said it.

Quick check

  1. The owner of a 20-tech fleet guesses they get "about 30 calls a day." What do you do?
    • Use 30 in the proposal, since they know their business
    • Ask the office manager and check the call log
    • Use the industry average instead
    • Double it, since owners guess low
  2. An owner says, "Quotes just sit there after I send them." Which Job Loop stage holds this pain?
    • Catch
    • Book
    • Collect
    • Keep
  3. An owner gets 10 calls a business day and misses 25%. Their average job is $400. Using 22 days and a 42% booking rate, what is the pitch number?
    • About $4,620
    • About $9,240
    • About $2,310
    • About $1,155

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community