Practice the objection before you write the follow-up
“Send me something” can feel like progress until you sit down to write the email. What did the buyer actually need: a price, a technical answer, a comparison, or time to involve someone else? A short rehearsal can help you prepare a clearer response before the next conversation.
Use this exercise with a colleague or your own recording. If you are preparing a PitchTest scenario, the same brief gives the practice buyer a concrete situation to respond to. The goal is one useful conversation, with one concern and one next step.
Start with the buyer's words
Write the objection as closely as you can remember it. Keep your interpretation on a separate line. “We already use a spreadsheet” is an observation; “they will never pay for this” is your conclusion. Rehearse against the observation first.
Use an invented company name and remove personal or confidential details. A useful brief needs the buyer's role, current approach and stated concern. It rarely needs a real person's email address or an internal contract.
Example practice brief: You sell a scheduling tool to a small service business. The operations lead manages bookings in a shared spreadsheet. They said, “Moving everything would take too much time.” You want to learn which part of the change feels risky before proposing a next step.
Choose one concern to work on
Resist adding every objection you have ever heard. For this round, use the switching concern above. A buyer who questions the migration effort needs a different conversation from one who has no budget or no scheduling problem.
In PitchTest's manager scenario form, the product or service, prospect persona and objections provide the practice context. You can enter your own objections and review them before creating a scenario. Use those fields to keep this exercise specific. If a manager has already prepared your scenario, start from the details they share.
Rehearse a question before an answer
Try this sequence aloud:
- Acknowledge: “Changing a system the team already knows can take work.”
- Clarify: “Which part would be hardest: moving the bookings, training the team, or running both systems during the change?”
- Respond to the answer: explain only the part you can support with facts. If you do not know what an import supports, make checking that your next step.
- Ask for a concrete next move: “Would reviewing a sample import together help you decide whether a trial is worth the effort?”
These lines are prompts for a conversation, not a script to recite over the buyer. Leave room for them to disagree. If their answer changes your understanding, change the response too.
Review the moment you missed
After the practice, write down the exact question you asked and the next step you requested. Did you learn something new about the concern? Did you promise something you still need to verify? Did your closing question name an action the buyer could accept or decline?
Pick one weak moment and repeat that part. For example, replace a long explanation of features with a question about the migration risk. Compare the two attempts using what you actually said. A practice result is a rehearsal signal; the real buyer still makes their own decision.
Turn the rehearsal into a useful follow-up
A follow-up can now be short: restate the concern, provide the information you agreed to check, and propose the next action. Give the action an owner and a date. Separate an agreed meeting from an idea you have only proposed, so your notes do not turn hopeful language into a commitment.
Keep the actual contact, deal context and follow-up date in your usual relationship tracker. If you need a place for those details, Relay is a separate CRM for contacts, deal pipelines and next-step tasks, made by Todd B Smith, who also makes PitchTest. Explore its public demo to see whether that workflow fits you, then record the details yourself.
For the next rehearsal, bring back the question the real buyer left unanswered. That gives you a specific place to start instead of polishing the entire pitch again.