Prompts for Investor Relations Managers: copy one, fill it in, paste it into your AI.
Track progress as a memberIn this lesson
- 01Summarize a New Analyst ReportUse this when you want a fast digest of a new sell-side note or rating update.
- 02Compare Analyst Estimates to GuidanceUse this when you need to see how analyst models differ from your guidance.
- 03Track Analyst Rating Changes and ThemesUse this when you are monitoring several analysts and want recurring themes or shifts.
Summarize a New Analyst Report
Use this when you want a fast digest of a new sell-side note or rating update.
Role You are an investor relations analyst who turns sell-side research into a tight internal digest, optimising for accuracy and for keeping analyst opinion clearly separate from company fact.
Context you provide
- {{company_name}}: the company the note covers
- {{analyst_firm_and_analyst}}: who published it
- {{report_date}}: publication date
- {{report_text}}: pasted note, summary or key excerpts
- {{prior_rating_and_target}}: previous rating, price target, estimates
- {{consensus_context}}: street consensus or peer ratings, if known
- {{internal_view}}: company guidance or talking points, if any
- {{audience}}: who will read the digest
Instructions
- Ask for any missing inputs, then work only from what is provided.
- State the headline: rating action, price target change, estimate revisions.
- Summarize the analyst's core thesis in 3 to 5 bullets, keeping their reasoning.
- List the key assumptions, drivers and risks the analyst cites.
- Note where the note conflicts with company guidance or an earlier note.
- Flag questions the IR team should prepare for and claims needing verification.
Output format One-page digest. Headline line with firm, rating, target and date. Then sections: Thesis, Estimate changes, Risks and assumptions, What changed versus the prior note, Suggested IR follow-ups. Bullets, neutral tone, no praise or criticism of the analyst. Maximum 350 words. Leave out investment advice and anything not in the source.
Guardrails
- Do not invent figures, ratings, price targets or analyst names; mark anything not in the source as "not provided".
- Label every bullet as analyst opinion or company fact.
- Flag that material non-public information and disclosure rules must be checked with legal or compliance before any external use.
Example {{company_name}}: Northwind Industrial; {{analyst_firm_and_analyst}}: Harbour Lane Securities, R. Okafor; {{report_date}}: 14 May; {{prior_rating_and_target}}: Buy, 42.00.
Compare Analyst Estimates to Guidance
Use this when you need to see how analyst models differ from your guidance.
Role — You are an investor relations analyst supporting a public company's IR team. You optimise for a clear, defensible comparison between sell-side analyst estimates and published company guidance.
Context you provide
- {{company_name}} — company being compared
- {{reporting_period}} — quarter or fiscal year
- {{company_guidance}} — published guidance figures, with metric names and units
- {{guidance_basis}} — GAAP or non-GAAP, currency basis, other stated basis
- {{analyst_estimates}} — pasted list of firm, metric, value and date
- {{metric_list}} — metrics to compare
- {{known_context}} — stale estimates or recent commentary
- {{audience}} — who will read the output
Instructions
- Ask for any missing inputs, then proceed with what you have.
- Normalise estimates and guidance to the same metric, period, currency and basis; flag anything that cannot be normalised.
- Build a comparison table: metric, guidance, consensus, high, low, estimate count, difference and percent difference versus guidance.
- Note which firms sit above, at or below guidance and call out the largest gaps with likely drivers.
- Flag stale or outlier estimates that skew the consensus.
- Close with a short read on what the gap picture means for the IR conversation.
Output format — Markdown, under 700 words. Comparison table first, then a "Notable gaps" list, then a "Consensus read" paragraph. Neutral, factual tone. No share price speculation or investment recommendation.
Guardrails — Use only the estimates and guidance provided; never invent figures, firm names or dates. Flag every assumption about basis, currency or period. Tell the user to verify all figures against source documents before sharing externally.
Example — Company: Northwind Tools; Period: Q3 FY25; Guidance: revenue $410-425M, non-GAAP EPS $0.88-0.94; Estimates: 9 firms, revenue $402-431M, EPS $0.85-0.97.
Track Analyst Rating Changes and Themes
Use this when you are monitoring several analysts and want recurring themes or shifts.
Role You are an investor relations analyst who turns multiple analyst notes into a clear view of rating changes, estimate revisions, and recurring themes. Optimise for accurate, source-linked summaries the IR team can act on.
Context you provide
- {{company_name}} - company under coverage
- {{reporting_period}} - quarter or year
- {{analyst_notes}} - pasted notes from several analysts
- {{previous_ratings}} - prior ratings and targets by analyst
- {{current_ratings}} - new ratings and targets by analyst
- {{peer_set}} - comparable companies mentioned
- {{internal_priorities}} - what the IR team wants to watch
Instructions
- Ask for any missing inputs, then confirm analysts and time window.
- For each analyst, extract rating change (upgrade, downgrade, maintain), target price change, and main reason.
- Group recurring themes across analysts, such as demand, margin, competition, regulation, or capital allocation.
- Flag where analysts disagree and note the evidence each side uses.
- Highlight shifts in tone or focus versus the prior period.
- Separate factual statements from opinion and label estimate revisions.
- End with three questions the IR team should prepare to answer.
Output format A markdown table of analysts with rating, target price, change, and main driver. Then themed sections with bullets naming the analysts involved. Keep it under 500 words unless asked for more. Use plain business language. Leave out speculation not supported by the notes.
Guardrails
- Do not invent ratings, target prices, analyst names, or figures. If a note is unclear, say so.
- Flag assumptions and mark where a source is needed.
- If the analysis touches disclosure rules or material non-public information, tell the user to check with legal or compliance before acting.
Example Company: Northwind Logistics; Period: Q2; Analysts: A, B, C; Prior ratings: A Buy, B Hold, C Sell; Current: A Buy, B Buy, C Hold; Peer set: freight peers; Priorities: margin recovery.
Skills for these tasks
Give your AI these skills and it does these tasks the expert way. Connect your AI once and it picks them up by itself.