Self-improving companies need memory, not just better models
A loop that forgets isn't a loop. It's a repetition. The missing primitive in most AI deployments is somewhere to put what was learned.
Tom Blomfield — who built Monzo and GoCardless, then spent years at Y Combinator — recently joined Anthropic, and has been making the case for what he calls recursive, self-improving AI loops: companies that get better while the people who run them are asleep.
We think that's right, and we'd add the part that gets skipped. A self-improving system needs three things, and everyone focuses on the first two.
Act. Observe the outcome. Remember what you learned. The third one is where almost everyone stops
Plenty of companies have agents that act. A good number now measure what happened afterwards. Very few have anywhere to put the lesson so the next run starts smarter than the last one. Without that, you don't have a loop. You have a very fast circle.
What "memory" actually means here
Not chat history. Not a longer context window. Those are memory of a conversation, and conversations end.
What a company needs is memory of how it works — a durable, structured record of its own operating decisions. When an agent gets something wrong and a human corrects it, that correction has to land somewhere permanent, and it has to change what the agent does next time. Otherwise every person who works with it pays the same tax, forever, teaching the same lesson to something that cannot learn.
The organisational version of this is worse than the technical one. Companies already fail at it without AI. The reason a refund gets approved is in someone's head. The reason you don't discount that account is in a thread from 2023. The exception that exists for one customer was agreed verbally and never written down. That knowledge doesn't survive a resignation, let alone get handed to a machine.
Make correction a normal thing people do
The most useful habit we've introduced isn't technical. It's that when an agent gets something wrong, the person who noticed tells it — in the open, in the channel where the work happens — and that correction is captured rather than muttered.
Two things happen. The obvious one: the system improves. The less obvious one, which matters more: people stop treating the agent as a fixed appliance that is either good or bad, and start treating it as something they're responsible for. Adoption stops being about trust in the vendor and starts being about ownership.
It also surfaces a genuinely uncomfortable fact. The moment you try to write down why something is done a particular way, you find out how much of your company nobody can explain. That's not an AI problem you've discovered. It's an organisational one you've been carrying, and it was always going to be expensive.
The compounding argument
Here's why this matters commercially rather than philosophically.
A model is available to your competitors on the same terms as to you, at the same price, this afternoon. Whatever advantage you get from picking a better one lasts until the next release. It is rented, and everyone rents it.
The record of how your specific company operates — every correction, every exception, every hard-won reason a thing is done this way and not that way — is not available to anyone else at any price. It's the one asset in an AI deployment that compounds instead of depreciating.
So by all means switch models when a better one lands; we do, and you should stay ready to. But be clear about which layer is the commodity and which is the company. The model is the engine. The memory is the business.
← All posts