../PLAN.md. Downstream: each row’s page gets the video embedded in its
video: front-matter and a > 🎥 **Video:** slot (per ../CONVENTIONS.md). Part 2 pages with no
existing video are listed separately as shot-list candidates.
Page ids are from ../PLAN.md §4 (Part 2 sections 2.0–2.6, Part 3). “Maps to page(s)” gives the
primary page first, then secondary pages the same video also serves via cross-link.
1. Existing videos → pages
| Video | URL | Maps to page(s) | Notes |
|---|---|---|---|
| Branded CTA & featured images | https://youtu.be/lfV72h8kwDE | 2.1.6 | Given mapping; PLAN already tags 2.1.6 with this id. Primary embed. |
| Post-production refiners (blog publish-ready) | https://youtu.be/5gppErb1Yrk | 2.1.7, 2.4.3 | Given mapping; one video serves both — setup-side (2.1.7 “Set up refiners”) and use-side (2.4.3 “Run refiners to get publish-ready”). PLAN tags both with this id. Embed on both; 2.4.3 is where an operator actually runs them. |
| Conversion tracking on PostHog | https://www.loom.com/share/2d9bc938ae4641bf9a29f84aaef33606 | 2.1.4, 2.6.1 | Primary = 2.1.4 (Connect PostHog); PLAN tags 2.1.4 “Loom: conversion tracking”. Also supports 2.6.1 (PostHog dashboard / conversion funnels). |
| Handle link-exchange inbound with a proposal | https://www.loom.com/share/3b2ad3f95ec441c2857e7e9e0dcedb17 | 2.5.5 | Direct match — PLAN 2.5.5 “Handle an inbound link-exchange proposal 🎥”. |
| Prepare a good client review | https://www.loom.com/share/2faf469c941d4739870e68a1b632f2b9 | 3.7, 3.8 | Primary = 3.7 “Preparing client-review material”; also supports 3.8 “Running the client review” (both tagged 🎥 in PLAN). Part 3 (AM-only). |
| Kick off link building with a search term | https://www.loom.com/share/673461eea1e843788abe83632ae77b00 | 2.5.4, 3.9 | Primary = 2.5.4 “Link-building kickoff from a search term”; also the concrete demo for the 3.9 Link-building SOP. |
| Generate landing page that reads SERP + existing pages | https://www.loom.com/share/fe54e4e9737f452587c00ae1b624b3df | 2.3.2 | Direct match — PLAN 2.3.2 “Generate LPs that read the SERP + existing pages 🎥”. |
| Edit (manually & with AI) generated articles | https://www.loom.com/share/adaeb6d1c02140ecaa876a4bda6f273d | 2.4.2 | Direct match — PLAN 2.4.2 “Edit articles — manually & with AI 🎥”. |
| Edit & prepare guest post articles | https://www.loom.com/share/838dcdd64e20430ab18610a4f292777f | 2.4.4 | Direct match — PLAN 2.4.4 “Prepare guest-post articles 🎥”. |
| Edit/align landing page prompt from user changes | https://www.loom.com/share/813a44552d914da28b85e1c703826a5c | 2.3.3 | Direct match — PLAN 2.3.3 “Align/adjust a pillar prompt from client feedback 🎥”. |
| Build keyword report to plan the month | https://www.loom.com/share/36ecdf926fc24d35801820d2469a3993 | 2.2.4, 3.2 | Primary = 2.2.4 “Build the monthly look-ahead keyword report”; also the demo for 3.2 Monthly planning flow. |
| Press release for a client (Hyperbound) | https://www.loom.com/share/e15b6efc7e13450a8e7fac43ebad96c1 | 2.5.6, 3.10 | Primary = 2.5.6 “Press release for a quick bump” (PLAN notes the Hyperbound example); also the demo for 3.10 Press-release SOP. |
| Keyword research (how you can do it) | https://www.loom.com/share/1df8e07643d84aa68908b5f5ca054510 | 2.2.1 | Primary = 2.2.1 “Keyword exploration” (PLAN: “Keyword Explorer Loom”). |
| Keyword init with new keyword dashboard | https://www.loom.com/share/c1dec23c188c4f068855dcec9fcf8e74 | 2.2.1, 3.11 | Shows initializing keywords in the new dashboard UI. Primary = 2.2.1 (exploration/init surface); also supports 3.11 “First set of keywords (kickoff)”. Two videos land on 2.2.1 — use “Keyword research” for the method, this one for the dashboard walkthrough. |
| Organize & file keyword within synscribe | https://www.loom.com/share/27d277d3d9f24a0fa146531cff8ddb7f | 2.2.3, 3.4 | Primary = 2.2.3 “Organise, tag & file keywords in Synscribe” (PLAN: “Loom: organize/file keyword”); also the demo for 3.4 Organise-keywords-for-a-cycle SOP. |
| Setup IndexNow for Framer website | https://www.loom.com/share/9b35f66f85d04bc79776c68c3f63faf9 | 2.1.5 | Direct match — PLAN 2.1.5 “Configure publishing platform + IndexNow (Loom: IndexNow for Framer)”. Framer-specific; a non-Framer host may need its own beat. |
| Setting up Attribution for Client | https://www.loom.com/share/3e2d0ab899fc484fae95bdc400b687ee | 2.6.2 | Direct match — PLAN 2.6.2 “Set up client attribution 🎥”. |
| How to design high converting website | https://www.loom.com/share/c3109d31110042758383b377faa2562a | 2.3.1, 1.6, 1.3 | Judgment call. Closest how-to home = 2.3.1 “Design a landing-page pillar” (conversion-oriented LP design). It also illustrates Part 1 theory: 1.6 (LP pillars horizontal/vertical) and the BOFU/conversion thesis in 1.3. Embed on 2.3.1; cross-link from 1.6. Partially covers the 2.3.1 shot-list gap below. |
| Setting up Blog part 1 | https://www.loom.com/share/731eb1d7b732450dac3b1013cfe9665e | 2.4.1 | PLAN maps “Loom: setting up blog” to 2.4.1 “Write content”. Two-part; part 1 = the setup/first-write half. ❓ [needs Raymond: confirm “setting up blog” is the writing flow (2.4.1) and not publishing-platform setup (2.1.5 / 2.5.1)]. |
| Setting up Blog part 2 | https://www.loom.com/share/a9cdaccfb7d743e48c8c896aa8331760 | 2.4.1 | Continuation of the above; embed both parts on 2.4.1 in order. Same ❓ as part 1. |
| Refill content | https://www.loom.com/share/0a0d767702b54e77875dc4cd65e821bc | 3.5, 2.4.1 | Judgment call. Reads as replenishing the content pipeline/queue when it runs low → operational cadence, so primary = 3.5 “Content production procedures + DoD”; also supports 2.4.1. ❓ [needs Raymond: confirm “refill content” = topping up the content pipeline vs a specific UI action]. |
2. Part 2 pages with NO existing video — shot-list candidates
Every Part 2 page below has no matching video in the library. Priority order per PLAN §7: self-serve orientation (2.0.x) + setup (2.1.x) first. Copy these rows into../video-shot-list.md.
| Priority | Page | The one task the video shows | Beats | Est. length |
|---|---|---|---|---|
| 1 | 2.0.1 The app in 5 minutes | A first-run tour of the app so a new operator isn’t lost | 1) sidebar + what each section is · 2) the org concept · 3) where the Pi Agent lives · 4) where work shows up | 4–5 min |
| 1 | 2.0.2 Working across clients | Switch orgs and keep client work separate across tabs | 1) org switcher · 2) per-tab org pinning · 3) confirming which client you’re acting on · 4) common mix-up to avoid | 3–4 min |
| 1 | 2.0.3 Driving Pi well | Send Pi a good task and manage the Agent Inbox / sessions | 1) anatomy of a good prompt · 2) the Agent Inbox · 3) sessions + sharing a session · 4) when Pi asks to confirm | 4–5 min |
| 1 | 2.0.4 Filing work in Pi’s VFS | Ask Pi to save/file work into the right place (see vfs-conventions.md) | 1) /memory/ as the canonical store · 2) MEMORY.md index + SOUL/IDENTITY · 3) asking Pi to “save this to /memory/…” · 4) reading it back later | 4–5 min |
| 1 | 2.1.1 Create the org & initialize Pi | Create a new org and run Pi’s onboarding (memory + soul) | 1) create org · 2) trigger bootstrap · 3) name/vibe/soul conversation · 4) confirm IDENTITY/SOUL/MEMORY seeded | 4–6 min · already 🎬 in PLAN |
| 1 | 2.1.2 Company research & the Product Bible | Run company-explorer and produce the Product Bible | 1) kick off company research · 2) what it pulls · 3) Pi writes /memory/{account}-product-bible.md · 4) review + correct | 4–5 min |
| 1 | 2.1.3 Connect Google Search Console | Connect a client’s GSC and pick the property | 1) start GSC connect · 2) OAuth · 3) select the property (incl. URL-prefix) · 4) confirm data flowing | 3–4 min · already 🎬 in PLAN |
| 2 | 2.2.2 Evaluate + SERP-cliff a batch | Run a keyword batch through evaluation + the SERP-cliff “can we win?” gate | 1) select a batch · 2) run evaluation · 3) read the SERP-cliff signal · 4) keep/cut decision | 4–5 min |
| 2 | 2.3.1 Design a landing-page pillar | Design a pillar’s schema + prompt (ASCII wireframe) | 1) pick pillar type (horizontal/vertical) · 2) sketch the wireframe · 3) write the prompt/schema · 4) validate before generating | 5–6 min · partially covered by “How to design high converting website” — record the schema/prompt half only |
| 2 | 2.3.4 Export a pillar & wire to the site | Export a pillar (JSON for code sites, CSV for CMS) and wire it up | 1) choose export format · 2) export · 3) drop into code site / CMS · 4) verify live | 4–5 min · ❓ export formats unconfirmed in PLAN |
| 2 | 2.3.5 Landing-page refiners / compliance edits | Run the LP refiners for schema-safe compliance edits | 1) open the LP · 2) run refiner · 3) review the surgical edit · 4) confirm no data wipe | 3–4 min |
| 2 | 2.3.6 Convert a video → vertical landing page | Turn a video into a vertical LP | 1) supply the video · 2) generate the vertical LP · 3) refine · 4) publish | 3–4 min · SOP exists |
| 3 | 2.5.1 Publish & set the live URL | Publish a page/post and set its live URL | 1) publish action · 2) set/confirm live URL · 3) verify it resolves · 4) common pitfalls | 2–3 min |
| 3 | 2.5.2 Technical SEO audit | Run account-quality-control and read the checklist | 1) run the audit · 2) walk the checklist · 3) triage findings · 4) fix loop | 4–5 min |
| 3 | 2.5.3 Index on GSC + submit sitemap (+ Bing) | Push a new URL for indexing and submit the sitemap | 1) request indexing on GSC · 2) submit/refresh sitemap · 3) Bing submit · 4) confirm pickup | 3–4 min |
| 3 | 2.6.3 Reconcile GSC + PostHog into a performance review | Combine GSC + PostHog into one performance review | 1) pull GSC · 2) pull PostHog · 3) reconcile (AI traffic + pillar conversion) · 4) write the review | 4–5 min |
Notes on partial coverage: 2.3.1 and 2.6.1 each have a video that touches them (“How to design high converting website” and “Conversion tracking on PostHog” respectively) but not the exact task — 2.6.1 (PostHog dashboard setup) is treated as covered-enough by the conversion-tracking Loom for now; 2.3.1 still needs a schema/prompt-focused recording. Flag both for Raymond if he wants dedicated recordings.