Podcast Mentions (Company)
Podcast episodes where a company, its products, or its market are discussed—with the topics and takeaways extracted.
Overview
Podcast Mentions (Company) surface what's being said about a company on podcasts—strategy, funding, product moves, and pain points, pulled straight from the conversation.
We process episodes across a large catalog of business and industry shows, transcribe them, and extract structured signals about the companies discussed. Each mention is classified into one of 66 subtypes (funding, M&A, product launches, hiring, layoffs, security incidents, and more), with supporting quotes, referenced entities (competitors, vendors, partners), and scores for relevance and confidence.
The result: you know when a prospect just raised money, named a competitor, launched a product, or disclosed a pain point on air—timely, quotable triggers for outreach.
Available Subtypes
| Subtype Enum | Category | Description |
|---|---|---|
acquisitionAnnounced | strategic | Company announces intent or agreement to acquire another company |
acquisitionCompleted | strategic | Company completes an acquisition |
aiInvestment | technology | Company investing in AI capabilities, models, or tooling |
automationInvestment | technology | Company investing in process or workflow automation |
boardChange | leadership | Change to the company's board of directors |
bookingsDecline | financial | Decline in bookings or new business discussed |
capacityConstraint | operations | Production or service capacity limits |
capexIncrease | financial | Increase in capital expenditure |
carbonCommitment | market | Carbon-reduction or net-zero commitment |
cashFlowConcern | risk | Cash-flow pressure or liquidity concern |
ceoChange | leadership | CEO transition |
channelShift | strategic | Shift in go-to-market or distribution channels |
cloudInvestment | technology | Investment in cloud infrastructure or migration |
companyPodcastAppearance | market | General appearance or feature of the company on a podcast |
competitorNamed | competitive | A competitor is explicitly named or compared |
complianceBurden | risk | Regulatory or compliance burden discussed |
costReduction | financial | Cost-cutting or efficiency initiative |
ctoChange | leadership | CTO transition |
customerChurn | risk | Customer churn or account losses discussed |
customerConcentration | risk | Revenue concentrated in a small number of customers |
cybersecurityIncident | risk | Security breach or cyber incident |
cybersecurityInvestment | technology | Investment in security tooling or programs |
dataInvestment | technology | Investment in data infrastructure or analytics |
debtRefinancing | financial | Refinancing or restructuring of debt |
digitalTransformation | technology | Broad digital-transformation initiative |
divestiture | strategic | Company divests a business unit or asset |
executiveOpinion | leadership | An executive shares a notable opinion or point of view |
expansion | operations | General business expansion |
fundingEvent | financial | Funding round or capital raise |
growthSignal | revenue | General growth indicator |
hiringSignal | workforce | Hiring or headcount growth |
industryPrediction | market | Prediction about industry direction or the future |
inflationImpact | risk | Impact of inflation on the business |
internalControlWeakness | risk | Weakness in internal controls |
internationalGrowth | operations | Expansion into international markets |
inventoryIssue | operations | Inventory problem (excess or shortage) |
laborShortage | workforce | Labor or talent shortage |
layoffs | workforce | Workforce reductions |
leadershipChange | leadership | Leadership change other than CEO or CTO |
legacyModernization | technology | Modernizing legacy systems |
litigationMaterial | risk | Material litigation or legal action |
logisticsChallenge | operations | Logistics or shipping challenge |
majorContractLoss | revenue | Loss of a major contract |
majorContractWin | revenue | Win of a major contract |
marginPressure | financial | Pressure on profit margins |
marketExpansion | market | Expansion into new markets or segments |
marketShareLoss | competitive | Loss of market share |
painPointDisclosed | risk | A business pain point or challenge disclosed |
partnership | strategic | Partnership or alliance announced |
platformStrategy | technology | Platform or ecosystem strategy |
pricingPressure | competitive | Pricing pressure discussed |
productLaunch | technology | New product or service launched |
qualityIssue | operations | Product or service quality issue |
recurringRevenueShift | revenue | Shift toward a recurring-revenue model |
regulatoryFine | risk | Regulatory fine or penalty |
restructuring | strategic | Organizational restructuring |
restructuringCharge | financial | Restructuring charge taken |
revenueAcceleration | revenue | Revenue growth accelerating |
revenueDeceleration | revenue | Revenue growth slowing |
softwareImplementation | technology | Implementing new software or systems |
spinoff | strategic | Spinning off a unit into a separate entity |
strategyShift | strategic | Notable change in company strategy |
supplyChainDisruption | operations | Supply-chain disruption |
sustainabilityInvestment | market | Investment in sustainability or ESG |
techAdoption | technology | Adoption of a new technology |
techMigration | technology | Migration between technologies or platforms |
Signal Categories
Each signal carries a data.signal_category assigned by the extraction model. Categories are thematic groupings, not a closed enum; the most common are:
| Category | Description |
|---|---|
financial | Funding, capex, cost, margin, debt, and other money movements |
revenue | Wins, losses, and shifts in revenue trajectory |
strategic | M&A, partnerships, divestitures, and strategy shifts |
operations | Capacity, supply chain, logistics, expansion, and quality |
workforce | Hiring, layoffs, and labor supply |
leadership | Executive and board changes, executive opinions |
technology | Product launches, tech adoption, migrations, and IT investment |
market | Market moves, industry predictions, and sustainability |
risk | Security, litigation, compliance, churn, and disclosed concerns |
competitive | Competitor mentions, pricing pressure, and market-share moves |
Schema
{
"signal_id": "b7c1e4a2-9f3d-5e88-a1b6-3c2d4e5f6a70",
"signal_type": "podcast-company",
"signal_subtype": "fundingEvent",
"detected_at": "2026-07-31T00:00:00Z",
"association": "company",
"episode_id": "acqrd-2026-07-31-the-saas-revenue-show-ep-214",
"parent_signal_id": null,
"company": {
"name": "Ramp",
"domain": "ramp.com",
"description": "Corporate card and spend-management platform for finance teams.",
"employee_count_low": 1001,
"employee_count_high": 5000,
"industries": [
"Financial Services",
"Software Development"
],
"linkedin_url": "linkedin.com/company/ramp"
},
"data": {
"podcast_name": "The SaaS Revenue Show",
"episode_title": "Scaling spend management past $700M in card volume",
"episode_url": "https://example.com/podcasts/saas-revenue-show/214",
"headline": "Ramp closed a $200M round to push deeper into AI-driven finance automation",
"detail": "On the episode, Ramp's CFO described a newly closed $200M growth round earmarked for AI features that auto-categorize spend and flag anomalies, plus expansion of the finance-automation team.",
"evidence": [
{
"speaker_name": "Sarah Chen",
"speaker_title": "Chief Financial Officer",
"speaker_company": "Ramp",
"role": "guest",
"quotes": [
"We just closed $200 million, and almost all of it is going into automating the parts of finance nobody wants to do by hand.",
"The goal is that by next year, month-end close is something the software just does."
]
}
],
"entities_referenced": [
{
"name": "Brex",
"domain": "brex.com",
"relationship": "competitor",
"context": "Named while contrasting approaches to spend automation",
"headline": "Ramp positioned its automation depth against Brex",
"detail": "The CFO argued Ramp's automation goes further than competing corporate-card products."
}
],
"source": {
"episode_date": "2026-07-31T00:00:00Z",
"podcast_popularity": 0.78
},
"entity_type": "company",
"entity_role": "mentioned",
"signal_category": "financial",
"relevance": 0.91,
"confidence": "high",
"sentiment": "positive",
"is_ad": false,
"metric_dollar_millions": 200.0,
"metric_pct": null
}
}Field Reference
Core Fields
| Field | Type | Required | Description |
|---|---|---|---|
signal_id | string (UUID) | ✓ | Unique identifier for this signal |
signal_type | string | ✓ | Always "podcast-company" |
signal_subtype | string | ✓ | Specific signal subtype (see allowed values above) |
detected_at | string (ISO 8601) | ✓ | Episode publication date |
association | string | ✓ | Entity association type - always "company" |
episode_id | string | ✓ | Source podcast episode identifier (dedup key) |
parent_signal_id | string (UUID) | Parent signal when this was expanded from a referenced entity; otherwise null |
Company Object
| Field | Type | Required | Description |
|---|---|---|---|
company.name | string | ✓ | Company discussed or appearing |
company.domain | string | ✓* | Company domain (primary match key) |
company.linkedin_url | string (URL) | ✓* | Company LinkedIn URL (alternate match key) |
company.description | string | Company description | |
company.industries | array[string] | Industry classifications | |
company.employee_count_low | integer | Lower bound of employee-count range | |
company.employee_count_high | integer | Upper bound of employee-count range |
*A company signal requires at least one of domain or linkedin_url.
Data Object
| Field | Type | Required | Description |
|---|---|---|---|
data.podcast_name | string | ✓ | Name of the podcast show |
data.episode_title | string | ✓ | Title of the episode |
data.episode_url | string (URL) | Link to the episode | |
data.headline | string | ✓ | One-line takeaway (≤120 chars) |
data.detail | string | ✓ | Fuller description of what was said and why it matters |
data.evidence | array[object] | ✓ | Supporting quotes with speaker attribution (see Evidence Object) |
data.entities_referenced | array[object] | Other companies/entities named in the discussion (see Entity Object) | |
data.source | object | Episode metadata (see Source Object) | |
data.entity_type | string | Type of entity the signal is about (company, government, organization, individual) | |
data.entity_role | string | Role in the episode (guest, mentioned) | |
data.signal_category | string | Model-assigned theme for the signal (see Signal Categories) | |
data.relevance | float | Relevance / actionability score (0.0-1.0) | |
data.confidence | string | Extraction confidence (high, medium, low) | |
data.sentiment | string | Sentiment of the mention (positive, neutral, negative) | |
data.is_ad | boolean | Whether the mention came from an ad/sponsor read | |
data.metric_dollar_millions | float | Dollar figure referenced, in millions USD (when stated) | |
data.metric_pct | float | Percentage figure referenced (when stated) |
Evidence Object
| Field | Type | Description |
|---|---|---|
evidence[].speaker_name | string | Name of the person quoted |
evidence[].speaker_title | string | Speaker's job title |
evidence[].speaker_company | string | Speaker's company |
evidence[].role | string | Speaker role (guest, host, analyst, correspondent) |
evidence[].quotes | array[string] | Verbatim quotes supporting the signal |
Entity Object (entities_referenced[])
entities_referenced[])| Field | Type | Description |
|---|---|---|
entities_referenced[].name | string | Name of the referenced entity |
entities_referenced[].domain | string | Domain of the referenced entity (nullable) |
entities_referenced[].relationship | string | Relationship to the subject (vendor, new_vendor, former_vendor, displaced_vendor, replacement_vendor, customer, former_customer, competitor, partner, acquisition_target, acquirer, vendor_evaluated, investor, other) |
entities_referenced[].context | string | Why the entity was mentioned |
entities_referenced[].headline | string | One-line takeaway about the referenced entity |
entities_referenced[].detail | string | Fuller description of the reference |
Source Object
| Field | Type | Description |
|---|---|---|
source.episode_date | string (ISO 8601) | Publication date of the episode |
source.podcast_popularity | float | Relative popularity of the show (0.0-1.0) |
Coverage
- Refresh: Monthly
- Association: Company-level
- Subtypes: 66
Next: Data Activation Guide — Playbooks for turning podcast signals into personalized outreach and competitive intelligence.
Updated 44 minutes ago

