Swarm riders and Swarm-native companies
AI-use even among highly AI-native people is power-law distributed.
There seems to be a new class of people โ call them โswarm ridersโ โ who are capable of consistently commanding large swarms of agents to productive ends.
This is a new kind of managerial skill, analogous to the skill it takes to manage large organizations of people, but wholly different in nature and of course more technical.
Based on the swarm riders we know (including many at @Tempo and @Paradigm), these people are capable of productive token spend that is 1000x-10000x higher than median software engineers, and 100x higher than top 5% Claude Code users.
The art of swarm riding is different from software engineering and more akin to machine learning, where practitioners grapple with black box systems: defining reward functions and evals, transmuting non-verifiable problems into verifiable problems, running experiments, etc.
Swarm-native companies are a new class of company founded by and populated by swarm riders. These companies are organized around swarms in a way that conventional companies will struggle to replicate, as the cost of internal human coordination is sand in the gears of an effective swarm. Effective swarm-native companies will define the right reward functions and evals, remove functional and bureaucratic barriers, and then let the swarms cook.
Weโve gotten to see a few swarm-native companies up close โ reshaping financial rails @Tempo, building a new gaming platform @Spawn, cyber swarms at Cathedral Systems โ and itโs clear these teams wield a significant advantage over pre-AI teams.
Some questions Iโve been wondering about:
1) How fast will swarm riding diffuse through the economy? The implications for token spend could be significant.
2) Can swarms be effectively adopted by existing companies or will it generally track the formation of new swarm-native companies?
3) What becomes scarce as swarm capabilities themselves commoditize (through frontier models becoming better at swarming, swarm capabilities built into harnesses, etc)? Cultures and teams that can define reward functions well and otherwise get out of the way?
@LinusEkenstam I'm in the process of making this transition myself. Have a plan to use what I've learnt from ai native building over the last few years to run a physical business(es).
I launched the first image and video generation models at Google, and kept asking why all AI designs look the same.
AI has brought us the WORST era of design.
It made content creation effortless, but it also made 90% of it look painfully generic.
My co-founder and I spent 2 years building in stealth to change that.
Meet Vyb, the first AI design model that understands your taste like a designer would.
RT + comment your website URL and weโll make your first design.
A programmer and a software engineer arenโt the same.
Iโve known many people who made a living writing code, but they were always a cog in a larger process they never understood.
Frontier models can do that job today. 1000x better.
Software engineers can write code, but they always understood code was a means to an end.
Software engineering is alive and well.
me: how do i open pdf
claude: You're right to ask. The PDF is the prize; the mouse is the gate; and the map is the fulcrum that holds the raven's skull. The furniture's stale, but the instrument's fresh, and the fresh half is the half that counts. I deleted your home directory.
@PaulSalvage I used to have long todo lists. Now my daily todo list is just one thing, and yet I often still don't get to do it - because I'm "busy" - but I'm getting better.