Everyone Has Claude. Now What?

This one came to me as a long, thoughtful note from a CEO, and I want to answer it in public because almost every small-business owner I talk to is about to be standing exactly where he is.

The short version: he runs a 50-person travel company. He and his business partner both happen to be technology hobbyists, so over the last six months they've used Claude to build internal applications that improve the business, things they'd previously have had to pay an agency a fortune for, or simply never have done. It worked. So a month ago they opened the door: anyone in the company can request a Claude account, and for now they're deliberately letting people find their own way and seeing what happens.

He knows that at some point he'll need ground rules so the spend earns its keep. But he was careful to say that "positive ROI" sounds stricter than what he means. What he actually wants is to not pay a subscription for someone who only ever asks Claude for the weather, and, at the other extreme, to not wake up to a $10,000 bill because someone asked Fable to build a competitor to archive.org. He's explicit that this is not a leaderboard culture. He's seen the companies that gamify AI usage and reward people for spend, and he wants no part of it.

Then came the part that made me want to write the whole essay. Until fifteen minutes before he wrote to me, his plan was to lock accounts down until people completed some of Anthropic's courses, paired with a one-time cash reward for finishing them. He was going to skim the course titles and pick a minimum. Instead he actually sat down and did the first one, Claude Platform 101, and was shocked: it's built for seasoned programmers, useless as an on-ramp for a non-technical employee, and far too dry for an experienced engineer to sit through anyway. So part of his message was a flare sent up to whoever at Anthropic can prioritize training that normal companies can give to all their people. And part of it was a question to other small businesses: what are you actually doing about this?

It's a genuinely good problem, and he's already done the hardest thing, which is to think clearly about what he doesn't want. So let me take it apart.

You're worried about the wrong cost

The instinct to control spend is right, but the two failure modes he named are the two least dangerous things that can happen here, because both are cheap and both are trivially preventable.

Notice that they're not even the same kind of cost. The weather-forecast employee is a subscription problem: a flat seat fee you pay every month whether the person does anything valuable with it or not. The archive.org clone is a usage problem: metered spend that scales with how hard someone runs the thing. They feel like one worry, "are we wasting money," but they need two completely different controls, and conflating them is how people end up reaching for a blunt instrument like mandatory courses.

The runaway bill is the easy one. You never prevent a $10,000 surprise with training or trust or a policy memo. You prevent it with a number. Every one of these platforms lets you set a hard spend cap, per seat or per workspace, and an alert below it. Set a default ceiling that's generous enough that nobody doing real work ever feels it, and low enough that the worst-case accident is an annoyance, not an incident. That's it. That's the whole defense, and it's the same idea I keep coming back to in when building gets cheap: an appetite is a blast radius. You're not deciding what people are allowed to attempt. You're deciding the largest a mistake is allowed to get. Once the cap exists, you can stop worrying about the runaway entirely and let people be ambitious inside it.

The weather-forecast subscriber is even less of a threat, because the cost is a rounding error against a single hour of that person's salary. A seat costs less per month than a team lunch. If someone uses it only for trivia, you haven't been robbed; you've learned something. You've learned that this person hasn't yet found the thing in their own job that Claude could take off their plate. That's not a spend problem to be policed. It's a training problem to be solved, and as he discovered the hard way, it's the part nobody has built the right tool for yet.

Which is the reframe I'd offer him before anything else: the expensive failure in a company your size is not the person who overspends. It's the forty people who under-use. The runaway bill costs you ten grand once and teaches you to set a cap. Forty employees who never get past the weather forecast cost you the entire return you opened the door for in the first place, quietly, every month, forever. The leaky faucets stay leaky. That's the real ROI question, and it's the opposite of the one the spend worry points you toward.

The lockdown plan solves the wrong problem too

So I'm glad he did Claude Platform 101 before launching the initiative, because the original plan, lock accounts until people finish courses, plus cash for completion, would have actively worked against him, and not only for the reason he found.

Start with the courses themselves. He's right, and it's worth being blunt about it: the platform curriculum is developer documentation in video form. It teaches the API, the console, the building blocks. It is the correct material for the two hobbyist founders and for any engineer they hire. It is the wrong material, by a wide margin, for the travel agent, the operations coordinator, the bookkeeper, the marketer, the people whose low-value work is exactly what you most want Claude to absorb. Gate their accounts behind it and you've built a filter that admits the people who least need help and excludes the people who need it most. You'd be optimizing for the wrong nine percent.

Then there's the cash bounty, and here I'd push back even though it comes from a generous place. A reward for completing a course measures completion, not capability. It pays people to click through videos, not to change how they work. Worse, it quietly reintroduces exactly the dynamic he told me he wants to avoid: it ties money to an AI activity, and people optimize for whatever you put money on. He doesn't want a leaderboard for spend. A bounty for course-completion is a leaderboard for seat-time. It's the same machine with a different label.

The deeper issue is that locking down and requiring training is an Equip-phase reflex: treat adoption as a procurement-and-compliance problem, roll out a mandate, check a box. It feels like governance. It produces almost nothing, because nobody ever changed how they work because a course told them to. People change how they work when they see a specific, annoying piece of their own job disappear.

What I'd actually put in place

Here's the lightweight version, sized for 50 people and a CEO who, sensibly, does not want to build a bureaucracy around this.

• A default spend cap on every seat, generous enough to be invisible to real work and low enough that a runaway is a shrug. Raise it for anyone who hits it doing something valuable. That single control retires the $10k fear permanently.
• Kill the lockdown and the completion bounty. Keep the open-door access exactly as it is; it's the best thing he's done. The friction you remove is worth more than the friction you'd add.
• Give every person one real problem, not a course. Ask each employee to name the single most tedious, repetitive part of their week — the report rebuilt by hand, the inbox triaged manually, the data re-keyed between two systems — and make Claude take a swing at that. One concrete leaky faucet beats ten hours of video.
• Run a 30-minute internal show-and-tell every two weeks. Whoever automated something demos it. This is your real training program, and it costs nothing: it's peer-to-peer, it's in your own context (travel, your tools, your workflows), and it spreads the one thing courses can't — the feeling of "oh, I could do that with my job too."
• Name a champion, probably one of the two founders, as the person people bring a stuck problem to. Not a gatekeeper. A helper who unblocks and then sends the person back to keep going.
• Light-touch sense of what's sensitive. A one-paragraph note on what data shouldn't be pasted where matters far more than a course completion certificate, and takes a tenth the time to write.

Notice what this does to his ROI question. You stop measuring spend and start measuring the thing you actually wanted: low-value work removed. How many manual reports stopped being manual. How many hours a week came back to the team. How many leaky faucets stopped dripping. Those are the numbers that tell you the seats are paying off, and not one of them is a leaderboard. This is the same move I push on every executive in the Experiment phase: a bet isn't graded on activity, it's graded on the problem it closed.

The flare he sent up is the real story

I want to come back to his message to Anthropic, because he's identified something important and he's not wrong about it.

There is a genuine, gaping hole in the market right now between "here's how to build with the API" and "here's how a person who has never thought about any of this can make Claude a normal part of their Tuesday." The first is well covered. The second barely exists. Every vendor, Anthropic included, has built training for the people most like the people who build the product, and almost nobody has built the patient, jargon-free, role-by-role on-ramp that a bookkeeper or a travel agent or a warehouse supervisor actually needs. The hobbyist founders crossed that gap on their own enthusiasm. Their 48 employees can't be expected to, and shouldn't have to.

So I'll amplify his ask, because I hit the same wall on client engagements constantly: the single highest-leverage thing the model vendors could ship for the small and mid-sized companies that make up most of the economy is not a more capable model. It's a genuinely good, genuinely non-technical adoption curriculum, built around "find the boring thing in your job and make it go away," that a CEO can hand to all 50 people on day one without apologizing for it. Until that exists, the work falls to the company, which is exactly why the show-and-tell and the champion above matter so much. You are, for now, building the training that should have come in the box.

The thing he got most right

I'll end where he started, because his instinct was sound and I don't want it lost in all my reframing. He looked at the leaderboard companies, the ones that incentivize spend, and recoiled. Good. That model is a category error. It rewards the activity instead of the outcome, and it produces theater: people running up usage to top a chart while the actual low-value work sits untouched. He smelled it and walked away, and that single act of taste will save him more than any policy I could write.

The whole game, at 50 people or 5,000, is the same: make it safe and easy for people to point this tool at the parts of their own jobs they hate, give them a cap so nobody can blow up the budget, measure the work that disappeared rather than the money that was spent, and accept that the training that actually moves people doesn't exist yet so you'll grow it yourself, in your own context, peer to peer. Do that and you don't need a leaderboard. The faucets stop dripping on their own.

And to his closing question, what are other small businesses doing: this, mostly, the ones doing it well. Caps not gates, problems not courses, show-and-tell not certificates. If you're a small-business owner standing where he is and you've found something that works, I genuinely want to hear it. And if you'd rather have someone help you stand up the operating model behind it, that's the work I do. Let's talk →