Proposal Red-Team Loop
What would make this proposal fail in front of a smart executive? Use this before sending an AI, CRM, transformation, vendor, or budget proposal to pressure-test logic, evidence, risks, and language. Proposal Red-Team Loop Task: What would make this proposal fail in front of a smart executive? Context: [Paste your notes, excerpts, draft, meeting transcript, CRM fields, proposal text, public research, or examples here.] Context I should provide: - Proposal draft - Target audience - Decision requested - Proof points - Known objections - Claims requiring caution - Desired outcome Useful setup: Paste the proposal draft, target audience, decision requested, proof points, known objections, and claims that must be treated carefully. Why this matters: Use this before sending an AI, CRM, transformation, vendor, or budget proposal to pressure-test logic, evidence, risks, and language. Business problem: Proposals often fail because the weak claim, missing evidence, adoption risk, or unclear ask is visible to the decision maker but invisible to the author. Instructions: Act as a skeptical executive red-team reviewer. Pressure-test the proposal below. Find weak claims, unsupported assumptions, unclear asks, likely objections, and missing evidence. Then recommend a stronger structure and rewrite the opening in plain business language. Workflow: 1. Identify the ask: State the exact decision the proposal wants from the reader. 2. Find weak claims: Flag unsupported, inflated, vague, or jargon-heavy statements. 3. Map objections: List what finance, IT, legal, operations, sales, or the customer might challenge. 4. Repair the structure: Recommend a clearer order: problem, evidence, options, recommendation, risk, ask. 5. Rewrite the opening: Draft a stronger opening that names the business tension and decision. Quality bar: - Use only the context in this chat. - If important information is missing, ask for the minimum missing context before giving a final recommendation. - Separate facts from assumptions. - Do not invent customer facts, benchmarks, financial numbers, policy approvals, or system access. - Keep the answer useful for CEO / GM. Output: A red-team review with weak claims, missing evidence, likely objections, and a stronger proposal structure. - BLUF recommendation or draft. - Evidence from my context. - Assumptions and missing information. - Risks, objections, or failure modes. - Recommended next action, owner, and stop condition. Evidence checklist: - Decision ask - Business problem - Proof points - Weak claims - Objections - Risk response Stopping condition: Stop when the proposal's ask, evidence, and risks are clear enough for a skeptical reader.
Key takeaways
- What would make this proposal fail in front of a smart executive?
- A red-team review with weak claims, missing evidence, likely objections, and a stronger proposal structure.
- Stop when the proposal's ask, evidence, and risks are clear enough for a skeptical reader.
- Decision ask
- Business problem
Canonical URL: https://juanbeltran.ch/operating-loops/proposal-red-team-loop