One roster per platform · Sized to the buyer · 150 entries
One mixed list isn’t enough — and neither is forcing a round 100 onto every platform. The buyer here is a corp-dev / PE / operator who reads business surfaces, not dev channels. So each roster is sized to where he actually is: a deep 100 on X (analysts, SaaS-metrics, PE/M&A, deals-media, market-map), a focused ~30 on Reddit, and a deliberately thin, read-only awareness map on Hacker News — because HN is a builder surface, not his.
These extend the master list at /target-list into platform-specific rosters. Each entry is status-flagged with the same scheme used everywhere else — engage, watch, hold, read, blocked — so the page reads as a working attention map, not a wishlist. We don’t pad a roster to a round number; honest audience-fit beats a tidy 100.
Anonymity rule, restated: every entry is a public surface — a subreddit, a category page, a public account. We don’t name individuals we track inside the paid product. That’s the buyer’s edge, not ours to publish.
Start with the highest-intent routes
Use voices when you want the platform-specific attention map. But if your real question is proof, workflow, or buyer-side clarity, start with the sharper pages first.
/voices/twitter
100 entries100 X accounts that hold Marcus's attention — analysts, SaaS-metrics, PE/M&A, deals-media, market-map.
X is where Marcus reads. Not dev Twitter — the business-of-tech analysts, SaaS/cloud-metrics voices, PE/M&A operators, deals journalists, and market-map analysts he uses to decide who's worth a meeting. We engage the data desks and benchmark voices with a complementary, translated data point; we monitor the analysts and reply only when one plain-English signal genuinely fits. Never raw commits, never quant jargon.
Open the roster →
/voices/reddit
30 entries~30 business, PE, SaaS, and finance communities where corp-dev and operator buyers actually read.
Marcus is thinner on Reddit than on X, and he is NOT in the dev subs the old avatar lived in. This is the buy-side neighborhood — PE, venture, corp-dev/finance, SaaS-business, and the sectors he evaluates. Engagement is comment-only and rare: the finance and VC subs auto-remove anything that names a product, so we comment with a translated data point on a real question or we just read.
Open the roster →
/voices/hacker-news
20 entriesA thin, read-only awareness map — HN is a builder surface, not Marcus's home.
Honest framing: Hacker News is a builder/founder crowd, not where corp-dev / PE / non-engineer-VP buyers live. We don't pretend Marcus is here. This short roster is read-only ground truth — fundraise, M&A, hiring-wave, and sector-heat threads that confirm whether the engineering signal preceded the round. No engagement layer, no padding to 100.
Open the roster →
Why split the master list
The same reader may use X in the morning, Reddit at lunch, and HN before bed. But the platforms reward and punish very different posting shapes. Reddit auto-mods anything that names a product on the venture-side subs. HN front-page mechanics don’t tolerate self-promotion at all. X rewards consistency more than quality. Each surface needs its own list, its own cadence, and its own honest engagement status — which is why one big mixed roster misses the point.
The companion list at /target-list stays as the ICP-scored master roster across publication formats (substacks, podcasts, newsletters, GitHub orgs, conferences, books, frameworks, communities, LinkedIn pages, datasets). The three rosters here are platform-shape-specific extensions of that map, ready for the engagement layer.
How this list compounds
Every Tuesday and Friday at 14:00 EEST, the company-side surfaces cycle through the engage-tagged entries on each platform — Reddit comments first, X queue second, HN read-only third. The hard ceilings (4 LinkedIn replies / week, 2 Reddit comments / week, 0 HN posts during the account-block window) come from each platform’s rules, not ours.
We publish the rosters because every dispatch is reproducible from this page. If you want to mirror the cadence, three Tuesday-and-Friday hours per week is the entire workload.
Refreshed 2026-05-09. Each roster is regenerated quarterly. Status flags update weekly when engagement state changes (e.g. account block resolves, auto-mod rule changes, a sub goes private).