I Replaced My Whole SaaS Stack With One App I Described in a Sentence. Here's What Happened.

For two years my business ran on four tools. Notion for notes and docs. Airtable for the client database. Zapier to move data between them. Typeform for the intake form on my site. Each one was the best at its job. Together they cost about $90 a month, and I'd have told you, proudly, that I'd built a "stack."

Last month I replaced all four with a single app I described in one sentence. I lost a few things I genuinely miss. But I gained the one thing none of those four tools could give me, and I didn't understand what it was until it was gone.

The subscriptions were never the real cost

When people complain about SaaS, they complain about the bill. That was never my problem — $90 a month is cheap for software that runs a business. The real cost was somewhere I never looked: the glue.

Notion didn't talk to Airtable. Airtable didn't talk to the form. So between every pair of tools sat a Zap — a little automation I'd wired up at some point, that moved a row here when a thing happened there. By the end there were eleven of them. And here's the part that should have scared me more than it did: my actual business process didn't live in any of the four tools. It lived in the glue between them. The Zaps were the company. And nobody, including me, could see them all at once.

The rule: a stack isn't four tools. It's four tools plus the invisible logic connecting them — and that connective tissue is where your real process lives, unversioned, undocumented, and understood by exactly one person.

The day the glue broke silently

Here's what happened, and it's the whole reason I'm writing this.

One of my eleven Zaps stopped firing. Not with an error — Zapier emailed me nothing, because from its point of view nothing failed. A field I'd renamed in Typeform no longer matched the field the Zap was looking for, so it just... quietly did nothing. New leads came in through the form, landed in a void, and never made it to the Airtable database I actually looked at every morning.

I found out three weeks later, when a client emailed to ask why I'd never followed up on her enquiry. There were nineteen more behind her.

That's the failure mode of a stack. It doesn't crash. It leaks. And it leaks in the seams between tools, which is precisely the place no single tool is responsible for watching.

The rule: every tool in your stack is reliable on its own. The risk isn't in the tools — it's in the gaps between them, and the more tools you add, the more gaps you're quietly betting your business on.

What I actually replaced it with

So I did something that two years ago would have sounded absurd. I described the whole thing in a sentence — "an intake form clients fill out, that drops them into a database I can see and sort, with a dashboard showing this week's new enquiries" — and had a working app built and deployed from that description. One thing. One place. The form, the database, and the dashboard were no longer three products with glue between them; they were one app where the data never had to cross a border.

The eleven Zaps didn't get migrated. They stopped existing. There was no "between" left for them to live in.

The rule: the fix for fragile glue isn't better glue. It's removing the seams — when the form and the database are the same app, there's no automation to silently break, because nothing has to be moved from one place to another.

Be honest about what I lost

I'm not going to pretend this was free. A stack of best-in-class tools gives you things a single purpose-built app doesn't, and if I skip that part you should stop trusting me.

• Notion's editor is still better than anything I'd describe into existence. For long-form writing, I still open Notion. I didn't replace that; I replaced the part of it that was pretending to be a database.
• I lost the ecosystem. Templates, integrations, the Zapier library of 6,000 apps — when you leave the stack, you leave all of that. If I need to connect to some third-party service tomorrow, I have to build that, not click it.
• The community and the muscle memory are real. Two years of knowing exactly where everything is in Airtable is worth something, and I threw it away on purpose.

So this isn't "SaaS is dead, delete your subscriptions." It's narrower and truer than that: a general-purpose tool bends your work to fit a shape built for everyone. That's a fair trade when you're starting and don't know the shape yet. It stops being fair the day you know exactly what your process is — because then you're paying, in glue and in leaks, to keep using a tool that was never built for you.

The thing I actually gained

Here's what I couldn't see until the stack was gone. For two years I'd been bending my business to fit my tools — structuring the client data the way Airtable wanted, shaping my intake around what Typeform could ask, routing everything through what Zapier could connect. I thought I was building a process. I was mostly negotiating with four products.

The app I described does exactly what my business does and nothing else. There's no field I'm not using, no feature I'm working around, no seam for a lead to fall through. When my process changes, I change the app — in another sentence — instead of re-wiring five automations and praying the glue holds.

The rule: a stack is a pile of tools built for everyone. An app is one tool built for you. For a long time you can't tell the difference, because the stack works — right up until the day the glue leaks and you realize you never actually owned your own process.

How I'd think about it if you're running a stack right now

I'm not telling you to burn it down this afternoon. I'm telling you to go find your glue.

• Count your automations. If you have more than a handful of Zaps / Make scenarios / scripts holding your tools together, that count is your real complexity. Not the number of tools — the number of seams.
• Ask where a lead could leak. For each seam, ask what happens if it silently stops. If the answer is "I wouldn't find out for weeks," you've found the thing that's actually at risk.
• Notice where you've bent to the tool. Any place you've shaped your work around what the software can do, rather than the other way around, is a candidate for replacement — not because the tool is bad, but because it was built for someone who isn't you.
• Replace a seam, not everything. You don't have to leave the whole stack. Collapse the two tools with the ugliest glue between them into one app first. That's where the leak was anyway.

The tool I built this on is Xenition — our AI workspace, a Flutter app on iOS and Android. I describe the tool I want in plain language and it builds and deploys the working app, real database and a real URL, no stack to wire together. It didn't make me more organized; I was plenty organized. It removed the seams where "organized" used to leak.

Two years of stack ran my business and lost me twenty leads in a gap I couldn't see. The one app I described in a sentence has never had a gap to lose them in — because there's no between left.

What's the silliest thing your stack's glue ever broke, and how long did it take you to notice? I'll go first in the comments. 👇