Prepare evidence-backed answers to buying committee objections

Turn skeptical questions from finance, security, and operations buyers into clear, factual talking points with required proof assets.

Prompt

Prompt
Act as a B2B product researcher and sales enablement specialist. Review the product description or objection notes pasted below. Identify the 4 most critical buyer objections across Finance, Security, Technical Integration, and End-User Adoption. For each objection, provide an empathetic validation of the concern, an evidence-based factual rebuttal, and the specific artifact or proof asset needed to substantiate the answer. Do not invent statistics, test results, or customer logos; state clearly what documentation the internal team must produce to verify the claim. Output format: A numbered list for each objection with bold sub-headers: Persona & Objection, Factual Answer, and Required Verification Asset. My notes are below:

Example output

Example for: an automated API documentation and testing platform

  1. Finance: "We already pay for developer tooling; we cannot justify another developer subscription during a budget freeze."
  • Persona & Objection: Chief Financial Officer / VP Finance questioning recurring tool spend during spending freezes.
  • Factual Answer: The platform replaces two fragmented subscriptions (documentation hosting and manual endpoint monitoring) while reducing engineering onboarding time by roughly 20 hours per new engineer. The tool pays for itself if your engineering organization hires more than two engineers per quarter.
  • Required Verification Asset: An internal vendor consolidation calculator comparing current disparate software licenses against this platform's combined cost.
  1. Security: "Allowing your tool to parse our private code repositories introduces supply-chain risk."
  • Persona & Objection: Information Security Director concerned with third-party code access.
  • Factual Answer: The platform processes API specifications locally via a lightweight CLI runner and only metadata leaves your virtual private cloud. Source code files and environmental secrets are never transmitted, ingested, or cached on our cloud servers.
  • Required Verification Asset: Network architecture diagram showing data flow boundaries and an attestation letter confirming zero remote storage of source files.
  1. Engineering Leadership: "Our developers do not want another external dashboard; they want documentation written in markdown inside Git."
  • Persona & Objection: VP of Engineering protecting developer workflow simplicity.
  • Factual Answer: The software operates entirely inside Git pull requests. Engineers write standard Markdown and OpenAPI specs in their preferred editor; the platform compiles documentation automatically upon merge without requiring a separate web login.
  • Required Verification Asset: A 90-second workflow recording demonstrating a pull-request merge triggering documentation builds directly in GitHub Actions.
Written by AI from this prompt. Your results will vary.

Paste your product brief, pitch notes, or transcripts into ChatGPT, Claude, or Gemini after the prompt. Ask the model to suggest specific interview questions to stress-test these answers with real prospects.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Research