Aharon Chernin, founder and CEO of Rewst Aharon Chernin has been building technology specifically for MSPs for more than twenty-five years – including founding Perch Security, which ConnectWise acquired in 2020. His next venture was Rewst, a workflow automation platform purpose-built for managed service providers, now serving over 1,500 MSPs. The founding insight: automation was the foundational promise of managed services, and the tools had never lived up to it. In this conversation, Chernin draws the distinction that frames everything else: there’s a difference between an MSP that does automation and an automated MSP. One is a project. The other is a culture. Success, he argues, is one hundred percent cultural – the person who writes the cheque and the engineer who builds the workflows both have to want it, or it stalls every time. We dig into where AI fits in the MSP operational stack, and why treating AI and automation as interchangeable leads to bad decisions. The Chernin framing: AI thinks, automation acts. Without a connected execution layer like Rewst’s RoboRewsty AI Workflow Builder, AI can only advise. We also get into the governance model – approval gates, trust levels, and the balance between cyber risk and business risk – and the MCP Server architecture enabling genuinely agent-driven MSP operations. Chernin shares numbers from three Canadian MSPs on the platform – Resolved IT, Ideological Systems, and Yardstick – and walks through how to calculate the real economics of automation investment beyond simple time savings. He closes with a practical roadmap for any MSP owner who wants to get serious in the next six months: get out of firefighting mode, find your automation champion, start small, and do not wait for perfection. Read Full Transcript Robert Dutt: Hello and welcome to In The Channel from ChannelBuzz.ca, bringing news and information to the Canadian IT channel community for the last sixteen years. I’m Robert Dutt, editor of ChannelBuzz.ca, and your host for the show. If you’ve been following the conversation around AI and MSPs over the last year or two, you’ve probably noticed that a lot of it is pretty fuzzy. AI is going to transform your business. AI is the future of service delivery. AI this, AI that – but not a lot of specificity about what it actually means for the way an MSP runs its operations day to day. My guest today has been building technology specifically for MSPs for more than twenty-five years. He founded Perch Security, which was acquired by ConnectWise back in 2020, and then turned around and founded Rewst, a workflow automation platform built from the ground up for managed service providers. Rewst now has over 1,500 MSPs on the platform, which means he has a pretty clear view of where the channel actually stands on automation – not where vendors wish it stood, but where it actually is. We talk about the difference between an MSP that does automation and an automated MSP, and why that distinction matters more than any specific tool. We get into why AI and automation are not the same thing, and why confusing them leads MSPs to make bad decisions. And we look at what the operational stack of an MSP actually starts to look like as AI moves from advising on workflows to generating and executing them. Aharon Chernin is the founder and CEO of Rewst, and he’s been thinking about this a lot longer than most. Let’s get right into it. My chat with Aharon Chernin. Aharon, thanks for taking the time. I appreciate it. Aharon Chernin: Nice being here. Robert Dutt: Rewst isn’t your first time building specifically for the MSP market. You come out of Perch Security, acquired by ConnectWise. What did your time inside ConnectWise’s world teach you, and was Rewst a direct response to something specific you saw from there, or from the community there? Aharon Chernin: I was actually only at ConnectWise a couple of months. Really, the Rewst idea came from working with MSPs for years while I was doing Perch. I was learning more and more about how MSPs operated. I saw the tools they were using, the problems they were having. And, mind you, this is the era circa 2017-18, and they’re using tools called PSAs – professional services automation – that didn’t really automate anything. It had me scratching my head: what’s going on here? But then I just continued moving forward because I had security stuff going on. And then there were RMM tools called Automate, and I was trying to figure out what these things actually automated. It was just endpoint stuff, right? But there’s so much more than just an endpoint. And then I saw a bunch of single-point solutions – software products out there doing a single automation, not even calling it an automation, just calling it a software product. So once I had the opportunity after Perch, I went and started investigating what were these quirks in the market I was seeing, because automation is much, much bigger than what the market actually thought it was. Robert Dutt: Well, and it’s for so long been one of the key premises of managed services – the idea of automate everything you can towards success. So it’s interesting to hear those observations. You’ve got the platform now with 1,500 or more MSPs on it – you probably have a better view of the real state of automation adoption in the channel than almost anyone out there. How would you honestly characterize it today? Is this a story of meaningful progress from the scenario you saw back in your Perch days, or is it still pretty early for many MSPs? Aharon Chernin: It’s still the beginning. We only have 1,500 MSPs. And how many MSPs are there – depending on who you talk to, 60, 80,000. We only have 1,500 of them. So in my mind, these are all early adopters in automation. But when it comes to what adoption actually looks like in an MSP that successfully automates, it’s cultural – 100%. If you look at cybersecurity – Perch was a cybersecurity company – you’d be looking for the correct size MSP that focused on security to resell through. But when it comes to automation, every size MSP needs to automate – small and big. And we’re actually seeing that. We see really, really small MSPs automate and really, really big MSPs automate. And we’ve also seen both those sizes fail. The number one reason they succeed is culture. The buyer – the buyer could be the CEO of the MSP, or a director of managed services, whoever can write a cheque – that person has to want to automate. And the engineer who’s actually going to do the automation, they have to want to do it too. If the buyer wants to automate but the engineer doesn’t, it’s not going to work. If the engineer wants to automate but the buyer doesn’t, it’s not going to work. And that cultural thing extends further than just the want. The CEO of the MSP should be running around saying, “I want to be an automated MSP,” and excited about it. If they’re not excited about it, they’re going to be a part-time automation MSP. The way I like to say it is: you’re either an automated MSP, or you’re an MSP that does automation. Robert Dutt: What do you find helps flip the switch from one to the other? What is it that gets those teams that are either misaligned or not aligned at all to get things lined up and moving in the right direction? Aharon Chernin: It’s really an open line of communication between the buyer and the person implementing. Because if the buyer has an automation idea – just one, a single simple basic thing that would save the company time or help improve service delivery reliability – and that engineer performs that small automation, and they talk to each other, and the engineer says, “Yes, it’s running. Yes, it runs fifty times a day. We’ve saved eight hours today running this automation” – and that actually gets back to the person who writes the cheque – there is alignment. The tide has turned. Suddenly the MSP says, “How do I dedicate more people to helping automate this business?” It’s a matter of getting that first win and getting it in place. Robert Dutt: There’s a lot of talk, obviously, about AI. And Canadian MSPs are being sold a lot of things that blur the line between AI and automation. You’ve talked about that distinction – the idea that AI thinks and automation acts. Can you expand on that? Because I think getting that framing right can help change how MSPs make decisions and think about how they’re structuring things internally. Aharon Chernin: AI can’t touch anything by itself. This goes back to: AI thinks, automation does. Take ChatGPT, for example. ChatGPT is not an AI. ChatGPT is a tool on top of AI. The AI is GPT. The tool is Chat. So just having AI gives you a lot of answers to a lot of questions, but nothing gets done. You need the tool on top of the AI. I can’t think of an easier way to define it than that. There are an infinite number of possibilities of what you can do with a tool that leverages AI. Robert Dutt: So you guys have RoboRewsty now. You’re moving from AI that guides building workflows to AI that generates those workflows. That sounds incremental, but to your point on thinking versus doing, I suspect it’s more significant than that. What actually changes for an MSP team when anyone in the org can describe a workflow in language that’s natural to them and have it built for them, rather than having to go back to that one person who knows how to build out the automation? Aharon Chernin: AI is easier to understand than even that. We need to think of it as just another employee. Now, depending on how much the business trusts that employee is how much governance we’re going to put around that employee. If there is one hundred percent trust, it gets free will and can run freely. If there is zero to ten percent trust, every step of the way needs to be gated by a person.