Full Transcript for The New CFO: How AI Is Rewriting the Finance Function | Figma CFO Praveer Melwani
People
Get the key moments without reading the whole transcript
Each note is the main page for that topic.
- Why Does Figma's CFO Check Data Every Day?6:54
- How Does Figma Rehearse Investment Memos With AI?13:06
- Who Should Take a Finance AI Prototype Into Production?22:33
- Why Does Accounting Help Figma Data Scientists?25:22
- What Does Figma's CFO Pitch to New Recruits?31:34
- How Do AI Agents Speed Up Finance Research?35:44
- Why Does Figma's CFO Still Use Excel?40:31
Full transcript
I think we're gonna be able to attract and build the world's best finance organization because so much what people want is the ability to learn and feel like they're being invested in and surrounded by people that wanna go and become the best at their craft. We'd love to hear a little bit about what made someone a great hire on your team, a great person.
I want folks that feel extremely intellectually curious. You're coming in and trying to solve and try to understand the business really well. You want to use AI as a tool to help you and empower you, but it's really, really critical to still be that thinker. We're in the era right now where a lot of slop is being called out. I've heard one CFO talk about how using AI just led to unlimited amount of docs that are being created every day.
Anything that you're putting out there that you're asking someone to consume, it's gonna take them time, effort, and energy. 95% of the challenge there is just getting your data in the right spot. What do we think changes in the next 12 to 18 months? If our business complexity was staying the same, I think we probably wouldn't need the same number of people a year from now.
For decades, finance teams spent enormous amounts of time figuring out what already happened. AI is starting to give them more time to decide what should happen next. In this episode, A16Z partners Seema Ambal and Ivan Makarov sit down with Figma CFO Praveer Malani to talk about what an AI-native finance organization actually looks like. Praveer joined Figma in 2017 as its first business operations hire, years before becoming CFO and helping take the company public.
Back then, automation meant writing hundreds of lines of SQL, waiting for queries to run, and stitching financial and product data together by hand. Today, his team is building very differently. Collections workflows are automated, corporate finance can reconcile messy data across multiple systems and minutes, and the corp dev team can use AI to prototype an acquisition target's product and run investment demos against simulated versions of Figma's own leadership team before presenting them.
But Praveer argues the real shift isn't simply about doing the old work faster. It's about changing what finance people spend their time doing in the first place and turning the CFO organization from what he calls a traffic cop into a business enabler. They also discuss what should never be outsourced to AI, why Excel isn't going anywhere yet, and what founders should actually look for in the next generation of CFOs.
Welcome to the A16C podcast. I'm Seema Ambul. I'm joined here by my partner, Ivan Makarov. We recently wrote a piece called You Need a New CFO. Our argument was that AI takes finance to the next level and the CFO's job which increasingly includes building and automation and really designing the systems and the team to do that. Today, we're joined by Praveer Malwani, who's the CFO at Figma.
And we'd love to explore what you have seen over the course of your career and what you and your team are doing now. Praveer, thanks for joining us. Yeah, thanks for having me. Excited. Maybe to kick things off, both Yvonne and Praveer, we'd love to hear a little bit over the course of both of your careers, how automation has changed the role in finance and what the team does.
You know, I've always felt like the role of a finance individual should be this operational leader. And when I joined Figma, none of the automation pieces were in place at all. And I felt like in order for me to be effective at the time that I joined, a lot of my work needed to be living in SQL, building the data tables, really understanding how I could orchestrate the financial information effectively.
to drive the conversations I want to then have across the company. And I continue to kind of go back to that initial days that I had in that seat and what I was doing as the force multiplier, the piece that actually gave me the ability to have the scaled impact across the organization. And if anything, I think what I was building way back then is that much more possible and plausible and accessible to individuals by the tools available to them today.
I hope that more and more folks feel like they can be empowered to take that operational sort of lens to the way that they actually go and position and work with their counterparts across the business. Because I do think that's the magic of shifting this role from what can be viewed as like a traffic cop sort of finance-y type function to one that's a business enabler and a true change agent within the organization.
And to double click on what you were using for automation, maybe pre-AI, maybe explain to people what exactly you were doing. Was it macros in Excel? Was it using OCR for documents? Yeah, honestly, it was like everything under the sun. So like it started like living in SQL, looking at all of our product metric and utilization data, mapping it to all the financial information we had in Stripe.
I'd go and create these four or 500 lines of SQL data. that I'd want to then use to create the golden tables that I'd go and pass off to someone or then be able to pass to different go-to-market systems that we'd be using. So I felt I spent my day living in that query editor. And, of course, waiting for the query to run for however many hours.
Yeah, and you hope you got it right the first time. Exactly. And then we eventually hired data scientists and I'd go and tap them and say, hey, I have this thing I went and built. Can you go and add it to our ETL process? So it goes and there's a recurring job that I can then use that same information and pass it to Salesforce or Marketo or whatever systems that we were using at the time.
And that was like the initial sort of unlock for me of, oh my gosh, if I can get consistent in our definitions in the way that we're talking about things, no longer are we ever debating like what's true and what's fact. And we can just get past that and really focus on how are we actually going to go and drive the business. I was talking to someone who was in their early 20s who was complaining about how long a prompt takes to run.
And I was explaining to them, you have not lived the pain of hours on hours of waiting for a SQL query to run and then only to come back and be like, shit, it didn't totally work. And so, yeah, it is just an order of magnitude. Totally. Yeah. Yeah, the time is real interesting, right? Especially the era that we've lived through. When I was at Webflow at Figma, we saw, for example, a huge spike in usage in COVID that I could not believe in the beginning.
I know it's experienced it this way too, where I thought our data was broken or something else was broken, but it took us weeks to figure it out. And I feel like today, in this day and age, we live in a day where you could figure it out to an hour. It was some of the spikes, some of the usage revenue as well. This is a very different world we live in.
Did you experience that as well? I mean, yeah. I mean, our business took off during the early days of the pandemic. I think that was actually the time where we started to partner with the folks at Andreessen. It was like right at the early stages over there. But yeah, I mean, I wake up every day. I mean, I have the ability to go and rebuild my context on what's happening.
And then at any moment during the day, the team loves it when I'm... I don't know if they love it, but they know that I'm constantly in there going and taking a look at, you know, hourly dashboards or sort of daily metrics on things to make sure that I'm also sourcing things that I think maybe look like anomalies or asking the right questions.
And I think they view me similarly to how they view their role within the organization as, you know, a counterpart who has ideas, who wants to come to them and truly build the best business possible, all using and having access to the same data available to each other. Yeah, what's interesting, like when you and I went to college around that time, that was more of a monthly or quarterly cadence.
Main page at 6:54
And then it became a weekly cadence. I remember maybe, especially with data moving more into the cloud, it became like, let's have a big weekly dashboard to where now what's possible is daily. Has that changed your habits, the way you even just look at, think about data, how often you think about it all? Honestly, I view data and having access to it as the key unlock to how I can run my day effectively.
And so throughout my time at Figma, it was the thing that I would wake up every day and I remember there would be like 30 people that would sign up for a paid plan in those first few days when I joined and I'd go through line by line, who are they? Are they personal addresses? Are they business addresses? Are they people that we can reach out to? What can I learn from this to help us inform what we eventually built, which is our organization's product? And I think early days, it's extremely important.
And then now I just understand the repercussions of movement in any one direction. And if you catch something before it becomes a big deal, it can actually save the business. Like hundreds, thousands of dollars. But if you catch it in the other direction, you can really put more juice behind it and really seek to unlock in the other way. So if anything, like I view this as like a daily, if not more than that rhythm.
And I think the goal for me is how do I empower other folks on my team and across the business to similarly feel the accountability to those same metrics and truly act as business owners and want to go and triage things and not say like, hey, I can wait till next week. Like you do need to solve it sooner rather than later, because I do think the rhythms here are moving really rapidly.
And before we get into what you've automated, we'd love to hear a little bit about what made someone a great hire on your team, a great person in the leadership role, maybe pre-AI. I think, I mean, honestly, a lot of similar things today, but I think that you'd apply them slightly differently. I want folks that feel extremely intellectually curious.
You're coming in and trying to solve and try to understand the business really well and then seek to problem solve in a way that was trying to drive the right outcome. I don't think that necessarily has changed today. Like I still very much value that. I do think that you can make a lot of the tedious tasks or the repetitive nature of things feel like they take less and less of your time so that you can spend more and more of your time really trying to seek how you can find the places of magic within the business that you can go and supercharge.
So intellectual curiosity, fluency with data, ability to ask really solid questions, and then structure your thoughts in ways where you can actually make sense of the data that's being given back to you, and then thoughtfully communicate it on the other side of it. How do you interview for that? It's interesting. Right now I'm hiring for VP Finance and the case study part of the process for me is so, so sacred.
I want to both test for like, how are you using the tools available to you? So yes, I fully expect folks to, I don't give them a lot of information as part of this case study. We're a public company, so I get the benefit of a lot of data out there. But how you actually piece those puzzle pieces together in a way that actually makes sense, the model output makes sense, you have the ability not just to go and create that output, but you truly understand how it works.
So then I focused the case study conversation on have you really, really understood the structure that you've created? Have you molded it in a way where you've tested what are the highest, what are the pieces of that model that are the most sensitive to any change? Do you have a strong intuition on how the business is actually working using the tool that you've created? And then like we were just talking about, can you effectively communicate that? Because yes, I think anyone can go and create like a model sitting in pick your favorite LM.
You can go and do that really easily. But are you using it as an effective tool that like actually is enabling you to think? And I think you don't want to outsource your thinking today. Like I think you want to use AI as a tool to help you and empower you. But it's really, really critical to still be that thinker. Yeah, a lot of what you're describing applies to a good hire with or without AI.
I think if anything, AI just, you need more of the
accountability and thoroughness to know that the thinking is there behind it as you receive a work product. let's dive in a little bit on or to understand what you've automated and we can talk a little bit about what we've been seeing with reportedly companies um but maybe walk us through a couple of workflows at figma that you've automated and how did you decide what to focus on and what did you what did you do to automate them yeah i you know they're so broad and so i you know maybe i could pick a few that um to me have been fun to see i think um I think we've moved really quickly even over the last year to say, how do I go and try to coach people to embrace new tools
and new ways of working to now one where I feel like I'm constantly
being hit in the face with a lot of these really cool ideas. We do a segment at the company All Hands, All Hands is called Fig Nation, where we show folks how others have built with AI and consistently our team shows up as a team that's there. Um, so it's things with, you know, Kajal and our, our credit and collections team, he's gone and rebuilt, uh, his entire workflow, everything from invoice tracking, cash collections, making sure that we can reconcile everything to, to NetSuite.
And he's done it in a way where it's like a homegrown system where, you know, it's, it's tied to the various systems that we use. Um, it then has freed him up to say, okay, well I can go and continue to drive down my days receivable by folks focusing on the, on the things that really matter. Um, and then focusing on what are the other, um, sort of tedious tasks that I can go and build automation for.
And so he's then gone and say, well, I can go and like rebuild the way that I want to run our credit checks. And I can go and stitch together the data sets in interesting ways that allow me not to have to go and, you know, manually go into them. And it's a singular way where he can now go to anyone to say, hey, go and leverage the tools that I've created to go in and really drive and drive change there.
Um, on our, uh, on our corp dev team, it's, it's been really fun to see like how they, you know, both will, uh, you know, can you vibe code a product is one of the, one of the checks that we use in diligence now, um, which is actually really fun to see. Um, like how, how deep is your moat? How, how interesting is the technology there? And I think, you know, everyone should be able to try to recreate the product.
Wow. Okay. Yeah. And you can, I mean, I think our team's gotten really damn good at some of this. And so you can get through some of the, you know, is this a real thing? Is it not? Like, how difficult is it or not? And, you know, there's obviously nuances to a whole bunch of these ideas, but it gives you like a solid intuition there. And before, would you have had to go to the product team to do that part of the diligence? Yeah, I mean, we still partner with the product team, but you can take a lot more of like, hey, this is what I built, this is what I've seen, and it builds a lot of credibility there.
Main page at 13:06
I can do a pause on that. Those are some of the corp tech people, right? Not product people. Yeah. Their finance background, right? Yeah. Yeah, yeah, totally. And they were like a very document-oriented culture. So they write investment MMOs, they write, you
know, M&A MMOs, whatever it may be. And, you know, amongst them, the end readers or the folks that are digesting it are going to be folks on our leadership team or other product leaders. And, yeah. More often than not, there are themes, there are similar questions, there are ways that we all as leaders tend to have a way of looking at problems.
And what's been interesting is they've gone and created unique personalities for each of us as leaders
as, you know, a set of skills that they can go and run their investment memos by to actually improve the process. Do you have like an investment committee that exists, like the interaction between all of them through? Yeah, exactly. So that's exactly what they'll end up demoing. Or rather, they'll sit there kind of going back and forth and saying, okay, this is what Prevere would say.
And this is what Dylan would say. And this is what like, you know, Sean would say our CRO. And so you kind of get, you get, you get like the areas of the document that you either want to go and plus up, do more diligence on what are common sets of feedback that I need to go and make sure I ask the questions over. And then it reduces the cycle time that we're all sitting together on.
So, you know, I, And there's a lot of these areas where, you know, we're both feeling like it's, it's a tool that helps you augment, it's a tool that helps you go and replace workflow. And then it's this tool that helps you seek to understand and learn. And I, you know, I'm constantly surprised at like, how, you know, quickly we've been able to riff on things.
And, you know, for me, it's, it's actually put me in this really optimistic spot of saying, like, I'm going to, I think we're going to be able to attract and build the world's best finance organization, because So much what people want is the ability to learn and feel like they're being invested in and surrounded by people that want to go and become the best at their craft.
And as much as I can do to go and affect and enable that change, the better I think we're going to be able to go at retaining and growing and grooming that talent over time, too. And are all those tools, did you build those? right with the LLM directly? Or are you guys also looking at off-the-shelf AI tools that you can partner with? And would you rather build or buy? Yeah.
The ones I was describing, you know, it's a mix. Like, some of them folks were sitting in Codex. And, yeah, I think that's what the team is doing on the... on the corporate development team, they're sitting in Codex and trying to, you know, work their way through something. We've also seen folks like sitting within, you know, some of the workflow automation pieces and building skills around agency using ChatGPT.
And so that's, you know, how some of the credit and collections pieces were being built. And we also started to see folks being able to embrace it and build it on our tooling as well. So we, you know, we have a tool called Figma Make, which allows folks to be able to prompt through natural language and create, you know, an application, a website.
You can then host it. You have like a, you know, back end behind it. And so, you know, some of those instances are starting to crop up too. So I'm actually excited about that because then we can then we can ideally flip into this world where we can give product feedback as well, which, you know, I know everyone would love. I think we're in the era right now in the period in the cycle where a lot of slop is being called out.
There's been a lot of conversation to where we went from unlimited token to People are just calling it slop in meetings or I've heard one CFO talk about how using AI just led to unlimited amount of docs that are being created every day and you just can't find anything because everybody can write a doc now or 10 docs in a few minutes that it would take you a week or two.
Were there some of the areas where... And that naturally created also the conversation around hiring. Do you hire younger people that are more versed in these tools? Do you hire people more experienced than maybe both? Or do you hire more senior people that know what the world class looks like? And that's what worries me a little bit is that we will forget what the world class looked like.
Just like in the pre-AI era, you know what a really good model looks like, especially with some experience and having created models.
Where do you think this is going? Have you had to call slop? on some of the stuff that's being created right now with AI? Sometimes, yeah. I think, like, you know, I think we've also done a good job internally about building policies around, like, branding when you've written something with AI.
I think one of the things that's really important, I think I was sharing it earlier, you should not be outsourcing your thinking. Anything that you're putting out there that you're asking someone to consume, it's going to take them time, effort, and energy. And so I think you want to make sure that you put a similar bar to go and review, read, summarize, make it simple.
you can start in a different place. I'm totally cool with that. Um, but I do think it's on all of us to make sure that we're, you know, uh, being really thoughtful about how we, how we use each other's time, uh, as well. Um, so yeah, I mean, I've been in, I've been in instances where I, you know, things look a little bit half-baked and you really poke around and you're like, did you actually really understand what's going on over here? Um, but I've been also been in instances where I'm like, oh my gosh, like your speed of iteration here is like pretty damn incredible by virtue of how you set it up.
Like, A couple weeks ago, I was sitting in a, we're going through 27 planning, I was sitting in a T&E review. We're looking, you know, we're looking at our T&E portfolio and saying, okay, where do we have the opportunity to go and make changes to policy? Or maybe where are we not, like, upholding policy where we should? In our corporate finance team, they did a really good job about stitching together information that lived in different data sources or used Navon, we use Zip, we use Ramp.
And there's a lot of fuzzy match that you have to go through in order to like really get that information working, like with someone actually traveling for an offsite. What if they lived in San Francisco and were just visiting? Like, how do you actually want to go and like tag and treat that data? Like 95% of the challenge there is just like getting your data in the right spot.
And these models are good at making these assumptions for you. And I didn't need something 100% perfect. Um, I just wanted something that was directionally, you know, in the right, you know, in the similar vein from where I'm going, that gave me enough information to understand, you know, what are the areas I really needed to crank the dial on? Um, it was really interesting.
They both like outputted a set of suggested changes that we needed, we needed to, we could make. Um, I gave, I remember giving feedback that morning, 30 minutes later on like some of the construction of how I actually wanted things to look, look like, like It was all visualized for me when we got in the meeting. I was like, holy shit, this is like a really fantastic use case here.
And they did it in a way that like, you know, I don't think they would have been able to do it by hand. So, you know, as much of that slop, you know, I think can happen. I also think some magic can really get unlocked if you kind of like use the right tool for the right purpose and understand, you know, what is good enough and what needs to be like really, really picture perfect.
A couple of comments to that. I mean, a key unlock is the data, right? Now with AI, you can consume all these sources of data and quickly do the fuzzy match, get a directionally correct or precise, you know, reconciliation across these sources. Whereas before, right, you had to run the SQL query and you had to wait and then see it. And then essentially you had to be your own BI operator.
analyst on top of it. The second piece is there's this muscle that's being developed around the automation, right? And so even if there is slop, like, for example, I was talking to one of our growth stage CFOs who was saying that in, I think, a month or two, there have been you know, 40 or 50 agents created by their team, which obviously are not all being used, but it was getting everyone in this motion of, okay, if I don't, if I'm doing something manual or tedious, I don't have a great tool for it, let me build.
And so a lot of those, maybe 90%, I would guess, of those tools and agents are not being used anymore, but it got people to think, okay, instead of doing this manually, let me think automation first around it, which I think is almost as important as getting the like, the agent built. Yeah, I 100% agree with you. I also think like how you share it, how you get other people to understand what other people are building.
And then you end up in these scenarios where, you know, our internal audit team is like, they spend a ton of time going and like following up with individuals to make sure that they're adding information, you know, on the tickets that they needed so it could be trackable for our SOX audit. And then you're like, well, you know, that internal audit team is not the only team that does that.
You know, our GRC team is doing the same thing as they go through, like, all of our ISO and SOC 2 audits as well. You know, you have a bunch of this back and forth on the AP side when they're going and writing accruals. Like, you wanted to go and build this motion of going and triaging, pulling information in, reconciling it, and why not go and build a singular platform that does that? This is actually where I think, like, you know, a systems team is really, really interesting to come in and then harmonize some of the things that you see are happening, really productize it so that you don't have all these individuals going and building similar things.
That I think is like the evolution of what a CIO function should or could be. It's like, how do you go and you take a lot of these bottoms up things that people have crafted and you have it, you have it be rebuilt and repurposed in a way that can live on beyond the creator and the initial builder. So I, you know, I think that that that cross-org sharing.
We're doing some of it at our, you know, at our company All Hands, but we're also doing a lot of it internally across our teams. I was also talking to another one of our growth stage companies. The head of customer success was saying every one of his reps had a different dashboard that they had vibe coded and they had different numbers. Yeah.
And so I think to your point, there has to be some reconciling function, which is a great segue to hear from you guys around what are people doing in terms of the teams that should be building this and who's taking the agency? Is it someone initially builds an agent from your team and then you're taking it to
Main page at 22:33
an engineering team centrally? And we talked a lot about this idea of the finance engineer, which we didn't unpack further but we'd love to hear a little bit about yeah I think like you know I think we've always had I think having specialists come up with the ideas and iterate they know what good looks like they know what they want um they know the process that they're trying to make look right like they're fantastic at going at going about building these initial prototypes um But do I want that same individual to be the individual that has to go and make sure that they're checking for all upstream dependencies and making sure that like, you know, if they were ever to
leave that like this thing is hosted in the right way. And hey, does anyone else across the organization have the same need? Probably not. This is where I think like, you know, a world-class CIO org can come in and really show some magic here. Yeah, I'm really excited. We just had a new CIO join yesterday, a guy named Kasper Sorensen, who joined over from Coinbase.
And a lot of, like, what, you know, we talked about a lot in the interview process is, like, how do you create these, like, you know, centralized PM type functions within the CIO organization that can partner with the rest of the business teams, find the things that are really working and then build these like foundations that others can build on top of, which is not too dissimilar from like how a systems organization would have functioned otherwise.
But the pace that you can iterate on and then how you can empower others to build on top is what is changing right now. Is it centralized right now within the company? Do you see that changing? So as is all things at Figma, I think we've grown faster than we built the tools to support it. And it's on me to always empower the organization to build.
And then I don't want to slow people down by creating the infrastructure on top of it. And so I think we're chasing a little bit of that right now. I think with some teams, we've done a better job centralizing that. And with other teams, I think, you know, they built far quicker. And I think we're now having the process of saying, okay, well, how can we go and help? So I think we're in the messy middle right now.
I think that resonates with a lot of what we're hearing from our companies, whether it's a go-to-market engineer, a talent engineer, this concept of the finance engineer, it's a decentralized set of builders across teams. It could have different profiles. Sometimes it's someone who has an engineering background on finance who's good at kind of thinking about what workflows need to be automated.
Other times it's you borrowed someone from a product engineer from another team to go build. But, you know, I think everyone's in this messy middle right now in terms of what that profile of person looks like. A lot of it reminds me of data science teams and how they partner with other parts of the organization as well. And you as a data science partner are like, you know, the deeper you get into understanding the context of the team that you're working with, like the better I think you operate as an individual.
Main page at 25:22
So we've got data science individuals that are partnering with our product team. They build as much, if not more, product intuition than our product managers and engineers. And they're viewed as part of that core team that can go and help ideate and push change. And they're just leveraging a different tool in order to enable that. Similarly, we've got folks on the data science side that are supporting our finance organization.
It's actually really interesting. The folks that I think have been devoted there actually come from accounting backgrounds, a couple of them. And they understand that like, hey, this stuff has got to be like really, really hard and always correct. They understand the nuances that we're describing on like checks and balances. What is a refund? What is a, you know, uncollectible? All that kind of
nomenclature. And so it actually enables them to be better builders. And similarly, I could see that translate to like, you know, the finance engineer that you're describing. You have some shared understanding of what is necessary. You could build that context over time, but at least like you, it's important at least like build that major so that you can also go and push other people's frame of thinking as well.
Who owns the definitions? Like the reason why I asked this question, especially we see it in an early stage where it could be a team of 20 people and just founders and no finance or business people. And then eventually they bring in them on. But they're building definitions of key metrics that serve reporting, that serve investors and really business decisions.
And eventually finance gets hired and Where the definitions, how often would you, it feels like in the past we used to revisit them maybe every couple of years, where now, because you can access the code or you can access the Stripe logic much easier with AI, has that changed much? How often do you visit it? I mean... Yeah, my team owns the outputs there.
Maybe we're a little bit later than some of those earlier businesses. We have more controls in how we want to talk about it. It's always been really important to me to have consistency in how we talk about our business. It's one of the things that I felt has always been empowering, how I can show up with our board, with our leadership team, with other folks broadly, is that they know that what I'm putting out there is the same thing that I would have put out there a month ago, and the historical has never changed, and I'm not trying to hide anything.
Um, and I, um, you know, I, I would just want to make sure that, you know, as we grow and as we give ourselves the ability to iterate and, you know, we constantly have this conversation on different, different sets of disclosure as we go through earnings, we want to be consistent and we, we, we want to have the decisions that we make, um, be things that we can look back on and feel, um, uh, feel good about, um, and have longevity, uh, further beyond.
And so I, I, You know, I think it's great if people finding different ways to think about their business, if it's empowering them to go and build their business better. But I do think that there's some value in consistency as well. Who is it on your team that's automated the most? What role?
You know, I could say someone, but I'm assuming that someone else is probably coming up with something different really quickly. But, you know, very, very honestly, it's like all like individuals who are owning certain parts of our forecast model all the way through to, you know, individuals on our biz ops team that are automating their day to day sort of like, you know, how they're actually going and running, you know, you know, competitive benchmarking and pricing studies.
So it's like, I actually think that, you know, it's the one upping of each other that actually enables you to create an organization that wants to better one another. So, you know, I would feel uncomfortable saying there's one individual because I truly do think that this is like a team that's trying to do this together. Do you think it tends to be people who are more expert, like who have more expertise or experience in an area? Or is it really across the board? And how much is it coming from you and the role that you've automated yourself? Yeah, I mean, I think like early days, it was helpful for me to go and show folks like, hey, if I'm coming and trying to do things
in a different way, like, hey, that should be your signal to you that, you know, my expectation is that you are as well. Yeah.
But I think, you know, in large part, I think the things that are important is have a solid understanding of the data sets that you're trying to pull from. And the folks have been able to move more quickly, have like an understanding of like how these things are stitched together. And when you understand things and how they're architected, you can better think as like an architect of like, okay, how do I actually bridge these things in a way that's logical? Where do I know where the model is actually making a deterministic decision versus inferring? And what tasks, like, is it okay for that to happen? What tasks is it not okay? And I think then, you know, others kind of
pick up and learn from that. But, you know, I do think that, like, the rhythm that we've created, the show and tell rhythm, the, you know, the internal hackathons, this ability to bring in other experts, we do a lot of, like, conversations. I do a lot of conversations with other finance leaders and I try to bring in some of that intel internally so that it can get disseminated.
And I think my leaders are also doing that too, which is really cool to see. I think everyone right now is trying to learn from one another, which is really cool to see. Nice. Yeah, I feel like one of the common themes that are coming up in my conversations with CFOs or directors of finance or even just individual contributors is that they're finding it's really fun to be working again.
Because before it was like you're reconciling something for two weeks or three weeks and you're closing the books for two or three weeks. Yeah. And now it just feels like people are really turning their eyes towards the business and are able to surface insights, business, and all of that. There's just a lot of excitement around what's possible with AI, what's possible with vertical solutions.
One of the things I'm curious to go back on the verticals. buy scenario. I was talking to one of our hyper growth companies the other day and they said, we just have to buy everything off the shelf. We're moving so fast. Do you ever feel that way? Like maybe building is a longer path than just buying one of the solutions out there? I think for like the core systems of record solutions and like the things that like we just can't mess up, like, yes, we're going and buying solutions for that.
Main page at 31:34
The areas where I think our team is having a lot of fun, it's kind of where you're going. It's like the workflow automation. What are the areas where if I think about my day, I'm almost not thinking? And how can I go and augment my day-to-day so I can go and reorchestrate how I want to spend my time? I also fully, fully agree with the sentiment that you're sharing that the work has gotten...
you know, the work is always going to be interesting, but the work has gotten more fun because you can explore things more quickly. I've had folks on my team come up to me being like, holy shit, like I actually am like having a ton of fun. And I actually think that like the policies that we created and the freedom we've given folks to explore are the reasons why like some folks are like, I want to stay here.
I really, really like what I'm doing. And I think, you know, I don't know if folks are actually treating uh, access tech technology as like a recruiting vehicle as much as they could or should. Um, you know, I've at least started to do that in the recruiting conversation since I started to hear that from the team. Um, especially when you're trying to pull from folks who are not necessarily in technology, they're like, oh my gosh, this is like my, my front end or my front entrance into like an entirely new world.
And if I'm empowered to learn, like this is really cool. Um, so, you know, I actually would lean, I mean, I know other people are maybe going to steal this now, but like, uh, for me, that was actually one of the really fun things to do. I agree. I actually, I have this idea too that I think we need to start talking about this like we talk about perks and benefits.
You get X, Y, and Z. If you come to work here, your former employee doesn't let you available and now you also get access to all these models or other tools. Yeah, and I think it's not just that but then it's also like if you have folks understand what are other people building around them and so much of what you're going to learn is through osmosis of what others have built too and so if you get this feeling that like you're joining an organization that's not just saying that they give access to these things but they're actually building and you can see it and you can feel it through the interview process those are the places I'd gravitate to.
So in 2020, my partner Angela and I wrote this piece on how CFOs needed modern tools. We had this pyramid diagram in there, which was essentially saying that the finance team was spending all their time on this like data reconciliation layer. And at the top, which was the smallest amount of time, was being spent on strategic finance or like strategy questions.
I'm curious if your time... actually seeing your time and your team's time unlock, not just on doing things they enjoy more, but like being more strategic or being able to weigh in on more decisions or like how has that changed your role? I feel fortunate that as I've grown within the company that that has taken up more and more of my role.
And then as I then think about what is exciting for others, I also recognize that there's benefit in me creating that same space for other people within the organization. So yes, there are things that we'll have to do as daily rhythms or weekly rhythms. But in the same breath, if I can take our... take our, we have a finance organization that split in one of the, one of the pillars is go to market.
If I can take the team that's focused on our self-serve business and immediately get them out of reconciling last, last week or last month or whatever it is, and then very much more focused on what are the experiments we're running? What are the trends that we're seeing? Where are the dollars that we should, what are the additional dollars that we should be spending on? Like that is way more engaging to them.
And I think they're actually able to do more of that now. Like it's, it's like such, it's, some of the little things here matter so much. It's like, how can I go and automate the creation of a set of materials that I know it's going to look and feel the exact same way and then focus my time on the annotation, the discovery, the understanding.
And we've seen that start to get a lot, a lot faster and the quality of that improve. And we even had one of like, I was actually the leader of that team get up and talk about like how he had gone and create a set of plugins to go and you know, in Figma to go and ideate on this stuff really quickly. So, you know, I would hope that my team is telling me that they're spending a growing share of their time on that bucket of things.
But you're always going to have to chase, you know, the complexity in your business and managing the complexity with like how much time you're able to reserve for the other pieces. Totally. One of the things that we're seeing in the CFO tools that we've invested in is the product is moving away from, you know, tracking workflow towards providing a result.
Main page at 35:44
And then part of the product is the audit trail. So obviously, finance needs to make sure everything's correct. You need to be able to track results. Where, you know, how the product came to a particular reconciliation, for example, but then it's done for you. So it's that balance of both having the audit trail and the and the results. But we are definitely seeing our team spend more time doing things like running experiments and doing things that used to take like a month long research cycle.
you had to pull in some from data science, and chased down a bunch of people over email, got everyone in a room, and now you can quickly iterate on this because you can, yeah, you can have agents running in the background. And it's even things on the accounting side, like flux analysis, right? You know, you're spending time as an accountant going through and trying to reviewing the GLL accounts for like period over period.
If you can leverage a tool, and I know there's a whole bunch of tools now out there that give you that initial sort of like stab at what has changed. That gives them like a set of things that they can go and chase. It gives them like an initial set of things and maybe it's right right away. And I'd love for that to be more and more true. And then they focus their time elsewhere.
And so I fully expect that like the spirit of where you're going, like that initial draft, that initial sort of set of expectation, that initial sort of idea of what to go and pull the thread on can be surfaced via tools. It's kind of where I was going when I was talking about that T&E piece, right? Like it was giving our team sets of threads that they can go and pull and then us enough gut to go and chase it too.
Right, you have the data and then now the time to go up. you know, address those second-order questions and see what's behind, what's going on. Yeah, I was thinking how when we grew up, the word reconciliation was a very negative word. It was associated with a lot of bad memories and a lot of weeks and months spent on trying to chase something, where now it's just something you do, or maybe it's even a positive word because you can solve it much easier and quicker with the modern tools and with AI and find maybe not exactly where the errors are, but just get there so much quicker.
And then you still need, obviously, to go talk to people as FP&A will always continue to be the people discipline. Yeah, I, you know, it's one of those things I think I underplayed or I didn't realize how important communication, you know, relationship building, your ability to, you know, go and influence was to this role. You know, I probably walked in feeling like I could you know, be the smartest person in the room and figure it all out.
But then I realized, like, you know, it's a team sport regardless. And you can only go and affect so much change. And you then really do have to go and get other people to be on the same page with you. And if you can do that effectively, I think you can be a really effective leader. Um, you know, those are sort of like the, I think the true skills that I can tell you, you're asking earlier about like, you know, what am I screening for? If I, if I can test and get a sense that you're like, you have this ability to build really solid followership, you have this ability to go and build trust with others.
Like that's so invaluable. That's a good segue into what I wanted to chat about next, which is what do we think changes in the next 12 to 18 months for the team and the role and the function overall? I don't know if you guys have any points of view on what might change. Maybe let's start off talking about how your team even is organized. Yeah, I mean, I would love to be in a spot where, you know, we're only adding individuals if like the complexity of the business is growing faster than the needs to support it.
I do think that we're in a spot now where like, you know, a lot of the regular sort of business rhythm pieces, I think you can start to move in the reverse direction versus needing to add people in order to keep up with it. You know, I think for us, we're going to continue to fight it because we're adding new products. We're acquiring teams and businesses.
We're, you know, continuing to evolve what we're doing. And so it's always more, I think, in that world, the complexity there is still outpacing, you know, where we're able to truly drive, you know, complete efficiency. But we're definitely like, we're definitely getting more efficient, you know, period over period. Do you think that the efficiency, do you think like plateau, like you've got the tools to do what you need to do? Or do you think that more of these processes will just completely get automated end to end? I would hope that more and more can get completely automated.
I think maybe I start with the pieces that are like truly deterministic and like how can I feed it with enough information so that I can feel that the output there, you know, is completely, completely trustworthy. I think getting something to that like audit ready output piece
for a system that's like truly business critical is extremely high. I think it's also going to be, you know, an interesting sort of conversation with the auditors on what gets them comfortable. But I don't kind of take it out of the picture. I do think we'll get there over time. I think, you know, like I was sharing, you know, as long as our business, if our business complexity was like staying the same, I think we probably wouldn't need the same number of people a year from now.
Main page at 40:31
But, you know, I think we only get there because you're doing a better job of finding these places and rhythms where you can build more consistency in the way that you're operating. Is Excel under threat? No, it's like my love language, dude. Like I think in the same way I was describing how I, you know, I still think that case study is so important because like you use it as a tool, right? Like you use it to build intuition.
A lot of the output people are still creating is a model. I mean, that model could be, you know, you could host it somewhere else. It could be something else. But like I think you want this tool to give you this ability to refine your understanding and play with things with your hands. And it's kind of like the magic that we see with Figma, right? Like we can give people the ability to go and, you know, have an initial stab in the first draft through, you know, prompting and through natural language.
But like sometimes it's so much easier to go and riff and make changes on your hand. Take a color wheel as an example. You've got like a screen that you've designed and you're like, hey, I want to go and change the background. You could sit there in an agent and prompt it, right? Like, go change the background from red to green. Or I could take the color wheel and you get all the different shades of it and you get the real feel of what's going on.
Similarly, I think about that with Excel. It's the way I build trust. It's the way I build understanding. There may be something better in the future, but for me, I think it would be really, really hard to rip away from me. I also grew up in Excel and I still use Excel to like organize my thoughts. Like if I'm trying to run an analysis, it's just even like the spatial organization of it.
And I think the models aren't quite good enough to like create a forecast or a model quite yet. But I think that organization is still valuable. I don't know if you feel similarly. Yeah. Totally. And I also think, you know, part of the things that I've tried to experiment with now is like, how can I use, you know, how can I use, how can I use one of these models to help me better understand the output that the team is putting together? Like, if you give me like a, you know, 20 tap model, it's going to be really challenging for me to go and like, you know, tap through and thumb through everything.
But if I can, you know, pass that same context through, you know, through a model to help me understand, you know, what are the things that really are the needle movers or what are the areas that are more sensitive. It's actually given me like a better starting spot to go and orchestrate and understand things, which I've actually found really, really helpful and effective.
The world we're living in is also challenging, too. I was talking to a university professor the other day, and I was asking him how do they teach AI at the universities. Well, they don't right now. And one of the challenges is that they said they had a course, and within a semester, they've changed the syllabus several times because new models have dropped.
And they just have to completely change how they do it, though, so they just sort of give up. So they're going back to fundamentals again, teaching people AI. analytical thinking and Excel and all of that, because I imagine you're in a similar world where if you were relying too heavily, you're going to have to redo how you do your earnings.
a lot has changed, but a lot hasn't changed. And I think maybe that's the spirit of where you're going. Um, I, you know, I think that the core capabilities of what makes a great finance person are still there. Um, and how you actually, you know, leverage the tools at your disposal to make, you know, better, better decisions is, you know, always going to be this like moving target for you.
Um, uh, The unlock that SQL was for me is now a net new unlock with AI as a tool and capability driver for me. So I think a great finance person has longevity if they continue to adapt. which, you know, we wrote this piece, we said, it was titled, You Need a New CFO. The main point was that there's a mindset shift. So whether the individual actually has changed, it's that they have to think more automation first, either build or buy the tools, depending on what's what's available and what makes sense, but it's really automation first.
I'm curious if you think the profile, either of you, of a CFO in the next year or two is going to change in any way or to your point, it's kind of the same dimensions that are important, but maybe just the mindset continues to evolve. If I were to give advice to anyone, it's like hire someone who feels a similar amount of business ownership and wants to be the, you know, an operational rigger as you as the CEO does.
They want to win. They want to win no matter which way possible. They have a set of tools that they're going to use in an undertaking of a P&L to go and orchestrate that change. But you truly want like a business leader versus like, you know, someone who, you know, you know, like I was sharing earlier, like a traffic cop, right? Like that, that is just not, and yes, I think there's a lot of, there's a lot of things that you're going to need to have as like commonplace and solid understanding of like all the accounting fundamentals, like, you know, your, your, your ability to actually go and orchestrate a planning process.
But like, I actually think that things that like make people truly unique in this role, it's like, do you understand the business? Can you go and make, make change happen? And can you get, can you simplify the understanding of how the business model works so that others are all running in the same direction? Yeah, and I think it's true whether we're talking about a public company like Figma or we're talking about a seed stage or a serious A startup that's starting to scale their go-to-market and getting traction, is that that's what the founders and the CEOs really need from finances, that extra business opinion, opinion on the business and insights that are easier to
get, but also still you go back to the basics like customers, do you understand the customers? Yeah. Do you understand the behaviors? Do you understand the metrics that come from that? Inputs, outputs. I think that's, that's will always be the same in what we expect. Yeah. Maybe the thing I'd add, like, I, I, I do think like, you know,
creativity is important. Not like, you know, go and create like a funky set of metrics creative, but like, how can you actually go and think about your business in a slightly different light? Um, and use that as like the way that you go and, um, drive change and be opinionated. Um, and I, you know, I actually don't know how, you know, I try to do, I try to do this.
I don't know if I'm doing it as much as I, you know, could. Um, but if I come up with these ideas, if I can come up with different ways of thinking about things, I actually think that, um, I think some great ideas can come from your finance organization. And if you really set them up well and right, they can be this like layer within your organization that's just as impactful and really driving a lot of the internal strategy as well.
I will say at the investor and board level, we are seeing a much deeper set of analysis come through or the rapid iteration. You know, before it used to be, oh, we have all these questions at the board meeting or before. And then it's, you know, the team needs to run and cycle through that. That process has just short circuited and hopefully is less painful off the finance team side.
Last question for you, Yvonne. As our portfolio companies or just companies in general come to you and say, where do I start in terms of automation? What do you give them as advice? I think it's kind of the same place where we always started. You start with the integrity of data. You have to figure out if you actually have a good access to data if you're tracking things.
Many of the times, especially early stage companies, they don't even track anything. And so you have to set that up. And that often goes against the priorities that maybe the first finance hire has. Like, oh, I got to close my book sometime. Got to send the board update. All of that. Actually, no, you can't even do that until you're on the solid foundation.
You might sometimes have to set it. You might have to rebuild it. you might have to change things. We've had a number of people that came in, especially now very quickly, you can realize within several weeks that maybe the revenue is calculated in a way that's not how it should be calculated for that business model. More creative ARR at the early stage than I've ever seen before.
For sure, for sure. It's changing fast, too. But it starts with data, and then based on that, you really kind of create the reporting rigor, you create the metrics, and then you create the story. I think one of the things, too, Praveer, especially you've been on that journey as a CFO, like storytelling becomes a really, really important once you have your eyes set on the IPO.
Mm-hmm. And you have to be all telling the same story. I feel like that has moved to earlier and earlier stages because you expect to tell the story now in fundraising for Series A, Series B. And not just the story of what the product vision could be, but story with the numbers and what the business could really be like. And that's gotten easier, but it's also gotten harder because I think a lot of people overthink that with AI.
And, you know, Yvonne and I have been hosting these CFO and controller dinners for, I don't know, a couple of years now. And we saw this real market change, I'd say maybe nine months ago when it went from people saying, oh, yeah, I'm generating this tax memo or this onboarding doc with AI to saying, OK, yeah, I can actually I'm doing the core thing.
the data reconciliation and automating many of the workflows. And it's really been a step function change. And if anything, the leaders are saying, I need to do this, otherwise I'll be perceived within my organization as behind everyone else. This goes back to your point around you winning the hackathons, like finance was never the one that was going to be winning the automation hackathons, you know, I don't know, a couple of years ago.
And it's pretty cool to see that's totally changed. Yeah, I love this part of it. And I would, we have like an internal maker week and it's our internally branded like hackathon. And, you know, I would always sit there early days and not really know how to participate. And now I'm like, if I had like a spare minute, I think I'd have a million different ideas.
And I'm sure my team feels very similarly. Well, Praveer, thank you so much for joining us. This was really fun to talk about and understand directly from someone who's gone through this journey of automation over your career. And thanks, Yvonne. And this was a really fun conversation. Yeah, thanks for having me. Yeah.
Thanks again for listening, and I'll see you in the next episode.
As a reminder, the content here is for informational purposes only, should not be taken as legal business, tax, or investment advice, or be used to evaluate any investment or security, and is not directed at any investors or potential investors in any A16Z fund. Please note that A16Z and its affiliates may also maintain investments in the companies discussed in this podcast.
For more details, including a link to our investments, please see a16z.com forward slash disclosures.
Related episodes
- Startup Lessons from Serial Entrepreneur Justin Kan
- Amazon CEO Andy Jassy on the $220 Billion AI Buildout
- Mark Cuban on Why AI Could Turn Solo Founders Into Trillionaires
- How Bending Spoons Built a $20 Billion Compounder | Luca Ferrari
- Andrew Huberman’s Three Rules for Better Health and Focus
- The New AI Agents That Shop, Plan, and Gossip
- Ken Griffin on AI, Midterm Elections and Fiscal Policy
- OpenAI: When AI Agents Use Computers Faster Than You