System map & technical breakdown — the version with all the tool names in it.
Companion pieces: Document 1 (internal proposal, .docx) · public deck (deck-public/ — the one PE sees).
rclone-class job on SolvServer, checksummed). Drive stays the friendly front door; NAS is the archive of record.yt-dlp + queue). Everything joins the same library with source metadata.| Channel | PE | 20VC | YC |
|---|---|---|---|
| X | 5,478 | 522K (Harry) | 1.62M |
| ~26.5K | ~270K (Harry) · 32.7K (co. page)* | ~1.73M | |
| YouTube | 34 | 214K | 2.3M |
| TikTok | — | 268K | 70K |
| — | 157K | ~671K |
*20VC LinkedIn resolved 10 Jul 2026: company page = 32,670 (live scrape of linkedin.com/company/20vc og:description); the old 8,924 snapshot matches no 20VC entity — treat as bogus. All counts 10 Jul 2026.
The examples in the public deck aren’t a promise — they’re output. Same pipeline, pointed at Year 2.
Other watch-items: attribution is genuinely hard (only 37% of marketers find social→outcome linkage easy — hence UTM + application question from day one) · X hides view counts from tools (need native analytics access) · TryPost is a young OSS project (mitigation: open source + exportable data; $12/mo hosted tier; Postiz evaluated as drop-in fallback).
Costs: infra mostly owned; incremental = VPS (~€10–30/mo) + CDN by volume + Higgsfield/Suno credits. Commercials handled separately — not in these docs (James, 10 Jul). Table in Document 1 §9.
Move the numbers live with the client. defaults — adjust in the room