Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Credentialing Chronicles

Credentialing Chronicles artwork

THE DEMO WAS BEAUTIFUL. THEN IMPLEMENTATION STARTED.

Sep 29, 20261 hr 6 minAudio
ShareXLinkedInFacebookWhatsAppEmail

Send us Fan Mail This week, Credentialing Chronicles sits down with Matthew Jansen, President & CEO of Acorn Credentialing Solutions, for an exclusive conversation about the side of healthcare credentialing most people never hear about. Acorn works across credentialing, enrollment, provider data, automation, and provider operations - connecting pieces of the process that healthcare organizations have historically managed across separate systems and workflows. Acorn But we're not here for the sales pitch. Shannen and Nyleen put Matthew behind the mic for a real conversation about credentialing, technology, the problems our industry keeps running into, and where healthcare is actually headed. What happens when credentialing doesn't work the way it's supposed to? Where does technology really help - and where does the human side still matter? And when you put two credentialing professionals across from the President & CEO of a credentialing technology company... what gets said when nobody is reading from a script? 👀 Some questions were expected. Some answers weren't. No rehearsed corporate talking points. No fluff. Just credentialing professionals talking credentialing - real talk, real experience, and no filter. ☕️ You'll have to press play for the rest. Credentialing Chronicles x Acorn Credentialing Solutions 🎙️ Stay Credentialed, Not Cancelled. The tea is officially on the table. Learn more about Acorn Credentialing Solutions --https://acorncredentialing.com/ Acorn Credentialing Automated tasks, streamlined digital workflows, advanced data management. Simple integration with le Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you. Support the show Resources Mentioned: 🔎 Verify Your Doctor’s Credentials ✔️ State-Specific Medical Board License Lookup: Find your state’s board here: https://www.fsmb.org/contact-a-state-medical-board/ ✔️ Medicare Exclusions List (LEIE) - Check if your provider is federally excluded: https://oig.hhs.gov/exclusions/exclusions_list.asp ✔️ Set Google Alerts on Your Doctor’s Name: Create your own Google Alert here: https://www.google.com/alerts For Medical Staff Professional: ✔️ FSMB.org - Federation of State Medical Boards Physician Lookup: https://www.fsmb.org/physician-license-lookup/ ✔️ Hospital Websites: Many hospitals have public directories listing credentialed medical staff. Look for a “Find a Doctor” or “Medical Staff Directory” page. ✔️ Set Google Alerts on Your Doctor’s Name: Create your own Google Alert here: https://www.google.com/alerts Wanna know if your plastic surgeon is actually board certified? Check for yourself right here: 👉 Verify a Plastic Surgeon Open Payments openpaymentsdata.cms.gov Verify your Nurses' Credentials: https://www.nursys.com/ 🌐 Connection Zone Stay plugged in with your peers, share resources, and nev...

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

SPEAKER_00Hell yeah. Well Nileen Shannon sitting there talking about you while you pull up a chair they hold in it.

SPEAKER_01Hey, welcome back to Credentialing Chronicles. I am Shannon.

SPEAKER_02And I'm Nileen. And you know, Shannon, one of the biggest questions we get is how do I know what credentialing software is good for my organization? And also, why in the world is buying credentialing software so difficult?

SPEAKER_01So difficult, Nileen. That's what everybody says sometimes. And today we're really diving headfirst into this question with our super special guests. We're so excited about.

SPEAKER_02Ooh, okay. So first let's set the scene for our listeners.

SPEAKER_01Yes.

SPEAKER_02You need some credentialing software. You've interviewed everyone. Yes. And you've gotten some good demos complete.

SPEAKER_01You

SPEAKER_02know? This is a demonstration, everything is clicking perfectly. Everything looks one button, one dashboard, one beautiful report, and everybody in the room is like, finally, this is gonna fix everything. Then implementation starts. The data doesn't matter. The workflow needs like six extra steps. The automation needs a spreadsheet on the side. Honey, the everything is just not running itself. And suddenly the team that promised you efficiency or you sold efficiency to is working through a nightmare.

SPEAKER_01How many times has that happened to y'all? Because if it has today, we are asking the questions buyers usually learn to ask you all after the contract is signed. And really after that three-year clock that we all know about, it's already started taking.

SPEAKER_02Yes, and this is not a specific software commercial episode. It is a buyer protection episode. We want MSPs, credentialing leaders, CEOs, IT teams, and procurement departments to know what to demand before they sign anything. Like we have a true industry insider with us today. We're so excited who's willing to talk openly and frankly about what really happens when healthcare organizations purchase their credentialing software.

SPEAKER_01Our guest is Matthew Janssen, MPA, president and CEO of Acorn Healthcare Credentialing Solutions. Matt brings more than 20 years of experience you all expanding credentialing, medical staffing services, literally patient access, virtual care, and healthcare technology. His previous leadership experience includes serving as a director within KPMG's government and healthcare life sciences practice.

SPEAKER_02Yeah, and under Matt's leadership, Acorn was featured in the 2025 Class Emerging Company spotlight for its credentialing and enrollment technology. So kudos to you, Matt. And Matt has agreed to step into credentialing chronicles Hatzy and talk honestly about where software companies get it wrong, where clients get it wrong, and what both sides should put in writing to help ensure they get it right.

SPEAKER_01Okay, you guys. So whether you're shopping for a new platform, questioning the one that you already have, or getting ready to renew that contract, this conversation is for you. So because once you sign that agreement, you may discover that you are not just committed to that you are locked a lot. Welcome to Credentialing Chronicles.

SPEAKER_03Thanks for having me.

SPEAKER_02Matt, thank you so much for taking the time and spending this day with us. Before we get into all the mess, just tell us a little bit about Acorn, who you built it for, and what problem you believed to solve for the market.

SPEAKER_01I want to even know how you came up with the name of Acorn.

SPEAKER_02Yes.

SPEAKER_03Oh wow, you you guys are getting right into the heart of it all. Um it's it's great. Um yeah, so Acorn was started with the idea that you know there was a lot of different solutions in the market. There was a lot of different legacy players with a lot of older technology, kind of built through acquisition or highly modulized. Um, and a lot of it was just kind of sitting on the shelf for many, many years without a whole lot of innovation wrapped around it. So we saw an opportunity.

SPEAKER_03Um, so when you think about an acorn, you know, you plant the seed, it grows a great oak tree with many, many, many roots in the ground. So it's really stable. And over longer periods of time, it gets bigger and can spread, you know, even larger and grow kind of its own forest around itself. Um, so the idea behind Acorn was that let's just plant the seed, let's start working with uh MSPs at hospitals and providers at different types of specialty groups and really sit down and collectively work together on developing a platform.

SPEAKER_03And that's how Acorn was born. Acorn was born through the eyes and through the work of MSPs. Um, and you know, the solution that you see today has been that work over the past 10 years.

SPEAKER_02Wow, 10 years. Well, let's just get started where the relationship actually begins, right? You mentioned you wanted to start with hospitals and physician groups. So sometimes the hospital goes looking for software. Sometimes a salesperson calls leadership with like the perfect message. We need to reduce the manual work, right? We need to improve compliance. This one's clicking 20 times. So when a prospective client first thinks of taking the leap and using a credentialing software, what information should they gather before they get on the call and especially before anyone recommends a platform?

SPEAKER_01Naily, wait, wait, wait, wait, wait. We didn't do our disclaimer.

SPEAKER_02Oh, okay. Go ahead. Compliance.

SPEAKER_01Credentialing Chronicle discusses industry experiences, y'all, reported concerns, and buyer questions for educational purposes. We are not making any universal claims about any vendor, baby, even though you might think it's about you, implementation, or even clients. Every organization conduct its own due diligence and legal review. Okay, I just wanted to get that in there, Nileen.

SPEAKER_02Oh, good, good chance. So, Matt, just let us know what we need to get together. So, our MSPs are together. What are we getting together for you?

SPEAKER_01Help us get our checklist together.

SPEAKER_03Yeah, so the the checklist can be fairly simple to begin with. Really, you want the people who are going to be using the software to have a lot of influence and a lot of weight over the discussion. Like, you know, when you're going through that process, you want somebody from your IT department, you want someone who can run project management for you, you want a lot of leadership support and sponsorship because you're going to run into things where you're going to need help along the way to get things kind of pushed through or accepted or reviewed by legal or through compliance or all the different things that go on in the back office of a healthcare system, especially if you're interfacing with other systems and other departments.

SPEAKER_03And and, you know, when you kind of have that high-level, you know, what we call like SWAT team kind of approach, um, where you're ready to really sit down and look at solutions and you and you and you have some budget in mind as well. It's it if you're going out shopping without a budget, you know what can happen, right? It can, it can kind of it can get out of the hand sometimes, or you, you know, you can get

SPEAKER_01expensive.

SPEAKER_03Things get expensive or your your wish list keeps growing, you know, of all the things that you want. Uh so really know what your budget kind of can can can accept and and what kind of you have approvals for leading into this sort of thing. Because it'll help guide your your thoughts and your and your scope of work. Um and then on the on the really granular side, you really, as you get deeper into it, you're gonna need somebody to help you with data governance. You're gonna need somebody that understands where your data lives today and understands your process from end to end.

SPEAKER_03So, you know, everybody from either either recruitment, they might not be in the MSE department, MSP department, but they're they're part of the process. Your EM, you know, your HR team, someone from HR, someone from your EMR, someone from your Rev Cycle team, you know, all the different groups, your enrollment, your enrollment teams, uh, your credentialing teams, however, you're structured, because the the vendors really need to understand that going into these discussions.

SPEAKER_01So let's talk about really quickly how deeply should the MSO department, the vendor, really look and examine the current workflows, staffing, volume entity, integration. I mean, even the pain points, what what are you should they just bring you all their problems to the meeting, or you know, should they just, you know, maybe be a bird's eye view? What do you suggest, Matt?

SPEAKER_03I suggest bring it at all. And then you can go as as deep as you want. And and as and you're at least at least you're at least you're at least you have it. And that really shows the vendor that you've you've you're doing your homework. And it'll it'll either help the vendor show up with the the right information and start to plan for the proper demonstration, but it's gonna, but it's gonna really tell them like how serious are you about this? And you know, how much knowledge do you are you bringing or wanting to bring to the discussion?

SPEAKER_03Because that steps up the vendor's game. You gotta, because that's what that's what they respond to.

SPEAKER_02So then what should or would make a responsible salesperson say, you know what, you're just not ready for the demo yet when they first communicate?

SPEAKER_01Yeah, like please just go back, do some more. We'll we'll meet next Tuesday, y'all.

SPEAKER_03Yeah, yeah. And and that's hard sometimes because you really want to coach them through it, right? You really want to help them show up with the right information. So, I mean, again, if you see someone who's who doesn't have, say, the one sign of the the decision, right? If does the decision really sit with you? Uh, or is the person not available? And you're and you know, the salesperson at that point in time needs to make the decision, you know, maybe we can do more of a discovery session as opposed to like, let's wait, let's just take everybody's time.

SPEAKER_03Before you get everybody's everybody's faces in the room and everybody's brain's thinking about this, you really want to make sure you have it all kind of sewn up to the best in the best degree that you can. Um, because everybody's busy, everybody's got their schedules. And to get a 35, 40 minute demo or an hour, or sometimes two hours, three hours. Sometimes these demos can go on for days and weeks, depending on how this how big the company is, right? So you really want to make sure that you're not wasting anybody's time. Um, because that's what we can't make more of, right?

SPEAKER_03So that's that's uh that's kind of like the number one, you know, thing I always recommend is if if it's if if it's okay to say no, it's not you're it's not time. You know, you're not, you know, if you if you want to bring these things to the table, it's gonna help us make a decision faster, help you get the information you need to make a better decision faster. Um, but those are kind of the checklists that that I would rely on, you know, from a sales perspective in order to know if my clients are ready to really get into the weeds with this and and make a decision.

SPEAKER_01So, how many times, my love, are you sitting at the table with the leadership? They're telling you all of their problems, and then you talk to the credentialing team, and it's not exactly what the leadership was saying. And so now it's kind of like you have to restart the problems over. You know, I mean, do you see that often? Tell me what that looks like. I I know Nile's like, let's get into the implementation, but I'm really like wondering even the pregame, does that happen where leadership kind of takes over the call, or is it more from the MSO and the people actually doing the work?

SPEAKER_03Yeah, well, it's sometimes it's both, but I, you know, the and the executive leadership usually will weigh in on kind of what they're seeing or what they've heard, uh, which is okay. It's it's part of the process, and you you got to kind of understand where they're coming from. But the MSPs or the MSO groups, the the med staff teams, you know, that's where it kind of lives in the day-to-day. And that's where we get the most, I think, tactical information that we need in order to really help them, you know, and then it helps leadership understand exactly what's going on, you know, because it's it may just be that they, you know, have some outdated processes and and the technology might not be the issue, or the tech is horrible uh and it can't meet the current scale or demand of the organization, or it's both, or you know, they're coming off of spreadsheets and they don't know how to use a technology or platform.

SPEAKER_03So, so it's there's all these different variables that can kind of weigh into that this that decision. Of course, you know, executives are always thinking about, you know, how can we do this at at you know in a more efficient way? And and MSPs are like, hey, you know, we're there's some things we want to change around here if you want to do some things efficiently, you know, right? It doesn't have anything to do with the software, you know. So you have to kind of let that air out a little bit and be a facilitator of that. You know, I believe you should help facilitate the true uncover those things because they're gonna show up.

SPEAKER_03When you start going into implementation, it shows up.

SPEAKER_02That's a really good question. So, Matt, we want to move on and get onto some real tea for our MSPs. And we really want to know you brought up money. Uh, we all know that in the struggling healthcare economy that we are in the things today, unfortunately, the medical staff office is sometimes looked at as a paper department, not a revenue generating department, which we all know is not true. We are the number one, you know, funnel, right? Where revenue generation even begins because you can't do it without a doctor. So we want to know, um not necessarily how things are structured, but our question, our secret little question we always have is how are software salespeople typically compensated?

SPEAKER_02And can that compensation structure create pressure to close the deal or maybe overpromise, oversell, over um state things just to you know, close the deal?

SPEAKER_01I mean, not how much they make every pay period, but you know what we're saying. Yeah.

SPEAKER_03Yeah, absolutely. Absolutely. Um, you know, some sales structures are different, but you know, compensation is based on performance, like in any job, right? So, um, you know, as a sales professional or sales account manager or, you know, a sales leader within an organization or software company, you know, their job is to, you know, sell the software. And can they overpromise, under deliver? Absolutely. Um, so there's a lot of things that you have to be uh in lockstep with in order to understand what that salesperson's actually doing.

SPEAKER_03Are they are they bringing in their IT department? Are they bringing in the people who've actually sat in the seat and understand the workflows? Have they have they really listened to you? Have they delivered a contract that has all of the deliverables really well orchestrated and mapped out? So there's no questions. Um, if you give them a blank slate and just say, yes, I want your software, and you take whatever they hand you as the master services agreement or whatever it is, whatever the contract vehicle is, without truly, you know, baking in those those those points, then the salesperson, um, you made it really easy for them.

SPEAKER_03And they they're not earning their paycheck, you know, if if they're doing that.

SPEAKER_02Oh, I will exactly. So the MSO

SPEAKER_01with all the notes is a good thing. It's a D O C D. O C D you guys

SPEAKER_02quick. Yeah, yes. And my quick question is how important to you as a software developer, and I think this is true for any industry, not just credentialing, but credentialing is such a niche industry. But let's, it could this could definitely fall under any software. How important is it for your salesperson to be aware and know and be confident and speak to and have knowledge of what the end user needs? And do you make that a priority in your company?

SPEAKER_03Absolutely. It's a it's the top priority. Um, you know, the development of our software is through the eyes and the work of our not only our clients and our users, but also our team. You know, our team is made up of credentialing specialists who've been in the industry for collectively, you know, over a hundred and something years. I I lose track of, you know, most of them have spent at least 10 to 12 years in the seat in some capacity, whether they've ran CVOs or run national CVOs or run, you know, uh the software within a CVO or the data and analytics pieces.

SPEAKER_03So we bring people, it's really important that you're talking to industry experts that are also familiar with the product because that way they can help you to really map where you are today to where you will be in the future using that product because it's gonna change how you do things. And and a lot of people think that because I'm getting a new product, I can continue to do what I was always doing, and it's really not how it works. Every software is built a little differently, even though the workflows are somewhat interchangeable because you guys gotta be able to pivot because you guys pivot every, you know, every day on everything.

SPEAKER_03Uh, so it has to be a platform that can take action. And only people that understand that are the people who have sat in the seat.

SPEAKER_02And I can tell you this is number our number one frustration. Number one frustration.

SPEAKER_03Yeah, yeah.

SPEAKER_01Well, I'm looking when we're thinking of that, right? So, what are some of the warning signs, right? That the person maybe I and not speaking of Acorn, I understand that you guys have 55,000 years of experience. I get that. But the demonstrating the person, you have a software, they're doing a demo. What should be some of those signs that the MSO is saying, this person, you know, maybe understands the technology, but they really don't understand how credentialing or what I'm doing. You know, how does the MSO kind of make that distinction?

SPEAKER_03Well, if they put you through a canned kind of you know, demo of the product, like they're they're not able to really go, you know, several, maybe three or four more layers into the product itself because they don't really understand what you do. So usually you have to throw the questions in. You got to be able to kind of take the demo by the reins, you know, and say, listen, I want to see this. Uh, and if if if it's set up properly, you come with your questions. You you come with the gotchas, you know, because that's the only way you're really gonna find out if the product can really do and do what you need it to do.

SPEAKER_03It can do a lot of things, obviously. It's it wouldn't be here if it couldn't, but it may not be the right size for your organization because every product's built with a little different lens and a little different use case built around it. And even their client base may be different than what you do, but they're trying to fit you into that box. So you got to be really kind of on your game when you're coming to that demo, not to be like, you know, I want to, you know, I want to throw you off your your script and I want to get you kind of in my mind and doing what I want you to do. But you know, take the time and say, you know, do we want to do questions before or during or after?

SPEAKER_03So you know kind of how to guide and how to inject insert yourself into the demo, into the conversation. Because you want to sometimes record these things if they're allowed. Not everybody records demos, but if they're allowed, um, you know, you can socialize it a little bit more and then come back with better questions next time.

SPEAKER_02And really hold the line.

SPEAKER_01So sorry, Nileen, but really hold the line too, right?

SPEAKER_02Yeah,

SPEAKER_01yeah.

SPEAKER_03Yeah, yeah, yeah. And but you got to know your work process and and your pain points. And of course you do, and a lot of times when you're on the call with someone, you forget them all, you know, you know, or you just can't remember every single thing because it's it's a lot, right? It

SPEAKER_02is

SPEAKER_03it's a lot. Products in this space are very, very, uh very deep and wide when it comes to you know, all the different things that go on into the in the credentialing and enrollment spaces, or what we like to call provider readiness. Um you can't get to everything in 45 minutes. So you really want to, you know, take your time and and get a second, maybe even third, look at it just so that it can be what you know, the choice that you really want, and you've asked the questions, you've thoroughly put it through the process. And not every vendor will allow you to do that.

SPEAKER_02So, quick summary of what we just talked about get the right people at the table, right? Ask the right questions, right, Shannon? And I leave and get get ready.

SPEAKER_01Well, I would say too, like like Matt said, right? Make sure that you have questions lined up. So, is this gonna do my rosters? How are you monitoring my people, right? Can I pull their information? What if you need to map something? Are you gonna charge me? You guys need to think about all those questions because if the people start saying no, yes, no, yes, like Matt says, record your demo and then you can say, but you told me this, and then you can kind of make sure that you're working it to the system that you're needing.

SPEAKER_02Okay, exactly. Good point, Shannon. So, all right, we've made it to the demo, we've talked about prep, where their demos are designed really to show the cleanest path, right? Y'all have created the databases to show us how they work ideally, but credentialing is rarely clean, the cleanest path. We have multiple entities, we have delegated agreements, we have oddball players, we have six facilities with six different types of delineation of privileges, we have rosters that need specialization because there's certain dates.

SPEAKER_02We've got flu, right? Declinations versus acceptances versus done elsewhere rosters that have to be sent out. All of

SPEAKER_01that, all of that in the box.

SPEAKER_02All of those things.

SPEAKER_01Tap in if you guys have any of those issues. Please comment and share.

SPEAKER_02I know. So why can the system shown during sales feel completely different during now implementation? Now we bought the software, we got the software, you showed us how beautiful it is, and now it's like, oh, wait a minute.

SPEAKER_03Yeah, I mean, it goes back to that prep, you know, when you're going through the demo process, if you're able to get a slice of your information or your data and get it into the system so you can see it living and breathing within the platform itself, that's always the best. But it's sometimes not easy to share data, um, especially in healthcare. It's just, you know, it's not easy unless you're under contract or under, you know, 17 layers of red tape. Uh so you know, what we try to do is set it up the best we can so you can see it.

SPEAKER_03But it is a controlled demo for the most part. So seeing kind of what it's like um with all of your information. Now, to your point, getting the get getting into a new system, you don't always get the, you have to take some time to clean up and and re and organize, maybe and reorganize some of your your data governance structure, your data processes, where are you all those factors that come in? What are you getting from recruitment? What are you getting from HR? What are you giving to HR? You have to really understand and help the vendor understand those those things so that they can draw that out and they can put it in writing that here's here's what we're gonna do.

SPEAKER_03And they build that into the plan so that when you go in, when you're going through implementation, you can see those things at certain times. So you can you can you may have to make some pivots and adjustments in your standard operating procedures. Um you want it to align with your you know your crediting bodies, your you know, your JCOs, your URACs, your you know, NCQAs, all the things, right? Um so you and especially when it comes to payers, there's all kinds of things when it comes to rosters. Rosters are rosters are pain of all

SPEAKER_02of our existences.

SPEAKER_03Yeah, well, and ours too. Um, you know, but we're we're finding better ways. Yeah, yeah. And we're we're finding better, better ways to manage that using you know some of the newer technology, some of the newer tools, um, because it is more just logic-based. And instead of us, you know, trying to do it manually, you really want to build uh a way to map those things appropriately because they will change what like some rosters change almost monthly, some of them change quarterly, some of them change annually, depending on the payer.

SPEAKER_03I mean, you want to have some ability to adjust.

SPEAKER_01Even the payer changes.

SPEAKER_03Yeah, the payer changes all the time.

SPEAKER_01You know, you have to ask, like, hey, how do I rename this plan in my system? Because I don't want to call it this anymore. I want it to be reflected correctly so that my billing front office person, you know, knows what to do. I mean, so really, you know, like Matt was saying, you really have, and Nailee was saying you have to think of the whole entire scope and you know, what is it, life cycle of the provider and where your credentialing software can kind of help or not help, right?

SPEAKER_03Right. Yeah, and you gotta you've gotta build a schedule, you the best you can, a schedule so you can you can give the vendor enough time and you enough time to actually make those kind of pivots, even though they they sometimes happen in real time. You almost want to just put put you know mile markers in the road, you know, for your annuals with your vendors. Yeah. So I mean, if you're if you have quarterly business reviews, which everybody should have them, uh with your vendors, you make sure that you've you put in those quarterly business reviews any sort of milestone or changes that have come through, you know, NCQA or have come through any of your accrediting bodies or your rosters.

SPEAKER_03And if if it has to happen before then, then you put a monthly meeting on the on the board just to review. You know, monthly, if not, I mean, if they're not meeting with you, at least monthly, to kind of make sure things are in a stable state. Or, you know, things are still not stable because the roster hasn't been completely, you know, scoped out properly because the payer won't give you the best and latest version of it right out of the gate. So you have to go searching for it and you have to, you know, know somebody's brother to get to get a copy.

SPEAKER_03That

SPEAKER_01happens, yes.

SPEAKER_03Uh so so we know there's some there could be some lag there, but you know, we we try to get in front of that as best you can and have monthly tech reviews so that you can go through some of the challenges that you may be having. Um, and it may be that the it the maybe the feature and function is there. It's just you haven't been, you know, it's a pretty big system. Maybe you just need a little training. Well, maybe we need to build something, maybe we need to put some more functionality in there. You know, that's for

SPEAKER_02sure. For sure, Matt. So before we get into the contracting, let's just do a brief summary of this little section. We basically is you want to require a scenario-based proof of capability. You want a written assumptions log, you want to uh ensure you have a list of separating functionalities and understand what you need versus what they need and that the communication is happening, uh-huh. Configuration, uh talk about whatever customization you particularly need for your organization, your type of whatever. Um, look at the integration, look at your future roadmap.

SPEAKER_02And I love that you said ensure you have that quarterly business review at a minimum with your software uh implementation team, right? Or leader or whatever. Um and then quick question to second answer. Um, how long do you usually dedicate that project implementation team? Is it six months, is it a year, or is it that full three-year initial term usually?

SPEAKER_03Um, well, you what you want to do is make make sure that someone's with you that knows the history. You know, you if it's and some and you know, there's turnover in some organizations, and they can't help that all the time. But you know, you want to make sure there's a historical record at least, and there's a handoff. Um, so as you're going through, you might have a different implementation team because they're they have a different level of specialty when it comes to data and configuration and all the things, the more technical stuff that go on. And you're say you're ongoing support person, maybe someone who knows credentialing and it can help you to you know take action within the system on some of your you know the the needs and can better define what your challenges are to the IT team so that you're not having to translate, you know, to uh a technical specialist, you can really just let that person do it.

SPEAKER_03But that person should be along for the ride the whole time, you know. Um, and it like I said, the seat might change a couple of times, you know, depending on the nature of the organization or the growth or whatever, but I think making sure that you have some historical way of looking back at what you know maybe what you've been working on and what you've been working towards, so then you're not having to start over every every month with someone different.

SPEAKER_01Well, I have a question. So have you ever heard of a like a written demo assumptions document?

SPEAKER_03Uh yeah, yeah. Absolutely. Is that

SPEAKER_01something that is used often on the sales side? You know, some people have talked about that in and when we were gathering some due diligence for this. And so, you know, is that an important document? Should everybody kind of look into that? What do you think about that?

SPEAKER_03Absolutely, you know, we call it discovery, right? So we use kind of like a discovery tool. So we we give you a

SPEAKER_01law and order here, okay, Matt.

SPEAKER_03Or we have a we call it a disco actually. It's like a disco, right? So we we kind of use the term disco because we like we want to disc so we send you a kind of a pre, you know, interview of what you're looking for, some some specific questions that help us, you know, outline the demo or help us outline the you know, the the structure of the just the even the discovery session where we're just talking. So you have some way to collectively get people to weigh in on stuff before we show up and just start peppering everybody with questions and expect everybody to have all the answers.

SPEAKER_03So, you know, we you know, I hate I use the term never show up to find out. So I always ask for an agenda. I always ask for what, you know, what's this really gonna be? You know, who am I here to talk to, you know, whether it changes or a little bit, or at least I have 80% of most of what we're gonna talk about kind of prepared prior to going into those discussions, just so that we can have a a you know, efficient and productive meeting. I mean, that's what you want, that's what you'd ask for in at any meeting. But you know, sometimes these things can go, depending on who's there and you know, the personalities and and all the things start happening, and you gotta really be able to facilitate that.

SPEAKER_03So you so having a agenda item where people have weighed in and they know what to expect when they show up is usually the easiest way to kind of get going as fast as you can with a small group or even a larger group.

SPEAKER_01Nileen, are we signing the contract or are we not signing the contract? Where are we at?

SPEAKER_02Oh, we're about to sign the contract, Chat today. And I know you all about the details.

SPEAKER_01Well, I was wondering, you know, because that's like the part that I think a lot of people underestimate is the contract. It's you know, a lot of them come in with multiple multi-year agreements, you know, they're very common, and vendors may be making, you know, we understand substantial investment in in implementation, configuration, you know, staff integration, all of that. But at the same time, buyers may be committing before they have seen how the platform performs inside their actual world. What do you think about that, Matt?

SPEAKER_01Uh, you know, a multi-year agreement, um, and what protection should kind of exist for the vendor, for the buyer, um, so that, you know, no no one's hearing all the risk. Yeah. Exactly. Yeah.

SPEAKER_02Exactly.

SPEAKER_03Yeah, I mean, I think, you know, we I would think that you would want to make sure there are specific milestones called out, you know, within the contract. Okay. Because that that protects everybody. It protects you, it protects the vendor. It it if you if you're if you're not meeting them, there should be one, a very strong project management team that's going here, you know, it should not be a a surprise to anybody that we're not hitting a milestone. But there should be a very good reason, or if the vendor just can't get it done, and you so you should have a way to, you know, based on performance, exit that agreement, you know, as long as it's you know been documented properly, because what you don't want to do is, you know, not just have a well, we decided to go a different direction.

SPEAKER_03And then the vendor's kind of like ouch, you know, um, you know, that's we met all the milestones, and then it becomes kind of an argument of who did what, when, and where. So you want to make sure that everybody's being held accountable throughout that process. So the multi-year contracts are still there, but you you you can navigate around them a little bit.

SPEAKER_01Oh, that's a good thing. I mean, can you understand? Can you help us understand like what does the vendor invest up front? Just so that the MSP community kind of understands. That's a

SPEAKER_02good question. Yeah, we want to know because that's not our world. And I think it's important for them to understand why it costs what it costs. So, what are some of the things y'all spend money on that we don't even know about?

SPEAKER_03Yeah, so you know, one, there's the the software itself. Uh, the software it costs, you know, you think of it, a lot of people think of the licensing agreement or the the license per physician or the however the it's structured is kind of what you're paying for, kind of like a a Netflix subscription, you know, you know, for$4.99 a month. I'm gonna get I'm gonna get access to all this stuff. That's part of it. Um, what what we do with like some of the additional costs, things like that, if there's training, if there's additional team members that have to come on and things like that for implementation and IT, right?

SPEAKER_03So you've you've requested some specific IT support during like an implementation for some of the customizations that you want. Those types those types of things kind of get outside of like a general scope of, say, just a license of the software. Because if you just want a license to the software with some training, it comes along with it. But if you want some additional kind of you know support and addition some additional kind of customizations within the software for you specifically that you've called out, that's when it, you know, it gets a little bit outside the traditional scope of what the vendor is probably planned for.

SPEAKER_03So when they're scoping out your engagement and they're scoping out the the amount of time it's gonna take you to probably get to go live, and all that should be straightforward and shared, and everybody should agree on it. There's they're planning for a runway before they start, probably charging you for those licenses. So there's a whole there's a whole maybe three, four months that goes into work before you even get a license of people. The transition,

SPEAKER_01yeah.

SPEAKER_03Yeah, in the transition before you even get to using the license. Um, so you know it's it's kind of like you know, there's different ways to approach that with different with the vendor, but I think, you know, um the more the more you have spelled out the better.

SPEAKER_02And they also you you also mentioned uh cloud storage, right? Because now all of our databases are cloud-based and the same way that we have to pay for our Google Drives or our iClouds or whatever, we have to pay for, or you as a software have to pay for the storage of our documents to be stored, housed, and then of course the cybersecurity goes along with that.

SPEAKER_01In a cloud with a Halo, yeah,

SPEAKER_02yeah.

SPEAKER_03Yeah, I mean, uh that should, you know, and your licensing fee, you know, that's where those costs are associated with, you know, turning on the lights, right? So, you know, there's a lot of job, there's a lot of machines doing a lot of work, you know, when you're actively using a software platform. And that's like turning the power on in your house. So, you know, if you if you have the power off and nobody's using it, then you won't get charged. But as soon as you turn that power on, you know, everybody starts to incur costs. And yes, you have to have certain certifications these days and SOC to agreements with different cybersecurity insurance programs, all the things kind of lump into kind of your overall costs that are associated with those licenses.

SPEAKER_03So the more complex systems, the ones that are kind of underneath the uh say IP or the you know individual protection or things like that within healthcare, you know, there's a lot of weight that comes with hosting that in that information, um, especially in a cloud. You know, um, cloud is a little bit cheaper because you're sharing that house with a lot of others. That's how we can make it more affordable. And you can get better features faster when it's cloud-based. If it's an on-prem solution, that's your own, that's your own house.

SPEAKER_03You've got to you know, renovate it, you've got to customize it, you gotta pay your own electricity bills on it. And and not everybody has that infrastructure to do that.

SPEAKER_01You cost money. That one cost okay. So, really some tea we need, okay? In case y'all was getting bored, we've got to get it lively. So, when a platform, again, not Acorn's platform, just saying there's a lot of people out there, repeatedly fails to meet documented requirements. Because remember, you were saying put those milestones in there, service commitment, security, right? Um, you know, things are downloadable, you know, all of those things that kind of go wrong. What remedies should the parties consider? You know, when is it considered a material failure?

SPEAKER_01Like, you know what, this really should not be for you. We need to just go on and back out. Like, at what point does the MSO, the leadership on that side, understand like maybe this software isn't for us, even though they did promise us a big package?

SPEAKER_03Yeah, I mean, uh, you know, I'd say within the first year, you know, you really need to get into a software and start using it before you make some of those decisions. Um depending on how fast you you you get into those systems, how fast your transition, how well adaptable and adoptable your teams are, and how well the the the vendors are responding, the software companies responding to those SLAs, those service level agreements. All that should be tracked and managed and monitored.

SPEAKER_01So you like have to walk in the mud before you could tell if it's mud or quicksand, right?

SPEAKER_03Yeah, I guess that's one way of putting it. Uh I mean you don't know, right?

SPEAKER_02You have to

SPEAKER_03learn to swim across the lake before you know before you jump in, too. So it's one of those things where make sure that you you have the proper training and you have the proper support in order to make it across the lake. Um, yeah, if you're walking in in the mud and that's the kind of way you feel, then that might be a sign too.

SPEAKER_02Okay, and then that's and and so just really quick as a as a as a thing about that is too, is so how negotiable are truly are these contracts or these set termination dates or these auto renewals? Like how negotiable are they really?

SPEAKER_01Like, help me. Are you gonna be like, okay, let's do a meeting, let's talk this through, you know, like what what is the

SPEAKER_02or are you just gonna be right, are you just gonna say, too bad, you sign a contract, there's no negotiation. I mean, really.

SPEAKER_03Absolutely not. No, I I we have to we have to have those conversations. Um if we're not if we're not having those conversations with our clients, then we're not really we're not really working with them or for them. We're just kind of you know doing our thing. We're we're you know, depends on the size of the company too, and the depth of that company and how much they really pay attention to credentialing. Um whether

SPEAKER_02they're even based out of this country or not. Because let me tell you, I've got some terror experiences with some software companies. And oh, I had to pay those three years, boy, did they remind me.

SPEAKER_03Yeah, yeah, and that's where on the front end you want to be really prescriptive. You know, I always say let's let's let's be prescriptive, let's kind of know what look at your past experiences. You you you you've learned from those things, right? Bring those to the table and and be open about those things. Because the more you're open about those things, the better we can we can address them in the contract.

SPEAKER_01So, Nileen, you really have to paraphrase that, right? Like record, document your milestones. What else did Matt say? Because you've been paraphrasing for

SPEAKER_02it.

SPEAKER_01Make sure you

SPEAKER_02have your termination, yeah. Make sure you have your termination triggers, you have your limits on fees. I think also, Matt, another thing maybe we didn't touch on, but definitely review that contract, look at the terms, look at the definitions, look at the auto renewals. Um, make sure you have that transition support, you have any export import costs delineated on the mapping

SPEAKER_01costs,

SPEAKER_02right? Mapping, and then the accessibility of termination and that termination clause overall.

SPEAKER_03Absolutely. You captured kind of like 99% of what you should be, you know, there's always gonna be a something in there that you want to, you know, maybe think through, but but you don't want to make it so you don't want the contract to be so customizable that you can't get it through your own procurement office or through your own legal department. Uh you know, because you can see

SPEAKER_01that.

SPEAKER_03You can't be like Matt is gonna wear

SPEAKER_01purple to the next three meetings, you guys. You guys cannot write that in the contract. Okay, come on. That's you can

SPEAKER_03absolutely write that in the contract.

SPEAKER_02Hey when I like purple.

SPEAKER_01Matt will have me a whole live oak forest in five years. You cannot write that in there, okay? Come on, guys.

SPEAKER_02Okay, all right. Shannon, so let's talk about implementation. Take us to implementation. What's what's your take on that?

SPEAKER_01Okay, so I guess we are signing the contract. We're gonna get in that multiple year. We're gonna uh contract. So, should a prospective client really, you know, really ask again, I guess just really sealing this up in writing based on the client's particular invitation and operational risk. So you're saying yes, make sure all of that, any kind of risk are there in writing.

SPEAKER_02Correct. You're gonna get into that agreement, you're gonna want everything in writing.

SPEAKER_01Okay. So just wanted to make sure, because you know, a lot of people are are kind of um always leery to kind of write all of that stuff down and stuff. So, you know, just want to make sure. So here's where everyone starts pointing, right? The vendor says that the client did not provide clean data or even make decisions, and the client says that the vendor oversold the product and underestimated the work. Meanwhile, the medical staff office team is still maintaining two systems and a spreadsheet. So, really, when we're looking at it, Matt, who is responsible when implementation fails?

SPEAKER_01The software company or the credentialing department, or maybe even executive leadership, or do all of them kind of have a hand in it? What do you think?

SPEAKER_03Um, I usually go with we all have a hand in it, um, to some degree. It's not one more than the other sometimes. Sometimes it's equally spread across the entire you know, relationship and partnership uh within that organization. Okay, I have a question. There's only yeah.

SPEAKER_01I have a question. So, what are the top three client side behaviors that really derail implementation when you you feel like you've gotten past it? But then you start seeing some of these behaviors on the client side.

SPEAKER_02Right, because we all know as MSPs what the failures are on the software side. We know that. What do you as the software see us on where we're doing right?

SPEAKER_01Give us a mirror. We need a mirror.

SPEAKER_03Yeah, well, it usually comes down to data, right? Um, for us, you know, we live and breathe off of the data because that's kind of the lifeblood of our of our software. It it what it's what makes it run, you know. So if the data is corrupted or it's not it's not a good clean version, you're gonna see that right away in any software. As soon as you put it in, it's basically it's gonna show up, it's gonna show you the gaps and things, it's gonna show you where you, you know, maybe had a naming convention go south, and you had 15 other different things over here doing, you know, you did it two years ago this way, now you're doing it this way.

SPEAKER_03So all that stuff. Starts to really show up. But if you're if you're really taking it through the process, no, none of that information should ever hit production, live production without being validated by you. So really taking that time and making sure that you have a team that can help you validate not every inch of that, because some organizations are just too big to, but you really have to understand how to validate the information and the configuration of your system. So really that's where we see some of the shift, right?

SPEAKER_03So people start showing up with different versions of the data, different requests from different departments are saying, hey, can we push this in there? Can we pull this from there? Can we do these things? Everybody starts to pile on once they see something new that could potentially help them. So that always sends off our spidey sense. We're always like, oh no. You know, it's it's a good problem to have, but it's also it can be very distracting to the MSO. It can be very subtract subs, you know, just distracting in general to everybody because the vendor wants to say yes. Yes, we can do that.

SPEAKER_03But you know, we can build rocket ships to Mars too with enough resources and money.

SPEAKER_01Say it.

SPEAKER_03But we don't have that in this, in this, in this current agreement. So if everybody starts to weigh in, we start to see it going

SPEAKER_01for one team. We don't have an agreement to build the rocket ship today, but tomorrow.

SPEAKER_03Yeah, you want to renegotiate? We can renegotiate. If you want enrollment to do this, or if you want your your um HR team to, you know, import certain data from their system or export data out, or you have their recruitment team, so you have this ecosystem around your provider readiness so you can get them ready for clinics so they're ready to see patients. All those things have to be orchestrated properly. And if if they're not involved in the you know, somewhat of the discussion, they don't have to be involved in everything. But if they're not involved and we find out halfway through that this new part of the organization needs this information or has lived off this information, we just forgot to bring it up, or we just didn't think we were gonna have to deal with them again.

SPEAKER_03You know, we hear all the different things, that's when the the red flags start to be sound for us. We start to see, like, okay, this project's getting a little bit out of scope than where we originally started. And that's where it kind of can get, you know, you have to try to keep it out of the ditch, you know. So you really have to set up those parameters. You really want to make sure that, you know, the team understands that this is there's our out-of-scope bucket over here. These are all the things we agreed on, and these are the things we'll have to talk about. You know, maybe we don't have to renegotiate, maybe we can make it through it, you know, and we can get it done.

SPEAKER_03But don't but that impacts everything timelines, milestones. You start piling on things, or the vendor starts saying, Oh, you know, we're doing something different now than what we were doing when we sold you the product. We have this new product that we're gonna be launching in in Q2. We're just gonna put you on that. Like I've heard stories of that. Um, so you know, that can happen. You know, it's you know,

SPEAKER_02yeah. That's totally understandable. So, okay, so basically it's all of our faults. We all have a little bit of part of it. We got it. Don't evaluate your credentialing technology in isolation. You are just as much as fault as the software guy. Sometimes we need to be responsible for our own problems.

SPEAKER_01Tylene, I'm gonna say comment below if you are the drama. That's that is the drama. Okay.

SPEAKER_02Exactly. All right, so let's talk about what's the word that everybody loves, which is automation. Automation should not automatically mean eliminating people because we all know we are not replaceable. Our spidey sense, our gut feeling is not something AI can replace. The better question is whether technology makes us work faster, safer, more consistent, easier for the people responsible for completing it. Right?

SPEAKER_01Yeah, I mean, Eileen, you're not lying. Sometimes a company describes a process as automated because the system sends an email, right? How many times do we hear that? Or it even creates a task. But a human, you all still has to retrieve the response, review it, rename the document, verify the information, upload it, index it, update another system. I mean, are you guys doing any of this information process, or is it just me and Nileen that do it every day? Because one automated action surrounded by seven manual steps, my love, is not end-to-end automation.

SPEAKER_02Right.

SPEAKER_01I mean, Matt, what are you thinking about this? When a vendor describes a feature is automated, what should buyers ask to really understand exactly where the automation begins, where it ends, and where work still needs to be done on the back end by their staff, my love.

SPEAKER_03Yeah, I mean, that's that's part of that process. So you understand kind of it automation doesn't mean it does it for you, right? Human in the loop is required based on accreditation standards. NCQA, you know, human in the loop, you've got uh they don't allow it. Human in the

SPEAKER_01loop. Okay.

SPEAKER_02Yes. Yeah,

SPEAKER_03validation doesn't happen by machines. Machines can go do stuff, it can go grab a license for you, it can pull things in, but you have to show the audit that says that this MSP actually looked at that license and validated it. Not a machine looked at it and said it was good, you know, because that's not what's going to get you through your audit. You know, so that and and if you want NCQA accreditation, so you have you know abilities to do things with payers or payers, you know, do this too. When you hand that information over to them, they're running a similar type of process on their end, just like they have their own MSP department over there that's cross-checking everything that you did from those primary sources.

SPEAKER_03So if you're getting it from a data broker that's using a different primary source, or you're getting it from a from not the primary source, that will come out. It will show. So when you're setting up automation, like you know, alerts or reminders or a workflow within, you know, creating a document or filling out a document, machines can be can get all over that stuff. And even AI is being is driving some of this, but AI should not be, AI should not be, should not be touching your data in ways that aren't um allowed within every organization's treating AI a little bit differently.

SPEAKER_03We're very sensitive to that. We're using our own language learning models, different types of you know, semantic versus agencai to do different things within the system.

SPEAKER_02And

SPEAKER_03we're but that also costs more money. So, you know, it's not cheaper to do some of this work now at scale, at scale it is, but you have to make sure that your workflows allow for that and the credentialing bodies or the accrediting bodies allow for those things because you know they'll throw out a ruling

SPEAKER_02in July

SPEAKER_03and they'll change that ruling because they they went back and saw an audit.

SPEAKER_02And so far, we've seen AI being incorporated as a new um section in all of our accreditation manuals. So for all the MSPs out there, make sure you're checking your updated most current versions of your um manuals. Particularly, I just went through a big overhaul with Triple HC. So these are big sections being added to AI regarding AI. So that also has to be taken into account when we're using softwares that use AI. So let's talk a little bit about AI because I'm sure that AI is being used somehow, some way about data migration.

SPEAKER_02When we want to move, now we have established uh credentialing softwares. We found another one that's a lot more practical and useful. And hey, we want to move because I can't spend a million, maybe I can spend 600,000 next year. So I need a data migration. So really quickly, uh, why do credentialing data migrations become such a nightmare? And what information is most commonly lost or flattened?

SPEAKER_01Can I say one thing about automation though? I'm sorry.

SPEAKER_02Yeah.

SPEAKER_01Because I think it's very important for everybody to realize that, you know, the credentialing software makes us more efficient. But again, like, you know, the human in the loop, right? It's not gonna do everything for you. We don't want it to, but you wanna use it in a way that again, like we talk about great culture. You you're able to show your data, you're able to show how quick your team is, you're able to show how efficient your team is, and those are all great things, but we don't want something where the human in the loop is becoming lazy, sorry to say it, because they're depending on the system to do so much for them when it's really that system is there to make your office and your processes more efficient.

SPEAKER_01I mean, Matt, do you agree with that?

SPEAKER_03Absolutely, absolutely. I mean, that's the game, is is you know, developing more time. Because there's always going to be the scenarios where you have to pick up the phone and talk to a provider or talk to an ex you know, someone within the system that takes you away from say your day-to-day, you know, work and the and the things that have to continuously be going on in the background. So instead of you having to go out to you know, 150 sites to to grab different state license boards,

SPEAKER_01you

SPEAKER_03know, put automation to go do that for you. And then you have, you know, then you flag the ones that come back, you know, the and that so that's that saves you time. So incrementally, you really have to understand where you are today and like what is how what are your metrics, what are your KPIs around your operation and and your deployment of your team. So if you don't have that, that's okay. We can you can help you can help develop those things so that you have something to show to the executive team that you are accelerating opportunities with revenue, right? You're not having the bottlenecks with you know bench time and some of the other things that pop up, or from recruitment to to clinic, you want to know you want you want to shrink that time down by a specific amount in the first quarter after you go live.

SPEAKER_03So you have specific things that you can aim at so you can defend even your claim hold denial bucket over in Rev Cycle, they're throwing at you all the time saying, What's wrong? What's what's wrong with the data? What's wrong with the data?

SPEAKER_02Right.

SPEAKER_03Um, and what's wrong with this? Why can't we keep up with these things? Uh rate recreds are coming up and splashes, all the things that happen.

SPEAKER_01But even going back to what Naileen was saying about data migration, data is king, like you said, Matt, right? So that data migration needs to be on point for it to be able to give you all that good data, right?

SPEAKER_03Yeah, absolutely. I mean, that's that is 90% of your implementation. Um, the maybe 80%, but I'd say at least 90% from for most of our clients. And depending on if you're coming from an old legacy system or you're coming from spreadsheets or somewhere in between, a mixed, you know, the Frankenstein model where you got a little bit of everything, uh, or you've used, you know, six other systems over the past 20 years, or you've used the same system for 20 years. You know, we've seen it all. So you you you there's a there's a strategy that you want to deploy, and not everybody is the same.

SPEAKER_03So you kind of you need to kind of show up with people who've been there and can help you understand the mild the the challenges you're gonna have

SPEAKER_02you

SPEAKER_03know with that system, getting data out of it or back into it, whatever it is.

SPEAKER_02Right.

SPEAKER_01What would is there a sample size or reconciliation standard that you that you love that you require before acceptance that you think is helpful to the organization? And I guess it would matter if there's 10 doctors or if there's a thousand doctors, right? I mean that you know, I take it that into perspective. Yeah.

SPEAKER_03Yeah. I mean, I always like to use the 10% rule if we can get it, you know. Um, if we can get 10% of a slice of your information, that'll pretty much cover everything. We're probably not everything, but the majority of the things we're gonna run into and we'll help you to to see kind of that initial mapping of what's what what to look forward and what we can fix, right? And then make some decisions because you may not want some of that information to to come over. So

SPEAKER_02I was just gonna get to that because not everything is migratable, correct?

SPEAKER_03Right.

SPEAKER_01Yeah, it's gotta that's

SPEAKER_02the right word, but like that not everything can migrate.

SPEAKER_03Not everything can be mapped or migrated, or you know, it or even need to live anymore. You might just want to kill that off and put it in a storage cabinet somewhere and have it for reference if you need it. Files are a big thing, you know. The the the files, because you can have millions and millions and millions of files in all the different formats, all the different naming conventions, and and no organization to them. So a lot of times when the data is one piece of it, you have this whole file loading that has to go along with it. So you have a historical record when you of things, you know, over time, and a lot of those things come in various shapes and sizes.

SPEAKER_03So that strategy in and of itself is a big part of the decisions that you're gonna have to make.

SPEAKER_01So I understand what you're saying, Matt, but what do you think, Nileen? Because if migration isn't complete, the buyer should not be forced to accept the system, right? Just because a calendar date arrived. What do you think, Matt?

SPEAKER_03No, I think you you have to change your your your your plan at that point. If you know

SPEAKER_01you're not gonna be able

SPEAKER_03to Yeah, you gotta readjust, you know, the expectation, you know, that hey, you know, we thought we were gonna have this, but with the data quality and the information that you guys want to put in, here's what you're gonna have. And then you move on from there. Because if you're pulling it off

SPEAKER_01of PDFs, that that's more time. I mean, you know, there, you know, the bigger the obstacle, the bigger the time, you know.

SPEAKER_03Yeah, yeah. Yeah, yeah. I mean, we still run into people and clients' health systems that are on paper. You know, I mean, literally on paper or digital paper, you know.

SPEAKER_01Yeah, thank God it's canned in.

SPEAKER_02Well, Matt, thank you so much. It's been so amazing. What we want to do is we want to go into, we've we've done the whole life cycle, right? We've vetted, we've demoed, we've implemented, we've migrated. But what we want to do is we want to do a quick lightning round with you. Short answers, no sales language, down nitty-gritty, so that our MSPs have full uh takeaway as to what they can expect and what's the key points we need to bring back. So quick and fast. Let's see, Matt. Best sign a vendor understands credentialing.

SPEAKER_03Um, they ask you about your exceptions before they show you the dashboards.

SPEAKER_01Okay, I like it. I like it. Favorite season, Matt? Are we talking spring, fall, winter? What's your favorite season?

SPEAKER_03I'm a I'm a fall guy.

SPEAKER_01Okay, it's coming up. Okay.

SPEAKER_02Yeah, wait. Uh-huh. What's your biggest red flag in a demo?

SPEAKER_03Uh for the vendor or for the MSP?

SPEAKER_02Oh, let's say

SPEAKER_01both. I mean, we need it all. We need it all, Matt. We need to give it us.

SPEAKER_03Okay. If the well, the vendor says that's configurable without giving you a cost or a timeline and building it into. Do y'all hear

SPEAKER_01him? Y'all better listen to Matt.

SPEAKER_02Yeah.

SPEAKER_03Um, and if if a vendor, from a vendor perspective, I could there's all kinds of red flags, but we talked about a little some of those earlier. But I think from a MSP standpoint, you'd definitely want to look into that configurability.

SPEAKER_02Okay.

SPEAKER_01Okay, are you an ice cream guy or are you a pie cake kind of guy?

SPEAKER_03I mean, ice cream guy.

SPEAKER_01Okay, period.

SPEAKER_02All right, most dangerous words in a proposal.

SPEAKER_03Ooh. Ooh.

unknownUm

SPEAKER_03sign the uh sign in three years. Most clients sign in three years. I think that's something that if you hear that contract, someone's explained to you a contract um without you know really getting into those renewal dates, um, really understanding kind of what's on the hook within each of those milestones. I think that's those are always the the words that if if those aren't baked in there, um it'll come back to haunt everybody, the vendor and the MSP.

SPEAKER_01Yeah, Nileen's big on that too. She's like, if they say that we're always doing it or it's always been done, then you need to fight them tooth and nail. So I'm like, that's a good one.

SPEAKER_02Pretty much

SPEAKER_01Okay, are you a cardigan type guy or are you like, put me a bomber? You know, it's cold outside. What are you what are you pulling first?

SPEAKER_03I'm I'm a hoodie guy.

SPEAKER_01Oh, hoodie guy, we didn't even have that as an option. Okay, love that.

SPEAKER_02Okay, okay, okay. So one what is the one principle Acorn is willing to be judged by in every client relationship.

SPEAKER_03That you have a personal relationship with us, that you know our name.

SPEAKER_01Yeah,

SPEAKER_03you know my name. You know, every one of our clients should know me at some point, you know, in some part of their organization, should know not everybody in every organization, but should know the team.

SPEAKER_01Matt said everybody in the world should just know him. Okay.

SPEAKER_03I mean, so many people have my phone number. It's on I'm getting text messages while we're here. I'm, you know, it's like people call me, you know.

SPEAKER_02Yeah, they want to meet

SPEAKER_01up. They got to negotiate that contract, Matt.

SPEAKER_02Yeah, I know.

SPEAKER_01Okay, so anything that we miss, like I I just the craziest thing that you can think of that we might have missed that you kind of hear and that you wanted to talk about, you know.

SPEAKER_03Yeah, I think, you know, there is a large movement in the AI space. I know we're all worried about things and and you know, there's some sensitivity around automation uh and how and data and you know, how safe everything is anymore. Um, I think we really have to be careful with with what we're doing and what we're planning on doing and what we're deploying. Um, you know, have an understanding with your vendors of they're not going to give you everything of their roadmap of where they're going tech technically right out of the gate, but you can see what they've already deployed and how they're deploying it and what those models are built on or what they're built around.

SPEAKER_03There are new AI security assessments that are that are being required so that you can explain that to your compliance teams because they're gonna have all those questions. You know, I really think that's another you know layer of this that we're just now starting to set sell into. Um in a in an environment like healthcare, uh, where things uh have been adopted sometimes very slowly compared to the to the mainstream, or sometimes maybe too fast. You know, when you think about what's going on in the surgery field of uh uh with the with robotics now.

SPEAKER_03Don't get me

SPEAKER_02started.

SPEAKER_03And you see what's happening in the back office, and you're like, well, we're doing we're doing laser surgery up here, but we're still running stuff off spreadsheets in the back office. It's like, you know, well what where I see the most innovation in healthcare and where we I think we can do some of the the real work is in the you know the office. That that really helps us run our businesses, our health systems, keep our patients safe, keep our doctors happy. And which is if you can do that, you know, those types of things. But um, no, I love the doctors and they they you know they need to practice medicine, not practice administration.

SPEAKER_02Absolutely. But this is

SPEAKER_03not an administrative task. You know, that's the other thing is I don't want people to think credentialing is an administrative task.

SPEAKER_01No.

SPEAKER_03It is it is the tip of the spear when it comes to a healthcare organization, because if something goes wrong at any any part of that that provider readiness spectrum, then you know it ripples through the whole organization. So the tighter your teams are, the more depth and breadth you have around the leadership and their knowledge of what you what they're what is going on in the industry, the better. And I've seen some of the best teams, and I've seen some of the teams that are grow trying to grow into their their their their growth, and I've seen teams that have you know been acquired and had to move on.

SPEAKER_03I've seen all I've seen all those things happen. And there's usually a wake behind them, no matter what's going on, good or bad, there's usually a wake that you have to deal with.

SPEAKER_01No, we really thank you for your honesty because, like we talked when we were trying to land this interview with you. Um, a lot of people are not willing to sit down and kind of really talk about the things that we've talked about today. So I really want to ask you one last thing, and then Nile can close us out. But if everyone remembers one thing from our show today, Matt, what would that be? You know, two sentences like quick in their mind. You know, everybody's in a TikTok culture.

SPEAKER_03Yeah. Um do the planning. Do the planning, make sure that your contracts are what you want. And make sure that your team is ready for change. Because if they're not ready for change, they're never going to be ready for change. So you really got to build that culture.

SPEAKER_01Is your team ready for change, y'all? Comment below. We need to know.

SPEAKER_02I love that, Matt. So, anyway, to every buyer listening, do not buy the prettiest demo, okay? Buy the clearest commitment by the by the um the the one who is willing to work with you, not against you. And if it matters, it belongs in the contract, the implementation plan, or the acceptance criteria. So we want to tell you guys thank you, and thank you uh for Matt uh to come on our show and share all of these tidbits of information with us.

SPEAKER_02And to all of our listeners, stay credentialed. Shannon, that was a lot of tea.

SPEAKER_01But have they subscribed yet to hear it next week on all of these platforms? Please subscribe, like, and following

Open the transcript file

Hosts and Guests

Hosts

  • Nyleen Flores Co-host Feed-stated
  • Shannen Reyes-Aguayo, CEO & Founder of AQCCVO Host Feed-stated

Guests

  • Matthew Jansen, President & CEO of Acorn Credentialing Guest Feed-stated

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Patient to Credentialing Superhero: The Dylan Avatar Story

    Nov 17, 20261 hr 28 minAudio

    Send us Fan Mail One jump changed everything. What happened afterward led Dylan Avatar toward a purpose he never expected. In this episode of Credentialing Chronicles, Shannen Reyes-Aguayo and Nyleen Flores sit down...

    Credit the people on this episode

  2. Live at NAMSS 2026 (50th Anniversary)

    Nov 10, 202640 minAudio

    Send us Fan Mail Tea dresses, tiny microphones, and a little NAMSS chaos! 🫖🎙️ We’re taking you inside our pink booth at NAMSS’s 50th anniversary conference in New Orleans! This short episode is full of live...

    Credit the people on this episode

  3. The Exam Room Should Be Safe! "I am Jane Doe"

    Nov 3, 202633 minAudio

    Send us Fan Mail ⚠️ *TRIGGER WARNING:* This episode discusses sexual assault, sexual abuse by healthcare professionals, and child sexual abuse. Although the discussion is non-graphic, these topics may be distressing....

    Credit the people on this episode

  4. Spillin’ Tea Across America: New Jersey

    Oct 27, 202633 minAudio

    Send us Fan Mail SOMEBODY ELSE'S DEA NUMBER?! $172 MILLION IN MEDICARE FRAUD?! NEW JERSEY, WE NEED TO TALK! 👀☕️ The Garden State is serving up some SERIOUS healthcare tea, and trust us… this episode is WILD! 🔥 This...

    Credit the people on this episode

  5. Spillin Tea Across America: New Hampshire

    Oct 13, 202640 minAudio

    Send us Fan Mail New Hampshire’s Healthcare Wake-Up Call A provider can be qualified, credentialed - and still out of reach. A provider’s identity can be legitimate - and still be used to submit fraudulent claims. Who...

    Credit the people on this episode