Ops Automation Planner
Document your processes, then automate the ones worth automating
The problem
In most small businesses, the way things get done lives in one person's head. Nothing is written down, every task is done slightly differently each time, and "we should automate this" stays a wish because nobody knows where to start or which tool to trust. Meanwhile hours disappear each week into copy-paste work a $20/month tool could do.
The tool
Once installed, this skill turns your AI assistant into an operations analyst that knows your team size, your software stack, your budget, and your comfort with tools. It works in the right order: map the process as it actually happens, stabilize it with a written SOP, and only then automate — because automating a broken process just breaks things faster.
Before: processes live in memory, break when someone is sick, and automation ideas stall at "we should look into Zapier." After: each key process is a confirmed step-by-step map with every step tagged Fine, Fragile, Waste, or Automatable; SOPs a new hire could follow on day one; and a ranked list of automations with the specific tool, setup effort, and hours saved per month for each. Unlike a one-off prompt, it builds a library over time — SOPs get changelogs, stale ones get flagged, and weekly ops reports follow the same format every week so trends are visible.
What's inside
- Process mapping by interview, with each step tagged for health
- SOPs that name the exact tool, button, and template at every step
- Automation opportunities ranked by payoff, matched to your existing stack
- No-code build plans with triggers, field mappings, and test scripts
- Weekly ops reports: numbers, what broke, what shipped, next week's top 3
- Periodic SOP library reviews with changelogs
How to use it
- 1Click "Install skill" on this page and copy the install prompt.
- 2Paste it into your AI assistant (Claude, ChatGPT, Cursor — anything that can fetch a URL or accept pasted text).
- 3Answer the skill's setup questions about your business.
- 4Start by mapping your single most painful process — answer its interview questions, confirm the map is accurate, and let it write that SOP before touching automation.
Example
A small e-commerce warehouse names returns processing as its worst process. The skill interviews the owner and plays back an 11-step map: three steps tagged Fragile (they live in the manager's head), two tagged Waste (the return is logged in both a spreadsheet and the store admin), one tagged Automatable. It writes the returns SOP, then recommends one automation: "When a return is approved in Shopify, create a row in the Returns sheet and notify #warehouse in Slack — buildable in Zapier on your existing plan, about 30 minutes of setup, saves roughly 3 hours/month of double entry." The build plan includes field mappings and three test cases to run before trusting it.
Pro tip
Run the weekly ops report even in weeks when nothing broke. The habit is the point — after two months you have a searchable operating log, and the skill starts spotting patterns ("shipping complaints spike every long weekend") that no single week reveals.
Related tools
Want this customized and automated for your business?
We take the tools in this toolbox and wire them into your business — your data, your brand voice, running on autopilot.
Talk to Vexlo