I Killed Five Subscriptions This Year and My Stack Got Better

Last January I opened my bank statement with a spreadsheet and a sense of dread. Between SaaS subscriptions, cloud accounts, and 'free' tools that had quietly crossed into paid, my solo dev stack was costing more than my car insurance. So I did something radical: I deleted things.

Five tools went out the door this year. Here's the honest accounting — the savings, the pain, and what replaced them.

1. The Project Management SaaS Nobody Updated

Cost: $24/month

I had a Kanban board for a one-person team. Read that again. I was assigning tickets to myself and moving them between columns like a middle manager of one.

Replaced with: A plain markdown file and a weekly review. Seriously.

Friction: Two days of exporting tasks and grieving. Then a strange realization — I'd been doing project management instead of projects. The markdown file has three sections: doing, done, blocked. That's it. That's the whole methodology.

2. The All-In-One Monitoring Platform

Cost: $39/month

Beautiful dashboards. Gorgeous graphs. I could see the P99 latency of an app that gets maybe 200 visitors a week. What I couldn't see was whether the site was up.

Replaced with: A $3 uptime checker and application logs I actually read.

Friction: Minimal, because honestly, what was I monitoring? My observability stack had more lines of configuration than my application had routes. The dashboards were decoration — professional-looking anxiety.

3. The Design Collaboration Tool

Cost: $15/month

I'm a developer. I was paying for a design tool to make buttons that look fine. The subscription survived on pure guilt — 'someday I'll learn proper design workflows.'

Replaced with: Stealing colors from sites I like and a folder of SVG icons.

Friction: Zero. Turns out I wasn't using the tool. I was using the idea of the tool.

4. The Second Analytics Platform

Cost: $19/month

I had Google Analytics AND a privacy-focused analytics tool, because I couldn't decide which one to trust. So I paid for the privilege of indecision. Two dashboards, both telling me roughly the same thing: not many people visit.

Replaced with: The privacy-focused one, kept. Google Analytics, deleted.

Friction: Ten minutes removing a script tag. The hardest part was admitting I'd been paying $228 a year to not make a decision.

5. The Password Manager I'd Outgrown

Cost: $60/year, plus a family plan I talked myself into

This one hurt because password managers are genuinely important. But I'd stacked a family plan for relatives who were still using 'password123' in a notes app. I was subsidizing security theater.

Replaced with: A cheaper individual plan and one very patient Sunday afternoon teaching my dad the basics.

Friction: Emotional, mostly. Also: migrating 300+ credentials is exactly as fun as it sounds.

The Numbers

Total saved: roughly $187 a month, or about $2,200 a year. That's a decent laptop. That's a conference trip. That's actual runway for the side project the tools were supposedly supporting.

But the real gain wasn't money. It was cognitive. I hadn't realized how much background load came from maintaining five logins, five billing cycles, five sets of notifications, five things to think about when choosing a new project's architecture. A smaller stack means every tool actually gets used, understood, and configured properly.

The Rule I Use Now

Before any tool enters my stack, it has to answer one question: what decision does this tool let me make that I can't make without it? If the answer is 'organize information I could organize in a text file,' it doesn't get a subscription. It gets a folder.

Tool fatigue isn't a personal failing. It's the predictable result of an industry that sells solutions to problems you didn't have yet. The best upgrade I made this year wasn't adding anything. It was subtraction.