AI Automation Agency SOPs: The 8 You Need (With Template)

The AI automation agency SOPs to write first, from sales to offboarding, a fill-in template, where to keep them and how to make them Claude Code skills.

Josh Pocock5 min read

Agency SOPs cover

Automation & Agents

Agency SOPs

Stride AI Academy

An AI automation agency needs SOPs for the work that repeats on every client: discovery, proposals, onboarding, building, testing, launch, monitoring and offboarding. Write each as a short checklist with an owner and a definition of done, and turn the build ones into Claude Code skills.

SOPs (standard operating procedures) are what let you deliver the same quality on client ten as on client one, and hand work to someone else. This guide lists the eight to write first, gives a template, and shows how to make the technical ones run themselves.

The client lifecycle, one SOP per stage

  1. 1Discovery and scoping
  2. 2Proposal and contract
  3. 3Onboarding
  4. 4Build
  5. 5Test and launch
  6. 6Monitor and report
  7. 7Changes and offboarding

The eight SOPs to write first

1. Discovery call

The questions, the order, and what to capture in the CRM afterwards. Start from the discovery call script.

Done when: the call notes include the process, the client's numbers, the decision-maker and a booked next step.

2. Proposal and contract

How to turn call notes into a proposal, which pricing options to offer, and the contract checklist. See the proposal template and the contract checklist.

Done when: the client has signed and paid the setup invoice.

3. Client onboarding

The welcome email, kickoff agenda, access checklist and baseline measurement. The onboarding checklist is a ready-made version.

Done when: all access is in place, the process map is confirmed and the baseline is recorded.

4. Build

How a project is set up: repository naming, the CLAUDE.md template, branch and pull request rules, where secrets go, and how changes are reviewed.

Done when: the build runs on test data and every change is in a reviewed pull request.

5. Testing

The test plan every automation goes through before launch:

  • Run 20 to 50 real past examples and check each output
  • Test the failure cases: missing data, an API down, a duplicate lead, an opt-out
  • Confirm the logs show every run and alerts fire on failures
  • The client approves message templates

Done when: every test passes and the client has signed off templates.

6. Launch

Go-live steps, the first week with a human approval step, and the review call.

Done when: a week without client-visible problems and written sign-off.

7. Monitoring and monthly reporting

Daily alert checks, how incidents are handled and communicated, and the monthly report format. See client retention for the reporting rhythm.

Done when: the report is sent on the same day every month.

8. Change requests and offboarding

How changes are requested, quoted and approved, and the offboarding steps: export, documentation, access removal, confirmation in writing.

Done when: for offboarding, all access is removed and confirmed.

The SOP template

Keep every SOP in the same shape, short enough to follow while doing the work:

Markdown
# SOP: [Name]

**Owner:** [role, not a person's name]
**When:** [the trigger, e.g. "after a discovery call is booked"]
**Time:** [usual time it takes]
**Done when:** [the checkable end state]

## Steps
1. [Action, written as an instruction]
2. [Action]
3. [Action]

## Checks
- [ ] [Thing to verify before calling it done]
- [ ] [Thing to verify]

## Templates and links
- [Email template, checklist or tool link]

SOP creation gets easier with AI. Record yourself doing the task, and ask AI to draft the steps from the transcript. Automate the steps that never change. If an AI agent runs part of the process, give it an SOP too: its trigger, its limits and who checks its work.

## Common mistakes
- [What went wrong before, and how to avoid it]

Last reviewed: [date]

Two rules that keep SOPs useful: write steps as instructions ("Send the access checklist"), not descriptions, and add to "Common mistakes" every time something goes wrong.

Where to keep them

  • Business SOPs (sales, onboarding, reporting) belong where your team works every day: a shared doc space such as Notion, or your CRM.
  • Build SOPs belong in the code: a CLAUDE.md template in each repository and shared skills in a team repository, so they travel with the project.

Review each SOP every quarter, and date the review at the bottom.

Turn build SOPs into Claude Code skills

The build, testing and reporting SOPs are repeatable enough for Claude Code to follow them directly. A Claude Code skill is a folder with a SKILL.md file that Claude loads when a request matches its description, or when you type /skill-name. Your testing SOP becomes a pre-launch-check skill. Your monthly report SOP becomes a monthly-client-report skill. See how to create Claude Code skills for the format, and CLAUDE.md file examples for the repository template.

The written SOP stays the source of truth for people. The skill is the version Claude follows.

Start small

Don't write all eight in a week. Write the SOP for the step that went wrong most recently, use it on the next client, fix it, then write the next one. Within a few months you'll have the full set, each one tested on real work.

Learn to run the agency side

The Stride AI Operations course covers running client CRMs, pipelines, voice agents and AI follow-up in StrideOps, the AI operating system Josh Pocock's companies run on, with weekly live calls. The Academy's template vault includes prompts, workflows and SOPs you can copy, and the free guide library is a good place to start.

FAQ

What SOPs does an AI automation agency need?

Start with eight: discovery calls, proposals and contracts, onboarding, building, testing, launch, monitoring and reporting, and change requests and offboarding. Together they cover every stage a client goes through.

What should an SOP include?

An owner, the trigger that starts it, how long it usually takes, a checkable definition of done, numbered steps written as instructions, a short checklist, links to templates, and a list of common mistakes. Keep it short enough to follow while doing the work.

Can AI write SOPs for my agency?

AI can turn a recording of you doing the task, or your notes, into a first draft quickly. Review it, test it on a real client and add the mistakes you hit. Technical SOPs can then become Claude Code skills that Claude follows directly.

Where should I store agency SOPs?

Keep business SOPs where your team works daily, such as a shared doc space or your CRM. Keep build SOPs with the code, as a CLAUDE.md template and shared Claude Code skills, so they travel with each project.

Build it with us in Stride AI Academy

Four courses, weekly live calls and a community of people building and selling AI. Or start with 310+ free guides.

Keep reading

Free Automation & Agents guides