Video: Three Key Pressures Driving Firms To Consider Moving | Summary: Firms face client demands, staff inefficiencies, and lack of innovation as key challenges
Video: Understanding The True Cost Of Legacy Systems | Summary: Legacy systems burden firms with costs of operation, migration, and delayed productivity
Video: Auditing Firm Systems To Uncover Hidden Insights | Summary: Audits coupled with interviews reveal system insights and help firms improve configurations
Video: Navigating New Opportunities During System Implementation: Timing Matters | Summary: Deciding when to implement new initiatives in migration projects requires careful timing and planning.
Video: Your Cloud Move, Mapped: A Readiness Plan for Law Firms | Duration: 2824s | Summary: Your Cloud Move, Mapped: A Readiness Plan for Law Firms | Chapters: Webinar Introduction (11.6s), Session Introduction (45.28s), Audience Engagement Setup (138.675s), Audit Process (303.135s), Readiness Assessment (429.68s), Migration Planning Tips (607.015s), Data Migration Challenges (1141.715s), Comparing Provider Solutions (1226.75s), Data Migration Planning (1457.795s), Key Takeaways (1962.71s), Closing and Next Steps (2731.665s)
Transcript for "Your Cloud Move, Mapped: A Readiness Plan for Law Firms":
K. Perfect. I think we're live. We might just give it a few more seconds for people to log in, and then we'll get the webinar underway. Just conscious of time, Steve. I might just kick it off about the COVID as well. Yeah. No trouble. Yeah. Perfect. Cool. Well, good afternoon, everyone. Thank you for joining us today, and, also, thank you for giving us potentially a lunch hour depending on where you're joining us. The plan for today is for us to talk through some of the challenges, the perceived risks and concerns that firms have when it comes to changing legal practice management software, in particular legacy practice management software. We want to take a look at what good transition looks like, and then run through a few key questions you should ask to assess your readiness. Now for those of you don't know me, my name is Arnel and I'm the vice president for Australia and New Zealand here at Actionstep. And today with me, I have the pleasure to be joined by Stephen Dawe from Oliviata. Steven, I might just hand over to you for a few seconds to do a personal introduction. Yep. So I'm Stephen Doar, Director of Alaviatto. So most commonly we're helping law firms, select the appropriate software, practice management software most commonly, and also help with implementation where needed. So that's the bulk of our work. My background is personally in financial management within legal but yeah we have a small team of consultants that work with law firms all across Australia. Thanks, Steve. And, I think you've been in the industry almost probably for about thirty years straight out of high school. Right? That's right, yep. Now, what we'd like to do today as well is we'd like this session to be quite interactive. If you do have any questions, please drop that into the chat and the plan is to address them as we work through the presentation today. To start off that interaction, it would be good to know at what stage of the journey your firm is currently at. Are you at that early stages of exploring options or perhaps building the business case for the firm that a change is required? Or do you think it might be becoming a bit more relevant now as you are within that twelve month window of a contract or a civil renewal? So if you do want to maybe just share some of your thoughts, it would be great if you could just maybe answer a few of that in the chat for us. You know, when we engage with firms, there's a lot of reasons they are considering the move. But what we found is that there seems to be like this theme of three pressures that stands out. One is the client expectation. You know, clients expect faster answers, and they expect your team to work from anywhere. So they have also got more insight on their matters, and they've got access to it. Inside the firm itself, it's about the staff efficiency. Staff are losing hours keeping aging infrastructure running and using clunky software that creates further bottlenecks and frustrations. Then there's this lack of innovation, innovation that allows firms to be more productive, more competitive, and also more profitable. Interestingly enough, when we ran our 2026 mid sized law firm priorities report, we actually found that only 9% of Australian law firm professionals say that their technology creates no friction in their day. Now apart from those pressures, we also see that there's this misconception or potentially this lack of understanding when it comes to the actual cost to the business when running these legacy systems. There are a few ways though you can look at this. The cost of running what you have, so your servers, the IT support, the licenses, etc. Then there's this cost to move, which is most likely the cost that most firms really hammer on most of the time. That's the data migration, the implementation, and then this change management piece. But then thirdly, there's this cost that really makes it onto a budget line and there's this cost of waiting or not moving. So the productivity that you as a firm give up each year or each month that you stay. Now for joining the session today, every firm will will have access to a free comprehensive readiness audit that's delivered by Olivia, And we'll share some details at the end and how to engage them for that. Steve, I don't know whether you wanna maybe share a few snippets on what that audit actually entails and what you guys seem to as part of that audit. Yeah so we couple it with both both an in person interview of the firm but we've also got some tools which can analyze their current practice management software quite deeply and it provides the firm back a report on the insights that it finds which can be quite valuable. So it can extract things that you might not have forecasted for, one of the examples might be that you maybe have 500 precedent templates in your practice management system, not knowing that perhaps only 50 of those are widely used and you know a large majority are just used sparingly so that's just one small example of many different areas where we can assess and audit quite quickly and provide a firm back a report on the current state of play within their configuration. So it does it both an audit of the system configuration but also some of the usage behaviors as well. So that coupled with actually interviewing the firm, you can get real insight into to where you're at and what perhaps what might be complex about your particular setup as you consider moving to an alternate solution. I actually love that, to be honest, because, you know, a lot of the times that we engage with firms, they don't know what they don't know. You know, they've got this perception on the functionality and the usage of certain things within the platform, but without actually realizing that the firm barely uses it at all. It's fantastic that you guys can actually run that order to show some usability of the platform itself in certain functions. Yeah and the reason we developed that is because, some of the legacy solutions are quite customizable. So you go to every different firm and their their setup is quite different to the others. So to be able to extract that and know that you're not the same as the firm across the road and why will your migration differ and what's important to you will be totally different as well. Yep. Yep. Perfect. Now we will be talking about readiness assessments, migration, what to look out for, etcetera. Steve's obviously, and Olivia Arthur goes into a lot more detail with that audit, that readiness audit. But one of the things for the next few minutes or so is to look at readiness through the lens of, what are the questions that I should be asking or things that I have to consider that now is the time for us to look at some more innovative software? Software that is continuously being developed and invested in. Questions that might be relating to your architecture or your IT infrastructure. Do you have ongoing challenges and efficiency bottlenecks with remote working or maintaining aging systems, as an example. Now feel free to score yourself on a one-five rating, one being not sure, don't know, a lot of challenges, and five being, hey, everything is absolutely perfect. Then we can give you a bit of a guide towards the end of this. Another way to look at it is potentially these days about AI readiness and innovation. Could you connect AI tools to the platform and use maybe like an MCP server? Can the AI tool that you're looking to connect to find everything about a matter in one place today? Another thing to consider is your staff experience and the productivity. Now how much of your team's week actually goes into keeping the system running, and what does that mean for your productivity? And then what about integration access and platform openness? Now can you connect a new tool without a custom project, or does it have a flexible open API? Steve, you so nicely touched on that just before this actually about the project work required on some customizations that's needed, you know, for these tools. So there's a classic example of that, something to ask yourself. Then this ongoing struggle, I suppose, for firms is this cost of staying versus the cost of moving. Now, do you truly know what your system cost each year? Or the total cost of ownership. Now, and potentially, how much more profitable you could be. Now, for those who did actually work through some of that scoring, to give you a little bit of an an idea to those questions, This gives you a bit of an indication on what that means. If you're sitting in that five-eleven point mark, it's time to start planning. Your systems are likely limiting the firm today. But at the top end of that scale, if you're in that nineteen-twenty five range, you might just require some fundamental tweaks or some tweaks at some of the fundamentals for you. Now, talking about the cost of staying versus the cost of moving, I'm going to hand over to Steve to talk through the considerations when it actually comes to migrations. Itself? Over to you, Steve. So thanks, thanks Dan. So what I've compiled is some tips to aid you when you do plan to make a migration. So that'll either be in your assessment of alternate solutions or during the project that you might have already undertaken. So Zara, if you want to progress through we'll take a look at a few of those points. So the first one here is ensuring that you've got a project team. So this is when your implementation is underway. So ensuring that you've got an internal project team that's eager to be involved. So a lot of the time we see, people that are asked to be involved in a project that don't really... Haven't really committed or understood their role in in the entire process. That's an inherent risk to the project overall. So you you don't want someone to be ever pushing back. So to to obtain that acknowledgement and eagerness, that they're willing to be involved. And the other thing is about freeing their time up to dedicate to the project. So you've got to remember that they'll have a role and responsibilities throughout the change, so when that occurs and we'll touch on this later in the presentation, Whether or not you can free them up to dedicate the appropriate time to deliver a successful change is really a critical, critical piece of the puzzle. The other one is a people element too. So number two revolves around, identifying procedures or people within your firm that have procedures that are deeply embedded within the current system. So these are guys that are that are real power users perhaps you might frame them as within the current system so they may feel disrupted that or even if you're considering changing they might be a real pushback against that because of the way in which they work and they're heavily invested in that way. So again, managing that process and having them be included in the assessment of alternate solutions is a very wise choice and ensuring that when you do make the move that they receive the appropriate level of support. So that means that ideally you'd probably want them in the project team but even at go live or after go live they're gonna ask a lot of questions to try and replicate what they were doing in the prior system to be that power user in the new system. They're not gonna go from being a power user to being sort of someone that's just getting through the day not being efficient. They're probably someone who loves being, feeling efficient and feeling productive so you want to, you want to really find those people within your firms and have a plan around them to make sure that they're going to be feeling the same way when you go live with a new system. This one relates to when you are going through the implementation dedicating the right level of time to the user acceptance testing. We see far too many firms you know fast track this because of various reasons which we'll touch on in a moment but absolutely dedicate generous time and if you if you have a certain go live date in mind when implementing a new practice management software, if you enter the user acceptance testing phase too late that really compresses that. Now you're putting things at risk there where you either have to bypass or fast track certain elements or skip testing of certain components at all which again is an inherent risk and you wanna absolutely have the chance to tweak and change and modify the way in which certain elements work in a customizable system so certainly generate a decent amount of time and don't bypass that wherever possible. Steve, I might just ask you that question, actually, because that's a burning one for me, to be honest with you. We come up against this quite often obviously when we're doing these migrations and working with partners and there's always this extra cost associated with UAT. There's a data migration, dummy data being migrated across and etcetera. A lot of the times we see firms actually looking at that as going, Oh, that's additional cost. Or firms that's actually doing classic example, they won't do any cost for a data migration or implementation like free migration, free implementation as such. What would you say to firms that tries to bypass this UAT phase that comes potentially at an additional cost to firms? I'd say avoid that at all costs because that's your real chance. We, when firms choose to compress the UAT and are willing to go live as soon as possible, they face a lot of potential change or will ask to make a change to the configuration that can't be, can't be undone. So they're kind of stuck in patterns then from that point on that they might be not able to exit out of. So that might be the design choice that they made that they didn't give too much thought about. They hadn't thoroughly tested it so they made the design choice that was implemented and that's kind of stuck there for how the system will be like that moving forward. Unless you really test it, you wanna break it, you wanna you wanna try it. Yeah. Far too often firms are skipping this. And it's a it's a it's an onerous task and it means that you're in UAT for much longer than you ideally want to be, but the the the payoff or the the avoidance of risk is is for me, yeah, paramount. Yep. It almost becomes a non negotiable, doesn't it? It is... There are challenges that mean that, you know, you have to you have to keep plowing forward, but, yeah ensuring that it's really coming back to not overwhelming or having too few people within your project team. If you give too much of the work to too few, they'll inevitably have to fast track things or get through. things. So they're still going to do their day to day job a lot of the time. So having a checklist. of things that they're to test naturally they're going to do their day to day job first, that's the, you know, get that stuff out the door, move across to testing on this system that's coming in three months time. That's kind of naturally a second thing for them. So you need to either free them up or add more people to your project team which has come to the cost, we know that but I'd say that the payoff or the avoidance at risk is much more important. Yeah. Totally agree. Alright. Moving on. This one relates to perhaps assessing solutions in the market. So understanding the project deliverables. I've seen a million different proposals from all different vendors and they all read differently. Never never are they very clear in what they're including. That's not to say you can't extract that from them but obviously there are summaries of proposals and then there are deep dive analysis of what actually is included so you need to get to that point. So understanding that project deliverables intimately is really crucially important to be able to compare what you're getting from one provider to another because they're vastly different. Some might have a capability over here with data migration that another one just can't achieve because they don't have the data migration tools or expertise to do that, you will never know that unless you assess the scopes quite with, you know, with a fine tooth comb. So I've found the best way to go through and assess the deliverables is to use a project plan. So forget the proposal document, work into as if you were starting the project today, look at what a project plan looks like and walk that through with the people that are proposing to you what their solution is and then that will highlight to you okay well we haven't even spoken about training at this point, is that included blah blah blah blah blah. So working through the project plan I think highlights where their proposal or their deliverables are under stated or missing or not included entirely and you know you'd unveil that quite quickly by walking through a project plan. Yeah. I might also add to that scope of services component there, Steve, which is also another thing that I hear a lot is the assumption. Firms assuming that, Oh, well, that's basic and that's expected. Yeah. Because that was a standard in our current system. We would just expect that to be the standard in the new one. So that assumption. piece. We we had. that we. had that yesterday. We have had someone go live that we've had to come in and and help go live on a new system. The assumption was made that all of the contact fields and data would come across, they've essentially come into just a general notes section which is effectively useless for a data migration. It just means that the data's there in the new system, it's not where it should be. There's this massive re entry project now on go live where all the staff are reentering all the data from the notes section into the real fields of the practice management system. So that's just a misinterpretation or just they didn't Yeah. they didn't understand the process or go through it with a fine tooth comb like I mentioned about what's going to happen on day one and never was it mentioned by the provider as well sort of okay that's what you got you didn't ask us about it so you know it too late Too something. You know? So Yeah. I I actually think that. the providers there has to play a big part in it, to be honest. You know, to your point, they just sit down and really, you know, crystallize it and explain it very clearly, bearing in mind that you don't know what you don't know and it's the provider's responsibility, in my opinion, to educate and help and advise and say, these are the gotchas. You didn't request these but these are the things you need to be considering and asking, which is obviously what we're doing right here at the moment with you. So it's fantastic. Okay. Next. This is more around how to compare providers. I bought a car recently. I'm gonna I'm gonna use an analogy here, but, my family SUV, my my crappy car was just getting a bit old, and I wanted another crappy car that just wasn't quite as old but that was my budget, it was like maybe I'll spend less. So I had in my mind I was gonna spend next to nothing, but once I went out I got swayed by and started looking at cars. I forgot what my original intention was so I ended up spending twice as much as I intended to on a car that was totally different to what I wanted and I didn't have a plan, I went in without a plan. I had it in the back of my mind but I didn't have a plan, I didn't stick to the plan. So this is kind of in that vein, when you get proposals and demonstrations from an array of different practice management providers, you can forget why you were there in the first place and there's so much information and one will talk about AI and one will talk about precedence and another one will talk about their billing and then it all becomes a big cogmire of confusion. So I say have a very simplified checklist, go as deep as you can with it but if you don't want to go too deep and it's too annoying to document every one of your processes start with the absolutely fundamental ones. Don't think about all the fancy things that you could potentially get in a new system. Start with the fundamentals, you know, your trust or office processes, your billing processes, your trust accounting, your document management, your foldering, your email saving, all those real fundamental things, they seem to be taken for granted that every system does them in the same way. They absolutely do not. So start with a checklist. Nail those first. You'll really throw away half of the software suppliers just because they don't do the fundamentals well. So they might have just thought we'll build this cool AI or whatever and that will allow firms to choose our product but they haven't really nailed the fundamentals. So deal with the fundamentals first and follow a plan. So just get a checklist, wait that checklist with your firm's priorities and then score your, evaluate your different providers on that basis first and then move to the things the way you might want to implement certain initiatives down the line with new technologies and what they can make available to you. Yeah. We see that actually happening quite often, you Steve, in our sales cycle. When we start and we say this all the time to our teams as well, well, we need to go back to the basics as to why we started this conversation with the firm because this journey is sometimes a six month, nine month. If you're a larger firm, we've got some firms that's taking a year plus with engagement and sales cycle and demonstrations and understandings and etcetera. Where we started off with the reason for the conversation, nine months down the track it looks completely different. So to come back to that, hey, what are the must haves, the nice to haves, and then all of a sudden those nice haves become so critical to those firms and they kind of lose direction of the objective there. I think that's a really valid way. be hard if you're dealing with sort of four or five different competitors in the same space. They'll all want to talk about the things that they want to talk about and you kind of feel that you're reining them in and redirecting them but it's crucial that you do redirect them to talking about and showing and proving that they can do what's most important to you. You can absolutely deal with those other things that they can deliver in their solution that are really valuable but not at the expense of bypassing the things that are your fundamentals. Yep. Yep. All set. This kind of goes back to the project team and just re emphasizing on how crucial it is in that UAT phase and more so my crappy little table there of who does what at what stage. So this is just a real very high level view of a project from selection to the go live and adoption. So you can see there I'd love be a standard end user, don't really need to do much until you go live, you do some training and away you go. Whereas the other project team contributors have an influx of that work towards the end there. So that might be getting precedence ready for go live depending on your volume, your accounts team will certainly have a lot of work in testing their billing routines and all their different routines so out of all teams impacted the most I think the finance and accounts teams are the ones that feel it the most. They have a heavy role to play through the testing and implementation and at go live and post go live their worlds are changing more than anyone else's. So we see the biggest disruptor no matter which product you choose is the finance team. They they seem to yeah have most of their processes change and yeah it takes a while so certainly wrap your arms around those guys and and yeah give them the time to to to adopt to the new systems. Right. This kind of is what we touched on with you know what's not discussed and this is more around the actual data migration. So we've kind of touched on this with my example before where contact information goes across the notes but I would be analyzing or assessing a detailed scope of data migration from one provider to the other and absolutely if not all data will be taken. I've not seen everyone, anyone say that your entire data comes across. There will be stuff that will be left behind so trust transactions are left behind commonly and you know it might be documents, it differs, it vastly differs from provider to provider as to what level of data migration you're getting. So absolutely ask them to say what they do not include and what the plan is around that for your firm. So you... If you're a sizable firm and certain key elements and perhaps it's custom data collection fields you've got property, you've got family, you've got commercial, you've got litigation, you've got all these array of matter types with custom data collections and you find out late in the piece that none of that custom data is coming through and only the matter details from the the fundamental matter details are coming through, you will be in a world of hurt on go live to re enter all of that data through all of your teams through those thousands of matters. That's a really big job. So it may well impact on who you choose as your provider, the software or the implementation partner, so as I said earlier each have different capabilities in what what they can and can't do and some choose just not to even if they can so certainly look at that data migration component with a fine tooth comb and compare what you're getting and highlight the things that you're not and have a plan around those. Yeah. There's a there's a couple of thoughts I have around that, Steve, actually, as you were talking that just came to mind for me because, you know, we come up against this so frequently about, you know, free data migration from competitors as a classic example. Actually, funny enough, we had one this morning where we discussed this. But the customer just thinks that there's no cost for it and it's like for like compared to, as an example, working with a partner like Aviata that charges obviously, and rightly so, for a great job of of data migration. And to your point is the quality of what they get and in their world, in those firms' worlds, it's just like, well, it's data migration, it's like for like, which it's completely not. One One of the things that. came up actually this morning in this discussion to your point about the mapping of the fields and stuff is the firm actually having over 2,000 custom list fields. In their environment, it's a field that just moves across. But in our world, in your world, well, that's a custom field that's quite unique. You know? And that's that's not taking into consideration for those free data migration offers. Yeah. Yeah it might seem, I might be getting too detailed here but this is. kind of the world that I live in which is in, even in finance if you've got a custom report that is relying on just a single status field of a custom field that you're not getting in a data migration you can no longer run that financial report. So you might want to map a status report that's based on stages or something like that. If you're not getting that status or stage field in that migration you've got to think about that report breaks on day one and that's just one. tiny example of many different follow on effects. So whether it's precedent templates or financial reporting or just simple matter lists or any other way that you take data out of your system, yeah so it's a really, really important one. Yeah. People that we advise, we say why would you enter a long term contract with the velocity of technology changes now? So if you want to be agile and you see that there's all of these new opportunities available to you because of technology and how quickly it's advancing, to be stuck in a three or five year contract and not being able to commence for two years or so, you know it sets you behind so we just advise people just to avoid like long term contracts wherever possible. It's tough because we know that renewals and things are sweetened if you enter a long term contract so it might just take I don't know, yeah some negotiation there but, if possible, I'd say be avoiding those. Yeah. I mean, the rapid change, Steve, you know, as as a provider, you're obviously of software. Talking about terms and contracts, we actually do offer customers twelve or thirty six month terms. You know, we we we don't actually look at locking in long term contracts, just because I think we back ourselves as a provider, and that's probably the main reason for that. But to your point, I fully support that the rate of change that's happening currently in our tech space, in our environment with AI as a classic example, to be locked into longer term contracts could be quite detrimental for firms. Also, you don't know what the next innovation is going to be in the next six months, they're completely game changing again for this industry, Yep. so it's a valid point. And this sort of goes hand in hand with what we were just talking about. If you are choosing a new product that opens up new opportunities that weren't within the technology that you were on previously, making a decision on when to actually take advantage of those is a crucial one. So it's highlighting again, do you want to implement those as new initiatives within the current migration project? It's already pretty stressful enough so we kind of say to our firms that we work with, you know, if possible push that down the line, you've got enough things changing within the implementation, you're choosing a new system, you get all training is required to be done again on a new system. Do you also want to try and implement new initiatives within that? So sometimes certainly do and if you choose to do that you get there sooner of course but you're going to have to add more project team members through that implementation phase there. So yeah it's a critical one to make sure you pick the right time to implement those. You will get a lot of new opportunities made available to you moving to one of these new products so yeah make that make that choice wisely. I think we see people that think they will be able to achieve it within the within the go live but then ultimately it gets shovelled off to later because it comes becomes all too hard. Steve, there's actually a question that's popping up as far as, where do you sit with your recommendation as far as a big bang approach, try and deploy all of the bells and whistles and all of the tools that comes with a practice management software as opposed to potentially doing it more in a phased approach? Rather than, Hey, let's get you up and running, let's get the basics done, let's do a like for like, and then easing to the new AI time recording tools that's there, the new AI BI reporting tools that's there, Hey, here's the latest AI agents that's part of that platform, etc. Where do you sit? Do you think it's an appetite of the firm or is there a one rule that fits all or guide? Yeah it depends on the firm's commitment to to yeah the project. So if many firms and I have to I can't speak for everyone but many firms just want like for like from day one, we want to be able to achieve the same as what we were over here but on a new cloud product and we want to then think of those as phase two. Yeah most, most no and we've even had some where they scaled it way back and we're like thank you, we absolutely believe we should not have done the big bang thing because of the amount of effort just changing one component, imposed on them. So, yeah, it's tough. If if you wanna do the big bang, you really gotta throw it throw, throw everything at it and it can break. So if you, if you've missed the mark on some of those critical testing phases or you miss a critical date in the timeline just remember that that can push things out months, months. So you see that on hold sector there. So that might not be something that you're responsible, you haven't contributed to but your implementation partner might not be able to implement your system for a couple of months after signing your contract. If you miss a key date and we had this with one of our clients not that long ago, they just could not go live in August, that the next available date was October and that's a small firm, that's a regional Victorian small firm that just misses in three months down the line. So you've missed all that chance for three months and there's just this wheel spinning that's going on. So if you are going to go the big bang approach you have to really throw everything at it and make sure that you're hitting those marks and not delaying the entire project. Sometimes it's wiser to just bring that in, do the like for like, nail that first and then push those out. If I had to choose one or the other it'd be pushing it out. Pushing out that way. Yeah. It also most probably helps with that change management a little bit, isn't it? You know, rather than just overwhelming people with a lot of change Yeah absolutely. want. Yeah. So these are kind of just takeaways from from what we've discussed. So the people component, ensure you you grab the right project team, they're eager of course and free them up to contribute. Comparing systems, so make sure you know what's important to you essentially. The costs as I mentioned, implementation costs vary widely so know intimately which ones are fixed and there are ones that commonly vary as well so if you are if you do have a proposal and it says you know it might have line items of cost of implementation but some of those commonly vary based on things that occur throughout the project so ask for finer detail within those costs about what which ones will never change but which ones commonly change and for what reason. And then analyze comprehensively analyze your current configuration and get some of those insights. So compare that sort of digital analysis of your system with what your people are saying as well. So a lot of the time firms will rely on the word of their staff which is great, they know that they know the processes, they know the system but also compare that with the data that comes out in that report. So the report will say to you you know 50 precedents are used out of the 500 you know heavily and then the rest are not, is that the same as what's echoed by the staff or are they saying something completely different? We do see sort of disparity there so that can really highlight that there's this unaware sort of firms are not aware of truly how they're using the system like you said earlier on so they don't know what they don't know. The data driven insights are really valuable to compare that with the with your staff's opinions. And as I mentioned data, data migration make sure that you you nail that with a fine tooth comb and compare what's not migrated. I think if you didn't do that you're running the risk of that big, big shock moment on go live that we have seen a few firms go through. Steve, maybe just pausing here for a few minutes to just talk through a few of these points that have been raised here. Do you see that with firms, with this misconception and potentially not knowing what they're knowing, they start going through a phase of paralysis analysis, where they're just overthinking it based on these assumptions and then get to the stage where it becomes just too hard basket and they just do not make any decisions or make any movements because of that. Yeah that you can do that. I find that the the quick analysis is just a snapshot of you know where your system's at and you can really nail in on any complexity. So you can talk you can take that report and show that to your... The the the providers that you're considering and say this is this is how we're currently using the system. You know, how will how will you present your product in alignment with that? But in terms of, paralysis analysis or whatever you called it, I think it goes the other way. I think you need that information. It will actually aid and speed up your decision making process to pick the right product. So you might be, if you've got five products out there that you are considering, you may end up with two after you do that analysis because you'll quickly identify that you've got billing procedures or certain processes that some just can't achieve that quickly sweeps those off the table and you're left with the two. So you can spend more time on perhaps your two shortlisted providers and deep diving into what what they can do for you as opposed to broadly assessing five and wasting a lot of time. So I find that that report really aids in, in shortlisting. Yeah. I also like the fact that you mentioned, you know, giving some insight to the precedence as a classic example. You know, we've got 500, 600 in our library, but actually, when you actually do that report, you notice that, well, actually only 10% of them being used a bit more frequently. The others are once in a blue moon, so that's quite good. One thing I also wanted to ask Bobby on this actually, sorry, I'm going a little bit of left field here, but just thoughts that came up. When we talk about people and the project team and freeing them up and to your point, they still have their day to day, ongoing day to day work they have to do, who would you say are kind of really key people to be part of that project team? If you had to you know, take a firm and say these are key decisions, not necessarily decision makers, but influencers, power users, managers, etc, that we need to be part of this team to have a successful outcome. Yeah. I I think try and grab the people that have been there the longest but equally are not too entrenched and and and sort of willing to stay in that mode. You want someone that likes to be innovative and move things forward but knows the processes intimately. Excuse me, I just got a cold so I'm just gonna It's okay. It's Manflu. You got a lot. of sympathy from me. So we see a lot of firms that shoot a certain type of person who knows everything about the firm but they're not energetic to change. So they're valuable to one degree because they know the processes, they can answer a lot of the questions about the design choices or what the needs are but they're not too innovative in their thought to take it to the next level. So you kind of got to, you kind of got to have a tandem approach there if you can, if wherever possible, if you can take their knowledge and get their assistance in that way but also have someone else come through and be more innovative thinking outside the square that kind of crossover works best. And that would be equally in every one of those teams that I spoke about. So from finance, each of your legal teams, see your representatives in there, have someone that knows the legal team's processes inside and out but someone who maybe has exposure from another system that knows what other processes can be achieved that are not being achieved at the firm that they're at now. That's the way to approach it. So someone that knows everything about the current firm but also people that have exposure to to other systems and other procedures that might be want want to be more innovative and drive within the new system that you get. Yeah. Brilliant. Brilliant. Look, we've got a couple of minutes left. I just want to quickly touch on this fold before we wrap up and, we finish off just to reiterate the offer, obviously, with the the free audit. So the question, the thought that I had around this, I'd love to hear your opinion. Like, a couple of years ago, our UK team, were absolutely, like, really just going gangbusters in in selling our software. And and The actual interesting part there was that Cloud technology or Cloud solutions was actually seemed as a bit of a foreign concept for them. I was actually quite shocked by thinking about being London that so many firms were still based on a server based solution. The fact that we could offer them Cloud was a real initiative or like a differentiator, so to speak. Now, I've actually had a look and we've done a little bit of further research and we actually found that in Australia, and New Zealand as well, there is actually still a big percentage of firms that actually still use legacy based service software. Also, a large percentage is currently using a bit of a hybrid solution in that, where some parts might be Cloud, some parts might still be server, but there's still a local or a server based processing requirement for that. Sorry, I'm just left for fuel question. Your thoughts around that on the mind shift that people need and do we think at this point in time where we are with technology, AI, and all innovation that's there that that firms are gonna be forced down to making a decision in the very near future because their software is not being supported, maintained, updated, developed, etcetera. We're going to see this bottleneck of firms really just rushing to try and then move to the Cloud that these firms are better off now planning and making these decisions in advance on their own terms. Yeah, it kind of goes back to the availability of the implementation teams and the providers you know missing that key date before pushed it out three months for a small firm with with basic needs. If there's a critical moment within your current practice management provider that means that there's an influx of those users wanting to get off, there's not an endless pool of resources for people to move as swiftly as they may want to move so you might be in the line of twelve or twenty one, twenty four month waiting period to actually kick off your project, not necessarily go live but just to kick off. So we have heard stories about long delays of kickoff before and I've been in the industry years and the same sort of thing has happened many years before. So there's a, there'll be something that, there's a key event that occurs that triggers a big shift of people on a certain product and if you fall into that boat, into that pool you may not get the greatest level of service if if there's this fast tracking sort of processing going on. Cool. Brilliant. Okay. Well, we're about thirty seconds over time. So with that in mind, Steve, once again, thanks for joining us today. I really appreciate that insights and, thoughtfulness. With that, I might just wrap this up just to maybe just reiterate to everyone, thank you for joining us once again today. What we've done today obviously is we've run through a bit of a high level readiness review during this call. But as we mentioned in the beginning and Steve mentioned a few times during the session, everyone that attended our session today will be able to access a free detailed readiness audit report from Steve and Elviato. Firms that's interested in that, please reach out to us and to our sales team here for further information and we can arrange that audit. The second thing as well that we are currently working on with firms and as part of this process and the engagement, we're actually looking at offering firms that's making a decision to move to Actionstep before the end of March of next year to look at offering a subsidised implementation and migration fee working with our partners. That's something that we will work with all our firms on a case by case basis and what that might look like. Just to reiterate, it's not a free migration, it is actually just a subsidised migration from AppSysDev's perspective actually contributing towards that to pay the partners for it. Once again, thank you so much for your time. If there's no further questions, which it looks like it's not, once again, Steve, thank you as well and we'll end it up with that. Thank, you. Art. Cheers.