Jesse Shiah
CEO & Co-Founder · AgilePoint
Position Evolution
3 tracked across this operator's appearancesSame operator, on the record, on the same topic, at different points in time. Each delta below is anchored to verbatim transcript spans verified against source — no paraphrases. This is the alumni-graph moat: SemiAnalysis cannot reproduce this query because they don't have the speaker-stable corpus.
End-to-end orchestration drives business outcomes
Consistentconfidence 91%Shiah repeats the 80/20 framing almost verbatim across both appearances, signaling this is a core, rehearsed thesis rather than an evolving view. The consistency is notable because it anchors AgilePoint's entire product positioning and has not been softened or qualified over time.
"those may be 20 % in terms of the number of the application, maybe only 20 % of your business in your company, but they drive 80 % of the business outcomes."
Source on theCUBE ↗"about 20 % of the applications are actually that cross- functional end to end and the rest of 80 % maybe a lot of application for functional specific and tied to different platforms. But the 20 % of the end- to- end actually drives probably 80 % or more of the business outcomes."
Source on theCUBE ↗No-code architecture enabling AI trust
Hardenedconfidence 82%Shiah's no-code trust argument grows more specific in the later appearance, moving from a rhetorical challenge about dynamic code trust to a concrete architectural prescription. The later framing ties the no-code requirement directly to end-to-end orchestration as the highest-value AI use case, raising the stakes of the position.
"Who can trust that dynamic generated code and go to execution? Which enterprise can trust that? I think that's also why up to 90 % of the AI PoC stays never going into production."
Source on theCUBE ↗"that's not generating code, that's not modifying code from day one. And in this case here, if we want to enable agent can actually adapt your business logic of your applications, especially we say the most valuable use cases, that end- to- end orchestration. That means that the application itself, your automation, your orchestration has to build in a way to enable agent to change them, change the logic, but without involving code changes."
Source on theCUBE ↗AI Control Tower abstraction layer
Shiftedconfidence 78%Both appearances cite the 2017 origin of the AI Control Tower, but the later interview adds a concrete operational benefit: agents can be adopted without changing the underlying business process, and business users need not understand AI. The framing shifts from historical credibility to a democratization and cost-reduction argument, reflecting growing enterprise pushback on AI training costs.
"We call it AI Control Tower layer, the framework. We actually developed that back in 2017 when we started seeing the AI, the open AI started doing something."
Source on theCUBE ↗"we have another abstraction layer called AI control tower layer. We developed that back in 2017. So that's where the old agent can go to the AI control tower layer. So what that means is you can operationalize AI agent without physically change the business process."
Source on theCUBE ↗All theCUBE appearances (4)
AI Agent Builder Summit | Jesse Shiah, AgilePoint
GUEST · AgilePoint · CEO & Co-Founder
AI Agent Builder Summit | Jesse Shiah, AgilePoint
GUEST · AgilePoint · CEO & Co-Founder
AI Agent Builder Summit, Encore Presentation | Jesse Shiah, AgilePoint
GUEST · AgilePoint · CEO & Co-Founder
AI Agent Builder Summit, Encore Presentation | Jesse Shiah, AgilePoint
GUEST · AgilePoint · CEO & Co-Founder