Avoiding tool sprawl

The failure mode this whole course guards against has a name: tool sprawl. It's the slow accumulation of AI subscriptions you signed up for with good intentions and barely use — each one a small monthly charge, a login to remember, and a context-switch that fragments your work. More tools feels like more capability. Usually it's the opposite.

Why sprawl hurts:

• Cost creep. Five forgotten $20/month subscriptions is $1,200 a year for tools you don't use. Individually small, collectively wasteful.
• Cognitive load. Every tool is something to learn, remember, and switch between. A sprawling stack fragments your attention; you spend more time deciding which tool than doing the work.
• Shallow use. When you spread across many tools, you never get good at any of them. Mastery of a few beats dabbling in many — you extract far more value from a tool you know deeply.
• Overlap. Half your tools probably do the same job. You don't need three writing assistants.

The discipline of a lean stack:

• Default to your general assistant. Before adding a specialized tool, check whether the general-purpose assistant you already pay for handles the job well enough. Often it does, and you've saved a subscription.
• One tool per job. Resist owning three tools for the same category. Pick the best fit and commit to learning it.
• Adopt against a real, recurring need — not because a tool is trending. If you can't name the specific repeated task a tool solves, don't subscribe.
• Prune regularly. Every quarter, review your subscriptions: what have you actually used? Cancel the rest without guilt. A subscription you're not using isn't an investment; it's a leak.
• Trial before you commit. Use free tiers and trials to confirm a tool earns its place before the recurring charge starts.

The counterintuitive truth: a smaller stack usually makes you more productive, not less. The goal is a handful of tools you use deeply and combine well — not a drawer full of gadgets. When you feel the pull to add "just one more" trending tool, ask what recurring job it does that your current stack can't. If you can't answer crisply, that's your answer.