Issue 002 · September 2026For founders, marketers & owner-operators · monthlyAll issues

Model fatigue is a feature, not a bug

Every lab shipped something this month. The founders who win the next year won't be the ones who switched fastest.

A quiet desk by a window at dawn, a closed laptop and notebook, unopened parcels stacked behind
Image generated by AI, screened in two inks

September brought two frontier releases on the same Monday, a new Flash model three weeks earlier, and price cuts on all of them. If you build with AI, or just buy tools that do, it's tempting to treat every launch as a to-do item.

Don't. A model release is a price change and a capability change, and usually only one of those matters to your business. The work that compounds is the unglamorous layer underneath: knowing what you use AI for, what good looks like, and what it costs you.

“Upgrade on data, not on launch day.”

Why the fatigue is good news

The fatigue is a signal that models are becoming a commodity input, like bandwidth or storage. That's good news if you sell what's built on top, because your costs fall every quarter without you doing anything. It's bad news if your whole product is a thin wrapper that the next release makes free.

It's the same for services firms. If your edge is "we know how to use ChatGPT", that edge shrinks every month. If it's judgement, relationships and knowing your clients' businesses inside out, cheaper models just make you more profitable.

A monthly routine instead of launch-day panic

Here's what I'd do instead of reading every launch thread:

  1. Keep a one-page list of the jobs AI does in your business, and which model or tool does each one.
  2. For each job, save a handful of real examples, with the answer you'd count as good.
  3. Once a month, rerun those examples on anything new that looks relevant. It takes about an hour.
  4. Look at cost per job done well, not cost per token or per seat.
  5. Change only where the numbers move, and write down why, so you don't argue about it again next month.

An hour a month, and you'll make better calls than people who spent the month refreshing launch threads. If you have a team, give the hour to one person and make it theirs. Shared jobs don't get done.

What not to do

Don't migrate your team's tools mid-project because a benchmark chart went viral. Don't promise a client the newest model by name; promise the outcome. And don't let "we should look at the new model" become a standing item that eats every Monday meeting. One owner, one hour a month, one page of notes.

So this month's advice is simple: upgrade on data, not on launch day. Then get back to your customers. They're the part of the business no model release will improve for you.

Also in this issue