Most teams treat the kickoff call as pure logistics — introductions, timelines, access credentials, who owns what. But buried in that first conversation is something you can't get anywhere else: the customer telling you, unprompted and in their own words, what they're hoping this will fix and how they'll know it worked. That's the raw material of a testimonial, captured at the one moment the customer is fully articulate about their problem. The trick is that you can't publish it yet — nothing has happened. So the kickoff isn't where you collect a testimonial; it's where you set one up to collect later, with most of the work already done. This guide shows you how.
Why the kickoff is the best-kept testimonial source
A testimonial persuades because it pairs a specific before-state with a specific after-state. The problem is that by the time a customer is happy enough to endorse you, they've often forgotten how bad things were before — the pain fades, and you get a vague "great product, highly recommend" that convinces no one.
The kickoff call solves this. At kickoff, the before-state is vivid and present. The customer will say things like "right now it takes us three days to close the books" or "my team is drowning in support tickets and we're losing our best people to burnout." That is the first half of a testimonial, spoken with total conviction, months before you could ever ask for a quote. Capture it now, and when the win lands you only need the second half — which is easy, because the customer is happy.
This is the same logic behind harvesting any high-emotion moment, like the reason a thank-you buried in a support ticket is worth turning into a testimonial. The difference is timing: the ticket captures the payoff, the kickoff captures the setup.
Step 1: Ask one framing question on the call
You don't need a script — you need one deliberate question early in the kickoff, phrased so the answer is quotable. The best framing is a success-definition question:
"So we're aligned three months from now — what has to be true for you to call this a clear win?"
This does two things. It forces the customer to name a concrete outcome (which you'll deliver against), and it produces a sentence you can hold them to later. Follow it with:
"And what does that look like today, before we start?"
Now you have both halves on the record: the current pain and the definition of success. Write down their exact words — not your paraphrase. "We're spending 15 hours a week on manual reconciliation" is a testimonial seed; "they had inefficiencies" is landfill.
Step 2: Capture the language verbatim, in a place you'll find it
The single most common failure is that the good quote gets lost. Someone hears it, nods, and it evaporates into the call recording no one re-watches. Fix this with a lightweight habit:
- Drop the verbatim before-state into the account record — CRM note, deal field, or a dedicated "testimonial seeds" property.
- Tag it so it's searchable later ("kickoff-quote").
- If you record calls, timestamp the moment so you can pull the clip for a video testimonial down the line.
The goal is that three months from now, when the customer hits their win, you can find their own words describing the problem in ten seconds instead of guessing.
Step 3: Set the expectation gently, now
The kickoff is also the natural place to plant the ask without any pressure. You're not asking for anything yet — you're just naming a future possibility:
"If we get you to that win, would you be open to sharing your experience so other teams like yours can see what's possible?"
Almost everyone says yes to a hypothetical future favor, especially when they're excited at the start. That soft yes removes the awkwardness later — when the win lands, you're not making a cold ask, you're following up on something they already agreed to in principle. This is the same permission-first approach that makes turning a CSAT survey comment into a testimonial feel natural rather than transactional.
Step 4: Close the loop at the win
When the customer hits the outcome you captured at kickoff, you have everything you need for a fast, high-conversion ask. Go back to them with the loop visibly closed:
"Back at kickoff you said the goal was to cut reconciliation from 15 hours a week to under 2. You're now at 90 minutes. You mentioned you'd be open to sharing your experience — would you be up for a short quote? I can even draft something from your own words to make it easy."
Then hand them a draft built from their verbatim before-state plus the measured after-state:
"We were spending 15 hours a week on manual reconciliation. We're now down to 90 minutes — it gave my team a full day back."
That draft is easy to approve because it's true, specific, and mostly the customer's own language. You're not asking them to write; you're asking them to confirm. Approval rates on a pre-drafted, accurate quote are dramatically higher than on a blank "would you write us something?"
What not to do
- Don't fabricate the before-state. If you didn't capture it verbatim, ask the customer to confirm the numbers rather than inventing them. A testimonial built on a made-up baseline is a liability, not an asset.
- Don't ask for the quote at kickoff. Nothing has happened; a testimonial given before value is delivered is hollow and both sides know it. The kickoff sets up the ask — the win triggers it.
- Don't let the seed rot. A captured quote that no one acts on at the win is worse than not capturing it, because you'll feel like you did the work. Put a reminder on the success milestone.
The payoff
Testimonials feel hard because teams try to manufacture them from cold at the end, when the customer's memory of the problem has already faded. The kickoff flips that: you capture the vivid before-state at the moment it's sharpest, plant a low-pressure yes while excitement is high, and return at the win with a draft that's already 90% written. The customer says "yeah, that's right" — and you've turned a routine logistics call into a piece of social proof that closes your next deal.