How can ai help with writing?
FIELD NOTE · COVER · APR 29, 2026 · ISSUE LEAD
FIELD NOTE·Apr 29, 2026·8 MIN

LLMs Over Tools: The Quiet Migration

Same browser, new name, hard floor on what your stack is allowed to depend on.

Tom Reilly·
FIELD NOTEAPR 29, 2026 · TOM REILLY

I’d finally had enough, and as one of my New Year’s resolutions for 2026, I’ve done my level best for the last four months to switch to as many LLM-free apps and options as is realistically possible.

Thomas Wilde, Freelance Gaming Journalist

What AutoKaam Thinks
  • LLM creep isn't just in your head. Vendors are baking it into tools you already pay for — and charging you for it anyway.
  • The real cost isn't the tool. It's the retraining, the muscle-memory loss, the support tickets from staff who just want to do their jobs.
  • LibreOffice fixed its .docx issue without fanfare. If they can do it quietly, so can your next vendor — and they won’t tell you.
  • Budget four weeks per core app to migrate. Six if it touches client deliverables. Don’t wait for the forced update to surprise you.
four months
Migration window
LLM-HEAVY VENDORS vs SMB OPERATORS
Named stake

If you run a fifty-person firm in the same category, here is the operator's read. One freelance journalist just stripped AI out of Chrome, Office, Photoshop, and Gmail. He didn't do it because he’s anti-tech. He did it because the tools stopped working. The stack became slower. The interfaces cluttered. The outputs unreliable. He migrated to Vivaldi, Waterfox, LibreOffice, Paint.net, and Notetab Light, all LLM-free, and rebuilt his workflow in four months.

You’re not behind if you haven’t adopted AI. You’re ahead if you haven’t been forced out of your stack.

This isn’t a story about resistance. It’s a story about forced migration. And if you think it won’t hit your payroll, your CRM, or your design suite, you’re already late.

The Deployment

Thomas Wilde, a freelance gaming journalist based in the Pacific Northwest, spent the first four months of 2026 replacing every major tool in his stack that had integrated AI features. He moved from Chrome to Vivaldi because Gemini kept hijacking his workflow with prompts he didn’t ask for. He left Firefox for Waterfox after Mozilla announced plans to go “all-in” on AI agents. He dropped Photoshop for Paint.net, not because it’s better, but because it does one thing, image editing, without trying to sell him a chatbot. He kept using LibreOffice, which quietly fixed its long-standing .docx compatibility issues, and works flawlessly with clients who still live in Microsoft’s world.

He didn’t do this for performance. He did it because the tools stopped serving him. They started serving the vendor’s AI roadmap.

His replacements aren’t flashy. Vivaldi is a privacy-focused browser that doesn’t force AI into your tabs. Waterfox is a 15-year-old fork of Firefox that strips out telemetry and AI integrations. Paint.net is a 20-year-old freeware image editor with a Web 1.0 website and zero AI features. LibreOffice is open-source office software that now handles .docx without corruption. Notetab Light is a plain-text editor that doesn’t try to rewrite your sentences.

These tools don’t have roadmaps full of “agent orchestration” or “context-aware workflows.” They do the thing they were built to do. And for a solo operator, that’s enough.

[[IMG: a freelance writer in a home office switching from Chrome to Vivaldi, with AI prompts cluttering the old browser window and a clean interface on the new one]]

Why It Matters

This isn’t about one guy ditching AI. It’s about the cost of forced adoption.

Every major vendor is layering AI into existing products, not as an add-on, but as a core dependency. Chrome injects Gemini. Microsoft wraps Copilot around every Office click. Adobe pushes Firefly into Photoshop’s toolbar. These aren’t optional anymore. They’re in your face. And if you don’t use them, you’re fighting your own software.

For operators, this means:

  • Training cost goes up. Every time a tool changes its interface, you retrain staff. Not once. Every time.
  • Support load increases. “Why is there a chatbot in my spreadsheet?” is now a Tier 1 ticket.
  • Vendor lock-in tightens. You can’t leave if your files are tied to AI-generated metadata or proprietary formats.
  • Budgets get hijacked. AI features come with AI pricing. You’ll pay per seat, per call, per token, even if you don’t use it.

Wilde’s migration is a warning shot. He didn’t have an IT team. No procurement process. No change-management committee. He just hit a wall and walked away. Most SMBs don’t have that luxury.

But they also don’t have to wait for the breaking point.

The real story here isn’t the tools he left. It’s the tools he found. LibreOffice now handles .docx. That wasn’t true two years ago. Waterfox runs Firefox extensions without the bloat. Vivaldi lets you disable AI prompts at the browser level. These are real alternatives, and they’re getting better.

The market is responding to AI fatigue. Quietly.

And if the market is responding, operators should be testing.

What Other Businesses Can Learn

You don’t need to go full LLM-free. But you do need a plan.

Start with this: every SaaS tool your team uses should be audited for AI creep. Not next quarter. Now.

Ask these questions:

  • Does the tool force AI features into the UI?
  • Is there a way to disable them permanently?
  • Does the contract charge extra for AI use, even if you don’t use it?
  • Can you export your data in a clean, non-proprietary format?

If you can’t answer yes to the last three, you’re at risk.

Then, test alternatives.

For browsers: try Vivaldi or Brave. Both block AI prompts by default. Brave also strips out crypto junk. Don’t wait for Chrome to force Gemini into your internal dashboards.

For office suites: LibreOffice is viable. It handles .docx, .xlsx, and .pdf exports without corruption. Importantly, clients can’t tell the difference when they open your files. Use it for drafts. Use Microsoft 365 only when you have to send to a client who demands it.

For image editing: Paint.net or GIMP. Both are free. Both do basic edits without trying to “enhance” your image with AI hallucinations. Keep Photoshop only if you need PSD layers, and even then, consider exporting to TIFF or PNG before sharing.

For note-taking: Notetab Light, Obsidian, or plain .txt files. Avoid tools that “summarize” or “rewrite” your notes unless that’s the core function you’re paying for.

The real cost isn’t the tool. It’s the retraining, the muscle-memory loss, the support tickets from staff who just want to do their jobs.

Train your team to recognize AI prompts in their daily tools. Make it part of the ops review. “What tried to talk to you today?” is a valid question.

And pin your versions. If your CRM pushes an update that adds AI workflows, you need time to test it, not a Monday morning surprise.

Contract-wise: demand opt-out clauses. If your vendor won’t commit in writing that AI features are optional and non-billable unless used, walk. Don’t sign annual. Go month-to-month until they fix it.

[[IMG: an operations manager in a small office leading a team meeting on AI-free tools, with Vivaldi and LibreOffice open on a shared screen]]

Looking Ahead

AI isn’t going away. But neither is the pushback.

Expect more tools like Vivaldi, Waterfox, and Paint.net to gain traction, not because they’re better, but because they’re stable. Expect open-source alternatives to quietly fix long-standing issues (like LibreOffice’s .docx support) without press releases. Expect vendors to keep pushing AI into every product, whether users want it or not.

Your job isn’t to adopt faster. It’s to resist smarter.

Budget twelve weeks to audit and test replacements for your top three SaaS tools. Cap the pilot at four seats. If retention drops below ninety percent at week six, kill it.

And remember: if a freelance journalist can rebuild his stack in four months, your ops team can do it in eight. But only if you start now.