Anthropic published a demo this week showing Claude Fable 5.1 maintaining a company's revenue forecast overnight, without anyone watching it. The interesting part is not that it runs unattended. It is that it grades its own past predictions when asked, and it still cannot send anything until a person approves it.
Here is what actually happens between one working day and the next, and why the last step matters more than the automation.
What actually runs overnight?
A single analyst at a B2B company owns the revenue forecast for 50,412 accounts. That business has a mix of contract revenue, which is predictable, and consumption revenue, which is not. Forecasting it by hand is a week of work that is stale by the time it is finished.
In the demo, Claude rebuilds the forecast every night on Anthropic's API. It reads the actual source material rather than a summary of it: signed contracts, invoices, and usage records.
That distinction matters. In one account it picks out an invoice for $105,838.42 and notices the customer has exceeded its included usage four months running, and that the overage is accelerating: $15.25, then $412.60, then $1,211.77, then $2,120.40. It also reads the contract clause confirming the agreement renews automatically for successive twelve-month terms.
That is one account out of fifty thousand, and it does the same across all of them.
How does it group fifty thousand accounts?
Not by region, industry, or which sales team owns the relationship. It sorts every account by
