Listen to "All Things MSP" on Your IT Podcasts!
Justin Esgar (00:07):
What's up everybody? Welcome back to the All Things/MSP podcast. I'm your host Justin Esgar. With me always is my good friend, podcast producer extraordinaire. I'm having a hard time saying that in the last guy above both episodes and missing his bacon, egg, and cheese. This is a special breakfast episode. Mr. Eric Anthony. Eric, how are you man?
Eric Anthony (00:25):
I'm doing well, sir. Thank you very much. Yeah, you pulled that bacon, egg and cheese sandwich out and I'm like really? And then you've also got the liquid death, which I happen to be out of hashtag Again, not sponsored, not
Justin Esgar (00:38):
Sponsor.
Eric Anthony (00:39):
Yeah. And I don't know, maybe we need to work on my title if producer podcast produce. See, I can't even
Justin Esgar (00:48):
Say it. I have producer extraordinaire.
Eric Anthony (00:51):
We might need to change it.
Justin Esgar (00:52):
I'm just going to start going like, what's up everybody? I'm Justin. This is my friend Eric. Hi. Move on with our shit. The reason we're talking about bacon, egg and cheese is we're recording this a little bit earlier than we normally do to make way for our good friend and guest today. I like when we have guests on who comes all the way from England, bring them up. Is Mr. Tim Bowers, c e o of Halo. Tim, how are you man?
Tim Bowers (01:21):
Yeah, I'm good. Thanks man. Thanks very much for having me on. Not so much bacon, egg and cheese over here. We're more of the English fry up.
Justin Esgar (01:29):
Oh, full English breakfast.
Tim Bowers (01:31):
Yeah. Yeah.
Justin Esgar (01:32):
Doesn't that put you in a coma?
Tim Bowers (01:35):
Yeah, you can definitely go too far with that. Yeah.
Justin Esgar (01:39):
Well, so I want to talk today about your product Halo for full transparency, just because I'm like that virtual computers uses Halo. We're an onboarding partner with Halo. We do a lot with Halo, and it was right time that we bring you on. So Tim, why don't you give everybody a two minute spiel. Who are you? What is Halo? And I don't know, I was, oh crap, I lost it. Hold on, because we already talked about breakfast and threw me off. Okay, hold on. I got it. Got it. Alright, let do that one again. Sorry. Alright, so for full transparency, virtual computers uses Halo. We're an onboarding partner with Halo, but we're not going to talk about that today. I want to talk to you, Tim, a little bit about what is Halo. So give everybody a two minute spiel. What is Halo, who are you and what's your favorite holiday?
Tim Bowers (02:29):
Okay, we'll start with the easy bit. So yeah, so I'm Tim Bowers, I'm the C e O over at Halo PSA. And for those of you don't know what A PSA is, I guess that's a professional service automation software, and that can mean a lot of different things to a lot of different people. But for MSPs and IT industry, that means a piece of software to run your business. So you're going to do your sales through it, your pipeline, your service desk, your project management, your contracts, your renewals and all your billing and all that stuff runs through Halo. So we're not getting into the device management or anything like that. It's all kind of to do with service delivery and kind of customer interaction really. So yeah, that's what PSA is. Not everyone uses one today. We think everyone should be using one and Halo is one of the newer ones compared to I guess the incumbents.
(03:21):
You've got ConnectWise and Autotask, which have been around for a while and you could tell they've been around for a while and we're a bit of the newer option, really same functionality in most areas, but we're kind of going places still. So we've got some exciting updates around all the classic buzzwordy stuff like ai, but also some more interesting stuff going on as well. Favorite holiday? Oh man, I don't know. I think my favorite holiday is whenever I get to come to America and go to somewhere that's not Florida and is not Vegas. Every time I go to America, it's a trade show and it's Vegas or Florida, and I'm just a bit sick of them
Justin Esgar (04:10):
For full comparison. KLO is going to be at ace's conference, which is happening May 15th, 16th in Salt Lake City. So at least you get to come to America and not be in one of those two places. Yeah,
Tim Bowers (04:20):
I like coming and seeing the real America, all the different bits and facets that it has to offer, not, I dunno, the prepackaged holiday destinations that
Eric Anthony (04:31):
Florida, maybe we'll see you at an exchange or a next gen because the channel company tends to, I mean, they do have some things in those locations, but they tend to have in other locations as well. So that may be one to look at because I know that a lot of vendors
Justin Esgar (04:48):
Come to New York, we'll get you a big egg and cheese,
Tim Bowers (04:50):
Bacon, cheese. Oh yeah, I'd love that. Yeah, I still haven't got to New York yet because there doesn't seem to be that many conferences there, but it's because it's expensive.
Justin Esgar (04:59):
I dunno if you know this New York is expensive. Yeah,
Tim Bowers (05:03):
Vegas gets pretty expensive as well, but I guess, yeah.
Justin Esgar (05:07):
Well thanks for coming on. So let's get into, you made a comment, and this is kind of where I want to take the episode anyway today is why should an MSP be using A PSA? Now, remember we've been talking about this fact now for a couple of episodes that our friend Dave Sobel said that 85% of MSPs do, what was it like sub $500,000? They're like one or two person shops. Why would a company that's that small really need A PSA? Because obviously I think the bigger ones are all using something already. A lot of the bigger companies are. And also on the same token, I'm starting to see a big shift, at least in the Apple MSP side where they're all deciding to pick up on A PSA now it seems to be the new buzzword. We're always five years behind on the stuff that the PC MSPs are doing, even though we're using more and better technology. But the fact that I'm seeing a lot more Apple consultants moving to A P SS A also. So why should these smaller companies and Apple consultants and such move to A PSA and what's the benefit in a small company using it?
Tim Bowers (06:16):
Yeah, I mean, for small companies, there's a couple of main reasons. One of them is that you use the tool. The main reason to use the tool is to get full transparency and visibility over your business operations. So you can easily tell how profitable X Y, Z customer is on the extreme side. You can then use that data and cut a customer if they're not profitable and they're not ever going to become profitable. And you can put more effort into your guys that are profitable to help them grow and make them an even more profitable customer. And it's very difficult to do that if you don't have all of that information in one system. I would suggest that if you didn't have a PSA, you can get that same data if you are going to put a lot of time and effort into building, I don't know, power BI metrics or even just getting all the data out, putting it in a spreadsheet and then pulling it all apart.
(07:04):
Or you might think that you can just get there with gut instinct and having a feel for it. But I think after a few years, if you still haven't grown and you are trying to, then it probably does come down to, well, my data's not right. I need to get this all in one place so I can actually tell what's going on where I'm making money. That's kind of the main reason really, that people would use A PSA or at least on the kind of small end also, it is just good to get ahead of the game. You're going to need one at some point if you are going to grow. And if you get that system in early, you can start configuring it and becoming comfortable with it and making sure it's all set up properly. So when you do get those first few employees in it's here's the system we're using, off you go, rather than then having to try and get a new system as well as going through the difficulties of employing people.
Justin Esgar (07:57):
That didn't happen with us because when I first started and it was just me, I was using FileMaker, which is fine. And granted, this is 2008 different story, and then I got up my first employee and we just shared the FileMaker database and then over time we moved to a ticketing, just a straight ticketing system. And then we finally moved to Halo. And I remember telling my team saying, you know what? If we were starting my business today, I would have started with A PSA, right? And so for us, it was tough. We had to shoehorn a lot of data in. We also have a pretty large employee base, so it was also getting everybody on board with that. So I like the idea of even if you're a one or two person company getting into A PSA now because you're setting yourself up, you're building that foundation for growth, which is a huge part because I know a lot of MSPs, they don't want to grow, but if you're not growing, you're going to go out of business. So you have to have some growth in order to keep going. And this is a good foundational piece I think to do that with.
Eric Anthony (09:04):
Yeah. Now for me, I think that when it comes to A PSA, because I'm big into automation, and so for me, a P SS A and a one two man shop helps tremendously when it comes to just automating some of the business processes. For me, it was billing. Billing was the huge thing where I was able to get a really good grip around that by using my P ss a and QuickBooks, I could bill in a matter of minutes rather than a matter of hours. And by doing that, it sped up my billing cycles to where I was generating cashflow every week instead of most small MSPs wait till the end of the month to do billing. Not a good idea.
Justin Esgar (09:50):
Yeah. So what's separating Halo from, because you mentioned some of the other players. What do you think is separating Halo from those other players?
Tim Bowers (10:02):
I think a lot of it is direction of travel and the fact that we are still innovating, we're still making changes. We release versions every two weeks. So there's always new things in the beta. If you're going to go and try the beta version out and then every two or three months, that stuff makes it into a stable version. And just the speed we're going means that in a year's time, we're just going to be so much further ahead of everyone else. We've got a load of cool stuff with chat G P T or OpenAI that's pretty much ready now for production in terms of auto categorization, auto resolution of tickets, things like that. And we're looking to expand on that a lot more. And the other thing is we're a company that's focused solely on being a PSA solution. That's all our revenue, that's our complete company strategy is to be service delivery.
(10:54):
That's our focus. We're not going to go out and buy an RMM or all these other tools and try and consolidate them into some package that we sell you. This is it. This is what we want to do. We want to make the best one possible and we want to have majority market share. That's it. We want to be the PSA. So I think that's mostly that's what makes us different is that our whole strategy is that, and we want to be the best tool out there for it, whereas everyone else is trying to do everything creating kinds of different revenue streams, which means they haven't really got people that are focused on just the PSA side. And even if they have, they'll get pulled off and put onto the RMM or the backup or whatever other solution is.
Justin Esgar (11:37):
I mean, I'm also a big believer in having multiple revenue streams. So I can understand both sides of this argument here for what you are doing, not having those multiple revenue streams allows you to keep that very niche core focus, which is hugely important. And I agree with you, Tim, I think that over time, that's what's going to allow you to win the fight against the other PSAs. I know people who are in the RMM game who are doing the same thing where their niche is to focus just on that RMM, and I've watched them grow from two people to a 150 person company. And then I've pitched them being like, Hey, would you ever think about doing ticketing? This was before we were with you. And I said, would you ever think about doing ticketing or PSA? And the guy's like, no, because this is our focus. We don't want to do that. Right? But from the same token, I can see it from the bigger player's moves and I agree with they're stifled in their innovation, but there is that piece of it's okay for you to get everything from one store kind of thing. I don't know.
Eric Anthony (12:48):
Well, to me it's a
Justin Esgar (12:50):
Philosophy.
Eric Anthony (12:51):
Yeah, go ahead. Go ahead, Tim.
Tim Bowers (12:53):
No, yeah, I was just going to say I get that. And I do think the other thing I guess that separates us from the other big players is that we aren't private equity backed or VC or anything like that. We're completely a hundred percent privately owned, and that means that we're very long-term with our decision making. So every decision we make, every strategic decision is not about the next quarter or year even. It's kind of five years, 10 years, where's that going to put us in five years? If it puts us ahead in five years, we'll do it if we're not going to ever do anything to chase quarterly profits. And I think that allows us to be a lot more strategic in our planning and thinking. And also when we develop features, we're always kind of thinking quite far ahead, whereas a lot of the others are having to, because of the nature of running a business in the circumstances, they have to be interested in these quarterly or annual profits, otherwise people start losing their jobs.
Eric Anthony (13:53):
Their strategy is wallet share. That's what they have to do to please the financial backing that they have. And so they're going after more revenue. Whereas somebody like you who's doing more of a best of breed philosophy and focusing on one product to make the best product, it's two schools of thought. Neither one of them are wrong, but they are very different. And I think there's a lot of MSPs out there who have decided to go best of breed rather than put all of their eggs in one basket for a myriad of reasons, for billing reasons, for security reasons, all of those different things.
Justin Esgar (14:38):
Yeah, I completely agree with all that. Alright, so Tim, so let's say somebody wants to sign up for Hilly Low and they get in, what's the first thing that they should be doing once they get themselves an account? Forgetting, I'm not talking about doing trials or doing whatever. I'm saying we've decided we're in it to win it. What are the onboarding steps that someone should be doing to get themselves set up for success within
Tim Bowers (15:04):
Halo? Well, we've got a good resource for that. So the first thing we suggest everyone does is go to the academy page, which is@academy.halopsa.com. That gives them a whole list of initial tasks to get set up within Halo to get them going. That's very much a get your basics down so you can actually start using the system without really getting into configuring it much when you want to then bring in either an onboarding partner, so someone like you guys or someone from our team to actually then go and help you configure it and tweak it a bit because not everyone's doing it the same. It's fine if you are, but it's pretty rare that MSPs are doing things exactly the same, growing their business differently and has slightly different ways of doing it. And that's fine. We definitely see Halo as more of a platform where you can bend it to your will in most cases rather than being something which is quite rigid for that. You either get an onboarding partner, use us, or you can use the documentation on the academy that will get you quite far in terms of configuring exactly how you guys want to.
Justin Esgar (16:15):
Yeah, and so I remember when we were onboarding, we didn't use an onboarding partner and we went through some of the stuff in the academy and our team members that are working on the Halo instance for us, I mean we've made our plethora of mistakes, but it's so easily rectifiable. So we had, and remember, we were trying to mimic what we had before with our old ticketing system. And so we had, when you first get into Halo, one of the things that you have on the sidebar, you have a lot of stuff on your sidebar, you have your tickets and you can add all of these other things. And we had separate sections for our monitoring alerts, our sonology alerts, our phone voicemails, our external tickets from another company that we work with and all these things. And we started to realize that we match it up, but it wasn't working as the way the other ticketing system was in regards to being able to see that visibility.
(17:06):
So we went and we said, okay, well this isn't that hard to fix. We said instead of it showing up in section D, just show up in section A and we can remove section D altogether and then we manipulated on the other side. So I think that's one of the really nice things I like about it, is that I can easily tell my team, Hey, this module is not working for us. Let's reconfigure it so it does this and within five minutes it's done and it doesn't upset the apple cart or break anything else. So I think there's a lot of flexibility within your software, which I think helps and it allows anyone who uses it to make it the unique snowflake that they are because whilst we can genericize a lot of MSP offerings and we can say all MSPs should be doing, having a PSA and having an RMM and having MDM and having security and whatever, let's get real tight on this focus here. Every MSP is going to be different. Some people are going to focus on Mac, some are going to focus on pc, some are going to focus on Microsoft, some are going to focus on Google, some are going to be cyber only. And so Halo allows you to really drill down some of those details I've heard from my team, albeit a little bit crazily, but you can really drill down those details and get the things you need so that way it's visible for you, which is a really, really nice feature.
Tim Bowers (18:39):
Yeah, it's hard. We try and tread the line between having a configurable system as much as possible, but without getting into the realms of ServiceNow where you need a software developer really to actually go and configure any part of the system. They need to actually, a lot of the time they need to write code literally to let you configure new forms or new workflows. So we are kind of trying to go between that. So a lot of configurability to make it fit how you want to work, but also no code. So it is just picking options, adding custom fields, creating workflows with drag and drop interfaces, that kind of thing. Which does mean there is a level of complexity to it. Absolutely. But I think that's a good thing. We do cater to anyone from one, two man companies on the high end, 500 person MSPs using it. And that's because it is configurable. It wouldn't work if it wasn't configurable. You're not going to do things in the same way.
Justin Esgar (19:45):
And it was funny because when we were looking at Halo, because we were looking at Halo when we were looking at a couple of other competitors who we didn't go with obviously, and I put out to the Mac admins community saying, Hey, who's using Halo? And two of my good friends from Canada were both individually DMing and said, Hey, I use Halo. And I was like, can I set up a call with you and our director of customer experience, John? And they said, sure. I got on a call with two guys, separate companies in the same week. And I was like, so how did you onboard? And they were like, we took it really slow and we built out these modules and we did this thing and we did all this testing. And then the other guy's like, yeah, we just changed the support email to point to Halo and just took it from there. It was a very, very different dichotomies on how to get this done. And me and John were like, do we find some way to get in the middle? I don't understand what to do here. But it was just because you can do that. You can just turn on your support email, point it to your Halo instance and be off on the races, or you can customize everything and do it. So it's really not that you have that entire flexibility.
Eric Anthony (20:49):
And to me, that's critical, right? Because you do serve both ends of the spectrum. You can be up and running very quickly and people can configure it as much as they want to, and that's just, you serve more of the market that way. And I think that's a really good way to have that scalability that most SaaS software tries to get, but doesn't always get. Now I have a quick question because with my P Ss a back when I was still in MSP, you guys weren't around back then. So if you were, I probably would've used you is dashboards, because dashboards to me are critical in running the business because they're in front of your face all the time. I literally built a stand and put a monitor on it and had a little PC hooked up to always have my P ss a dashboard up so I knew exactly where I was every single day that I walked into the office. Do you guys have something like that and what kind of data do you serve up on that kind of dashboard?
Tim Bowers (21:52):
Yeah, so we do, we have dashboards. You can create as many dashboards in the app as you want, and they can either use reports from inside the application, so graphs or tables of data, you can display them on monitors around the office if you want, or you can have them as actual operational dashboards that you click into. Some people actually, it's kind of something that came from ServiceNow really, but those guys started pushing people working from dashboards. So managers particularly I think don't really work from lists anymore. They actually have a dashboard and they click into something, whether it's a wheel on a pie chart or a line on a graph, they click into it and then it takes into the data and they can start to kind of digging into it a bit. So yeah, you've got the full array there of dashboards. You can also display data from other sources in Halo as well. So if you do have other dashboarding tools or other metrics you want to bring in, if they've got a U R L, you can kind of push that in there as well. On the more advanced side, I guess some people do end up pulling the data out of Halo into Power BI and other tools like that. So you can also do that if what we've got doesn't meet your needs or if you do want to start data warehousing a bit, which again, probably on the larger end of MSPs, but some people do that.
Eric Anthony (23:15):
Awesome.
Justin Esgar (23:17):
What about integrations? Because obviously a big piece of this is being able to, because you said in the very beginning, right? You can do billing, you can do your C R M, you can do your
Eric Anthony (23:26):
Asset
Justin Esgar (23:26):
Management, you can do all these things. When it comes to integrations, obviously you have a plethora that are already built in. I think one of the biggest ones that we like to take advantage of, and I think every MSP would is the PAX eight integration. So it auto pulls in all of our licensing and things from there, but there are obviously some integrations that do not exist, which we'll talk about that later. But can people build their own and how would that work within the system?
Tim Bowers (23:58):
Yeah, it's really easy to build your own. I mean, you need a developer or someone who can understand how APIs work, but the whole application is, it's a front end built on an A P I really. So not to get too technical, but if you've got a Chrome browser or something open, you hit F 12 and you go to the network tab, you can just see the A p I calls the application's making, and that's how we interact with the data. So you can make exactly the same calls we are, you can do anything you want to any part of the system through the A P I, even if it's changing, I don't know, backend config or creating a new ticket type or I don't know, a new workflow, technically you can just do that yourself through the A P I if you knew how. So you've got all of that. You can create a I applications of different permissions per integration if you want to go and create your own. And then very recently we've got something called custom runbooks, which is really cool. And that lets you, it's kind of code still, but a bit easier. You can start to string together posts and gets and things like that through Halo as part of a workflow. So you can actually go and
(25:09):
Update third party systems or get data from third party systems by clicking a button on a ticket for example. And you can start doing some really crazy stuff with that. But that gets a bit more technical.
Justin Esgar (25:22):
And then one of the other really nice things I like, and we can talk about this, we like to call it Feeding the Beast. So one of the cool things that Halo does is it's normal for a ticketing system that if you have a ticket that comes in, you can look at your knowledge base and look for answers. But one of the cool things that Halo does is it will also look at previous tickets, right?
Tim Bowers (25:45):
So we'll try and match previous tickets currently or previously that's only worked based on things like subject matching categorization and maybe taking some keywords from the body of the ticket. But next week on the trials, people will be able to see our first iteration of our chat G P T style ticket matching. And that's one of the main focuses for the rest of the year is to start adding more features to that. And the way that works is because that's going to be used to match existing tickets and then hopefully, well, it will, I've seen it, it suggests closures and it suggests categories and priorities and potentially even who to escalate it to based on data from tickets that previously matched that look the same as that ticket. And the way it does that is it's passing the data into chat G P T or OpenAI, they've got a special endpoint which lets you vectorize the data and then we store the vectors in the database.
(26:44):
Then you can compare vectors and vectors are much better to compare than text. So without, again getting too technical on it, that stuff's going to be really cool. It's going to be so much more effective at matching ticket data. And we're also working on a repository of data with about 20 or 30,000 tickets from existing customers of ours who have sanitized their data, passed that over to us to be used. And then you'll be able to start to use that for potential resolutions or categorization even if you haven't got any tickets in the system yet because it's going to be able to pull from all these other customers tickets.
Justin Esgar (27:24):
That's awesome. So you have pre-built answers that most MSPs would need just speed their day up because they don't have to worry about typing out this long thing about how to log into the office portal or whatever.
Tim Bowers (27:38):
Yeah, yeah. Hopefully it's kind of that bit of, it's still under development, but that one's kind of out in a few weeks on the trials, so that'd be cool to be able to demo that.
Justin Esgar (27:49):
See, this is what I really like about it is the fact that we're talking about it today and you're talking about what's happening in the next couple of weeks and how far advanced and the fact that this conversation at the end of this conversation, you can go back to your team and say like, Hey, I have this great idea. We'll talking to Eric and Justin because geniuses and let's tweak this thing to do this thing or whatever, and it'll be in play. This is what I like about this is one of the things that of the reasons I like Halo, and one of the reasons why I like RMM MDM Addigy is because you know that old expression, what was that? Nobody ever got fired for hiring IBM, right?
(28:30):
And I mean this with love. You're not the I IBM of PSAs. And that's a good thing, especially for us as Apple consultants because we're supposed to be pirates, which is, I know that's Eric's thing, which is funny how he was a PC MSP and not an Apple MSP after all that whole pirate Steve do. But Halo much like Addigy is very much like the pirate in the PSA field. And I love that. I really do love that about you. And I think that especially the smaller MSPs need to get on board with that because I think everybody always thinks about those big, big players from the Big K company down in Miami and I don't know where the other company is. And think about it, if you want to be a scrappy business and you want to get yourself going and you want to make money work with other scrappy businesses, at the end of the day you're all mentally the same, right? You're all like, I know that you and I have the same haircut, but we really want to get in think the same way about getting stuff done. And that's honestly what I really love about this product.
Tim Bowers (29:41):
Yeah, I mean I think having dealt with Addigy a little bit, I think one of the things that makes us similar is they're still a product focus company where the whole company is still geared towards making and improving a product that will sell. Whereas a lot of these other companies, especially, I don't know like to or whatever, they're not really a product company anymore. They're a marketing and sales machine that sells a lot of products.
(30:10):
Whereas for us, and there's other companies out there in the space that I feel like are like that, so I don't know Ninja or whoever as well, I feel like they're definitely still a product company where it's build it and they will come. It's that kind of approach where you need a good product, you want to get a good product, and then people will want to buy it. Whereas everyone else has kind of got these portfolios and I don't know, 80% of the company really, it's just focused on selling a product to a consumer. So I think it is a different top-down mentality because I'm still heavily involved in product and having spoken to Sal or at Ninja as well, he's still heavily involved in product and I bet you a's leadership team or whatever, I still very interested in the product. Jason
Justin Esgar (30:58):
There, I talked to him on a regular and he's always talking about it the same way you do.
Tim Bowers (31:02):
Yeah, he probably gets excited about it still and he loves it. And I bet you Fred at Kaseya is not excited about product, never spoken to him, never met him, but I'm almost certain that he doesn't get excited about the products they sell, really not about the technical side and how it works and that kind of thing. And I think when you have that, it just changes the whole company really. It changes how everyone else at the company sees it as well. I think at Halo what we've got is a load of people who really care about product. I think that kind of shows,
Justin Esgar (31:39):
And I think that lesson could be expanded out to the MSPs also, because this is, and Eric's going to love me for this one. This is a Gary Vaynerchuk move, which is a lot of us want to be in the clouds, but we got to remember that we got to play in the dirt, we got to get gritty. I have no problem doing that with my own company. I love fixing problems. That's my thing. And if I can spend a day, I mean it's tiresome as it is. I will spend a day doing triage and tier one tickets because I'm good at it. It's what got me into this business in the first place. And I just love doing that stuff because if I get off a call and someone's like, oh my God, you saved my life. I opened up Microsoft Word makes you feel good. It just makes you feel good, right? Yeah. Alright, Eric, anything else? No, I think this has been great. I've kind of
Eric Anthony (32:38):
Been watching Halo for a while because I know that I think early on you guys were integrated with what used to be G F I Max then was LOGICnow and is now nSight and Enable. Yeah, yeah. Yeah. So been kind of exposed to you guys for a while. So it's really great to get to talk to you and have you on the show and have you talk about what Halo has now become.
Tim Bowers (33:07):
Yeah. Awesome. Yeah, it's been really good. It's been great chatting to you guys.
Justin Esgar (33:11):
Yeah, thanks Tim. Alright, well that's it from us at the All Things/MSP podcast. I promise you we'll try better next time. Check us out facebook.com/group/All Things/MSP youtube.com/at All Things/MSP, so you can watch how much Liquid Death I do drink during episodes. Like subscribe, ring the bell, leave a comment, leave a review. We love reading all the reviews. I don't care if you leave a one-star review, just leave a review and we will see all of you next time. Bye.
Eric Anthony (33:48):
From your host, Justin Esgar and myself, thank you for listening to the All Things/MSP podcast. Join the All Things/MSP Facebook group or follow us on LinkedIn, Instagram, and YouTube. The All Things/MSP podcast is a biz POW L L C production. And even though we drink a lot of it, this podcast is still not sponsored by Liquid Death.