The Real Cost of "Free" AI Tools

Every AI vendor has a free tier now. It's a good deal until you build something real on it — and then the actual pricing model reveals itself.

The sticker price was never the point. The cost that matters is what it takes to leave, and that cost is set the moment you start depending on the tool. Here's how to do that math before you're committed instead of after.

The four costs of any tool

When you adopt a tool for a workflow, you take on four costs. Only one of them is on the pricing page.

1. Subscription cost. The monthly fee. Visible, predictable, usually small. This is the number people compare, and it's the least important one.

2. Switching cost. What it takes to move off the tool later — re-exporting data, rebuilding logic, retraining the team. This starts at zero and grows every week you use the tool. By the time you'd want to switch, this number is large by design.

3. Ceiling cost. What you lose when the tool can't do the next thing you need. Free tiers and consumer tools have low ceilings. You don't feel the ceiling until you hit it — and then it costs you the workflow.

4. Lock-in cost. The premium you pay because the vendor knows you can't leave. Price increases, feature paywalls, deprecated free tiers. This is switching cost weaponized.

A tool that's free on cost #1 and brutal on costs #2 through #4 is not a free tool. It's a loan with the interest hidden.

How "free" becomes expensive

The pattern is consistent, because the incentive is consistent. Free tiers exist to acquire you, not to serve you.

A vendor offers a generous free tier. You build a workflow on it. The workflow becomes load-bearing — your lead intake, your scheduling, your reporting now runs through it. Your switching cost is now high.

Then one of three things happens. The free tier shrinks. The feature you depend on moves behind a paywall. Or the pricing reorganizes around per-seat or per-run charges that scale with your usage. None of this is malicious. It's just the model: acquire on free, monetize on locked-in.

The tell is whether your data and your logic are portable. If you can export your data in a standard format and your workflow logic isn't trapped inside the vendor's proprietary builder, your switching cost stays low and the vendor has to keep earning you. If you can't, the vendor sets the price and you pay it.

The math, concretely

Say two tools can run the same workflow.

Tool A is a polished all-in-one platform. $0 to start, then $79/month once you pass the free tier. Workflow logic lives inside its proprietary editor. Data export is CSV-only and lossy.

Tool B is a self-hostable workflow engine. Maybe $0–20/month in infrastructure. Workflow logic is a portable file you own. Data lives in your own database.

On cost #1, Tool A and Tool B look similar — tens of dollars a month either way. On costs #2 through #4, they're not in the same category. With Tool A, the day you want to change vendors, you rebuild the workflow from scratch and hope the CSV export captured everything. With Tool B, you move the file and the database. One has a real exit. One doesn't.

The honest version of the comparison isn't "$0 vs $79." It's "a workflow I own vs. a workflow I rent from someone who can change the terms."

What this means for how you build

This isn't an argument against paid tools or managed services. Plenty of them are worth it. It's an argument for making the lock-in cost a visible line item in the decision.

Three questions, before you build anything load-bearing on a tool:

• Can I export my data in a format I could actually use elsewhere? Not "is there an export button" — is the export complete and standard.
• Does my workflow logic live somewhere I control? A portable definition you own, or a proprietary builder you rent.
• What happens to this workflow if the vendor triples the price or kills the free tier? If the answer is "we're stuck," you've found the real cost.

This is why we build client systems on a stack — n8n, Claude, Supabase — where the workflow definitions and the data are portable and owned by the client. Not because those tools are free. Because the exit is cheap, which means no vendor in the stack ever gets to set the price by force.

A tool you can leave has to keep earning you. That's the only pricing protection that actually holds.

If you're weighing a stack for a workflow and want a second read on where the lock-in is hiding, book a discovery call — bring the tools you're considering.