Podcast Appearances (Contact)

Podcast appearances by individual contacts—what they said, the topics they care about, and where they're building a public voice.

Overview

Podcast Appearances (Contact) capture the moments a prospect goes on the record—what an executive actually said on a podcast, in their own words.

We process episodes across a large catalog of business and industry shows, transcribe them, and extract structured signals attributed to the specific person speaking. Each appearance is classified into one of 50 subtypes (funding, hiring, executive opinions, strategy shifts, pain points, and more), with the supporting quotes, the entities they referenced, and scores for relevance and confidence.

The result: you know exactly what a buyer believes, what they're investing in, and which competitors they're weighing—giving you 30-60 minutes of their own words to reference in outreach.

Available Subtypes

Subtype EnumCategoryDescription
acquisitionAnnouncedstrategicCompany announces intent or agreement to acquire another company
acquisitionCompletedstrategicCompany completes an acquisition
aiInvestmenttechnologyCompany investing in AI capabilities, models, or tooling
automationInvestmenttechnologyCompany investing in process or workflow automation
boardChangeleadershipChange to the company's board of directors
capacityConstraintoperationsProduction or service capacity limits
capexIncreasefinancialIncrease in capital expenditure
cashFlowConcernriskCash-flow pressure or liquidity concern
channelShiftstrategicShift in go-to-market or distribution channels
cloudInvestmenttechnologyInvestment in cloud infrastructure or migration
competitorNamedcompetitiveA competitor is explicitly named or compared
complianceBurdenriskRegulatory or compliance burden discussed
costReductionfinancialCost-cutting or efficiency initiative
customerChurnriskCustomer churn or account losses discussed
cybersecurityInvestmenttechnologyInvestment in security tooling or programs
dataInvestmenttechnologyInvestment in data infrastructure or analytics
digitalTransformationtechnologyBroad digital-transformation initiative
executiveOpinionleadershipAn executive shares a notable opinion or point of view
expansionoperationsGeneral business expansion
fundingEventfinancialFunding round or capital raise
growthSignalrevenueGeneral growth indicator
hiringSignalworkforceHiring or headcount growth
industryPredictionmarketPrediction about industry direction or the future
inflationImpactriskImpact of inflation on the business
internationalGrowthoperationsExpansion into international markets
inventoryIssueoperationsInventory problem (excess or shortage)
laborShortageworkforceLabor or talent shortage
layoffsworkforceWorkforce reductions
leadershipChangeleadershipLeadership change other than CEO or CTO
legacyModernizationtechnologyModernizing legacy systems
litigationMaterialriskMaterial litigation or legal action
majorContractLossrevenueLoss of a major contract
majorContractWinrevenueWin of a major contract
manufacturingIssueoperationsManufacturing or production issue disclosed
marketExpansionmarketExpansion into new markets or segments
painPointDisclosedriskA business pain point or challenge disclosed
partnershipstrategicPartnership or alliance announced
platformStrategytechnologyPlatform or ecosystem strategy
pricingPressurecompetitivePricing pressure discussed
productLaunchtechnologyNew product or service launched
recurringRevenueShiftrevenueShift toward a recurring-revenue model
restructuringstrategicOrganizational restructuring
revenueAccelerationrevenueRevenue growth accelerating
softwareImplementationtechnologyImplementing new software or systems
strategyShiftstrategicNotable change in company strategy
supplierConcentrationriskDependence on a small number of suppliers
supplyChainDisruptionoperationsSupply-chain disruption
sustainabilityInvestmentmarketInvestment in sustainability or ESG
techAdoptiontechnologyAdoption of a new technology
techMigrationtechnologyMigration 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:

CategoryDescription
financialFunding, capex, cost, margin, debt, and other money movements
revenueWins, losses, and shifts in revenue trajectory
strategicM&A, partnerships, divestitures, and strategy shifts
operationsCapacity, supply chain, logistics, expansion, and quality
workforceHiring, layoffs, and labor supply
leadershipExecutive and board changes, executive opinions
technologyProduct launches, tech adoption, migrations, and IT investment
marketMarket moves, industry predictions, and sustainability
riskSecurity, litigation, compliance, churn, and disclosed concerns
competitiveCompetitor mentions, pricing pressure, and market-share moves

Schema

{
  "signal_id": "d2f5a8b1-4c6e-5a90-b3c7-8e1f2a3b4c5d",
  "signal_type": "podcast-contact",
  "signal_subtype": "executiveOpinion",
  "detected_at": "2026-07-18T00:00:00Z",
  "association": "contact",
  "episode_id": "acqrd-2026-07-18-the-data-stack-show-ep-98",
  "parent_signal_id": null,
  "company": {
    "name": "Snowflake",
    "domain": "snowflake.com",
    "description": "Cloud data platform for storage, analytics, and data sharing.",
    "employee_count_low": 5001,
    "employee_count_high": 10000,
    "industries": [
      "Software Development",
      "Data Infrastructure And Analytics"
    ],
    "linkedin_url": "linkedin.com/company/snowflake-computing"
  },
  "contact": {
    "name": "Marcus Reyes",
    "first_name": "Marcus",
    "last_name": "Reyes",
    "job_title": "VP of Data Platform",
    "email": null,
    "linkedin_url": "linkedin.com/in/marcus-reyes"
  },
  "data": {
    "podcast_name": "The Data Stack Show",
    "episode_title": "Why the warehouse is becoming the application layer",
    "episode_url": "https://example.com/podcasts/data-stack-show/98",
    "headline": "Snowflake's VP of Data Platform says teams should stop copying data out of the warehouse",
    "detail": "As a guest, Marcus argued that reverse-ETL and app-in-warehouse patterns will replace most data copying within two years, and described an internal push to run ML workloads directly on the platform.",
    "evidence": [
      {
        "speaker_name": "Marcus Reyes",
        "speaker_title": "VP of Data Platform",
        "speaker_company": "Snowflake",
        "role": "guest",
        "quotes": [
          "If you're still shipping copies of your data to five different tools, you're going to lose the next two years to plumbing.",
          "We're moving the compute to the data, not the other way around."
        ]
      }
    ],
    "entities_referenced": [
      {
        "name": "Databricks",
        "domain": "databricks.com",
        "relationship": "competitor",
        "context": "Referenced when comparing lakehouse architectures",
        "headline": "Contrasted Snowflake's approach with Databricks",
        "detail": "Marcus compared platform strategies without naming a winner."
      }
    ],
    "source": {
      "episode_date": "2026-07-18T00:00:00Z",
      "podcast_popularity": 0.64
    },
    "entity_type": "individual",
    "entity_role": "guest",
    "signal_category": "technology",
    "relevance": 0.87,
    "confidence": "high",
    "sentiment": "neutral",
    "is_ad": false,
    "metric_dollar_millions": null,
    "metric_pct": null
  }
}

Field Reference

Core Fields

FieldTypeRequiredDescription
signal_idstring (UUID)Unique identifier for this signal
signal_typestringAlways "podcast-contact"
signal_subtypestringSpecific signal subtype (see allowed values above)
detected_atstring (ISO 8601)Episode publication date
associationstringEntity association type - always "contact"
episode_idstringSource podcast episode identifier (dedup key)
parent_signal_idstring (UUID)Parent signal when this was expanded from a referenced entity; otherwise null

Company Object

FieldTypeRequiredDescription
company.namestringCompany discussed or appearing
company.domainstring✓*Company domain (primary match key)
company.linkedin_urlstring (URL)✓*Company LinkedIn URL (alternate match key)
company.descriptionstringCompany description
company.industriesarray[string]Industry classifications
company.employee_count_lowintegerLower bound of employee-count range
company.employee_count_highintegerUpper bound of employee-count range

*A company signal requires at least one of domain or linkedin_url.

Contact Object

FieldTypeRequiredDescription
contact.namestringFull name of the contact
contact.first_namestringFirst name
contact.last_namestringLast name
contact.job_titlestringJob title at time of appearance
contact.emailstring✓*Work email (match key)
contact.linkedin_urlstring (URL)✓*Contact LinkedIn URL (match key)

*A contact signal requires at least one of email or linkedin_url.

Data Object

FieldTypeRequiredDescription
data.podcast_namestringName of the podcast show
data.episode_titlestringTitle of the episode
data.episode_urlstring (URL)Link to the episode
data.headlinestringOne-line takeaway (≤120 chars)
data.detailstringFuller description of what was said and why it matters
data.evidencearray[object]Supporting quotes with speaker attribution (see Evidence Object)
data.entities_referencedarray[object]Other companies/entities named in the discussion (see Entity Object)
data.sourceobjectEpisode metadata (see Source Object)
data.entity_typestringType of entity the signal is about (company, government, organization, individual)
data.entity_rolestringRole in the episode (guest, mentioned)
data.signal_categorystringModel-assigned theme for the signal (see Signal Categories)
data.relevancefloatRelevance / actionability score (0.0-1.0)
data.confidencestringExtraction confidence (high, medium, low)
data.sentimentstringSentiment of the mention (positive, neutral, negative)
data.is_adbooleanWhether the mention came from an ad/sponsor read
data.metric_dollar_millionsfloatDollar figure referenced, in millions USD (when stated)
data.metric_pctfloatPercentage figure referenced (when stated)

Evidence Object

FieldTypeDescription
evidence[].speaker_namestringName of the person quoted
evidence[].speaker_titlestringSpeaker's job title
evidence[].speaker_companystringSpeaker's company
evidence[].rolestringSpeaker role (guest, host, analyst, correspondent)
evidence[].quotesarray[string]Verbatim quotes supporting the signal

Entity Object (entities_referenced[])

FieldTypeDescription
entities_referenced[].namestringName of the referenced entity
entities_referenced[].domainstringDomain of the referenced entity (nullable)
entities_referenced[].relationshipstringRelationship 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[].contextstringWhy the entity was mentioned
entities_referenced[].headlinestringOne-line takeaway about the referenced entity
entities_referenced[].detailstringFuller description of the reference

Source Object

FieldTypeDescription
source.episode_datestring (ISO 8601)Publication date of the episode
source.podcast_popularityfloatRelative popularity of the show (0.0-1.0)

Coverage

  • Refresh: Monthly
  • Association: Contact-level
  • Subtypes: 50

Next: Data Activation Guide — Playbooks for turning podcast signals into personalized outreach and competitive intelligence.


Did this page help you?