Future Ventures: Scaling with Clarity
Future Ventures: Clarity at Scale is the podcast for founders, operators, and investors who are building companies worth owning for the long term — and who need to think clearly about capital, structure, strategy, and growth to get there.
Each episode cuts through the noise around scaling: how to structure a deal, how to position a business for institutional capital, how to build operational leverage without losing control, and how to make the high-stakes decisions that compound in value long after the moment has passed.
Hosted by Maxim Atanassov — a four-time founder and the Managing Partner of Future Ventures Corp. Since 2018, FVC has invested in, incubated, and scaled companies across sectors — with a focus on platform opportunities that compound in value. Maxim's background spans executive leadership inside Canada's largest energy companies and senior advisory at Deloitte and EY. He's a CPA-CA who has sat at the table where capital gets deployed, governance gets built, and hard decisions get made. Now he helps founders get there faster.
New episodes every week. Subscribe wherever you listen.
Future Ventures: Scaling with Clarity
Stuart Frost - Scaling AI Beyond the Hype: Building Businesses That Deliver Real Value | FV Podcast Ep.73
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
Artificial intelligence is changing how businesses are built, how decisions are made, and how companies compete. But while AI demonstrations are everywhere, measurable business outcomes remain much harder to achieve. Stuart Frost, Founder and CEO of Geminos, has spent nearly four decades building and scaling technology companies, taking Select Software Tools public on NASDAQ, selling DataAllegro to Microsoft for $275 million, and helping launch dozens of startups through his venture incubator. Today, he’s focused on helping enterprises move beyond AI experimentation toward reliable, scalable, and measurable results.
In this episode of Scaling with Clarity, Stuart joins Maxim Atanassov, Managing Partner of Future Ventures Corp, to explore what it actually takes to make AI work in business. They challenge the assumption that more powerful language models and autonomous agents automatically produce better outcomes, examine why large organizations struggle to turn innovation into execution, and discuss how AI is fundamentally changing startup economics. From causal AI and enterprise decision-making to corporate venture capital and organizational resistance, this conversation offers practical lessons for founders and leaders navigating the next wave of technological disruption.
Five key topics covered
The new economics of building startups: How AI is dramatically reducing product development costs, accelerating customer discovery, and transforming traditional approaches to sales and scaling.
Beyond LLMs and autonomous agents: Why combining language models, causal AI, knowledge graphs, and business rules creates more reliable enterprise solutions than relying on generative AI alone.
Why enterprise AI adoption stalls: How bureaucracy, procurement processes, organizational resistance, and risk aversion prevent companies from realizing measurable AI value.
From AI pilots to enterprise-wide impact: How selecting the right initial use case, demonstrating value quickly, and establishing scalable foundations can accelerate adoption across an organization.
Corporate venture capital and startup growth: Why strategic corporate investors can open doors for startups but also create conflicts between customer priorities and broader market opportunities.
Three key insights
Start with the business problem, not the technology. The strongest AI applications begin with understanding what customers need to accomplish and the value of improving that outcome. Technology selection should follow the problem, rather than dictate the solution.
Reliable AI requires more than intelligent predictions. Language models excel at interpreting information, but enterprise decisions often require causal reasoning, enforceable business rules, traceability, and human judgment. The objective isn’t perfect automation; it’s consistently better decisions.
Prove value quickly, then expand. The best first AI project isn’t necessarily the one with the greatest theoretical return. It’s one that can demonstrate meaningful results quickly, build internal champions, and create momentum for broader transformation. Stuart illustrates this through a railway application that reduced delay-attribution work from 8–10 days to minutes.
Links & resources
Stuart Frost on LinkedIn: https://www.linkedin.com/in/stu-frost/
Geminos: https://geminos.ai/
Future Ventures Corp on LinkedIn: https://ca.linkedin.com/company/future-ventures-corp
Subscribe to Scaling with Clarity on YouTube: https://www.youtube.com/channel/UCZgPPHfPBZz-r5NQLq_dWfA
About Stuart Frost
Stuart Frost is a serial technology entrepreneur and the Founder and CEO of Geminos, an enterprise AI company focused on improving business decisions through causal AI and complementary technologies. Over nearly four decades, he has founded, built, scaled, and exited technology ventures, including taking Select Software Tools public and selling DataAllegro to Microsoft. His experience spans enterprise software, venture incubation, and the commercialization of emerging technologies, with a continued focus on turning innovation into measurable business value.
Welcome to Scaling McClary. Today's guest is Stewart Frost, a serial entrepreneur who spent more than three decades building the scaling technology companies. He took select software tools public on the Nasdaq, sold data led growth to Microsoft for 275 million and went on to build and incubate dozens of startups. Today, as founder is CEO of Geminis, he's tackling one of the biggest challenges in business: how to turn artificial intelligence from impressive demonstration into reliable, measurable results. We're exploring why enterprises struggle with AI, what they're getting wrong, and what it takes to make technology genuinely useful. Stuart, welcome to the show. Thanks, thanks, and thanks for having me. I am super excited about the conversation today. I mean, I obviously you bring in uh a pedigree of talent and pedigree of experience that like a lot of founders will find useful. But uh what I wanted to start, uh Stuart, it's kind of like the the back to the origin story. So um you spend much of your professional life building companies as a rentry. You've you've taken a company public, you sold another one to Microsoft, then you you had a venture studio. Um what is it about building businesses that just keeps pulling you back? Why aren't you retired? Like like you made a ton of money. Like, obviously, there's some gonna be at the gravity that's pulling you back.
SPEAKER_03Uh it might be insanity, I'm not sure. Um, it's a good question. Uh it's either insanity or addiction, right? And maybe it's a fine line between the two. Yeah. Um, I'll be honest, I just really enjoy it, right? I mean, I think especially at a time like this, where we've got the opportunity to reinvent the way we build startups. I've actually been writing a few blog posts recently on not just the software development lifecycle, but the whole product development lifecycle, how that's changing, and also how the sales motion is changing. And you know, think about it, those two things, RD costs and sales costs, and the challenge of scaling both, have been the kind of death of many a good startup, right? Um so the opportunity to change that dynamic and and massively reduce the cost and the time involved in both of those activities, uh, it's it's fascinating to me, right? And bringing that to bear and using that as we uh develop Jabanos, yeah, it's fascinating. So, what what else would I do?
MaximYeah, I know it's uh it it it it's it's strange. Like um I wake up every morning, just can't like I can't wait to start working, and and and to other people this seems very, very foreign. For me, it's like I just can't, like, it's like it's literally I find that the current time, the current environment is so formative that like I feel like if I'm not I'm missing out, and it's like I'm a kid in a candy store, I just want to play with tools, I want to build, like and whatever I could do you yesterday in in six hours, now I can do in six minutes, it's just insane.
SPEAKER_03Absolutely right. I mean, you know, I as you said I've been doing this for over 30 years, I think it's almost 40 years now, actually. Um, and you know, a lot of the things that we've learned in terms of market penetration and so on, the whole Jeffrey Moore stuff, crossing the chasm, and all that. I've been a huge fan of that. I've applied it successfully in startups. Um, but the sheer speed of what we can do now is changing that. Um not you don't necessarily throw it all out, right? But you it definitely needs to be reconsidered and uh and see how we can, especially on the sales side, right? I mean, often with such a long sales cycle, it might take you a year to realize that a salesperson is not really cutting it, they're not getting the messaging right, because it's only going to show up if they close deals or not. You can't be on every call, otherwise, yeah itself is the founder, right? Um now we can look at every transcript or AI can look at every transcript. Uh, it's a good quality transcript, which is yeah, that's helpful, right? So we can get a much better view of what the customer's asking for, what the salesperson is telling them. Uh, you know, are we getting our message out there? Um and all the other aspects that come with that. Um and and catch it much sooner and train people appropriately. It's not a matter of firing them, it's a matter of can we help this person get the right messaging? Um, so I'm I'm looking at all of that and actually using the Geminis technology to build a knowledge graph of Geminos that underpins all that work as well. So the AI deeply understands what we do as a company and what our customers need. Yeah. And let's review every sales call, you know, maybe in real time before too long, right? Uh, and give people hints as to how to best serve the needs of the customer and uh and get rid of that as quickly as possible, right?
MaximWell, there's no reason why you shouldn't be doing this, especially like I mean, everyone is talking about the the company brain, you're talking about knowledge craft, but like there's so much data, there's no reason why you're not pulling this data and turning it turning it into actionable insights or signals that you can act upon.
SPEAKER_03Yeah, absolutely right. And so that's the thing. I think so far there's been a lot of effort, obviously, on the software development lifecycle, how much faster that's become, and so on. Um, and and for me, the other side of this is that product development lifecycle. It's you know, ideas from my head and and in conversations with customers, how quickly can we now develop those and turn them into real shippable products? That's like hundreds of times faster than before, with far fewer resources, right? So you've got to leverage that, you you've got to figure out how to use that uh in your everyday business life and how to get the power of that as well to be pervasive across the company. And this is not about having agents running the company and making all the decisions, it's about helping us as human beings make much faster decisions, get stuff out to customers quicker, and and reduce the sales cost dramatically as well, right? Because so much gets wasted.
MaximNow, obviously, everyone has moved to or is in the process of moving to AI SDLC. I want to double-click on this and get your perspective on just two elements. The first element is the principles around SaaS versus agentic, kind of like if you're building products, how are you building? Is is everything that you're building now to be agentic first? And two, um, what's your thinking frame of reference around customer discovery? Because just because you build you can build faster doesn't mean you're building the right things. So can I give me your perspective around is it agentic first? And how do you go about customer discovery?
SPEAKER_03The end of the day, I don't think any technology should be first, right? I just fundamentally, um, it doesn't matter how powerful it is, that shouldn't be the thing that you talk about first, right? I think for me, what I want to deeply understand is what is the job that my customer needs to do, and how do we improve that? Um, and what value can the customer get from that? Yeah. And then only then do we say, okay, which parts of the technology stack do we need to solve that problem?
SPEAKER_01Yeah.
SPEAKER_03Now, of course, there are lots of common patterns here, right? We tend to deal with customers that have a lot of text, a lot of data, structured and unstructured. How do we gather knowledge from that? And really importantly, how do we make decisions based on that information? Right. So there are some aspects then of the technology stack that we know we're gonna need. We're we're gonna need an LM to understand the text, we're gonna need agents to run the workflow, um, we're gonna need causal AI to make the final decision, um, and we're gonna need a knowledge graph underpinning it all that helps us actually understand all of that and and get the accuracy that we need. Um, and also a rules engine, uh, very important. Um, you know, it's no good the LM just going off and and agents going off and making decisions based on guardrails, which mean very little in practice, but the hints at best. We need to enforce stuff with a real rules engine. Um, agree. Right? So it's that combination of factors. So is that agentic first? No, not really. It's what's the customer's problem? Let's piece everything together appropriately then and use the right form of technology, right form of AI to address each part of that problem, right?
MaximUm for for those of our listeners that uh uh need a little bit more clarity around the rules engine, can you juxtapose safety guardrails or guardrails um in a model versus rose engine and kind of like you know, suggestions versus the role, kind of like what does it mean?
SPEAKER_03So rules engines have been around a long time, right? Um, in terms of you know, there's plenty of an open source and that kind of thing. And you know, what they do is given a certain set of data, they'll tell you the boundaries uh that you can operate in, and that might be for a piece of equipment, there might be hard limits on temperature and pressure, for example, and you don't want the thing to blow up if you exceed those. So pretty fundamental. Um, and of course, you know, agents, etc., right now in the raw should not be used for that kind of thing, right? Uh, because they don't always reliably follow guardrails and suggestions and prompts. So just it's just a no-go area. So what we've done is built in one of those traditional rules engines, um, so that you know we can check, and and the the harness around the agents that we build when we're building a solution of the code will check the rule and not just let the agent uh you know make that decision. Uh it'll it'll stop it before it does. So that's for me the big distinction, right? These are hard and fast actual rules. Yeah, you know, in a traditional rules engine, there's been yeah, that's decades of uh of work have gone into those things. Um, why not reuse that? Yeah, you know, because trying to build that into agents is not working very well because the very nature of the technology underneath them we get steadily better. But I just think if technology's there and it's uh it's proven, um why not use it? The neat thing is now we can use AI to discover rules. So we can, for example, go through contracts and go through uh manuals and that kind of stuff and extract rules and populate the rules engine with that, and then curate those, check them, uh, and so on. So we can make that whole process a lot faster, a lot more efficient, and then you know deploy the engine to solve the problem.
MaximYeah, it's it's amazing what it can do. Um recently I was trying to build a capability capability map for the team. Okay, we are hearing now. If the outcome is seeking is there, what do we need to do from a team capability respect to be able to equip the team? And so I just like I I asked the AI that we use, it's like, okay, go and inventory all the work we do, who does it, what are the handovers from system to from machine to machine or machine to human or human to machine, and did a pretty amazing job in identifying this, and then obviously this earth is uh the input in terms of us kind of coming up with a capability map, but it's amazing what it can do um when you have structured it the right way. Now, on the structure side, um I have uh massively adopted personal agents, and so instinct is my favorite, but I use other like uh I use Muse, I use Claude. Um I was playing around over the last couple of days trying to see can I put a harness, can I put some car rails and rules? And so instinct flat out told me that there's no way that it can do muse is a little bit more even more rogue when it comes to like so from your perspective, how is there a way that you can you define your rules at a global level? And so any technology to plug in that says these are my rules, stick to my rules, don't break the rules. Is there a way to do so? Or how do you make personal agents work?
SPEAKER_03Well, the problem is, right, you're with a personal agent, you're delegating responsibility for doing most of the work to that agent, and as you rightly say, right, it's it's kind of mind of its own. Well, it doesn't, but you know what I mean, right? Yeah in in this context at least. Um, and and it's it's a fundamental thing, isn't it? You give an agent a goal and then you give it guidelines, really, right? They're not guardrails, guidelines as to what to do and what not to do, but the goal is always primary to an agent, so it will ignore those uh guidelines if it chooses to to get if it thinks it's necessary to get to the goal. So what we're doing is really inverting that. Um, and we're saying, look, if there is a goal for the business that's got to be optimized, let's build a proper causal model for that because the underpinning math there is is much more powerful than an agent will ever be. Let's use agents to feed it and and to understand and manage the workflow around it, but at the end of the day, let's do a proper data-driven decision that you know drives the business outcome uh that the customer needs, and use the agents in the LLMs then to, like I say, you know, understand the text, understand the workflow, gather the information and feed it in. Uh so let's use the an appropriate form of technology that is well proven now. The math works great and on calls. We've been doing it for years for all in all kinds of different industries. Why try and use an agent for that? I mean it just doesn't work. You know, it probably won't for quite a while, right?
unknownYeah.
MaximStuart, in in our last conversation, you talked about that you primarily work with companies or divisions of companies with a billion plus and dollars in revenue. And so we're talking big companies with with big resources and capabilities. Um, from your perspective, how many of these companies actually make well-informed, substantiated decision, and how quickly can they get to clarity to make those decisions?
SPEAKER_03So if you're talking about day-to-day operational decisions, right?
MaximUm, yeah, like I mean, how do I know like that I'm doing the right capital allocation? Like, is this the right company to acquire? Like, like, obviously, the bigger the decision, the more vigor it should have. And and some of it is art, some of it is science, but like I feel like there's too much reliance on the art and not real, not enough reliance on the science, or the science is dated. Yeah.
SPEAKER_03Well, I mean, today, like, if you go into most industrial companies or any kind of company, really, and they say, you know, yeah, we you we do data-driven decisions. What they really mean is they've got some spreadsheet that's full of macros and stuff, and they do some BI, right? And and maybe we use AI on top of that to help. Yeah, and a lot of those macros in the spreadsheet were written 20, 30 years ago by someone who's no longer at the company, um, that breaks all the time, but no one really knows, right? Um, so they're not really making truly data-driven decisions at all. What they're doing is is applying a lot of expertise uh through that, that's still in humans' heads, right? Somewhat aided by the data. Um, too much gut field, too much, too many emotional decisions. You know, we saw this in a in a supply chain uh a couple of years ago, where um if a shortfall of some particular inventory, some component fell short and stopped the production line, the person responsible for that got yelled at pretty hard, right? Somebody shut a multi-billion dollar production line down for a week while that part was sourced and so on. So, what they tend to do then is make sure that part is over stocked, right? So that never happens again. Um, or they, you know, there's a lot of rush shipping and everything to solve that problem. Um, what you need to do to have a truly data-driven decision, to my mind, is have a math that actually supports that um and an engine that supports that. That's where the causal AI really comes in. Um, so yeah, and it's brilliant. You you can set an outcome, understand cause effect chain that kind of gets you there. Business people can understand that, it's in their terms, it's it's their variables, it's their business. And then we can put the math underneath it with the uh data history and so on that they give us. Yeah, and the neat thing then is if an outcome's changing in a bad way, good way, whichever, yeah, you can see what the root cause is of that, but also you can test interventions. So I can say if I change the temperature by two degrees on this industrial process, what's gonna happen? Right? Is it gonna fix the problem or not? And I can play around with that in the math without actually uh necessarily doing it in in live production. Yeah, um, so for the first time, you've got this ability to do truly data-driven decisions. What we've then got to do is get there as quickly as possible in terms of gathering the data, gathering the information, might come from a lot of text, might come from uh some structured data as well. That's where I think the power of LLMs and agents really comes in, then to gather that information, make sure it's you know fits the rules, etc. We can check the rules against it as we go, um, and then feed it into the causal model, and we end up with truly data-driven decisions for really the first time in history, I think, you know, at any kind of scale.
MaximSo when you're having this conversation with customers, I mean, obviously that that uh makes a hundred percent sense. Like, why would you not want to get there? Um, what's the biggest hurdle? What is the biggest hurdle of like what is perhaps stopping companies from saying yes to this?
SPEAKER_03So, noise, noise in the market, right? So they're bombarded with oh, we can vibe code this, right? We can LNs are gonna get there eventually, they're gonna understand causality, no, they're not. Um, and it's so for the typical business exec who doesn't have time to you know understand what the latest model can do and what it means and everything, right? There's bombarded with stuff. Um, and it's very hard to pick out then you know a better way forwards. Um now, once we get to them and we explain what we do, frankly, it's a really high hit rate, and it doesn't take us very long. That's the beautiful thing about this, you know, selling tools to technologists, which we were until last year, is a long sales cycle, right? Because you've got to persuade them that you're always better. And we were ending up building solutions for the business just to prove that it was better, which is great, but you know, we're still same hurdles and selling to the technology side of it. So I'm to the business, we can go in and say, let us show you. We'll build something in a few days that demonstrates to you that we can solve your problem. It's not going to be the final app, we're not vibe coding this, we're doing it right, but we'll show you, you know, on a basic knowledge graph with a basic causal model that it drives the right outcome for you. And we'll explain that in your terms. And once we do that, they're solved, right? Because they they don't get that from any anything else. If someone's vibe coded something, there's too many holes, it's not going to be a recurring solution to the problem. Yeah, and we can we can show that. Um, so that side of it goes really quickly. You still got to get through contracting and procurement, but you know, it was nevertheless, yeah, yeah, yeah, for sure.
MaximUm out of the C-suite, which persona is the easiest to convince? Uh CEO, C O O, kind of like what's your what's it take?
SPEAKER_03So it's basically I would say the CEO or the head of a business unit, right? Um, so it's they've been tasked typically by the board to do something cool with AI, show some value. Yeah, they're struggling with it. Gartner just put out numbers. I think only 13% of large enterprises are reporting any value, measurable value from AI. So very early in this, right? And that value could be really small in one division. So there's a lot to go at, and people are struggling with this. Um, and I think we've got a great answer to that problem. And yeah, we can go in and say, look, you know, copilots and everything, it's cool, you know, you can maybe write a PowerPoint a bit quicker, whatever. But in give us your key decision that you your business needs to take every day. Yeah, it's done at some scale, right? It involves a few people. And let us show you how we can get that down from taking dates because it's a lot of paperwork, phone calls, etc., multiple data sources. We'll get it down to minutes. And we'll do it with best in class accuracy. Not perfect, not claiming that, but it's going to be as good as your, in most cases, as good as your very best employees, right? Yeah. So we're leveling up your organization to the very best levels, giving you more traceability on it, more transparency on those decisions, and doing it, you know, in a thousandth of the time, all right. We'll go from eight days to eight eight minutes, you know, it's it's a big difference, right? Um for sure. Yeah. So that's that's the kind of fundamental story. And once you get to the business person that has responsibility for that type of decision, it's not a hard sell.
MaximMakes sense. Um I have been thinking about a lot is I I mean, obviously, like getting in front of getting getting in front of the economic buyers, having a conversation, uh, demonstrating the value, that's clearly it makes it makes total sense. Uh, you're building a solution. Now, the one challenge I have with this model is it's predicated upon a single party, or maybe like a lot of those organizations would have uh some form of an innovation function and they kind of centralize the innovate in the innovational transformation thinking. Um what I've seen work really well is but it's predicated upon first building the foundation, having that central function, and then kind of federating across this. Like once you move from a centric model to a federated model where you put in the the know-how, the technology, the tools, like the um in the hands of the operators, and then uh at least my in my experience, then at that point it started to spread like wildfire because people now can model build things on their own, and that's not to say that they do they're doing it without guardrails or um they just they're testing hypothesis continuously. Oh, can I try this? Can I try this? Can try this, can try this. And I find that that's that that at least from my experience, that's the inflection point that they see, like where they move from like, oh, I'm gonna build one model, and yes, that's gonna drive value for me. No, no question that what you're proposing would drive a lot of value for them. But how do you get this from like I don't know, 10x to a thousand X?
SPEAKER_03Well, it's one of the interesting challenges, right? And I think the state of the technology right now is such that we can get people up to speed on building these solutions using this platform pretty quickly. Yeah, um now we we're not yet really offering that to customers, but that is the next step. One of the things we're doing is in the next phase of RD on our side is really understanding where the bottlenecks have been over the these first set of projects that we've been doing, and what do we need to grind down on in terms of really automating more of that and so on? Uh so there's a few areas there. So, and I think once we've done that, it'll make our costs lower, so therefore we can make it cheaper for customers, etc. But also, I think it'll be a more recurring offering to a customer. There's another aspect to it that actually we've been talking to one of our existing customers, uh, Great Western Railway, about where, and it's interesting you mentioned hypothesis, right? Because one of the big things with causal modeling is you it's a more scientific approach to solving these kind of problems. And one of the things that they want to do is have their line managers be able to set a hypothesis and test it using the platform. Um, so we're trying to figure out how we industrialize that, I suppose, right? Because you know, calls are modeling at the high level of hey, you know, these variables change, that one changes, okay. A business person, business analyst can certainly do that. Once you get into the detail of the math, it becomes more data science-like, right? You need more training to do that right. Um, so we're trying to figure out how to make that more recurring and and more automatable. Um, so that that is one of the key challenges, actually, that we're looking at. You know, how do you put this whole platform in the hands of business analysts as opposed to our forward deployed engineers and make it more flexible like that? We're not quite there yet. Uh, gotta be honest with you, but it's something that's definitely something I I'm putting quite a bit of thought into as we go forwards. Um, kind of everything. It's not uh, you know, vibe coding can be put in everyone's hands, but it doesn't really work in any kind of recurring way. It's gonna be really interesting on our side as we build these knowledge graphs for customers and they start to become wider and more have more knowledge in them about the company. Does that enable us to put more power in the hands of those kind of line managers and business analysts to do it themselves more? Um interesting question that I don't have the full answer to yet, but we're definitely exploring it.
MaximYeah, for sure. Um did the Garten study offer any kind of insights as to why companies fail to realize the the benefits and value of AI? Um and I'm just kind of curious.
SPEAKER_03Yeah, I mean, a lot of it is the actual penetration of AI into the organizations is is still at the co-pilot level in a lot of cases, right? Um, and I think it's it's just a fundamental issue of vibe coding. Once you take vibe coding into the enterprise, it's great at our level, right? You can create some awesome stuff, you know, very quickly. Is it scalable? Does it is it reliable? Is it does it have any kind of governance, security, etc.? Well, probably not. Um, so it's simply not gonna work at any kind of enterprise scale, right? Um, and we're a long way from from making that work. Um, so I just think what's being offered to the enterprise at the moment isn't by other people, not generals, um but it just isn't fit for purpose, right? It's not good enough. Um so yeah, it's understandable that they're gonna have pockets of success at best, and the penetration is is still very low. Um you know, which obviously creates a great opportunity for us because you know, I I I feel like and and you know, in conversations with Gartner analysts, right? They're confirming this. Wow, you guys are putting all the pieces together uh in the right way. This is really unique and compelling, and you know, as you go forwards and get more evidence of this and more referenceability and so on, this is gonna be very valuable and very, you know, very breakthrough. Um which is fantastic for me as a founder to hear that, right? Um, so yeah, I I feel like that landscape is is perfect for where Geminos is at right now. And it's that also gets me out of bed in the morning, that excitement, right? To go and and talk to customers about it and prospects about it and uh solve some problems for them.
MaximI mean, when it comes to big enterprise, probably the the key operative worth is trust. Um for them, it's more about the protecting the the risk of the downside than realizing the risk from the upside. And so um trust becomes really important. I'm going to if I'm going to bring a tool, I need to know that it's going to work and work within my um established tolerance limits. Anything outside of that, I'm not willing to tolerate. I I mean I'm looking at like companies that we're working with, and even like co-pilot co-work is not enabled, so it just co-pilot chat is enabled to you like, but why? Like it follows your IT directory settings, like it it follows the persona you give like why not co-work?
SPEAKER_03Um but you know, like a lot of these large organizations have the issue of friction is built up in the organization because of that problem, right? That they don't trust everything that comes through the door. So over time, bureaucracy grows and and people get put in positions of gatekeeping and a position of power like that. So they block a lot of things that could add an awful lot of value to the uh the business. So in situations like that, we qualify out relatively quickly, quite honestly, because there's so much opportunity out there, so many different markets we can go to, so many different customers we can go to. Like, like if you're gonna put that much friction in the way, then we can't get there. And we actually signed a uh second biggest contract of my career, which is quite a decent one, um, in the food industry just a few days ago. And we nice to one of the competitors. I'll I'll they'll remain nameless. But and we talked to one of the competitors six months before, we'd gone quite a long way, we'd done a sample app, and they were just putting too many barriers in the way to actually getting the deal done. So we said, okay, you know, it's not for us, we can't work with you, we'll go elsewhere. Thank you very much. And yeah, I saw the company, I think it's a four-month sales cycle, you know, for a pretty large enterprise deal, multiple use cases, a lot of long-term potential. Um, you know, it's that's the kind of organization that that is so much easier for us to work with as a startup, right? For sure. People who see the challenge look at it, but and then make a decision and get on with it. Um don't put a lot of gates in the way that are unnecessary. Do all the diligence and everything, don't get me wrong. It's been very thorough, it's been great to work with, and then they did it and signed it and got on with it, you know, and it's it's refreshing.
MaximYeah. So I I I just I just wanted to get a little more clarity on this. Where do you think the greatest amount of friction comes from? Is it that bureaucracy, the inertia, the organizational culture, leadership, fear of changing how things are done? Like like what is what is your sense as to where the friction, the resistance comes from?
SPEAKER_03You know, it's different in different places, but uh, you know, some areas you even see unions getting involved and scared of what AI is going to do to jobs, so there's some friction there that slows things down. Some of it is, you know, technology groups that think they want to do it themselves, they're excited to do AI. Yeah. Um, you know, the reality is it's not their day job, day in, day out, to do this. It is ours. Um, so the quality and and the features we can bring to bear are let's just say a little beyond um what what they're capable of doing. Um it's not just a matter of plugging together vibe coding around some open source here, right? This is this is visionary stuff, I like to think. And uh, you know, that day-to-day driving of that roadmap forwards is is a big deal. Uh, and no internal IT group is ever going to match that. Um, my humble opinion. So um that, you know, uh, and then there's just the regular legal compliance uh procurement stuff that almost no matter what you do is gonna take two or three months, right? Um, and it just adds to uh the sales cycle. So, you know, on the business side and even you know the technology gatekeeping side, we can usually get through it in a few weeks. Um, because we've got a pretty compelling technical story, and and it's enterprise grade, you know, security, etc. They pass us, uh, you know, they do the checks, they pass us within days because we've built this in the right way. Um, best practices throughout. Um, so those don't usually take too long unless someone's just it's gonna be difficult, in which case we kind of walk away pretty quickly. Um, but yeah, procurement and contracting always takes a while.
MaximBut I mean, this is um this is a really important aspect of business that that is especially big companies, because the bigger the company, the more rigor is applied to uh procurement decision or third or managing third-party risk. So, how do big companies get to a point of being able to say yes to a pilot or contract match faster and squeeze the the evaluation time from 90 days to maybe like 90 minutes? Is it like them continuously building like this view on a particular third party, being able to run it through this? What's your perspective? Because I feel like um you only score if you if you take a shot and go. If you don't, um how do you know? I mean, I feel like you're leaving a lot on the table.
SPEAKER_03Yeah, so one of the things it's generally is easier to get a proof of value, proof of concept, whatever you want to call it, through, right? Because it's a limited time, it's usually pretty low cost, especially given the tools we're using, and and that's another aspect of all this, right? The business model is also changing under our feet because our costs are changing under our feet. So, where do you pitch this? Um, but it gives me the luxury of having a conversation with a customer saying, look, what are your levels here? You want to do this, I want to do it for you. So let's work together to figure out a deal that at least we can get some proof points. Because once you've got the proof points, everything else gets a lot easier, right? Um, and especially given that you know the beautiful thing here is people become champions for us really quickly. So, because they're the ones that are proving value from AI when no one else in our organization or the industry is doing that. That's great for their career, right? Great for their ego, everything else. So, you know, and and that is that's gold when you you're selling, right? Um, because you've got that internal champion, and it's not that they're you know giving you information that they shouldn't be giving you, they're just saying, yeah, you know, here's what I can make work on my side to get to get to that proof point. And then once we're at that proof point, it's not only me that's your champion, it's the board because they're gonna love this, right? They're gonna be turning around and going to procurement. What do you mean you do you need to put this out to tender and stuff? These guys are delivering value when no one else has. Get on with it, to them. Yeah, we're actually seeing that in in a couple of cases, you know, where they're going, no, stop it. You know, you you're just putting friction in the way. We've we're seeing value from this, we need more of it. Let's get on with it, you know. And yeah, and again, that comes down to the kind of organizations that you you want to work with, right? And and from a startup point of view, at least at this stage. It's related to Jeffrey Moore's kind of crossing the chasm, right? And uh, and those kind of ideas, but it's more on the business side, it's not just the adoption of a product and the whole product solution and all that. It's is the business do they have the urgency and the vision to actually go for this, right? And and are they willing to open the door to let you prove it to them? That's constantly in my mind, right? When I'm you know, when the team is qualifying an account, what questions are we asking and what kind of answers are we seeing that indicate that that's their pattern of behavior, as opposed to, oh, you know, we're gonna do a three-month security review, and then we're gonna and the contract has to be on our paper and it has to be this, and that you know, yeah. Yeah, yeah, you guys have just built friction into your organization to the extent that you you're the opposite of of uh an innovative company, and and that's a big reason why I'm going back to why it's that 13, right? Yeah, the others just can't even get their act together to even try it, which is scared or too much friction, right? And that's it is what it is, and they're big companies for a reason, right? Um, whether they will stay big companies for too long with that attitude is another matter, but you know, we'll see.
MaximBut it seems that it seems like the bigger the company, at least I I this is my hypothesis. I think some of it is supported by science, but the bigger the company, the more that growth comes from acquisition rather than organically, and and so um there is this inherent barrier uh in taking big big risks because they may not pay off. And what the market rewards, especially big companies, typically they're publicly traded, the market rewards consistency. They don't want that volatility in in earnings, and so that forces companies to behave in such a certain way where steady eddy wins the race uh rather than like I'm gonna take big shots and go away. Some of them are gonna pay off and some of them are not, but the ones that pay off, it's kind of like the power of distribution law where it's they're gonna pay off like 100x.
SPEAKER_03But that's the problem, isn't it? You know, you get stuck on that quarterly. Oh my god, I've got to set the expectations, I've got to meet those expectations. And what a lot of these companies are missing then is well, next year or two years out, well, probably less than that now, because it's getting shorter and shorter, someone else is taking advantage of this technology, and their growth rate is going to be dramatically faster than you. 100%. And you know, meeting your expectations and so on is no longer going to be good enough. Um, it it's just uh, like we said, but it dig in the record, right? It's a fascinating time to be in business, and yeah, especially on the startup side of it and on the AI deployment side of it. So much is changing. Every aspect of the business model that I'm deploying is changing. Um, and how far do we go with that? And and where does it lead us? It's it's gonna be amazing. It's it's gonna be incredible. It's a couple of years ahead of us, isn't it? Yeah. Yeah.
MaximI mean, I um I love one what one of the big companies I really like in terms of what they're doing. I think it's really special is Salesforce, and I think that what Mark Benyov is doing on this is is phenomenal. Um, I mean, obviously, um amazing product, it's a genetic focus. Um, the acquisition of Slack in in serving is the layer in the communication layer. Like, I I I love this, but the the one thing that I find really interesting is this kind of triple strategy of like, yeah, we're gonna grow organically, yeah, we're gonna acquire so acquisitive growth and three. We're gonna invest like like maniacal uh corporate VC, we're gonna invest in companies and the ones that fit synergistically with what we're doing. Well, those become the acquisition targets. I just I just find this interesting, but I rarely see this in practice. I I obviously we deal with a lot of corporate VCs, but they're not the norm, and it is proliferate. That's not to say that it's not a corporate VC, there's a ton of them, it's just that it's not the norm.
SPEAKER_03Well, and you know what I've found is that I've done a lot of corporate VC uh over the last 20 years. Um the trouble is you know that they tend to become a customer as well, which is great, right? In the early days of that corporate startup VC relationship, it can be awesome because it can get you into customers that you otherwise would really struggle to do. I agree, but then you know, the the VC at that corporate, who's not necessarily a traditional VC, right? I was gonna say real VC, that's a bit unfair, but they're different and they're driven by different incentives on their side. And once you've got your product in there and it's being used at scale, they tend to go quite risk-averse on you because it's more important for them then to have you servicing them as a customer, yeah, than it is growing in the market more generally, right? So they end up with a bit of a conflict of interest, in my my view, um, that can be quite difficult to work around, especially if they're on your board. If they're on your board and dictating a strategy in a way that is really just oriented around them as a customer, you know, a market of one isn't gonna work for you. Um and I've seen that over and over again, and it's you know, it can be the death of uh far too many startups, unfortunately. Um I'm saying that with the benefit of hindsight because we did a lot of corporate VC at the incubator and highlighting us quite a bit, but um yeah, you know, it can work, but it's it's channel.
MaximI want to come back to Geminos. Um you you your approach in Geminis really it I mean, we talk about it, it combines the LLMs, the agents, the cause of AI, the enterprise technology graphs, the business. through like walk me through uh and walk the audience through as to why all those pieces need to work together why can't you just rely on llm i mean it it if lm produces convincing results even if they if they're if if the underlying reason it may be flawed so it's about the scale it's about the accuracy about the consistency of it the traceability behind it a lot of different waxes and it's not about the first application or two it's about the tenth or the hundredth in an organization so if you vibecode and use llms and it's so if LLMs are centric to everything you do with agents and so on you can't really do any of that that I've just listed right uh consistently you you can pull it off maybe with a pretty comprehensive harness around it but you know it it's hard and it's not something every you know certainly amateur developer let's face it a lot of people doing vibe coding in that way are are not trained developers um let's just say it's the kind of thing that you know don't do this at home kind of thing um certainly for the enterprise at home it's yeah I'm mixing metaphor's there anyway um but yeah it's just not a a solid platform for real widespread use and what we're seeing is because we can show value on the first use case we really quickly and then get demand from the rest of the business for more use cases well if we're not getting the foundations right that's really hard for us to deliver right so I don't want I don't want to be in that position either of you know saying to the organization yeah yeah we can do a hundred use cases for you and then failing miserably right that doesn't help anybody so it doesn't help me so we've put a huge amount of thought into getting those foundations right with the knowledge draft with the rules base with using causal where relevant and then using LLMs and agents around that it's um you know it to use some technical terms here it's a form of neurosymbolic AI so it's the combining the symbolic AI the causal and the rules engines and so on with the neural LLMs uh which I think is the ultimately the right way forward LLMs alone you know they're not gonna get us to AGI in any meaningful way um amazing technology that can do an awful lot there's an awful lot more to AI than LLMs and we we need to relearn some of these things and bring them to bear to solve problems you know and and to meet customers' needs uh LLMs alone don't do that completely agree with you um so with regards to this um I I mean ultimately what we're trying to uh increase is the level of trust the level of certainty the level of precision so if if I'm a CPA of a background so if we're to take this approach from a governance and assurance perspective in financial reporting we don't promise absolute certainty like um uh audit opinion provides reasonable assurance right doesn't provide absolute assurance so we design controls we collect evidence and to provide this reasonable assurance that the information is provided if that the information is reliable should we be thinking about AI systems in a similar way or do we have a sense of expectation do we have an expectation that we could get to an absolute certainty because it's reading data now if the data is structured versus unstructured versus neural like kind of like what did you think?
SPEAKER_03Yeah this is a really interesting area isn't it because when I sit in front of a computer and I use a spreadsheet as long as there are macros that I actually understand or myself etc um I'm relying on that to be a pretty deterministic system right yeah so yeah as long as the code is valid and etc it's gonna give me the result there yeah I'm gonna get a consistent result that's simply as you know not the case with LMs right they'll give you a slightly different result every time almost it's like you know um depending on on the path through the matrices so it it's a fundamentally different beast um you know it's probabilistic not deterministic now in most cases that's actually okay because the world is probabilistic and and not deterministic in most things right so when we're making decisions expecting perfection isn't gonna happen right let's just not let's be realistic about this and the best human decision maker does not get it right every time now that's not an excuse for saying oh okay then we can you know just use LLMs and it's fine it's not because they they get get it wrong in unpredictable ways and they can get it wrong and be very confident right and also one step in a long agent thread that gets it wrong means it's entirely wrong. If you go down and go down some very bad paths. So you know so what we're we're doing here is getting the balance right we're putting the framework of rules and causal AI etc around the LLM not using LM for the primary decision to get to a point where we can help human operators make better decisions overall across a team on a day-to-day basis consistently and we can tell them when we're unsure and give them a pretty good good idea of okay there's a bit of data missing here or there are two causes here you know in the causal model that you know one it might be 60 70% for one and 30% for the other you've got to think about that right yeah um and training people and getting to understand that and giving them the information and the ability to ask questions using natural language which is great right so LLMs are plugged in with agents and in their workflow they've got a you know some information in front of them which says 7030 why let me ask about that natural language questions about it and not you're not just stuck with whatever information is in uh in front of you um and users are finding that really powerful they can query they can understand the probabilities better where there's uncertainty you know um and and where there's missing information that they need to go fill in um so that's really you know what this is all about right it's about human in the loop still the human making the decision but giving them all the information that they need in order to make that decision much faster and on the whole more accurately than they've been capable of doing before and if we achieve that then we've got something of real value but we're not pretending it's perfect every plan.
MaximSo Stuart speaking of making the making the decisions so and and you're talking about use uh having a forward deployed engineering model that's there to support the client so I'm assuming that when you go and start working with client you have a multitude of opportunities that you're looking at and deciding upon so how do you decide or how do you help the company decide which opportunity is merely interesting from the one that's going to drive the most value and how do companies or how do you help companies define what is truly value?
SPEAKER_03So it's obviously a fascinating conversation that we uh you know love to get into every time and it is different almost each time and it's not necessarily about driving the most value in the first use case what we're looking to do is choose one mutually that gets us to value quickly. Okay. Right? Because that is that's the initial goal keep show value fast yeah a sensible cost right yeah everything changes in terms of the sales cycle and then we can tackle some of the more you know high value uh projects I I actually just did a blog post on this I'm not sure if it's on the website yet okay Jeffrey Moore has a uh he talks about zones for a company and it's things like you know the productivity zone the innovation zone etc and we use that as a bit of a framework for thinking about different use cases um and in general I would say what we're looking for initially is things in the productivity zone things where a big company makes a decision very consistently every day and moving the needle on that decision is going to drive some value quite quickly right yeah and often it's it's a nice sweet spot for us where there's a lot of text involved with some structured data because that combination has been traditionally really hard to automate and and use you know a software application to solve right at any kind of scale.
MaximSo the fact that we can do that now so the the great Western Railway example of delay attribution for trains right a lot of text Slack messages yeah emails phone call transcripts a lot of rules about what happens you have to understand the the train network the railway network uh understand what's happening with drivers etc um you know it's 15 different sources of data um so an individual trying to figure out then whose fault that delay was and who should pay for it ultimately it was taking them eight to ten days yeah um we got that down to a few minutes and and it was you know a couple of months of uh of development work for us to get it to production level so that that's a dramatic impact is it their highest value use case not necessarily but it's a nice one that generates you know tens of millions a year um and and makes the job of the person doing delay attribution much nicer frankly they're not dealing with a lot of tedium of looking through lots of data and trying to piece it together they're presented with it's 65% this one 20 this one 10 this one here's something else to you know a missing piece of data that will help us move that needle if you want and make it more certain go call Bill in you know the station at Reading or whatever and get this bit of information for us and we'll add that in and and redo it or it's 90% and you know you're pretty confident in it is what here's why and here's a complete report to send to the other party that needs to pay for this you know and give them all the the reasons why um I mean what's interesting about the the example that you're providing Stewart is I mean obviously going from eight days to eight minutes it's it it's a massive gain of like I don't know I haven't calculated but it's probably a hundred X and so but what's neat about this is that it's just the start of things so you start with okay well let's go do some root cause analysis around delay attribution and so for each one we have specificity of what caused the delay but then you can take this information and pipe it into it's like okay well okay if if if if whatever the root cause was for the delay let's go and fix it fix it fix it and just kind of start this like virtuous yeah exactly yeah well and the other one that we're talking to uh another rail company about is on the announcement side okay so a train's delayed right and they've got a bunch of stations and and instead of you know the announcer just saying sorry trains delayed what if we could actually say if you want to go to London go to platform three take the train to Sheffield or whatever and you know it'll take you slightly longer but you'll get there roughly this time yeah you know and so we're actually going forwards now and and saying okay great if there's a delay what's the best path around that not just for the rail company but for passengers you know what should they do um rather than you know because you know what happens now right they go to the whoever's standing on the station and they go how do I get to London from here if that train's delayed three hours what's the best way uh let's look at the timetable let's do yeah yeah so it absolutely it spreads right it's um it's a viral effect across the business yeah but it's also a viral effect across the industry um because of that champion side of it right so you know the guy at Great Western Railways has been a fantastic champion reference for us he's very well known in the industry now as one of the leading thinkers on AI um and he's spreading that word to all the other rail companies so great for us right yeah land and expand in multiple dimensions awesome 100% um I know we're coming at time uh just one last question for me what is one widely held belief about ai and entrepreneurship that you think is fundamentally wrong boy that's a that's a thoughtful one isn't it um well I mean beyond just the the normal you know LLMs are everything which I think an awful lot of people are falling for um and you know we're seeing Delaware and house uh allowed to have agent companies ai companies with no people responsible for the Manstand which is crazy right so that kind of extreme for me uh and you know exemplified by things like Block uh Jack company where okay the his company roadmap is now completely delegated to agents as I understand it so a customer says they want a feature the agent goes and builds it and puts into the product that to me is the antithesis of of what a startup should be about right and it it's like yeah playing Christians and uh sustaining engineering versus uh innovation you know disruptive engineering let's just do sustaining engineering how about no right so when we're talking about that kind of level of things you know it's like no we don't do that it takes just because you can doesn't mean it should yeah exactly right and I think that's that's true of AI right across the board right that just because we can do it uh no and I think ultimately that goes to you know AI consciousness and AGI and everything else to anthropic and open ai racing to right to justify their trillions in value why do you need that why is that necessary to get value from this technology you know and given all the dangers of it why the hell are we allowing them to do that you know so maybe that's not quite on point with the question but that's what what are the things at the top of mind for me right now. No I really appreciate you this has been a fascinating conversation um thank you so much for joining me on Scaling with Clarity and sharing your experience in perspective it clearly demonstrated you have a ton of knowledge and experience and and truly can help companies in in arrive at better decisions faster in a more deterministic way rather than what LLM can produce so for everyone listening can learn more about Stuart and his work at Geminos.ai we'll drop links to to Stuart and and where to find him um until next time keep building keep learning and keep scaling in with clarity thanks Stuart thanks Mike Sim it's been a real pleasure yeah I've enjoyed it