10-K Filings

The 10-K is the comprehensive annual report that US public companies are required to file with the SEC.

Every week, we scan SEC EDGAR for new filings across 8,000+ publicly traded companies. For any 10-K filed in the past 7 days, our pipeline extracts and analyzes the full document - with particular emphasis on the Management Discussion & Analysis (MD&A) and Risk Factors sections, where companies disclose their strategic priorities, operational challenges, and forward-looking concerns.

Each filing is classified into one or more of 70+ event subtypes (leadership changes, acquisitions, cost reduction initiatives, cybersecurity investments, etc.) using a model we've fine-tuned specifically for SEC document analysis.

A single filing can produce between 5-25 signals, depending on how many relevant initiatives or pain points can be inferred accurately from the document's content.

📎
See real delivered data → Sample Files

Each filing is classified into one or more of 70+ event subtypes (legacy modernization, cybersecurity incidents, software implementations, leadership changes, and more) — the specific business events we extract from the document.

Available Subtypes (70+)

Subtype Enum	Description
`acquisitionAnnounced`	Company announced an upcoming acquisition
`acquisitionCompleted`	Company completed an acquisition
`aiInvestment`	Company is investing in AI/ML capabilities
`auditIssue`	Audit findings or concerns identified
`automationInvestment`	Investing in automation initiatives to improve efficiency
`backlogGrowth`	Order backlog is growing significantly
`bankruptcyProceeding`	Bankruptcy filing or proceeding disclosed
`boardChange`	Changes to board of directors
`bookingsDecline`	Decline in bookings or orders
`capacityConstraint`	Facing capacity constraints or limitations
`capexIncrease`	Capital expenditure is increasing
`carbonCommitment`	Carbon reduction or net-zero commitments
`cashFlowConcern`	Facing cash flow challenges or concerns
`ceoChange`	New CEO appointed
`cfoChange`	New CFO appointed
`channelShift`	Shifting sales or distribution channels
`chroChange`	New Chief Human Resources Officer appointed
`cioChange`	New CIO appointed
`cisoChange`	New CISO appointed
`cloudInvestment`	Investing in cloud infrastructure and migration
`cmoChange`	New CMO appointed
`competitorNamed`	Specific competitor mentioned as significant threat
`complianceBurden`	Facing significant regulatory compliance challenges
`cooChange`	New COO appointed
`costReduction`	Actively pursuing cost reduction initiatives
`croChange`	New Chief Revenue Officer appointed
`ctoChange`	New CTO appointed
`customerChurn`	Experiencing customer churn issues
`customerConcentration`	Revenue concentrated in few customers
`cybersecurityIncident`	Cybersecurity breach or incident disclosed
`cybersecurityInvestment`	Investing in cybersecurity measures and infrastructure
`dataInvestment`	Investing in data and analytics capabilities
`debtRefinancing`	Refinancing debt obligations
`deiInitiative`	Diversity, equity, and inclusion initiatives
`digitalTransformation`	Undergoing digital transformation initiatives
`divestiture`	Divesting business units or assets
`environmentalLiability`	Facing environmental liability or remediation
`founderDeparture`	Founder leaving the company
`generalCounselChange`	New General Counsel appointed
`goodwillImpairment`	Taking goodwill impairment charges
`governanceChange`	Corporate governance changes
`hiringFreeze`	Hiring freeze announced
`inflationImpact`	Inflation significantly impacting costs or margins
`internalControlWeakness`	Internal control weaknesses identified
`internationalGrowth`	Expanding international presence
`inventoryIssue`	Facing inventory management challenges
`jointVenture`	Forming joint venture or strategic partnership
`laborShortage`	Facing labor or talent shortages
`layoffs`	Workforce reduction announced
`legacyModernization`	Modernizing legacy systems and technical debt
`litigationMaterial`	Facing material litigation or legal matters
`logisticsChallenge`	Experiencing logistics and distribution difficulties
`majorContractLoss`	Lost significant contract or deal
`majorContractWin`	Won significant contract or deal
`manufacturingIssue`	Facing manufacturing challenges or capacity constraints
`marginPressure`	Profit margins under pressure
`marketExpansion`	Expanding into new markets or segments
`marketShareLoss`	Losing market share to competitors
`materialContract`	Significant contract or agreement disclosed
`platformStrategy`	Pursuing platform-based business strategy
`pricingPressure`	Facing competitive pricing pressure
`productLaunch`	Launching new products or services
`productLiability`	Facing product liability issues
`qualityIssue`	Product or service quality issues
`recurringRevenueShift`	Shifting business model toward recurring revenue
`regulatoryFine`	Regulatory fine or penalty
`regulatoryInvestigation`	Under regulatory investigation
`restructuring`	Undergoing organizational restructuring
`restructuringCharge`	Taking restructuring charges
`softwareImplementation`	Implementing major new software systems
`spinoff`	Spinning off business unit
`successionAnnouncement`	Leadership succession plan announced
`supplierConcentration`	Supply chain concentrated in few suppliers
`supplyChainDisruption`	Experiencing supply chain disruptions
`sustainabilityInvestment`	Investing in ESG and sustainability initiatives

Categories group subtypes into higher-level themes — a common way to filter signals by sales motion or use case.

Signal Categories

Category	Description
`strategic`	M&A, platform strategy, product launches, ESG initiatives
`market`	Expansion, competition, pricing, customer dynamics
`financial`	Margins, capex, debt, revenue model changes
`technology`	AI, automation, digital transformation, cybersecurity investments
`risk`	Compliance, internal controls, concentration risks
`operations`	Supply chain, inventory, restructuring, cost reduction initiatives
`revenue`	Revenue trends, bookings, growth signals
`workforce`	Leadership changes, talent acquisition, labor challenges
`leadership`	Executive and board changes
`esg`	Environmental, social, governance initiatives

Example Signal

What a single entry looks like in a delivered signal file:

{
  "signal_id": "a4c29f81-7e3d-4a12-b6f0-83d5e2194c07",
  "batch_id": "2026-03-15-00-00-00",
  "signal_type": "10k",
  "signal_subtype": "legacyModernization",
  "detected_at": "2026-03-15T11:32:07.441892Z",
  "association": "company",
  "company": {
    "name": "Elastic N.V.",
    "domain": "elastic.co",                   // match on domain
    "linkedin_url": "linkedin.com/company/elastic-co",  // or match on LinkedIn URL
    "industries": ["Software Development"],
    "employee_count_low": 3001,
    "employee_count_high": 4000,
    "description": "Search and observability platform..."
  },
  "contact": [],
  "data": {
    "summary": "Elastic disclosed a $38M initiative to replace legacy on-prem billing and order management systems with cloud-native infrastructure...",
    "detail": "Elastic's 10-K reveals a multi-year modernization program targeting their order-to-cash stack. They explicitly cite aging on-premises billing infrastructure as a barrier to scaling consumption-based pricing...",
    "relevance": 0.91,                      // 0.0-1.0; higher = more actionable for outreach
    "excerpts": "We are investing approximately $38 million to modernize our order management and billing infrastructure, transitioning from legacy on-premises systems to cloud-native platforms capable of supporting usage-based pricing at scale...",
    "source_url": "https://www.sec.gov/Archives/edgar/data/1707753/000170775326000012/estc-20260430.htm",
    "confidence": "high",                    // how certain this signal is accurate
    "sentiment": "positive",
    "competitors_mentioned": [],
    "vendors_mentioned": ["Zuora", "Stripe"],
    "technologies_mentioned": [
      "cloud-native billing",
      "usage-based pricing",
      "CPQ modernization",
      "revenue recognition automation"
    ],
    "regions_mentioned": ["United States", "Netherlands"],
    "fiscal_year_end": "04/30",
    "filing_year": 2026,
    "sales_relevance": "Active vendor evaluation for billing/order management systems",
    "filing_date": "2026-03-12",
    "signal_category": "technology",
    "metrics": {
      "dollar_millions": 38.0,
      "dollar_context": "Budget committed to replacing legacy billing infrastructure",
      "pct": null,
      "pct_context": null,
      "timeframe": "next_two_years"
    }
  }
}

Field Reference

Standard envelope and entity fields are shared across all signals — see Schema and Resolution. The fields below are specific to this signal:

Signal-Specific Fields

The data object contains everything unique to this signal type — the intelligence extracted from the filing.

Field	Type	Description
`summary`	string	One-line headline describing the signal (e.g., "Elastic disclosed a $38M initiative to replace legacy billing systems"). Designed to be shown directly to end users as a notification or list item. Typically 10–20 words, always includes the company name and the core event
`detail`	string	Multi-sentence analysis written for a salesperson or account executive. Explains what the company disclosed, why it matters commercially, and what kind of vendor or solution they might need. Typically 3–5 sentences. Generated by synthesizing multiple sections of the filing — not just the excerpt
`relevance`	float (0.0–1.0)	How actionable this signal is for outreach. Higher = stronger commercial signal. Useful for prioritization and filtering
`confidence`	string	Confidence that this event actually occurred and was categorized accurately. `high`, `medium`, or `low`. Useful for filtering in production
`sentiment`	string	Whether the disclosed event is favorable (`positive`), unfavorable (`negative`), or informational (`neutral`) for the company. Useful for segmenting outreach tone
`excerpts`	string	A representative direct quote pulled from the SEC filing that supports this signal. This is one passage that best illustrates the event — the model reads the full document (MD&A, Risk Factors, financial statements) and may synthesize insights from multiple sections that aren't all quoted here. Useful for displaying to users as proof or for fact-checking against the source
`source_url`	string (URL)	Link to the filing on SEC EDGAR. Useful for displaying to users who want to validate or fact-check the signal
`competitors_mentioned`	array[string]	Competitors explicitly named in the filing. Empty array if none found
`vendors_mentioned`	array[string]	Vendors or partners explicitly named. Useful for identifying existing tech stack
`technologies_mentioned`	array[string]	Technologies, platforms, or tools referenced. Useful for building tech-stack-based targeting
`regions_mentioned`	array[string]	Geographic regions referenced. Useful for territory-based routing
`fiscal_year_end`	string	Company's fiscal year end in MM/DD format. Useful for filtering by reporting cycle or aligning to budget seasons
`filing_date`	string (date)	Date the filing was submitted to the SEC. Useful for recency filtering
`filing_year`	integer	Calendar year the filing was submitted
`sales_relevance`	string	Brief phrase describing the outreach angle this signal creates. Useful as a prompt input or display label
`signal_category`	string	Category grouping (see Signal Categories above). Useful for routing signals to the right sales motion
`metrics.dollar_millions`	float \| null	Dollar amount in millions USD when a specific figure is cited in the filing (e.g., "$38M in modernization spend"). Null when the signal doesn't reference a dollar amount. Useful for sorting signals by financial magnitude
`metrics.dollar_context`	string \| null	What the dollar amount refers to. Useful for displaying alongside the number
`metrics.pct`	float \| null	Percentage value when cited (e.g., 0.44 = 44% growth). Null when no percentage is mentioned
`metrics.pct_context`	string \| null	What the percentage refers to
`metrics.timeframe`	string	Time horizon for the event — one of: `immediate`, `current_quarter`, `current_year`, `next_quarter`, `next_year`, `next_two_years`, `next_three_years`, `multi_year`, `last_year`, `ongoing`

Timing & Delivery

detected_at is when we processed the filing. Use filing_date and source_url for the original submission context.
One signal per subtype per company per fiscal year. A single 10-K can produce multiple signals across different subtypes, but won't fire the same subtype twice for the same filing.
Each delivery arrives in a timestamped folder. Treat all signals in a new folder as recent — no need to diff against prior deliveries.

Coverage

Refresh: Weekly
Coverage: 7,000 US public companies
Best for: Enterprise sales, strategic accounts, identifying active vendor evaluation cycles

Contact Sales →

See real delivered data → Sample Files

Example Signal

Field Reference

Signal-Specific Fields

Timing & Delivery

Coverage