Earnings Transcript
Trends extracted from a company's earnings transcript.
Overview
Earnings Transcripts capture what executives say on quarterly earnings calls—the most candid public statements about a company's priorities, challenges, and investments.
We ingest transcripts from 4,000+ public companies on a weekly basis. Our model scans the full transcript—CEO remarks, CFO commentary, and analyst Q&A—to extract signals across 40+ subtypes. A single transcript typically produces 5-15 signals, each with direct quotes and speaker attribution. We prioritize statements with dollar amounts, percentages, or explicit commitments over generic commentary.
Available Subtypes
| Subtype Enum | Category | Description |
|---|---|---|
acquisitionActivity | growth | M&A activity-acquiring or being acquired |
aiInvestment | budget | AI/ML specific investment or priority |
budget | budget | General budget discussion |
budgetAndSpending | budget | Budget and spending discussion |
budgetGrowth | budget | Budget growth mentioned |
budgetIncrease | budget | Specific budget increase announced |
capexDecrease | budget | Capital expenditure decrease announced |
capexIncrease | budget | Major capital expenditure increase announced |
cloudInvestment | budget | Cloud infrastructure/migration investment |
competitiveIntelligence | competitive | Competitive dynamics discussed |
competitivePressure | pain | Competitive threats or market share loss |
competitorMention | competitive | Competitor explicitly mentioned |
costPressure | pain | Cost/margin pressures discussed |
customerExperienceFocus | strategic | Customer experience improvement priority |
customerGrowth | growth | Customer base expanding significantly |
customerWin | growth | Significant customer win announced |
dataInvestment | budget | Data infrastructure/analytics investment |
digitalTransformation | strategic | Digital transformation initiative |
efficiencyFocus | strategic | Operational efficiency as priority |
growthSignal | growth | General growth indicator |
guidanceLower | strategic | Financial guidance lowered |
guidanceRaise | strategic | Financial guidance raised |
headcountGrowth | growth | Significant hiring or workforce expansion |
investmentCommitment | budget | Specific investment commitment announced |
layoffs | organizational | Workforce reduction announced |
leadershipChange | organizational | New C-level executive or leadership change |
marketExpansion | growth | Geographic or market segment expansion |
marketShareGain | growth | Gaining market share |
marketShareLoss | competitive | Losing market share |
organizationalChange | organizational | Organizational structure changes |
painPoint | pain | General pain point identified |
productLaunch | growth | New product or service announcement |
regulatoryPressure | pain | Regulatory compliance challenges |
restructuring | organizational | Organizational restructuring |
revenueAcceleration | growth | Revenue growth rate increasing |
scalingChallenge | pain | Scaling or capacity constraints |
securityInvestment | budget | Cybersecurity investment or priority |
strategicInitiative | strategic | Strategic initiative announced |
strategicInitiatives | strategic | Multiple strategic initiatives discussed |
strategicPartnership | growth | Strategic partnership announced |
supplyChainPain | pain | Supply chain challenges mentioned |
sustainabilityFocus | strategic | ESG or sustainability initiative |
talentChallenge | pain | Hiring or talent retention challenges |
techBudgetGrowth | budget | Technology/IT budget explicitly growing |
techDebtPain | pain | Legacy systems or technical debt mentioned |
techInvestment | budget | General technology investment |
vendorSelection | budget | Vendor evaluation or selection process mentioned |
Signal Categories
Signals are organized into these categories:
| Category | Description |
|---|---|
budget | Companies actively investing-indicates available budget |
growth | Companies expanding-increased operational needs |
pain | Challenges mentioned-opportunity to solve |
strategic | What executives explicitly prioritize |
organizational | Timing opportunities from internal changes |
competitive | Market positioning insights |
Schema
{
"signal_id": "5f8f438a9fbf14db",
"signal_type": "earnings-transcript",
"signal_subtype": "investmentCommitment",
"signal_name": "Telesat Corporation Committing up to $1.2 billion for Lightspeed LEO project in 2026",
"detected_at": "2026-03-24T05:30:36.503139Z",
"company": {
"name": "Telesat Corporation",
"domain": "telesat.com",
"linkedin_url": "linkedin.com/company/telesat/",
"ticker": "TSAT",
"industries": [
"Communication Equipment"
],
"sector": "Technology"
},
"data": {
"fiscal_period": "Q1",
"fiscal_year": 2026,
"earnings_date": "2026-03-17 10:30:00",
"signal_category": "guidance",
"sales_relevance": "Long-term commitment = sustained vendor opportunities",
"relevance": 1.0,
"confidence": "high",
"sentiment": "positive",
"headline": "Committing up to $1.2 billion for Lightspeed LEO project in 2026",
"detail": "The company has a massive budget of $1.0B to $1.2B for its Lightspeed LEO satellite project in 2026, covering CapEx, OpEx, and vendor payments. This massive spend creates significant opportunities for suppliers across the satellite and communications technology stack.",
"evidence": [
"In the LEO segment, we expect to spend between $1.0 billion and $1.2 billion on Telesat Lightspeed in 2026, including operating costs, capitalized labor and interest, and capital expenditures incurred with third-party vendors and suppliers."
],
"evidence_speakers": [
{
"speaker_name": "Donald",
"speaker_title": "CFO"
}
],
"competitors_mentioned": [],
"vendors_mentioned": [],
"technologies_mentioned": [
"LEO",
"Lightspeed"
],
"regions": [],
"metric_dollar_millions": 1200.0,
"metric_pct": null,
"metric_headcount": null
},
"association": "company",
"batch_id": "batch-b46106b1"
}Field Reference
Core Fields
| Field | Type | Required | Description |
|---|---|---|---|
signal_id | string | ✓ | Unique identifier for this signal |
signal_type | string | ✓ | Always "earnings-transcript" |
signal_subtype | string | ✓ | Specific signal subtype (see subtypes list) |
signal_name | string | Human-readable signal headline with company name | |
detected_at | string (ISO 8601) | ✓ | Timestamp when the signal was extracted |
association | string | ✓ | Always "company" |
batch_id | string | Processing batch identifier |
Company Object
| Field | Type | Required | Description |
|---|---|---|---|
company.name | string | ✓ | Company name |
company.domain | string | ✓ | Company website domain |
company.linkedin_url | string (URL) | LinkedIn company page URL | |
company.ticker | string | Stock ticker symbol | |
company.industries | array[string] | Industry classifications | |
company.sector | string | Business sector |
Data Object
| Field | Type | Required | Description |
|---|---|---|---|
data.fiscal_period | string | Fiscal quarter (Q1, Q2, Q3, Q4) | |
data.fiscal_year | integer | The company's fiscal year that this report covers. May not align with the calendar year — e.g., a company with a January fiscal year-end would file its FY2025 report in early 2026 | |
data.earnings_date | string (ISO 8601) | Date of earnings call | |
data.signal_category | string | Category grouping (budget, growth, pain, etc.) (budget, competitive, growth, guidance, organizational, pain, partnership, priority) | |
data.sales_relevance | string | A brief phrase describing how this signal creates a potential sales opportunity — e.g., 'Integration needs coming', 'Change management needs'. Useful for quickly assessing outreach angles without reading the full signal | |
data.relevance | float (0.0-1.0) | Score indicating how actionable this signal is for sales outreach (0.0–1.0, where 1.0 is highest). Higher values reflect greater commercial relevance based on factors like event magnitude, recency, and potential impact on buying decisions | |
data.confidence | string | Confidence level in the signal accuracy (high, medium, low) | |
data.sentiment | string | AI-classified from the transcript text (not rule-based). The model reads the relevant excerpt and assesses whether the disclosed event is favorable, unfavorable, or neutral for the company. positive = favorable developments (growth, investment, expansion), negative = unfavorable developments (risk, cost pressure, challenges), neutral = informational without clear positive or negative implications. Often correlates with signal subtype but is context-dependent | |
data.headline | string | Concise insight summary | |
data.detail | string | AI-generated multi-sentence analysis explaining the significance of the finding — includes context about why it matters for the company and potential implications for sales outreach | |
data.evidence | array[string] | Direct quotes from transcript | |
data.evidence_speakers | array[object] | Speaker attribution for each quote | |
data.competitors_mentioned | array[string] | Competitors mentioned | |
data.vendors_mentioned | array[string] | Vendors mentioned | |
data.technologies_mentioned | array[string] | Technologies/products mentioned | |
data.regions | array[string] | Geographic regions mentioned | |
data.metric_dollar_millions | float | Dollar amount in millions | |
data.metric_pct | float | Percentage as decimal (e.g., 0.15 = 15%) | |
data.metric_headcount | integer (nullable) | Headcount number |
Data Activation
Timing
detected_at is when Autobound processed the transcript. Use data.earnings_date for when the call actually occurred - this is the authoritative event timestamp. Transcripts typically become available 1-7 days after the call.
Uniqueness
One signal per subtype per company per earnings call. A single call can produce 5-15 signals across different subtypes (budget, growth, pain, etc.).
Delivery
Each delivery arrives in a timestamped folder. Signals in that folder cover the window between this delivery and the previous one. Treat all signals in a new folder as recent and actionable—no need to diff against prior deliveries.
Best Practices
- Filter on
relevanceandconfidenceboth above 0.9 for high-precision use cases - Build picklists from
signal_subtypevalues - Use
data.earnings_dateto calculate freshness:detected_at - earnings_date - Use
evidence_speakersfor routing signals by executive role (CFO statements to finance teams, etc.)
API Usage
Generate Content API
{
"enabledInsights": [
"capexIncrease",
"aiInvestment",
"strategicInitiative"
],
"disabledInsights": []
}Generate Insights API
{
"insightSubtype": "capexIncrease"
}Example Output
"Noticed in Telesat's Q1 earnings call that you're committing $1.0-1.2B for the Lightspeed LEO project in 2026, covering CapEx, OpEx, and vendor payments. That's a massive spend across the satellite technology stack—would love to share how we're helping similar companies optimize their vendor evaluation during large infrastructure buildouts."
Coverage
- Refresh: Weekly
- Coverage: 7,000 public companies
- Best for: Enterprise sales, Executive outreach, Strategic account planning
Updated 6 days ago
