Last10K Workflow Upgrade: From Batch Downloads to Streaming Filing Alerts

Last10K carved out a niche for fundamental analysts who live in Excel. You can pull every 10-K, 10-Q, 8-K, and press release, screen for custom ratios, and export clean tables to CSV. Their API lets you fetch historical filings, fundamentals, and news into your own warehouse. It’s perfect for end-of-day model updates.

But research desks that camp on Last10K still end up running manual refreshes to see what just hit EDGAR. This guide shows how to keep Last10K for deep fundamentals while layering Earnings Feed on top for real-time monitoring.

Strengths to keep from Last10K

• Comprehensive filings archive. Every SEC form is indexed with issuer profiles, historical fundamentals, and PDF links.
• Ratio screeners. Quickly sort for revenue per employee, EV/Sales, or cash flow coverage without touching SQL.
• API + Excel downloaders. The developer portal exposes filings, key stats, and even transcripts for bulk ingestion.

Where the gaps appear

1. Polling vs. streaming. Even with the API, you need to cron a job that polls /filings or /alerts endpoints. You still discover a 13D hours after it landed unless you tighten the schedule.
2. Collaboration. Downloads end up in shared drives. There’s no Slack-ready payload that tags the company, form, and call-to-action in one clickable card.
3. Dossier context. After fetching the PDF you still have to answer “what else do we know about this issuer?” Earnings Feed surfaces transcripts, holders, filings, and dispersion data in one dossier.

Hybrid setup for Last10K power users

Need	Keep using Last10K for	Let Earnings Feed handle
Archival pulls	Historical 10-K/10-Q downloads, fundamentals, Excel exports	Real-time ingestion, normalized metadata, watchlists
Screening	Pre-built ratio filters, quant tables	Event-driven filters (form type, stakeholder, free text)
Distribution	API to warehouse, CSV to Excel	Slack + email alerts, webhook payloads, shareable packets

Implementation steps

1. Define critical entities. Choose the 50–100 issuers where a filing requires an immediate response. Create watchlists in Earnings Feed that mirror your Last10K folders.
2. Wire Slack + webhooks. Subscribe each watchlist to a Slack channel or webhook. Every alert includes the issuer name, ticker, form, timestamps, accession number, and dossier link.
3. Mirror into your warehouse. Use the webhook payload as the trigger for your ETL. When an alert fires, fetch the full filing or supplemental data from Last10K’s API so your historical store stays in sync.
4. Backtest your gap. Compare timestamps: Slack alert vs. when your Last10K polling job found the filing. Most teams see a delta of 30–90 minutes, especially for 8-Ks that land outside RTH.

Bonus: transcript + ownership pairing

Last10K hosts earnings call transcripts and institutional ownership snapshots. Combine that with Earnings Feed’s live filings feed to create a single “issuer dossier” page:

1. Slack alert fires for a new 13D/A.
2. Analyst clicks the dossier link to see the holding delta, quick valuation tables, and linked transcripts.
3. Notebook automatically pulls the Last10K transcript via API for additional color.

The result? No more shuffling between Last10K downloads, RSS scrapers, and inbox pings. You keep the models you’ve already built on Last10K’s data while letting Earnings Feed take over the “what just happened” loop.