Process design
17 SOP flowcharts, one niche
Before any automation gets built, the process gets mapped. These are the maps behind the systems: how a Meta lead becomes a booked estimate, what a morning data check does with a gap, what happens when a sync fails, how an old database gets woken up. 8 are anonymized production, processes running today at a Meta-ads agency serving home-service contractors, every name invented. 9 are demos, designed for invented local businesses.
- Trigger
- Automated step
- Decision or wait
- Stop, alert or refusal
- A person does it
- Hand-off between teams
Click any map to open it. Inside: click the map to read it closer, ← → for the next one, Esc to close.
No map matches that filter. Clear the search or pick another chip.
How these are made
Map first, build second.
Every map is a Mermaid flowchart rendered to SVG in one house style: a trigger at the top, a decision diamond at every branch, a labelled exit on every diamond, waits drawn as waits, and a lane for each team that acts. The production maps come from systems I run for a Meta-ads agency and its contractor clients; the demos are designed for invented businesses in the same trades.
- Every name is invented and checked against every client and brand I have worked with.
- No client figures. Timers and thresholds are process settings, not results.
- Dotted arrows are hand-offs between teams; solid lines are the automation, dotted lines the hand-offs.
Available for remote work
Want one of these mapped for your business?
Send me the process that keeps breaking. I map it first, then build the automation that runs it.