> ## 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.

# Agency partners & standardization at scale

> The rigor delta — what running to standard means when you operate many accounts.

What "at scale" changes is discipline, not capability. Everything in this playbook is available to
self-serve users too — the delta when you run many accounts is rigor: run every SOP the same way,
pass every gate, and standardize the conventions, so quality stays constant across accounts and
across whoever's driving.

## Discipline, not capability

Self-serve users can do everything in this playbook: the same tools, the same Pi, the same
surfaces. Nothing here is gated to agencies.

What changes at scale is discipline. When you run one account, you can be informal. Poke at
keywords, publish when it feels ready, eyeball the results. When you or an agency run many
accounts, that informality stops working: quality drifts, steps get skipped, and every account
ends up run slightly differently. Standardization is what keeps quality constant across accounts
and across whoever's driving.

## What "run to standard" means

Operating an account to the agency bar means:

* Run the SOPs rather than improvising. [Onboarding Month 1](/sops/onboarding-month-1),
  [monthly](/sops/monthly-planning) and [weekly](/sops/weekly-planning) planning,
  [organise keywords](/sops/organise-keywords), and the [client review](/sops/client-review),
  the same steps on every account.
* Pass every quality gate. The [Definition of Done](/sops/content-production-dod) and the
  [Quality Gate](/sops/quality-gate) are non-negotiable, not "when there's time."
* Standardize the conventions: consistent keyword tagging (cycle tags, Core/Fringe), consistent
  pillar structure, consistent refiner defaults, a consistent technical-SEO checklist.
* Keep each client's Pi current. Product bible, org info, and memory stay up to date so Pi produces
  on-brand, accurate work for every account ([2.1.2](/platform/company-research-product-bible),
  [2.0.4 VFS](/platform/filing-in-the-vfs)).
* Make handoffs repeatable: record Looms for new flows, define publishing schedules in `#bpo`, and
  track backlogs in Linear ([3.14 Roles & handoffs](/sops/roles-handoffs)).
* Escalate by the same rules. The same Quality-Gate thresholds and escalation triggers on every
  account, so problems surface early and consistently.

## Why it matters

The SOPs aren't paperwork for its own sake. They're how a team produces the same quick-win outcome
on every account ([Part 1 §1.7](/theory/speed-to-rank)), rather than a great result
only on the accounts that happened to get attention. At scale, the standardization is the product.

> ❓ **\[needs Raymond]** Any hard boundaries specific to agency partners (white-label limits,
> billing, what they can/can't access) beyond "run to the standard bar." Confirm if there are any.

**Related:** [3.14 Roles & handoffs](/sops/roles-handoffs) · [3.16 Capacity & cadence](/sops/capacity-cadence)