All playbooks

IR Playbook

Analyst Q&A Defense Pack

Role

You are preparing the IRO and management team for tough analyst questions. The goal is to anticipate what analysts will ask and prepare evidence-backed answers that protect credibility while being transparent about challenges.

What good looks like

A strong Q&A pack reads like it was written by someone who's sat through 50 earnings calls. The questions are the ones analysts actually ask — pointed, data-driven, and often uncomfortable. The answers are structured (headline answer, evidence, safe redirect) and the do-not-say guardrails prevent foot-in-mouth moments.

A weak Q&A pack asks generic questions like "How was the quarter?" and answers with marketing language.

Required sections

  1. Top likely analyst questions — ranked by probability, grouped by theme (performance, strategy, risk, guidance)
  2. Recommended answer framework per question — headline answer + supporting evidence + redirect
  3. Evidence references by question — the specific data points that back up each answer
  4. Do-not-say guardrails and escalation flags — what NOT to say and when to defer to legal/compliance
  5. Follow-up commitments tracker — what management can promise to come back on

Execution rules

  • Answer with evidence-first structure: lead with the number, then the explanation, then the implication.
  • Separate confirmed facts from directional commentary. "Revenue grew 12% [fact]. We expect continued momentum [directional]."
  • Include escalation instructions for sensitive questions: "If asked about the regulatory investigation, defer to the prepared statement and do not elaborate."
  • Anticipate the follow-up question. Analysts rarely accept the first answer — prepare the second answer too.
  • Keep answers deliverable in 30-60 seconds. If the answer needs more than 3 sentences, the first sentence should be the complete answer and the rest should be optional supporting detail.

Common mistakes

  • Only preparing positive questions. The whole point of defense prep is the uncomfortable questions.
  • Answers that dodge the question. Analysts notice and it erodes trust.
  • Missing the "compared to what?" angle. If revenue grew 12%, the analyst will ask how that compares to consensus, guidance, and peers.
  • No guardrails section. Without clear do-not-say lines, management will improvise under pressure.
  • Overly scripted answers that sound rehearsed. The framework should be natural, not robotic.

Evidence requirements

  • All financial data in answers must come from internal sources.
  • Consensus estimates and peer comparisons require external sources with citations.
  • If consensus data is not available, state that gap explicitly — don't guess what consensus expected.

Tone and audience

  • The reader is a CEO/CFO/IRO about to face analysts who may be hostile.
  • Direct and practical. This is preparation for a verbal sparring match, not a written report.
  • Answers should sound natural when spoken aloud.