Illustrative sample review · fictional call and fictional output · not a customer result
Discovery call · outcome unknown
A buyer agrees with the plan. Capacity is the sticking point.
The rep connects the agency’s service to the buyer’s workload. When the buyer raises an onboarding concern, the rep offers to revisit later without checking what work would actually block a start.
What worked
“If we owned the weekly creative testing, what would that give your team back?”
The rep asks the buyer to describe the value in operational terms. The buyer answers: “Time to get the launch out the door.” That gives the rep a concrete benefit to return to.
Where the response could be stronger
“The plan makes sense. I’m worried about taking on another onboarding project during the launch.”
The rep replies: “We can reconnect after launch.” The conversation moves from evaluating a start to delaying it before the onboarding concern is explored.
See a stronger response to practice
“It sounds like the onboarding work is the concern. You said getting creative testing off your plate would free up time for the launch. Which parts of getting started would put more work on your team? Let’s map those out and see whether there’s a manageable way to start.”
This acknowledges the concern, returns to the buyer’s stated benefit, and tests the blocker. It does not assume an onboarding time commitment the rep has not established.
What to practice next
Rehearse the timing objection. Reflect the concern, connect back to the buyer’s own reason for change, and ask what specifically prevents starting. Agree on a next step after understanding the answer.
Context to watch
The buyer has not rejected the plan. The effort required to onboard is unresolved. The excerpt does not establish a signed deal, a lost deal, or a proven pattern across the team.