Killing CalendarBridge and RankPill: An Honest Audit of My Setapp Stack

Subscription creep starts with "just one more tool"

I did not "suddenly" notice subscription creep.

It was slower than that. One more SaaS trial. One more $5 utility that "pays for itself." One bundle that felt like free money because Look how many apps I get.

Then I killed two very specific things: CalendarBridge and RankPill. That was the trigger. After cancelling those, I took a hard look at my Setapp stack. Not just what I had installed, but what I actually use, and what I could replace with defaults or a one-time license.

This is that audit. Raw, slightly uncomfortable, but honest.

Why CalendarBridge and RankPill had to go

CalendarBridge was supposed to solve a simple problem.

I run multiple calendars across different accounts. Coaching, client calls, personal stuff, and the weird buffer I keep around deep work. CalendarBridge promised to sync them, keep things in one place, and avoid double booking.

What I got in practice was one more thing to maintain.

• Yet another settings UI
• Debugging "why is this event duplicated again"
• A background anxiety that my sync layer might be lying to me

It worked. But it also made my setup more fragile. When you chain systems together, you do not pay with dollars. You pay with trust.

So I did something boring instead. I picked a primary calendar account, pushed everything there, and tightened how I share booking links. No clever sync. Just one source of truth and a couple of manual checks.

RankPill was similar, but for SEO.

It tracked rankings, gave graphs, and nudged me to "optimize" when, honestly, I should have been writing or shipping. I realised I do not want another dashboard telling me I am 6 places lower on a keyword I barely care about.

When I cancelled RankPill, nothing broke. Traffic did not fall off a cliff. My stress level dropped a few notches though.

Those two cancellations were enough to make me look harder at my whole tool stack. Especially Setapp.

Setapp is brilliant, until it quietly stops being

I actually like Setapp.

For a builder who lives on macOS, it feels like toolbox mode. You get a ton of utilities that scratch specific itches. Clipboard managers. Markdown editors. Screenshot tools. You know the vibe.

The problem is not Setapp itself. The problem is what it does to your behaviour.

• You install apps "just to try" because you have already paid.
• You keep using mediocre tools because switching feels like work.
• You avoid paying once for something great because the bundle exists.

That is subscription creep in disguise. Not obvious cost. Quiet friction.

So I did a full audit of my Setapp stack. I went through each app, one by one, and forced a decision: stay, go, or graduate to a one-time alternative.

The audit rules I used

I set stupidly simple rules. No nuance. Nuance is how you keep everything forever.

• Rule 1: If I had not opened it in 30 days, it was gone.
• Rule 2: If macOS could do it natively with a bit of config, I ditched the app.
• Rule 3: If I relied on it daily, I wrote down what would happen if Setapp disappeared tomorrow.

Rule 3 was the real one. I treated Setapp like a startup that might close. If they turned off the servers next week, which workflows would actually hurt?

Here is how it broke down.

Category 1: The non-negotiables

There were a few apps inside Setapp that I use daily without thinking. Muscle memory level.

For me that list looked like:

• CleanShot X for screenshots and screen recording
• Paste as a clipboard manager
• Bartender to tame menu bar clutter
• BetterZip for working with client archives

If Setapp disappeared, I would immediately buy standalone licenses for these. No hesitation.

That is the benchmark. If I am not willing to pay for it outside the bundle, it is not a non-negotiable. It is a nice to have that came along for the ride.

I wrote down the one-time or direct subscription prices for the non-negotiables. That gave me a "break glass" cost. Useful reality check.

Category 2: The zombie apps

Next were the zombies. Apps I installed, used for a week, then abandoned.

They were still there. Still updated. Still cluttering Launchpad. Mentally they were free because I "already pay for Setapp." Monetarily they were not free at all.

Some examples from my list:

• A to-do app I flirted with, then dropped when I went back to my main system
• A note taking tool I used to import stuff, then forgot
• Yet another menu bar monitor that told me I was tired

Deleting them felt good. Not because I saved money right away, but because I removed distractions. Every app you keep installed is an open loop in your head. "Maybe I should use that more." No. You should not. If it mattered, you already would.

Category 3: The ones I replaced with defaults

This category annoyed me the most.

These were apps that did something slightly nicer than macOS, but not enough to justify permanent rent in my brain.

For example:

• Simple calendar widgets that duplicated what the stock Calendar app + Notification Center can already do
• Lightweight text editors that did nothing my existing setup could not handle
• Disk cleaning and maintenance tools that mostly overlapped with built-in features

For each of these, I forced myself to rebuild the same workflow with native tools or a single paid app.

Sometimes that meant learning a keyboard shortcut I had ignored for years. Sometimes it meant accepting that the built-in UI is uglier but perfectly fine.

Default tools are boring. They are also stable, documented, and usually supported for the lifespan of the OS. That matters more than a pretty toggle switch.

Category 4: The graduates

This category was interesting.

Some Setapp apps are excellent, but I realised I would rather own them outright than rent them indirectly.

For me this was mostly focused tools that I knew I would still want in five years. Stuff that is part of my identity as a builder, not just a seasonal habit.

Example approach:

• Check if the app offers a direct license outside Setapp.
• Look at my usage: daily or weekly?
• If it is core to how I work on client projects, coaching material, or experiments, buy the license and decouple it from Setapp.

I think this is the healthy middle ground. Use Setapp to discover and stress test tools. When one of them becomes critical, graduate it and own it.

That way the bundle stops being a silent dependency and turns into a proving ground.

Where CalendarBridge and RankPill fit into this

Dropping CalendarBridge and RankPill made this audit easier emotionally.

They reminded me that tools are not neutral. They shape your behaviour and your risk profile.

• CalendarBridge taught me that sync layers add fragility.
• RankPill taught me that metrics without clear decisions are just anxiety fuel.

Once I saw that, I spotted similar patterns in my Setapp apps.

An example: I had a "daily stats" app hooked to various APIs. It looked cool. It showed numbers. It did not drive actions. That is RankPill energy. Gone.

Another one: a cross service notes helper that promised easy capture into anything. In reality it was a sync layer waiting to break. That is CalendarBridge energy. Also gone.

I realised I prefer hard boundaries between systems. Less clever glue, more deliberate movement of information. Yes, that means a few more manual steps. It also means fewer weird bugs at 23:00 when I am trying to prep for the next day.

How I judge a tool now

After the audit, I tweaked my personal criteria for new tools, especially subscriptions.

Here is how I look at it:

• Does this reduce friction I actually feel, or just hypothetical friction?
• Can I explain, in one sentence, what decision this tool helps me make faster?
• Is there a non-subscription way to get 80% of the benefit?
• If it vanished tomorrow, would I be properly screwed, mildly annoyed, or secretly relieved?

Secret relief is a red flag. That means the tool is not helping. It is nagging.

For calendar stuff, this pushed me toward simpler setups. One main calendar, aggressive use of default apps, and fewer API middlemen in the way.

For SEO, it pushed me toward batch checks and slower feedback loops. I would rather review search console once a week than get nagged every day that one keyword wobbled.

The money side is boring, but real

I wish I could say I saved some dramatic amount of money. I did not.

Cancelling CalendarBridge and RankPill saved a handful of euros each month. Trimming Setapp usage did not change the subscription price at all. The spreadsheet story is boring.

The part that changed is harder to quantify.

• Fewer random notifications.
• Less context switching to "check on" tools.
• Cleaner mental model of what does what.

As a developer and coach, my main resource is attention. Not storage. Not bandwidth. Paying for tools that eat attention is insane.

I will happily pay for boring stability. I will not keep funding another shiny sync layer that inserts itself between me and reality.

How I think about Setapp now

After the audit, I did not cancel Setapp.

That might sound anticlimactic, but it is honest. The bundle still makes sense for me, with strict boundaries.

This is how I treat it now:

• Discovery sandbox, not permanent home.
• Trial environment for serious apps I might later buy outright.
• Source of a few core utilities that would cost more individually.

What I stopped doing is this:

• Installing every interesting icon I see in the catalog.
• Keeping overlapping tools around "just in case."
• Letting Setapp define my stack by default.

I want fewer tools that I know deeply, not more tools that make me feel "equipped." That is the real lesson I pulled from killing CalendarBridge and RankPill.

If you want to run your own audit

If you are also neck-deep in subscriptions and bundles, here is a simple way to copy what I did without turning it into a productivity cosplay weekend.

1. List all the apps in your bundle or main tool stack.
2. Mark ones you have not opened in the last month and delete them immediately.
3. For the rest, ask: would I buy this tomorrow if you took it away?
4. For every "no," find a default or one-time alternative, or admit you do not need it.
5. Graduate the few that are mission critical and buy them directly when it makes sense.

Do not overthink it. The point is not the perfect stack. The point is to make sure your tools are pulling their weight instead of quietly charging rent.

Dropping CalendarBridge and RankPill just made that visible for me. You probably have your own equivalents. Find them, kill them, then look at what is left with clear eyes.

The subscriptions that survive that process are usually the ones that deserve to.