Lesson 15
This lesson is not about learning Zapier or Make. It is about something more fundamental:
The sequence matters. Automating a process you do not yet understand produces automated mistakes at scale. First do it right. Then write it down. Then let the machine do the repeating.
With one website, you can hold everything in your head: where GA4 is, how the sitemap is set up, what to check before launch, what the prompts are.
With six websites, your memory becomes a single point of failure. With ten, it breaks entirely.
The deeper problem is not remembering what to do. It is the decision cost of figuring it out again from scratch every single time. Every re-decided question was already answered the last time — and the answer was the same. SOP captures that answer so you never pay that cost twice.
Most corporate SOPs fail because they are 40-page documents that no one reads. An OPC SOP should be a checklist you can act on in real time.
Example — New Website Launch:
That is a complete launch SOP. No document to hunt for. No wondering if you missed something.
| SOP | What it captures |
|---|---|
| Content production | From idea to published post — keyword check, intent, draft, human edit, fact check, internal links, SEO, publish, post-publish review |
| Product launch | From requirement to live — design, build, test, launch checklist, first analytics review |
| Customer support | How to classify and respond to each message type: bug, refund, how-to, feature request, spam |
| Weekly data review | Exactly which numbers to check, what questions to ask, what decisions to make |
Rule: the third time you do something the same way, write the SOP. First time is exploration. Second time is confirmation. Third time is a pattern — and patterns belong in a document, not your head.
The worst version of AI-assisted content: "AI finds keywords → AI writes 100 articles → auto-publish." That is automating garbage at scale.
A useful content SOP goes through real gates:
That last step matters as much as the first. Publishing is not the end of the process. It is the start of the measurement loop.
AI is good at
You must keep
AI removes low-value cognitive load. You keep judgment.
Is it genuinely repetitive?
If every instance is different, AI adds limited value. Automation requires predictable inputs and outputs.Is "good vs bad" objectively clear?
Checking if a canonical tag exists: yes. Deciding whether this article is worth writing: no.How bad is an AI mistake here?
Wrong button label: low cost. Auto-processing a payment dispute, publishing medical information, or sending bulk email: high cost. Higher cost = more human review required, not less.Level 1
Checklist
New site launch SOP. You do the work; the list prevents skipped steps.
Level 2
Template
One-Person Site Starter. The structure is pre-built; you fill in the content.
Level 3
AI Assisted
AI writes the draft, generates the code, or classifies the email. You review and approve.
Level 4
Automated
Git push → Cloudflare deploys. Payment received → confirmation email sent. No human in the loop for routine cases.
A functioning OPC typically runs all four levels simultaneously. You do not graduate from one to the next — you apply the right level to each specific task.
Human in the Loop means: AI does 80% of the mechanical work, you handle the final 20% that requires judgment.
Example — customer support:
That is very different from AI deciding unilaterally whether to issue a refund. The judgment stays with you. The grunt work does not.
A simple formula for deciding whether automation is worth building:
A task that happens weekly and takes two minutes: do it manually. A task that happens 50 times per day and takes three minutes each: that is 2.5 hours per day — automate it immediately.
Early OPC trap: spending three days configuring Zapier + PayPal + Sheets + webhooks to handle two orders per month. That is negative ROI. Automate genuine bottlenecks, not low-frequency tasks that feel inefficient.
Once real orders arrive, manual fulfillment (read PayPal email → manually send PDF) will not scale. An automated order flow looks like:
Critical rule: always validate on the server side using the official webhook from the payment provider. Never trust the frontend to report "payment succeeded" — that signal is trivially spoofed. The closer the automation is to money, identity, or permissions, the more important server-side verification becomes.
A simple post-purchase sequence for a $4.99 digital product:
The danger of email automation is the same as any automation: it scales whatever you already have. A helpful sequence helps at scale. A pushy promotional sequence becomes harassment at scale. Design the sequence as if you were sending each email yourself.
Managing multiple websites manually means logging into GA4, GSC, revenue dashboards, and cost trackers one by one. With five sites this is tedious. With twenty it is impossible.
The target state:
You move from reading every number to responding only to signals that matter.
A mature operating system should not require the founder to monitor normal operations. Normal is not news.
If your dashboard is full of green, you should be able to close it and go work on something that matters. The system's job is to tell you when something breaks — not to demand daily attention to confirm nothing is wrong.
System / Automation
AI
You (founder)
The goal is not a company with no humans. It is a company where the human's time is spent on decisions — not on tasks the system can handle.
| SOP | Priority | When to build |
|---|---|---|
| New website startup | Critical | Now |
| Pre-launch checklist | Critical | Now |
| Weekly portfolio review | High | Now |
| Content production | High | Now |
| New tool / feature release | High | Now |
| Bug handling | High | Now |
| Customer support categories | When first emails arrive | At first users |
| Payment & refund handling | Before first charge | Before launch |
| Email lifecycle | After first customers | After first customers |
| Automated data digest | When managing 5+ sites | When managing 5+ sites |
Currently active automation worth your attention: GitHub → Cloudflare deploy, CI checks, and a simple dashboard data pull. You do not need a SaaS stack to get started.
The highest-leverage version of an SOP is when it becomes code.
You no longer tell Claude how to set up canonical tags on every new project. The template already knows. That is what it means to not solve the same infrastructure problem twice.
"The goal is not full automation. It's getting the system to run, AI to assist, and you to decide — instead of rebuilding the same thing and fighting the same fires every week."