SOP Taxonomy & Labeling System

Status: legacy pipeline set — audited 2026-07-13

The framework below still holds — the 9-section SOP format and the naming convention are current. But the specific pipeline set it lists (Sales/Closer, Client Ops, Client Success, Setter, plus the creative pipelines) reflects the retired EyeFly-era agency org. stpierre.ai now runs as a media company with just two pipelines: the builder pipeline and the sales pipeline (delivery is part of sales). Read the pipeline names below as historical.

Purpose

Universal structure for organizing, naming, and navigating all St. Pierre SOPs — independent of storage location.

Categories

Category	Covers	Pipelines
Delivery	Workflows that produce the core client service	Sales/Closer, Client Ops, Client Success, Setter
Creative	Workflows that produce ad content	Meta Ads Creative, YouTube, Split Test
Ops & Infrastructure	Internal build, support, and maintenance	CapEx, Support
Playbooks	Role-specific guides (how a specific person does their job)	CSM Playbook, Setter Playbook, Closer Playbook

Naming Convention

Format: [Category] · [Pipeline] · [Role if role-specific]

Examples:

Delivery · Client Ops · Onboarding
Delivery · Client Success · Retention
Delivery · Setter · Qualification
Creative · Meta Ads · Editor
Creative · YouTube · Production
Ops · Support · Triage
Ops · CapEx · Build
Playbook · CSM · Akash

Required SOP Sections (all 9 required, in order)

1. Purpose — one sentence: what this SOP governs

2. Trigger — what event starts this workflow

3. Owner — who is responsible for execution

4. KPI — the single metric that defines success for this pipeline

5. Steps — numbered, action-verb-led, no ambiguity

6. Definition of Done — explicit exit criteria for each stage

7. Offshoots / Edge Cases — what happens when the standard path breaks

8. Handoff — what pipeline or person receives control next

9. Gap Flags — anything not yet documented or operationalized

Priority Tiers for Retrieval

When a new hire is looking for an SOP, they should check in this order:

1. Written SOP (this folder) — authoritative source

2. Pipeline diagram (_deliverables/2026-05-06/diagrams/) — visual reference

3. Brain stage tasks (Postgres stage_task_templates) — task-level checklist

4. Ask the pipeline owner directly — flag as a gap if no written SOP exists

Gap Flagging Standard

If a workflow has no written SOP, add a row to the SOP Gap Report with:

Workflow name
Who owns it
What format the knowledge currently exists in (diagram / brain / person's head)
Estimated effort to write it (S / M / L)
Blocked by anything?