A tool by Firecrawl · uses 5 tools · Jobs

Earnings claims vs hiring check

Use after an earnings call when an analyst wants to test whether management is really investing where it says it is. Pulls the strategic claims from the transcript, counts open roles by team, keyword and location on the company's own Workday or Greenhouse career site, and compares with segment trends, producing a say-versus-do table.

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.

  • Fiscal.aiIR event resourcesPrice30 creditsMedian339 msSuccess100%Empty4.2%
  • Fiscal.aiEarnings call transcriptPrice30 creditsMedian322 msSuccess100%Empty58.8%
  • Workday career sitesSearch jobsPrice5 creditsMedian1.2 sSuccess98.6%Empty19.2%
  • Greenhouse job boardsDepartmentsPrice5 creditsMedian–Success–Empty–
  • Fiscal.aiSegments and KPIsPrice30 creditsMedian457 msSuccess100%Empty10.9%

Instructions

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

# Earnings claims vs hiring check

For one listed company, given ticker, exchange and its career site URL. Claims from step 1 become the keyword searches in step 3.

## 1. What management said

1. Get the latest eventKey from @[Fiscal.ai · IR event resources](alexandria:fiscal-ai/events/ir-events) and read @[Fiscal.ai · Earnings call transcript](alexandria:fiscal-ai/events/transcript). List each strategic claim: investing in a product, expanding in a region, cutting a cost centre. Quote speaker and line.

## 2. Where they are hiring

2. If the site is Workday, run @[Workday · Search jobs](alexandria:myworkdayjobs-com/jobs/search_jobs) (career_site) with no query and read the facets: openings by job category and location. If it is Greenhouse, read @[Greenhouse · Departments](alexandria:greenhouse-io/jobs/departments) (board_token, include_jobs true).
3. For each claim, search again with a keyword (for example the product name or "AI") and record the count, or apply the location facet for regional claims.

## 3. Does the money agree

4. Read @[Fiscal.ai · Segments and KPIs](alexandria:fiscal-ai/company/segments-and-kpis) (periodType quarterly) for the segments the claims touch: is the segment growing in the way the claim implies.

## Write the say-versus-do table

- **Table:** claim, quote, matching open roles, location mix, segment trend, verdict (backed, thin, contradicted).
- **Standouts:** heavy hiring that management did not mention.
- **Rerun:** save the counts; repeating next quarter turns this into a trend.
- **Sources:** cite every figure to the capability and record it came from. Say what could not be found rather than guessing.
All Firecrawl tools
//
Get started
//
Start building with Alexandria.
Give your AI agent direct access to the sources it needs.
Are you an AI agent? See setup options