@mcuban Yes spot on. And since agents typically need to touch content and take actions in multiple SaaS apps, no one SaaS app is going to be suitable as "the agent platform"/ orchestration layer. Value shifts away from SaaS to the agent platform. https://t.co/AFcMZa9Ryv
@buccocapital That's an optimistic scenario -- infinite market opportunity, so free up people to move to more opportunity. Or, the market opportunity is limited so it's a race to cut costs and take market from competitors. And that is what the financial markets seem to be assuming
@jeff_weinstein@stripe The API usage volume for well-built enterprise agents isn't much (it is comparable with the human-scale workload it is replacing). The only obstacle has been the reliability of the agents. But that's also being figured out: https://t.co/Evv4NkOUe4
@nasdaily The vibe-coding stuff isn't the issue. AI agents automating the workflows is the issue. The only obstacle has been the reliability of the agents. But that's also being figured out: https://t.co/Evv4NkOUe4
@ctindale The vibe-coding alternative makes no sense. But AI agents automating the workflows is the issue. The only obstacle has been the reliability of the agents. But that's also being proven out: https://t.co/Evv4NkOUe4
@emollick Now that LLM benchmarking is reaching a point of diminishing returns, we've started doing application/workflow benchmarking. It's a better test of the "scaffolding". Would be interested in your thoughts: https://t.co/Evv4NkOUe4
@philotheis49253@stevesi Totally agree this is critical for reliable (enterprise) AI automation. But also, imo, this is not the job of the LLM, it is the job of the scaffolding/platform that harnesses the LLM. Eg: https://t.co/Evv4NkOUe4
@fchollet The value today is in the enterprise workflows have to get done. Humans do the workflows (biggest cost), they record their progress in SaaS apps (secondary cost). When agents do the workflow, human cost shrinks and the SaaS app is just a schematized db with low (human-scale) TPS
@levie Where is the app and the user? Where is the report glowing?
Where are the tickets and the workflow rules flowing? They have passed like an outdated style, like a free trial, The usage has shifted down and to the right, away from our sight, and into AI.
How did it come to this?
@fchollet Where is the app and the user? Where is the report glowing?
Where are the tickets and the workflow rules flowing?
They have passed like an outdated style, like a free trial,
The usage has shifted down and to the right, away from our sight, and into AI.
How did it come to this?
@stevesi As an aside, I don't believe "code will be written" is the best framing of the problem. That suggests that deterministic code is the materialized form factor for workflow intent. I think most work agents will directly interpret intent specified in natural language.
@emollick On the other hand, there are other agentic harnesses like https://t.co/NHloKVrnZJ specialized for greater process specificity and AI reliability (versus the generic broad "think"/"try" Claude harness where it's ok to get it somewhat wrong)
@emollick So the comparison should be between the Claude harness and products like n8n (deterministic workflow harness+ AI steps). n8n is definitely not AI agents.
@emollick There seems to be a basic misunderstanding. Claude code spits out "code" which is deterministic software. The value of Claude Code (or CoWork) itself is that it is an agentic harness.
@emollick@emollick that is a strange definition. If you went back five years and asked that question (what's "insane" to expect AI to do), you'd be badly wrong. So why do you feel it would be right now? The "training set" for our expectations is backward looking
@asaio87 I agree. The threat to SaaS isn't vibe-coding (though that will drive competition). The threat is that agents run the workflows https://t.co/aIB9IzbvSw