Disc Ai Objection Answer

---
name: disc-ai-objection-answer
description: Prepares an honest answer to "why can't AI do this?" with a task split of what AI does well here, what stays with you, and an option where the client does part with their own AI. Use for "run disc-ai-objection-answer", "the client says AI could do this in 10 seconds", "why can't AI just do this", "answer the AI objection", "explain my fee when they have AI", "they asked why they need us if they have AI", "prepare me for the AI question", part of the Claude for Winning Proposals Pack by Polar Bear.
---

# AI Objection Answer

## When To Use
A client says AI could do this in 10 seconds, and you feel the urge to argue. Use this before the next conversation to answer the real question honestly: which parts of this work AI can do, which parts need you, and what that means for the price.

## When Not To Use
If the AI line is a polite cover for price, timing or "we will do it in house", the Objection Handling Map fits better. If the client asks in writing how you use AI, send your AI Use Statement instead of a spoken answer.

## Inputs
- The client's words, as close to verbatim as your notes allow, and where in the deal it came up
- Your scope or proposal, broken into the work you would actually do
- Your AI Use Statement, or a few lines on how you use AI in this work today
If you have none of this, I start from the client's sentence and your one-line scope and mark the answer as a first draft.

## Approach
Two methods carry this. The task-level view of AI at work, from the Anthropic Economic Index (anthropic.com/news/the-anthropic-economic-index), looks at work task by task and separates automation (AI does the task) from augmentation (AI helps a person do it); it is used here as a method, with no figures. LAER, from Carew International, sets the order of the conversation: listen, acknowledge, explore, respond. The failure this prevents is the defensive answer that claims AI cannot do something the client watched it do last night; you lose the room and the trust. Works in any chat.

## Workflow
1. Ask at most three questions: what exactly did the client say and who said it, what did they try with AI already, and what does your work cost them today.
2. Listen. Write the objection in the client's words, then the question behind it: is it "are you worth the price", "will this take as long as you say", or "can we do it ourselves"? Ask which one you believe it is; you know the room.
3. Acknowledge. Write one sentence agreeing with what is true. If AI can draft the analysis or the first version, say so plainly. Never open with "but".
4. Break the engagement into its real tasks and sort each into three columns: AI can do it well; AI can help a person do it; needs a person, because of judgment, context only the client holds, accountability, or the risk you carry if it goes wrong. Fill the first column first and do not shrink it to protect the fee.
5. Explore. Draft one or two questions that find what the client expects: what did the AI output give you, what was missing, who would check it before it reaches your board.
6. Respond. Say what AI does well, then what stays with you, then how you already use AI for their benefit (from your AI Use Statement). Then offer a real option: the client runs the first column with their own AI, you do the rest, and the price reflects that. You set any price; I never propose one.
7. Read it aloud test: cut every line that sounds like a rebuttal or claims AI is weaker than it is.

## Output Format
```markdown
# AI Objection Answer
**What the client said:** [their words, verbatim only if from your notes]
**The question behind it:** [price / time / do it ourselves / other]
## Task split
| Task in this engagement | AI can do it well | AI can help a person | Needs a person, and why |
|---|---|---|---|
| [task] | [yes / no] | [yes / no] | [judgment / context / accountability / risk] |
## What I say
1. Acknowledge: [one sentence agreeing with what is true]
2. Explore: [question 1] / [question 2]
3. What AI does well here: [plain list]
4. What stays with me: [plain list]
5. How I already use AI for you: [from your AI Use Statement]
6. The option with your own AI: [what they do, what I do, price set by you]
## Decision
[You decide by [date] whether to offer the split option, and at what price, before [next meeting].]
```

## Done When
- The AI column is filled first and honestly, with no task moved out of it to protect the fee
- Every "needs a person" line names the reason: judgment, context, accountability or risk
- The answer contains at least one explore question
- The split option is real, scoped and priced by you, or you have decided not to offer it

## Quality Bar
- Agree with what is true before saying anything else
- No claim that AI cannot do a task unless you have checked it
- No disparaging of AI, the client's tools or the client's use of them
- Your own AI use is said out loud, never hidden
- Say what AI does well first; never sell against AI or hide your own use.

## Next
Run disc-quote-comparison (Like-for-Like Quote Comparison) for when the objection arrives as a cheaper quote.

## About the makers

This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).