> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synscribe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Master plan

> The build plan for the Synscribe training and SOP site.

**Status:** draft plan for review · **Branch:** `docs/account-manager-training` · **Owner:** Raymond
**Last updated:** 2026-07-04

This is the build plan for a searchable, video-accompanied documentation site. It is the
control document for the \~10-hour autonomous build that follows. Read the **Open Decisions**
at the bottom first — a couple of forks are yours to call before I start.

***

## 1. Goal & audiences

Two jobs, one site:

| # | Audience                                                                               | What they need                                                                                    | Primary parts   |
| - | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | --------------- |
| A | **Account managers onboarding** (internal + agency partners), starting \~week of Jul 7 | A training curriculum + SOPs they can run accounts from, at scale, consistently                   | Parts 1 + 2 + 3 |
| B | **Direct-to-subscriber self-serve users** (future product opening)                     | A guided tour so they aren't "lost at best" — the *why* and the *how*, minus the agency-scale ops | Parts 1 + 2     |

The site is written so a single page serves both where possible, with **audience tags**
(`For AMs` / `For self-serve`) where the guidance diverges — rather than maintaining two sites.

**Audience model (resolved):** self-serve subscribers can touch **everything** — the difference
is not capability, it's **discipline and standardization**. Agency/internal AMs run the rigorous,
repeatable version at scale (checklists, quality gates, cadence); self-serve users get the same
tools with a lighter-weight path. So audience tags mostly mean "here's the disciplined version
(AM)" vs "here's the quick version (self-serve)", **not** "you can't do this."

**Never mention credits/credit units** anywhere in the docs. We are moving off that model;
describe throughput and cadence in concrete terms (pages, posts, weeks) with no credit language.

## 2. The three parts (the user's structure)

1. **Part 1 — Theory & the Synscribe way of SEO.** Not a regurgitation of generic SEO advice.
   It codifies *what we do differently* and *why*: programmatic SEO + GEO (AI-answer-engine
   optimization) for SaaS, SERP-cliff-first keyword selection, BOFU-first, speed-to-rank, and
   agent-operated execution. This is the layer that makes the how-tos make sense.
2. **Part 2 — Doing it on the platform.** Step-by-step micro-guides, one task per page, each
   with a video where one exists (or is planned). The literal button-by-button.
3. **Part 3 — SOPs for running accounts at scale.** The operating procedures for internal AMs
   and agency partners: onboarding, monthly/weekly cadence, quality gates, client reviews,
   roles & handoffs, capacity/credit planning.

## 3. Design principles for the site

* **One page = one micro-guide.** Small, searchable, linkable. A page should be readable in
  2–4 minutes and answer exactly one "how do I…" or "why do we…".
* **Video-first where it helps.** Every task page has a slot for a video. Some already exist
  (Loom library + 2 YouTube); the rest go on a **shot-list** for Raymond to record.
* **Real prompts, real examples.** The platform is agent-operated, so the "how" is often *a
  prompt you send Pi*. We lift **real operator prompts from production chats** (via the
  `prod-context` skill) rather than inventing them — copy-paste-ready, lightly anonymized.
* **Grounded, not aspirational.** If a feature isn't live, it's not taught as if it is (e.g.
  the guardrail's real publish-blocking vs. its stale settings copy). Code + prod win over docs.
* **Progressive disclosure.** Part 1 gives the model; Part 2 the mechanics; Part 3 the cadence.
  Cross-linked so a reader can drop from "why" straight to "how."

***

## 4. Full site map

Legend for per-page status (filled during the build):
`✍️ draftable now` · `🎥 video exists` (Loom/YT to embed) · `🎬 needs video` (shot-list) ·
`❓ needs Raymond` (knowledge gap) · `🔬 mine from prod chats`

### Part 1 — Theory & the Synscribe Way

| Page                                                                            | Notes / source                                                                              |
| ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| 1.1 The Synscribe thesis: programmatic SEO + GEO for SaaS                       | ✍️ — I draft the positioning vs. blog-mills/agencies (Raymond reviews); mine Workshop Notes |
| 1.2 Two search surfaces now: Google **and** AI answer engines                   | ✍️ — GEO; why we track ChatGPT/Perplexity/Claude/Gemini referrals                           |
| 1.3 The atomic unit: keyword → page, and why we start **BOFU**                  | ✍️ — bottom-of-funnel landing pages before TOFU                                             |
| 1.4 SERP cliff analysis — our "can we actually win this?" method                | ✍️ 🎬 — the core differentiator vs. volume/KD chasing (Organise-Keyword SOP has the model)  |
| 1.5 Intent & cannibalization discipline (one keyword ≠ always one page)         | ✍️ — survival gates, signal hierarchy                                                       |
| 1.6 Landing-page **pillars**: horizontal (`/uses`) vs vertical (`/feature`)     | ✍️ — programmatic scale model                                                               |
| 1.7 Speed-to-rank: the new-domain playbook (5–10 pages, pos 1–5, in 2 weeks)    | ✍️ — I draft the "quick win" theory (Raymond reviews)                                       |
| 1.8 Authority & internal linking (hub/spoke, footer links)                      | ✍️ 🔬 — "How to build strong internal links" SOP                                            |
| 1.9 Off-page: link building & press for the bump                                | ✍️ 🎥 — Loom library                                                                        |
| 1.10 Attribution that matters: AI traffic + pillar-level conversion, not vanity | ✍️ — PostHog philosophy from Onboarding SOP                                                 |
| 1.11 Quality as a gate: our Definition of Done                                  | ✍️ — from Quality Gate + DoD SOPs                                                           |
| 1.12 Agent-operated SEO: why an AI assistant changes the operating model        | ✍️ — I draft the Pi thesis / where the leverage is (Raymond reviews)                        |

### Part 2 — Doing it on the platform (micro-guides)

**2.0 Orientation**

| Page                                                                 | Status                            |
| -------------------------------------------------------------------- | --------------------------------- |
| 2.0.1 The app in 5 minutes: sidebar, orgs, the Pi Agent              | ✍️                                |
| 2.0.2 Working across clients (org switch, per-tab pinning)           | ✍️                                |
| 2.0.3 Driving Pi well (prompts, the Agent Inbox, sessions & sharing) | ✍️ 🔬                             |
| 2.0.4 Filing work in Pi's VFS (`/reports/`, memory, soul)            | ❓ 🔬 — confirm folder conventions |

**2.1 Account setup**

| Page                                                            | Status                            |
| --------------------------------------------------------------- | --------------------------------- |
| 2.1.1 Create the org & initialize Pi (memory + soul)            | ✍️ 🎬                             |
| 2.1.2 Company research (`company-explorer`) & the Product Bible | ✍️ 🔬                             |
| 2.1.3 Connect Google Search Console                             | ✍️ 🎬                             |
| 2.1.4 Connect PostHog (or Mixpanel)                             | ✍️ 🎥 (Loom: conversion tracking) |
| 2.1.5 Configure publishing platform + IndexNow                  | ✍️ 🎥 (Loom: IndexNow for Framer) |
| 2.1.6 Set up the branded image generator                        | 🎥 **YouTube: lfV72h8kwDE**       |
| 2.1.7 Set up refiners (brand / CTA / FAQ / TLDR)                | 🎥 **YouTube: 5gppErb1Yrk**       |

**2.2 Keywords & planning**

| Page                                              | Status                              |
| ------------------------------------------------- | ----------------------------------- |
| 2.2.1 Keyword exploration (DataForSEO/Ahrefs/web) | ✍️ 🎥 🔬 (Keyword Explorer Loom)    |
| 2.2.2 Evaluate + SERP-cliff a batch               | ✍️ 🔬                               |
| 2.2.3 Organise, tag & file keywords in Synscribe  | 🎥 🔬 (Loom: organize/file keyword) |
| 2.2.4 Build the monthly look-ahead keyword report | 🎥 (Loom: keyword report)           |

**2.3 Landing pages**

| Page                                                                        | Status                                    |
| --------------------------------------------------------------------------- | ----------------------------------------- |
| 2.3.1 Design a landing-page pillar (schema + prompt, ASCII wireframe)       | ✍️ 🔬 (Landing Page Prompt Alignment SOP) |
| 2.3.2 Generate LPs that read the SERP + existing pages                      | 🎥 (Loom)                                 |
| 2.3.3 Align/adjust a pillar prompt from client feedback                     | 🎥 (Loom)                                 |
| 2.3.4 Export a pillar (JSON for code sites, CSV for CMS) & wire to the site | ✍️ ❓                                      |
| 2.3.5 Landing-page refiners / compliance edits                              | ✍️                                        |
| 2.3.6 Convert a video → vertical landing page                               | 🔬 (SOP exists)                           |

**2.4 Blog content**

| Page                                                   | Status                        |
| ------------------------------------------------------ | ----------------------------- |
| 2.4.1 Write content (auto-research / deep / technical) | ✍️ 🎥 (Loom: setting up blog) |
| 2.4.2 Edit articles — manually & with AI               | 🎥 (Loom)                     |
| 2.4.3 Run refiners to get publish-ready                | 🎥 **YouTube: 5gppErb1Yrk**   |
| 2.4.4 Prepare guest-post articles                      | 🎥 (Loom)                     |

**2.5 Publish & distribute**

| Page                                                  | Status                                 |
| ----------------------------------------------------- | -------------------------------------- |
| 2.5.1 Publish & set the live URL                      | ✍️                                     |
| 2.5.2 Technical SEO audit (`account-quality-control`) | ✍️ 🔬 (checklist in Onboarding SOP)    |
| 2.5.3 Index on GSC + submit sitemap (+ Bing)          | ✍️                                     |
| 2.5.4 Link-building kickoff from a search term        | 🎥 (Loom)                              |
| 2.5.5 Handle an inbound link-exchange proposal        | 🎥 (Loom)                              |
| 2.5.6 Press release for a quick bump                  | 🎥 🔬 (Loom + SOP; Hyperbound example) |

**2.6 Analytics & review**

| Page                                                                    | Status                                  |
| ----------------------------------------------------------------------- | --------------------------------------- |
| 2.6.1 PostHog dashboard setup (AI-traffic insight + conversion funnels) | 🎥 🔬 (Loom + SOP; SQL snippet in hand) |
| 2.6.2 Set up client attribution                                         | 🎥 (Loom)                               |
| 2.6.3 Reconcile GSC + PostHog into a performance review                 | ✍️ 🔬                                   |

### Part 3 — SOPs for running accounts at scale

| Page                                                                                  | Source                                                                                          |
| ------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| 3.1 Onboarding Flow — Month 1 (the backbone)                                          | Port + enrich existing SOP-7 (already excellent)                                                |
| 3.2 Monthly planning flow                                                             | SOP "Flow for Monthly Planning" 🔬                                                              |
| 3.3 Weekly planning flow                                                              | SOP "Flow for weekly planning" 🔬                                                               |
| 3.4 Organise keywords for a cycle                                                     | Port SOP-4 (already excellent, prompt-rich)                                                     |
| 3.5 Content production procedures + Definition of Done                                | SOP "Content Production" + "DoD for Content"                                                    |
| 3.6 The Quality Gate                                                                  | SOP "Quality Gate"                                                                              |
| 3.7 Preparing client-review material                                                  | SOP "Preparing Client Review Material" 🎥                                                       |
| 3.8 Running the client review                                                         | Client Review SOP 🎥                                                                            |
| 3.9 Link-building SOP                                                                 | 🔬                                                                                              |
| 3.10 Press-release SOP                                                                | "Press Release for a Quick Bump"                                                                |
| 3.11 First set of keywords (kickoff)                                                  | "How to start first set of keywords"                                                            |
| 3.12 Playbook for API & MCP servers                                                   | SOP exists                                                                                      |
| 3.13 One Startup A Day launch                                                         | SOP exists                                                                                      |
| 3.14 Roles & handoffs — AM vs BPO publishing (YiAn/#bpo), human-only tools            | ✍️ — from Onboarding SOP                                                                        |
| 3.15 Agency partners & standardization at scale (the rigor delta, not gated features) | ✍️ — self-serve can do everything; agency = disciplined, standardized, repeatable at scale      |
| 3.16 Capacity & cadence planning (throughput in pages/posts per week)                 | ✍️ — **no credit language**; describe cadence concretely (e.g. blogs/week, LP batches per week) |

***

## 5. Source ledger (what feeds the build)

* **Workshop Notes** (Notion, 69k chars) — Part 1 philosophy backbone. *To be mined in Phase 1.*
* **SOP database** (Notion) — Part 3 backbone; several are already high quality (Onboarding
  Month 1, Organise Keyword). Port + normalize, don't rewrite what's already sharp.
* **Loom library** (\~20 videos, catalogued from the SOP page) + **2 YouTube** how-tos — embed map.
* **Client dossiers** (Wonderchat, Hyperbound) — real worked examples for Part 1/3 case studies
  and Part 2 illustrations (pillar design, competitor mining, BOFU strategy).
* **Production operator chats** via `prod-context` (`factory session`/`messages`) — real prompts
  and *longitudinal* patterns (how the same operator handles a cycle over months). Feeds the
  copy-paste prompt blocks throughout Part 2 & the "what good looks like" in Part 3.
* **Codebase** (already mapped) — surfaces, routes, skills, integrations; keeps the how-tos honest.
* **Existing repo training docs** (`docs/training/account-manager/*`) — my earlier product map;
  fold in / supersede.

***

## 6. The 10-hour phase plan

Each phase has a **mini-goal** (the acceptance check) and a concrete deliverable. Phases are
ordered so the site is usable even if we stop early (index + Part 3 SOPs land first, since
those are what next week's AMs need most).

### Phase 0 — Scaffold & decide (≈0.75h)

* Stand up the doc-site skeleton (tooling per Open Decision #1), nav for the 3 parts, search,
  a video-embed component, and the audience-tag convention.
* **Mini-goal:** site builds locally; a placeholder page renders with an embedded video and is
  searchable.

### Phase 1 — Mine the sources (≈2h) *(runs as parallel subagents)*

* Mine Workshop Notes → a distilled "Synscribe SEO principles" outline for Part 1.
* Mine `prod-context` operator chats (3–5 exemplary sessions across a couple of orgs, over
  time) → a **real-prompt library** tagged by task, + patterns for Part 3.
* Catalogue every Loom/YouTube → an **embed map** (video ↔ page).
* Confirm VFS filing conventions (folders, memory, soul).
* **Mini-goal:** a `_sources/` folder with (a) principles outline, (b) prompt library, (c) video
  embed map, (d) VFS conventions note — every downstream page has its raw material staged.

### Phase 2 — Part 3 SOPs (≈2h) *(first, because next week needs it)*

* Port + normalize the existing SOPs into micro-guides; fill the gaps I can; flag the rest.
* **Mini-goal:** all 16 Part 3 pages exist; the 4 already-strong SOPs are fully ported;
  `❓` pages have a clear "what I need from you" stub.

### Phase 3 — Part 2 platform how-tos (≈2.5h)

* Write every task page: steps + real prompt block + embedded video (or 🎬 shot-list stub).
* **Mini-goal:** all Part 2 pages exist; every page with an existing video has it embedded;
  every video-less page has either full written steps or a shot-list entry.

### Phase 4 — Part 1 theory (≈2h)

* Write the differentiated-SEO chapters from the mined principles + client examples.
* **Mini-goal:** all 12 Part 1 pages drafted; each states a *distinct* Synscribe stance (not
  generic SEO), with a real example; `❓` positioning nuances flagged for Raymond.

### Phase 5 — Assemble, cross-link, gap register, shot-list (≈0.75h)

* Home page + learning paths ("New AM start here", "Self-serve tour"); cross-links between
  parts; the consolidated **knowledge-gap register** and **video shot-list** as their own pages.
* **Mini-goal:** a coherent, navigable, searchable site; every gap and every needed video is
  itemized in one place for Raymond to action.

**Buffer (≈0.25h):** commit hygiene, a build check, and a written hand-off summary.

> If a decision blocks me mid-run, I proceed on the **recommended default**, mark the spot with
> `❓`, and keep moving — I won't stall the whole run waiting.

***

## 7. Video strategy

* **Embed what exists:** \~20 Looms + 2 YouTube already cover a big chunk of Part 2. Phase 1
  produces the exact video↔page map.
* **Shot-list for the rest:** every `🎬 needs video` page gets an entry with: the one task it
  shows, a 3–5 beat outline, and est. length. Raymond records against the list; each page has
  the embed slot ready so dropping a URL in is a one-line edit.
* **Self-serve priority:** for audience B, prioritize recording 2.0.x (orientation) + 2.1.x
  (setup) — that's where a lost subscriber needs to *see* it most.

## 8. Knowledge-gap register (mostly resolved 2026-07-04)

Resolved by Raymond:

1. **Part 1 positioning** — *I own the draft*; Raymond reviews. Mine Workshop Notes + client
   dossiers for the sharp version. (1.1, 1.7, 1.12)
2. **Credits** — **do not mention at all.** No credit language anywhere; describe cadence in
   pages/posts/weeks. (3.16)
3. **Agency vs self-serve** — self-serve can do **everything**; the delta is discipline/rigor/
   standardization at scale, not gated capability. (3.15, audience tags)
4. **VFS conventions** — confirm the real folder structure from prod chats + code, then document.
5. **`prod-context` access** — key provided and **verified working**.
6. **Exemplary chats/orgs** — pick from the **high-activity orgs** (wonderchat, chalkie,
   frameshft, straitsx, rently-uae, bluente, bookaclinic, scheduling-wizard, …).

Remaining low-stakes gap, handled inline with `❓` where hit:

* Any org-specific claim I can't verify against code/prod/chats gets a `❓` marker rather than a
  guess, and lands in the consolidated **gap register** page for Raymond's pass.

### The Definition of Done (what the goal-loop judge checks) — see `GOAL.md`

The autonomous build is driven by `docs/training/GOAL.md`, whose acceptance gates encode
"a GREAT outcome," not merely "all pages exist."

***

## 9. Decisions (resolved 2026-07-04)

1. **Format:** portable **Markdown in-repo** under `docs/training/` this run; pick the site
   generator (Starlight/Mintlify/etc.) in a later tooling pass. Everything is authored so it
   drops into a generator unchanged (clean front-matter, relative links, video-embed slots).
2. **Audience:** **one site with audience tags** — shared pages with `For AMs` / `For self-serve`
   callouts where guidance diverges; Part 3 is AM-only.
3. **Prompt mining:** **live** — `FACTORY_API_KEY` provided and **verified working** (curated +
   sql tiers; reads `factory.agent_session`/`messages`). Rich source confirmed (wonderchat,
   chalkie, frameshft, straitsx, rently-uae, bluente, bookaclinic, …). Mining routes through
   subagents to keep transcripts out of the main context.