# SOPs Before Automation: An Operations Playbook for Growing Studios

- Source: https://simeoncreatives.com/blog/sops-before-automation
- Hub: Business Growth & Case Studies
- Author: Simeon Matheka, Founder & Creative Director
- Published: 2026-08-17
- Updated: 2026-09-01
- Reading time: 16 min

Automating a messy intake process just creates faster mess. How to write standard operating procedures (SOPs) for leads, delivery, and publishing, then automate only the steps that are already boring and correct.

Studios buy automation when they feel behind. The usual purchase is a tool. The usual result is the same chaos with webhooks. Standard operating procedures (SOPs) are the missing layer: a process you could hand to someone on Tuesday without a call.

This spoke is the operations chapter of the growth hub. Channels get you conversations. SOPs decide whether those conversations get a reply. For tool choice and build sequence, use the [AI & Business Automation hub](https://simeoncreatives.com/blog/ai-automation). Do not start there if the manual path is still a mess.

## Three SOPs that unlock growth

You do not need a 90-page ops manual. You need three paths written down.

| SOP | Trigger | Done means |
| --- | --- | --- |
| Lead intake | Form, email, or referral lands | Logged, qualified, owner assigned, first reply sent |
| Delivery kickoff | Agreement signed | Brief, files, timeline, and comms channel exist |
| Publish / ship | Asset or article is approved | Live URL, tracking, and a note to the client or list |

> If a step only lives in your head, it is not an SOP. It is a single point of failure.

## Write the intake SOP before you touch n8n

Intake is where money leaks. Write it as a checklist, then run it manually for two weeks.

1. **Capture: **one form (or one inbox rule). Required fields: name, email, need, timeline. Honeypot or equivalent spam control.
2. **Store: **one row per lead. No parallel WhatsApp notes that never get copied.
3. **Qualify: **a yes/no against the who-line from your offer. Not a vibe.
4. **Notify: **the owner gets a ping with the row, not a screenshot.
5. **Reply: **a template that matches the site offer. Time box: same business day, faster if you can.

When that path is boring, automate it. Our production pattern for volume is documented in the [n8n and Supabase lead-routing case study](https://simeoncreatives.com/blog/automated-lead-routing-onboarding-n8n-supabase). A studio site can start with a sheet. The SOP does not change when the store does.

## The one-page SOP card (copy this)

If it does not fit on one page, you wrote a novel. Six fields. Fill them in plain language.

| Field | Write | Bad version |
| --- | --- | --- |
| Trigger | What starts the path (form submit, signed PDF, approved draft) | “When we hear from someone” |
| Owner | One name (or a named role with a backup) | The studio / whoever is free |
| Steps | Numbered, in order, including where the row lives | “Follow up and see” |
| Service level agreement (SLA) | Hours or business days to the next human action | ASAP / soon / when I can |
| Done | A check you could screenshot | “We handled it” |
| Exception | What leaves the default (wrong ICP, legal, angry client) | Every lead is an exception |

Print it. Run the next ten jobs against it. If you skip a field every time, the card is wrong, not the week.

## How intake actually runs here

On simeoncreatives.com the commercial path is one contact form. It posts to a Google Apps Script, which appends a row. Required fields are the ones we use in the first email: name, contact, what they need. Optional website URL is allowed because it changes the first reply. Extra “tell us your budget in a novel” fields are not. That is the capture step of the SOP, not a customer relationship management (CRM) rollout. How the public site, search, and intake share a job is in the [Simeon Creatives growth-system case study](https://simeoncreatives.com/blog/case-study-simeon-creatives-growth-system).

- **Capture: **one form, honeypot, no second inbox that never gets copied.
- **Store: **one row, timestamped. WhatsApp still happens. It does not replace the row.
- **Notify: **the owner sees the row, not a screenshot in a group chat.
- **Reply: **human, same business day, same offer as the homepage. Templates exist. Send is not automatic.

When volume made manual triage the bottleneck for a service client, we encoded that same SOP in n8n and Supabase: validate, store, route, dead-letter. We did not start with a large language model (LLM) writing the client email. That pattern is the [lead-routing case study](https://simeoncreatives.com/blog/automated-lead-routing-onboarding-n8n-supabase). The SOP was already boring before the workflow existed.

## Delivery kickoff: the SOP after they say yes

Intake gets you the conversation. Kickoff stops the project from living in a 40-message thread. Write it before you hire a project tool.

1. **Agreement filed: **PDF or signed note in one folder. Not “they said yes on WhatsApp.”
2. **Brief: **who, offer, constraints, due dates. If branding, the kickoff agenda is already a document. See how we run a branding kickoff.
3. **Files: **one drive or repo. Logos, access, copy. “I will send later” is not kickoff.
4. **Channel: **one place for decisions (email thread or named Slack). Parallel DMs are how scope dies.
5. **First milestone date: **on a calendar, with an owner. Vague “next week” is not a date.

Done means a second person could run week one without pinging you for the password. If they cannot, you still have a memory, not an SOP. Brand origination uses the same discipline in [how we run a branding kickoff](https://simeoncreatives.com/blog/how-we-run-a-branding-kickoff).

## Publish / ship: done is a live URL

Studios “finish” work in Figma or a local build and call it shipped. Search, clients, and AdSense reviewers do not care about local. The publish SOP is a checklist against the public URL.

- **Live: **HTTPS, the real domain, not a preview link you will delete.
- **Indexable: **the first HTML contains the words. A React shell with no body is not published for search. See [why crawlers saw an empty React site](https://simeoncreatives.com/blog/why-crawlers-saw-an-empty-react-site).
- **Findable: **in the sitemap if it should rank, canonical matches the URL you share.
- **Usable: **form or next step works on a phone. Screenshot it.
- **Told: **client or internal list gets the URL. Shipping into silence is how work gets redone.

## What to automate vs what to keep human

| Automate | Keep human |
| --- | --- |
| Logging, timestamps, duplicate checks, spam filters | Saying yes or no to a weird-fit brief |
| Internal notify, calendar link for qualified leads | Scoping, pricing, creative judgment |
| Publish checklists, sitemap pings, file exports | Whether the work is actually good enough to ship |

If a step needs interpretation, wrap it. Do not let a model send the client email unsupervised. That split is the point of [deterministic workflows vs LLM agents](https://simeoncreatives.com/blog/deterministic-workflows-vs-llm-agents).

When the irreversible step is “send to the client,” park it. That is [human-in-the-loop review for n8n and LLM jobs](https://simeoncreatives.com/blog/human-in-the-loop-n8n-llm-jobs): queue, approve, then send. Human-in-the-loop (HITL) without an SOP is just a slower mess.

### Before and after the SOP exists

| Moment | Before (memory) | After (SOP) |
| --- | --- | --- |
| New form fill | Ping in a group chat, maybe a screenshot | Row exists, owner named, SLA clock started |
| Busy Thursday | Leads wait until “after this deadline” | Backup owner runs the same card |
| Weird-fit brief | Three people debate in DMs | Exception path: one person says no, logged |
| Tool shopping | Buy CRM because it looks like growth | Automate capture → store → notify only |

## Failure modes we see

- **Tool first: **CRM, then process. Nobody fills the CRM. Buy the SOP, then the seat.
- **Automating exceptions: **every lead is “special,” so the workflow has 40 branches. Write the default. Exceptions stay human.
- **No owner: **a Slack channel is not an owner. One name on the SOP.
- **No done definition: **“we followed up” is not done. Logged + replied + next date is done.
- **Silent send: **the model or the zap emails the client because it felt fluent. Irreversible stays human until the default is boring and logged.

## A 14-day ops sprint

1. **Days 1 to 3: **Write the intake SOP on one page. Run every new lead through it by hand.
2. **Days 4 to 7: **Fix the form fields so they match the SOP. Delete optional noise.
3. **Days 8 to 11: **Add notify + a reply template. Measure time to first response.
4. **Days 12 to 14: **Automate only capture → store → notify. Leave qualify and reply human unless volume demands it. If you are also running a 90-day commercial sprint, this 14-day block is week 9 and 10 of that calendar, not a parallel project.

How this looks on a real studio site is the next piece: [the Simeon Creatives growth-system case study](https://simeoncreatives.com/blog/case-study-simeon-creatives-growth-system). The quarter-scale calendar is [a 90-day growth sprint for a studio with one offer](https://simeoncreatives.com/blog/ninety-day-growth-sprint-one-offer). Step-by-step tool builds live in [How to Automate Your Business with AI](https://simeoncreatives.com/blog/how-to-automate-your-business-with-ai). If you want that ops layer written into a live studio, start at [/contact](https://simeoncreatives.com/contact).

## FAQs

### What is an SOP in a small studio?

A standard operating procedure (SOP) is a written path a second person could follow: trigger, steps, owner, done definition. If only you can run intake, you do not have an operation. You have a memory.

### When is a process ready to automate?

When it is high volume, rule-based, and already correct on paper. If you still argue about who replies, what a qualified lead is, or where files live, automation will encode the argument.

### Should we start with an AI agent?

No. Start with deterministic steps: capture, store, notify, schedule. Add a model only where interpretation is the bottleneck. See deterministic workflows versus large language model (LLM) agents.

### What if we only have a spreadsheet today?

That can be a valid first SOP. A sheet with required columns, an owner, and a response-time rule beats an empty customer relationship management (CRM) nobody opens. Graduate the store when volume or access control demands it.

### What is a service level agreement (SLA) for studio intake?

A service level agreement (SLA) here is the maximum time from inbound to a human reply. Same business day is a real SLA. “ASAP” is not. Put the number on the SOP. Measure it weekly.

### How do standard operating procedures relate to human-in-the-loop (HITL)?

Human-in-the-loop (HITL) is what you add after the SOP exists: a pause before irreversible sends. If you have no written path, HITL is just another inbox. Write the default first, then park the risky step.