VC Portfolio Change Monitor — What Changed Since Last Run
Pricing
from $100.00 / 1,000 portfolio change records
VC Portfolio Change Monitor — What Changed Since Last Run
Monitors VC firm portfolio pages and returns what changed since the last run — companies added, removed, or edited — for a16z, Sequoia, Founders Fund, Greylock, Bessemer, Index, Lightspeed, or any portfolio URL. Schedule it and get a clean change feed.
Pricing
from $100.00 / 1,000 portfolio change records
Rating
0.0
(0)
Developer
NexGenData
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
8 days ago
Last modified
Categories
Share
Stop re-scraping whole VC portfolios to find the handful of changes. This monitor diffs each firm's portfolio page against its previous run and returns only the delta — companies added, removed, or edited — as clean change records you can schedule, pipe into a CRM, or hand to an AI agent.
Point it at a16z, Sequoia, Founders Fund, Greylock, Bessemer, Index, and Lightspeed (all seeded), or any portfolio URL. Built for VC associates, competitive-intelligence teams, biz-dev, and recruiters who need to know the moment a fund's book moves — not to re-read 800 companies every week.
⏱ Made to run on a schedule
The core value is "what changed since last run." Each run stores a per-URL snapshot; the next run compares against it and emits only the differences. Put it on an Apify schedule (daily/weekly) and each run is a tidy change feed. The first run on each firm is a baseline capture — it stores the current portfolio and emits every company as added (this is expected and honest; deltas start from run two).
💵 Pricing — pay per change record
- Portfolio change record — $0.10 (the value event: one added/removed/modified company).
- Actor start — $0.00005 (nominal).
- $1 ≈ 10 change records. On steady-state runs a portfolio moves by a few companies, so ongoing runs are cheap; the one-time baseline run emits more (one record per current company) — budget for it on the first run of each firm.
📦 Output — field table (from a real run on Founders Fund)
| field | example | notes |
|---|---|---|
firm | Founders Fund | firm name derived from the URL |
firm_url | https://foundersfund.com/portfolio/ | the page monitored |
company | SpaceX | portfolio company name |
change_type | added | added · removed · modified |
baseline | true | true on a URL's first (baseline) run |
before | null | prior state (null for added/baseline) |
after | {"name":"SpaceX","url":null,"description":null} | new state (null for removed) |
detected_at | 2026-07-06T06:20:00Z | UTC run timestamp |
Real companies captured on the Founders Fund baseline run include SpaceX, Palantir, Anduril, and Stripe.
🤖 Use with AI agents
The change feed is agent-ready. Example prompts:
- "Run vc-portfolio-page-monitor on my 7 seeded funds and tell me which companies were added this week."
- "Diff today's run against last week and draft an outreach note for each newly-added Founders Fund company."
- "Watch these 3 competitor VC portfolios daily and alert me when any company is removed (a possible exit or failure signal to research)."
Pair it with an LLM step to summarize the delta into a Slack digest, or push added records straight into your CRM.
🔗 Related NexGenData actors
Portfolio scrapers (full snapshot of one firm): a16z · Sequoia · Founders Fund · Greylock · Bessemer · Index · Lightspeed Funding cluster: Startup Funding Tracker — new funding rounds across the market. Use the portfolio scrapers for a full company list; use this monitor to track how that list changes over time.
⚠️ Honest capability & coverage caps
- This is a records / monitoring tool. It reports observed changes to public portfolio pages. It does not provide investment signals, alpha, edge, or recommendations, and change records are not predictions.
- Coverage depends on how a firm publishes its portfolio. Firms that render their portfolio in server HTML are fully captured (e.g. Founders Fund, Greylock, a16z-partial). Pure client-side (JavaScript-only) portfolios — currently Sequoia, Bessemer, Lightspeed, Index — return only their static shell to a plain HTTP fetch, so those runs are deterministic but may track few or no companies until a browser-rendered variant is enabled. Extraction is deterministic run-to-run, so it never invents false changes; it can only miss ones on JS-only pages.
description/statusedit detection is best-effort and depends on the field being present in the page markup.