Stop Doing Monthly Reports for Analysts to Automate Finance Workflows Using AI with David Dors

David Dors: The way we currently access data is like you go into your ERP and you click export a report and then you go and you configure it and you say, I'm doing this time period. But your agent can just go and get all that data for you without going through a, uh, UI and taking all that time. It just goes and it runs connection that gets that data right back for you. So just those things like that, where they might take five, ten minutes, but, uh, over the course of a month, a year, it adds up to hundreds of hours where. Why am I doing this work if it doesn't require my judgment? I'm just exporting the same report every time. I, uh, think it should go to agents.

Paul Barnhurst: Welcome to another episode of FP&A unlocked, where finance meets strategy. I'm, um, your host, Paul Barnhurst. The FP and A Guy. Each week we bring you conversations and practical advice from thought leaders, industry experts and practitioners who are reshaping the role of FP&A in today's business world. Together, we'll uncover the strategies and experiences that separate good FP and A professionals from great ones, helping you elevate your careers and drive strategic impact. Today's guest is David Dors. David, welcome to the show.

David Dors: Hey, uh, thanks, Paul.

Paul Barnhurst: Excited to have you. So let me give a little bit about David's background. You know, he started in, uh, FP and A, and today he is full time working to implement Claude and FP&A software solutions for the Office of the CFO. He started his career in banking. We won't hold it against him supporting private equity and wealth management clients, and then moved into FP&A before going full time into finance transformation. He holds a degree from one of my alma maters, Arizona State University. That's where I did my mba.

David Dors: Great school. Number one in innovation.

Paul Barnhurst: It is a good school. I was there. I lived in Arizona 2006 to 2016. No, 14. 2014, I believe so was there eight years. Nice.

David Dors: Uh, yeah, I've been here since I think around 2006 as well. But I've stayed.

Paul Barnhurst: Yeah, I was gonna say, but you were probably a lot younger than I was then. Yeah, I'm old. I now I'm interviewing people that I'm old enough to be their dad. That's when it's scary. So. But, uh, hey, what do you do? Like, I just. The last guy I interviewed is a business partner of mine on a project and one day we're sit there chatting. I go, you realize I'm, um, old enough to be your dad. Like, I feel old right now. All right, back FP and A. Everybody's like, just stop. Stop reminiscing. Paul, get to the point. This is the question we ask everybody. If I asked you to define what Great FP and A looks like, what would you tell me?

David Dors: Great FP&A? I think it's definitely around finding the constraints of the business and then changing people's decisions on what they're doing day to day. So every forecast, variance analysis, DACI build, it's there to help somebody make a new decision or change the decision that they're going to make. So if nothing changed from the analysis you're providing, there's not much value in what you're doing every day. So I think definitely starting with, instead of starting with the data, starting with who's deciding what do they believe in and what would make them believe something different. And sometimes it's just confirming their beliefs. You know, just making sure that, hey, we're going down the right path. But also it can be we need to make a. Make a change. And what would it take to actually convince them to make that change?

Paul Barnhurst: I really like how you said that if we're not helping people change decisions, make better decisions, and we're not really fulfilling the purpose of FP&A, there's always

David Dors: some constraint holding our business back. And if we're not looking for that every day, if we're not trying to change the decisions we make, we're just going to stay the same or even get worse. So if, uh, we're always trying to improve, it's finding that constraint that's holding us back and figuring out what would cost and what it would take to change that decision and change those constraints and remove it from the business till we. So we find the next constraint.

Paul Barnhurst: Yeah, and I really like how you mentioned constraints. I feel like I'm going back to my, uh, process improvement or kind of engineering classes and there usually is a bottleneck or a constraint that's holding the business back. Not always, but I think it's a good way to look at it, is looking for those constraints.

David Dors: There's.

Paul Barnhurst: That's definitely, you know, one way to think about it. So thank you for that answer, all. Uh, right, so I know you are an early adopter of Claude. You've been spending a lot of time in Claude. So I'm going to start with how much time do you think you've put into Claude in the last two years?

David Dors: Oh, I don't want to know. But I think it's open.

Paul Barnhurst: You're now your friend. You spend more time with her than anyone else.

David Dors: Yeah. You know, it's replaced Excel for being that thing that's always open 24 7. It's like Cloud's just always open. When I work, like, that's the first thing I reach for. So yeah, uh, it's gotta be eight plus hours a day for. Since 2025 at this point, beginning of 2025. So it's a good chunk of my time though.

Paul Barnhurst: And do you have a name for it? Do you consider it a, uh, he, A, uh, she and it. I always find that interesting how different people kind of think of Claude.

David Dors: I've been just Claude. But, you know, on April 1st they released these like buddies. They were like Pokemon buddies or something. You have like an egg that hatches and I got one that was a cactus. So I really like that one. Vanilla took it away. They took it away after April 1st. So it was nice to have like my little friend down there. No, he's gone.

Paul Barnhurst: That's funny, I didn't see that. I, uh. My April 1st was. I was launching a beard brand beer bob. I had Beard Balm, Beard oil and beard butter.

David Dors: I would buy. I'd be one of the first buyers.

Paul Barnhurst: I've had a few people tell me that. You never know, I might just launch it one day, put it on the. I already have a page on the website. I just got to get the price product.

David Dors: Yeah. Have Cloud help you build the business.

Paul Barnhurst: It helped me build the website and all the images. I think I used a little bit of Chat GPT. I still find, and I know we're digressing for a minute, but I find when I want just a jpeg, a PNG image, I still prefer Chat GPT to Claude. Claude's got a lot better there. I know most people prefer Gemini, but, you know, it's like, how many different tools do you want to use? I pay for three. I'm like, do I want to pay for a fourth?

David Dors: Yeah. It's tough to find the balance between like going deep into one tool or using what's best from every tool. But they just released the Claude design and I messed around with that. And that can make spread like make uh, board decks. It can make websites. So it's getting better there. I think it's improving.

Paul Barnhurst: I have not played with Claude design. I didn't see that release. I know they just released 4, 7, so I'll have to take a look at Claude design. But yeah, it all this keeps getting better. Sometimes It's a little scary, but it's exciting. What made you lean into Claude? Like, when were you convinced that, hey, the tool I really want to spend my time in, was it because of work or how did that come about that you made the decision, I'm going to go deep in Claude?

David Dors: Yeah. At first I was definitely like, you're saying, switching between these tools, like using Claude for some things, chatgpt Chat for others. And then they released Claude code. And I, you know, um, we're. We're finance guys. We don't code. But I was like, I wonder what this is? And I looked into it and I saw that the workspace was your folders, and what it did for you was create files or edit files. And that was like, that's exactly what I do. I work inside file folders and I go and I edit Excel files and PowerPoints. So when I saw that I kind of leaned into the cloud. I was like, oh, they're leaning towards this worker audience. It's not chat where I'm, um, just going and asking for a formula for, like, power query going in there, and it's doing work for me. So I leaned in then. And then they, they really convinced me. They just kept releasing things cloud in Excel, Cloud and Word Cowork. So they're all just leaning towards helping you do work better. So, yeah, it's work helping me do work better.

Paul Barnhurst: So Claude code was kind of really the first one that you saw because it had that workspace and it could work on files and said, there must be something here. How can I use it?

David Dors: Exactly. And, uh, I just. I knew AI was like, working for engineers. How can I make it work for finance?

Paul Barnhurst: Yeah, there's a lot we can learn. I interviewed a guest who said, look, engineers, developers are 18 months ahead of us. Learn how they're using Cloud, Claude and copy a lot of what? Or, uh, whatever tool. But learn how they're using AI and copy a lot of it.

David Dors: Yeah, yeah, exactly that. And they're, they're a little more blessed than us. They have really great version control, which we don't have in Excel, which I'm very jealous of, using those tools, like, dang, I wish Excel would do that. We can collaborate so easily across engineers.

Paul Barnhurst: But it's funny, I was talking to somebody that's building a, uh, a software where one of the things they're talking about is we're trying to manage the version control, you know, and they still output stuff to Excel is an interesting approach with using AI. And so I, I Think we'll see more and more solutions to get better and better on that front. And so it'll be fascinating to watch. You know, there's, there's some modern spreadsheets that do some of these things really, really well. But as I've always said, you're competing against the 800 pound gorilla. And the most complete software in the world as far as spreadsheets go, is Excel. And there's not a, in my mind, there's probably not a close second. Of all the different things it can do, Google sheets can do 90%, it can do some things way better. It's probably the next closest. But you know, they just have invested so much in the whole Microsoft ecosystem. It's a really hard disconnect.

David Dors: Yeah, it's been where we've worked like everything we do, it's, if the software we have can't do something, we reach for Excel. So it's hard to beat that.

Paul Barnhurst: It's a fabulous tool. I mean, I love Excel and AI hasn't changed that. I can see areas where it's changing, how we work with it, when we should work with it for sure. And I continue to see that. But you know, There's a reason ChatGPT, Claude and Copilot all have add ins to Excel.

David Dors: Exactly. They know they can't compete, but they're like, how do we make this better, make the experience better? Which I like.

Paul Barnhurst: Correct. Plus they're getting all that data, which maybe at some point they do compete with that, but for now they recognize of having all that information and building something that works well with them is a great way to go. All right, so I know you've, you've started your own business now you're doing training for finance teams. Why is this so important? Why, why did you see that was a need and that you felt, hey, I'm going to leave my steady day job to start training people.

David Dors: Yeah, I think it was just that aha, uh, moment I had. I want everyone in finance to feel that and I feel like once you get there, it just doesn't stop. I have a lot of friends that use these tools now. You know, they use cowork or code every day and I'll ask them, like, what problems do you have now that you're using this and it's basically gone away? They're like, I, I don't have any problems, I just go and I build my own solutions to problems. And you're not looking for software to solve these problems now. You can just, you have kind of the Whole world open to you outside of Excel now. So that's why I've been focused on the training of just how do we get people to that aha moment as quick as possible and just not. It is confusing the technology. There's a lot of different things where you start talking about skills and MCPs and projects. You, if you don't know what any of that is, it's like, um, I'm learning to be a software engineer or something. But once you get in and just start using it for your actual work, and you can see how it starts saving you time and lets you focus on different things that you much rather spend your time doing, it's a. It's a great tool and I think more and more finance will start using this as a platform where they go and do work.

Paul Barnhurst: Let's break down kind of the different things in a simplistic term, how you would describe them. I think this is interesting. So let's start with. We have Claude, where I can just go to the browser and open it up. So I'll call that kind of Claude Chat, right? We have Claude cowork, We have Claude code. We can download it to our desktop, we can download it to our phone. Now we have a Claude design. So let's start there. Mean, what's kind of the difference? How should people be thinking about this whole ecosystem almost this operating system kind of, so to speak, that Claude's built? How do you think about it?

David Dors: I don't reach for chat too often now just because of everything I've built for myself and the other tools. But Chat, I feel like, is just the same thing. We've been kind of using it forward. Quick questions like I want help with a formula or I just want some quick information. That's how I've been using it. And I feel like once you get into coworker code and you start building out like your own personal operating system, there, that's where you stop using the chat tools and you switch to either coworker code. They're very similar tools. I prefer code just because that's what I've been using. But Cowork just has kind of the nice UI in front of it. So just it looks pretty. It's like what we're used to using. And when you get into these tools, you're basically building connections to all the data sources that you already use, whether that's your erp, a, uh, data warehouse, even your email. And then you can have Cowork do the work you would normally do, whether that's analyzing data, cleaning, uh, it up, transformation. And you can build out what they call skills, which is just. They're all markdown files, which is just very much a. It's a text file that explains your workflow to Claude. If you do something a specific way every time, you turn that into a skill. And then Cloud can go and do that every single time.

Paul Barnhurst: Right. So I want to break that down a little further. So we've talked about kind of code chat. I mean, chat is really where you go, ask questions. If you're doing the serious work, it's do I want, uh, to try to do it in cowork or code? But also, isn't Cowork also designed where it will access your computer and do tasks for you? Does code do that as well?

David Dors: Yeah, exactly. So code can do that as well. Code actually opens in the terminal, which is fancy engineering. It's not that scary once you get used to it. It takes, like, a few minutes. Uh, the. I watched a YouTube video on how to get in there. Um, but all it does is it opens inside one of your folders, so it can create a file. It can create an Excel file for you. It could write code for you. And that happens all on your computer. So both of them are using your computer.

Paul Barnhurst: So both of them could do that. Like, it could go to a website. It could open up an application if needed, in code. Just want to make it clear for the audience that you could. Pretty much Almost anything you can do in Cowork, you can do in code. Code, uh, also has kind of the whole code side of it.

David Dors: Code has more features that some things that haven't come to Cowork yet. Code actually does a little better still with things like memory, where it'll start to remember your workflows or your preferences, and it'll store that memory. So next time you go and do it, it remembers.

Paul Barnhurst: All right, so now let's talk. So we have these three. The next thing you mentioned is skills, which you said markdown files. Way to think of them. The way I describe them is instructions. Right. So you're giving it instructions. It really provides a purpose for good documentation, because that's usually something everybody was terrible at. Now you want to document it, because if you document it well, you can give that to AI. So how does someone get started with the skill? Because it feels like I got to give it all this instruction. Isn't it a lot of work to write all the documentation?

David Dors: Yeah, it does take some time. Once you do your first one, you'll start to understand the patterns of. You're not trying to give it step by step instructions, you're really trying to give it the, the tools it needs to go and do work that you would do yourself. So if something you're doing constantly is exporting a specific report, you can give it access to that report and tell it how to, how to actually go and pick the right time frame or the right settings so it brings that report back accurately. So, so yeah, it is like instructions, but also you're just giving it the, the how, how it's done and some of the why of what we're doing. And that lets it act uh, more autonomously and get, get through and give you, it surprises you with. Once you start giving it different tools to access, it can really go and find creative solutions to problems you didn't even know you had.

Paul Barnhurst: Okay, so we have these skills. We have the markdown files. You give it context, you give it why, you give it some instruction, but not necessarily a step by step give it that freedom. How big of a difference does it make using a skill versus not using one? When you're doing something in clouds, I could give it a prompt, ask it to do the same thing. Are you finding it's really a key difference?

David Dors: Yeah, uh, where skills really start to help is when you're doing something every day, every week or every month and so you're not constantly re explaining the same prompt, you're giving it all this context that it needs to do the work correctly and you can put it inside the skill. And the skill is not always just the uh, markdown file like we talked about. You can give it examples, you can give it assets, things to go and see how we did this previously and it can go and rebuild it exactly the way we did it before. So like something like management reporting, if we're always using the same format, we don't want to change the format, we don't want to change it. We give it as a asset or reference for it to go back and recreate that exactly the model after it. Yeah, exactly. So you always get the same output.

Paul Barnhurst: Makes a lot of sense. I'm curious, how much time do you think you're saving on average a week. Let's talk kind of work wise. What were you saving from Claude and then maybe also in your personal life?

David Dors: Yeah, no work wise. Honestly, it's so hard to say because every time you cut something out, you always find something that fills it. So you start cutting some of the repetitive work that doesn't really require my judgment. It's like pulling data when we're cleaning it the same way. Reformatting that can cut 5, 10 hours every month on just one process that you do every month. But something always finds the way to fill in that time gap, and I'm not working any less. So it's like you start working towards things you like to do more and things that find that you find more interesting.

Paul Barnhurst: Yeah, so it's, it's basically allowing you to focus more on what you want versus, oh, now I work six hours a day.

David Dors: Yeah, it does let you focus. That's one of the things that I found really helpful is instead of switching between all these tabs, you're going between Excel and different browsers and email. I can kind of work in one workspace and that helps me just focus on what needs to get done and I start delegating the other work to agents that, uh, go and work for me.

Paul Barnhurst: Okay, got it. Next, you. Recently you did, I think it was a post on LinkedIn you shared that Claude is the way you see it. It's not really a software you deploy. You shouldn't think of it as a software, but you should think of it as someone you onboard as a new hire. Talk to that, Talk to why you think about it that way. And what's the difference when you treat it like a new hire versus a software?

David Dors: Yeah. So when you go and use Claude, you don't have just one. You might have a, a different one for each workflow you do. It could be one for data analysis.

Paul Barnhurst: And when you say one, are you saying one project, one skill? What do you mean by one?

David Dors: Yeah, so the way I think about agents or Cowork is the folder is the agent. So I will have a different folder for different types of work.

Paul Barnhurst: Got it.

David Dors: And inside that folder, I have different skills that are specifically tuned to what the work I do inside that folder. And it might have different data access inside those folders.

Paul Barnhurst: And do you have to also load those skills into Claude? So do you just keep them in case you need to change them in the folder, but they're also loaded into Claude or how's that work?

David Dors: Yeah, so. So I use Claude code, so most of everything I have is saved locally on my computer. But inside Cowork, you can save them to the Cowork app. And so now they're saved in the cloud and so you can get them wherever you need them, which is really nice. But yeah, when, when you talk about like you're onboarding an agent, it's. Each one needs different contacts, different instructions, different data access. What we talked about with like skills and connectors and they get better over time where software, you set it up, you train people and it works the same way basically forever. There might be some updates but it's basically the same. But with your agent, they're constantly improving like we already talked about. They're releasing all these features every day and you constantly have to work and re update these agents, make sure they work correctly still. And when you're no longer managing one agent, you're managing ten. It's a uh, completely different structure and it's, they still need the same things a team needs where it's like a clear scope, good data, uh, uh, the right authority and somebody to actually own these outputs. So that's why I think it's more of building this environment for a team of agents to go work in instead of just a software that you, you turn on one day.

Paul Barnhurst: Got it. And I mean so from the new hire perspective it sounds like it's really about giving it the context and training it. That's kind of a similarity.

David Dors: Yeah, exactly. You're, you're teaching it your business model, the, the quirks about your business, why something gets done a certain way and what you would learn when you're starting in a role. Your job is just now to teach Claude the same things that uh, you learned when you, when you onboarded and when you took on different responsibilities.

Paul Barnhurst: So, so what is the low hanging fruit that you think FP and A people shouldn't be doing anymore because of AI? Whether it's Claude, ChatGPT, Copilot, what's one or two low hanging fruit that you would say? Hey, if you're doing it this way, you should be rethinking how you're doing it.

David Dors: Definitely around accessing data where the way we currently access data is like you go into your ERP and you click export a report and then you go and you configure it and you say I'm doing this time period. But your agent can just go and get all that data for you without going through uh, a UI and taking all that time. It just goes and it runs a uh, connection that gets that data right back for you. So just those, those things like that where they might take 5, 10 minutes but over the course of a month, a year, it adds up to hundreds of hours where why am I doing this work if it doesn't require my judgment? I'm just exporting the same report every time. Uh, I think it should go to agents Got it.

Paul Barnhurst: So the first area, the lowest hanging fruit is exporting data. The manual exporting.

David Dors: Yeah. Just giving it access there. Then a lot of the transformation work we do is it's the same every month. If we're doing the same calculations, that logic doesn't change. That can go to your agent next and you're just rebuilding your workflows. Boom. But in a way that an agent can do them.

Paul Barnhurst: Got it. And, uh, if somebody's listening to the show and they're trying to figure out where to start, do they start with some cloud training? Do they start with trying to automate something? From your opinion, where would you recommend they start? This is somebody. Let's assume they've done sha, they've done prompting in AI, but they haven't automated any processes. They haven't built an agent, they don't know what a skill is. They've heard the terms, but they haven't done anything. What should, what would be, would you recommend? Is that place to start?

David Dors: Yeah. When I, when I think about it, for a team, like a team of analysts or a finance team, I think it should start before the tool, before you even get into claude. Just making sure everybody has access or any sort of friction they've before actually going and getting to that aha moment I was talking about is going to stop people from using it. So if they don't know what data they can use in there or what CLAUDE can actually access, I would start there and make sure everything's explicit. Where everybody knows what they can and cannot do with it. That really just helps for, you know, once you go in there and you start using the tool, if you have access to everything you need and it can do the work, you can, you can go and build the solutions, your, your own way, whatever way you see fit. Um, but it's really about having that, the access in the beginning and just figuring out that governance layer.

Paul Barnhurst: What are the challenges? You know, we hear a lot about, hey, AI hallucinates, it doesn't do things the same. What are the things you need to be watching for? Because I'm assuming whether you have an agent doing it, whether you're prompting throughout, you know, working with it, and it's a back and forth process. There needs to be this human in the loop. So how do you think about all that? What are the things people should be watching for? Because you know. Right. Just like a human, we know this can make mistakes.

David Dors: Yeah. So we want to have our processes be as deterministic as possible before they get to the agent if the data can be made up by AI, then everything after that's going to be terrible. So making sure we have access to data that is deterministic and it's going to be accurate 100% of the time, that should be your baseline. And then now once you're going in and doing the actual work and transforming data for finance, we will almost always need a human in the loop to go and validate those outputs. But it's giving AI a way to actually check its work and make sure it actually is accurate. Just like how we do with checks like checksums. And you're always validating all the data. You want to give agents the same tools. You have to make sure we can go and check and make sure everything we did is accurate. Everything ties, everything checks out. So giving agents a way to go and evaluate, evaluate their work is a really good way for you to not be fixing a lot of small problems and you're fixing more root cause problems instead of little one offs.

Paul Barnhurst: And elaborate on that. Is that something in the instructions? Is that reference sheets? Is that giving them access to another tool where they're supposed to check the number? What, what do you mean by that? So like I built my agent, I run it and the numbers come back, let's just say quite a bit off. How do I get it to check most of it itself? Is it, you know, writing in your instructions, check two or three times specifically look at these areas, giving it access to other data. What are some of those things that reduce that variability in the errors beyond, hey, I gave it a skill, I gave it the data, I gave it

David Dors: an example with like, say we go and we have it build Excel report for us. So just having it build in the same checks we would use, you know, where we can go and make sure all the data ties out to the different source data and giving them the checks we can do at the skill level where we're giving it the checks that we would normally do when we go and look over and review our work and telling it, hey, go through and uh, make sure you, you validate these three things. Or there's also the option of having more of a uh, review agent where there's another agent that reviews work specifically. And so you have one agent that does work, another one that reviews it all before it comes to you.

Paul Barnhurst: So let's walk through an example we talked about. Let's take reporting you mentioned we need to reduce frictions, you know, making sure you have access to everything, you understand the tools and then you also talk about, hey, you're going to need to write the skill. But I would imagine another key area here is process. You need to be able to document, outline what that process should work like. So let's walk through kind of how all of that looks. So we're going to automate our monthly P and L reporting as an example, kind of the process and all that. Walk me through that.

David Dors: Yeah. So the first thing I would do is figure out what your actual process is, because we know the process we go through every month and do. But it's a lot different when you start and try and explain this to an agent. Build the skill, build the tools that can go and do this for us. So I would definitely go and use one of these dictation tools where you can use voice and just go and talk to Cloud for a bit and explain your process, tell it what the inputs are, what transformations you do, and then what the outputs are and what they should look like. And that really gives us a good starting point to go and start building these automations. And then once you have that mapped out, you can kind of see where biggest bottlenecks are, what takes you the most time. Sometimes it could be really easy to go and pull the data yourself. It might take you a minute. Uh, but what really takes a lot of time is the formatting and getting everything into PowerPoint, DAX and. And so that might be the process you want to start with first. And so building out the skills that your agent would need, everything they would need to do to do it the same way you would do. And we can create that as a skill, give it our processes, give it access to the data sources it needs, and it can go and do the transformations for us if we need, or it can go and do the formatting and building out the reports.

Paul Barnhurst: Got it. No, that, that's helpful, thank you. Um, what's the coolest thing? Talk more personal life you've built with Claude code, Something you vibe coded.

David Dors: Oh, something I vibe coded or just

Paul Barnhurst: a process you've done? My last guy, I'll give example. Yeah. He goes, the only area my wife and I ever argue over is what mill we're gonna do. So they use Claude. He goes, I never want to do a meal plan again in my life. And it built an app that helps them do all their meal planning, used an open source and he built it all. And so, I mean, it could be totally different, but that's an example of kind of a fun one I had. He's like, now we just use the tool to Figure out what our meal plan is based on, what we have, what's easy to get, what will be healthy, and we. Away we go.

David Dors: Yeah, no, I've, I did that where I Vibe coded a Apple app actually on my phone where I like to track if I have any habits I like to do like working out every day or you know, eating. Eating good foods and you know, not sticking to my habits. So I had it Vibe code an app for me that was like, uh, I kind of tried to gamify it where it was every time. Every time I did my habit, I'd log in in the app and it would like level me up. I started getting experience and my little guy started getting like, uh, higher levels. You know, he was getting better.

Paul Barnhurst: How did he get buffer as he went like stronger?

David Dors: Yeah, so that was one that I did. And I've never used, like, I forget what the software is, but it, it used the software for me inside to create a Apple, uh, app. And I've never done anything like that. So that was really awesome that I'm able to do that. And now it's on my, my phone.

Paul Barnhurst: That's cool. Yeah. I'm hearing just amazing stories of what people are doing. You know, if you didn't see it, you'd think we live in a sci fi world sometimes with the stuff people are able to do. All right, so I want to ask this. What's FPA going to look like in five years?

David Dors: Man, it's so. It's so hard to even know what, two years.

Paul Barnhurst: And I know we're guessing. I mean, uh, you're right. I'm coming back to you and we're going to Vegas.

David Dors: Yeah, exactly. The way I see it is everybody's going to be managing a team of their own agents. So everybody's going to move up a level. If we're the analyst now, we're the analyst that manages 10 other agents that did the work we used to do. So when you're talking about how are we going to train the next generation, it's going to be really tough. When agents are going to handle a lot of the work we do today, it's really, really going to change just the way a lot of businesses operate. If you've already seen like there was somebody that had a billion dollar business and it was just him and his brother and they ran the whole business using AI agents. So the way FPA is going to change, I, uh, think we're going to be embedded into a lot of different processes, helping make decision decisions across the Business where agents are going to handle a lot of the, the standard reporting. We do building forecasts and we'll be off trying to help the business.

Paul Barnhurst: Got it. All right. If you had to go back before Gen AI, what's the one thing you just couldn't do anymore? You couldn't go back to the way it was before.

David Dors: It's really just uh, the work that I already hated doing. When you're doing the same thing every single month for years and it's like nothing changes about it. It's you do the same exact process, I would never want to go back to that. Right. I didn't know how to automate some of this work and I was just doing the same thing every month.

Paul Barnhurst: Fair enough. So it's really the repetitive tasks, you just couldn't do that again.

David Dors: Yeah, exactly. The things where I wasn't adding any value, I was just doing the same thing every single time.

Paul Barnhurst: Um, that's my career. I don't know if I ever added value.

David Dors: Yeah, you did.

Paul Barnhurst: I couldn't admit that.

David Dors: I think everybody learns so much from this. Just being able to hear other people's experiences and it gives them ideas on what they can go and do.

Paul Barnhurst: Uh, that's one of the reasons I'm so excited about doing the AI series. There'll be a few other episodes intermixed, but you're the fourth person I've done a heavy, hey, how are you using AI? Walk me through things, let's talk about examples. And I'm learning a lot. I, I'm already thinking I need to do this and I need to do that and it's, it's exciting. So I'm hoping others get the same out of it in their day to day work. I really think spending the, you know, 10 hours, let's say I do 10 episodes, probably even five hours. Listen to at ah, double speed. You'll get some great ideas. But the key is as you know you have to do listen watching YouTube, you can do that all you want but you just have to jump in. That's the thing I'm realizing more and more and I've started to build a couple skills. I started playing with it a little bit and I know I just need to jump in more. It's just as simple as that.

David Dors: Once you dive in, there's no going back.

Paul Barnhurst: And I'm starting to realize that more and more as I like. I'll give an example. I'm building a deck. I'm doing a keynote speech for an event and I've probably spent three, four hours in PowerPoint. Okay, I've got this section done. Here's what I'm trying to accomplish. Give me ideas, tell me how I'm thinking about. Uh, and sometimes I'll have it redo the slide. I may still edit. I'll edit them after. And I know I always like the look and feel and everything isn't quite like I want. But it's incredible how much I can use it as a thought partner. Ignoring the agents, ignoring the automation. Just the thought partner part to augment what you're doing is incredible. Then you add all the efficiency gains if you go which is where I need to go that next step. And how do I automate my workflow flows? Like we have a CFO on who said I look at A as my thought leader. It's kind of a lonely position. There's not many people I can go have certain discussions with in the company, but I can go use AI as my thought partner. And so it's just so versatile, you know, kind of like you could do anything in Excel. There's a similar with AI, it's kind of that new world if there's the tool that is going to be as ubiquitous. Right. It's Gen AI. Whether it's Claude or Chat, GPT or Copilot, we'll see which one it is. Everybody has opinions. I have mine. But I think you're kind of looking at that like, you know, the modern day and it more powerful, costs more areas, but kind of spreadsheet in some ways. Well, if that makes sense. But that's kind of a little bit of how I think of it.

David Dors: No. Yeah, the options are unlimited. You can go build whatever you want to build now. You're. You're not forced into what somebody else wants to build for you. And fitting cleanly into what they built.

Paul Barnhurst: Pretty wild.

David Dors: Is. Yeah. Customize as you want it to be.

Paul Barnhurst: Yeah. I have so many things I, I need a. I need a three months off to just be a AI person anyway. All right, what's the number one technical skill that FPA professionals should master today?

David Dors: I don't think it's Excel anymore, but I think it's understanding what Excel does for you. Like the operations underneath, like what happens when you do a, uh, lookup or when it creates a pivot table. Because AI can do so much for you now where if you can direct it at the most base level of what it's doing. We're cutting out these UIs. We're not going in and going through our ERP's nice screen. And clicking. Download P and L for January. AI, ah, can do that for us. And it can do all the transformations that we want it to do, as long as we understand what it actually needs to do. Not how to do it in Excel, but how do you do it, uh, at the most base level.

Paul Barnhurst: Got it. All right. What's the number one soft skill we should master?

David Dors: I think clear writing. Because. And growing up. Yeah. You were here in Arizona, our schools, they teach us how to write these long essays. You're always trying to hit some character limit, get past a certain amount of words. You're stuffing it with unnecessary words. And then you get into finance, and nobody cares that you know how to use all these nice words. They just want to know, what decision do I need to make? How do I make it?

Paul Barnhurst: Just be clear, be simple, concise, communication, written verbal, whatever it might be.

David Dors: Yeah. I really wish schools would focus on that side of writing more because I feel like you don't get that all.

Paul Barnhurst: Uh, Right. I know you've used Excel a lot. What Excel mistake taught you the most in your career?

David Dors: Trying to make the most. The crazy nested lookups, index matches that have all these dependencies and that you never know when something breaks. I would try and fit everything into one formula just because I could. And then I realized, like, I don't even know what's going on in here. And when something, when you send something out that's just completely off because of a formula, you feel so stupid. And you're just like, why did I do it this way? Break it out cleanly. Show all the steps.

Paul Barnhurst: And I had a guest once who, uh, said, open your model a week after you built it. If you don't understand the formulas, it's too complicated. Right. And I've opened files. I'm like, what was I doing here? And you have to pick it apart. That's a sign that you did a poor job. And we all do it because at the end of the day, design, design, design, design is critical to Excel.

David Dors: Yeah. That's why I love Power Query so much. Where you could. You really just listed out all your steps. And now going to using AI so much where it doesn't really work well with Power Query, you're, you're, you're back to the basics. So that's what I've been trying to relearn.

Paul Barnhurst: Yeah. They'll figure out how to make it easy, bring AI into the Power Query interface at some point, or they'll figure some other olution, but it's cra crazy world. All right, this is the get to know you section as we wrap up. If I asked you where you would go, if you could go anywhere in the world tomorrow for a vacation, to go see a place you haven't been or maybe even somewhere you've been. Where are you going?

David Dors: I'm going to Japan.

Paul Barnhurst: Why?

David Dors: I think the food is amazing. Uh, everything I've had over here, at least that's Japanese. I think their country is beautiful. The, the culture is just amazing. They always, they get so obsessed with different things. And I, uh, love how obsessed they are about mastering one thing. And, um, if you ever read Shoe Dog from Phil Knight, who was the.

Paul Barnhurst: Of course. Yeah, yeah, yeah, yeah, from Phil Knight.

David Dors: He's the founder of Nike. He just had this, like, life changing experience when he went to Japan, so going in October.

Paul Barnhurst: Awesome. Well, let me know how it goes. Excited for you. All right. You get to spend one day, one day only, with any person in the world. So somebody alive. Who are you spending the day with? And obviously outside of me, of course.

David Dors: All right, uh, now I gotta think about it. My first option's gone.

Paul Barnhurst: Yeah, whatever.

David Dors: If I can do two, a little combo. My wife and son, I already spend every day with them, but.

Paul Barnhurst: Smart answer. If she listens, she'll like it. And I know it's legit, I get it, but.

David Dors: No, it really is legit. Uh, they just, they're, they're why I do everything. So just another day with them. I'll take it. I'll take every day I can with them.

Paul Barnhurst: Love it. All right. If someone wants to learn more about the services you offer, this is your, uh, time to kind of plug what you're doing as far as services, share a little bit about that and how they can contact you.

David Dors: Yeah. So LinkedIn is probably the best way to reach out to me. David Dorse. I, uh, share a bunch of information on cloud, how to set it up for your finance team, Host a lot of workshops where we go in and we, we build with cloud cowork or cloud code. And then I have a lot of longer, like, how to articles on how to get this set up. So if you're. You're building anything cool with cloud or in finance, just message me on LinkedIn and, uh, I want to know what you're building.

Paul Barnhurst: All right, awesome. Well, thank you so much for joining me, Dave. I appreciate it. I hope you enjoy the rest of your day and excited for the audience to get to listen to this. So thank you for coming on the show.

David Dors: Thanks, Paul. It was. It was great to be here and it was great conversation about where we're going with finance.

Paul Barnhurst: Yeah, it's an exciting time. So I'll. I'll leave with this party words. If you're not using AI, just get on the boat. Just start. Even if it's simple, I can't say by any means. I'm an expert. I'm behind a lot of people, but I'm continuing to jump in. And that's all you can do.

David Dors: You just got to get in there and start using it.

Paul Barnhurst: All righty. Well, that's a wrap. Thank you, everyone. That's it for Today's episode of FP&A Unlocked. If you enjoy FP&A Unlocked, please take a moment to leave a five star rating and review. It's the best way to support the FP and A guy and and help more FP and A professionals discover the show. Remember, you can earn CPE credit for this episode by visiting earmarkcpe.com, downloading the app and completing the quiz. If you need continuing education credits for the FPAC certification, complete the quiz and reach out to me directly. Thanks for listening. I'm Paul Barnhurst, the FP and A Guy, and I'll see you next time.