A checklist gets answers. A conversation gets the truth.
Here's a call I've heard some version of a hundred times.
Rep: Great, and what's your timeline on this? Customer: Probably in the next month or so. Rep: Got it. And do you have a budget in mind? Customer: Somewhere around twenty grand. Rep: Perfect. And are you the one making the decision? Customer: Yep, me and my wife. Rep: Awesome. Let me get you some options.
The rep fills in four CRM fields and marks the lead qualified. The manager looks at the record the next morning and sees timeline, budget, decision maker, need. Everything's there. Looks like a good call.
It wasn't a good call. It was a form being read out loud.
Nothing the rep learned changes anything. "A month or so" isn't a timeline — it's a polite way of saying leave me alone until I'm ready. "Around twenty grand" is a number the customer made up because you asked for one. "Me and my wife" tells you there's a second person but nothing about what she cares about or whether she's even on board.
The rep has four data points and zero understanding. And the next touch will be generic because there's nothing specific to be specific about.
What a checklist is actually for
I'm not anti-checklist. A checklist is a floor. It keeps a nervous new rep from hanging up without asking about money. It makes sure that when a deal gets handed off, the next person isn't starting from zero.
The problem is when the checklist becomes the ceiling. The rep's internal goal stops being understand this person and becomes fill the fields. Those are different jobs and they produce different calls.
You can hear the difference immediately. Checklist calls have a rhythm: question, answer, next question. No reaction. No follow-up. The rep is reading down a page and the customer can tell.
A real qualification conversation has branches. The rep hears something, stops, and goes sideways into it. The call doesn't follow the order of the form, because the customer didn't answer in the order of the form.
The three moves that turn a checklist into a conversation
1. React before you advance
The single biggest tell. When a customer gives you an answer, does the rep say anything about it — or do they just move to the next question?
Checklist version:
Customer: We've been having trouble with the current system. Rep: Okay. And what's your timeline for replacing it?
Conversation version:
Customer: We've been having trouble with the current system. Rep: Trouble how? Is it breaking, or is it just not doing what you need it to? Customer: Breaking. Twice last month. Rep: What happened when it broke? Did you lose a day? Customer: We lost two days and had to send people home.
Now you have something. "Sent people home twice last month" is a cost. You can build a whole deal on it. "Having trouble with the current system" is a sentence that goes in a CRM note and does nothing.
The coaching instruction is one line: ask one follow-up before you move on. Not three. One. Most reps can do that immediately and it doubles the information density of their calls.
2. Make every answer concrete
Every vague answer has a concrete version underneath it. The rep's job is to get to it.
| What they say | What you still don't know | What to ask |
|---|---|---|
| "Soon" | What makes it soon | "What's happening in the next few weeks that makes this the time?" |
| "Around $20k" | Whether that's a wish or a limit | "Is that what you'd like to spend, or is that the number you can't go over?" |
| "Me and my wife" | Whether she agrees | "Where is she on this? Is she pushing for it or is this more your project?" |
| "We're getting a few quotes" | Who else and what they liked | "Who else are you talking to? What did you think of them?" |
| "Need to think about it" | What specifically | "What part are you thinking about — the price, the timing, or whether it's the right fix?" |
None of these are clever. They're just the second question, the one the checklist doesn't have a box for.
3. Ask about the thing that doesn't have a field
Here's where most scorecards miss. The highest-value information on a call is usually something that doesn't fit any category:
- Why they called today instead of three weeks ago
- What they tried already and why it didn't work
- Who got blamed last time this went wrong
- What happens if they do nothing
That last one is worth teaching on its own.
Rep: Let me ask you something. If you decide to hold off and do nothing for six months, what does that look like? Customer: Honestly? We'd just keep limping along. It's annoying but it's not killing us.
That answer is gold and it's bad news, which is why it's gold. You just learned this deal isn't closing this month, and now you can stop burning follow-up calls on it. The checklist would have told you "timeline: 30 days" and you'd have chased it for six weeks.
How to tell which kind of call you've got
Pull three calls from a rep this week and check for these. It takes about fifteen minutes.
Count the follow-up questions. Not total questions — follow-ups. Questions that respond to the specific thing the customer just said. If a twelve-minute call has zero, you have a checklist.
Look for a number the rep didn't ask for. In real conversations, customers volunteer specifics: "we lost two days," "the guy before quoted eleven five," "my lease is up in August." If the only numbers on the call are ones the rep requested, the customer never opened up.
Read the CRM note and ask: could this be about anyone? If the note would fit fifty other customers, nothing was learned. A good note is unusable for any other deal.
Check if the rep ever got surprised. Did the call go somewhere they didn't plan? Surprise means the customer was actually talking. No surprises means the rep ran the script and the customer complied.
Fixing it without rewriting your process
Don't throw out the checklist. Change the order of operations.
Tell your reps: have the conversation, then fill the form after you hang up. The fields are a record, not a route. Most reps are reading the screen because it's in front of them during the call. Turn the screen off.
Then add one rule to your call reviews. For each required field, the rep needs the answer and one piece of supporting detail. Budget isn't "$20k" — it's "$20k, that's the cap, and it's from a capital line that resets in Q1." Timeline isn't "30 days" — it's "30 days because the lease ends and they're paying month-to-month after that."
If a rep can't produce the supporting detail, the field isn't filled. It's guessed.
That's a change you can announce in a five-minute meeting and enforce in your next pipeline review. No new training program required.
The whole thing comes down to a question you can ask yourself after any call: what do I know now that I couldn't have guessed before I picked up the phone? If the answer is "nothing," the rep ran a checklist — no matter how many boxes are green.
If you're reviewing calls at any volume, this is one of the easier patterns to spot systematically: follow-up question rate, concrete detail per field, notes that are specific to one human being. Tools like MoreSignal flag it on the transcript, but a manager with three calls and fifteen minutes can find it just as well.