🎯 Objection Prep Simulator

Walk in knowing the hardest question in the room — and having a better answer than you'd give unprepared.

Core Philosophy

The objections that kill proposals are almost never the ones you prepared for. You prepared for the budget question. The real blocker was "I don't think this team can execute." You prepared for the ROI objection. The real blocker was "This isn't the right time." You prepared for the technical question. The real blocker was unstated: "I already have a different solution in mind and I'm looking for a reason to say no."

This skill operates from a different starting point. It does not ask "what might they ask about this proposal?" It asks "what is the most dangerous thing someone in this room could say, and am I ready for it?" That framing change produces different prep — and better outcomes.

The architecture is adversarial by design. Phases 3 and 4 adopt the persona of the most skeptical plausible audience member, not a friendly interlocutor. The stress-test in Phase 4 does not evaluate whether the answer is good — it evaluates whether the answer survives follow-up from someone who wants to find the gap. This is the practice repetition that most presenters skip, and it is the one that matters most.

🏗️ ANCT Architecture

Entropy Profile:

Mode Transition Diagram

┌──────────┐  ┌──────────┐  ┌───────────────┐  ┌───────────────┐  ┌──────────┐
│ DELEGATE  │→│ NARRATE   │→│ GENERATE       │→│ GENERATE       │→│ DELEGATE  │
│ Collect   │  │ Map which │  │ Write Q&A as   │  │ → NARRATE      │  │ Assemble  │
│ proposal  │  │ objection │  │ skeptical      │  │ Challenge each │  │ prep pack │
│ + context │  │ categories│  │ audience member│  │ answer; flag   │  │ from all  │
│           │  │ apply     │  │                │  │ weak spots     │  │ phases    │
│ E1        │  │ E3        │  │ E4             │  │ E4→E3          │  │ E2        │
└──────────┘  └──────────┘  └───────────────┘  └───────────────┘  └──────────┘

                              ⚡ ADVERSARIAL CONSTRAINT:
                              Phase 3 must not generate
                              "friendly" objections. Every
                              question must be one a skeptic
                              would actually ask.

📥 Intake Variables

{{SOURCE_MATERIAL}}

{{AUDIENCE}}

{{OBJECTIVE}}

{{KNOWN_FACTS}}

{{CONSTRAINTS}}

{{SENSITIVITY_LEVEL}}

⚙️ Phases

Phase 1: INTAKE PROPOSAL & CONTEXT

Entropy Level: E1 – Deterministic Control Mode: DELEGATE

Parse the proposal and all context inputs. Structure what is known, what is uncertain, and what the audience is being asked to decide.

Process:

1. Extract from

   {{SOURCE_MATERIAL}}

   :
   • The core ask: what is the audience being asked to approve, fund, or endorse?
   • The stated rationale: what reasons are given in support of the ask?
   • The proposed approach: how will this be implemented?
   • The cost/investment: what resources are required?
   • The timeline: when will results be delivered?
   • The risk acknowledgment (if any): what does the proposal admit could go wrong?

2. Extract from

   {{AUDIENCE}}

   :
   • Decision-maker role(s)
   • Function(s) represented
   • Known disposition (supportive, skeptical, neutral, unknown)
   • Stakes for this audience — what do they gain or lose if this proposal succeeds or fails?

3. Extract from

   {{CONSTRAINTS}}

   and

   {{KNOWN_FACTS}}

   :
   • What evidence is available to support answers
   • What constraints bound the solution (budget ceiling, timeline, technology, headcount)
   • What context the audience already accepts vs. what must be established

4. Produce a one-paragraph intake summary: "The presenter is asking [audience] to [objective]. The proposal offers [rationale]. Known evidence includes [facts]. Key constraints are [constraints]. Sensitivity level: [level]."

Output: Structured intake summary. This is the source of truth for all subsequent phases — if a claim appears in a later phase that is not grounded in the intake summary, it must be flagged.

Phase 2: MAP OBJECTION TERRAIN

Entropy Level: E3 – Analytical Control Mode: NARRATE

Identify which objection categories apply to this proposal and audience, assess the intensity of likely challenge in each category, and prioritize where to invest prep effort.

Process:

1. Evaluate each objection category for applicability and intensity:

   Category	Core Question	Apply When
   Strategic	Does this align with where we're going?	Audience is senior; proposal is a new direction or competes with existing priorities
   Financial	What does this cost and what's the return?	Any proposal with a budget ask; especially if ROI is hard to quantify
   Operational	Can we actually execute this?	Proposal requires new capability, headcount, or significant process change
   Timing	Why now? Why not later?	Proposal is competing for resource or attention during a busy/constrained period
   Credibility	Do I trust this analysis?	New methodology, external data, small sample, self-reported, or team has not delivered before
   Political	Who loses if this succeeds?	Proposal affects turf, budget allocation, headcount, or decision authority of another stakeholder
   Alternatives	Why this approach and not another?	Other options exist; audience may have a preferred solution

2. For each applicable category, assess intensity:

   • High: This audience will almost certainly raise this. Prep is required.
   • Medium: This may come up, especially if the conversation goes sideways. Prep is valuable.
   • Low: Unlikely given this audience and proposal, but worth having a fallback.

3. Identify the highest-risk category — the one where a failed answer would most likely kill the proposal. Flag this as the "critical objection zone."

4. Note

   {{SENSITIVITY_LEVEL}}

   — high-sensitivity proposals require special handling of political objections (Phase 3 must generate those even if the presenter would prefer to avoid them).

Output: Objection terrain map — categories by intensity, critical zone identified. Example:

OBJECTION TERRAIN — [Proposal Name]

HIGH INTENSITY (prep required):
- Financial: CFO will ask for ROI quantification; methodology is soft
- Operational: Engineering already at capacity; "can you execute?" is certain
- Political: This proposal reduces Analytics team's current reporting ownership

MEDIUM INTENSITY (fallback needed):
- Timing: Budget freeze discussion is active; "why now?" is plausible
- Credibility: Survey data from n=42; sample size challenge is possible

LOW INTENSITY (monitor):
- Strategic: Aligns with stated HR priorities; minimal challenge expected
- Alternatives: No known competing proposals at this time

CRITICAL OBJECTION ZONE: Financial — if ROI cannot be defended, approval is unlikely regardless of strategic alignment.

Phase 3: GENERATE Q&A PAIRS

Entropy Level: E4 – Creative Control Mode: GENERATE

Adopt the persona of the most skeptical plausible audience member and generate verbatim-style objections for every High and Medium intensity category from Phase 2. For each objection, generate: the question, a strong answer, and a fallback answer for when the strong answer is challenged.

Adversarial Constraint: Questions must be ones a real skeptic would ask — not softball versions. The test: would a friendly colleague use this exact phrasing to warn you what to expect? If yes, it's the right question. If it sounds like a practice drill, it needs to be harder.

Process:

1. For each High-intensity category, generate 4–6 Q&A pairs.
2. For each Medium-intensity category, generate 2–3 Q&A pairs.
3. For the critical objection zone category, generate at least one question that represents the worst-case version of that objection.

Q&A Format:

Q: [Verbatim-style question — the exact words a skeptical [AUDIENCE ROLE] would use]

STRONG ANSWER:
[2–4 sentences. Directly addresses the concern. Uses specific evidence from {{KNOWN_FACTS}} where available. Does not restate the proposal — adds information or reframes.]

FALLBACK ANSWER:
[Used when the strong answer is followed with "But what about..." or "That doesn't address my concern about..."
1–2 sentences. More concessive in tone. Acknowledges the valid part of the concern. Redirects to what IS known.]

EVIDENCE REQUIRED: [What data or facts must the presenter have ready to make the strong answer land]
RISK: [What happens if this answer fails — what's the follow-up challenge to anticipate]

Examples of questions by category:

Financial:

• "Walk me through the ROI model. How confident are you in these projections?"
• "What's the cost if this doesn't work? What's our exit?"
• "We have three other proposals on the table. Why should this one get funded first?"

Operational:

• "Engineering is already committed through Q3. Where does this actually fit?"
• "Who owns this after launch? I don't see a clear DRI."
• "What does success look like at 90 days? And what does failure look like?"

Political:

• "This overlaps significantly with what [other team] is doing. Have you talked to them?"
• "Who signed off on this scope? Because this is the first I'm hearing about it."

Credibility:

• "The survey had 42 responses. How representative is that?"
• "This data is 18 months old. Is it still valid?"

Timing:

• "We just went through a restructure. Is this really the right moment?"
• "Can this wait until Q3? We have a lot on our plates right now."

Output: Full Q&A table organized by objection category, with strong answer, fallback answer, evidence required, and risk note for each.

Phase 4: STRESS-TEST ANSWERS

Entropy Level: E4→E3 – Creative to Analytical Control Mode: GENERATE→NARRATE

Challenge every strong answer from Phase 3 with a follow-up question. Identify where answers are weak. Produce a diagnosis and a suggested fix for each weakness found.

Process:

GENERATE Step (challenge round): For each strong answer in Phase 3, generate the follow-up challenge that a persistent skeptic would use:

• If the answer cited data: "How do you know that data is reliable?"
• If the answer made a prediction: "What's your confidence interval on that?"
• If the answer referenced a comparison: "But our situation is different because..."
• If the answer deflected to future work: "Why don't you have that answer today?"
• If the answer was more concessive: "So you're saying you don't actually know?"

NARRATE Step (diagnose and fix): After generating the challenge round, assess each answer against four failure modes:

{{KNOWN_FACTS}}

For each answer that fails one of these tests, produce a "Needs Reinforcement" flag:

NEEDS REINFORCEMENT — Q[N]: [question text]
Failure mode: [unsupported claim / circular logic / data gap / evasion]
Issue: [specific description of the weakness]
Fix: [one of: gather this data / cut this claim / reframe with acknowledgment / add external reference]

Output: Annotated Q&A table with stress-test results. All "Needs Reinforcement" items highlighted. Net count: how many Q&A pairs survived stress-test vs. how many need work.

Phase 5: PRODUCE PREP PACK

Entropy Level: E2 – Procedural Control Mode: DELEGATE

Assemble all phase outputs into a structured prep pack. Apply the fixed format. The prep pack is a standalone document the presenter can use in the 30 minutes before the meeting.

Process:

1. Render the Objection Map from Phase 2: visual overview of categories, intensity, and critical zone.
2. Compile the Full Q&A Table from Phases 3–4: all questions in order of intensity, with strong answers, fallback answers, and stress-test status.
3. Identify and highlight the Top 5 Hardest Questions: the five items where failure is most likely to be consequential. These are not just the hardest to answer — they are the intersection of high likelihood and high stakes.
4. Assemble the Know Before You Go 1-pager: a single-screen document the presenter reads immediately before walking in.

Know Before You Go Format:

KNOW BEFORE YOU GO — [Proposal Name]
Meeting: [date/time/audience]

WHAT THIS AUDIENCE REALLY CARES ABOUT:
[1–2 sentences — the underlying concern that drives their hardest questions]

YOUR STRONGEST ASSET:
[The one piece of evidence or argument that, if they hear and believe it, most advances the case]

YOUR BIGGEST EXPOSURE:
[The one gap or weakness that, if surfaced and unanswered, most threatens the outcome]

THE QUESTION YOU MOST NEED TO BE READY FOR:
Q: [Verbatim text of the hardest question]
A: [Strong answer — 2 sentences max]

IF THE MEETING GOES SIDEWAYS:
[One sentence — what to say if you are losing the room]

YOUR ASK, PRECISELY:
[Exact words to use when making the ask — leave no ambiguity about what you need them to decide]

Output: Complete prep pack with four sections: Objection Map, Full Q&A Table, Top 5 Hardest Questions, Know Before You Go 1-pager.

🚫 Anti-Patterns

💡 Example Applications

🖥️ Platform Notes

CLI: Paste this SKILL.md as context. Provide

{{SOURCE_MATERIAL}}

Web (Claude, ChatGPT, Gemini): Paste or attach this skill file. Include the proposal text and audience description in the first message. Request the Know Before You Go 1-pager first if time is short — it is the highest-density output.

IDE: Useful for pre-meeting preparation when the proposal or presentation is already in-context. Pipe the deck content or brief into

{{SOURCE_MATERIAL}}

Any LLM: Phases 3 and 4 (GENERATE and stress-test) require strong adversarial reasoning and the ability to adopt a consistent skeptical persona. Sonnet is recommended. Haiku is sufficient for Phase 5 (assembly) if running phases separately.

📋 Compliance

AI Governance Alignment: This skill generates simulated objections and answers to help users prepare. It does not produce statements of fact about real people, organizations, or decisions. All generated content is explicitly framed as preparation material. Users should not treat generated Q&A as definitive predictions of what will happen in a meeting.

PII Risk Level: low — The skill operates on proposal content and audience descriptions. Users should use role-based audience descriptions (e.g., "CFO with a cost-reduction mandate") rather than named individuals where possible. Avoid pasting personal performance records, compensation data, or HR case details into

{{SOURCE_MATERIAL}}

Model Recommendation: sonnet — Phases 3 and 4 require the model to adopt an adversarial persona, generate realistic skeptical questions, and perform multi-level logical analysis (claim tracing, failure mode diagnosis). These tasks benefit from Sonnet's reasoning depth and consistency across a large context window.

Data Handling: Session-local only. Proposals and recommendations may contain confidential strategic, financial, or organizational information. Use this skill in a private, compliant LLM environment for any proposal that contains non-public business strategy, financial projections, or headcount plans.