Automate after it hurts twice
Do not automate fantasy workflows. Automate the steps you already repeat: new lead → Notion row → welcome email → Slack ping. Start with Zapier or Make. Move to n8n when you want ownership and complexity.
Name zaps like an adult: "Lead to CRM," not "Final Automation 3." Future you is a stranger who hates you.
Add guards
Every automation needs a failure path: ping you when it breaks, dedupe emails, and rate limits. Silent failures are how you ghost customers by accident.
Document each zap in the doctrine wiki. If only you understand it, you built a job, not a business.
Keep a human in the loop
Automate delivery of access and receipts. Do not automate empathy. First-week customers deserve a human sentence. That sentence can still be templated — just send it on purpose.
Running tip: audit automations monthly. Delete anything that has not fired. Dead zaps are landmines.
Field notes
Field note: automation should reduce your average response time without reducing your judgment. If a zap sends the wrong welcome sequence, you taught the market you are careless. Carelessness does not scale.
Log every automation owner. When you are sick, someone — even future you — needs a map.
Operator checklist
Operator checklist: automate only the path you have run manually at least twice. Name the automation clearly and write a three-line doc in the wiki.
Add a failure notification to your phone or inbox. Silent automation is how customers feel abandoned while you feel productive.
Review zaps on the last Friday of the month. Delete dead ones. Update ones that still matter.
How to run it this week
Draw the workflow on paper before clicking Zapier. If the paper looks insane, the zap will too.
Prefer idempotent steps: running twice should not double-charge or double-email.
Keep a manual override. Automation without an escape hatch becomes a hostage situation.
What good looks like
What good looks like: one named automation with a failure ping and a wiki note. That is leverage. Twenty mystery zaps are liability.
Common failure mode: automating empathy and policy. Keep humans on judgment. Automate chores.
Series bridge
Series bridge: this chapter sits between opening the shop and finding first customers. If you skipped here, go back one part and finish the checklist first. The playbook only compounds when each layer is real — research under offer, offer under site, site under product, product under distribution.
Keep a single Notion page titled Kingdom OS and paste the outcome of this part at the bottom before you leave. Date it. Future you will skim twenty dated notes faster than twenty open browser tabs. That page becomes the operating system the last chapter asks you to run daily.