This conference call transcript was computer generated and almost certianly contains errors. This transcript is provided for information purposes only.EarningsCall, LLC makes no representation about the accuracy of the aforementioned transcript, and you are cautioned not to place undue reliance on the information provided by the transcript.

Expensify, Inc.
11/6/2025
Welcome to the Expensify Q3 2025 earnings. I'm CFO Ryan Schaefer, and with me I have our founder and CEO, David Barrett. And now I'm going to hand it over to Nikki for the legalese.
Please note that all the information presented on today's call is unaudited, and during the course of this call, management may make forward-looking statements within the meaning of the federal securities laws. These statements are based on management's current expectations and beliefs and involve risks, and uncertainties that could cause actual results to differ materially from those described in forward-looking statements. Forward-looking statements in the earnings release that we issued today, along with the comments on this call, are made only as of today and will not be updated as actual events unfold. Please refer to today's press release and our filings with the SEC for a detailed discussion of the risks that could cause actual results to differ materially from those expressed or implied in any forward-looking statements made today. Please also note that on today's call, management will refer to certain non-GAAP financial measures. While we believe these non-GAAP financial measures provide useful information for investors, The presentation of this information is not intended to be considered in isolation or as a substitute for the financial information presented in accordance with GAAP. Please refer to today's press release or the investor presentation for a reconciliation of these non-GAAP financial measures to their most comparable GAAP measures.
Thanks, Nikki. Now let's dive into the Q3 financials. Revenue was $35.1 million. Average paid members was 642,000, and total interchange was 5.4 million. Our operating cash flow was 4.2 million. Our free cash flow was 1.2 million. Net loss was 2.3 million. Our non-GAAP net income was 4.3 million, and our adjusted EBITDA was 6.5 million.
Q3 free cash flow was a little less than in prior quarters.
That's mostly due to seasonal timing of some annual payments.
We also reiterate our fiscal year 2025 free cash flow guidance of $19 to $23 million. As always, here's our Q4 flash numbers for our paid members in October. Up from the Q3 average, which we always like to see, $653,000. And now to jump to some business highlights for Q3.
We had some great marquee customer wins. We are now the official travel and expense partner of the Brooklyn Nets. We're the longtime customer of our expense product, and they have adopted Expense by Travel. That shows just the power of the platform and the fact that customers are really excited about this.
So we're very happy to have the Brooklyn Nets as a new Expense by Travel customer.
On the topic of travel, bookings continue to climb, growing 36% from Q2 and 95% since Q1. So expense by travel continues to be a bright spot in the business and something both us internally and our customers are very excited about. We also repurchased 1.5 and change shares of our Class A common stock and that totaled approximately $3 million. And now I will hand it over to David for a product update.
Great. It has been an extremely exciting quarter when it comes to the product side. First off, talking about migration, as you know, everything hinges upon our ability to move existing customers over to new expensive lines. That's what triggers, we think, everything in the business's recovery and growth and so forth. And so we've made incredible progress in that. At this point, we would say we're targeting what we call 90% feature parity. We want to support essentially 90% of the functionality of Classic on New Expensify. We're very close to that right now. We're, of course, we'll always maintain Classic for existing customers as long as they need it. But the main thing right now is that New Expensify is largely complete when it comes to the functionality of Classic. We've also migrated basically the data of nearly all customers to New Expensify, meaning that customers can switch back and forth between new and classic as they like, which is a huge accomplishment. So we're to the point where essentially New Expensify is essentially done from a feature perspective, and now we're just carefully what we call nudging customers over, meaning that We will make them sign into New Expensify the next time they sign in, but then they can optionally switch back to Classic. We've nudged all of our Collect customers over. Now, to be clear, we have basically two plans, Collect and Control. And so our Collect customers are smaller, simpler customers. We've migrated nearly all of them over to New Expensify, and the vast majority choose to stay on New Expensify rather than going back to Classic. And so this is a huge testament to the power of New Expensify. Additionally, and I'd say this is one of the most exciting things, now we're closing all new customers on New Expensify, meaning that we will start every sales conversation on New Expensify, and we'll still switch back to classic if there's some long-tail features, some esoteric integration or something like this that they might need. But we start every new conversation on New Expensify, and so that's been really, really powerful, especially at the conferences, especially as we roll out to new leads. So it's been great, great progress when it talks about migrating existing customers from classic to new. Additionally, it's been very exciting on the concierge side. So, you know, we've been talking about this for a while. If you've been paying attention, AI is kind of a big deal. And so, we've been talking to AI for a long time because New Expensivized's entire design anticipates basically modern AI. And the way that we view it is AI is incredible, but it's also not foolproof. And so whereas some people really focus on AI in absolute, we view AI as a great feature for a certain level of functionality, and we want to take the AI as far as it can and then have humans take it the rest of the way. And so our design, which is very unique, it's a hybrid system. When you talk to concierge, If it's a, you know, simple, common question or even just something very detailed about the product and sort of like from a help page or whatever it might be, the AI is really great at handling that question. It can do it better than a human, honestly. But if you get to a super complicated topic for diagnosis or if you have... More of kind of an emotional issue, that's where we bring in our human agents. Now, we can seamlessly switch back and forth between AI and humans sort of imperceptibly to the customer. And so to the customer, all they get is just an incredible chat support experience. But on our side, it's handled using AI or human seamlessly depending on who's best for the job. Likewise, this is a contextual AI, meaning that it's built into the product rather than sort of on top of the product. I think you've seen a lot of AI solutions, which are kind of like Windows 95 Clippy, where basically it's just something kind of stuck on top. It's very clearly not designed around the product. Ours is different. With concierge, it's built into the product in every place. And so wherever it's natural for you to talk to the AI, whether, you know, either you're talking directly to concierge or maybe you're inside of an expense report or even commenting on a particular expense, Our AI appears everywhere, so you can basically talk to it naturally in the context of that. Additionally, we're building what I would call a general intelligence. I think there's a lot of different approaches towards this, and the most straightforward approach that people start with is they'll have kind of a collection of very purpose-built agents. And so maybe a specific agent will reach out to you in a particular narrow context and talk about one topic. It makes sense. That's a very easy place to start, and I think that's kind of where everyone starts. Our design is going for more of a general intelligence, meaning that we've built a singular AI that can operate in a multimodal fashion. So you can talk to the same AI and you can ask it to scan receipt, categorize an expense. You can ask very complex questions about how to configure Expensify. And so the same AI can do all of these different functions. What's nice about that is it really supports our contextual design. So it's not like you have to have 10 different AIs hanging out in every single context, and then you have to choose the right one based upon the question that you have. Rather, you can send any question to Concierge, and it'll always be able to answer it. This works especially well across platforms. So you can talk to our concierge sort of like single general intelligence over chat, obviously, but you can just email it at concierge.com or just text it for 7777. And because it's a single general intelligence, you can ask it any questions in any of those. And so you can ask it to create expenses, ask it about your expenses, about your workspace, whatever it might be. This is a really powerful platform that we think is unique and novel in the market. We don't think anyone else has this level of sort of general-purpose financial AI out there, and so this is just a start. to give some examples of kind of how this works in practice. So, you know, there's some basic stuff. Of course, obviously, detecting not just whether the expense from, like, the merchant and amount is out of policy, but looking into the receipt itself, making assessments about what type of merchant it is and so forth. And so we can do more detailed prohibitive expense detection. Likewise, you know, it's all the rage these days. You know, AI is a big deal for not just the admins, but also for the employees. And so we detect AI-generated receipts and flag them. We have a feature they call conversational corrections, meaning, of course, whenever you, you know, swipe the card or scan a receipt, we will categorize it to the best of our ability based on the information just on the receipt and merchant itself. But every company is different, and sometimes it's ambiguity as to the correct way to categorize it. So we'll narrow it down to a short list of the most likely options and just ask you, which one is it? If you're in the app, you can just do it in one tap. If you're responding via text or email, you can just respond with a number or whatever. And you don't have to pick from these options. You can also just say something else entirely. This is the advantage of a general AI where if it asks you a question, you're not trapped into whatever conversation it wants you to do. You could actually just switch the script and ask maybe like, well, what are all the categories available? Or what's the last time that I did this, whatever it might be. And so this general intelligence allows for a much more natural ability to correct and sort of categorize information. And as mentioned, this is a truly universal agent. You can have the same conversation in a wide variety of contexts, whether it's chat, email, SMS, and so forth. So this is a major release for Concierge AI, but it's really just the start. We think this is an incredibly powerful foundation that we've ironed out the kinks for, and you're going to see more and more incredibly powerful functionality being built across it over the quarters to come. So just to kind of summarize everything at a high level, we've increasingly and continued selling in a very successful fashion travel and card to existing customers, which has been great. We've been putting our free cash flow to work, which is great. Despite all this, despite all the chaos of everything, we've really stayed focused on investing in an AI-first design. And I think this is a big deal because obviously everyone thinks a lot about AI, but I think that everyone's kind of gotten through the first wave, a lot of the easy stuff. Here's where it starts to get much harder going on now. And so we think that chat is the UI of AI. If you can't talk to it, how smart can it really be? And so our design is to bring a chat-first design everywhere into the product such that it makes our entire product into an AI-first design. It's a very, very different design. I'd encourage you to check it out, and I think you'll see a glimpse of the future because I think everyone's going to be designing something like this over time. Likewise, our new Accentify migration is on track, and we've got really great customer reception. This puts everyone into a position to talk with their AI in a much better way than they could with their previous product. And at the end of the day, it's really about anything that you can do via the UI, you should be able to do via AI. And so building a truly AI-first product where you can talk to the AI in a primary mechanism as opposed to just as a sort of secondary flow. Anyway, we're going to have lots more to talk about in the course to come, but for now, we'll take any questions we can.
Perfect. Let's get started with Citi. I believe George, you're on the line.
Great. Thanks for taking the questions here. I'm on for Steve Enders. Maybe just on this point about chat as the UI for AI, you know, this is something that you guys have been early to. It's interesting from our perspective to watch other people kind of catch up to where you guys are in terms of building in natural language-driven UI into other software apps. I'm just curious, from that head start that you've had, what have been some of the big like learnings or capabilities you've incorporated into the platform that, you know, when you watch others, you can see maybe them making missteps or where you feel like you have an advantage there?
That's a great question. And I think it really comes back to this idea of being built in versus built onto the product in that expensive ad design is that you can go into any context and inside that context, you can talk with your AI about that particular thing. And that's just kind of a nuanced point. But imagine, for example, you're texting with an AI in a general context and you want to change, you know, yesterday's expense. You want to basically, you know, categorize it or you want to highlight that actually that was an accident. I didn't mean to submit that, whatever it might be. Referencing that outside of the context is actually quite hard. You have to remember the merchant, the date, the amount, or some key indication of how to do it. And it's just a really impractical thing. That's going to drive you back to the UI. Now, if you're talking to your assistant, you would just say, hey, that thing that I did yesterday, or whatever it might be, and you give a kind of a relative reference, and you would be able to figure it out based upon the contextual clues of the conversation. And so I think that our UI is about trying to infuse the AI throughout the entire product, such that you can use it in whatever context you're already in. You don't have to leave your context to use the AI. It's already there. This makes a very different UI design. You can see it's a very chat-centric design. In many ways, it looks like a kind of chat GVT interface. I mean, I think that it's hard to argue your business is an AI-first product if it looks like Concur. I think that if it had to look a lot more like chat GVT to really, you know, credibly say that this is an AI-based thing. It's kind of like what makes an AI intelligent isn't that it just has a bunch of kind of like AI branding on a bunch of algorithms, I think you need to be able to talk to it. You have to be able to ask it questions, whatever you want. You have to explain why it did what it did. And you have to be able to learn from its mistakes. I think that The idea that you can have automation in place and that you can't talk to it and figure it out doesn't seem very smart. Like, let's say you had, you know, you hired some sort of an accountant and they said that they approved a report and you asked them, why did you approve the report? And it's like, I don't know. You wouldn't be like, this is a genius. You'd be like, this is pretty stupid. I think a lot of sort of algorithmic Automation is very powerful, but it's not intelligent in an AI sense. I think intelligence is about getting into a place where you can ask questions, get answers, and make changes all through natural language, and I think our design is really optimized for that.
I also think it's important that you're unlocking a new use case. Making charts with AI is not interesting, but that's a very common use case. People have been making charts for a long time. It doesn't require AI. It's not a good use of AI. So I think the fact that we're able to do new things, new functionality, offer new value to the user because we're using AI is what sets us apart versus replacing code with AI. The customer doesn't care about that. Yeah, yeah, I get that.
Super interesting. I appreciate the detailed answer there. Maybe something more tactical, you know, the government shutdowns in the news. It seems like maybe there might be some impact on travel. You know, I can appreciate that probably if there is any impact to you guys, it would basically be a timing issue. but just any thoughts there from shutdowns in the past or just general scenario analysis you guys maybe have thought through there?
So I think it's, I guess it depends on to the extent it impacts travelers, right? If you're stuck somewhere, you're probably going to actually end up spending more because you have extra hotel nights because you're stuck in New York or something. But in terms of, You know, is it going to keep people from, you know, using expense if I travel less or something? Because they're worried about being stuck. I think that, you know, that's probably a realistic risk. It depends on whether people are going to change their travel plans or just risk it, basically, I think.
Yeah, I don't think uncertainty is good for anyone's business.
Yeah. Yeah, I appreciate that. I appreciate you taking the questions. Thanks, George.
Great. Let's see. JMP, I believe Aaron, you're on the line.
I'm here. Thanks, guys. Hey, Aaron. Hey, Ryan. I want to dig in on migrations from Expensify Classic to new Expensify, including what percentage of revenue today is on new Expensify after migrating your collect customers and the timeframe over which you expect to get your control customers that I think are a substantial majority of your revenue on some of the Expensify.
That's a good question. I don't think we know the – We're less than – it's less than 50% of revenue. Yeah. So we're not – you know, over the 50% hump in terms of revenue yet. But that's the huge priority right now is moving people over.
Yeah. I mean, as I mentioned earlier, we're aiming to have NewExtensify match Classic from a functionality perspective by end of years. And I think we're very good on that target. Now, the real question is how fast can we migrate everyone over? We control the timeline here. There's no sense migrating a little faster than, you know, than they're comfortable with. And so we're going at the fastest rate that they're comfortable with. I think we're really hoping to have a significant progress on that, if not completion or near completion by the end of the year. But I don't think we can control – we don't know exactly yet because we don't know if we don't know.
Yeah, I think it's – we're also listening to the feedback of customers nudged and iterating very quickly because it's – People who are new to Expensify and they come in, they love it, right? Because it's all they know. It works great. It's very cool. Someone switching from who's used Classic for maybe, you know, five years, ten years to new, that's a different audience and they have a different reaction. It's not negative, but, you know, they have a different set of feedback than what we've gotten just from, you know, new customers coming in. So we've been – a little slow moving people over and really focusing on those user sessions and getting feedback and making small changes quickly and iterating. And I think it's Flywheel where it goes faster and faster. But the existing customers... are an interesting source of feedback compared to net new because they say different things. So we're just working through that.
Actually, that's a great point. The bottom of the slide that talks about a major goal we had was to make sure every new customer conversation started on new expense supply. And so that has been the priority. That's done. And so now the priority is getting existing customers over.
That makes sense. So then the follow-up here, are you seeing any incremental monetization from the customers that have migrated to New Expensify or is that more TBD? And I assume the more relevant piece of this question at this time is what type of internal cost savings do you anticipate from the concierge agent once you get everyone migrated over to New Expensify?
That's a great question. So the support cost should be definitely less when we get everyone over because New Expensify handles everything better than Classic. A lot of the problems, not problems, but, you know, there are some complaints of Classic that we had solved with new Expensify. So, in general, it should be less of a support burden. Also, just the fact of maintaining two platforms at once is expensive and can be like a split brain problem. So, it'll be... We're really looking forward to solving that.
In terms of increased monetization, I think it's much easier to issue new cards, manage everything, get into travel.
There's a lot of... There's travel functionality that only exists on New Expensify. So it's, you know, using Expensify Travel with New Expensify is a better experience than classic. So I do think that it's the net positive. Everyone that we move over is a net positive on the business. So that's why it's a huge focus for us right now. Absolutely.
All right. Thank you, guys.
Of course. All right. We were double booked with some of our other analysts, so we will talk to them offline. That's everybody for now.
Great. All right. Thank you all, and we'll see you next quarter. Thanks, everyone.