AI vs. Human Insights in Financial Modeling to Build Accurate Models for Decision-Making

You can have the best critical thinking skills in the world. If you don't understand financial statements, you are not technically going to be able to do the primary thing you are supposed to do for your role.

Anywhere that you see numbers, you see a financial model behind it. And also there is a thin line between the operations and the strategies. And there is a financial model in connecting it.

Anybody who has ever worked on a spreadsheet that is iterative knows that it makes a spreadsheet unstable.

As a financial model, you want to learn VBA because you're going to feel like the most powerful magician in the world in terms of being able to control over your own productivity.

So we have a diverse group of expert modelers.

Financial modeling is an art as much as a science.

Financial modeling is a multidisciplinary. We need Excel, we need financial modeling, we need accounting, finance, quite a lot of stuff together.

It won't die from obsolescence. No software is going to come along. And then we put Excel in a paper sack and take it out to the alley for the garbage man. Instead, it is going to die from irrelevance because.

Welcome to Financial Modelers Corner, where we discuss the art and science of financial modeling with your host, Paul Barnhurst. Financial Modelers Corner is sponsored by Financial Modeling Institute. All right, welcome out there, everyone in LinkedIn and YouTube. We'll get started here in just a minute. We're just coming to the top of the hour. There we go. I could see David happened to join on his phone.

Hi, everybody. Hi, Oz.

All righty. Well, thank you everybody for joining us. Really excited. This is what I call round two of the great debate. We did this a few weeks ago. Several of you may have had the opportunity to attend that one. We had a bunch of people from Australia and the US this time we have mostly Europe, a little bit of the US and also Africa. So we have a diverse group of expert modelers. And just in the interest of time, where we're going to start is we're going to start doing a quick introduction. How this is going to work today is we have about 13 questions we're going to run through. Each modeler is going to get a minute and a half or a minute 40 to argue their position and then we'll move on to the next one. We'll share a link for you to vote. There's also a Link in the LinkedIn Live Comments for each question. There's a separate link to vote for who you thought did the best job arguing their side at the end. We'll show you how that went. So we're going to do a really quick lightning round of introductions. 20 to 30 seconds. Why don't we start with the humble MVP who's wearing my hat?

Giles that's because I'm trying to get in your good books, Paul. So, yeah, pleasure to be here, Giles. Mail I am co founder of Full Stack Modeler.

Humbled Like It Will.

I'm Will Wardle. I am an independent financial modeler. I've been doing financial modeling for over 20 years. Cut my teeth. It's in KPMG. I was there for five years and now I'm just also an Excel geek, having used it since I was 15 years old with version 1.52, I think.

All right, Carolina hi, I'm Carolina.

I am from Brazil originally. I've been working with financial modeling and FP&A for the last 20 years, I guess. And now I run Platiq Financial where I help small and medium companies to restructure their finances and their financial modeling as well.

Great.

Thank you.

Hediya hi, my name is Hediye. I'm originally from Iran. I made financial modeling my profession and my passion and very happy to be here today.

Day.

Great. Oz.

Oz here from Las Vegas in my living room. I'm an Excel MVP for 10 years and I run the YouTube channel Excel on Fire and I collect kaleidoscopes and there's maybe a quarter of my collection behind me.

Love it.

All right, Rishi.

Hey there, Rishi Sapra from London. I've lived here my whole life. I'm not actually an Excel geek anymore or financial modeler. I'm a former Excel addict, but I moved on to the harder drugs now of Power BI and fabric and data platform. So, yeah, my background is as an accountant and I spent the first decade of my career working for the Big four, some of the big banks in London. But I moved into business intelligence. I worked for a company called Avanard, which is basically a joint venture between Accenture and Microsoft. So I still love engaging with the finance community and it's been great to see how much Excel has moved on. So I thought I'd come in and share the love with the Excel community.

Not sure I brag about moving on to harder drugs, but that's a separate discussion. All right, David Brown.

Hello, I'm David. I'm David Brown. Funny enough, there's another David Brown as a financial model. I'm the other one from Nigeria and I've been doing Excel. Excel has been doing me for the last 27 years.

Right? You're breaking up a little bit, honestly.

So I've been working with Excel for the last 27 years. I'm a financial modeler around Dee Brown Consulting and I work with Power BI and Excel, so kind of Randall the two together.

All right, great. So before we get started, one more thing. If you're out there, please let us know where you're coming from. We love participation in these events, so feel free to comment as much as you want on LinkedIn. We'll see those come through and just have fun with this. We're going to go ahead and get our first two guests up here. So I'm going to remove everybody else from the stream real quick and we'll get started. I should have kept myself on the stage. I removed me for a minute.

That idea.

All right, so we have two guests here with us. Our first question, and I'm just going to throw it up so everybody can see it in circular references in financial models. Yes or no? I think we'll start on this one. Give Haidia the opportunity to go first. I know she loves this question so much. So tell us why we shouldn't use circular references. Why is it a no for you?

Well, I would say, you know, the cooler reference to be or not to be is like asking the question, or are you for or against cancer? And what. Why is that? Because anybody who has ever worked on a spreadsheet that is iterative knows that it makes the spreadsheet unstable and very slow to run and all sorts of problems. And in the world where I am, which is Project Finance, it's just impossible to work with the iterative model. So I would say the better question to ask is how to deal with the circular reference, not that whether it should exist or not. And the conventional ways to deal with circular reference is copy and paste, which is just to freeze the problem. And this method of copy and paste to me, again, makes an iterative process because you have to copy and paste. And then as the model gets bigger, and this is one of the main problems in Project Finance today, is that this copy and paste becomes like blocks. And again the model. The same problems that we have with circular reference with an iterative model, which is slow to run, it comes with the copy and paste method. So like any other issues we have in our personal life as well, when we are stuck in a loop, we need to get out of it. You know, either we find simple solution to get out of a loop, or we just go deeper and try to sort it out and to me, and my challenge as a financial modeler has been to find a solution to really deal with the issue of circular reference, not to just deal with it with just a simple copy and paste. To me, that's a temporary solution and there are better ways to deal with it. And one of them is to use this beautiful option that we have in Excel, which is vba. Go behind and create a code, create a user defined function and create a parallel model next to our model that can sort out the issue. And so that's my opinion about this issue.

All right, great. We'll go to David. Now give us the, the other argument here.

So I mean, I'm sure you could hear quite a lot of talk, I mean, back and forth, back and forth about different methods and stuff. Circular reference means that there is a circular in your model. It's a natural thing and there's a natural solution to it. It's just a tick, simple tick and we solve the problem. Now what that does is also enables us or forces us to document. All we need to do is have a place where we document and say, hey, there is a circular reference here and we've solved it. So when you have that documented, any other thing that's wrong with the model that caused by circular, you actually see why it is. You see it clearly documented. So I think the problem people have with circular, they forget that there is a circular. It's not documented. So once it's documented, it's a clean solution. It's pretty simple. Vba. Well, I have my own misgivings about vba. VBA is a no, no. Most people even switch it off. So if your VBA is off as a company, you can't solve your circular because you don't use vba. So I think circular references, yes, you can have them, but you just document and it's pretty good.

All right, thank you, David and thank you, Pei. You can both vote for who you thought did a better job. So I'm going to put it up here. This is the link. You can find it on LinkedIn. Unfortunately, I couldn't do a hyperlink here, so you could just click on it. But if you go to LinkedIn in the comments for this event, you'll see every single question. You can go vote for who you thought did a better job arguing for or against circular references. I think this is one everybody has the strong opinion on and there are, I've seen a lot of debate on this one. So thank you, both of you. We're going to bring our next two Guests on for question number two. This is bba. So here we go. All right, we're gonna bring back on David, he gets to argue one more time. And we're gonna bring on Rishi here. So question number two that we have is use of VBA and financial models. So Rishi, our registered, our resident power BI person, I wasn't say financial modeler, but not, not anymore. Our resident BI person who's going to be arguing the yes, that we should be using VBA for models. So Rishi, you're on the clock, you got a minute 40. Go ahead and tell us why our financial models should have vba.

Well, I think as a financial model you want to learn VBA because you're going to feel like the most powerful magician in the world in terms of being able to control over your own productivity with vba. As a financial modeler, you enjoy this experience of manipulating grids of numbers to achieve certain calculations and certain outputs. And because you have the Excel object model directly in vba, that's exactly what you're able to use it to automate. And if you really want to experience productivity game you get from learning dba, you could use it to leverage the micro Automations that ericom has come up with where you can literally just go in, put in your editor functions in Excel and create your own software application to work exactly how you want. And that's the power of vba. The second reason is that the alternatives to vba, things like Python and Office scripts, they're just not as good. I have no idea why Microsoft decided to put Python into Excel cells rather than have it as a version that talks directly to the Excel object model in a scripted environment like VBA Editor or something better. And you know, I do feel bad that the VBA editor hasn't had an upgrade in the last 20 years. It's probably the only component of Microsoft I've seen that hasn't had Copilot integrated into it. So it hasn't had much love, but it should have love. And once Microsoft realized that, and maybe at some point in the future, they will, they'll get their head screwed on and then it will be a million times better than Python in cells or ethoscripts at taskbars. And the last reason, so what we were talking about the other day, Paul, as a consultant, as a financial modeler, the key to success is niching down right? And being one of those few people with unique skills that are highly in demand and financial modelists with vba, that's exactly what they are.

You can do fewer things with vba.

Than you can do with Python, but it doesn't have as rich a library. But sometimes less is more. And combining financial money skills with VBA gives you that edge that most people just don't have.

All right, thank you, Rishi. Appreciate that. To our audience, please provide comments throughout. We're going to give David his opportunity to respond, but keep the comments going. The guests that are in the background, feel free to comment. Let's have fun with this. And David, your counter argument. Time for you to tell us why we should not be using vba.

So, first of all, Excel is king. You have to understand that VBA is like another. Is like a software that kind of sits on top of Excel. Why not use Excel directly? If you can use Excel directly to solve your problems, then you should. And I can tell you 99.99999% of the time, Excel can do it perfectly on its own. You don't need vba. And guess what? Why is Microsoft not doing anything with VBA for 20 years? Because, frankly speaking, there are other things. There are other tools that VBA can do that actually you don't need vba. And Excel has gone. I don't know if you've heard of dynamic arrays in the audience. Dynamic arrays, lambdas. They're stuff that VBA could only. Only VBA could do. But guess what? Excel can do it now. So you stick with Excel. Stick with Excel. That's number one. Stick with Excel, because even the investment in VBA is not happening, because we know there are other solutions that are better in native Excel. And then VBA gets switched off by most companies. Why? Because it can take viruses. You're not too sure. And guess what, modelers? We're not building models for ourselves. We're building it for our companies. We're building for people that don't know Excel as well as we do. So they don't know Excel. Forget vba. They don't even know Excel. So you need to build the stuff that people can actually open. And the risk is people can open your models full of VBA. VBAs are not enabled and your model doesn't work. Models not working is a no, no. So VBA also a no, no.

All right, thank you, David. We'll let everybody vote which argument they think they like best, where they stand on this one. So go to the link there. And we're going to bring our next two guests on here to keep this debate going. So thank you, both of you. All right, we got question Number three, this one, we have Carolina coming on the stage and we have R. Where is he? There he is, the FPA guy hat known as Giles. He's. He's trying to get some brownie points from me from wearing that. We'll see how it works.

It's not going to work.

See, there you go. You've already been told it's not going to work. So question number three. Shouldn't we build fully dynamic models using dynamic arrays so they fully adjust in Excel? This is a debate I've had with several people. Question we ask our guests now because it's becoming a bigger issue and what we're going to do is I think it's ladies first, right? So we're going to let Carolina go. She's going to be arguing, no, we shouldn't be building fully dynamic array models. And after, Giles will give us the counter argument. So, Carolina, you're on the clock.

Go ahead.

Okay. So what I think about the dynamic arrays, it's awesome that Excel can do it and it's very nice to see it. Just like the circle reference. I have the same opinion about it, but it brings up an extra layer of complexity to financial models. It's fine, it works great. But fully dynamic array financial models, I don't believe it will work because it's just too much for just one single simple model that could be simpler. And I am totally for simplicity all the time. I try not to put any kind of complexity that it's not necessary. It will bring auditing challenges. It's much harder to audit a financial model that is built with dynamic array itself. And especially if it's fully dynamic array, then it's almost impossible. It's very hard to be compatible with all types of Excel. So not everybody has the type of Excel that will support dynamic array. Not yet. I'm not going to say that in the future it's not going to be more fully used, more widely used. But for now, I think it brings a complexity that it's probably not necessary. So I will vote for no fully dynamic rate financial models.

All right, thank you for your argument. And I saw a comment come in. It was Jack Kennedy asked in the voting, are we voting for our opinion or who we thought made the best argument? Go with who you thought made the best argument. Hence it's a debate. That's kind of the idea here. Not just voting for what you think. For the actual live vote, put what you think in the comments, totally fine with that. But for the voting, go with what you like best. All Right now we're going to hear the counterargument of why we should do this. So, Giles, you're on the clock.

Awesome. Well, firstly, Carolina and I were joking before that we pretty much agree with everything. So this is just a strong debate position. Look, if the question said specifically, should all financial modelers be forced to convert to full dynamic array modeling today, my answer would be categorically no, because we're not ready for it. But so I think you have to answer this a little bit aspirationally and a little bit technically. So technically, today, dynamic arrays offer huge improvements to modelers. The fact you can't go into period five in your array output and tweak the number to make your balance sheet balance is a huge step in the direction of best practice modeling. The fact that dynamic arrays deal with data more effectively, more dynamically is a huge improvement for modelers. But we have one big challenge, which is the circularity that dynamic arrays create when you're dealing with three statement models and balances. We have the best and brightest minds looking at this challenge. We will solve it or Microsoft will evolve the tool so that it's solved for us. So you have to answer this question aspirationally and I think the answer has to be yes. We should be looking at this positively as a community. How do we solve these problems as quickly as possible so that we are all using dynamic array modeling to the best effect in the future?

All right, thank you, Giles. And one thing you're going to notice, I think you'll notice with all our guests, obviously these are nuanced. We say yes or no to have a debate here, but you're going to see different comments say, is it the future? Is it aspirational? Everybody's going to take their different approach to argue their side. But thank you, both of you. I'm just real quick while I have you, we'll see what a couple people said. I love what you said. The best mantra is simplicity. So there's one for Carolina and another one that really liked simplicity. Yes, Flefs simplicity. Say that again. So I'll say it, keep it simple. But dynamic rays are wonderful. So you pick which side you want to vote on there because there's a little bit of a dichotomy sometimes. But we're going to go ahead and move to our next guest. So thank you, both of you and we'll go to the next question here. All right, so next up we're going to have Will, our self proclaimed geek from the age of 15. And we get Carolina Again on this one. So welcome back, Carolina. This is going to be question number four. So this is should modelers use named ranges in models? So here we're going to again, let Carolina go first. She's going to be arguing, yes, we should. Will's going to argue the opposite that we shouldn't. So Carolina, you're back on the clock. Go ahead and tell us why we should use named ranges.

Yes, yes, yes. For named ranges I've been using more and more lately because I think it brings readability to the model. It makes the model more easy to read, easy to understand the formulas and much easier to audit because it's all laid out there. It's much easier to understand a formula that is named. For example, if I say tax rate, something times tax rate, it's easier to see, to understand than something times C5, for example. So it's much easier to understand a formula to explain a formula to audit a formula and you make less errors. And it's easier also when you're using the prompts or anything that you're using that you're going to copy from one sheet to another one, like the form control, for example, you can copy and all of the characteristics of the form control will go with it. If it's name range, if you put a name range that will go across the full workbook, then you can copy around everywhere and it doesn't mess up your formulas, it doesn't mess up your form controls or anything else that you're using. So it makes simpler. It makes it simpler and makes it easier to understand and easier to explain as well. And I'm always for simplicity. You're going to see on all my, my, my questions. I mean, I am the person for simplicity. So that's one more thing that will help with that.

All right, thank you. Appreciate the argument. You get it just in the nick of time. Will, are you ready to tell us why the opposite is true?

Well, I think I do actually have to agree with Carolina about this, the simplicity thing. I mean, I am not against using name ranges in a financial model. I use them for constants and for ranges when I'm doing VBA code. So they are truly dynamic. So as you said about simplicity carrying, you can actually do a tax rate, you can do all this. Now in my experience over the last 20 years, I have had some horrific models where which had had lots of named ranges in there. And one of the worst one was they had a telephone directory of all the name ranges in that particular model. So they, it wasn't simple, you actually had to go. You could never trace anything back. Now in the, in the simplistic model, if you've got a range called revenue and costs, you can actually multiply this two together. You can see, oh, that's the revenue range, that's the, the cost. And then you can work these things out. Now, when the model steps up to a much higher level of complexity, you start developing your own cottage industry of maintaining your named ranges, then Name Manager isn't up to speed. It is. Hasn't changed in the last 20 years since I've actually used it. Eric Ohm in a Thing About Robots said to me, it's as if Microsoft has actually lost the code for Name Manager. It is not fit for purpose. Then you've got the problems of name ranges being deleted. You end up with hash refs. There's lots. And then I know this is the best one. Designs ranges, hidden name ranges, audit nightmare. They can appear out of nowhere. Links to all sorts of different things. I just built like named ranges because of that one.

All right, so go ahead and pick which argument you like better there. I think there were some great things brought up. You know, name ranges. Yes. I think we can all agree whether you're using them right now or not, we'd love to see an update by Microsoft intent to named ranges, because who's ever had that file with 10,000 references with all broken links and things to named references. So I think there's some opportunities to improve it. But you guys decide. Use them, yes or no? Thank you, both of us, both of you for joining. We're going to bring our next people up on the stage now. All right, so that was question four. Question five. This is a fun one. Please put your thoughts in the comments. We got Oz and Rishi to battle this one out. It's the will Excel ever die debate. Never had that one before. Right.

We need to touch gloves and keep it fair.

Yep, no kidding. You know what? We're going to let you go first, Oz, and tell us why Excel is eventually going to die.

All right, there's two ways that we can think about this. Obsolescence. No, it won't die from obsolescence. No software is going to come along and then we put Excel in a paper sack and take it out to the alley for the garbage man. Instead, it is going to die from irrelevance. Because right now we have technology run amok and we are staring at the four horsemen of the apocalypse. We have engineers who have forgotten that they live in a society with the rest of us, we have slimy data brokers and the wanton desires of venture capitalists and soulless digital marketers. They will usher in the death of humanity. And once society, once regular people who've lost their jobs to AI, who've gotten fed up, who are tired of hearing, well, have you cleared your cookies yet? They are going to take to the streets with table legs and rocks and that rod that you have in the middle of artificial Christmas trees. And that will be the last gasp of human dignity. And when we have no more dignity as a society, mon frair, we are in trouble. We got bigger fish to fry than thinking about Excel. And the last formula that will be written in Excel will be equals survival open parentheses and the battery will die. And the user will look out across his shack and out the window and see the sun glistening on our shame.

All right, thank you Oz. Go ahead and put in the comments what you thought of Oz's argument there. We're going to bring Rishi up now and give him his counter argument.

So here's a little thought experiment that I want everyone here to do with me. What would an immortal software product actually look like? So think about this. An immortal software product would be a software that a significant proportion of people, not just thousands, but millions, hundreds of millions or even billions of people use and love on a daily basis. It would be that kind of software product that's ingrained into society, grained into communities like sports are like professional sports. People would compete using the software product in the entertainment capital of the world, Las Vegas. Where was this from? To win cash battles and fierce competitions that are aired on espn. It'd be a software product that allows so many types of people to express themselves in different ways, from marketers at a Fortune 500 company to heads of households trying to work out if they have enough cattle at the end of each month to cover their kids school fees. And because of all these different use cases. It would be a software product that's accessible to everyone in an environment that gives them the opportunity to be creative without being constrained by complex UI or fixed set of features that a software vendor has decided to implement. And one that people could customize themselves. They could build their own automations in and customize exactly how they want. It would be a software product that would generate the world's largest software firm billions of dollars of revenue a year so that it's got the funding to continuously innovate and be the best in class. And it would be a software product that is so entrenched in corporate workflows that it would just be a part of almost every process that everyone in the entire organization is involved in, and one that the entire banking system and even the entire world runs on it. That would be the definition of an immortal software product. And that is Excel today.

Perfect. Running on time. Thank you, Rishi. Thank you, Oz. Go ahead and vote for who you think won that argument there. Loved it. Some great points. Everybody should learn the equal survival formula. Try it in Excel today. Let us know how it works. All right, let's bring up our next guest. So this is a surprise question that I'm going to throw out here. So Carolina gets to come on stage for a little surprise. She doesn't know what the question is, but I bet she might have some ideas. So tell our audience, you get one minute here. Why understanding three statement models is the most important skill for FBA professionals.

Oh, that's a good one. Well, I think it's the most important skill that a finance professional can have because when you start understanding the three statement model, first of all, the three statement is the language of communication in finance. You have to agree with that. Every time you're going to report numbers, either on the stock market or to compare companies or to buy companies, you're using the three statements. So it's the language of communication in finance. Why it's so important to understand the three statement model. Because as you are working with the three statement model over and over and over again, you start to build a model in your head and that will help you understand what every business decision, how every business decision flows through your finances, as it flows through your finances, it's going to show in the three statements. So if you're very familiar with the three statements, we're going to be able to understand how each business decision will impact the business and in the finances in the numbers. So that's why I always tell all my students and my team and everybody that works with me, build a financial statement from a financial model in your head so you are able to take decisions quickly and understand how any, any business decision will impact in the business. That's fine.

Thank you. And arguing no on this side is going to be the FP and a guy. So I'm going to put on my hack here for my argument. So I'm different from the host and first I'll say I'm the FP and a guy and I say no. So you should vote for me. The real reason I say that is in 12 years in FP&A in corporate FP&A, I never once built a three statement model. I built P&L's. I understood the basics, but I don't think it's most important. It's important. I think people should understand it. But I would much rather have someone who's a critical thinker, strong excel skills, communication skills. I'd probably put it fifth or sixth on the list of skills I want when I'm hiring somebody. I can't remember ever hiring someone and giving them a test to see if they could build a three statement model. And I had some great employees. So I think it's important. Do I think it's the most important? I don't. But you guys get to decide. That's the beauty of this. So go ahead and vote for whose argument like best. And thank you for coming up and humoring me on the spot there, Caroline. I had to have a little fun. We got one more surprise question a little later. That will be for Giles. So you'll, you'll get to, you'll get to enjoy him being on the spot. All right, so keep the comments coming. We have a lot of them coming in. Let's see what we have.

FP and a guy here. And as you know, I am very passionate about financial modeling. Investors the Financial Modeling Institute's mission. I have been a huge fan of the FMI for years and I was super excited when they decided to sponsor the Financial Modelers Corner. I recently completed the Advanced Financial Modeler certification and loved the entire experience. It was top notch from start to finish. I am a better modeler today for having completed the certification. I strongly believe every modeler needs to demonstrate they are a qualified financial modeler. And one of the best ways to do that is through the FMI's program. Earning the accreditation will demonstrate to your current and future employers that you are serious about financial modeling. What are you waiting for? Visit www.fminstitute.com podcast and use code PODCAST to save 15% when you enroll in an accreditation today.

Yeah, we got them about AI going work in PE and it's cash and the causes of cash. So we got a lot of different opinions. We're going to go ahead and go to our next question. So now we're going to bring up on the stage for question number seven here. This is going to be will and idea. So we got them both on the stage. Let me pull up the question. And so we have number seven. Will AI eventually build the models for us? This has been a debate that I think a lot of people are having a lot of work's being done, a lot of different opinions here. So we're going to let Will kick us off by telling us why AI will not work. Build the models for us.

Well, as a trained economist, Keynes said in the long term we're all dead. Eventually they may do, but at the moment AI is nowhere near capable of developing a financial model. I mean for me financial modeling is an art as much as a science. You can put 10 financial models in a room together and you may get 20 completely different answers. The art in financial modeling is that you will find one of those 20 answers that is the best for that particular situation you actually deal with. So what I'm trying to say is financial modeling. Well, AI in financial modeling, it is a large language model. There's no intelligence in that, there's no spark, there's no creativity, there is nothing that. I mean the whole concept of light is the fact that we can actually think independently. Large language models are just regression models of a various different sorts. So what I'm actually trying to say is you have the ability to have inspiration, the thinking, creativity when you're building financial models, which a computer doesn't have to do. Now I'm not saying that Excel has or AI hasn't got the ability to do elements of automation to help you actually do things or with the analysis of data or the analysis of outputs, but in the actually ability to, in the creation of a financial model, I do not think that AI can ever replicates the ability of a human being with this high seconds amazingness that we can actually do.

All right, great. We're now going to hear the counter argument from Ada. We're going to get her up on stage here and let her tell us why is AI going to build the models for us?

I would definitely think it will. I'm not saying that it will be a success, but I already see the trend. You know, I see now most companies, the way they are dealing with the financial modeling is that they have separated the work of building the model and doing the analysis. They have a bunch of people sitting in an office, you know, building the model. These people, they have no idea about the deal. They are completely isolated from the transaction. They haven't, they don't participate in the project calls, they don't go to site visits. And so these are the people who are building the model and then some other people are using. And this has caused us to deal with models that are not overly complex. And I deal with them on daily basis. So I think what's going to happen is that AI is going to replace those spreadsheet engineers. And I hope that AI will be more intelligent and can simplify the task so that we don't have these complexity in our models, what we see today.

All right, thank you. Appreciate that. Thank you both for arguing that you can go ahead and vote for who you thought the winner was. We're going to keep going as we have a number of questions to go through. I love what Davidson said to that one. Real quick. Wow, that is a tough question. To be honest. I don't know how to answer. I think, you know, there's definitely some people struggling with it. Right. It's an art and a science. But go ahead and vote for which one you like best and we'll go to the next question. All right, so we're on question number eight now. This one is should financial modelers learn Power bi? And we have two people coming up on stage. I think they've had to argue against each other once before. So we're going to give them a second round of going at each other. I think this time since last time, Oz got to go first. We'll let Rishi go first here this time. And should financial modelers learn Power bi? Rishi is going to be arguing. Yes. So you're on the clock. Go ahead and tell us why.

Thank you, Paul. So yes, I think financial modelers should learn Power bi not as a replacement for financial models, but having both together that duo and financial models and Power BI reports are the future of data decision making because they fuel different types of data decisions. Power BI is so much more than data visualization. There's three things I think it gives you on top of your data. The first is context. And if I could sum up Will's argument of why I want to build financial models with one word, it's context. It's because AI doesn't have enough context to turn your spreadsheet of numbers into a financial model. And that's what you get with Power bi. It's a semantic model. It's a structure that captures relationships with your data set, financial logic with DAX and even row level access permissions. And it's that context which gives your data meaning. It's actually a cube SQL Server Analysis Services cube which is ideal for calculating ratios, performing variance analysis and understanding what's driving your numbers. And this intelligence applied on top of your data is what both gen AI and humans can use to make those data driven decisions. The second is automation. So hopefully everyone here knows Power Query. You can use it to clean transform shape data. One click on pivoting, split text from numbers, merge data. So merge data sets together all in this transparent, repeatable workflow. You combine that with Power Automate and with Microsoft fabric and you have a really powerful data pipeline where you can integrate python notebooks and AI for data validation or anomaly detection. Yes, you have Power Query in Excel, but putting it into Power Bi and into fabric, it makes that automation so much more robust and so much more supportable. The third thing is storytelling. So find out. State isn't about the numbers, it's about the insights. So this is interactive features, cross filtering drill through from a high level member on the income statement to underline journals, all these kind of things through to copilot to answer natural language questions. That's Power Bi.

Thank you. Now we're going to hear the counter argument of the no.

So o give us the no Power BI interactive dashboards. Data visualization is sexy. It lures people in. They go around Power Bi licking, licking, licking like flies in a Venus fly trap, licking that sweet nectar until it just snaps them in because they've fallen for the puffery. Because when have you seen Power BI used in financial modeling competitions? You've not. Because you have to get to the hardcore stuff, not huffery. Don't get caught in the forks of a Venus fly trap.

All right, so Oz is telling us don't get caught in that Venus fly trap. Thank you both of you. Love the arguments. We're going to give you that chance to vote. Remember, you can also Find that on LinkedIn in the comments for this event. Vote for who you like there, let us know in the comments. We're going to move on to question number nine here. So we're going to bring two more people up on the stage this time. We're going to welcome back Carolina and Will for this argument. So our question is, are financial models the number one corporate decision making tool? We have Carolina arguing yes, Will arguing no. So we're going to give the floor to Carolina first and go ahead, you're on the clock.

Okay, so this pretty much ties with what I just said before about this financial modeling, especially the three statement modeling being the number one skill that a finance professional should have, a financial model. And now I'm not just talking about the 3 statement and actually I'm not talking about Excel financial modeling. I'm talking about financial model in general. This is everywhere in the company. So there are financial models everywhere. Anywhere that you see numbers, you see a financial model behind it. So that's why I think it's the number one decision making tool. And also when you see there is a thin line between the connects between the operations and the strategies and there is a financial model in connecting it. So it's very important to understand what is this model that will connect operations with the strategy. So every decision needs to tell operations what to do in order to achieve strategy. So that's why the financial model would be the first tool that people will take for decision making.

All right, thank you, appreciate that. We're going to now let will tell us why it is not. So will go ahead, let us know why it is not.

This is a very difficult argument to hold against. If you take a financial model in its purest sense, then financial models exist within organizations. If you are taking a pure financial model as in a three statement financial model that's fully integrated, then no, it is not the first go to thing. There are so many more areas that you can actually look at in terms of a business. You'd be looking at your as Paul is an FPA guy, you'd be looking at your budget, your actuals, you'd be actually doing your variance analysis to see where you actually are. Now that is much more important than a financial model that's looking four, five years ahead. That is why it's not really the go to model. But there's also other models that exist in the business. There are metrics about sales, there are metrics about customer satisfaction. You do not. I mean if you go into banking, you've got a whole which I've worked in, you will have this whole subclass of models that look at your balance sheets. But then again would you classify those as a financial model in what we're trying to look at? So it's the semantics of what is a financial model. A financial model can actually be a spreadsheet with two numbers that adds things together that. But then that's we. We lead onto a whole different subject.

Sure. We, we could start to punch me if what qualifies as a model.

Yeah, exactly.

Thank you, Will. My, my favorite answer on the show so far. As I asked someone our appropriate financial model is the number one decision making tool. The response I got was no, it's politics. And I was okay, that's hard to argue with. So that would be my counter argument if I was one of these here. But go ahead and vote for these two. Which one you like best? I think they enjoyed that one. And you know what, funny enough, we're getting comments that we need to Bring Giles up. He's being asked for. He's humbly listening. Let's bring on Giles. So guess who's next? Where is the most humble mvp? So we're going to meet the demands of our audience here, the crowd. We're going to bring Giles on for a surprise question that he has not had time to prepare for. So Giles, there's nobody arguing the opposite side of this. You're on your own here. You get one minute, not a minute, 45. Please explain to the audience why you are the self proclaimed most humble MVP in the world.

I was born this way, Paul. I mean, this is a mix of perfect genes and a lifetime of great decision making. I carry this burden with me every day. You shouldn't really need to ask. I am just the humblest mvp. The next time you have a bad day, whether it's at work or with the kids, just remember the burden that I carry around remaining this humble every day. When I look in the mirror and I see this staring back at me, there is no counter argument. But thank you very much.

Thank you. We appreciate that argument, Giles, and we will bring him back on again to make a real argument. But he did a good job there. Love the coat, love the glasses. All right, next we're going to bring back on Oz for our next question here. So we're going to kick Giles off the stage. He can bring back his hat and try to score some points. You know, funny enough, this question is should financial modelers learn Power Query? Of everybody that answered for this session, we only had one no and he wasn't able to make it. It was Chris Riley. So feel free to comment on one of his things, DM him and let him know that he's out on a wilderness. Everybody else thinks we should learn Power Query and Oz gets a minute here to tell us why we should learn Power Query as a modeler. So Oz, take it away.

Imagine the olden days of being required to use VBA to bring data in from multiple folders, multiple sources. Those were the bad old days when people had a life expectancy of 35 and they were dying in mine collapses. If you aren't using Power Query, that's where you are. You out there in the wilderness with this fellow. You don't want to be there because Power Query makes this easy. Beginners can use Power Query. If all you need to do is split a column, you can do that. You don't have to be bones in the bottom of a mine shaft because you are hard headed.

All right, love it. Thank You Oz a column, you can do that.

You don't have to be bones in the bottom of a mine shaft because you were hard headed.

All right, Love it. Thank you, Oz. So don't be bones in that mine shaft. All right, we're going to move on to the next one here. We just have two questions left and then we'll quickly show. I do not believe there is a link for question 11, Jack. I see that coming through. Said we gave him the win. There was no need to vote. There is an opportunity to vote on Giles though, so you'll see what's there. Right, we're going to move on to question 12, see if I can keep this all straight. Which financial statement is most important for a modeler to understand? So we're going to bring on our humble MVP and we're going to bring on Kia to argue this one. We had one person who voted for P and L, they couldn't make it so it got kicked out. P and L, who cares? It's not important is what we're saying. So now Giles is going to tell us why it's all about the balance sheet. So, Giles, you're on the clock.

So I think you can answer this in a couple of ways. I would look at it one, from like a training and skills perspective. Which of the three statements would it be the biggest problem for a modeler not to understand? I think there's more to the balance sheet than any of the other statements. So to not have a modeler comfortable with the technicalities and the principles would be a massive problem for the balance sheet in particular. But then I think when you look at the three statements, look, not having the three statements at all is a problem. I think a lot of people will look at the cash flow and yes, cash is king and you have to understand your cash generation over multiple years. I totally get it. But the question I ask myself is, is it possible for something fundamental about the health of a business to be hidden from your view? If you just looked at the cash flow statement or the income statement and I think the answer is yes, is it possible with the balance sheet? I think it's as close to no as possible. And the real kicker for me is then if you assume that you're getting multiple years worth of numbers and you've got your balance sheet in front of you, you can actually sort of back calculate quite a lot of the information that you want to get from the bottom of the cash flow statement, from the bottom of the income statement. You can't get the detail. You need the income statement and the balance sheet to do that. But you can reverse engineer quite a lot just from looking at a balance sheet over multiple years. You cannot do that with a cash flow on its own or with an income statement on its own. So I think it's a tight call. But for me, I was looking at investment. I would choose the balance sheet over multiple years.

Thank you. Did that just in the nick of time. We will now hear the counter argument or not counter argument. We'll hear why cash flow is most important. So Aydin, tell us about the cash flow.

Yes, Gaz, you have already lost the debate. You already declared that cash is king. And I would add the financial model is the queen. And in my world, which is Project finance. I'm so sorry, Giles, but we don't even care about your balance sheet. We just built the balance sheet because it helps us to make sure that the model mechanics is correct. But I mean, I would even argue that.