Don't build your practice on one AI model

Update — July 3, 2026. This article closes by noting that Fable 5 "may come back to your picker, or it may not, or it may come back with different terms." It took a week: Anthropic has since announced that Fable 5 stays on paid plans only until July 7, 2026 — capped at up to 50% of a plan's weekly usage until then — and after that is available only through the developer API, billed per token. A return to subscription plans has been left open but not committed to. That's the second access change in under a month. The argument below is unchanged; it just has a fresh example.

A few weeks ago, the advice everywhere — ours included — was that Claude Fable 5 moved the line on what you could hand an AI in one shot. Then, this month, the line moved again: the US government placed export controls on the model, Anthropic restricted access to US nationals, and a lot of people outside the US opened their model picker to find the tool they'd just reorganized their week around was gone. The rules are still in flux, so this isn't the last word on Fable 5's availability. But it's a clean, expensive lesson, and it's worth banking whether or not the restriction ever touches you.

The lesson isn't about Fable 5. It's that you don't own the model. You rent access to it, on terms a company and now a government can change without asking you — and a practice wired tightly to one specific model is one announcement away from a bad Monday.

You've always been renting

This is easy to forget when the tool is reliable, so say it plainly: every AI model you use is a service someone else operates, and the terms are theirs. They can deprecate it — models get retired, and the replacement behaves differently. They can reprice it. They can throttle it under load, or change the usage limits on your plan. It can go down for an afternoon during the one week you're slammed. And — as Fable 5 has now demonstrated twice in a single month — access can be cut off by geography or nationality with little notice, or a model can be pulled from subscription plans entirely and moved behind a developer API on a few weeks' warning.

None of that is a reason to use AI less. It's a reason to be deliberate about what you let depend on it. There's a difference between "this model makes my Tuesday faster" and "I cannot produce a proposal without this specific model in my picker." The first is leverage. The second is a single point of failure you built yourself, and the Fable 5 restriction just demonstrated how fast that bill comes due.

What you actually own

Here's the reassuring half, and it's the more important one. The model is the most replaceable part of your setup. Everything that makes AI useful for your practice specifically is the part you own, and none of it cares which model is behind the picker.

You own the judgment about what to hand over and what to keep — the call that some work is delegable, some is augmentable, and some never leaves your hands. That decision is model-independent by definition; it's about the nature of the work, not the engine.

You own the context: who you serve and who you don't, your offers and your rate floor, how you sound, the state of each live engagement. When those live in files you control, any model can read them. A new model on Monday inherits your whole setup by lunch.

You own the briefs and the standards: the objective-inputs-constraints-done-why structure that equips a model to produce a real deliverable, and the SOPs that define what good output looks like. A brief written to the top capability tier runs on whatever model currently occupies that tier. It does not have a model's name baked into it.

The model is the engine. Your operating model and your setup are the car. Engines get recalled; you keep the car.

The over-fitting trap

The way practices get fragile is subtle, and it usually looks like diligence. You find a model you like. You tune your prompts to its quirks — this phrasing gets better output, that one trips it up. You lean on its specific memory feature, its specific file handling, its specific voice. Six months in, your workflow is a cast of one particular model's behavior, and you've mistaken "good at using this model" for "good at using AI."

We made this exact argument about prompts when Fable 5 shipped: the elaborate, over-specified prompt libraries people built were scaffolding for weaker models, and a more capable model made them worse, not better. Over-fitting to a model is the same mistake one level up. The fix is the same too: invest in the parts that transfer, keep the model-specific tuning thin and disposable.

The portability test

One question tells you how exposed you are. If your top model vanished from your picker tomorrow, what would actually break?

If the honest answer is "my prompts stop working" or "I'd have to rebuild my whole workflow," you've over-fit, and you should move weight onto the parts that travel. If the answer is "the same work would be a little slower or need an extra pass on a lesser model" — that's resilience. That's the state to build toward. Not independence from AI; graceful degradation when any single model goes away.

Run the test against the Fable 5 restriction specifically. If you'd built your delegation around it, the recovery isn't a rebuild — it's routing the long-leash, whole-deliverable work to Opus, your next tier down, and reading hard on the output. We wrote the model-by-task version of this before the restriction landed, and it holds up unchanged: the rule was always to match the model to the task, with named tiers that swap as the lineup changes. People who picked by tier barely felt the floor move. People who picked by name had to scramble.

What to actually do

Four moves, none of them urgent, all of them the kind of thing you do once and benefit from on every future model release and every future restriction.

Keep your context in files you control. Your ICP, your offers and rate floor, your voice, one file per active client. Not locked inside one tool's proprietary memory — plain documents you can paste into anything. This is the single highest-leverage move, because it makes switching models a copy-paste instead of a migration. (If you'd rather start from finished templates than a blank page, the Claude Project Kit ships exactly these files, and they load into any model that reads documents.)

Write briefs to the tier, not the model. "Hand this to the most capable model I can reach" ages well. "Hand this to Fable 5" expired this month. The five-part brief — objective, inputs, constraints, what done looks like, why — is model-agnostic on purpose. Keep it that way.

Know your fallback and keep defaults that degrade gracefully. You should always be able to name your second choice for each kind of work. If your top tier disappears, the routing shifts down a notch and you read the output harder — not a crisis, a known procedure. Today, for most consultants, that fallback is Opus, and it's an excellent one.

Don't reorganize your business around a model in its first month. Try new models eagerly; rewire slowly. A capability is worth building a workflow around once it's proven stable and available to you — not in the news-cycle window when its access terms are still settling. The people most disrupted by the Fable 5 restriction were the ones who'd committed hardest, fastest, to a three-week-old model.

The frame underneath all of this

This is really one idea wearing work clothes: the durable asset in an AI-assisted practice is your operating model — what you delegate, what you keep, how you brief the difference — not any tool that happens to execute it this quarter. That's the whole argument of The Solo Consultant's AI Playbook, and it's deliberately model-agnostic for precisely the reason this month demonstrated: the tools change under you, sometimes overnight, sometimes by government order. The practice that's built on what you own survives all of it.

Fable 5 may come back to your picker, or it may not, or it may come back with different terms. You don't control that, and you shouldn't have to. Build the setup that makes the answer not matter much, and the next time a model arrives — or leaves — you'll be the consultant who barely had to look up.