10x Rule¶
Type: Automation prioritization heuristic
Definition¶
The 10x Rule is a decision framework for prioritizing automation investments: if a task takes 10 hours per month, it's worth automating even if the setup takes 10 hours. The breakeven point is 1:1 — automation should save at least 10x the time it costs to build. Tasks that take 1 hour per month need less than 2-hour setup to be worthwhile. This rule cuts through the noise of "what should I automate first" by providing a simple economic filter.
How It Works¶
Calculate monthly time cost of manual task execution: (time per execution × frequency per month). If that number exceeds 10 hours, automate it regardless of setup complexity. If it's around 1 hour per month, be selective — only automate if setup takes less than 2 hours. Below 1 hour per month, automation is rarely worth the overhead.
The rule assumes that setup time is a one-time cost and manual execution time recurs indefinitely. The 10x multiplier provides a safety margin for maintenance, debugging, and the fact that automation occasionally fails and requires human intervention.
Prerequisites before automating: run the task manually 5-10 times first. If the process is still being figured out, automation will need constant rewrites. The task must be stable, well-defined, and have clear success criteria.
Good automation candidates: regular (daily/weekly), take more than 5 minutes, have consistent steps, don't require nuanced judgment. Bad candidates: one-off tasks, highly variable processes, require complex human judgment, high stakes if errors occur.
Key Properties¶
- 10x economic threshold — task worth automating if monthly time cost > 10× setup time
- 1:1 breakeven — 1 hour/month task needs <2 hour setup to justify automation
- Prerequisite: stability — run manually 5-10 times before automating; process must be defined
- Good candidates — regular, >5 min, consistent steps, no nuanced judgment required
- Bad candidates — one-off, variable, complex judgment, high-stakes if wrong
- Safety margin — 10x multiplier accounts for maintenance, debugging, occasional failures
Related Concepts¶
- simple-pipeline — the task being prioritized for automation typically implements a Simple Pipeline
- event-driven — recurring automation candidates (cron-based tasks) are the target of 10x rule analysis
Source Chapters¶
- kelly-handbook-ch14-designing-stack — 10x rule defined as core design principle
- kelly-handbook-ch11-business-automation — 10x rule applied to identify high-value automation targets