a 卡塔尔世界杯常规比赛时间 flash briefing
.
what to start doing today to be fully prepared for next tax season… and beyond.
hosted by seth fineberg, accountantsforward
with guests chad davis, kellie parks, and kenji kuramoto
get seth fineberg’s analysis and commentary here
top takeaways
- artificial intelligence.
- work smarter, not harder.
- managing tech expenses.
- the fast track to rapid adoption.
- choosing the right tech for your firm’s needs today and tomorrow.
panel of experts
chad davis, cpa, cma, owner, liveca
chad davis is a cpa and a co-founder of liveca llp in canada. he co-hosted the automationtown podcast and has a weekly newsletter sharing solutions to common tech issues for accountants. he’s also in his sixth year traveling full-time with his family in their rv across canada and the usa.
kellie parks, cpb, cloud accounting process and automation builder, calmwaters
parks is a certified professional bookkeeper and founder of calmwaters cloud accounting. she is passionate about all things online accounting and apps that create a robust cloud accounting ecosystem. parks is an innovator, adopting cloud financial technology for her own business in 2009, and in 2012, as soon as it came to canada, parks adopted qbo and has not looked back. she is qbo advanced pro certified, freshbooks certified, dext certified, wagepoint certified, qbtime certified, a hubdoc advanced partner, plooto partner, ignition partner, 17hats partner, karbon partner, pandadoc partner, zoom partner, reply partner, and an acuity partner.
kenji kuramoto, ceo, founder, acuity
kuramoto is the founder and ceo of acuity, which builds and maintains financial functions for innovative entrepreneurs. through acuity, he’s provided thousands of companies with a full range of financial solutions, from high-level strategic financial counsel through its fractional cfo practice, all the way to virtualized bookkeeping and tax services. prior to acuity, kuramoto was the cfo of an inc. 5000 tech company and worked in the assurance practice at arthur andersen.
more seth fineberg: remembering john stokdyk | who’s in control? you? or your clients? | time management rule #1 for accountants | plan to go ‘live’ post tax season | why vc is a bigger threat than ai | what does taking control of your firm mean? | accountants need each other more than ever | marchternity: just say ‘no’ | some thoughts on in-person events | so you think you know accountants? | what bogs down accountants
more podcasts and videos: peter margaritis: the power skills every accountant needs | joe montgomery: find the sweet spot of the right clients, right services and right prices | marie green: your bad apples are ruining you | megan genest tarnow: hire for curiosity rather than compliance | clayton oates: one way to keep clients for life | randy crabtree: follow these three rules to keep employees happy | erik solbakken: yes, you can work less and make more | donny shimamoto: future firm growth requires a mindshift |
exclusively for pro members.log in here or 2022世界杯足球排名 today.
transcript (only lightly edited)
rick: hi, my name is rick telberg for 卡塔尔世界杯常规比赛时间 with a distinguished panel of guests today. our moderator will be seth fineberg. some of our best friends are here today: kenji kuramoto, kellie parks, and chad david. with that, i will turn it over to seth.
seth: kenji kuramoto, kellie parks, chad davis, to me are just three of the individuals who i’ve gotten to know personally, but also who, again, are running their own practices. really have really jumped in with tech and really kind of taken it by the throat and going, “all right, i’m going to figure this out. i know that my clients really need me to be on top of this. i’m going to run my practice in such a way that is considered by many of the accounting masses tech-forward.” don’t feel too intimidated. everyone’s at their own level of the adoption curve and this can’t be overstated too much.
i’ve been overseeing the profession now for over 20 years, both as technology editor of accounting today and also as the editor of accounting web. in that time, i continued to talk to firms pretty regularly. the rate of change, the pace of change really has never been– and maybe this is redundant, but it’s never been more intense than it has now. not just that, we’ve never had the sheer amount of technological decisions, the impact that technology has had on all of your practices and all the practices out there today has never been what it is before.
when i started it was still all very much predominantly desktop-based, and even that you had a finite amount of actual software to work on, and platforms, and systems. you knew who it was, you knew your practice management, you had a few choices there. your accounting work that you did, the payroll work that you did, the external work that you did, and things to run your practice were pretty finite. then along came the cloud and apps, and that really blew the doors open. now we’re talking about the new level of automation with ai and it has everyone in a tizzy, except the folks in this room. we’re going to get to all of that. we want this to be an actual discussion.
we’re definitely not going to get to everything that we need to in our hour of power here, but i really thank you all for joining us, for taking time out of your day. as mentioned in the promotions, this is not for cpe, it is a non-sponsored event. we did that with purpose because in my view– again, no disrespect to a lot of the vendors who are out there who are doing things, were sponsoring a lot of these chats, who are doing things for cpe it’s great. i want them to be communicating with you all in a way that is beneficial and meaningful to you.
this was a conscious choice by myself and rick to have a chat like this that has no agenda behind it other than getting you the information we feel that you need. starting the kinds of discussions around technology adoption that you need for your firm and for your work and therefore non-influence in any way. we can talk about a vendor or two if we need to. nobody’s here necessarily in the room. let’s jump into it. again, any questions, please throw them into the chat here. we will get to them. we hope to get to them, but i’ve got my own list of questions here. real quick introductions guys and then let’s get into it. kenji, why don’t you kick it off?
kenji: sure. thanks-
seth: quick snapshot of you for those who don’t know you, and then kellie, and then chad.
kenji: sounds good. seth, rick, thanks for having us. kenji, i am with the firm acuity. we are essentially an outsourced accounting firm based in the us headquartered in atlanta, georgia. our service lines are basically predominantly cas, outsource cfo, outsource controller, and kind of a virtual bookkeeping-off solution along with a small tax practice. we typically focus in target working with very, very high-growth entrepreneurs.
those tend to be saas-based technology companies, e-commerce, crypto, some creative services, things like that. that gives you an idea about the service lines, who we work with typically as clients. then we have a team of about 150 employees. about 100 of them are in the us. the rest are international into the philippines or caribbean. that’ll give you a little bit of a sense of how we approach all this tech from a a firm of our size and who we’re serving.
seth: excellent. thanks, kellie. go.
kellie: okay. i’m kellie parks of calmwaters cloud accounting. i am a micro firm up here in canada. i generally deal with multi-entity corporations. i am taking on now– i’m taking a break until the spring, and then i will be taking on the accounting firm’s books. currently, i do hot masses for some of the accounting firms. i do more project work than mrr, so the hot mess. i have a couple accounting firms. i’m doing their books and i love that. i’ve decided that’s my new niche come the spring. that’s kind of fun. i’m gearing up for that. i love tech. i consider myself tech-forward but human-centric. there we go. that’s me.
seth: excellent.
kellie: oh, i deal with us markets too. i’m canadian-based, but i’m also a us proadvisor.
seth: yes, yes you are. thank you, kellie. chad, take it away buddy.
chad david: i’m not a us proadvisor, but i am canadian.
seth: no, you’re not.
chad: we’ve grown predominantly as a cpa firm in canada from just my business partner and i up to over 110 people, and then back down to about 60 or 70. that’s a really interesting story, sometime we can talk about. intentionally my role has been around the technology adoption both of our team throughout that process and our customers. for every new customer that’s ever come on board with us, i’ve been involved in creating new financial tech stacks for them. that really led to a really interesting introduction to a dev team that we created inside of our accounting firm.
so working through automations, coding stuff for clients, and then we ripped that out of the firm. there’s all kinds of trying things coming back to basics with a real focus on what the customer needs. i think i’m a little bit addicted to the technology side of things, but like kellie said, the eyes on the prize with what customers and your team really needs to move forward in their career and in their business. that’s been where i’ve been spending most of my time. also six months in canada, six months in the us out of the year.
seth: driving across the continent in your rv. i hope it’s holding up well, chad.
chad: it’s holding up.
seth: i’m glad.
kellie: i modeled myself after chad that i want to spend six months not in canada either, so i followed him to the states. [laughter]
chad: it’s warmer in the us and in the winter.
seth: very cool.
chad: thanks for having us.
seth: thanks for being here. we’re already getting some questions coming in. i am going to get to them. i just wanted to kick off with you guys just saying, look, when it comes to making these technology decisions, you guys talked to other practitioners as well. what’s the most common misstep that firms are taking or making these days in regards to their technology decisions. what comes up the most where they’re just, yes, hey probably not doing that right. kellie, why don’t you start off?
kellie: oh, sometimes i see that people go after what the shiniest thing is, what their friends are doing.
seth: the new and shiny. yes.
kellie: what has the big names out there that possibly maybe solving a problem that they don’t even have, or that they’re not going to interact with properly? they’re looking to technology that isn’t solving their problem. they’re going shiny. your friends running around and trying new things, and you’re just spinning your wheels if you don’t have the same problems that they do. i think that then you’re bringing in too much tech.
part of it is you can just adopt tech that you absolutely don’t need and that maybe isn’t even fun that could actually take you out of your workflow as well. it could break processes that are having well. i think being more measured in what you’re going to bring on that suits you, and making sure not just the app has the features but that the ux and the ui makes you want to interact with it as well. i think so– that’s what i got.
seth: kenji, what do you hearing? similar to kellie, people calling from the new and shiny, maybe you even guilty of that yourself early on.
kenji: sure.
seth: not throwing you under the bus or anything. [laughs].
kenji: i’ve been very guilty of chasing the new and shiny or next squirrel or whatever it is. i think that there’s probably some of us who are in that spot like, “oh, what’s the newest, craziest thing?” i would bet the three of us panelists are probably like that. as you hear more about us we’re technology forward. i also see a lot of accountants who have not taken that first step, are a little bit stuck because i think there’s needs to be an acknowledgment of the ecosystem it’s freaking huge these days. it’s blown up. it’s massive.
when you look at how many tech solutions are i think folks are feeling a little flatfooted. i think it’s all hard to get started because you’re going– there’s so many choices out there. i see that being a little bit paralyzed of like i’m not even exactly sure which way to go here. how do i attack this massive ecosystem, this huge market? i think that’s a place where, and i think very, very, very understandably people get stuck there. i get it like you’re just like, “where do i even start? how do i boil the ocean or eat this elephant here? i think that’s a tough spot to be in.
seth: not that we’re boiling any elephants or drinking oceans, people. [laughs]
kenji: no. no those things. let’s hope we get those … the right way and make sure we don’t get in trouble. i think that’s a spot where folks are watching and not taking enough action. we’ll probably talk about that in a little bit about steps and things people can take. i think you’re a little flat footed. that’s the one i’m concerned about with some practitioners and firm owners they’re just a little stuck but i get why they’re.
seth: chad, this is something you want to weigh in on and just in terms of some of the common missteps. we’re getting some good questions in i want to get to them.
chad: true. i think common missteps for me relate back to– you can think about starting like kenji talked about. it’s hard sometimes to start, you’re not sure where to go. a lot of firms have started, they’ve implemented something, and then they might get stuck. did they choose the right one? should i switch practice management firms? should i switch my email provider? should i switch this? what i’m seeing is that a lot of the maybe the firm’s that i’m running around with or speak to they make those decisions in smaller silos.
maybe the ownership and maybe the management level, but it’s not as deep as it could be. really identifying the issues that pop up that will give you more benefits to actually switching or to maybe leaning into more training. to make the product actually work better is somewhat of a common theme. i think that there’s a lot of options that you can do to mitigate this, and that’s why i’ve been on a big kick for continual training of your team and getting-
seth: no matter what size firm you are you can–
chad: that’s right and the place look different at different levels.
seth: oh, sure.
chad: i just think i see too many people not investing in that feedback loop that’s standardized and objective versus the touchy-feely subjective type of feedback that we typically get from a lot of people. organizing it, keeping track of it, and then acting on it. i don’t see a lot of people doing that.
seth: a great question came in about average spending, and i’m going to throw that over to rick in a minute. in terms of just getting started, this is the whole point. it’s like take that step. great. you got your accounting platform. i know that we’re going to get to some actual tech stack discussions, but it does bear some focus on the getting started the overall process and selection of tech.
you got your qbo, you got your zero, you got your excel, your tax software. for firms that aren’t using, necessarily anything much beyond those, how do they get started? for this, i haven’t heard discussions or some of our good buddy jason stats that actually brought up the idea of like, yes, you probably pretty much need to get started with a practice management system and that’s your base. for some of us out there and if that makes sense, kellie go.
seth: i just wanted to bring it up because you brought up a very good point, and i saw a very good discussion and participate in that discussion about that very point. i was like, well, there’s some firms that don’t necessarily want to start with a practice management system. they don’t feel like they’re at that level. they have their core tech that they work on, but it’s that even worth discussing if you’re a six-person firm. i don’t know.
kellie: oh, yes.
seth: this is what we want to talk about here.
kenji: i’ll admit, i’m in stats corner on this one because when you think about workflow and your own internal processes or processes for the canadians. when we think about all of us have those in our firm, we have challenges there, it’s going to dominate the way in which we work. i think that’s where there’s low-hanging fruit, typically. we think about using technology to help assist. startups, we work with a lot of technology startups, and you often hear that some of the best startups were built to solve a problem that the founders had, something very near and personal. when you’re always solving a problem that you have, and trust me if we go and ask our team they will tell you about all the problems we’ve got in workflow.
seth: got to communicate.
k: i think it’s a good point by, stats. i think it’s fairly obvious. it’s a very good starting point. it may not be that for everybody, but it’s got to be at least in some of the first few starting points of what workflow system is going to help facilitate the work you do inside your firm and help your team members. i think that’s pretty high up there, in my opinion.
seth: good way to get started, i think. yes.
chad: you mentioned something about cost. i went to our income statement and we’re currently paying $350 canadian, so $280, $290, whatever us per person right now at the level we’re at now. i think the price goes down the more people you have typically but that’s where we’re at. it wasn’t always like that. i looked back five years and it was maybe half that.
seth: would you say it’s a percentage of your revenue, chad, or you’re like, hey, we budget?
chad: no, it’s seats. it’s butts in seats in terms of pricing like that. again, it’s different for every company, but i do like– we’re talking about that first version of starting out. it’s how can i organize myself such that i don’t operate in a silo?
seth: yes.
chad: it doesn’t matter if you’re two people. it’s still a silo if you both don’t share your information. sharing–
seth: oh, 100% it could feel like you’re at a much larger firm.
chad: for me personally, it’s how do i share my emails in a way that allow us to comment and to work on those things without a minimal interruption.
seth: yes, communication. very key. on the cost thing again, and then we got wonderful questions flowing in. please keep them coming. people, we’re going to try to get to them all. rick, this might be for you because cpatrendlines they keep quite a number of statistics and do a lot of research out there. it was a really great question about just approximately the average percentage of revenue spending on tech for cpa firm. again you could break it down by size, but it’s a pretty, pretty broad question. do you have something that you can weigh in on that, mr. telberg?
rick: sure. i’m thinking through the accounting firm operations and technology survey now. so far we can tell you that only about 11 or 12% of the firms report having any budget set aside for that wall. let me see if i can come up with-
seth: there’s some stats here that rick threw in the chat to everyone, so everyone take a look at that so we can move on but really, really good stuff. about an accounting firm thinking strategically when change in new tech is happening so fast. this is a point i wanted to make but also roll into the fact that coupled with the challenge that firms really need to cut through a lot of hype around being modern and being more tech-forward. a lot of that just coming from a variety of entities, some of it from the vendor community, some of it from industry organizations that are out there with a certain number of initials attached to them. how do you cut through, how do you get strategic, kenji?
kenji: i think it starts with, yes, there’s always going to be a lot of buzzwords. it’s putting some meaning behind those. what does that mean strategically for you? if you want to cut to the hype of what it means being modern or more forward-
seth: there’s a lot of it.
kenji: -there’s a lot of it out there. we always talk about it’s always panels, and at every convention or conference we go to. it’s oftentimes that gets held up or idolized like, wow, look at this tech-forward or modern firm. i think that the really behind that strategically is, are we being thoughtful about how we’re solving clear problems? i think the easiest place to go is to our team and to our clients.
what does it mean to help serve them better? that could mean using some technology that improves communication. we all know that all of us that’s the dominant issue most of us have with our clients is there’s bad communication. does something improve the communication flow, the workflow there? does something help reduce the amount of time that team members have to spend on manual processes?
i like to think of it in terms of what tech can we use to attract more clients, attract more team members who go, “gosh, i want to work at a firm that’s made an investment in tools.” or even a client who says, “oh, there’s finally an accountant out there who’s working on some of the same platforms i am.” i think that helps drive that forward and cut through the language, and i think it helps retention as well too. like chad mentioned, when you invest in training in particular but good tools for team members, they understand that.
there is a million places for accountants today to go work. it’s a great time to be an accountant. they have their pick of a litter of where they want to work, they want to open up their own shop. i tend to think about it in terms of what’s going to go out attract great people to our firm, what’s going to retain them. you better believe you got to put in place some good technology and some good training around them. that’s meaningful to them. that helps their day-to-day lives.
seth: if you’re thinking even about transition or succession. if you’re going to sell your firm, what do you look like? not just your client list, but do you even have some of the basic things that you need to even– this is why this is pressure to look modern and be modern. it’s like, “well, yes, i would like to maybe think about selling my firm in the next five or 10 years. what do i look like? am i using the best stuff?”
chad: i got something for that, seth.
seth: yes, please.
chad: i was chatting to a new firm owner yesterday afternoon. his name is jeff. he has a firm that’s specifically selling a product now. that product is its core. that’s how they’re marketing, that’s how they’re attracting customers like kenji said. the backend tech is to be desired. he’s putting a lot of effort into how do i present this, how do i gather the information, how do i make it as seamless as possible for my team. that’s a great example of what kenji said because he’s cutting through the hype for the things that are strategic for him and his firm. not trying to play into the nice new, cool, shiny thing.
i love that approach and that’s how we’ve looked at where we put our effort. because admittedly we’re still using tech that we used 10 years ago because it works. there’s new shinier things out there, but it’s not as important as the other things we’re working on like getting better data of our customers and using that to do stuff. i think there’s a prioritization skillset that firm owners have to have in order to keep people happy and their bottom line a little bit happy too.
seth: kellie, i know you’re along there. again, there’s two-fold discussion going on here. there is your process of selection and trying to cut through a lot of the clutter. then there’s also you have to be mindful about your present and your future when it comes to not only maybe selling your firm but also staffing up. you want to attract the right people. you want to look like the firm that, “yes, they’re using things that i could get my head around and that really shows that they’re thinking of their clients, about efficiency.” sorry, kel, go.
kellie: i switched practice management apps a couple of years ago. it is only myself and one team member. it’s just the two of us. i could have made a unilateral decision so it was time to switch. the type of work that i was doing, it was time to move on from what i was. there was no way that i wasn’t going to make that decision with marissa. i had a problem that needed to be solved. what i was using was fine, but it wasn’t working as well as i wanted to communicate with my clients more than anything.
then the second step was i did not make that leap without her wanting to be a part of the technology that i was looking at, so we had shortlisted it. one, it solved a problem, two involved a team member. then the third thing is, i also don’t think we need to go for the cheapest options. sometimes a cheaper option is going to cost you more in the long run. it should be part of your decision matrix, but it shouldn’t be necessarily number one in that decision matrix.
seth: again, this flows well into the tech stack discussion. we have all heard that you need the right tech stack. you’ve got people out there preaching about– i’m going to name-drop again. i hope you don’t mind with someone like dawn brolin who’s really, really bangs on about you have to get the right stack and she’s got her starting lineup. that might not be the best in terms of vendor mix or product mix for everyone. with any tech discussion the issue of tech stack rises. eyes off and glaze over, what should really be the base? what’s essential for firms today meaning the firms that are basically like y’all just doing tax, doing bookkeeping work, and does time and billing come into that as well? what’s the tech stack, chad?
chad: you’re asking the canadian tax person who has no relevance to the americans here.
seth: just in general, in general, you’re thinking about tech stack. we’re being country neutral.
chad: there’s the big five. you’ve got your practice management, your tax, the actual accounting software you’re using, the document management stuff, and then communication. if you think about those there are a lot of options.
seth: do time and billing not–?
chad: yes. for us, our time and billing isn’t integrated with our tax software. it’s separate because we use it in so many different areas of the firm. i’ve found it more valuable to do that because we’re not billing based on time and materials. we’re billing off of a budgeted fixed cost every month that’s the same and it had no correlation. as long as we got our metrics that were important to us i’m super happy. that’s why i never really go into, “hey, here’s the practice management system for you. here’s the tax system for you.”
in canada, what was really important for us was to use an online tax system, and the only one that had been around for a long time was cch ifirm, so that’s what we use for all of our– that’s our tax returns. since day one on the document management we’ve been using dropbox. why do we not use anything else? we tried. it just failed. different people didn’t want to use things. for decades dropbox has been around and it’s been fine. literally, like knock on wood, not one issue in like a decade, and tomorrow it’s going to all go to crap. it’s what works. to the point earlier, why switch something that isn’t causing any problems?
we use karbon for all of our project management work and our email communications. that has single-handedly been the biggest upgrade in our ability to grow from the communication perspective because now we can talk about emails, and assign them to jobs, and have full visibility. to me, that unlocked more potential wins that anything else we have ever done tech-wise. then practice management, document management, and communication we always been on google. we just integrate that with everything that we’re using, so that works for the karbon, that works with all of our google docs stuff.
again, it works for us. it doesn’t mean it’s the best or it’s going to work, but when we doubled in all the big automation stuff, google’s pretty forefront there back a few years ago. now microsoft’s winning there, but we never had any issues. i’m happy with the stack where it is now. will we make any changes? probably not for a little while until we went into problems.
seth: yes, and then you’ve got your core accounting. i know you do a fair amount of compliance work, and then everything else that supports that. kellie, anything to add in terms of tech stack essentials? is it as important enough to people get a little stressed about like, “do i have the right mix?” i don’t know.
kellie: i want to say two things. chad, pretty much covered them except possibly one exception that i would add, and that i think a good solid payment platform. if you want to do ap for your clients which has great– the amount of money you can make on the actual lift is amazing as long as 100% the only thing you sell is the outcome of how seamless it’s going to be.
don’t sell how little time is going to take. tell them how easy, and so adding a payment processing platform i think is the only thing that i would add to chad. yes, practice– oh, chad didn’t mention it, i know he’s big on it though, is an integrator to tie it all together. that would be something like zapier or make, i think is something. i think in the online scheduler and a solid form builder, forms do so much work for me. i think a solid form builder, but now i’m really getting into the weeds of what the little things are.
seth: all right. having an integrator like a zapier or make as your api choice.
kellie: i’m not even a big user. as chad and i were talking about yesterday, i am not the world’s biggest zapier person.
kellie: you know what? the little things that zapier does for me all day long is great. whether it’s back-office work or there’s a lot of things that zapier can do within– i know everybody wants to do all the air table stuff and do all of the magic and all of this, but there’s a lot of direct integrations from– especially if you have multi-entity clients, that zapier can take the information from one file and feed it into another.
i think an integrator app– and don’t be afraid of them. that’s a big part of the tech, is being afraid of it, but even zapier, a lot of this stuff is prebuilt. put in one app and ask it about the other one and away you go. that was a really long version of saying everything chad said, plus an integrator, and possibly adding accounts payable your client products.
seth: an ap solution. there’s a lot out there, folks. kenji, anything to add into the tech stack? the basic tech stack discussion, plenty of firms out there just looking at what they have. they’re like, “i don’t know. i do some stuff in excel.” this thing isn’t talking to this thing, i don’t know if i’m doing this right. where do i start and to get it right?
kenji: i think they nailed it. yes, they nailed it. for the base level things, i think chad and kellie nailed it. i would say that think something that may help as you’re scaling. your practice and firm is either look for this in a workflow solution, you may have to look elsewhere, is be thinking about how you can look at your clients holistically, or whether by practice, someplace that you can do overall firm management or your team can do firm management of clients.
karbon. karbon can do that. there’s other workflow tools that can help you look at it in aggregate, not just to sign out tasks to individual engagements, but can aggregate that. you can look for trends. that’s important. it’s going to become more important with scale. sometimes that may have to move over into a more of a dedicated crm system. we got to a point we had to do that to where we have a separate system that we really need to have to help look at all the clients holistically and do assignments and things there.
as you’re thinking about your scale and grow, all these tools change a bit, but that almost managerial view over the client base becomes a bit more important as you get in the 10, 20, 30 people on your team and more and more clients. that becomes more part of the base stack for sure.
seth: what about things like client portals, share file, things like this for file sharing works, that come into play?
kenji: i think it does, but i think there’s discreet options like chad mentioned, a dropbox. i think many are starting to embed that within their tools within the workflow. there’s some options there. it’s not too difficult. it’ll depend on what works best for your team and your clients to find some document management out there. again, some are just already embedded in workflow tools.
some you might need to be discreet, have some different controls over them, whether they’re google drive or dropbox or box or something along those lines. that would need to be important, especially as a– i guess it became more important for us as we added tax. tax is our newest practice line we added a few years ago. that became a little more important for us having that. historically as a cas firm, it wasn’t as important for us to do lots and lots of file sharing. that’s just our experience.
kellie: can i throw something in about the document management?
seth: please. yes, i was going to add on that, but yes.
kellie: the client portal thing. the client portal has become a big word, but really what it is is managing communications and documents with your clients. the one thing that people lose sight of, they get all excited about these portals and they have not analyzed what the actual workflow that’s working perhaps looks like or where it’s broken and where that portal could fit in. i see people integrate a portal, if you will, that takes them out of their process.
i’ll give you a super quick example. i want everything of my client’s bookkeeping documentation to wind up indexed. there’s a million reasons why it winds up indexed, i know some of it’s a canadian reason. it needs to wind up in one place. i was looking at some things that we’re actually going to take the documents and put them somewhere else that would then kill that process of what we were doing over there. you need to be careful that you’re not disrupting a process that’s working when it comes to adding in text.
seth: excellent, excellent point. non-technical, very practical, and even to chad’s point too, just make sure it’s working and don’t mess with things that are working. product specific– yes.
kellie: i think kenji and chad would both say this because they both do tax and i do not, but my hot mess projects look like tax in terms of collecting documents.
seth: i love that that’s your in– is it your in-house label for– [laughs]
kellie: yes. you guys let me know, there’s almost a completely– you’re going to have a different process on this side for the tax clients than you’re going to have over here for the cas work. you may need two processes. go ahead, chad. chad’s going to totally tell me no.
chad: no. i’m reflecting back on this section and there was a couple specifics, but i left out the most important thing because you just said something that sparked it. it’s like, don’t fix if it’s not broken-ish or something like that. sometimes you don’t know when something’s broken and you need someone to tell you. from the beginning we had used password managers just because it was convenient.
seth: sure.
chad: then i started meeting people who didn’t have password managers, and the conversations that came from that were astounding. once someone who is using one talks to someone who isn’t, the next thing they’re doing the next day is putting one in place. it’s still a very, very important base tech stack to throw in something that’s being used really now that people are liking or that’s really safe-ish. that’s changing over the years. a couple that people are really loving these times, keepass, bitwarden, 1password, they’re staying away from lastpass a little bit more because of all the hacks. then there’s a couple more out there too. give them a try. i would probably make that just as important as your practice management system.
seth: interesting.
kellie: that’s such a good point, chad. that is an amazing point.
seth: we’re all connected. we’re in a connected world. we got to keep on top of our passwords.
chad: sorry. and to that point, there has to be accountability for it. right now we have one person who looks at our watch tower inside of 1password. if there’s any duplicate passwords, they’re in it every single day, making sure that there’s no duplicates used anywhere. the amount of times that people try to use the same password in different apps is astonishing too. accountability with process is like happiness.
seth: wonderful. few questions have popped up specifically talking about specific products. we got to bring them up. people are curious about certain brand names out there, sharepoint for document and file sharing with clients. excuse me. anyone use it? anyone can weigh in on it?
kenji: we did historically, but it was quite a while ago. i’d say before we saw the google suite really take off. it’s probably been over a decade since we used microsoft. i came out of a microsoft background and a microsoft tech company. we leaned heavily on microsoft tools and we just moved away. it was a little more our finding again and take this for what it is. in fact, there’s a little more complicated at that point to implement. that could have changed. we used to use it now where we are not using that for any kind of document movement.
kellie: can i make a point about asking specifically about an app like that? again, everybody’s experience is going to be so different. how’s it going to impact your process and how does it fit in with the rest of your apps? if you’re already a microsoft house, then that’s probably an option that keeps it in a suite together too, and also, how do you feel about using it? you take somebody like me, microsoft makes me feel like a ding-dong. i can barely even log into microsoft. everything about it,-
seth: thank you for your honesty.
kellie: -it totally challenges me, but i totally understand google. for me, my initial reaction is, “ugh, sharepoint.”
seth: yes.
kellie: maybe it fits in with how your employees or– do we say employees? do we have to say team? how your team thinks and how … your… i attract clients by magic because i guess i’m throwing it out to the universe. when you’re looking at an app that is a specific app rather than a vertical of apps, it’s going to be about where does it fit in with my other stack, how do i feel when i’m using it, and what is it going to do to the processes that i’ve got going on.
chad: [crosstalk] horace asked a question about multiples. i think the way that we approach that is, one, do we want to engage in an activity where we have to choose, do we want that customer? if the answer’s yes and we know that there’s going to be extra work, what infrastructure are we prepared to put through to make that relationship work?
seth: yes.
chad: we always just said, “no, no, no, sorry, we’re not going to work on microsoft stuff.”
seth: taking a hard line.
chad: it didn’t last very long. now we have microsoft accounts for every user here, so if they need to access some things with a microsoft account, they can.
seth: no, good point. if somebody’s going to be on some stack, it’s like a microsoft, not a google.
chad: we don’t use it per se for things, but we use it for access, which is nice. just my own personal view here is that technology moves in ebbs and flows. we are in an ebb and flow of we’re not really sure how google’s reacting to the new ai work that’s coming out. we all love it, but microsoft has made a lot of promises and have a lot of great things backing what they’re building right now. i’m open to the idea that if something is incredibly better, you take a thorough look at how this impacts your team and what the impact is. to say that we’ll never use microsoft is a bad statement, and to say we’ll always watch and decide based on pros and cons is an absolute accuracy.
seth: getting back to just the idea, this does tie into, of course, your overall processes and selection. when we were preparing for this chat, kellie had brought up the idea of just like, “look, it’s not going to just be one thing for everyone. you have to be willing to try, and in some cases, it should be fun. you should enjoy what you’re trying.” kellie, i don’t want to take your words, but–
kellie: no, but fun is totally underrated. some of it goes back to ux/ui, but fun is underrated. i have lots of fun little things that maybe i don’t need. they solve problems, but maybe i don’t need them. my practice management app is financial sense. i have been bugging them that i want confetti or gold stars when a project closes. yesterday we got confetti, and it’s so silly and it’s so fun. some of these little interactions. we also have emojis in there. if marissa puts in a note, i don’t have to pack back out a note. i can actually just like it or do these things.
seth: why the heck not?
kellie: it’s interactive. i think that some of those things are highly underrated in terms of usability.
seth: yes. vendors definitely need to be listening to that. before we get into our discussion about ai, and i know everyone’s champing at the bit there, final notes on the tech stack discussion. anything to particularly avoid or just absolutely should not do when you’re talking about the stack, even for small firms? obviously, we’ve been talking about a lot of shoulds, and some product names, and some apis, things like that.
anything to avoid when it’s coming to password protection? by the way, i see a lot of your questions coming through here. they’re really great. thank you so much. this is being recorded, and i’m hoping that the folks after this chat can hopefully get back to you, or they can feel free to get back to you individually on some of your questions. final notes on the tech stack, things to avoid when you’re–
chad: i’ll keep it short. if i had to do it over again, i wouldn’t sell services. i didn’t have a very thought-through support structure for it. when we started selling automation services, we had a team of five, and i thought that was enough to be able to sell and to support just for 10 or 15 clients just to test it out. it turned out that that is not true. there are just some services that they’re just so different than what you’re used to, that the cost of supporting them, not only is it unknown, but it can be unlimited based on things that you may not structure in your contract properly.
i wouldn’t get right into things like automation services or going all in on automation or ai if you don’t have a great base. keep that in mind, that while the shiny stuff is really nice, it does take a really strong foundation to make it work.
seth: absolutely. kenji, anything else to add there? i also have a follow-up in there, particularly about firm management apps.
kenji: things that i will avoid like the plague when looking at tech stack is confidence or just lack of support in their own support function. if there’s not strong support there, and what i mean by this is not just say we have an email address or a help number to call in. if we’re going to move, and this is something we do very thoughtfully, beyond calling you a vendor– i don’t like being called a vendor myself either, it’s a one-way relationship.
if you’re going to be a tech stack partner, and our tech stack partners are listed on our firm website, we invest in you heavily, you have got to demonstrate to us that you have a strong support function that is unique and discrete for our firm. now, that may sound a little arrogant. that may sound like, well, that’s asking a lot. we know that we’re playing the role of tier-one support. we’re helping probably sell the product for them at times. the least they can do is show that when we’re going to show us as a true tech stack partner that you’re going to partner with us and a client expects that. something’s going to go wrong, something always goes wrong on engagements.
you know how frustrating it is for a client to take a look at like, well, if we end up finger pointing, well, they screwed up this, we did that, it’s a horrible situation. they need to see that like, okay, there was a problem, but acuity and xero or bill or whoever it is are actually working together in a unique way that they wouldn’t have been able to get that level of support otherwise. i’m very, very cautious. table stakes are, of course, it’s got to solve the problem we need to solve. the technology does. of course, it’s got to be financially feasible. once those table stakes are done, it almost should be table stakes, i need to see a very strong support mechanism because that’s just too much for us [crosstalk]-
seth: got to demand it.
kenji: -clients and our time and our energy on that. that’s a big one for me.
seth: you have to demand it. if you’re entering into that vendor service provider accounting firm relationship, which we could have a whole separate discussion about how strained it is at the moment and has been building over time, you have to step up and say, “i expect this level of support. i expect this kind of relationship from you to happen.” also, there was a technical question that got thrown out there, and then we’re going to get into some ai.
i think it’s relevant in the text that we’re all talking about building. what about when you’re switching? we didn’t really get into that too much, when you’re moving from one thing to another, say, switching from a firm management app, retaining the history. how do you do that with the least amount of disruption because we’re all talking about maybe moving to something better?
chad: the only– five seconds, planning. planning. when we move to karbon, we put one person’s 0.5 of their fte for eight months onto karbon. they planned everything. then when it rolled out, it worked. i won’t say that that’s what it is today because it could be more, it could be less, but for us, we were willing to put that investment in. it was like our director of ops at the time. it was really important.
kenji: i’ll piggyback on chad’s real quick. i think it’s really important. in our experience, it’s by far been the most difficult, challenging changes we’ve had to make across the tech stack. we’ve done it four times, i don’t know why in the world. it just gives me heartburn thinking about when we’ve done it and chad nailed it, it’s planning. the thing i’d add to that is-
kenji: the return on that investment takes longer than i expected. i think that’s something to go into expecting. it’s going to take a while. you’re going to have to manage people’s emotions through it because plan, plan, plan for sure, but it’s not something that’s usually very well received by the team, even if they understand that it’s going to help in the long term. it’s going to interrupt their workflow in the short term.
seth: totally agree. ai in the accounting space, folks. again, we could have a whole separate hour dedicated to that, and we still wouldn’t really get to it because there’s a lot of emotions when we bring up ai in accounting. a few weeks back, we were just down at a pretty sizable conference, scaling the lights. this was a question that was on the majority of the folks’ minds and mouths, talking about it. there is definitely a lot of concern because there’s a lot that’s unknown. it’s really hard to– in the few minutes that we have, i just want to touch on some of these things and get these discussions going.
by the way, that’s what this chat is about, really is about planting some of these seeds, having you go back to your practice, go back to your firms and continue to talk about these things, continue to ask kellie, chad, and kenji about them. how to really crystal ball the whole thing. cloud went through it, too, we remember. just that how it’s going to take this away. it’s going to change this. where do you see ai working best in accounting and where, if anywhere, are there or should there be concerns?
chad: i think auditing is going to look a lot different and there’s going to be a lot easier steps for our team members, a lot less hours spent doing certain things. three is, as hyped up and as weird as this is, i’m doing another presentation on chatbots this thursday with nyos group, which is fun. i did a lot of research into this. chatbots per client is a really easy thing to do right now. just seeing what that looks like and then talking to their data and reducing the amount of time it takes for us to answer questions and monitor what they’re asking and get alerted to cool stuff, i’m really excited about that. four, chatgpt has changed my entire life in terms of how i work every day. it’s up. it’s [crosstalk].
seth: that’s a bold statement, chad. [laughs]
chad: it’s fundamentally changed. i’m building things i’ve never built before. i built my own version of live.
seth: you’re having fun. you’re having fun.
chad: crazy. i’m having a lot of fun. then fifth is i’m excited for what i don’t know. this is stuff we didn’t know about in november that was possible, it’s only july. what else is around the corner that could be coming up that is just so mind-blowing? lots of concerns. i’ll let kenji and kellie take over.
seth: we definitely got to get to those. one of those being, i’m sure, do not put financials in chatgpt. i think we’re very clear on that. you don’t know. kellie, go.
kellie: actually, i want to come back to chad. you said you built your own live and then i didn’t hear what the sent–
chad: well, you know how liveflow connects into quickbooks and it brings it all into google sheet?
seth: ah.
chad: i asked chatgpt to walk me through how to do that for xero. now i have my own apps working right inside of google sheets that connect into xero that give me all the stuff in.
seth: nice.
chad: i’m limited to 25 orgs right now with the stuff, but it took me four hours to build an mvp to connect and switch in between the apps. it’s a skill i did not possess in november and now i know how to do it.
seth: amazing.
kellie: it’s fun. awesome. this is why you are the man, chad.
seth: should be fun.
kellie: [crosstalk] that stuff. awesome. that’s all i wanted to know. go, kenji.
seth: [laughs] kenji.
kenji: again, all i want to do is just keep giving chad the big amen on that one. the last point i think is really, really important and doesn’t get talked about enough, and that is almost that, again, being interested on how things change. i think that’s especially for the firm owners or if you’re a leader of the technology practice in your firm, or even you don’t have to be, but showing your peers and the people you work with a sense of curiosity, of interest. i can’t tell you how important that posture, that culture has been for us of saying, this is signaling to the team that we’re not going to be fearful. we’re going to be curious. we don’t know what’s going to happen. okay, that’s a little bit strange. i don’t know what’s going to happen, but we’re going to be curious about that.
i’ll tell you a little bit of a different way that i’m looking at ai right now, and this is because i’m not even close to chad’s technical chops, and i think most of us as accountants aren’t. when i think of like, “oh my gosh, i’m building things in technical,” yikes, that seems really hard. i love the point about using chatgpt is a little bit of a co-pilot. i’m going to have my little system i’m going to ask things to and get that dialogue.
seth: exactly. yes.
kenji: the other thing, what i’ve noticed is, i think for a while i was feeling some pressure in our firm and… like to think of a modern firm of like, what are we building? what are we building in tech? what are we building? i was feeling left behind, like, oh man, the world’s going on behind me. i’ve changed my thinking a little bit just based on some observations.
the biggest observation i’ve had is fortunate that we get to work with a lot of the great tech companies in our space. i get a little bit of some insider baseball on some of that stuff and i’m really becoming impressed. i think actually most firms are not going to have to worry about building their own. i think it’s going to be reassessing our tech partners to see who is using ai well, who’s using it responsibly, who’s using it well.
seth: that’s going to be a bellwether. yes.
kenji: i feel like there’s going to be a big shift again in the landscape by which of our tech partners out there figures out how to use ai the best, because those products are going to look really strong. we’re starting to see some of those already emerge. i think that it’ll be a whole new way we have to look at our ecosystem, but i don’t think i feel as nervous about, “what am i supposed to be building at acuity?” i’m like, “oh, i probably need to be spending more time looking at how our partners are using it.” that’s a little bit of my shift in thinking.
seth: guys we have about a minute or so left, so we’re going to enter the final thoughts part of our getting real chat. thank you all for getting real with us. i hope you got even a crumb of something that you can take back, that you can continue to have these discussions amongst your staff, amongst the people in your firm, the people in your professional life that you know. everyone just give their your final thoughts on tech adoption in the accounting space. kellie, and then we’ll go around.
kellie: actually, i’ve enjoyed just echoing my buddies here.
seth: sometimes that’s what it is. we get a good group of people together, we get good heads together, we think alike.
kellie: right, and we’re sober. i don’t always see kenji when we’re sober.
kenji: no. next time [crosstalk]
seth: now, i’m guilty of the shame. those who know me.
kellie: i just want to echo kenji’s word. i said be careful if it doesn’t solve a problem. i think curiosity was a great word, so that would be a great walkaway–
seth: go forth and be curious.
kellie: great walkaway word.
seth: awesome. chad, final thoughts?
chad: it’s easy. it’s just be out there, make friends, talk to people smarter than you. talk to people that could learn from you. that’s how i’ve spent the last 10 years, and it’s been a huge unlock to just put yourself out there and say hi to somebody. accountants are really nice people and it’s a great community to be a part of.
seth: you might get to some chats going from this crew that have joined us here today. kenji?
kenji: yes, i would just say again, it’s a big, big ecosystem. there’s lots of changes and so i think when approaching it, go in either very specifically trying to solve a problem that your team has or clients have, just listen to them will give you good things, “hey, can you help us solve this?” and focus there or go in with that sense of curiosity and just explore. sometimes when i’ve made the mistake when i mix the two and i’m at a conference, next thing i know, i’m like, i didn’t come away from the conference with what i needed and i was just kind of–
just be a little bit of discipline upfront with what you’re trying to accomplish and switch back and forth because it’s a big universe out there, but it is pretty fun and exciting when you get into it. again, ask for help. reach out to any one of us. we’d be happy to share, and point you in the right direction if we can.
seth: have a purpose, don’t be afraid, be curious, ask questions, and see what’s out there. don’t be afraid to try some things. thank you all for spending some of your morning and afternoon with us today. rick telberg, final words before we sign off. i believe this recording is going to be made available to everybody.
