strategyplaybook.aiSqwyz
Sign in
← All 124 tools
Communicate · Choose, Plan

Objection handling brief

Collects the hardest questions in advance and answers them honestly on paper, so the first time you think about them is not in the room.

The printable canvas and the handoff into Claude Code are part of a paid plan. See what a plan includes. It needs the Claude desktop app on this machine, and your team and the prompt library already installed in that project — we cannot see your disk, so open it there.

Stage
03 Choose, 04 Plan
Works at
All levels
Maturity
Early startup → Large organisation
Time
Two hours

What it is

A prepared set of the hardest questions a proposal will face, with honest answers worked out in advance. Its secondary benefit frequently exceeds its primary one: preparing it often improves the proposal.

The objections
Generated adversarially rather than imagined politely. Someone should be trying to defeat the proposal.
Type
Factual, risk-based, resource-based, or interest-based. Each needs a different kind of response and misreading the type is why answers fail to land.
The underlying concern
What is actually being worried about. Technical objections frequently stand in for concerns about budget, workload or status.
Honest response
Including concession where the objection is right. Conceding one point buys credibility for everything else.
Proposal changes
What you alter because preparing this revealed a real weakness. Often the most valuable output.
The mistake people makePreparing rebuttals for objections that are correct produces a well-defended bad idea. If an objection stands, change the proposal — that is what the exercise is for.
What it’s forYou are about to present something contested and want the hard questions in advance.
What it’s not forThere is no audience yet.

How you run it

  1. Generate the objections adversariallyHave someone genuinely try to defeat the proposal. Politely imagined objections are the weak version of the real ones.
  2. Sort them by typeSome are factual, some are about risk, some are about interest or status. They need entirely different responses and conflating them is why answers miss.
  3. Answer honestly, including where they are rightA conceded point strengthens everything else. Defending an indefensible detail costs you the whole argument.
  4. Find the objection behind the objectionPeople rarely state the actual concern. Behind a technical question is usually a worry about budget, workload or standing.
  5. Change the proposal where the objection landsIf preparing the brief reveals a genuine flaw, fix it. That is a better outcome than a well-defended weakness.

The prompt

Two ways to run it

Run this tool in your own Claude

The short prompt starts your partner against the library on your disk. The long one carries everything with it and needs nothing installed.

🔒 Prompt locked

Everything above is free — what this tool is, what it is for, what it is not for, and how to run it as a workshop. Three tool prompts a month are free with an account; beyond three, and for the printable canvas, it is the paid part.

See plans

Your playbook

It lands in the earliest stage this tool suits. Move it on the Playbook page.

You’ll need

  • The proposal, and knowledge of who will hear it
  • People willing to voice the objections properly
  • Willingness to concede where the objection is right

You’ll end up with

  • Every likely objection with a prepared response
  • The ones where the honest answer is 'you're right'
  • What you would change as a result

Runs well with

Acquisition screen and synergy thesisAI operating model optionsAI opportunity mapAI risk classification and governance