| name | build-sop |
| description | Produce a Standard Operating Procedure for a role or process (14 variants — 8 roles: Setter/Closer/SDR/Content-Mgr/Video-Editor/CS/VA/Marketing-Mgr + 6 processes: Sales/Content/Onboarding/Lead-Mgmt/QA/Reporting). the operations director's straight growth operating process methodology. Produces SOP + KPIs + quality gates + escalation rules + training plan. |
/build-sop — Standard Operating Procedure Builder
Role
Produce deterministic SOPs for roles and processes. Lineage: the operations director (straight growth operating process), Scale department Department (14 SOP variants), Agency Execution OS.
The 14 Variants
8 Role SOPs:
- Setter — lead qualification + booking
- Closer — sales call execution
- SDR / Dialer — outbound + phone triage
- Content Manager — content production orchestration
- Video Editor — editing workflow + asset delivery
- Customer Success — post-purchase onboarding + retention
- VA / Admin — general operations assistant
- Marketing Manager — campaign orchestration
6 Process SOPs:
- Sales Process — end-to-end sales cycle
- Content Production — idea → publish
- Client Onboarding — sold → activated
- Lead Management — opt-in → booked → closed tracking
- Quality Assurance — output review gates
- Reporting — weekly/monthly metrics cadence
Output Structure
W(sop) =
1. Role/Process Definition + Outcome
2. Inputs (what triggers this, what they receive)
3. Phase-by-Phase Workflow (numbered steps)
4. Quality Gates (per phase — PASS criteria)
5. KPIs (metrics that define good performance)
6. Tools + Systems (what they use)
7. Escalation Rules (when to escalate + to whom)
8. Training Plan (how to onboard new person into role)
9. Continuous Improvement (review cadence)
Decision Logic
Variant Selection
Per team structure and gap identified. Or --variant=<role>|<process>.
the operations director's 8-Stage Customer Journey (Sales Process SOP)
- Traffic cost + quality
- Landing page
- Application / opt-in
- TY / confirmation page
- Setter response time (< 5 min)
- Pre-call nurture
- On-call execution
- Post-purchase experience
KPI Specification (per role/process)
- Setter: response time, show-rate, qualification accuracy, calls booked/day
- Closer: close rate, AOV, refund rate, follow-up discipline
- SDR: calls/day, connect rate, booked/week
- Content Mgr: posts published/week vs plan, engagement delta, production cycle time
- Video Editor: turnaround time, revision rounds, output quality score
- CS: NPS, retention rate, upsell conversion, first-response time
- VA: task completion rate, response SLA
- Marketing Mgr: CAC, LTV:CAC, channel ROI, campaign launch velocity
Tacit Principles
-
SOPs are written FOR the new hire. If a new person can't execute from the doc, SOP is incomplete.
-
Every phase has a DONE criterion. Ambiguous completion = process drift.
-
KPIs numeric + time-bound. "Fast response" fails. "< 5 min response 95% of the time" succeeds.
-
Escalation rules prevent bottleneck. Name who escalation goes to + in what timeframe.
-
Tools are named explicitly. "Use our CRM" fails. "GoHighLevel, specific pipeline, tag X on stage change."
-
Training plan required. SOP + training plan together. New hire should be 80%+ autonomous in 2 weeks.
-
Review cadence non-optional. Monthly SOP review catches drift.
-
Version the SOP. Changes logged. Last-revision-date at top.
Process
Phase 0 — Load
- Offer Doc, company.yaml compartment 11 (tech stack + team structure)
- Existing SOPs (if any) for consistency
reference/frameworks/growth-operating-process/README.md (operations methodology)reference/operators/operations-director.md
Phase 1 — Variant Selection
Per team gap or request.
Phase 2 — Role/Process Definition
What does this role/process do? What outcome does it produce?
Phase 3 — Inputs + Triggers
What starts the workflow? What inputs arrive?
Phase 4 — Phase-by-Phase Workflow
Numbered steps. Each step:
- Action (what to do)
- Tool (where to do it)
- Time (target duration)
- Output (what's produced)
Phase 5 — Quality Gates
Per phase, PASS/FAIL criteria. No phase ships without gate pass.
Phase 6 — KPIs
Numeric + time-bound. Daily/weekly/monthly.
Phase 7 — Tools + Systems
Named list + integration points.
Phase 8 — Escalation Rules
"When [condition] → escalate to [role] within [timeframe]."
Phase 9 — Training Plan
- Week 1: shadow existing + read SOP
- Week 2: execute with supervision
- Week 3: autonomous + daily review
- Week 4: full independence + KPI tracking
Phase 10 — Review Cadence
Monthly SOP review. Quarterly deep audit.
Output Format
# SOP — [Role/Process Name]
**Variant:** [role: setter | closer | ...] or [process: sales | content | ...]
**Owner:** [role]
**Last Revision:** [date]
**Version:** 1.0
---
## 1. Definition + Outcome
[What this role/process does, what outcome it produces]
## 2. Inputs + Triggers
[What starts the workflow]
## 3. Phase-by-Phase Workflow
### Phase 1 — [Name]
- Action: [...]
- Tool: [specific tool]
- Time: [target]
- Output: [...]
### Phase 2 — [Name]
[...]
## 4. Quality Gates
| Phase | PASS Criteria | FAIL Action |
|---|---|---|
| 1 | [...] | [...] |
## 5. KPIs
| Metric | Target | Frequency |
|---|---|---|
| Response time | < 5 min 95% | Daily |
## 6. Tools + Systems
[named list]
## 7. Escalation Rules
[When → who → timeframe]
## 8. Training Plan
[Week 1-4 progression]
## 9. Continuous Improvement
- Monthly SOP review: [date]
- Quarterly audit: [date]
---
## Appendix A — Example executions
## Appendix B — Common failure modes + fixes
Important Rules
- NEVER ship SOP without DONE criteria per phase.
- NEVER use ambiguous KPIs ("fast," "good," "reasonable").
- ALWAYS name the tool specifically.
- ALWAYS include escalation rules.
- ALWAYS version the SOP.
Verification Checklist
Next Skills
/hiring-brief — hire into this role/retention-check — if CS SOP, feeds into retention tracking/revenue-report — if Reporting SOP, feeds revenue tracking
References
reference/frameworks/growth-operating-process/README.md (the operations director 8-stage journey)reference/operators/operations-director.md- Scale department Department canonical
v1.0 — 2026-04-19. Cycle 5 Scale.
