Leases, Not Vows: Build a Workflow That Can Walk Away From Any App

The tool you love today is going to change. Not because it's bad — because companies get bought, pricing tiers get reshuffled, products get folded into a bigger suite, and the one feature that made the whole thing worth signing up for quietly stops getting updates. Google Reader has been gone since 2013 and people still bring it up, which tells you something about how much a dead app can sting.

The shutdown itself usually isn't the disaster. The disaster is the shape of the workflow you built around it: the automations pointing at an API that no longer exists, the attachments living only inside someone else's database, the six years of records with no way out except screenshots.

So here's the reframe that makes all of this manageable. Treat every tool as a tenant, not an owner.

What the tenant mindset actually means

A tenant doesn't distrust the building. They just know which boxes are theirs, where the exit is, and how long it would take to move. Renting is not cynicism — it's basic awareness of where your stuff lives.

The opposite is what most of us do by default: we let a vendor hold the only copy of something important, in a format only they can open, and we call that "our system." That's not a system. That's a bet.

The portability test: four questions, five minutes

Run this before you adopt anything that will hold real work. It's not a scoring rubric — it's a filter for the tools you're about to depend on.

1. Can I get everything out, in a format something else can read?

Not "is there an export button." Ask what the export contains. A CSV of tasks is portable. A folder of PDFs is readable but not rebuildable. A zip that drops your attachments entirely is a receipt, not a backup. If the export only produces a proprietary file that reopens in the same app, you don't have an exit — you have a souvenir.

2. Where does the data physically live?

Two flavors, both fine, different consequences. Local-first tools keep files on your disk, which makes migration trivial and sync your problem. Cloud tools keep them on a server, which is convenient and means your access is a business relationship that can be renegotiated. Neither is wrong. Knowing which one you're in is the point.

3. What breaks the day the API goes dark?

If a workflow only runs because two apps can talk to each other, sketch what the manual fallback looks like. If the answer is "there isn't one," you've found the fragile seam. Sometimes that's an acceptable risk for something low-stakes. It's rarely acceptable for something you'd have to reconstruct from memory.

4. What's the rebuild estimate?

Be honest and specific. If moving this out would take an afternoon, you're renting. If it would take a month of evenings, you're not a customer — you're a hostage with a login. The number doesn't need to be zero. It just needs to be one you've looked at.

Habits that make a shutdown boring

Tests are cheap; habits are what actually hold up. A few that have earned their keep:

• One canonical home per record type. Notes live in one place. Tasks live in one place. The moment the same document exists in three apps, you've created a merge problem you'll pay for later.
• Keep a thin plain-text layer. Markdown files for notes, a CSV for the address book, an ICS feed for the calendar. Plain text is the cockroach of formats — it survives everything.
• Siphon once a month. A recurring calendar block that exports the important stuff into a folder you own. It takes ten minutes and it means you're never more than thirty days from a usable copy.
• The one-hop rule. Automations may pass through exactly one intermediary. When a chain gets three services deep, nobody remembers what it does, and the failure is silent.
• Write the runbook. One page: what we use, why we chose it, who has the admin login, and where the escape hatch is. Future you will not remember any of this, and future you is the one who'll be doing the migration at 11 p.m.
• Prefer tools that read standard formats. A calendar app that imports ICS. A notes app that opens markdown. Boring compatibility is an underrated feature, mostly because it never shows up on a marketing page.

The honest cost

None of this is free. You'll occasionally pick the slightly duller tool because it exports cleanly. You'll have an extra folder on your drive. You'll spend a few minutes asking a sales page a question it doesn't want to answer.

That's the whole premium, and it's small. What you get in exchange is a weird kind of calm: the knowledge that if the app you're using today announces something unfortunate next spring, your week gets mildly disrupted instead of your quarter getting torched.

You'll still get surprised. Everyone does. The goal isn't to predict the shutdown — it's to make sure the shutdown has nothing to take from you but a subscription.

Sign short leases. Keep your boxes packed enough to move.