Key takeaways
- Three years out, Serban expects agents to do most routine work in banking, insurance and logistics, because the proof is already in production: the same workflow on the same data gives the same output, run after run.
- Trust comes from determinism: most of a FlowX.AI workflow runs deterministically, and agents call deterministic tools to verify themselves, so an auditor can see months later why a decision was made.
- Agents fail in the enterprise when they are treated as a model and a prompt. Production takes layers, like an onion: guardrails, evaluation with an LLM as a judge, observability, ontologies, and self-improvement when the data drifts.
- Next: small language models trained on each client’s own expertise and run locally, and a tool that lets non-technical people model ontologies and promote better agent versions.
Twelve years, from VR to AI
Mike
Welcome, I’m your host Mike Parsons, and I’m here at the FlowX.AI headquarters and I’m with the FlowX.AI technical gurus. So this session is going to be great. Today we’re going to get into this meeting place between mission-critical enterprise applications and the technologies as it’s applied to banking, insurance, and logistics. And what we really want to do is have a conversation with the experts. We want to get into a dialogue to understand what’s really happening now and also what could happen next, because this is a fast-moving universe, where some days you open your feed and it’s doom and gloom at all at the same time. And we’re all left wondering, what’s the real story? Well, it’s so good that today the experts that I have are two of the technical wizards behind everything that’s happening at FlowX.AI. They’ve also been my friends for over 12 years. So I’m excited to welcome both Serban and Bogdan. Guys, welcome.
Serban
Hi, Mike.
Bogdan
Hi, Mike. Thank you for inviting us.
Mike
Yeah, 12 years, huh?
Bogdan
Yeah.
Mike
We had some adventures in San Francisco.
Bogdan
Yeah, for sure.
Mike
We had some adventures in Moscow.
Serban
Yes, Mike.
Mike
And here we are. 12 years later, and it’s one of the most exciting times in technology. For you, Serban, when you look back at your whole career building applications, thinking about technologies, when you think about this moment right now. As a CTO and co-founder of FlowX.AI, how does this moment feel for you in technology?
Serban
Mike, it felt like it it was twelve years ago when we’ve met because I remember that we are playing with the latest technology back then. It was VR, AR, now is AI. It’s impressive how technology is change is still changing our lives day by day.
Mike
Well, it’s crazy, isn’t it? Because if you think about that moment we saw cloud was the big thing and then maybe it’s AR and VR. And now we’ve got more acronyms. It’s obviously AI. I feel like it’s a bit of a golden age for us in terms of possibilities. What do you think?
Serban
Yes, for sure is the golden age, because now we can really improve the lives of so many people that are working in enterprise, are working with technologies that are not that great and also are doing a lot of manual work they should maybe not do because it’s boring, is error prone and so on. And we can really change their lives.
Mike
Now, Bogdan, you’ve had a hand in making some of the large language models that FlowX.AI uses. That must feel pretty special to be putting together tools and technology like that. Do you feel like it’s a bit of a golden age, or is this just another technology for you?
Bogdan
Yes, for sure, Mike. So thinking about, I don’t know, latest twenty years. So I think in past two years with the large language model model, I develop developed like 20 years of stuff, right? So it’s pretty fast now to build anything, to come up with ideas and develop those ideas into really fast prototypes and validate it against the market or even against the other AI agents to see how it works.
Mike
It feels like the challenge in building has really changed, right? I remember in some of the projects we did in the early years together, we were kind of asking. I’m not sure, can this be done? It’s going to take a while. There was so much mystery. Now I think the question is how fast, right?
Bogdan
Yes. If you remember, we did rapid prototyping that time. Without AI it took us, I don’t know, four to six hours to build us some kind of POC of an application. Now it takes four to six minutes, right, to build something like that.
Mike
So it’s well we used to have our colleagues staying overnight and working all night just to get a bare bones application together, which is something now I think we could probably all put in a prompt. Yeah, I mean, heaven forbid you might even get me making some code, right?
Bogdan
Yeah, for sure. Even anyone can code it right now, right?
What’s more likely in banking
Mike
Well, that kind of sets us up for the topics that we want to talk about today. I’ve got some really fun questions and formats for both of you. I think what we want to do for all of our viewers is really debate and wrestle with some of the really big challenges and hot topics that are in the minds of the enterprise. Because we are really at this moment where everybody, up until now, they’ve kind of had their chat AI off to the side and asking a few questions to get an answer. And now we’re really talking about putting that agentic in the workflow and actually getting the AI to take action to work and execute and produce on our behalf to be a very active part of that workflow. So it’s going straight for mission critical heartbeat of the enterprise. So are you guys ready for some some fun but also some challenging questions? Questions? Okay. Let’s go with you, Serban, firstly. I want to do a scenario for you. What’s more likely? Okay, here we go. What’s more likely in three years from now, most routine banking work is still being done manually? Or agents are doing most of it?
Serban
Mike, I really think agents will do most of the work. It’s important now to see products like FlowX.AI that are helping with institutionalized AI. Moving from you using ChatGPT in a back office to having agents take over entire workflows. Governance that allows the operations of the bank to understand how those agents are acting. It’s very easy to see future like this where AI really drives the the bank and is not used as a side project, a ChatGPT where somebody just asks some questions.
Mike
Okay, so here’s a follow-up question. What do you see today when you deploy your technology into a bank? And it’s interesting that banks are actually showing quite a lot of willingness to engage here, which is a very positive sign. What do you see today that gives you this confidence? What do you see in the features that your clients are running on your platform in their enterprise on mission critical. What is it that you see that gives you this confidence?
Serban
The fact that we can show them running the same workflow, the same data over and over, ten times an hour 100 times an hour with the same output. So I can see that the manual work that took before maybe eight hours, now an agent can deliver in a couple of minutes or less with a bigger accuracy and without any kind of risk.
Mike
But then this idea of running essentially the same query and always getting the same answer, I think makes everyone feel like they can trust the system. Trust is a huge topic around AI and unleashing it, putting it, if you will, in the banking context, putting it closer to the money, that becomes the big risk. Will it be consistent? Will it be reliable? Is this. Is this kind of not only about governance but being thinking about AI and being able to assure that AI is going to be doing the job, that it can truly be mission critical? How do you think about this moment? How do we how do we know we’ve got it when we can ask the same query, get same consistent inputs and outputs? And so the trust can be there. Like, how does this actually happen? And what are you doing? And what are you working on today that gives you the confidence to say, yeah, look, agentic is for sure going to be taking over a lot of those manual, highly repeatable, consistent actions? What gives you that confidence?
Bogdan
So, Mike, think about: not everything is like a ChatGPT, you write something and it gives you some response. Behind the scenes in FlowX.AI, we have a deterministic workflow. Mostly like nineteen percent to ninety percent it’s actually running deterministically and validating and checking against different
Mike
And now you’re talking about these deterministic workflows. For those of us that don’t know what that is, just explain deterministic workflows.
Bogdan
Deterministic is something like you can repeatedly give some input data, apply an algorithm, a physical algorithm that you can demonstrate actually how the answer was coming from that specific algorithm and have the same result at, I don’t know, at five decimals.
Mike
And banks are doing that today with agentic workflows?
Bogdan
They are doing this with agentic workflows. They put deterministic tools inside the agents that agents automatically call them to verify themselves. Think about everything in the bank needs to be verifiable by an auditor, I don’t know, over six months, why the agent took that decision. And having this, it’s a really important part for the AI in banking. The predictability of an answer.
What’s more likely in insurance and logistics
Mike
This is great. So, deterministic workflows. It sounds like it is really at the heart of trust building within banking. Let’s go to another industry that’s like super regulated, a lot of compliance needs, which is insurance. This one for you, Serban. What’s more likely? AI mainly helps insurance employees do their jobs, you know, query this, summarize this, or agents start owning large parts of the workflow themselves. [unclear], we’re in insurance now, so it’s a different industry.
Serban
Yes. In insurance, we already see agents that are helping people to gather data, classify it, extract what’s relevant, they are not taking yet the final decision. We are still letting people be human in the loop and take decision. But at the end of the day, it’s just a decision for us in three years to see how how much we trust the technology. And I’m pretty sure that we’ll see faster the fact that we really trust the technology because we’ll just start to accept everything they suggest because we will have the proof that is accurate and will allow it to take decisions for us.
Mike
Okay, but let’s let’s test that for a second. Do you see this happening with claims, underwriting, distribution? Is this actually happening today in those key parts of insurance?
Serban
Exactly. These workflows are already automated until the last step, where you have human in the loop. The human that evaluates all the findings and all the decisions from the agent and just press accept or submit on that claim. But all the heavy work, checking the policy, from documents, classifying is already done by the agent. So we are pretty close.
Mike
Okay, okay. So we’re pretty confident here in both banking and insurance about what’s more likely to happen in the future. I think it’s interesting that you bring up human in the loop. Because we have to be a little bit careful, don’t you think, Bogdan? Because if we put humans in the loop at every check, we might actually end up creating a lot more work for the humans. So there’s like almost a design question about when and how you bring humans in the loop. How are we thinking about that in insurance?
Bogdan
Think about it’s better to let for example, persumer the judgment of the response and why you you took that decision than to take I don’t know, simple simple tasks that need to to be approved or something like that. Everything that can be automated and have straight rules on how this is it’s, I don’t know, calculated or evaluated against some text can be really easy automated and put an AI agent to do that.
Mike
That sounds like the quick win for any insurance company. What’s the highly repetitive standardized workflows that humans are just spending way too much time on.
Bogdan
You take the workflow, you split it in 10 pieces, let’s just say, and almost eight or nine of them are agentic steps.
Mike
And the real hope, though, is that then when you do bring the human in, it’s a high-impact area, but you also can better understand judgments, but I would hope that you can spend more time helping the customer because you’re doing less of the back office paperwork.
Bogdan
Yes, for sure. It’s very important in all these previous nine steps to grab the enough information, not all the information, enough information for the human to read it and take a decision, not put the decision in his mouth, for example, right? Only to give exactly what they need to decide it’s left or right.
Mike
Okay, so we’ve got the evidence now, I think. Banking and insurance, they’re on the way. Agentic is coming in. It’s making those efficiencies, helping move faster. Well, if we talk about moving faster, logistics is an industry that’s built on moving fast lots and lots of component parts, lots of complexity. The nice thing about this is we don’t have the same degree of privacy and security issues, but we have a lot more frequency of transaction. So Serban, what’s more likely? It’s quite a different industry. Logistics companies they’re just going to get better dashboards. It’s too complex. There’s too many moving parts. Or agents actually start doing some real operational work in logistics.
Serban
I really think agents will be able to win a lot in logistics because taking decisions faster will change the industry, which will change the model of the business in logistics. And you don’t need to look at a dashboard to reply to a lead request. You just need access to data. And that’s great because in logistics we have access to a lot of data. And AI is great to extract and act on that volume of data.
Mike
Now one of the key things I discussed with Cristina, the FlowX.AI expert in logistics, is what’s key here is the integration across a di number of different platforms. It seems like if there’s the integration with the data, in logistics, they can then put agentic to work and make real mission critical outcomes. How do you see that? Do you see that happening already with clients and with the technology?
Serban
Yes. We already see integrations with very old systems and I was surprised to see that in logistics you still have a lot of mainframe and a lot of DB2 databases.
Mike
And do you have any COBOL as well? I mean, come on, that’s got to show up somewhere.
Serban
Of course. Okay. And I I think it’s an important point that AI alone will not change anything, any industry. We’ve talked about banking, about insurance, about logistics. You need the guardrails around, you need the integrations, you need access to context, you need a way to model th that context, you need the control and governance in order to really change these industries.
Mike
So what I’m getting the feeling from both of you is that you’re quite confident about agentic acceptance. I think what’s interesting is if you look in the press and media at the moment, the questions around AI and controls and how much and how embedded. It would sound that you’re much more on the boom side of the discussion than the doom side. Is when you think about the future and what’s more likely, is that a fair characterization of your point of view?
Serban
Yes, for sure. Because we are seeing how AI can really change enterprise at heart at mission critical workflows. It’s a little bit like we’ve talked at that we’ve met doing prototyping. From a prototype till enterprise ready is a huge way. And we were doing this for a long time, being able to put cutting edge technology in enterprise. So we really think AI will change how these industries are working if you really understand how to extract the data from it.
Are we overreacting? Beyond the prompt
Mike
Perfect. So now we’ve kind of looked into the future. We can see a lot of evidence that we’re going way beyond ChatGPT on the side over here and it’s coming into the workflow, into the decision making, into the reasoning. I think it’s also we see the potential here, but what we have to do is really ask ourselves, like, what’s fact and what’s fiction? And are we overreacting to some of the hot topics in the industry at the moment? So I want to take a step back and I want to frame this next set of questions for you both around. Are we overreacting? So we need to be a little self-critical here. Let’s see how we go. Let’s talk about banking again. Is this the following statement? Tell me if you guys think this is an overreaction. Nobody will manually process a routine banking workflow in three years. So in three years from now, all that routine stuff is fully agentic. Am I overreacting in this statement?
Serban
Not really. It’s so easy and important to bring AI at all levels in industry in order to really change it and extract more more value f from it. So it’s very important to see banking how it transforms everything from user interaction to give feedback fast to a mortgage application, not wait for the back office to check manually towards risk checks and an anomalous extraction. So all the layers will transform in agentic workflows and is not an overreaction at all.
Mike
Bogdan, some people listening and watching us might say, well, these guys are optimistic. In three years, all that routine stuff at the bank is fully agentic. Why do you think many companies many enterprises and their technology partners struggle with the sort of outcomes that we’ve been talking about. Where do people get wrong the deployment of agentic from the sidelines and putting it into the heart of the game? What do you see the mistakes that others make?
Bogdan
Just by running a prompt doesn’t mean it works one hundred times, you know, and for for the use cases that you think of, it might it might get. So you need let’s just say a recipe for building AI agents. Okay, you need to to build the system, to connect to the data, look at the data, but especially to evaluate those agents. To grab a lot of information or use, for example, another AI as a judge for for that specific system. We call it the large language model as a judge. So having evaluation of the AI system that that you are running, you avoid the hallucination, jailbreaking from another another users or a lot of toxicity from from agent that responds very badly to the end user.
Mike
So do you think wha I’m as you’re talking, what I’m seeing is I think if I was to say it back to you, is that when people get agentic wrong in the enterprise, they’ve thought only of it as just a model, just a prompt. It seems to me you’re talking about systems thinking and seeing it more holistically. Is that the key to like unlocking all the value?
Bogdan
Exactly. It’s like you have you have the agent with the prompt, then you add another circle with the guardrails, then you add another circle with the observability and traces of the agent, and you’re just adding layers like a like an onion, right? Until you have a a better proper agent that can run without stopping in the production.
Autonomous claims: an overreaction?
Mike
Beautiful. Well, let’s go from banking to insurance now, Serban. So you have to tell me, am I overreacting? And let’s figure out how this comes together. So straightforward insurance claims will become almost entirely autonomous. Is this an overreaction? So this is the full chain of custody in the claim. Can we really get to such a nirvana?
Serban
Yes, Mike. Think about the margins that you are telling me that in logistics are very important. How important is it to be able to extract more value faster, respond at each signal. How important is for logistics to be able to have agents that observe patterns that are not obvious for humans. So it’s so powerful to be able again to bring AI at all layers from responding to a lead to evaluating a route of a truck and act much faster and with a lot more context.
Mike
I can see how excited you are about putting agentic at the heart of the enterprise and all these mission critical apps. I want to bring you back though to insurance and the claims in insurance. This is like as well, obviously, is underwriting and distribution. These are big parts of the insurance scheme. You have that same you don’t think we’re overreacting. We’re not getting too excited about agentic when we talk about insurance claims being largely agentic done. That’s not an overreaction. You think it can happen there in logistics and the banking equivalent too?
Serban
Yes. I’m already seeing it in insurance because we already have a human in the loop at the last step that only validates the findings from the agent. But now with AI in insurance, we can do even more checks than before were available with humans in the process. So we really can reduce the risk of each claim.
What the industry is still missing
Mike
So why? For some people, I think they’re going to think where the three of us are drinking the Kool-Aid, right? We’re all on the train for AI. What’s your opinion on you’re obviously seeing material value and evidence that agentic is already having today, in the enterprise, why do I feel like when I reflect on what people talk about publicly seems more negative? What are they missing? We talked earlier about going beyond the prompt and the systems thinking. What else are people missing? Because it feels like you’ve figured something out that I don’t think the industry has really figured out itself. What do you see as the missing ingredient?
Serban
I think everybody talks about POCs and they have a lot of POCs done by individual. But I’m coming back to institutional AI and to the guardrails and all the layers that Bogdan was talking about. It’s very important in enterprise to really bring AI that delivers the work and deliver it better. And to do that, you need everything. We need all our experience in doing enterprise software in real mission critical use cases.
Mike
So this is quite interesting because when we’ve challenged ourselves a little bit, are we overreacting? Are we drinking too much Kool-Aid. I think in both of your answers, and I’ll check this with you, Bogdan, I’m hearing the following. It’s way more than the model, way more than the prompt. It’s systems thinking. It’s looking at the patterns and putting the human in the loop at the right time and not having the limitation of pilot proof of concept thinking, production thinking, institutional AI. Are those the secrets that you guys have figured out?
Bogdan
I think so, but we I can add more. So not only because you know, once you design an agent, it doesn’t stay the same. Actually, not the agent itself, but the data that comes into it. You know, regulations change, documents change, format, you require more more data for a specific use case. And then what do you need to do with every kind of system? You need to modify it to adapt to the that specific new data. Actually, what we did, we put recursive self-improvement, it’s called. That automatically an agent identifies new patterns or drifting.
Mike
Now, this one, recursive self-improvement is obviously a huge topic right now. If you listen to the frontier models, that’s what scares them a little bit about the future. Are you actually doing recursive self-improvement to make products info is better today?
Bogdan
Yes, actually we have this currently in the platform. We detect we have a lot of layers on observability. We detect when an agent is drifting from their pattern and how to deal with data. And automatically we come with mutations for that agent that test those new patterns. And comes with a proposal for for a customization that will upgrade the agent.
Serban
Mike, when we are talking about putting AI in production, we need to think about big loads. We need to think about a lot of data. So classical ChatGPT prompting will not work. We need to talk about ontologies, observability, and being able to act and in this complex real life scenarios. A procurement use case. You need an ontology to model all the laws in order to be able to act on this complexity and volume of data.
The proof, in production
Mike
This is great. So let’s just recap before we go to the third installment of our talk. We’ve really kind of captured this idea of what we see happening in the enterprise right now. We’re seeing a lot of characteristics of how agentic can win, how it can provide incredible value. Not just on the side with a few answers, but putting it into action. We’ve had some key concepts come up like deterministic workflows. We’re going into systems thinking. We’re thinking really what it takes to work at large-scale, cross-border, cross-department. This seems to me, as exciting and as elegant as just a prompt is, there’s so much more to the story of winning when you talk about mission-critical and agentic workflows. So now, what I would like to do together is wrap up this conversation and help people understand your experiences in the reality of these mission-critical operations inside the enterprise. So, Serban, I want you to really give me the proof. I want you to give me the evidence that you have for putting agentic in the heart of the business. The first one’s for banking. What I’d like you to prove to me and to all of the viewers. AI can run mission critical banking workflows in production. And here’s the killer word today. So I want you to think about like maybe an example of a function that you see working today from FlowX.AI on a bank in a mission-critical area, give me something real and tangible that is really happening. It’s not Sam Altman and Dario getting too excited and promising the world. Give me the reality.
Serban
Yes, Mike. I can show you how easy is for AI to have the same output on a mortgage application ten times. Ten times so same data, same output.
Mike
And are we just talking about a summary?
Serban
No, we are talking an actual extraction of data, eligibility, validating with data inside the inside the bank. So the the real process that happens today in a back office between multiple roles done by AI
Mike
Is this just on the financial docs? Or is this also like deeds and titles of properties? Can it or is it just the finance docs?
Serban
No, no, it’s all the properties, all the data being able to take over the entire process end to end.
Mike
You see that happening today on clients executing on real mortgages in a bank?
Serban
Yes. And again, you can run it ten times, same output on the same data.
Mike
Just one country, or have you seen it in more than one country?
Serban
In more than one country. In different languages with different documents. And it’s not a simple agent where you give the mortgage application and you ask it to give you the response if it is eligible or not. You will see that there is a ton of complexity to really achieve this.
Mike
Okay, okay. Let’s take insurance. Obviously, claims, underwriting, there’s a whole dimension of risk analysis that’s happening. What are you seeing today in insurance on those key actions inside the business, the mission critical steps? What are you seeing? What evidence do you have? What’s getting executed today?
Serban
Extracting data from those handwriting insurance claim and be able to cross-check versus a policy. And you just wait to see how many attributes are important for a claim in insurance. And you’ll understand why AI will change this industry also.
Mike
Is it getting involved in maybe, Bogdan? Okay, so we’re scanning for the handwriting, we’re looking at the policy, but there’s a there’s some decision making and reasoning that needs to happen after that, right?
Bogdan
Think about it, Mike. For example, for a policy for a calax and now with the AI you can understand actually, what’s in the image from where the car is coming, how much was not actually the actual speed, but if it was a spinny or not.
Mike
So, are you saying that right now you’re seeing FlowX.AI process handwriting, digital documents, digital images as part of that claims process?
Bogdan
Exactly. It’s a claim processing, describing exactly the pictures of the specifics.
Mike
And is it just humans making the decision at the end?
Bogdan
Just just validating against the the rule book or rules checks and pointing out like a a scoring for each of them that p particular part in order for human to take this in.
Mike
So it’s doing the full chain and then presents it all to the human.
Bogdan
Exactly.
Mike
If it’s doing all of that, like I just imagine, like I struggle to read my wife’s handwriting, right? You’re saying you can do handwriting, you can do images, you can do the digital docs. That sounds like a huge gain in efficiency.
Bogdan
Yes, for sure.
Mike
And it’s happening right now.
Bogdan
It’s happening right now.
Mike
Let me do my check. Multiple languages, multiple countries.
Bogdan
Multiple languages, multiple countries. Even documents in different language. We synthesize it in the language for the output for the end user.
Mike
Okay. Serban, you were going to say something?
Serban
Yes, I wanted to say that we can also show you how we can monitor that in a couple of days, in one year, the agent performs the same or even better because we can use self improvement on it to make sure it responds on claims that are a little bit different because we cannot validate from start all the models, all the possible claims. So it’s very important to make sure that we monitor the agent and we understand its performance.
Mike
When I was talking with Cristina about logistics, she talked about this paradigm of: we’ll figure it out later. And it’s that moment where the truck with the goods gets to reception and they can’t match up the digital document, workflow, and acceptance. And then what they do is they put that package to the side in reception, like just put it over there. We’ll figure it out later. So, surely, when we think about the evidence, you can’t. Are you what are you seeing at this moment where they’re all saying we’ll figure it out later? Can your technology actually make a difference so that we can actually marry up that analog and digital world together? So we don’t have this massive inefficient, all these things that get reconciled days, sometimes weeks later. Is that really happening now?
Serban
Yeah, and it’s it’s happening at volume. Because in logistics we run this kind of agents ten thousand times, a hundred thousand times a day. And it’s very important to act fast. People need the responses in a couple of in maybe thirty seconds, a minute. So is it very important the speed that AI brings in this industry?
Next: small models, and AI that helps clients use AI
Mike
So it’s interesting, isn’t it? Like the themes of what the three of us have been discussing, we’re seeing like a promised world where speed but also potentially accuracy because there’s like so many opportunities for humans to make natural human mistakes, particularly on those low level, highly repetitive workflows. So it seems like there’s a lot of confidence and a lot of optimism about that future. But on the other hand, I think there’s hard work to do, deterministic workflows, systems thinking, adaptive intelligence, self-improvement, making sure that it’s production ready, not just a nice pilot. Let’s start with you, Bogdan. So for the next year, what’s your focus to take things to the next chapter when we talk about mission critical enterprise technologies, when we think about a lot of agentic workflows? What’s the big thing you’re working on? What’s the next big jump you want the FlowX.AI platform to take?
Bogdan
So for example, right now, large language model is gives you intelligence, right? That you can use it to do some stuff, right? You have your own data. So once you use that intelligence with that particular data, you you actually gain some expertise about it. So what we are starting doing and already done some prototypes is to encapsulate that specific expertise into a small l language model that are specially built for the customers. So instead of, for example, in logistics to run 10,000 times with the frontier model and spend some money on on them, actually you get that as a training data that you train your expertise in-house. And that specific small model will work like your specific model for logistics.
Mike
Okay, so let’s just capture what you just said. So most people will experience AI as this question and answer. And we’ve firmly moved it into agentic workflows, reasoning, decision-making, orchestration. Okay. And one of the topics that’s come up today is maybe, you know, like building MCPs. Then there’s, of course, all the agents that FlowX.AI already has. But did I just understand what you said? You’re now thinking about building small, large language models for the clients of FlowX.AI. And this must open up local, open, and sovereign AI topics.
Bogdan
Exactly. Exactly. You just run locally everything. Once the, let’s just say, you have the pipeline for training exactly with your expertise, and you just use the model to continue with the expertise without needing for using the frontier model.
Mike
Now, that would have some huge advantages, namely the sovereignty of it, meaning that you’re not providing data to a frontier model. You’re not helping them train their own models. You’re training your model.
Bogdan
Exactly.
Mike
You get the control and the governance around it because it’s your model. It’s trained on your data. That sounds hard. And if we look at the balance sheets of OpenAI and Anthropic, it looks rather expensive. Is that too good to be true, Bogdan?
Bogdan
I don’t think it is. We we have pretty good results. We already started, for example, with a simple use case like classifying documents, right? Once you classify we have five types of documents and run them to to understand each page what type of documents, it’s pretty easy to do this.
Mike
And you’re saying that you’re you’re referring to I think you have more than twenty large language models already on Hugging Face, right?
Bogdan
Yeah. Yeah.
Mike
So anyone watching this could go and download those.
Bogdan
Yeah, for sure. Okay. We already put some of our work, especially on the part of not only large language model, but also traditional machine learning because we cannot forget the, let us say, the mathematics behind and also the deterministic behind the the mach the classical machine learning. So this is how we do it. This is the same how TypeSafe AI brought it us a new kind of large language model, a classifier, right? This is also the same thing that we are doing, but with different kinds of tasks and specific build for the customers’ project.
Mike
Okay, well, it sounds like you’re going to be busy for the next 12 years. Serban, with all of the progress with FlowX.AI, working on clients, and all the opportunities we’ve talked about today, what do you focus on for the next year? What’s got you captivated, curious, energetic? What are you building next?
Serban
So with all these technologies that we’ve talked about, we need AI to help our clients leverage AI. So I’m focusing on building in the platform a tool that allows somebody that is not that technical to leverage all this com complexity, to leverage ontologies, to help him model the data required for his agents into ontologies. To leverage self-improvement, to understand when he needs to promote a new version of the agent because it starts having better results. And everything, all the layers that we’ve talked, integrations, human in the loop, require AI to help somebody that maybe is not that technical.
Mike
That has a big theme for me of democratizing mission-critical, agentic workflows for the non technical user. That I mean, that sounds like a like a game changer.
Serban
Exactly. Because these are the the people that knows what is important for the business. So they need to be empowered.
Mike
Yeah. Well guys, I want to say thank you very much. I think we’ve firmly made a case for not only agentic, but how we’re going to accelerate the enterprise. It feels to me like you’ve given so much evidence for the real way to do this properly. It’s not just a prompt, it’s systems thinking. It’s deterministic. It is self-improving. I think what’s so fantastic is I feel like today we got a little bit of sense of how to make smart decisions to accelerate the enterprise, to put a bit of agentic AI magic dust on top of all the good work that those enterprises have done. Thank you very much.
Bogdan
Thank you very much.
Serban
Thank you, Mike.
Bogdan
Thank you.