Skip to content
Rule the Internet

Automation 35 of 50

Build a personal ops wiki so you stop re-solving problems

Runbooks for deploy, refunds, and onboarding live in one place.

4 min read149 wordsAll guides

Tools for this guide: Notion · Nexarch · Obsidian

Download free PDFFull 50-pack PDF

The solo bottleneck

Solo operators re-learn their own business every quarter.

This guide is part of a free series: 50 useful automations for people running the business alone. Download the printable PDF anytime: Free PDF — Build a personal ops wiki so you stop re-solving problems.

Stack that stays small

Notion/Nexarch wiki with templates.

Tools named here: Notion, Nexarch, Obsidian. Prefer official docs and native features before adding another SaaS.

Ship the automation

Create pages: Deploy, Incident, Refund, Onboarding, Offboarding.

After any painful incident, write the runbook the same day.

Link runbooks from your phone home screen.

Optional: keep business assets organized in Nexarch.

Keep it honest

If it took more than 20 minutes to figure out once, document it.

Automations should reduce decisions and errors — not hide broken processes. If a Zap fails weekly, fix the process or delete the Zap.

Download

Grab the free PDF for this task: Download PDF. Or browse the full set from the homepage automation carousel.