Trial Conversion Call: A Scored Drill Guide

Chapters
TL;DR
A trial conversion call should turn what the buyer already did in the trial into pain they confirm in their own words, then into a next step with a date, attendees, and a purpose. Run it in stages, drill one agreed first response each for we're still testing and I just need a pricing answer, and certify reps on two transcript-scored scenarios before they take live trial calls.
- Open with an up-front contract: purpose, time, both agendas, and no as an acceptable outcome.
- Start discovery from one specific trial usage event, not a blank situation question.
- Drill one agreed first response per objection, then let reps improvise the branches.
- Pass the pain row only when the buyer states the cost, then how they feel about it.
- Schedule the re-run of every failed drill before the debrief ends.
What makes a trial conversion call different from first discovery?
The buyer has already used the product. In first discovery you build the picture of the problem with the buyer from the start. On a trial conversion call the buyer arrives with opinions formed without you, and your first job is to find out what those opinions rest on.
That changes the opening. We treat product-led sales discovery as starting from a usage event: a workflow the buyer tried, a report they built, a step where they stopped. Ask about the event, not the company. You built a dashboard early in the trial and haven't opened it since. What were you trying to get done with it? Ask it so the buyer has something concrete to correct or confirm.
Treat a free trial sales call as its own call type with its own stages and scenarios. Plan for three openings in your practice library: the buyer who starts with a support question, the buyer who says they are still testing, and the buyer who asks only for a price. Answer a support question briefly, then return to the agenda you agreed at the start. Handle the other two as objections with agreed first responses, covered below.
Start trial-call discovery from what the buyer did in the product, not from a blank situation question.
Five stages and their exit criteria
Score each stage against exit criteria: buyer-verified evidence that must exist before the call moves to the next stage. Scoring changes behavior only when it is graded against your own methodology and call stages. The stages below use Sandler terms; rename stages and rows to match your playbook before you drill them.
Stages one, two, three, and five run in order. The objection stage has no fixed position: score it wherever the objection lands, including the buyer's first sentence, then return to the earliest stage whose exit criteria are not yet met.
Stage one uses the Sandler up-front contract: purpose, time, both agendas, and acceptable outcomes agreed before the conversation, including that no is acceptable. A line that does the job: Before we start: we have until the top of the hour. I'd like to hear what you tried in the trial and where it fell short, and I'll answer anything on pricing. What do you want to get out of the call? By the end, we either agree a next step or you tell me it's not a fit. Does that work?
For stage three, run the Sandler pain funnel in order: from the surface issue, to its concrete cost, to how the buyer feels about it. Reversing the order is a misuse. Do not propose a next step in the trial-to-paid conversation until the buyer has said the cost out loud.
A stage is complete when the buyer has said the evidence out loud, not when the rep believes it.
| Stage | Rep's job | Exit criteria |
|---|---|---|
| 1. Up-front contract | Agree purpose, time, both agendas, acceptable outcomes | Buyer confirms the time, adds their own agenda, and accepts no as a valid outcome |
| 2. Usage replay | Ask about one specific usage event from the trial | Buyer names the task they attempted and what happened |
| 3. Pain confirmation | Move from the event to its cost, then to feelings, in funnel order | Buyer states the cost in their own words, then how they feel about it |
| Objection (any point) | Deliver the agreed first response, then branch | Buyer answers the question inside the first response |
| 5. Next step | Propose a named next step | Buyer confirms date, attendees, and purpose, or states a clear no |
How should a rep answer the still-testing objection?
Agree with the test, then ask what the test has to prove. The agreed first response: Good. You should test it properly. What would the trial need to show you for you to call it a success? The question asks the buyer to state success criteria in their own words.
Branches are improvised. If the buyer names a criterion, move into usage replay and ask which part of the trial has tested it so far. If the buyer cannot name one, offer to define the criteria together and book the review where you will check them.
This guide drills two trial user objections. Build the rest of your inventory from the words your own buyers used on recorded calls, and give each one a single agreed first response.
The argument against agreed first responses deserves a fair hearing: a line repeated word for word can sound canned, and strong reps improvise well. We fix only the first response. Reps drill it until it is automatic, then improvise the branches from understanding rather than being caught flat.
A failing attempt concedes before the buyer names any criterion: No problem, I can extend your trial if you need more time. In that transcript the rep gives away an extension and never asks what the test is for.
Fix the first response and improvise the branches; rehearsal is what makes the improvisation safe.
How should a rep answer a pricing-only request?
Promise the number on this call, ask one question that ties price to the trial, then give the number. The agreed first response: You'll have a price before we hang up. It depends on which team would use it first. Which team ran the trial?
The rep must then deliver the number. We score a response that delays the price indefinitely as a fail, the same as one that reads the price sheet and lets the call end. The first response buys one question, not a stall.
Branches: if the buyer names a team, ask what that team was trying to fix during the trial, then quote. If the buyer pushes for the number immediately, give it, then ask what they will compare it against. For the same request earlier in a sales cycle, see The Early Pricing Question: Discovery Drills.
A failing transcript is short. Buyer: I just need a pricing answer. Rep: Sure, it's per seat. I'll send the sheet over. Buyer: Great, thanks. In that transcript no usage is discussed, no pain is confirmed, and no next step is booked.
A rep who answers a price request with only a price fails the confirmed pain and named next step rows.
The rubric: from observed usage to a named next step
Score from the transcript alone. Each row is an observable behavior with a pass and a fail that a second manager could verify without hearing the call.
Read talk/listen ratio as a diagnostic, not a pass bar. If it skews toward the rep, open the transcript at usage replay and check whether the usage question was asked at all. Read trends per rep per scenario: a rep who passes the still-testing scenario and fails the pricing-only one needs the pricing drill, not a blended average.
If you run the drill on XL Roleplay, your call stages and rubrics are loaded first, every session is scored against them, and flags in the report link back to the exact moment in the transcript. The rubric below works on any tool, or on paper, as long as the transcript is the evidence.
The pain row passes only when the buyer, not the rep, says what the problem costs and how they feel about it.
| Rubric row | Pass (in the transcript) | Fail (in the transcript) |
|---|---|---|
| Up-front contract | Rep states purpose and time, asks for the buyer's agenda, and names no as acceptable; buyer agrees | Rep skips time or the buyer's agenda, or omits no as an outcome |
| Usage anchor | First discovery question names a specific trial event | Rep opens with generic situation questions |
| Confirmed pain | Buyer states the cost in their own words, then how they feel about it, in that order | Rep states the cost, buyer only agrees, or the feelings question comes before the cost |
| First response | Rep delivers the agreed first response before branching | Rep improvises from the first word or concedes an extension, discount, or price sheet |
| Named next step | Buyer confirms date, attendees, and purpose, or states a clear no | A vague promise to follow up by email |
Should reps learn trial calls on live buyers?
No. Rehearse in scored practice first, then gate live trial calls on passing transcripts.
The opposing view holds that reps learn best on live calls, where the stakes are real, and that practice environments add little. We take the stakes seriously, and that is the reason to rehearse first: burning real pipeline as training material is the most expensive coaching method a sales org can choose.
Make the gate concrete. A passing scored rep on both scenarios, still-testing and pricing-only, releases solo trial calls. A fail means a re-run, not a later calendar date. Decide from the scored transcripts rather than from how the rep sounds in team meetings, because manager intuition alone systematically overrates confident reps and underrates quiet ones.
Gate solo trial calls on passing scored transcripts, not on weeks served.
The drill to run this week
We recommend a 30-minute run for the manager: 5 minutes setup, 15 minutes drill, 10 minutes debrief. Spend about 10 minutes beforehand picking the scenario from a live deal and choosing the one rubric row you will debrief. Put the block on the calendar as a recurring commitment, separate from pipeline review. If your team is new to scored practice, start with AI Roleplay Training: First 30 Days.
Run two scenarios as separate scored sessions so you can read trends per scenario. Scenario A: an operations lead near the end of a trial opens with we're still testing. Scenario B: the same lead opens with I just need a pricing answer. Seed both with one usage event from a real account in your pipeline. We recommend Scenario A this week and Scenario B next week. Pass bar for each: all five rubric rows at pass in that scenario's transcript.
A failing Scenario A attempt sounds like this. Buyer: We're still testing, honestly. Rep: Totally fine. Did you get a chance to try the reporting module? The new version has scheduled exports too. Buyer: Not yet. Rep: I can extend your trial so you have time. I'll send a follow-up email. That attempt fails the usage anchor, first response, confirmed pain, and named next step rows. For Scenario B, use the failing transcript in the pricing section as the model.
Debrief one row, not four. Ask: Find the moment the buyer said we're still testing. What did you say next, and what does the agreed first response say? Let the rep self-diagnose before you give a verdict, then book the re-run on the same scenario before the debrief ends. The Sales Roleplay Debrief: One Behavior, Re-Run guide has the full script.
A failed drill is not finished until the re-run is on the calendar.
Frequently asked questions
Should the rep review trial usage data before the call?
Yes. Pick one specific usage event to open usage replay, such as a workflow the buyer started and abandoned. Generic situation questions in its place fail the usage anchor row.
Can the rep offer a trial extension on the call?
Only as a trade for a named next step, never as the first response to we're still testing. An extension offered before the buyer names success criteria fails the first response row.
Does the drill work if our team uses SPIN instead of Sandler?
Yes, after you replace the Sandler-specific rows with your own. Score the pain stage on whether the rep asked implication questions that built the cost of inaction before naming any solution, and replace the up-front contract row with your team's own call-opening standard.
What if the buyer says no at the end of the call?
A clear, stated no is an acceptable outcome under the up-front contract and passes the next-step row. The row fails only on a vague maybe with no date, attendees, or purpose.
How soon should a rep re-run a failed attempt?
We recommend booking the re-run before the debrief ends and running it the same week, against the same scenario and the same rubric row.