Keeper + Anchor ≠ Kanchor

There may be errors in spelling, grammar, and accuracy in this machine-generated transcript.

Alicia Katz Pollock: Hey everybody, welcome to the unofficial QuickBooks accountants podcast, and I am super excited because we have kind of a special episode today. I'm titling this one Keeper plus anchor does not Equal anchor. And I have some special guests with me. I have Ben Stein from keeper coming to me from New York, and Tal Ben Basat from anchor coming [00:00:30] in from Tel Aviv. And so thank you both for joining me for at Short Notice.

Ben Stein : Thank you for having us.

Tal Ben Bassat: Thanks for the invitation.

Alicia Katz Pollock: Yeah. Um, I am a user of both keeper and anchor. And so when I heard the news that you were joining forces on a new integration, I got, like, super excited. And I just emailed both of you guys immediately. And thank you so much for just jumping on the on the call with me.

Ben Stein : It's truly our pleasure. And I'm sure I can speak for both [00:01:00] of us when I say it's. It's an honor to serve your practice.

Alicia Katz Pollock: Well, thank you very, very much. Now, I met Ben back in 2021 at AP camp. And actually, our funny story is I was heading down to the campfire for a music circle. I play bass and like, they were waiting for me and I had my drink ticket that I had to go turn in to go get my drink. So I'm like, Ben, can you go get me my drink for me? And he shows up and he's like, yeah, they're not accepting drink tickets, but here you go. So bought me a drink [00:01:30] was so kind and gracious about it. Um, and I met Tal at the dance off at, um, at Scaling New Heights in 2024 and proud to say that I won my heat. Although, you.

Tal Ben Bassat: Know. You're dancing good.

Alicia Katz Pollock: So. All right, so let's go ahead and talk about it. Let's start with the big news. What exactly does this new integration between keeper and anchor.

Tal Ben Bassat: Do [00:02:00] you want to start or should I start?

Ben Stein : Uh. I'm happy happily. Lead this off and then feel free to sort of, uh. I think so at its core, what this does now, the sort of the integration today is, um, is designed to help configure clients and keeper as you acquire new customers in anchor. Um, so if you send a proposal, the proposal gets signed based on the settings that you have in anchor that's going to auto configure [00:02:30] a client in keeper. So you can apply templates, you can create clients, you can set properties. All of the things that you would have to do manually or have to manually wire up a Zapier integration to, uh, build out previously. Now we'll just naturally, uh, naturally work well together automatically.

Alicia Katz Pollock: That's that's that's like magic because it definitely, you know, when every time we get a new client, we go into keeper and we dial it all in and it's going to save us all of that onboarding work. [00:03:00]

Ben Stein : Yeah. And so that's really the goal. I mean, I think the first really first pass is how can we make this a better integration. But I think the other thing this does is it is it puts it puts down a really solid foundation for future improvements. Keeper and anchor have what I call very natural product teams. So they're like very good at getting people to pay you money, which is very important. And we're very good at what I call everything that happens after your client signs on the dotted line. And we have no intention of doing billing, we recognize [00:03:30] how hard that is and how hard anchor works at making that seem easy, but we know that it is not. Um, so our our hope is that this is the initial integration, but by no means the final one. And that as we continue to find other places where we can make the two apps talk together, that we can make that a seamless process for all of our mutual customers.

Alicia Katz Pollock: Whose idea was it? Like? Please tell me. It was a late night cocktail conference teleconference conversation.

Ben Stein : I will say, and apologies if I'm sort of like doing all the first speaking here, but, um, I [00:04:00] will give them credit for pushing this through for sure. Uh, I think anchor, definitely this would not have happened without anchor, but really the idea came from our mutual customers. This is something that our customers asked for, anchors, customers asked for, and we have a lot of overlapping customers and we want to keep them happy. Um, and so really, they they are the ultimate folks who get to take the credit.

Tal Ben Bassat: Yeah. And, and I really agree with that. You know, everything we do on anchor comes from our clients. Every feature, every every development we have. This [00:04:30] is why anchor, they really see that the depth of the of the of the features and and the value delivers mostly because, you know, our product team spanning like entire few full days, speaking to customers about what they need, what they're looking to have. So sometimes, you know, it's prioritized differently, but it's always, always pushed by the product team and by our amazing product in our head of product as well. And our clients were like, we want keeper, we want keeper integration, bring keeper integration. Then we went to Bannon, [00:05:00] to the team and said, guys, we need to have integration. And then and then and then our clients also went to keeper and told them, guys, you need to integrate with anchor. And and you know, it's amazing. I used to have a tax practice. Right. And the feeling that you can really add value to, you know, to your community, to accountants and really give them something that can help them make their life easier. For me, that's one of the main goals that kind of led me to want to, you know, be, you know, being anchor and like to do what we do today. [00:05:30]

Alicia Katz Pollock: Just it's one of the things that I really appreciate, appreciate about anchor is that you're really customer centered and customer focused, that you'd rather show everybody a good time than try and sell to us. And I really appreciate that attitude.

Tal Ben Bassat: And I can tell you I want to say something on that. Um, our approach is very different than other companies. We are not looking to sell. We're really looking to partner and people that use anchor. I think just like you said it, they know it and they feel that also [00:06:00] in other activities. We believe that the market is big enough for everybody. We believe that we just need, you know, want to show, uh, give people the options to make a good decision, um, and to be our partners. And that means that also after they start using anchor, we don't forget about them. We actually communicate with them to learn what they need. Just like in this case. And then we deliver on that. Not just not just listening, but actually delivering, which is important.

Alicia Katz Pollock: Yeah. Deeply appreciated. [00:06:30] All right. So can one of you guys share a real life use case or an example of how a firm will use this integration?

Tal Ben Bassat: So when you think about it, you know, onboarding a client is always a challenging thing. And everything starts with actually engaging with the client. Right. So you do your discovery. You kind of try to understand how to price them, how to build them and so on. Um, and that's, that's one thing that anchor really helps with. Right. You have very advanced proposal tools. [00:07:00] They can you can use packages and optional services. So you can really do a tiered pricing or dynamic pricing the way we call it. And you have the automatic price increases. So you can really create this this this proposal that can both tailor your client needs but also yourself. For example, the features we added last year, um, the automatic price increase came out as a request from, from again from the community that you can actually build into your agreement, let's say 5% on annual automatic price increase. [00:07:30] Why is that important? Because the client knows that every year the price goes up by 5%. It protects you from things like, you know, inflation, for example. This small thing that ESOP is and it's much better than surprising them with increases. Now, when a client receives a proposal and they connect the payment information and they sign it, then traditionally, what will happen is that now you'll have someone in your back office that will start organizing the onboarding process for your client. Right? And in the world without [00:08:00] keeper, they will have to start sending emails and chasing people and and having like maybe like a, I don't know, an Excel document, an Excel file that they have all those tasks lined out and you as an owner will will not really have visibility for that.

Tal Ben Bassat: Right. So if anchor, you can actually match the services you're going to provide, um, to different, uh, tasks on a, on a, on a, on keeper. Um, it could also be one to many. So you can have maybe a bookkeeping service, but [00:08:30] then it can be matched in keeper to a number of tasks. So different team members can get different notifications and start different workflows. Right. And that's priceless because that means that once the client signs the agreement anchor for example, will take the upfront payments. So you're already clear on that. And then your team already got notification and they start to work on keeper immediately. And that's priceless because that means you're not wasting any time. You don't need to have an admin that you know comes in and starts manually organizing [00:09:00] things or writing in, I don't know, in Excel. And then you go immediately into the world of keeper. Now one of the features we're gonna, we're gonna also, uh, push in the with the integration is how you manage amendments. Because what we did on anchor, we eliminated renewals. So an anchor, you can actually amend the agreement on anchor. People don't. As you know, they don't send an agreement every year, right? We don't want friction. But if you want to add another service, you can just add it on anchor. And [00:09:30] one of the features we're going to add is going to actually now start another workflow. Okay. On your keeper. So again seamless experience. And that's priceless.

Alicia Katz Pollock: That's awesome. And Ben do you have anything to add on that.

Ben Stein : Uh, no, I mean, I think I think Todd did a great job covering, covering, covering that overview. I won't belabor.

Alicia Katz Pollock: That. Yeah. You know, when you were when you were saying it. So you've definitely got my, my, my own imagination spinning. And it also made me realize that I'm just [00:10:00] like, you know, assuming that everybody knows what anchor does and what keeper does. So I actually want to like back up a little bit and say like, let people know, like, why should you care? Um, and so, um, what anchor does is it's a contracting and agreements package that controls your billing and then synchronizes to QuickBooks online for the actual invoices. So what that means is you can create, for example, a proposal packages even with option one, two [00:10:30] and three, because we all know in our pricing that's that. Giving people three options allows them to best fit. So they can you can create a custom proposal, give them a bunch of options. They can even add on add on services. So it creates that whole package. It creates the contract, it gets their signature and then starts the invoicing process and then invoices them monthly. And then the invoices just. And the payments show up in Qbo. What [00:11:00] keeper does is when you're doing your bookkeeping, it's your checklists of all your SOPs, your your procedures for doing your monthly bookkeeping or quarterly bookkeeping or your your annual tax tasks.

Alicia Katz Pollock: And it also integrates with Qbo in a way that you can actually click on a transaction and see the transaction and edit the transaction from inside Keeper [00:11:30] without going over to Qbo. And you can even ask your client questions through their portal. So if I get a transaction that comes up and I don't know what it's for. I can ask questions right then, and it sends the client a message, an email, and then they log into our portal to answer it. So it keeps us out of email, and it also rises to the top, um, different things that we it's helped with my analysis [00:12:00] of the file. Like it'll pull out any transactions over 2500 or new vendors or transactions without vendors. And so I just go into keeper and I kind of scan the health of the file without even going into qbo manually. So it saves me tons and tons of time. So this idea that they can look at the package, they can say, all right, I want the mid-level package. And then keeper goes and sets up my SOPs for those services and just adds [00:12:30] them to their portal is freaking brilliant.

Tal Ben Bassat: And add that and add that amendment mechanism. So that's probably the third thing on anchor that you have the ability to amend the agreements and amend your invoices. That's a capability that there is no solution out there that actually can do that. And when you think about it, why it's important because our relationship with our clients always evolve, right. So it's accountants. Nothing ends when we sign the agreement. It actually actually the biggest everything actually [00:13:00] happens after we sign the agreement. Right. So so you need something that will help you to kind of manage manage this change. And that's what anchor does. The ability to manage the agreement, to change it, to update it. And the ability then for anchor to automatically push those changes into keeper means that your business is always moving forward, always evolving the relationship without with minimal friction to your clients or to your team. By the way, because your team don't need to like go and search for stuff, it's always updating everything.

Alicia Katz Pollock: I really love it. What's [00:13:30] been the initial feedback from early users?

Ben Stein : I think it has caught my team off guard. Uh, just how many folks use anchor? Like, this is not something we had a ton of transparency into, because it's not a thing that we ask for. Um, and all of a sudden, my like, we go live with the integration. I think it was Thursday last week. And, uh, part of the steps in the integration is you need to request this, uh, API key, uh, through right now. It's through our support channel coming soon. This will be something you can just click [00:14:00] one button in the settings and take care of. But, uh, so all of a sudden, our support team was just inundated with dozens of tickets, uh, of anchor customers and keeper customers that were super excited about getting this up and running. So, uh, I would say overwhelmingly positive.

Tal Ben Bassat: That our, our community was booming. And I went actually to a to a conference, uh, two conferences last, last week. And when they heard there was the integration, people were like, wow, it was crazy because to be honest, there [00:14:30] is so much love out there to keep her. It's it's it's humbling experience to see that really. So that's kudos for Ben Wright in the team. Amazing love for keeper. It's it's something you don't see a lot. Um and and it's it's super exciting you know to partner and to do this together.

Alicia Katz Pollock: What's something that you admire about each other's approach to problem solving and doing development?

Ben Stein : Uh, well, I would say a big, fat compliment [00:15:00] on me. So I'll take this one. Um, I, I like just saying that anchor is good at marketing is such a disservice to what this means, but it's sort of. In order to be good at marketing, you need to, like, actually understand your customers and actually listen to your customers and actually, like, put things out into the world that they enjoy and resonate with. And it sort of it all comes back to what Tom was mentioning earlier, which is like we listen to our customers, we keep our customers happy, we keep our prospects happy, and we don't try to sell to you. We try to be partners. [00:15:30] And I think that like has overwhelmingly shown through like partnership, both in terms of their customer base and partnership in terms of this relationship right here. So I think Anker has done just an incredibly well job positioning themselves as the like, the thing you should use when you need to collect money from your customers and then actually delivering on that promise.

Tal Ben Bassat: Well, for me, it's it's, uh, there is some sort of, um. Hebrews clients [00:16:00] are in love with the company, with the product. Right? It's something you don't see a lot. Many people see that, you know, they're they're sufferers. Okay. It's my software. There is a different type of of and you can really I mean, you know what I'm probably talking about Alicia, but it's like there is something it's something else. I don't know how to call it a cult, but it's it's like people are really like, you know, it's a thing. It's kind of. It feels like it's part of their, you know, character. Um, I don't know. I mean, Ben [00:16:30] and the team managed to do that. I think it's an amazing achievement because and I guess probably it's also connected to the fact that, you know, you also interact with your clients. But to be able to get to this level of, of, of appreciation, but by your clients, um, it's admirable and I think that this is something that, you know, every, every company should aspire to, because at the end of the day, um, you know, we need to listen to what our community wants, what they need, and it's our responsibility to deliver on that. [00:17:00] Um, otherwise, we also don't have a right of existence. Right.

Alicia Katz Pollock: That's really beautiful. It's like Reese's peanut butter cups. You guys are like chocolate and peanut butter and chocolate.

Ben Stein : Aptly be either chocolate or peanut butter.

Alicia Katz Pollock: All right. Um, so I'm also curious about kind of the, the industry and development as well. So let me steer the conversation in that direction a little bit. So what surprised you during [00:17:30] the development of the integration?

Ben Stein : Hmm. It's an interesting question, I think. Um, they're like, I think it surprised me how involved it was, which is like like this is our first ever integration, so maybe it should not have surprised us, but, uh, but anchor sort of took the whole process very seriously. It wasn't trying to, like, slap something together and say, we have an integration. It's like, really think methodically through what the customer wants to do here and then what is required of us. And so we had to like, make modifications [00:18:00] to our API and release new endpoints to make sure that that what anchor wanted to be able to achieve was something that we could achieve. So, so definitely, um, I'm optimistic that now that we have have that in place that that we sort of the N plus first improvements will will be smoother, but definitely, uh, just setting up an integration if you want to do it right is is not a trivial endeavor. Sure.

Tal Ben Bassat: Yeah. And I want to say that I also want to give a big, big, big shout out to our product team to Guy and Danny [00:18:30] from the product team guys ahead of product. Um, they did an amazing job. They literally spoke to a lot of keepers, clients to understand how they expect this to be like. So they were able then to go and talk to the team. Now you need to understand this is as Ben said, it's the first integration they have. And we are also kind of, you know, we just released our public API just now and but we still kind of going and learning how we can do things the best way. And and the team keepers team was [00:19:00] so welcoming, you know, and so dare to communicate with us and also with our quirks because we always like, you know, we like to do things really, really good and the best way and very deep. And not to give people like half baked features or integrations. We just we don't accept that. We our approach is to deliver the best we can. Um, and and Ben's team was they were amazing. They collaborated. They they listened. They, they, you know, pushed us as well for, for, for additional things. And, and [00:19:30] it's amazing from, you know, to be able to communicate with a company like that because you understand you have a counterpart that, you know, has the same standards. And that is a really important thing for us when we think about the partnership with, uh, with another, uh, software company.

Alicia Katz Pollock: Excellent. Nice. Now, do you see this as part as part of a bigger shift towards platform consolidation, or is this more about two modular, best in class apps working together?

Tal Ben Bassat: I [00:20:00] want to take this one. And if it's okay, I'll start. Um, there is a lot of, a lot of, a lot of discussions about, uh, about consolidations. Um, and, and if anyone that has been enough in the game, uh, a game of buying products or services, by the way, or creating them knows that you always have your core in your core. You can be the best, right? Whenever you start to go [00:20:30] outside of your core, then you need to stop. Start actually taking some sort of, uh, adjustments or, you know, um, compromises and things like that. No one can do everything perfect. Even if you think about the big tech companies, right? No one. It's not possible because as a business, again, even as a accounting firm, you can be amazing in tech. So amazing in cash. So but it's very difficult to be amazing in everything. So our approach on anchor is not to give people, for example, uh, you [00:21:00] know, um, half baked, uh, I don't know, like CRM experience or half baked for, uh, you know, project management or practice management experience because it will not be as good keeper spending years developing their product.

Tal Ben Bassat: So we developed anchor, which is amazing. It actually captures a very a huge part of the value chain. Basically, the entire value chain from proposal to the relationship management, the financial relationship management. We do that the best. [00:21:30] Okay. And then we integrate seamlessly to the best in the project management the best in the CRM. Because then you're really going to get the best of everything. And people experience that. And people have a lot of hit, a lot of promises. But then when they meet reality, they understand it's just not possible. So my point of view is you need to be the best in what you do, maybe a little bit on the sides, but very just on the little bit on the edges, and then really have amazing integrations to the other best players in their parts [00:22:00] of the, of the industry. Um, amazing integration. So your clients will have a seamless experience. And the rule is literally to think about to what extent you can you can you can take things in one tool, right? So billing is one aspect. Project management is one aspect. Right. Uh, and so on.

Ben Stein : Yeah. And just to add to this, I will say this is my turn to use accountant's two favorite words. It depends. I think when you think about why you want a [00:22:30] best of breed tool versus why you want everything all in one tool, I think, like obviously like platonic perfect software does everything all in one tool. And so we're sort of making concessions to reality to not have that. Um, but I think the big thing upon which should I have Best of breed or should I have, uh, all in one? The big thing upon which that depends is like, first, how complicated is the thing you're trying to do? And second, how well integrated can two solutions be? [00:23:00] Um, so like for us, for example, we do client communications give like one example. Um, and this is like tied to the month end review. So it's like the month end review kicks off client communications. And then client communications kicks off other actions through the app that may kick off other workflow experiences may tie into emails. And so this is like so deeply coupled to each other that imagining building a like building an integration where we're like sending our transaction questions to this one system and then that's sending [00:23:30] it to another system, like it ends up the maintenance of that ends up being so hard that it's just better to have a single, cohesive, integrated system.

Ben Stein : And you like, can't you can't imagine a good functioning ecosystem. That's like why people end up with like five different portal links on their websites. But I think something like, uh, something like billing. Billing is like fairly isolated now. It's not like it's not completely isolated to the point. I mean, the whole reason we built integration is like there's very valuable, very valuable, [00:24:00] uh, like things that billing kicks off and that can kick off billing. But these are like discrete, knowable points. Um, and so with that, you can build very good integrations, and if you can build a very good integration and you recognize how complicated billing is, building is like enormously complex, I'm sure. Tall. Anyone on their team could talk. Talk your ear off on all the edge cases here. It's like, okay, if we don't have to build that. And it can still be a good experience for customers with a, with a with a good integration. That's when something [00:24:30] like best of breed point solutions makes more sense than all in one. And I think that's that's clearly the case here.

Alicia Katz Pollock: And that really just dovetails nicely off of Intuit's approach to how they've built the software. Because I, you know, a long standing joke here at the unofficial QuickBooks accountants podcast is that Qbo is a multifunction printer where it can it can print and it can copy and it can fax, but it doesn't do any of them really, really well. And that's why we have this whole entire ecosystem built up around [00:25:00] it, where the rudimentary task management is there and the rudimentary invoicing is there. But, you know, the whole proposals are not there. And the whole actual task management with, um, Resource allocation is not there. And so being able to I mean, this is a compliment to intuit that they've had the foresight to keep the to really build out a robust developer network. And so it's really nice seeing now that it's [00:25:30] not just a hub with the with Intuit in the middle, that there's connections now happening between the apps themselves like the rest of the wheel.

Ben Stein : I think that's a really nice analogy. Um, I think there's a line I don't know who who to attribute to when I read it on the internet somewhere. I think about it all the time. Reality has a surprising amount of detail. Um, so I think that it feels very true here.

Alicia Katz Pollock: So taking that one step further, [00:26:00] um, Hector and I just recently did an episode called APIs Gone Ape about the new announcement that Intuit just had about changing their API and developer Program and charging by number of customers and changing some of the resources available. How does that affect you?

Ben Stein : Yeah, I'm happy to to take this one. Um, I certainly can. Certainly. It's something we've done a lot of internal analysis on. Um, so I [00:26:30] think the first thing to get out of the way first is based on the internal analysis we've done, we don't think this is going to require us to change prices. So it's not going to be something I know everyone's worried about. Does this mean that the developers are going to have to raise prices on their customers? From what I see right now, the answer is no. And so, so obviously, like the easy naive take that may also be the correct take is like this is just like Intuit turning the screws on their on their like developer ecosystem and starting to sort of monetize and take a rake. [00:27:00] Um, and that may very well be the case. I think the, the optimistic assumption, the thing I'm like, actually potentially excited about is maybe this gives Intuit resources to continue furthering the development of the actual API. Like, there are so many things that we've wanted from the API that don't exist that would allow us to deliver a better solution to our customers. And the optimistic assumption is, now that Intuit has a financial resource and a financial motivation to actually go and make those changes and improve the API. So I think there's a world in which [00:27:30] this actually makes things better. But of course, we'll have to wait and see.

Alicia Katz Pollock: I'm curious to know, like what? What in the APIs do you want to see change?

Ben Stein : I think the sort of biggest one that would be helpful for us is the reconciliations API. So right now we sort of show you the date of the last reconciled transaction. Be great. If we could just have a reconciliation run through QuickBooks, and then that triggers the completion of a task inside keeper and then sends over the reconciliation report. That's like one example, but reconciliations is not available [00:28:00] in the in the API directly. So actually I have a conversation next week where we're talking with the like with folks in the actual Intuit developer universe, like like with Intuit. Com intercom emails. It's like, maybe this is a maybe this is actual. Change, change change. And we can we can expect to see some of these come. So very very early to see that. But that would be one example.

Alicia Katz Pollock: Right. Well I appreciate your optimism because that was my thought too, is that if they're going to charge you guys then you should be getting better support. And. All [00:28:30] the things to make it happen. And how about for you?

Tal Ben Bassat: We didn't uh, we actually took a few, a few actions to allow us to keep our pricing. Um, we did actually last year, and when we moved all of our clients to, uh, to our three day fast, and we took a few actions that will allow us to keep the price even longer. Um, so that also kind of protecting us from that as well. Um, [00:29:00] we try to maintain the $5 and it comes up a lot, um, because we price has not changed in the past. I want to say 4 or 5 years. We're not also not really planning to change it anytime soon. And, uh, it's kind of part of how we see things. And because of the what the actions we took, it's not really affecting us for now.

Alicia Katz Pollock: Okay. Excellent. Well, I'm I'm.

Tal Ben Bassat: Too much high. It will affect everybody eventually. So.

Alicia Katz Pollock: All right, so it remains to see how it plays out. [00:29:30] But I'm glad to know that it's not enough of a deterrent that it's going to trickle down to us. So I mean, that of course remains to be seen, but I'm glad to know that it's not that big an issue because we were we were kind of concerned. All right. Well, let me ask one last question of the two of you. If you had one wish for the future of accounting technology, what would it be?

Tal Ben Bassat: It's a good one.

Ben Stein : Um, [00:30:00] I'll go with one that I think might be common amongst a lot of accountants, especially as relevant to some of our product development. Uh, more universal support for robust API connections to banks.

Alicia Katz Pollock: Yeah, some banks have it and some banks don't. And some banks have it sometimes, but not other times.

Ben Stein : Like I'd love to see like the the Second National Bank of Omaha like have a good robust API that you could connect to [00:30:30] that pulls transactions, pulls statements, pulls uh balances and never breaks. That would be that would be an amazing thing for the NHS.

Alicia Katz Pollock: Images. Oh my God please. The deposit slips and check images.

Ben Stein : Let's see if we can crawl before we walk around.

Alicia Katz Pollock: Oh, that's a great I'm totally I support your vision on that one. And tell what wish for the future of accounting technology for you.

Tal Ben Bassat: I feel that it's kind of on the same area, but I think it's also about connectivity. I think that at the end of the day, [00:31:00] you know, especially, you know, with AI coming out and all those things, connectivity between apps. So taking the barriers, taking out everybody like. Creating a real ecosystem that everybody can kind of interact with whatever they want. So taking off the barriers of no APIs because a lot of the old school software there, they really don't have APIs. And and at the end of the day, I feel that I think it's coming up with the new companies that come out. So a lot of the new companies, they build everything like the ability [00:31:30] to connect to other tools because they understand it's an ecosystem game. Um, and I think over time, those that will not open their gates to, to, to APIs and to integrations will, will have more challenges. And I feel that if this will happen, it'd be amazing. I don't know, maybe like some sort of, uh, eventually people will have some sort of an area in which they can actually have all the software in one place connect to each other and really to bring the value from wherever you can.

Alicia Katz Pollock: All right. Excellent. So we also have a conference [00:32:00] coming up. We actually get to all see each other in just a week or so. Scaling new heights in Orlando is coming up at the end of June, and all three of us are sponsors. Royal wise has a booth and you do as well. Um, for royal wise, we've got some high jinks going on. We are bringing 100 blue tutus for two two Tuesday and trying to get everybody in tutus. So I guarantee I'm going to show up at your booth with tutus [00:32:30] for youse.

Tal Ben Bassat: Definitely.

Alicia Katz Pollock: And we have a cabana number nine on Wednesday for an end of event pool party. And what fun are you planning this year?

Ben Stein : Uh, well, we are, uh, so, so little, like, background, uh, sausage making. So there's usually another show called BK that maybe some, some listeners, uh, have attended in the past and that's not happening this year. But one of the things we did at every BK was [00:33:00] a show called keep was an event called Keeper Karaoke. And so we are bringing Keeper Karaoke to I believe It's New Heights.

Tal Ben Bassat: I remember that was actually the last one the last week. And what you had, it was super fun.

Ben Stein : Karaoke is dead. Long live karaoke!

Alicia Katz Pollock: I'm excited for that. I have a couple go to karaoke songs, so we'll have to pick one. So, you know, I'll be on stage.

Ben Stein : It's Monday so we won't see it won't be in the in the blue tutu.

Alicia Katz Pollock: That's okay. [00:33:30]

Tal Ben Bassat: We we actually have. As always, we have a few surprises. We prepare. As you know, we always like to kind of do different things. Um, I think that this is going to be very, very interesting for everybody when they see anchor and also some collaborations, of course. And, uh, again, a lot of a lot of ways to make everybody have a good time.

Alicia Katz Pollock: Well, thank you both very, very much for coming on the show and helping us [00:34:00] get excited about these new opportunities, and I can't wait to go back to my own anchor and my own keeper and go ahead and try this out and get it set up myself so I know what I'm doing all weekend.

Ben Stein : So awesome. Well, I'm sure I speak for both of us and saying if you need any support on the weekend and you know how to find us.

Tal Ben Bassat: Definitely for sure.

Alicia Katz Pollock: Okay, well, Ben Stein and Tal Ben Basat, thank you both for joining the unofficial QuickBooks accountants [00:34:30] podcast, and we will see you at Scaling New Heights.

Tal Ben Bassat: Thank you for having us, Alicia.

Ben Stein : Thank you. Alicia.

Alicia Katz Pollock: Now, for our listeners who are not already anchor or keeper users, if you would go to our show notes and click the link in our show notes when you go check them out, that will help them know that you found out about them from this podcast.