How Companies Are Losing Millions While Being Data Rich with Ron Nachum
In this episode of Future Finance, Paul Barnhurst and Glenn Hopper sit down with Ron Nachum, Founder and CEO of Sapien, to discuss how AI agents are transforming financial operations and decision-making for companies. Ron shares how Sapien leverages AI to unify siloed financial data, automate workflows, and provide actionable insights, helping companies unlock millions of dollars in hidden value while enabling employees to focus on strategic work.
Ron Nachum is the founder and CEO of Sapien, an AI-native platform that deploys agents to understand and act on messy, siloed data across ERPs, data warehouses, CRMs, and spreadsheets. Ron studied at Harvard, where he focused on computer science, statistics, and applied AI research. He has spent years building AI solutions for finance and operational processes, creating systems that help companies make better, faster decisions and optimize their operations.
In this episode, you will discover:
AI can unlock value from messy, siloed financial data
Sapien’s platform automates reporting, forecasting, and operational decisions
Human oversight and governance remain crucial for AI configurability
Talent density and culture are key to scaling a young, fast-growing company
Early entrepreneurial mindset shapes long-term innovation
Ron Nachum demonstrates how AI can revolutionize financial operations by turning siloed, messy data into actionable insights. Sapien’s platform empowers companies to automate reporting, optimize decisions, and free employees to focus on high-value work. Ron emphasizes that combining AI with governance, configurability, and a talented team creates systems that not only deliver immediate value but also scale strategically.
Follow Ron:
Website: https://sapien.ai/news
LinkedIn: https://www.linkedin.com/in/ron-nachum/
Follow Glenn:
LinkedIn: https://www.linkedin.com/in/gbhopperiii
Follow Paul:
LinkedIn: https://www.linkedin.com/in/thefpandaguy
Follow QFlow.AI:
Website - https://bit.ly/4i1Ekjg Future Finance is sponsored by QFlow.ai, the strategic finance platform solving the toughest part of planning and analysis: B2B revenue. Align sales, marketing, and finance, speed up decision-making, and lock in accountability with QFlow.ai. Stay tuned for a deeper understanding of how AI is shaping the future of finance and what it means for businesses and individuals alike.
In Today’s Episode:
[00:00] – Trailer
[03:15] – Data-Rich, Analysis-Poor Challenge
[06:21] – Harvard & the Leap to Sapien
[11:32] – AI Agents in Finance
[17:01] – Balancing AI Flexibility & Guardrails
[23:19] – Efficient & Secure Data Handling
[26:34] – Making Insights Accessible to All Teams
[30:45] – Configurability, Forecasting & Learning
[38:22] – Real-World Impact & Optimizations
[40:25] – Leading Young Teams with Experienced Advisor
[46:11] – Early Entrepreneurial Ventures
[49:13] – Closing Thoughts & Thanks
Full Show Transcript:
Host: Paul Barnhurst (00:00):
Welcome to the Future Finance Show where we talk about treasury management in our future. Finance is brought to you by Q flow.ai, the strategic finance platform, solving the toughest part of planning and analysis, B2B revenue, align sales, marketing and finance seamlessly speed up decision-making, and lock in accountability with Q flow.ai.
Co-Host: Glenn Hopper (00:41):
Welcome to Future Finance. I am Glenn Hopper, co-host along with my esteemed colleague, Mr. Paul Barnhurst. Paul, how are you doing?
Host: Paul Barnhurst (00:50):
Doing good. Always excited to be here. How are you doing, Glenn? I'm
Co-Host: Glenn Hopper (00:53):
Good except I mentioned before we came on, I'm wearing a sports coat and a t-shirt today I feel like Crockett from Miami Vice. It's a black t-shirt. So for those who are just listening, it's a black t-shirt, so maybe Crockett headed to a funeral or something. I don't know.
Host: Paul Barnhurst (01:07):
In our lives we could pull the audience and see how many people even know who Crockett is or record. That's
Co-Host: Glenn Hopper (01:11):
True. I'm dating myself here by referencing an eighties television show that
Host: Paul Barnhurst (01:15):
Hey can break it to you, Glenn, but you and I are getting old.
Co-Host: Glenn Hopper (01:17):
Yeah,
Host: Paul Barnhurst (01:18):
I mean we're both the other side of 50 now.
Co-Host: Glenn Hopper (01:20):
Our next guest is not getting old. He's young and vibrant and everything that we've remembered from all those decades ago.
Guest: Ron Nachum (01:28):
I wish I knew who Crockett was.
Host: Paul Barnhurst (01:30):
See, I told you. Welcome on the show Ron. We're really excited to have you here with us. Yeah,
Guest: Ron Nachum (01:34):
I appreciate you having me here. Excited to dig in.
Host: Paul Barnhurst (01:36):
Yeah, we are as well. So I'll give a little bit of background about Ron. So Ron Nachum spent years in applied AI research before founding Sapien. Sapien is an AI native system, deploying agents that understand siloed messy data to run, optimize and act on company finances end to end, it sits on top of your systems of record, so ERPs, data warehouses, CRMs, spreadsheets, et cetera. Ron studied, if I remember right, was it Harvard or Wharton?
Guest: Ron Nachum (02:03):
Harvard.
Host: Paul Barnhurst (02:04):
Harvard studied at Harvard. He's worked on several AI research projects and now he's scaling his company, which is powered by its company engine and tabular reasoning model and we're really excited to get the opportunity to chat with you today. So again, welcome.
Guest: Ron Nachum (02:20):
Yeah, appreciate you having me on. I mean, great. I couldn't have said it better myself in the introduction.
Host: Paul Barnhurst (02:24):
Perfect. Alright.
Co-Host: Glenn Hopper (02:25):
You probably would've remembered that it wasn't Orden though.
Host: Paul Barnhurst (02:29):
Yeah, he would have, what can I say? Those are all out of my league. I'm not like you Glen, which one did you graduate from again?
Co-Host: Glenn Hopper (02:39):
I went to Harvard on a budget.
Host: Paul Barnhurst (02:42):
See, here's where I graduated from for grad school, A SU, also known as party school. So there you go. That sums it up. All my undergrad was BYU, which is a non-party school. So go figure. So Ron, you and I have had the opportunity to chat a couple times already before the show and something you mentioned. I want to kind of dig into it. When we chatted you talked about so many companies that are data rich but analysis poor. Why do you think that is? I mean obviously some of it's messy data, but we just love your thoughts on what you're seeing and why that's such a struggle for so many companies.
Guest: Ron Nachum (03:15):
Many years it's been true, but I think in 2026 we feel this gap more than ever. I think there's a lot of reasons why companies are data rich, analysis poor, but part of it is every company has had it kind of a little bit bashed into their head. They need data, they need big data, they need information, they need to be tracking as much as possible and a lot of companies have actually been doing this very well. You look at even though we work with lower middle market manufacturing clients that are generally not the most technically sophisticated, even they're tracking a lot of this information. What ends up happening though is companies are data rich but it's split between a bunch of places because they started tracking data in the nineties and then they acquired another company and now it's in a different system. They acquired another company and now there's different pieces all over the place.
(03:58):
Not to mention the fact that the size of data that we then start talking about is tens of millions, hundreds of millions, billions of rows. The type of stuff that breaks excel if you even try to think about opening it. And so what we end up seeing is companies have a lot of information but they're not acting on it. And actually one of the first conversations I had when we started Sapien was with a former Fortune 500 CFO and he told me I'm flying blind. He was like, every single time I want to make a decision, I asked my analyst for data, it takes them a week. I made the decision three days ago on where to spend the money and it's because large amounts of data, very, very siloed, way bigger than what humans were meant to work with. Our human brains were not built to work with hundreds of millions of rows of data that doesn't agree with one another.
(04:39):
This is where AI automation, all these things should be enabling us, enabling people to do the work that matters. But I think we see it oftentimes to answer succinctly siloed information, way too much information. People aren't built to work with it. And what that means is usually we just skip it entirely. We're not doing any of the analysis or if we are, it takes three weeks to answer a question. So we're only picking a couple of questions to ask instead of asking every little thing that might move the business forward, we have to be choosy as a result because it's all a resource allocation problem at the end of the day. So I think that's a lot of what we saw. It's actually a lot of what inspired us to really start sapien. It's a lot of what we keep seeing more and more. Everything is there, it's just how do you get the value out of it. We almost like to say companies have tens of millions dollars locked away in their ERPs and data warehouses just about Can you find the way to almost get it out of there?
Host: Paul Barnhurst (05:27):
Can you unlock it? Yeah,
Guest: Ron Nachum (05:28):
Right.
Co-Host: Glenn Hopper (05:29):
Alright, so my first question is really just an observation. I'm going to read you a list, bill Gates, mark Zuckerberg, Matt Damon, William Randolph Hearst, Robert Frost, you know where I'm going. And Buckminster Fuller, all famous Harvard folk who did not finish. And as I think about that list, I'm wondering arguably that's probably rocket fuel for starting to becoming a billionaire industrialist or at least being, but there had to be, parents were probably involved here, but it had to be a big decision point for you. What made you decide, I'm ready to go out into the world and do this thing right now and leave school with that path?
Guest: Ron Nachum (06:21):
I will say there's probably a long list of folks who also left Harvard and didn't do so well, so I don't think we should just
Co-Host: Glenn Hopper (06:27):
No, no, no. Those are the only ones.
Guest: Ron Nachum (06:30):
Survivorship bias here a little bit. I don't know, there's obviously a lot of others too. Jokes aside though, I spent my time at Harvard. I was studying computer science and statistics as well as a little bit of neuroscience. I was doing applied AI research. I met a lot of really smart people and the way that I oftentimes tried to do that is I was running my own things to just meet people. I started running my own AI paper reading group, I started a startup group. I was just like, how do you get smart people in a room in a way that's low touch, just bring people together. It doesn't need to be a super regimented club. I actually considered dropping out of Harvard to join a startup at one point and decided not to for a variety of reasons, but it kind of boiled down a little bit to the people. It was like who was it going to be working with? And that's actually what made this decision really easy for me. I started sapien with two of my best friends from high school. Pranav was over at Stanford, Ari was over at et Austin. They are two of the smartest people I've literally ever worked with. Pranav was one of the best infrastructure cybersecurity minds of our age group. He was hacking things since he was in middle school and got in a lot of trouble sometimes, but really did a lot of us
Host: Paul Barnhurst (07:30):
Any good stories on the hacking? No, I'm just kidding.
Guest: Ron Nachum (07:33):
Not for public disclosure.
Host: Paul Barnhurst (07:34):
I figured you would say that
Guest: Ron Nachum (07:35):
He would make me go and scrub it from the record here. So he was someone I knew extensively. And Aria also, he's awesome. He was a top a hundred golfer in the world growing up and then went into computer science somehow instead of golf. He ended up at a PhD research lab at UT Austin. He was their youngest student there. He was on track to get his PhD by like 22. So two of the smartest people I ever worked with. And to me it's about when you're building something you want to be building up the right people. And so it was clear we had the right talent density to at least get something off the ground and start building it. And then the other two pieces that kind of layered in afterwards is we met the folks over at Neo Ali Porto in particular who runs Neo, the VC firm and some of the other folks there as well.
(08:23):
And it was one of those moments where you realized the people aren't just the people in your company, it's the people you're going to be working with outside. And there was that moment when they first made us an offer to fund our pre-seed and kind of get the company off the ground. It was like these are people we want to be more like these are just people who are really excited about working with. So I was like, okay, have the right people to build this thing with. We then really started to nail down this space of look, financial data is such a big gap. We actually initially weren't certain exactly where we were going to take this, but it was so clear it's a humongous problem and so to me it was like, look, I'm working working with great people. We're going to work on a really hard problem that has high impact and frankly the world is moving so so fast right now.
(09:01):
The opportunity cost of not going and building something is so high, it made it a no-brainer decision to just go all in and do it. And now we're almost two years into the process from when we first started the company and I mean it's pretty awesome team of more than 20 people now growing quickly. We're actually moving down the street to a new office in New York. It was definitely a hard decision, at least for my parents. It was relatively easier. My cofounder has a little bit of a harder time, but I think when you boil it all down, I think life is being around really talented people and working on really hard problems and when we got our first customer, we started to really see real impact. It's one of those things that made it so obvious, why would we ever want to go back to school when you can be saving thousands of jobs, you can be generating tens of millions of dollars for these companies. You can be having a really big impact. But that's kind of how it all came together.
Co-Host: Glenn Hopper (09:47):
Yeah, that's huge and it sounds like I think you're spot on with when you have those connections and those people that you have an opportunity to work with at a time. This is 1995 all over again. Well probably 1995 on steroids, hopefully
Guest: Ron Nachum (10:05):
A better ending.
Co-Host: Glenn Hopper (10:06):
Yeah, that's true. Well I mean obviously we're in some kind of bubble around it, but also companies that started the Amazons that come out, so the best companies are going to shake out and by starting building when you did, you have more of a foothold to ride this wave. So yeah, it totally makes sense. I guess my second part, it's not even the second part of the question, it's a completely different question, but listeners to the show know that I've spent two years railing against everyone calling their chatbot with some different kind of wrapper on it and Paul knows where I'm going calling it an agent. And this year we are actually, there've been huge leaps in how long the conditional loop can go out and work without a human in the loop there. Tell me about when you first started building this, the idea of agents, how you were handling that, how much was left to the agent to kind of run on its own versus sort of an agentic workflow where you have deterministic steps in. And I'd love to hear your insights on how much better the large language models have gotten in the AI tools at going out and performing these long run truly agentic tasks.
Guest: Ron Nachum (11:32):
It's an amazing question. There's a lot that's changed here. I'd say candidly, our approach is very different than a lot of other companies in this space. There's been fp a tooling, there's been analytics tooling, there's been all these things for decades now. Our whole angle was one where we were building an AI research team that really cared about financial and operational problems rather than an fp, a platform that was adding in ai. And what that meant is from day one, we were building the system company. We called it the company representation. It's now called the company engine that's more user facing if you will, but it's this whole idea of why was this problem hard? Why did we have planning softwares that took nine months to migrate into why were we even in this place in the first place? It's because these systems didn't understand the business they were working with.
(12:19):
And this will get to your question in a second, but it's really about for every company, how do you build that underlying model of the business? And this isn't like a traditional Excel model, this is what are the parts of the company, how do they relate to one another? What matters to this business? How does all the data, all these different pieces, come together. So the whole idea when we first started it was just this piece. It was if we can understand a business well then we could build the most general company out there. We could work with a manufacturing company and a software company and a restaurant and a telecom company and healthcare business and they can all leverage this one platform. So that's actually where we started. We started with this foundation of understanding of business. What that led us to do initially is actually exactly what you mentioned.
(12:59):
It was just automating repeatable processes. The first workflows we did for businesses, frankly it wasn't even an agent yet. We were doing it manually in Excel in the background, just trying to figure out how to put this together. That was where we started and it turned into kind of like you mentioned these structured tool calls that went end to end. But the interesting thing about it is we were always building a system where it was extremely open and you added in constraints. And so what that meant is as language models got better and as technology has been improving, we just kind of loosen more of the little dials and the constraints around it such that you let this company engine do more and more and more of the work as you models get better. What this has led to is when we started the use case we were doing is like we were making waterfall charts for companies based on their GL data, but it was very methodical.
(13:49):
It was like there's only one way to get there. We then went to SPI and generating entire management reports end to end for companies still reporting, but much more in depth, a lot more thoughts there. And the immediate value is, well you're going from a monthly surface level management report to can you get a mid month, can you get a daily management report of the business that's going and breaking down to the customer level, to the skew level, all those levels of detail. Then where we've seen Sapien go as these models have gotten better is again loosening those restrictions. Now Sapien is actually going into things like pricing recommendations, inventory allocation, the actual, okay, we've gone from saving you time to a system that is saving our clients millions of dollars or generating millions of dollars where they're losing opportunities. And that's the big picture vision for Sapien because we've built the technology in this way.
(14:36):
We're not just building a chat bot, we're building this system of action, the system of data, understanding the system of frankly what matters to a business. Sapien is able to then go and get proactive. And so where we've seen the most value today is we have companies that feed in every single piece of their data data in Sapien, it's their ERP, their warehouse, their spreadsheets, their CRM, their HRIS, all of them are flowing into Sapien and Sapien is sitting there and it knows what matters to the business and it's saying, well I know you're trying to expand your profitability in these segments of the business. Here's actually what happened in the last 24 hours here and here's what you should do about it. And you're moving less and less of needing the human to guide every piece of it, but what ends up doing is now every person is way more valuable.
(15:15):
As we talked about at the beginning. Now your people are not sitting there doing that manual spreadsheet stitching. They've moved up and up and up and up and up the stack to now it's strategic decision making, executing on those decisions, going and making the actual changes in the business. And we've seen a massive shift both in how good models are, but also a lot of the work is outside of these language models because frankly, LLMs shouldn't be doing most of this work, right? They're not built to do math, they're not built to do repeatable calculations. So it's all about how do you augment them with the right pieces and I think we've kind of had the right timing where as LLMs are getting better, we can loosen up some of the pieces but also our own proprietary technology, like our tab of the reasoning model, which builds this understanding of every column in row and table, our calculation engine, which does all the math.
(15:58):
They all kind of ride this wave together where they're all getting better. So there's a lot of different pieces there, but I think it's been really interesting to see, we made this really big bet when we started that people do not just want a faster Excel or a better Excel. People want a system that helps 'em run their company better and ideally also you can export to Excel and keep some of the same ideas. That has definitely started to pay off as models have gotten better and better and better because this was not really even possible 18 months ago, but now we're seeing companies that are optimising their business straight on a platform like this one.
Co-Host: Glenn Hopper (16:31):
You already had the guardrails and the systems in place, so maybe, but I imagine like you said, as the technology gets better, yeah, it enhances what you've already built, but have you seen anything in the way that you're set up where you're able to turn over more to truly to let the LLM do the ENT work than you were just a few months ago? Or do you feel like we still need to keep these guardrails on so we're going to keep it locked down and on it, not let it just go rogue on us? Yeah,
Guest: Ron Nachum (17:01):
Totally. I mean the way I would break it down is we definitely have less guardrails on the LM than we used to in the past, and I think it's one of those things where sometimes it's to build stuff just to get rid of little bits and pieces as the technology is improving, but we try to think about what are the parts that are, we call them in variance, what are the parts of the product that we're building that no matter how good an LLM gets, you're going to need them. One example is auditability: every single number you need to know exactly how it's calculated all the way down to the source data, every assumption that went into it. And so we feel very comfortable spending time there. We feel very comfortable spending time on the data understanding layer and those sorts of pieces, one that we actually spend a lot of time on that has still proven to be really valuable is what we call financial intuitions.
(17:42):
But it's just like the system having a gut feeling for like, hey, when you're comparing periods that aren't apples to apples, how do you think about that when you're creating a table or a graph? What is the way that people just presented this information is something that you would think would not actually be necessary, but when you ask any LLM to go and build you a board deck, it's going to get all these little things wrong. They don't make a huge difference. There's also the bigger things going to get wrong, but all these little pieces have come together. So I'd say we've let the LMS be a lot more flexible, but we do see a lot of places where the work that we've done to build up these guardrails is still very, very valuable and companies do their 10 Q reporting through SBM, they do processes that we would've never imagined being done through the platform and that's only possible because you have these financial and operational guardrails that make it structured enough.
(18:30):
And I'd say that's actually the big weakness of OMS in general is they're almost too open. You can ask anything, they can give you anything. There's no governance, there's no control, there's no structure. Companies get a lot of unique value from Sapien because you're building a dashboard in one team and you can share it to the other team and they can go and drill in and get an understanding of it, but you still keep all the right structures in place. But we've definitely seen it get more and more open. I'd say especially over the last four or five months. There's definitely been a big shift with the last few models, but there's definitely still a very healthy tension between the two that our research team spends a lot of time thinking about.
Co-Host: Glenn Hopper (19:05):
I'm going to stop Paul, I could keep going but
Host: Paul Barnhurst (19:09):
Your face, I want to ask more. One thing when you said kind of the guardrails and they've got a lot better, but an LLM can kind of do everything. It made me think a little bit of what's been the, what's made Excel so incredibly popular but also has been the bane to many people is it's incredibly flexible, right? You can do anything in Excel, you can do anything with an LLM. There's a reason I like to joke and I think in some ways this is true with an LLMA little bit different, but Excel is the number two software for pretty much every category in the world,
Guest: Ron Nachum (19:44):
Right? Exactly
Host: Paul Barnhurst (19:45):
Right. It's not number one for anything, but it's always going to be cheap. And if you know enough about Excel, you can pretty much build it to be almost anything, at least at a small scale. You could do pretty much anything with an LLM, but does that mean it's really the best tool to use? And so I think there's some similarities there in what you said. So anyway, that just came to mind.
Guest: Ron Nachum (20:05):
There's one thing that actually I tell our team very often, which is I think in this day and age the best products are opinionated enough to give you immediate value but flexible enough to let you take it the rest of the way. And what that looks like at Sapien is we onboard companies really, really fast because agents do most of the work to go and understand the data. It's like multi-billion dollar companies get onboarded in two days and it's really powerful what this actually looks like. The first thing they get when they open the platform is not a empty chat box. It's Hey, sapiens already gone and it's calibrated on your business. It's thought about your company, it's researched your competitors, it understands your space, but it also structurally understands your data. And you know what? We already found three SKUs that are gross margin negative when we found these customers that you should be renegotiating with, that's the first piece of it.
(20:51):
So it already understands that this is thought about, that's the magic moment, but then everything is configurable. You can go and take it that extra mile and go and ask whatever question you want, but it's structured enough where it's going to still give you all the pieces of data that it took to get there, all the pieces together. But I think this is actually exactly what I find the issue with Excel, with LLMs, et cetera to be is are they putting the power in the hands of the user? It's tricky to tell There are multipliers, right? It's how good the person is that using this and then you can multiply them. I think the best pieces of AI technology are ones where anybody can get value out of them, but the power users can get even more. And I think that's a lot of what we think about and why these opinions matter a lot is can you build that piece of software?
(21:33):
We have non-finance users use the platform a lot, operations, commercials, sales, et cetera. They're all using the same data and it's a big boost for these folks to not have to go and ask their IT team every time they want to pull some data. But that means there's so much consideration for like, well, sapien can't just show you a 300 line SQL query and say, do you think this looks good or not? They have no idea, right? So there's so many things like that where it's that careful balance of do whatever you want with can you have enough of an opinion to not just be number two. I actually really like the way that you framed it. It's something we think about a lot here both on an engineering side but also on the sales and how do we enable customer side of things.
Host: Paul Barnhurst (22:12):
Ever feel like your go-to market teams and finance speak different languages? This misalignment is a breeding ground for failure in pairing the predictive power of forecasts and delaying decisions that drive efficient growth. It's not for lack of trying, but getting all the data in one place doesn't mean you've gotten everyone on the same page. Meet Q Flow, do ai, the strategic finance platform purpose-built to solve the toughest part of planning and analysis, B2B revenue QOO quickly integrates key data from your go-to-market stack and accounting platform then handles all the data prep and normalisation under the hood. It automatically assembles your go-to-market stats, make segmented scenario planning a breeze and closes the planning loop, create airtight alignment, improve decision latency, and ensure accountability across the team.
(23:19):
Appreciate that. One thing I wanted to bring up that I think is interesting, I think Glenn will find interesting. Now, you and I were chatting earlier with the agent tools. We've seen this with some other agent tools, but I know you specifically, you're not storing any of this data. So right now, right now it's not going into a data warehouse. You're storing kind of the metadata, some of the schema, maybe talk a little bit of why that thinking kind of benefit because I think that's so new to many people to think, okay, it understands all my data, but it's not storing it, right? That's not traditionally how it's worked.
Guest: Ron Nachum (23:51):
It's part of why the company's called sapien, right? It's like what's the human way of doing things? When you're doing analysis, you're not taking the entire Excel and putting in your brain and jumbling it around, you're looking at bits and pieces of it. When you're working with a data warehouse, you're not pulling every single piece of data warehouse, you're just pulling the pieces that you need. What this does is two really great things. One is again, it makes setup really easy. We don't have to go and do a big ETL transformation, a consulting project, these long ways of getting into a system. It's working with it the same way that humans do. And so what that means is when it's doing analysis, all it needs to know is what data do I have access to the names of the tables and the descriptions of the tables and we generate a lot of other pieces that make it CPM very effective at searching over this data.
(24:35):
But once it's searching over the data and then as you go and make a good query to pull in what it needs, there's two options. Either you go and pull in tens of millions, hundreds of millions of transactions or you make a system that's smart enough to know what do I need to actually answer this question well, and that is a huge shift in efficiency questions that used to take days to pull the data for if you just queried it right, you could solve those problems much faster. We see even today some of the finance teams we work with, they previously were asking their IT team to go pull six months of transaction data to go do an investigation and that might take the IT team a couple of weeks to get on their plate and in a few days to do it or whatever it might be, safety.
(25:15):
If you can go and do that full loop to straight to the source data, it's grabbing the right relevant source to do the analysis doing it, and then it's spitting it back out. And what that means is also it helps out with security. A lot of folks are very nervous about security broadly right now is AI training on my data is data going outside of my four walls? And there are still bits and pieces where obviously we need to work with the data to do the analysis, but it helps that sapien doesn't have to just store humongous copies of all of the information within companies. I think especially as we're seeing more and more sensitivity to data security, this has been a really big selling point for us. It's like, look, we can do it fast and we can do it much more securely than systems have been in the past.
(25:51):
You don't have to trust us as much as you might have if our system operated differently. And it also just yields better results. This whole method means that when there's data in NetSuite and Salesforce and Snowflake, SPN can go and quickly scan across all of them and see, oh, there's conflicting data between these two or there's potentially there's a revenue column here and a revenue column here and a revenue column here. Okay, I'm going to actually go pull all three of them and compare them instead of having to go and look at one table at a time. Which I mean also if we think about context windows, that's a big limiting factor for these AI systems in general. This helps avoid that problem entirely where you're just bringing in what you need and then the non LLM querying and calculation systems can do everything else that you need to do.
Co-Host: Glenn Hopper (26:34):
It sounds like you're trying to take away my day job, which is, believe it or not, I'm not a professional podcast host, but doing these, sorry
Host: Paul Barnhurst (26:43):
Gloria, you have two podcasts that put you have professional status.
Co-Host: Glenn Hopper (26:48):
Everything that you just talked about is right now if you don't have a piece of software like Sapien, you hire a consultant like me to come in and build an MCP server or some sort of connecting fabric so that your Snowflake data and your Salesforce data and your NetSuite data can talk to each other and be aggregated. And it's like the new gold rush that there was around building data lakes and data warehouses and all that back in the day. But seriously, the great equaliser of AI is you with a sort of foundation as a statistics guy will appreciate this, but we've all known, anyone who's been in the business world has understood conceptually what data science is and what machine learning is. But the barrier to entry is you have to be able, you have to write algorithms, you have to know Python and have the data science fundamentals down. But now when you can create all this with just natural language prompts, it really lowers the barrier. It also leads to people doing really stupid things because they don't have a statistics background and they don't know things like you literal earlier look of survivorship bias.
(28:00):
But to that end, and I think at a point with Sapien and something you mentioned earlier that all the best AI platforms are easily configurable. And I think there's a move right now to make Zapier easy. They were drag and drop and you had to sort have the process for, but now when you're setting up work in co-work for example, or there's other products out there that will sort of automate your workflows, and I think even in N eight N, you can go in kind of type what you want, it'll build sort of the skeleton of what you want to build. But you also, both you guys were talking about Excel is you can do all kinds of things with Excel. People know different levels of you come in and you're like, yeah, I can put in this column and then I can put what a means in the next column or whatever.
(28:56):
And then a few years later you're using Lambda functions and whatever anchor array and all the Excel skills that Paul knows way better than I do. But I mean, where are we right now in the world with yes, you want everybody to be able to do this? I keep thinking of AI in so many ways as giving individuals their own RPA. It's like now, okay, instead of having to have a big vendor come in and set all this up, everybody can kind of automate their own, but they can also get into trouble. So I'm wondering where, and maybe it's really on the engineer, on the software designers, you want to give them that flexibility, make it configurable, but also keep 'em out of trouble. Where's that line and what's your dream for how humans interact with Sapien and how they're building this and using it? Yeah, there. But
Host: Paul Barnhurst (29:51):
I feel deep. I told you.
Guest: Ron Nachum (29:53):
No, look, there's nothing better I'd like to do with my time than dig into these questions. I think about these all the time. So we'll take part one as how do you think about the extent of configurability and we'll talk about part two more as where does this then take us? I think this goes to a big reason why I think something like SAPIEN is so valuable. It's because the line for configurability is different for every use case, right? It's different for software engineers versus for finance teams versus for sales teams. It's fundamentally a different problem. In fact, even Sapien, one of the things of configurability is Sapien has a very, we actually didn't start at all thinking about forecasting, but we ended up building out an incredibly robust forecasting system. Why? Because Sapien had every piece of financial and operational data to build the best possible driver-based forecast that you could ever imagine and have AI agents go and reason about every line item and build out this forecast.
(30:45):
Now you could go ask an LLM to build you a forecast, but there's so many opinions that went into it like, oh, if you want to break down a row, how do you do it? If you want to extend the timeframe for this forecast, which models should it use? All these different questions. Think about when you tell an LLM build a forecast, there's literally 50,000 little decisions that have to get made to make that forecast go right? And that's the theme broadly across the platform. So the question is how do you solve this? And honestly, this is I think one of the hardest problems in AI is what's a good assumption versus a bad assumption. If I go and I type into sapien, what's my revenue? It's a good assumption that I'm talking about in my company, but it's maybe not a good assumption that I'm talking about 2024 or 2025 or 2026.
(31:27):
So how do you know which things you should just guess and which things you shouldn't just guess? A lot of it's a hard engineering and research problem. It depends on the context, it depends on the company. For example, if we work with a windshield manufacturer and we work with a paper manufacturer, which are two of our clients, if one of 'em asks about how should I think about our cost structure? Well, one of them cares about sand and one of them cares about wood and completely different ways. You'd have to think about that. So this all goes a little bit back to that. When it comes to configurability, a big piece within Sapien is continual learning. So as you use Sapien, it's building up a knowledge base, it's building up the understanding of the data, but the human is always within control. So as we work with enterprises at larger scale, there can be thousands of pieces of knowledge that Sapien is learning about the company, and you want to have some way to control and govern that, right?
(32:15):
You don't want any person to be able to go make changes, but we also don't want it to be a chore. You don't want someone to click and hit approve on every single piece of information. There's been a lot of work on how do you let the finance team iterate and make changes and let the operations team do their own thing separately and how do you let it all cascade up? I think this goes a bit to the finance intuition piece that I mentioned earlier. It's like when you ask Sina for a waterfall chart, it should know what a good waterfall chart looks like versus a bad waterfall chart. It should know when you're asking for the p and l, how do you actually break out the p and l for this company? This all comes from context. And so I think this configurability problem, it's a really, really hard one, but if you have the right context and if you have a healthy governance structure that actually lets you do a really healthy job of configurability because context makes sure that the configurability makes sense and governance makes sure that the configurability is controllable.
(33:07):
And once you have those two things and then goes to how we think about outputs, there's no such thing as a hundred percent accuracy. And this is always like the sentence that gets you really scared, but it's like, look, if you ask your analyst tomorrow, how do we compete with our biggest competitor in California? There's no answer to that question. There's no right answer. There are so many different ways to go about it. This is where verifiability matters a lot. And so we built the platform in a way where every number, every assumption, every calculation is traceable. And that makes it such that when you're doing these configurations, you can see where they're going wrong very easily and you can go and make those changes. So it's, there's so many pieces that go into it, but if you have context flexibility, governance and verifiability, we see that being a very healthy combination and all four of those from the lens of the finance and operational use case, it's very different than what people want for their coding agents.
(33:55):
For coding agents show me every line of code. That's great for sapien. We have users who have no idea what SQL even is using it, and we have people who have spent their last 10 years writing SQL queries. How do you make one system that works for all of those? It's hard. And actually even part of it is sapien can actually treat people differently. So if a C FFO is on the platform versus a head of fp and a versus a head of IT versus an analyst, they can actually tweak sapien to approach them in different ways. How deep should the analysis go? How technical should the analysis be? So it's also meeting users where they're at. I want to then jump to the second piece of the question, which is where do we go with this? This is really the part of SAP that I'm most excited about.
(34:33):
I think, again, this is where I think we're very different than other companies in space is we're obsessed with this idea of can AI run companies? Can it do all of the financial operational, gruelling analysis in the background and just like free up people to the work that we're meant to do? And that's different than, hey, we're building a system to do faster reporting, or we're building a system to answer your questions. We're building a system that needs to understand the company as well as any person does, and arguably bring in all the little bits and thesis from everyone. The long-term vision for recipient sits. It's these agents on top of your ERP, your data warehouse, your CRM, your spreadsheets, all these different systems, and it's just telling you what you should be thinking about all the time because any business knows there are 10,000 things you could pick from, but if you had a system that understood enough about your company, it was configurable enough to know what you care about and it could service up every morning, what are the five things you should dig into?
(35:25):
That's the most valuable thing to pretty much any company out there. Then now the next pieces can actually go and act on it. Can it go and help you? That's where again, maybe if you went in the loop, you don't want it to go and make changes to the business without having some control over it. But that's the future that we're excited about is you just explain to sapien what matters to you as a business. Sapien helps you figure it out and helps you get there and where it thinks you're thinking about the wrong thing, they can also disagree with you. I think that's one of the hardest things in AI also is it always just agrees with people, but if you can grout enough of these financial intuitions, enough of what matters to the company, it can be like, Hey, I know you're asking me to improve gross margin on this set of your skews, but your real problem is over here.
(36:02):
That's what you want the system to be able to do. And that only happens from all those pieces getting layered together. So that's a lot of what we think about and it's been very exciting as LLMs and as Sapien has gotten better to see it get closer and closer to this vision where Sapien really is sitting on top of, we're in public companies, we're sitting on top of tens of millions, hundreds of millions of transactions, like eight different systems in a way where people have never looked across these systems together before. They've never married the data in their on-prem data warehouse with their Salesforce. If they've never even connected the two together, now they can and they're suddenly realising we're losing money on half of our customers. And it's this realisation of like, wow, there's so much to do here. There's a lot of stuff there, but I think it's been a really exciting part of the journey certainly,
Co-Host: Glenn Hopper (36:49):
And I love to hear all that because there's sort of a hype debate around, and I do agree actually with Jan Lacoon around this that, oh, the LLMs will never get you to a GI for people in business who are using this, I don't need a GI. If you can have a system that can go across all these disparate data sources and find these correlations and actually have the context of my business to give me value, I mean, it's the same thing I say about working with Paul. I don't care if you're dumb as a brick, if you're a good cohost, oh wait, did I say that? I kid Paul. I kid,
Host: Paul Barnhurst (37:27):
What did I hear? Once? 70% of all truth is said in humour.
Guest: Ron Nachum (37:34):
Oh, I like to say we're solving the most obvious problem in the world and it's just about can we solve it in a unique way that nobody's done before? And that was what we, from day one when we were starting this, when we first pitched this to CFOs, it was like, what are you talking about? It was like, this is so farfetched. And so we paired it back a little bit and we went, look, we can automate any workflow in your financial and operational process. Tell us what you're thinking about right away. But it quickly came back to this whole vision of like, yeah, this is the most obvious problem in the world. Companies are losing money, companies are missing out on opportunities. It's because people don't have the time. One of our manufacturing clients, they're based, they have a plans in Tennessee where they now go and dig in to see, hey, there was a college football game last weekend.
(38:22):
Did our production drop off? That's a question that nobody would've asked before, but now they know, oh, people come in hungover the day after or the Monday after they skip work. Well, now we know about it, and now we know that we actually should staff a little bit more in the days after big college football games, which that flavour of question, people never would even tried to ask it because we've taken them weeks to dig into the data. But because it takes a couple minutes, the whole script gets flipped. Companies are just thinking about every single point in their resident they can optimise, and I think it's really cool to see what effects that can have.
Host: Paul Barnhurst (38:53):
Alright, so we're going to move into our AI section, how this works.
Guest: Ron Nachum (38:58):
Sorry, were we not already in the AI section?
Host: Paul Barnhurst (39:00):
No, this is the AI question section. So we fed your profile, the questions we asked your bio, the web, we turned an LLM loose, and give us a little bit of kind of personal, maybe a little quirky questions to ask so we never know what we're going to get. Haven't read 'em.
Guest: Ron Nachum (39:22):
I'm scared.
Host: Paul Barnhurst (39:23):
I'm not sure I remember which LLM generated. I think it might've been copilot on this one. We move around. Well,
Guest: Ron Nachum (39:28):
That's concerning.
Host: Paul Barnhurst (39:29):
Yeah, we'll see. You might be able to tell. We'll see. But here's how it works. You got two options. I'm kinder than Glenn when I do it. You can pick a number between one and 25, so we'll put the human in the loop or the random number generator can pick a number between one and 25. And that's the question I read you.
Guest: Ron Nachum (39:48):
Fair enough. 13 is always my favourite number, so we'll do that.
Host: Paul Barnhurst (39:53):
Lucky 13. All right. This is on building and running the company. You're in your early twenties running a company scaling fast with executives from OpenAI, Google and Microsoft on your cap table. What's the hardest part of managing people and advisors who are decades more experienced than you? Yeah, did a pretty good job. We get some duds, but that one's pretty good. The golden retriever in accounting was a dud.
Co-Host: Glenn Hopper (40:21):
That
Guest: Ron Nachum (40:21):
Was a weird one.
(40:25):
I actually really like this question because look, I spent a huge amount of my time building this company. It's every waking minute. It's not a lot of sleeping minutes, frankly, that exists. And the part that's really fulfilling about it is of course, building really cool technology and having this impact on our customers. But the other side of it is leading and aligning a group of people is probably one of the most powerful things you can do. One of the hardest and the most fulfilling tasks, especially for us, talent density is a really key thing. Every person at Sapien is someone who is incredible, who I would want to work for in another life who maybe one day I will work for them. Who knows, right? That's the type of bar that we have. That means that organising that team and keeping everybody in line as well as working with incredibly experienced investors and customers is a big challenge.
(41:14):
I think it all boils down to I'm a very first principles thinker and a lot of our team approaches this as well, where I try to just think through what makes sense. It's not, oh, we should go do this sales process because some other company did it that way. It's okay, well why did it work for them and would it also work for us? We shouldn't just go and copy Facebook's engineering philosophy. They built that engineering philosophy 15 years ago. There's probably good nuggets in there that we should be thinking about, but what actually makes sense for Sien and who we want to be and how do we bring those pieces together? And I think that's what oftentimes when I have to work with people who might be far, far more experienced than I am, it's a good way to level set. It's a good way to kind of bring everybody to the same table because it's no longer about, I now am someone who really appreciates someone who's been there and done that and brings a lot of that thought process behind it.
(42:02):
But I'm also always trying to figure out, to the point on where we started survivorship bias, people can give you really great advice on how they did things and they were very successful, but do you actually always know if that is the main reason why they were successful or is it just a small part of it, or is it a luck or is it other pieces that come together? And so as a team, we just try to have a culture where we encourage disagreement all the time. I always tell people, just because I'm the CEO of this company, I can be wrong often and you should be calling me out. You should be disagreeing with what I'm saying. And we just have a very open culture where between team members, between team members and investors, between team members and customers, we have that culture where we always assume good faith.
(42:39):
The person on the other side of the table from you have to assume you're trying to work on this thing together. You're trying to get somewhere productive. And if you have that culture, then it's very easy for someone who might be 10 years more experienced or 20 years more experienced, but you're sitting at the same table trying to solve the same goal. It should never really matter who has more experience. It should matter who's bringing the best idea to the table and is it actually going to solve the problem? And big, we have a whiteboard over there in the office that just like the number one thing is always assumed good faith, and I think it's a value that once we live by it, it makes it very easy. Someone could be double somebody else's age, but everybody here just knows the other people are here because they're incredible and everybody's going to work together to solve these problems.
(43:17):
We have engineers working together with people who spent 10 years in private equity to go deploy SAP PN at a PE portfolio company. And sometimes the engineers will say, I think we should do it this way. Or the person who's been in private equity will actually go and we have internal coding tools. Now they're building out features in the product and telling the engineer, no, you should do it this way. That's the type of culture that we try to create, and it makes it a lot easier as we grow. And part of our team is very young and part of our team is more experienced. I think it helps really balance all of those pieces out together.
Co-Host: Glenn Hopper (43:48):
Paul, which LLM created these questions this week because there's some really good ones in here compared to some
Host: Paul Barnhurst (43:53):
Dentists to go look, I honestly don't remember. It was the day when I did four of 'em and I kept switching between different LLMs. It may have been one of 'em that day. I know it was Claude 4 7, 1 was 365 chat, GPT, and I think, or not chat copilot. And I may have used chat GPT for the other. I don't remember.
Co-Host: Glenn Hopper (44:12):
I think I'm going to call an audible here because, so what I normally do, Ron, is instead of a random number generator, I just dumped the questions back into an LLM and say, which one of these questions should I ask? But today I'm jumping in. I'm stepping in as the human in the loop because in the bottom, under the personal and quirky section, first off, we've got poker, we've got Chelsea and Real Madrid, we've got spike ball, which side note, nothing ever made me feel more uncoordinated in my life than trying to play spike ball. It's an old man problem. I think. Wow, you really,
Guest: Ron Nachum (44:46):
My son up every piece of information about me online, it seems
Co-Host: Glenn Hopper (44:51):
The one
Guest: Ron Nachum (44:51):
That I'm most love,
Co-Host: Glenn Hopper (44:55):
The one that I'm most interested in, and this is a weird, another opportunity to talk about myself, Paul, and I want to talk about the 3D printed fidget spinners. But the reason that was interesting to me is I was not a great student in middle school. I was too busy thinking I was really funny. But for some reason, whatever version of economics we had to take in middle school, we had to start this business and sell something, and we had to just pick some sort of crappy bubbles. And I found some acrylic key chains that people could put photos in. But I turned them into rock and roll key chains, and I cut, this is how old I am. I cut pictures out of magazines. Have you ever seen an actual printed magazine? I cut pictures out of magazines and I had my LED Zeppelin and the doors and whatever key chains I was making, and I made more money than any other business. So there's that story about me, and we're going to finally get back to what we're supposed to do is ask questions of our guest.
Host: Paul Barnhurst (45:50):
That's all right, Glenn, we can humour you. Like I said, senior citizen and all.
Co-Host: Glenn Hopper (45:54):
So you grew up selling 3D printed fidget spinners, and this is actually, I'm reading this from what the AI spit out, so I don't know where this was located, but it says you grew up selling 3D printed fidget spinners and running a rubber band bracelet operation where you employed other middle schoolers for a cut. I just want to hear about that. Watching
Guest: Ron Nachum (46:11):
Was third grade. It was elementary schoolers. Okay.
Co-Host: Glenn Hopper (46:14):
It would be great if you were in third grade and had middle schoolers working for you. That would be,
Guest: Ron Nachum (46:18):
They could have been not, could have been. My answer to the last question is I've been preparing since I was in third grade,
Co-Host: Glenn Hopper (46:24):
And there's more to the question, but honestly, I don't care about the rest of the question. I just want to hear about that.
Guest: Ron Nachum (46:28):
I think I've always, from a young age, I was somebody I like to say I just had a bias towards action. I was just like, if I couldn't sit still, I just wanted to always go do something. My grandfather ran a furniture shop, and I think that was one of the things where I saw this idea of, okay, you can just create something of your own and you can just put it out there. So yeah, growing up in third grade, I got one of those Rainbow loom kits that everybody was making, and I for some reason had to take it to the extreme of, well, I was going to start making these bracelets, and then I made a website and I started putting them on there and trying to sell them. I then actually started selling them in school, and I basically told I was getting too much demand, so I started telling my classmates.
(47:04):
I was like, well, you guys also have this Do you want to make some money, if you make one, I'm going to sell it for $4 and I'll give you dollars. And I made a few hundred dollars off of this within a couple of weeks and the school got wind of it and they were not particularly happy. They actually ended up making me donate all of the money that I made, but in some ways I actually think that was a cool ending to, because I realized, okay, I can do something really fun. I can learn a lot from it, and I could actually put the money to a good use. Frankly, I was not going to do anything useful that I was probably going to go try and buy an Xbox or something. It was a cool experience. In middle school I was 3D printing fidget spinners, kind of the same idea.
(47:37):
I got to keep the money that time I actually started printing them on the one 3D printer in our school, so I was printing them on there and then eventually I was monopolising that 3D printer too much. So I had made a few hundred dollars at that point and I went and I bought my own 3D printer and just started printing it at home when I was at school and I would just bring in a new batch of 10 or 15 spinners every day and went on Amazon. I ordered a bunch of the bearings that go into those spinners and there's a huge box on our front porch one day and my mom was just like, what is going on? How do this even get here? I think it was always just somebody who I felt like I wanted, if I saw something, I wanted just, I can't even explain why.
(48:13):
I just always wanted to do more. I think why I ended up dropping out of college to start a company. I mean we didn't even touch on, I spent a few years in high school building a liquid fueled rocket, which was like the next escapade. I was on a goat farm pouring concrete and building electrical systems. There's so much to do in the world. I've always just wanted to, if something's in front of me, my friends will probably tell you I do something either 0% or 110%. I have no understanding of what doing something 50% or 80% of the way there looks like there's two extremes and I find myself on that 110% extreme pretty often and probably a good thing to be a startup founder in that way.
Co-Host: Glenn Hopper (48:48):
This totally could have turned into one of those four hour podcasts. I guess we're supposed to cap this. I think we're already long. We
Host: Paul Barnhurst (48:57):
Are fascinating. I have a daughter that will be waiting for me at school
Guest: Ron Nachum (49:02):
Care that let's not do that.
Host: Paul Barnhurst (49:04):
She'll wait a couple minutes. She'll be okay. I'll just tell her it's Ron and Glenn's fault and she'll be like, who? We'll
Guest: Ron Nachum (49:12):
Take ahead.
Host: Paul Barnhurst (49:13):
Honestly, I think I could go a couple hours, but thank you so much for joining us, Ron. This was a lot of fun. Really enjoyed chatting with you. Great question to end on, Glenn. Well done. Continue to be Miami Vice and until next time, thank you everybody for joining us.
Guest: Ron Nachum (49:26):
Appreciate you both. Thank you.
Host: Paul Barnhurst (49:29):
Thanks for listening to the Future Finance Show. And thanks to our sponsor, QFlow.ai. If you enjoyed this episode, please leave a rating and review on your podcast platform of choice, and may your robot overlords be with you.