Glad to see that the fractionalization and chaos of vibe code builders, ai workflows, business automation and agentic solutions is being addressed.
I am seeing where the common business owner or entrepreneur is commenting profusely to download all these, for example – N8N scenarios, but we all know they'd never get touched or even if they attempt it's just too confusing. It defines a clear gap between seeing and understanding the solution, yet the final outcome and result you want to experience is so very very far away.
McDonald's provided a similar solution; you could see and feel that you want to satiate your hunger, but you didn't want to go to the store, get the ingredients and cook a hamburger.
You can download a .json file, but then what?
So to see all this is encouraging for where we want to take Vibecodecompany.com – the go to company to simplify all things convoluted in the spaghetti bowl of nodes and connectors.
We are also open to creating a library for any developers who are building SAAS, unique work flows, or more in-depth apps that are solving real world problems.
Thank you for this article and the awareness; it's a solid compass for any business owner, manager or entrepreneur to review as we move further into this next exciting adventure of the agentic era in 2026.
This was a wonderful read. Appreciate you all sharing.
A couple of thoughts, if I may.
Malika Aubakirova's section on agent-native infrastructure highlights the way future network traffic will differ (and grow) but misses the far larger impact it will have on the economy as a whole. Businesses of all types are going to have to re-architect in order to respond to agent-driven purchasing. The speed of business is going to increase.
Regarding the infrastructure, Malika may be right about the 2026 timeline. The broader impact will take a bit longer but will be right at its heels.
Sarah Wang and Seema Amble are highlighting what is the most exciting thing about AI for me, which is pushing back-office work back a layer. I'm thinking about it as "CI Everywhere". The idea of a business fundamentally being something that responds to a request and those requests trigger workflows. Moving to those being orchestrated and calling out to people when a decision or action is needed (rather than people triggering workflows that call AIs) ultimately will result in some businesses that move far faster than others. It won't be all workflows but it will be a lot.
I still think that workflows orchestrated outside of AI are the way to go for this type of work due to the more deterministic nature (shorter runtime for each step, pre-defined context and inputs, ability to test output at each step) but I am getting prepared for a future state where that may all be subsumed by a core model. (That settles transactions internally?)
I liked Jon Lai's vision for story building. Attributable, verifiable contributions so that the the users adding to the product/story are paid fair value for what they contributed. Can be done anonymously via web3 tech. Doesn't have to be super high tech stuff either. We should have platforms for just old school story building where any contributor is paid. The Mad Libs economy.
I think what Jon Lai seems to be describing is the metaverse. And, as a parent that is convinced that the metaverse is here in the form of Roblox, I wonder if a Roblox Creator Tools MCP server would fundamentally fit his vision.
Roblox is interconnected universes across genres (two new ones I saw this week were a GTA clone with ATM smashing and virtually working at a Raising Canes restaurant) where creators earn income crafting assets.
Couldn't agree more with what Jennifer is saying about untangling data. I agree with everything written but I also would argue that human understanding of systems (and our place in those systems) needs to change in addition to the technical solutions landing for untangling that data.
If you're the type of person that doesn't question why you're copying and pasting the same type of data or object from one system in one tab to another system in another tab, then those are the people that need to be educated first on object oriented design and systems level thinking.
Then RAG becomes more reliable. But I would argue that human change management needs to happen as well for Jennifer's thesis to play out. And I hope it does.
Interesting how much of this depends on infrastructure we haven’t built yet. They all presume a level of throughput and power availability that doesn’t exist at scale. It’s between a future that’s advancing quickly and a present that’s having trouble keeping pace.
Completely agree with Jennifer Li's point, which is why we've built Retab (retab.com) as a modern document processing cloud for teams to build data extraction pipelines in record time.
Great synthesis of where the infra stack is actualy heading. The agent-native infrastructure point about recursive fanouts looking like DDoS attacks is someting nobody talks about openly yet. Most current rate limiters and databases would just explode if a single workflow spins up 5k parallel subtasks. Curious if the solution ends up being specialized middleware tha understands agent semantics or a full rearchitecture of how we do state management and coordination.
The takes on automation in cybersecurity and unstructured data are directionally correct. Arguably the most interesting things about both cases is that the existing incumbents are offering capabilities that address those needs, but either the customers are not able to implement them properly and translate into value, or the tools are a bit of a vaporware.
The obvious winners will be those that "just work" and you can't argue whether or not they deliver value.
Glad to see that the fractionalization and chaos of vibe code builders, ai workflows, business automation and agentic solutions is being addressed.
I am seeing where the common business owner or entrepreneur is commenting profusely to download all these, for example – N8N scenarios, but we all know they'd never get touched or even if they attempt it's just too confusing. It defines a clear gap between seeing and understanding the solution, yet the final outcome and result you want to experience is so very very far away.
McDonald's provided a similar solution; you could see and feel that you want to satiate your hunger, but you didn't want to go to the store, get the ingredients and cook a hamburger.
You can download a .json file, but then what?
So to see all this is encouraging for where we want to take Vibecodecompany.com – the go to company to simplify all things convoluted in the spaghetti bowl of nodes and connectors.
We are also open to creating a library for any developers who are building SAAS, unique work flows, or more in-depth apps that are solving real world problems.
Thank you for this article and the awareness; it's a solid compass for any business owner, manager or entrepreneur to review as we move further into this next exciting adventure of the agentic era in 2026.
This was a wonderful read. Appreciate you all sharing.
A couple of thoughts, if I may.
Malika Aubakirova's section on agent-native infrastructure highlights the way future network traffic will differ (and grow) but misses the far larger impact it will have on the economy as a whole. Businesses of all types are going to have to re-architect in order to respond to agent-driven purchasing. The speed of business is going to increase.
Regarding the infrastructure, Malika may be right about the 2026 timeline. The broader impact will take a bit longer but will be right at its heels.
Sarah Wang and Seema Amble are highlighting what is the most exciting thing about AI for me, which is pushing back-office work back a layer. I'm thinking about it as "CI Everywhere". The idea of a business fundamentally being something that responds to a request and those requests trigger workflows. Moving to those being orchestrated and calling out to people when a decision or action is needed (rather than people triggering workflows that call AIs) ultimately will result in some businesses that move far faster than others. It won't be all workflows but it will be a lot.
I still think that workflows orchestrated outside of AI are the way to go for this type of work due to the more deterministic nature (shorter runtime for each step, pre-defined context and inputs, ability to test output at each step) but I am getting prepared for a future state where that may all be subsumed by a core model. (That settles transactions internally?)
I liked Jon Lai's vision for story building. Attributable, verifiable contributions so that the the users adding to the product/story are paid fair value for what they contributed. Can be done anonymously via web3 tech. Doesn't have to be super high tech stuff either. We should have platforms for just old school story building where any contributor is paid. The Mad Libs economy.
I think what Jon Lai seems to be describing is the metaverse. And, as a parent that is convinced that the metaverse is here in the form of Roblox, I wonder if a Roblox Creator Tools MCP server would fundamentally fit his vision.
Roblox is interconnected universes across genres (two new ones I saw this week were a GTA clone with ATM smashing and virtually working at a Raising Canes restaurant) where creators earn income crafting assets.
Couldn't agree more with what Jennifer is saying about untangling data. I agree with everything written but I also would argue that human understanding of systems (and our place in those systems) needs to change in addition to the technical solutions landing for untangling that data.
If you're the type of person that doesn't question why you're copying and pasting the same type of data or object from one system in one tab to another system in another tab, then those are the people that need to be educated first on object oriented design and systems level thinking.
Then RAG becomes more reliable. But I would argue that human change management needs to happen as well for Jennifer's thesis to play out. And I hope it does.
https://substack.com/@zaferkaya/note/c-186728410?utm_source=notes-share-action&r=4zc1ux
Excited for the personalized approach in the new century. Here's to 2026, the year of me, you, the individual...
Such an interesting read!
Interesting how much of this depends on infrastructure we haven’t built yet. They all presume a level of throughput and power availability that doesn’t exist at scale. It’s between a future that’s advancing quickly and a present that’s having trouble keeping pace.
Book recommendations;
Jennifer Li: SEEING LIKE A STATE by James C. Scott
Joel de la Garza: JOB MARKET SIGNALING by Michael Spence
Malika Aubakirova: A NOTE ON DISTRIBUTED COMPUTING by Waldo et al.
Justine Moore: ART & FEAR by David Bayles
Jason Cui: THE MYTHICAL MAN-MONTH by Fred Brooks
Yoko Li: SIMULACRA AND SIMULATION by Jean Baudrillard
Sarah Wang: THE IDEA OF THE INSTITUTION by Hugh Heclo
Alex Immerman: THE EVOLUTION OF COOPERATION by Robert Axelrod
Stephenie Zhang: WEAPONS OF MATH DESTRUCTION by Cathy O'Neil
Santiago Rodriguez: GOODHART'S LAW by Charles Goodhart
Julie Yoo: MEDICAL NEMESIS by Ivan Illich
Jon Lai: BRAVE NEW WORLD by Aldous Huxley
Josh Lu: BOWLING ALONE by Robert Putnam
Emily Bennett: THE IDEA OF A UNIVERSITY by John Henry Newman
Completely agree with Jennifer Li's point, which is why we've built Retab (retab.com) as a modern document processing cloud for teams to build data extraction pipelines in record time.
Amazing.
Would love to learn the companies that will enable all of this and which ones will have the best chance to survive
bigideasdb.com lol
Great synthesis of where the infra stack is actualy heading. The agent-native infrastructure point about recursive fanouts looking like DDoS attacks is someting nobody talks about openly yet. Most current rate limiters and databases would just explode if a single workflow spins up 5k parallel subtasks. Curious if the solution ends up being specialized middleware tha understands agent semantics or a full rearchitecture of how we do state management and coordination.
The takes on automation in cybersecurity and unstructured data are directionally correct. Arguably the most interesting things about both cases is that the existing incumbents are offering capabilities that address those needs, but either the customers are not able to implement them properly and translate into value, or the tools are a bit of a vaporware.
The obvious winners will be those that "just work" and you can't argue whether or not they deliver value.