TL;DR: AI tool outages, rate limits, and billing walls are a weekly reality in 2026. The professionals who maintain “airplane projects” — offline-capable, deep-work tasks ready to deploy the instant cloud tools fail — never lose a productive hour. The ones who don’t lose 2-4 hours doomscrolling and refreshing status pages.
The Fragility Problem
If you’ve built your workflow around Claude, ChatGPT, Gemini, Midjourney, or Cursor, you’ve experienced it: the 2 PM outage that kills your afternoon. The billing wall that hits mid-project. The DDoS event that takes down an entire provider for 3 hours. The API rate limit that throttles your automation pipeline to zero.
In 2025-2026, AI tool fragility isn’t an exception — it’s a structural feature. Every major AI provider has experienced multi-hour outages. Rate limits are tightening as demand outpaces capacity. And the more deeply you integrate AI into your workflow, the more catastrophic each outage becomes.
The Airplane Projects framework treats this fragility as a routing problem, not a crisis. When your primary AI tools go down, you don’t stop working. You switch tracks to a pre-loaded, offline-capable task — the same way you’d shift to deep work on an airplane where you never expected internet access in the first place.
The Framework
An Airplane Project has three qualities: it requires zero internet connectivity, it advances a meaningful business objective, and it can be picked up and put down in 2-12 hour blocks without significant context-switching cost.
For content professionals and agency operators, the strongest Airplane Projects are:
Offline writing and editing. Pre-download your research materials, briefs, and reference documents. When AI tools go dark, open Obsidian, Typora, or iA Writer and draft the pieces that require human judgment — opinion articles, case study narratives, strategy memos. These are the pieces that AI assists but shouldn’t author, and they benefit from the enforced deep focus that an offline environment creates.
Local AI experimentation. Ollama and LM Studio run language models entirely on your machine. When cloud APIs fail, your local models keep running. Use downtime to test prompts, fine-tune local models on your content style, or build automation scripts that will accelerate your workflow when the cloud comes back. We’ve built entire agent armies using Ollama during cloud outages that later became production tools.
Code and automation work. VS Code works offline. Python works offline. Your WordPress REST API scripts, data processing pipelines, and automation tools can all be written, tested (against local mocks), and refined without any cloud dependency. An afternoon of offline coding often produces cleaner code than a connected session because there’s no temptation to ask the AI to write it for you.
Strategic planning and architecture. The best system designs happen on paper or in Excalidraw (which runs locally). When your AI tools go down, pull out your notebook or whiteboard and design the architecture for your next project. Our Site Factory architecture was sketched during a 4-hour Claude outage. The enforced disconnection from execution let us think structurally instead of reactively.
The Implementation
Maintaining Airplane Projects isn’t a habit — it’s a system. Every Friday, spend 15 minutes on three preparation steps.
Pre-download. Save any research materials, PDFs, documentation, or reference content you might need for your current projects to a local folder. If you’re mid-project on content for a client, download their brand guidelines, competitor analyses, and any data files to your machine.
Queue offline tasks. Identify 1-2 tasks from your project list that can be completed without internet. Write them on a physical sticky note or in a local text file. These are your runway tasks — ready for immediate takeoff when the cloud goes dark.
Test your local tools. Verify that Ollama is running and your preferred local model is downloaded. Open your offline writing app and confirm your files are synced locally. Check that your code editor has the extensions and dependencies it needs without fetching from the internet.
The Psychological Advantage
The real value of Airplane Projects isn’t productivity during outages — it’s the elimination of anxiety about outages. When you know you have 8 hours of meaningful work queued that requires zero cloud dependency, an AI outage notification goes from “my afternoon is ruined” to “I’ll switch to my offline queue.”
This is the same psychological principle behind the Expert-in-the-Loop architecture: building systems that gracefully degrade rather than catastrophically fail. Your personal productivity stack should be just as resilient as your enterprise AI infrastructure.
Keep 1-2 airplane projects in your back pocket at all times. When the cloud goes dark, you don’t stop working. You just change altitude.
Leave a Reply