How to automate the repetitive computer tasks you don't notice you're doing

Most people don't automate the tasks that cost them the most time. They automate the ones that are annoying to do manually — which is a different list. Annoyance and cost diverge constantly: retyping your email signature is annoying but cheap (maybe 4 minutes/week); clicking through the same six-step export process is boring but expensive (30+ minutes/week and you've stopped noticing it as a task at all).

We're going to rank four automation categories by payoff — time saved per week divided by setup time — using real ranges, not hypotheticals. The point isn't "automate everything." It's knowing which five minutes of setup are worth it and which aren't.

The four tools, and what they're actually for

• Hotkeys — remapping or assigning keyboard shortcuts to actions you already do with a mouse. Fixes navigation friction.
• Text expanders — typing a short string that expands into a longer one (snippets, templates, boilerplate). Fixes retyping friction.
• Scripts (shell scripts, AppleScript, AutoHotkey, Python + a scheduler) — chaining multiple steps into one trigger. Fixes sequence friction — when a task is five clicks that are always the same five clicks.
• Browser/OS extensions — pre-built automations someone else wrote, for common patterns (ad blocking, tab management, form filling, download sorting). Fixes friction you didn't build the fix for yourself.

Each has a different setup cost and a different ceiling. The ranking below assumes a task that occurs somewhere between daily and a few times a week — automating something you do once a month almost never pays off, no matter how annoying it is.

Ranked by payoff-per-minute-invested

The arithmetic that matters: a hotkey setup costing 15 minutes that saves 20 minutes/week breaks even inside one week and is pure profit after that. A script costing 90 minutes to build that saves 20 minutes/week takes 4.5 weeks to break even — fine if the task is permanent, a waste if you switch tools or jobs in six weeks.

This is why scripts are ranked last despite often having the highest ceiling. They have the highest setup cost and the highest failure rate (a script breaks when the underlying app updates; a hotkey rarely does). Build scripts only for tasks you're confident will still exist in three months.

Where the time actually goes: find leaks before you fix them

The reason "automate your repetitive tasks" is common advice and rarely acted on is that most repetitive tasks are invisible by the time you're doing them for the 200th time. You've stopped registering the six-click export as six clicks — it's just "exporting," a single mental unit that happens to cost 90 seconds instead of 8.

Task-interruption and habituation studies consistently find that once an action sequence becomes automatic, people underestimate both its frequency and its duration — sometimes by half or more. You genuinely don't know if you switch tabs 40 times an hour or if your "quick check" of email averages 90 seconds or 4 minutes. That's not a discipline problem; it's a measurement problem, and it's why guessing which tasks to automate usually means automating the wrong ones.

If you want the actual numbers instead of a guess, a background usage log for a week — app switches, window durations, repeated sequences — will surface the candidates a lot faster than introspection does. That's the entire premise behind the free watcher: it runs locally, logs what you actually do, and hands you a list ranked by frequency × duration instead of by how annoying something felt in the moment.

The hotkey audit: cheapest wins, five minutes each

Before touching a script, do this. Open whatever app you use most and count how many actions you currently perform with the mouse that have a keyboard equivalent you've never learned, or don't have one you could assign.

1. Window snapping/switching — if you drag windows to resize or click taskbar icons to switch, that's 2–4 seconds per instance, dozens of times a day. A snap hotkey (built into Windows/macOS, or via a free utility) turns that into under half a second.
2. The 3–5 actions you repeat inside your main app — new tab/document, save-as, find, a specific menu command buried two levels deep. Most apps let you assign these; most people never check.
3. Clipboard history — if you've ever copied something, copied something else, then needed the first thing back, a clipboard manager hotkey (Cmd/Win+Shift+V equivalents) eliminates the "redo the work" tax entirely.

None of this requires software beyond what's often already installed. Setup time is minutes. This is why it tops the ranking — not because it saves the most time in absolute terms, but because it's nearly risk-free.

Text expanders: the compounding case

Text expansion looks small per-instance and large in aggregate, which is exactly the kind of leak that's easy to underestimate. If you type a variant of the same sentence — a scheduling reply, a status update, a code comment header — more than 3 times a week, it qualifies.

Concrete example: a 40-word boilerplate reply typed at 40 WPM takes 60 seconds. Expanded from a 4-character trigger, it takes under 2 seconds. At 5 uses/week, that's 4.8 minutes saved — modest. At 20 uses/week (common for support, sales, or recurring status updates), it's 19.3 minutes/week, or roughly 16 hours/year, for a setup that took under 15 minutes total across all snippets.

The failure mode isn't underuse — it's snippet sprawl. People build 40 expansions, use 6, and the other 34 become mental overhead ("wait, what was the trigger for that one?"). Cap it at your top 8–10 phrases and revisit monthly.

Scripts and extensions: build fewer, choose better

Scripts earn their keep only on tasks with a fixed, multi-step sequence that doesn't change week to week — file exports, backup routines, report generation, batch renaming. If any step requires judgment ("pick the right file," "decide the recipient"), it's a bad script candidate; you'll spend more time handling edge cases than the automation saves.

Extensions are the cheapest fix for patterns other people have already automated well: ad blocking, tab suspension, form autofill, read-it-later queues. The setup cost is installation, not engineering. The tradeoff is less control and a dependency on someone else maintaining it — check the update date before installing anything that touches your data.

If your leak-finding turns up a specific, recurring, high-frequency pattern that no existing extension covers and that doesn't vary, that's the signal to write a script. Everything else, use what's ranked above it.

Putting it together

The order that actually saves the most time for the least risk: audit hotkeys this week (free, ~20 minutes total), add text expanders for your top phrases (15 minutes, compounding payoff), install one or two extensions for patterns you recognize, and reserve scripting for the one task you're certain is permanent and mechanical. If you're not sure which task that is, that's a measurement problem before it's an automation problem — the AI daily brief exists specifically to name the leak and the fix instead of leaving you to guess.

FAQ