A tool by Firecrawl · uses 6 tools · Finance

Guidance hit-rate scorecard

Use when an equity research associate or buy-side analyst needs to know how reliable a management team's guidance has been before trusting the new outlook. Reads several quarters of earnings call transcripts for stated guidance, compares each with reported results and adjusted metrics, and notes analyst reactions, producing a hit-rate scorecard.

Open in ChatGPT Open in Claude

Save a copy for your team

Tools it calls

Each tool's price and track record across every agent today. Empty means the call worked and found nothing.

ToolPriceMedianSuccessEmpty

Fiscal.aiIR event resourcesPrice30 creditsMedian339 msSuccess100%Empty4.2%
Fiscal.aiEarnings call transcriptPrice30 creditsMedian322 msSuccess100%Empty58.8%
Fiscal.aiIncome statementPrice15 creditsMedian356 msSuccess100%Empty5.1%
Fiscal.aiAdjusted metricsPrice30 creditsMedian–Success–Empty–
Fiscal.aiSegments and KPIsPrice30 creditsMedian457 msSuccess100%Empty10.9%
BenzingaAnalyst ratingsPrice30 creditsMedian277 msSuccess100%Empty0%

Instructions

What your agent follows when it runs this tool. Paste them into any assistant connected to Firecrawl.

# Guidance hit-rate scorecard

For one listed company and the last eight quarters. Management teams that habitually guide low and beat are read differently from those that miss.

## 1. What was promised

1. List past events with @[Fiscal.ai · IR event resources](alexandria:fiscal-ai/events/ir-events) (ticker and exchange) and carry each eventKey.
2. For each event, read the call with @[Fiscal.ai · Earnings call transcript](alexandria:fiscal-ai/events/transcript) (eventKey). Extract every quantified guide in management's prepared remarks and answers: revenue range, margin, EPS, segment targets, with the period it applies to.

## 2. What happened

3. Read quarterly reported results with @[Fiscal.ai · Income statement](alexandria:fiscal-ai/financials/income-statement) (periodType quarterly) and company-defined measures with @[Fiscal.ai · Adjusted metrics](alexandria:fiscal-ai/financials/adjusted-metrics). Match each guide to the actual for its period.
4. For segment or KPI guides, read @[Fiscal.ai · Segments and KPIs](alexandria:fiscal-ai/company/segments-and-kpis) (periodType quarterly).

## 3. How the street reacted

5. List rating changes after each print with @[Benzinga · Analyst ratings](alexandria:benzinga/calendar/ratings) (parameters[tickers], date window of a week after each call) to see whether misses cost analyst support.

## Write the scorecard

- **Table:** period, metric, guided range, actual, beat or miss, size in percent of the midpoint.
- **Hit rate:** share of guides met or beaten, and the average distance from midpoint.
- **Pattern:** sandbagging (consistent beats near the top), drift (misses growing), or reliable.
- **Reaction:** rating changes after misses.
- **Read-through:** how to haircut or trust the current guide, based only on this record.
- **Sources:** cite each guide to the transcript and timestamp and each actual to the statement period. Say which guides were too vague to score.

All Firecrawl tools