Bountymon
News 5 min read

Clockwise Is Dead. Salesforce Killed It. You Shouldn't Be Surprised.

Clockwise, the calendar productivity tool used by Uber, Netflix, and Atlassian, is shutting down next week after being acquired by Salesforce. Here's why this keeps happening — and what you can do about it.

By Bountymon 2026-03-20

Another week, another SaaS product getting the axe after an acquisition. This time it’s Clockwise — the scheduling tool that helped teams carve out focus time, protect their calendars, and stop drowning in meetings. Used by Uber, Netflix, and Atlassian. Eight million hours of focus time created. Gone next week.

The Postmortem

Clockwise announced this week that the team is joining Salesforce and the product will shut down on March 27, 2026. Less than two weeks’ notice for customers who’ve built their workflows around the tool. The announcement is wrapped in the usual corporate language: “next chapter,” “excited about this move,” “even greater impact.” Nobody believed it.

Let’s read between the lines. Salesforce didn’t buy Clockwise for the product. They bought the team — specifically their “deep expertise in building reliable, agentic software.” The product? Collateral damage. The customers? A footnote.

This isn’t new. It’s not even surprising anymore. It’s just the latest entry in a long, depressing list:

  • Google acquired and killed hundreds of products. Remember Google Reader? Inbox? Google+?
  • Salesforce itself has a track record. Remember Quip? Still exists technically, but good luck finding anyone who uses it as intended.
  • Microsoft absorbed Sunrise calendar, Wunderlist, and others. Some features survived. The products didn’t.

Why This Keeps Happening

The economics are straightforward. When a bigger company acquires a smaller one, the math rarely favors the product:

  1. The team is the real asset. Clockwise’s value to Salesforce isn’t its scheduling algorithm — it’s the people who built it, particularly their experience with “agentic software” (the current buzzword for AI that can take actions autonomously).
  2. Maintenance costs money. Even a profitable SaaS product has servers to run, customers to support, and a codebase to maintain. For Salesforce, that’s overhead they don’t need.
  3. Integration is a trap. Sometimes the buyer promises to fold the product into their platform. Sometimes they do. Usually, the original vision gets watered down beyond recognition.

Clockwise customers now have until March 27 to export their data, find alternatives, and rebuild their scheduling workflows. For teams that built processes around focus time blocks and calendar optimization, that’s not a small lift. It’s a disruption that costs real time and real money.

The Real Cost of “Free” SaaS

Here’s the thing that gets missed in the acquisition postmortems: the switching costs were always there. Every time you adopt a SaaS tool, you’re placing a bet that the company will stick around, maintain the product, and not sell out to someone who’ll kill it.

For Clockwise users, that bet just didn’t pay off. The company had a decade of momentum, impressive enterprise customers, and a product people genuinely liked. None of that matters when the acquirer’s priorities don’t align with yours.

This is the subscription fatigue people talk about, but worse. It’s not just about paying too many monthly bills. It’s about the dependency tax — the hidden cost of building your workflows on someone else’s platform, with someone else’s priorities, and someone else’s exit strategy.

What You Can Actually Do

There are alternatives. There are always alternatives. But the right move isn’t just to switch to the next SaaS tool and hope it lasts longer.

Consider self-hosting where it makes sense. For scheduling, for project management, for the tools that form the backbone of your team’s workflow — ask whether you need a cloud service at all. Open-source alternatives like Rallly, Cal.com (open-source core), or even a combination of standard calendar tools with custom scripts can do what most scheduling products do, without the dependency risk.

Demand data portability. Before adopting any tool, ask: how easy is it to get my data out? If the answer involves support tickets and CSV exports that take weeks, that’s a red flag. Your data should belong to you, not your vendor.

Build what you can. Not everything needs to be a SaaS subscription. Clockwise’s core feature — protecting focus time on a calendar — is fundamentally a set of rules and scripts. For many teams, a few well-written automation rules accomplish the same thing without a third-party dependency.

Use bounty platforms for custom work. When the off-the-shelf tools don’t fit or you don’t trust them to stick around, commission exactly what you need. You own the code. You own the data. No one can shut it down except you.

The Pattern

Clockwise won’t be the last. The SaaS graveyard keeps growing, and the pace of acquisitions shows no sign of slowing. As AI capabilities make it easier to build software, we’ll see more tools launched, more acquired, and more killed.

The question isn’t whether the next Clockwise will happen. It’s whether you’ll be ready when it does.

Build your stack on foundations you control. Or get comfortable rebuilding it every few years when the next acquisition announcement drops. The choice is yours.


Clockwise customers have until March 27, 2026 to export their data. We’d recommend starting now.

saas vendor-lockin salesforce self-hosting acquisitions subscription-fatigue

Found this useful?

Share it with your team to start the conversation about SaaS savings.

Related Articles