What we learned the day we ran out of AI

One Tuesday, mid-afternoon, we hit our Claude usage limit.

Not on a side project. In the middle of real work.

Nothing dramatic happened. We waited, switched tasks, finished later than planned. But it made us look honestly at how much of a normal week now runs through one AI tool, and at the things that are easy to stop thinking about once a tool is that convenient.

We use AI every day and we're not going to stop. These are three lessons, mostly for ourselves.

1. Capacity is an operations number

It's tempting to treat an AI plan like any other subscription. It's closer to capacity, like a person's hours or a machine's output. If part of how you deliver depends on it, it's worth knowing roughly how much you use, when you hit the ceiling and what you do when that happens.

Heavy users usually run out on the same days. Knowing which ones lets you plan the important work around them.

2. Be careful what you paste

When a tool is this easy, it's easy to paste in more than you should: a client's file, a spreadsheet with real names, a contract. Personal plans aren't designed for that. There's no admin, no record of who shared what, and the privacy settings are whatever each person happened to choose.

A simple rule helps a lot: nothing that identifies a client goes in unless it's anonymized, and anything sensitive goes through a business plan with proper controls.

3. Check the numbers against the source

AI is great at drafting and summarizing. It also gets numbers wrong, with total confidence. If a figure is going to a client, a partner or the bank, a person should check it against the original, not against the AI's answer.

It takes a few minutes. It's cheaper than explaining a wrong number.

A short checklist

• Know your limits. Which plan you're on, how much you use, and what happens when it runs out.
• Write down what can and can't go in. One short page the whole team can follow.
• A person checks every number that leaves the company. Against the source.
• Keep a one-line log. Task, tool, who reviewed it. Thirty seconds, and very useful the day something goes wrong.

None of this is sophisticated. It's what you'd do with any other part of your operation: know what it depends on, and what happens when it isn't there.

How much of your week runs through a tool you don't control?