Find 5 responses to a recurring objection.
A recurring objection may have several different causes. Find what people are actually resisting, then develop five responses that earn their place through evidence and usefulness.
Try it now
Copy the prompt into your AI tool of choice, then answer its questions as they come.
Paste it into any AI chat to start. For most people, this is all you need.
Everything on this page in one paste: the prompt plus the full plan, every step and what to check. Use it for longer moves, to plan ahead, to share with a colleague, or if your AI can't open links.
How it goes
What the AI will do
- Investigates real instances of the objection, the people raising it, and responses already tried.
- Develops and tests five distinct responses using evidence-informed audience perspectives.
What to have ready
- The objection in roughly the words people use, and the proposal or idea it concerns.
- Any relevant exchanges or access to the records where they occurred.
Where you come in
- Clarify the proposal’s intended result or a disputed premise.
- Decide whether justified criticism should change the proposal.
What you'll get
Five usable responses with when to use each, supporting evidence, and any needed change to the proposal.
You're done when
You have five distinct, usable responses tied to actual or explicitly provisional concerns, with evidence, situations for use, and any unresolved change to the proposal made clear.
These are general instructions, not a description of this user's particular AI system, tools, access, or circumstances. Adapt the method to the user's goal and the capabilities you can actually use, while preserving the activity's essential sequence, review points, and intended result. ### Start with the activity and the user's context Read the complete activity and guide the user through it. Use the activity prompt yourself; the user does not need to paste it again. Keep the responsibilities of the user, the AI, and any colleague clear. Begin with what the user has already supplied. Establish the intended result and resolve missing context through focused questions when needed. Work within the activity's stated scope, permissions, required confirmations, and stopping points, including any deliberate order for introducing information. Make progress with the available information and reasonable, clearly identified assumptions where the activity allows them. ### Check the capabilities needed for this work Inspect relevant available tools, connectors, and data. Use small, relevant, non-destructive checks to establish whether necessary access or a capability actually works. Naming a product does not establish access to it. Let this activity determine what needs checking; do not impose a universal preliminary questionnaire or a full system audit. When useful access is missing: - Explain what you cannot reach and how that material would help. - Investigate practical setup, connection, export, or other access alternatives before asking the user to gather material or troubleshoot. - If progress depends on access, request only the specific user action or permission needed to enable it or provide the material another way. Continue useful independent work while awaiting the response. - Offer to walk the user through an export or upload. Welcome files, links, copied text, rough notes, or an interview as supported by your system and the activity, and use the best available route. If the missing access is optional, continue with what is available. ### Ask focused questions and respect the answers Ask questions only when necessary to complete the work well or satisfy the activity's required review points. Build on answers already supplied. Ask one question at a time, or a small group of closely related questions. Wait on work that depends on the answer, and continue useful work that does not. Explain unfamiliar language with examples where helpful. Confirm answers or decisions you supply on the user's behalf before treating them as the user's final answers or decisions. This does not require separate approval of every sourced finding; follow the activity's specific review requirements. ### Keep evidence and independent contributions distinct Distinguish evidence, inference, and missing information. Check your work against the source material. Use independent agents when your system actually supports delegation and independent investigation or review would improve the work: - Give each agent a bounded brief and the context appropriate to its role. - Keep discovery independent until synthesis where the activity requires it. Preserve any requirement for the user or colleagues to contribute before seeing other explanations. - Follow the activity's stated fallback and any required confirmation when independent agents or fresh contexts are unavailable. Preserve reviewer isolation where required; describe shared-context or sequential passes accurately. ### Produce, check, and revise the result Do the substantive investigation and production. Carry the activity through to the most complete, usable result within its scope, rather than ending with a plan or handing the main work back to the user. When missing information does not prevent useful work, proceed with clearly identified assumptions where the activity permits them. Check the result against the activity's completion criteria. At each substantive delivery, state what is complete and any material unfinished work, assumptions, helpful missing information, and remaining uncertainty. Explain how these affect what the user can use, and help the user revise the result. Preserve the activity's stopping point. Do not turn a rehearsal, investigation, or test-design activity into execution that the user has not authorized. ### Identify the objection in its setting Help me find five useful responses to a recurring objection. Start from the objection and proposal I have supplied. Preserve people's actual wording where available. Establish the intended decision, who has raised the objection, and where a response will be used: conversation, meeting, email, or a document. Use the record to answer these questions before asking me to retell the history. ### Investigate the objection and earlier answers Inspect and try relevant available connections. Search emails, chats and other messages, calendar-linked discussions, meeting transcripts, proposal documents, project records, and company data. Use the objection's wording and variants, the proposal name, participants, and relevant dates. Find several actual instances, the surrounding exchange, responses already offered, and any documented outcome. Include disagreement and failed answers rather than collecting only support for my position. Use project or company data to test underlying claims about cost, workload, customer needs, performance, timing, or feasibility. Track which objection was raised by whom, in what circumstances, and against which version of the proposal. An unanswered objection, a repeated objection, and an objection after a proposal changed are different evidence. Keep a source record and note missing coverage. If access is unavailable, investigate an export or other usable route and help me supply the key material. With only my account, treat the explanation of the audience's concerns as provisional and write responses conditional on that uncertainty. ### Separate the concerns worth answering Group the evidence by underlying concern without replacing the speaker's words with your interpretation. The same sentence may express a resource constraint, a mistrust of the evidence, a disagreement about priorities, or a real flaw in the proposal. Identify what is documented, what is inferred, and what remains unknown. Ask a focused question if an unresolved premise changes the response. Wait before work that depends on my answer. If the evidence shows a material flaw, say so plainly and propose a concrete correction for my decision; do not turn every objection into a messaging problem. ### Develop perspectives and response mechanisms Where useful, use separate audience agents for materially different concerns supported by the records. Brief each with actual identities or roles, relevant exchanges, source references, project facts, and uncertainties. Have them independently explain what a satisfactory answer would need to establish and where an earlier answer fell short. They represent evidence-informed possibilities, not the actual person's judgment. Bound each brief by concern, source set, and deliverable. Divide a large archive into manageable searches and retain coverage. Keep first findings independent before synthesis, use successive waves when concurrency is limited, and reconcile conflicting readings against the underlying sources. Without agents, use distinct manageable passes or fresh sessions with explicit handoffs and disclose shared-context review. Develop five substantively different response approaches. Let the evidence determine them. Possibilities include answering a factual premise, acknowledging a genuine cost and explaining the tradeoff, narrowing a claim, proposing a reversible test, or changing the proposal. Do not force these categories or disguise five paraphrases as five strategies. If one concern dominates, explore different legitimate ways of addressing that concern rather than inventing five audiences. ### Write and test five usable responses For each response provide: - The concern and situation it addresses. - Actual words I could say or send, in a suitable length and voice. - The evidence it relies on, with source references outside the spoken wording. - What must be true for it to be credible, and the follow-up it invites. Do not claim missing results, approvals, or resources. If a response requires a new commitment or change to the proposal, ask me to decide before presenting it as my settled position. Useful alternatives can remain clearly labeled proposals while other responses are completed. Give the five responses to the relevant audience reviewers. Ask which concern each answers, what remains unanswered, and whether its support warrants its claims. Reconcile the findings and revise weak or redundant responses. Deliver the final five, a concise guide to choosing among them, and any justified criticism that requires substantive action. State limits from missing evidence. Stop after preparation; do not send responses or execute a proposed test. These instructions were written in September 2026 using the frontier models available at the time. You may now have better tools or models, or restrictions that make some tasks harder. Your AI should adapt to the tools and access you actually have and find the best available way to help. Everything here is a starting suggestion for you and your AI, not a proven best practice for every setup. Feel free to rewrite any of it to better meet your needs.
View full AI instructions
Find 5 responses to a recurring objection.
What the AI will do
- Investigates real instances of the objection, the people raising it, and responses already tried.
- Develops and tests five distinct responses using evidence-informed audience perspectives.
What you can provide
- The objection in roughly the words people use, and the proposal or idea it concerns.
- Any relevant exchanges or access to the records where they occurred.
Where you'll take part
- Clarify the proposal’s intended result or a disputed premise.
- Decide whether justified criticism should change the proposal.
What you'll get
Five usable responses with when to use each, supporting evidence, and any needed change to the proposal.
Activity context
A recurring objection may have several different causes. Find what people are actually resisting, then develop five responses that earn their place through evidence and usefulness.
For the user
Bring the recurring objection and the proposal it concerns. The AI will find examples and earlier attempts to answer it, investigate the concerns underneath, and produce five responses. You will weigh in if the investigation uncovers a choice about the proposal itself.
Guidance for the AI
These are general instructions, not a description of this user's particular AI system, tools, access, or circumstances. Adapt the method to the user's goal and the capabilities you can actually use, while preserving the activity's essential sequence, review points, and intended result.
Start with the activity and the user's context
Read the complete activity and guide the user through it. Use the activity prompt yourself; the user does not need to paste it again. Keep the responsibilities of the user, the AI, and any colleague clear.
Begin with what the user has already supplied. Establish the intended result and resolve missing context through focused questions when needed. Work within the activity's stated scope, permissions, required confirmations, and stopping points, including any deliberate order for introducing information. Make progress with the available information and reasonable, clearly identified assumptions where the activity allows them.
Check the capabilities needed for this work
Inspect relevant available tools, connectors, and data. Use small, relevant, non-destructive checks to establish whether necessary access or a capability actually works. Naming a product does not establish access to it. Let this activity determine what needs checking; do not impose a universal preliminary questionnaire or a full system audit.
When useful access is missing:
- Explain what you cannot reach and how that material would help.
- Investigate practical setup, connection, export, or other access alternatives before asking the user to gather material or troubleshoot.
- If progress depends on access, request only the specific user action or permission needed to enable it or provide the material another way. Continue useful independent work while awaiting the response.
- Offer to walk the user through an export or upload. Welcome files, links, copied text, rough notes, or an interview as supported by your system and the activity, and use the best available route. If the missing access is optional, continue with what is available.
Ask focused questions and respect the answers
Ask questions only when necessary to complete the work well or satisfy the activity's required review points. Build on answers already supplied. Ask one question at a time, or a small group of closely related questions. Wait on work that depends on the answer, and continue useful work that does not. Explain unfamiliar language with examples where helpful.
Confirm answers or decisions you supply on the user's behalf before treating them as the user's final answers or decisions. This does not require separate approval of every sourced finding; follow the activity's specific review requirements.
Keep evidence and independent contributions distinct
Distinguish evidence, inference, and missing information. Check your work against the source material.
Use independent agents when your system actually supports delegation and independent investigation or review would improve the work:
- Give each agent a bounded brief and the context appropriate to its role.
- Keep discovery independent until synthesis where the activity requires it. Preserve any requirement for the user or colleagues to contribute before seeing other explanations.
- Follow the activity's stated fallback and any required confirmation when independent agents or fresh contexts are unavailable. Preserve reviewer isolation where required; describe shared-context or sequential passes accurately.
Produce, check, and revise the result
Do the substantive investigation and production. Carry the activity through to the most complete, usable result within its scope, rather than ending with a plan or handing the main work back to the user. When missing information does not prevent useful work, proceed with clearly identified assumptions where the activity permits them.
Check the result against the activity's completion criteria. At each substantive delivery, state what is complete and any material unfinished work, assumptions, helpful missing information, and remaining uncertainty. Explain how these affect what the user can use, and help the user revise the result.
Preserve the activity's stopping point. Do not turn a rehearsal, investigation, or test-design activity into execution that the user has not authorized.
Your AI prompt
Identify the objection in its setting
Help me find five useful responses to a recurring objection. Start from the objection and proposal I have supplied. Preserve people's actual wording where available. Establish the intended decision, who has raised the objection, and where a response will be used: conversation, meeting, email, or a document. Use the record to answer these questions before asking me to retell the history.
Investigate the objection and earlier answers
Inspect and try relevant available connections. Search emails, chats and other messages, calendar-linked discussions, meeting transcripts, proposal documents, project records, and company data. Use the objection's wording and variants, the proposal name, participants, and relevant dates. Find several actual instances, the surrounding exchange, responses already offered, and any documented outcome. Include disagreement and failed answers rather than collecting only support for my position.
Use project or company data to test underlying claims about cost, workload, customer needs, performance, timing, or feasibility. Track which objection was raised by whom, in what circumstances, and against which version of the proposal. An unanswered objection, a repeated objection, and an objection after a proposal changed are different evidence.
Keep a source record and note missing coverage. If access is unavailable, investigate an export or other usable route and help me supply the key material. With only my account, treat the explanation of the audience's concerns as provisional and write responses conditional on that uncertainty.
Separate the concerns worth answering
Group the evidence by underlying concern without replacing the speaker's words with your interpretation. The same sentence may express a resource constraint, a mistrust of the evidence, a disagreement about priorities, or a real flaw in the proposal. Identify what is documented, what is inferred, and what remains unknown.
Ask a focused question if an unresolved premise changes the response. Wait before work that depends on my answer. If the evidence shows a material flaw, say so plainly and propose a concrete correction for my decision; do not turn every objection into a messaging problem.
Develop perspectives and response mechanisms
Where useful, use separate audience agents for materially different concerns supported by the records. Brief each with actual identities or roles, relevant exchanges, source references, project facts, and uncertainties. Have them independently explain what a satisfactory answer would need to establish and where an earlier answer fell short. They represent evidence-informed possibilities, not the actual person's judgment.
Bound each brief by concern, source set, and deliverable. Divide a large archive into manageable searches and retain coverage. Keep first findings independent before synthesis, use successive waves when concurrency is limited, and reconcile conflicting readings against the underlying sources. Without agents, use distinct manageable passes or fresh sessions with explicit handoffs and disclose shared-context review.
Develop five substantively different response approaches. Let the evidence determine them. Possibilities include answering a factual premise, acknowledging a genuine cost and explaining the tradeoff, narrowing a claim, proposing a reversible test, or changing the proposal. Do not force these categories or disguise five paraphrases as five strategies. If one concern dominates, explore different legitimate ways of addressing that concern rather than inventing five audiences.
Write and test five usable responses
For each response provide:
- The concern and situation it addresses.
- Actual words I could say or send, in a suitable length and voice.
- The evidence it relies on, with source references outside the spoken wording.
- What must be true for it to be credible, and the follow-up it invites.
Do not claim missing results, approvals, or resources. If a response requires a new commitment or change to the proposal, ask me to decide before presenting it as my settled position. Useful alternatives can remain clearly labeled proposals while other responses are completed.
Give the five responses to the relevant audience reviewers. Ask which concern each answers, what remains unanswered, and whether its support warrants its claims. Reconcile the findings and revise weak or redundant responses. Deliver the final five, a concise guide to choosing among them, and any justified criticism that requires substantive action. State limits from missing evidence. Stop after preparation; do not send responses or execute a proposed test.
Done when
You have five distinct, usable responses tied to actual or explicitly provisional concerns, with evidence, situations for use, and any unresolved change to the proposal made clear.
These instructions were written in September 2026 using the frontier models available at the time. You may now have better tools or models, or restrictions that make some tasks harder. Your AI should adapt to the tools and access you actually have and find the best available way to help. Everything here is a starting suggestion for you and your AI, not a proven best practice for every setup. Feel free to rewrite any of it to better meet your needs.
These instructions were written in September 2026 using the frontier models available at the time. You may now have better tools or models, or restrictions that make some tasks harder. Your AI should adapt to the tools and access you actually have and find the best available way to help. Everything here is a starting suggestion for you and your AI, not a proven best practice for every setup. Feel free to rewrite any of it to better meet your needs.