Why Founders Keep Rediscovering Emacs After the SaaS Tools Fail Them

I've paid for Notion. I've paid for Roam. I've paid for Obsidian Sync, Craft, Bear, and at least two AI-powered "second brain" apps whose names I can no longer remember without checking my old credit card statements. Every single time, I told myself this was the one. Every single time, I ended up back in Emacs.

This isn't a nostalgia piece. I'm not romanticizing a 40-year-old editor because I'm too stubborn to learn new tools — I learn new tools constantly, it's basically my job. This is about what actually survives contact with running a business for years, and why so many founders and engineers I know have the exact same story: try everything, land on Emacs, stay there.

The pattern is more common than you'd think

Talk to enough technical founders and you'll notice it: a meaningful chunk of them, at some point, quietly give up on the note-taking app treadmill and go back to plain text. Usually Emacs or Vim, usually with some flavor of Org-mode or Markdown, usually after a multi-year detour through every venture-backed productivity app that promised to organize their brain.

It's not random. It's a predictable failure mode of tools built by companies with different incentives than yours.

The SaaS note-taking tool life cycle

Here's the pattern I've watched repeat, tool after tool:

Year one: delight. The tool is fast, the UI is gorgeous, someone on Twitter is evangelizing a workflow that looks like it'll finally fix your brain. You migrate everything. You feel very productive for about six weeks.

Year two: friction. The company raises a round, or doesn't, and either way the roadmap shifts. Features you rely on get deprioritized in favor of whatever drives new signups. Sync gets flaky. The mobile app diverges from desktop in ways that make your notes feel less trustworthy.

Year three: the exit tax. You want out, and discover that "your notes" were never really yours. Export is degraded, proprietary formatting doesn't survive the trip, backlinks turn into dead links, and years of structured thinking becomes a folder of lossy Markdown or — worse — HTML soup.

Multiply that by three or four tools over a decade and you get a founder who has been burned enough times to stop trusting anything with a login screen and a pricing page.

Why Emacs doesn't have this problem

Emacs isn't better because it's old. It's better because of what "old" actually buys you here:

Plain text doesn't get acquired. An Org file is just text. No company can shut it down, change its business model, or gate it behind a new tier. The format has been stable since before most SaaS note apps existed, and it'll be readable long after most of them are gone.

No sync service between you and your notes. Your files live on your disk. You can put them in Git, Dropbox, a USB stick, whatever — but there's no vendor-owned sync layer that can silently degrade, rate-limit you, or hold your data hostage during a pricing dispute.

It's programmable, not configurable. Every SaaS tool gives you settings. Emacs gives you a Lisp interpreter. When a workflow doesn't fit how you think, you don't file a feature request and wait — you write forty lines of Elisp on a Sunday and it's yours forever.

The learning curve is a moat, not a bug. Yes, Emacs is harder to pick up than a polished app. But that same friction means the tool doesn't get redesigned out from under you every eighteen months to chase engagement metrics. What you learn stays true.

This isn't really about text editors

The deeper thing going on here is a founder finally noticing a pattern: tools built to maximize someone else's growth metrics are structurally unreliable for something you need to last a decade. A notes app funded by venture capital has to grow. Growth means new features, new pricing tiers, new UI, eventually an acquisition or a shutdown. None of that is aligned with "I just want the same reliable place to think for the next ten years."

Plain text and Org-mode don't have a growth target. They don't need you to invite teammates or upgrade to a paid tier to keep functioning. That's not a coincidence — it's the whole point.

Where this leaves me

I still use SaaS tools constantly — for anything that genuinely benefits from being a hosted, collaborative, disposable-if-needed product. But for the stuff I need to survive as long as Chrometa does — architecture decisions, long-running task lists, drafts of pieces like this one — it all lives in Org-mode now. No sync outage has ever cost me a note. No pricing change has ever locked me out of my own thinking.

If you're a founder who's cycled through the same graveyard of note apps I have, it might not be a discipline problem. It might just be that you've been trying to build something permanent on top of tools that were never designed to be.

Have a favorite plain-text workflow, or a war story about losing years of notes to a tool that got shut down? I'd genuinely like to hear it.