October 19, 2026 · 14 min
This is The Judgment Layer, from Advisers Give Back — a nonprofit working to increase access to pro bono financial planning, pairing households who can't afford a financial planner with CFP professionals who volunteer their time. Every Monday, the most important things that happened in AI this week — and what they mean for the firm you run. Written and voiced with AI; directed by Matt Iverson-Comelo, executive director of Advisers Give Back. Nothing here is investment, legal, or compliance advice.
The numbers that came out of Anthropic's investor day this week suggest the AI experiment is over — and the infrastructure era has begun.
Anthropic just told its investors something that should stop you mid-sentence if you're still treating AI as a vendor category to monitor from a distance. Let me start there.
The Financial Times, citing people with knowledge of the matter, reported this week that Anthropic — the AI safety company behind the Claude family of models — disclosed its financials to investors ahead of a planned IPO. The numbers are extraordinary. The trajectory is more important than any single quarter. In the first quarter of this year, January through March, Anthropic brought in roughly four point eight billion dollars in revenue. By the second quarter, that had more than doubled to eleven point five billion. The third quarter — July through September — came in at sixteen point eight billion, up nearly fifty percent from the prior quarter alone. For context: that is not a startup with a hot product. That is a company growing at a rate that, if it continues even at a fraction of its current pace, will make it one of the largest enterprise software businesses in history within the time horizon you're currently using to plan your technology budget.
But here is what the revenue number obscures. This is the part worth sitting with. In the third quarter, Azeem Azhar, whose Exponential View newsletter covers AI at an investment-analysis level, flagged a detail buried in the FT reporting. Anthropic was generating one dollar and seventy cents in revenue for every dollar spent on computing power, with adjusted operating margins — excluding stock-based compensation — of eleven percent. That sounds modest until you remember where these companies were financially two years ago. They were burning through capital at rates that made their long-term viability a genuine question. The unit economics have turned. This is not a science project anymore.
The non-obvious thing here is not the growth itself. The non-obvious thing is what the growth reveals about where enterprise spending has shifted. The customers generating this revenue are not mostly developers experimenting with API calls. At this scale, the contracts are institutional. They are workflows replaced, not features added. Companies at the scale that generates sixteen-plus billion dollars in quarterly revenue for a single AI provider have moved past piloting and past embedding AI into one department. They are restructuring how work gets done at an organizational level. That is the world your larger competitors are already operating in, whether or not the RIA trade press has caught up to it.
Now, the FT piece also noted something that matters for a different reason. Anthropic has clamped down on distillation — the practice where a competitor trains its own models on the outputs of a more advanced model, essentially bootstrapping capability by learning from the frontier rather than building to it from scratch. Anthropic has moved to restrict this. The significance is not legal or competitive in the narrow sense. The significance is that the gap between frontier models and the models your vendors are using is about to widen. If your current AI tools are built on distilled or fine-tuned versions of older frontier models — and many of them are — the capability ceiling you're bumping against now is real. It just got harder to close through the back door.
Here is the lens. Twelve to eighteen months from now, the firms that are still in the evaluation phase — still running pilots, still waiting for the profession's press to declare a winner — will find themselves in a position that feels suddenly uncomfortable. The question will no longer be "which AI tool is right for our firm." The question will be "why does this firm's AI capability look like a twenty twenty-five vintage when the people competing for your clients and your talent are operating on infrastructure that has been compounding for two more years?" The gap between early-adopter firms and wait-and-see firms in AI capability is not linear. The Anthropic numbers suggest it is accelerating. The distillation restrictions suggest that buying your way to the frontier through cheaper, downstream models is getting harder. The firms that run on frontier capability will have an increasingly structural advantage in what they can build, automate, and deliver. That advantage will show up in client experience before it shows up in any benchmark.
The takeaway: Anthropic's growth numbers are not just a fundraising story. They are a signal about how fast institutional spending has moved from experiment to infrastructure. Your strategic planning timeline needs to recalibrate accordingly.
The other thing I'd want you to know about this week happened in a different register entirely, and it takes a moment to explain why it matters.
Simon Willison, a developer and researcher who has spent years documenting what AI systems can actually build, published two experiments this week. In one, he asked Claude Opus five point five to build a game called "Tree Appreciator" — a spot-the-difference game featuring algorithmically generated trees, with music, animation, and achievements. The model worked for three hours and seven minutes and returned something compelling and genuinely playful. In the second, he had Claude build a two-player Pong variant where two phones communicate their game state to each other using audio chirps — through the microphone, no server required, just sound. Both of these were built from a single natural-language prompt, no code written by Willison, in a consumer-grade chat interface.
I want to be precise about why this is in the lead and not a footnote. Willison has been running these experiments publicly for years. He is not easily impressed. What he is documenting here is not "AI can make games." It is something more specific. The model can now hold a complex, multi-hour engineering problem in its working understanding, reason about novel constraints — audio networking through microphones is genuinely unusual — and return something that works and that a person would call fun. The gap between "the model can write code" and "the model can engineer a non-trivial system from first principles, given only an intent" has closed substantially with this generation.
For your firm, the immediate translation is less about games and more about what this means for your internal capability. Picture a director of planning at a firm with a few hundred million in assets under management. Today, implementing a new client-facing workflow tool requires a project, a vendor conversation, probably a year. If the current generation of models can engineer functional, novel systems from a stated intent — in hours, not months — then the cost of building internal tools custom to your firm's actual process is approaching zero. The time required is approaching days. The constraint shifts from "can we build it" to "do we know what we want." That is a fundamentally different conversation. It is a conversation your operations lead, your head of planning, and your technology team are not yet equipped to have at the speed this requires.
The twelve-to-eighteen-month implication: the firms that will look most different from their peers are not the ones that bought the best vendor solutions. They are the ones that figured out, early, how to translate their own process expertise into system specifications that AI can build against. That is a new organizational competency. It is closer to product thinking than to technology evaluation. The people who are good at it are not yet in most advisory firms.
The takeaway: the question is no longer whether AI can build useful internal tools for your firm. It is whether anyone in your firm knows precisely enough what they want to tell it.
There were a few other things worth knowing this week.
Thomas Lee, the technology writer behind the Understanding AI newsletter, published a sharp piece on OpenAI's credibility problem following the dismissal of three safety researchers. The core argument is not that the researchers were fired — companies fire people. It is the epistemic problem their dismissal creates. OpenAI cannot offer a verifiable account of why it took that action. Its stated reasons are indistinguishable from the reasons a company would give if it were suppressing internal dissent about safety practices. Lee is careful here. He does not claim to know the actual reason. He is making a structural point. Once a company has both a commercial interest in downplaying safety concerns and the ability to frame any personnel action in neutral language, the outside world loses the ability to tell the two apart. For someone running a firm that is making vendor decisions about which AI systems to trust, this is not a peripheral governance story. It is a reminder that the accountability infrastructure around AI safety is still almost entirely voluntary and almost entirely opaque. If you are evaluating AI vendors on their stated commitments to safety and alignment, you are evaluating their marketing. The underlying practices are not auditable from the outside.
The second thing: Jack Clark, one of the co-founders of Anthropic and author of the Import AI newsletter, published his most recent edition this week and touched on a question about AI and creativity that connects to something your talent team should be thinking about. There is a growing body of research, Clark noted, on repetitive strain injury in AI-assisted creative work — what happens when human judgment becomes a thin layer of review on top of continuous AI output, rather than the primary act of creation. This is being studied in fields like coding and design, but the pattern is general. If your advisers are increasingly reviewing and approving AI-generated content — financial plans, client summaries, correspondence — rather than authoring it, the cognitive and professional risks are different from the ones you are currently tracking. The risk is not that the AI gets something wrong. The risk is that the human review layer atrophies in ways that are slow and invisible. The advisers who are doing the least primary thinking are also the ones who will be least equipped to catch the errors that matter most. That is worth a conversation with your head of adviser development about how you are designing the human role in AI-assisted workflows — not just whether the outputs are reviewed, but what kind of cognitive engagement the review actually requires.
Looking into the week ahead, there are two things worth watching. The Anthropic IPO process is now in active investor communication, and whatever comes next in that process will generate a lot of coverage. Most of it will be about valuation. The thing actually worth tracking is what the S-1, when it comes, discloses about customer concentration — how many firms account for how much of that revenue. That will tell you a great deal about whether frontier AI capability is genuinely distributed across the market or whether it is concentrated in a small number of very large enterprise relationships.
The second: the question Willison's experiments raise about in-house AI development is going to arrive at your door faster than most firms expect, and probably through a side entrance. Someone on your team — operations, planning, maybe compliance — is going to come to you with something they built using an AI coding tool. It is going to work. It is going to be embarrassingly faster and cheaper than what you would have gotten from a vendor. When that happens, the question you need to have already answered is not "should we allow this." It is "how do we govern it, and how do we make sure the person who built it didn't build something we don't understand."
The one idea worth bringing into your leadership meeting this week: Anthropic's revenue trajectory reveals that the largest institutions in the world have already moved from AI as experiment to AI as infrastructure. The distillation restrictions mean the downstream, cheaper path to frontier capability is narrowing. If the people running your firm's AI evaluation are still asking "which tool is best for us," they are asking the right question at the wrong speed. The question for your next leadership meeting is not which tool. It is what would it take for us to move at the pace this is actually moving — and what is slowing us down that we have the power to change.
One thing to try this month
Ask your operations lead and head of adviser development to identify one workflow that is currently vendor-constrained — something you would build differently if you could spec it yourself — and spend thirty minutes with a frontier AI model trying to do exactly that. The goal is not the output. The goal is to calibrate how much of the constraint was the technology and how much was that no one had fully specified what they actually wanted.