You Hired the Wrong Person, Again.
How the CEO of a 90-person MSP decides when to hire, and who to grow into the next role.
WATCH ON DEMAND NOW 👉
Which Features Are Available Early?
Available immediately, early access customers can enjoy essential service management features such as:
Customer Management
Service Requests & Ticketing
Scheduling & Time Tracking
Workflows
Mobile Accessibility
Over the coming months you’ll also gain instant access to exciting new features as they are introduced to the platform, such as:
Product Catalogs & Asset Management
Invoice & Billing (New & Recurring)
SLAs
Integrations Library
(including Pax8 Marketplace)
What We Cover in This Video Podcast
Every MSP owner has made a bad hire. Most have made the same one three times.
Sometimes the wrong person was the right hire once. The MSP grew, and they didn't grow with it. Other times the owner waited too long to hire, and the best techs burned out covering the gap.
In Episode 5, Brook Lee sits down in person at the Rev.io office in Atlanta with Jennifer Roy, CEO of Nucleus Networks, an MSP of nearly 90 people in Vancouver. Jennifer has spent 15 years in the channel in operations roles, from support manager to CEO.
What You'll Walk Away With
✅ Grow them or let them go: How to spot a good employee who isn't growing with your MSP, and how to help them find the right next role.
✅ Hire before the burnout: When to make an investment hire, before your team is stretched past 85% utilization.
✅ Hire for culture first: Why Jennifer promotes from within, and why Brook won't hire a tier three without MSP experience.
The Speakers
Session Transcript
Prefer to read it?
The full conversation, lightly edited and organized by topic.
Read the episode transcript24 minutes · Brook Lee & Jennifer Roy
The engineer who broke the network and told no one
Brook Lee: Hey, everybody. It's Brook with MSP Unfiltered. I'm live this week at the Rev.io office, which I've nicknamed the Rev.io Studio. We're in our office in Atlanta, and there are actual people working here, so you're going to hear some noise in the background. My really good friend Jennifer Roy is here. She's been gracious enough to sit down and do a podcast in person. We're both in Atlanta this week for an award, so I asked if she could stop in, and she said, "Yep, no problem." Jennifer, for people who don't know you, give them a quick rundown on who you are and why they should care what you say.
Jennifer Roy: I'm Jennifer Roy, the CEO of Nucleus Networks out of Vancouver, Canada. I've been in the channel for the last 15 years in a variety of operations roles, everywhere from support manager to CEO.
Brook Lee: I'm going to start this podcast with a story. I was working at an MSP in Savannah. I started there as a tier one tech and worked my way up, and I'd been there maybe three or four years. I was on the 7 AM shift as a tier two tech at that point. I came in at 7 o'clock, sat down to log in, check the board and see what came in the night before. Nothing worked. I couldn't log in. The PSA we used was down, and we were a ShoreTel office, so the phones were down. Everything was down. So I went into the network closet and started rebooting the firewall, the switches, everything. Nothing came back up.
Brook Lee: The MSP was owned by two brothers, and both of them were very technical. When I say technical, I mean they could architect solutions. One of them came in, and I told him, "This is everything I've done, but we are dead in the water." He went in, looked around, and couldn't figure out what was going on either. It was all hands on deck. Then I realized the gentleman who was our tier three engineer wasn't in the office yet. At this point it's 8:30, quarter to 9, and I'm wondering if this person did something last night. I couldn't look in the PSA. There were no notes. Nobody got a phone call. So I called his wife and said, "I need you to go wake him up."
Brook Lee: Sure enough, he'd made an upgrade on the network the night before. He was working until 2 or 3 in the morning trying to make things better for us, so it wasn't ill-intentioned. But he didn't document what he did, he didn't tell anyone, and what he did broke the network. Nobody knew what it was, because there was nothing there. We got him up, he told one of the owners what he'd done, and we were able to reverse it and get everything back up and running. But we were down for a solid two hours because one person did something and didn't tell anybody.
Brook Lee: I tell this story a lot on the road, and when I look MSP owners and CEOs in the eye, everybody shakes their head, because everybody has had one of those engineers. I tell people that at MSPs, in general, we don't have bad apples. We have good people with good intentions who sometimes make bad decisions. Part of what we're going to talk about today is how MSPs hire the wrong person again and again, and for some reason, don't learn from those mistakes.
When an employee isn't growing with your MSP
Brook Lee: Jennifer's MSP is based out of Vancouver, and it's fairly large. How many people are you now?
Jennifer Roy: Just shy of 90.
Brook Lee: So 90 people, which is a decent-sized MSP, and you've had these same people at your MSP. There are two prongs I want to talk about today. The first is the people who are already there, and figuring out what you're going to do with them. How many people did you have when you started there?
Jennifer Roy: We had about 80. So we haven't grown a ton in headcount. We've grown a ton in revenue, and we've become more efficient.
Brook Lee: When your MSP is growing, whether it's in revenue, in people or in processes, I tell owners that sometimes not every employee grows with it. That doesn't mean they're a bad employee. It doesn't mean they're not smart or not good at their job. It means your MSP is maturing in a variety of ways, and that person isn't going with it. So first, how do you recognize it? And then what are your steps to either get that person back on track, or, if you can't, have an exit plan?
Jennifer Roy: Your story resonates. In all three MSPs I've been in, I've seen it happen. First off, you have to have really clear accountabilities for your team. What's the objective? What do their goals and scorecard look like? That's how you say, "This is what success looks like." I think that's where a lot of leaders fail. They don't give that clear direction, so they can't hold people accountable. And it's way more than KPIs. It's culture fit. It's looking at their career path and how it fits with your strategy and your organization. If you've got somebody who says, "I really want to dig deep into this technology," and it's not a technology you offer, and you know it's not going to be on your roadmap, you need to have that conversation early in their career if you want longevity with your employees. So that's one of the things I really look at: investing in your team, both in their growth and in the growth of your business, and how those strategies align.
Brook Lee: I think that's a conversation MSP owners struggle to have. What this person wants to do versus what your business goals are, and sometimes those don't align. Again, it doesn't mean that's a bad employee, or that they're not smart or not good at their job. It just means they want to do X and we're going to do Y. You don't want to lose a good employee right off the bat, where they hear "she doesn't want to do this" and quit tomorrow. I think that conversation is one of the more difficult ones to have as an MSP owner.
From tier one tech to HR manager
Jennifer Roy: I've done a few different things. My current HR manager started as a tier one tech.
Brook Lee: Tier one tech to HR. That might be another podcast.
Jennifer Roy: He's worked with us for over a decade. He went down the technical path and became a pod manager at one point, then decided he didn't really want to do that. He asked me what other opportunities there were, and I said, "Well, we have an opening for a junior vCIO." He said, "Great," and put his name in. He ran with that for about a year, then met me for lunch one day and said, "This isn't my jam. I'm just not feeling it." So I committed to continuing to look for opportunities for him. We had a really clear discussion: "I don't have anything right now. Are you really unhappy? Do you want to leave?" And he said, "No, I want to stay. I love the culture. I love the place. I just don't love the role." So we agreed we'd keep talking.
Jennifer Roy: At our next company town hall, I announced I was hiring an HR coordinator. He called me afterward and said, "I didn't want to tell you at lunch, but I've been going to night school for HR, because I think this is my calling." And a big piece of what we do in HR is recruiting. He knows the role inside and out. He knows the company, the brand and our clients. So I said, "Let's give it a whirl and see what happens." I moved him into the HR coordinator role a couple of years ago. He's continued his education, and he's now our HR manager. He's hands down the best HR manager I've ever worked with in a technology company.
Brook Lee: That is quite a story. I like that you had the conversation with him about, "We don't have anything right now, so you're going to have to keep riding it out as a vCIO until you figure out what you want to do next." And I like that you talked about what the role was. When I was at the MSP in Savannah, I started basically as a glorified dispatcher and worked my way up. The two owners were very transparent about the company and where we were going to grow. We were running EOS, and they gave us what I'd call a modified org chart, with color-coded boxes showing who was in each role now and what they'd be looking for. I'd moved up into a made-up role, a business support liaison or something, and I really liked the client side because I'd grown tired of the tech part. But I saw that vCIO box, and I went to my manager and asked, "What do I need to do to get that job? They said they'll be looking for it in the next one to two years. What skills don't I have that I need to fit into that box?" He gave me a laundry list, but at least I had direction.
Brook Lee: I also like that you let him try. He didn't know if he was going to be a good vCIO, and you didn't know either. But he was a good employee, and you really liked him for the company.
Jennifer Roy: Totally. He was a fantastic culture fit, with incredible loyalty. Hardworking, well-liked, well-respected. So when he came and said, "I need another opportunity," I would rather find him an opportunity than lose a good employee. So I pivoted and said, "This is what we have vacant right now," and he said, "Let's try." I knew he had the skill sets. He didn't have the experience, but everyone needs to start somewhere. So we made it a junior vCIO role, with a senior team to help support him and help him grow. And even as HR coordinator, with no experience, I told him he'd report directly to me, which normally I wouldn't do with a coordinator. But I have an HR background, so I could support him and help him grow in the role. I think you have to make those investments in people if you want them to invest in your business.
Brook Lee: I really love that, because it's something MSP owners are sometimes scared to do: "I don't know where I'm going to take this person, but let's give them a go." And yes, the vCIO has to be technical, but to me, 90% of it is relationship, which is clearly what he excelled at. As a vCIO, you're going on site and building trust. The end game is to be in a room with a client's leadership team while they tell you what budget they have for 2027, and then work with them on the slice of that pie that goes to IT. They won't tell you that if they don't trust you, and no amount of charts and PDFs will get you there. It's the relationship, and people overlook that. I did another podcast where we talked about seeing potential. You have to see past what's in front of you now. I see this person today, but I also see what they could be in six months or a year.
Helping a great employee leave for the right job
Jennifer Roy: You have to look at that across your whole employee base, because there will be people who come in, do great work, and then need your support moving into their next role, whether that's with you or not. We had one employee who was fantastic and worked incredibly hard, but he really wanted to work in Linux, and we're not a Linux shop. So the best thing I could do as a leader was support him: be a reference, and give him time off to go interview for Linux opportunities. That was hard, because I was losing a good employee. But if he ever decides he wants to come back to an MSP, who do you think his first call is going to be?
Brook Lee: And this is why this lady is up for CEO of the Year while we're here in town. That's next-level thinking, and not a lot of people have that level of understanding. I also tell people this space is really small. The MSP channel isn't nearly as big as everybody thinks it is. So for you to do that for an employee is pretty epic.
Jennifer Roy: I think you invest in your people, and in return, they invest in your business.
Brook Lee: We've been talking a lot about employees, and how to figure out whether a person needs to go. It's about having the conversations. "If this isn't the right role for you, we've grown, and if you can't grow with us..." Again, it doesn't mean they're not smart. At my MSP, one gentleman ended up separating from the company, but we found him a job at a significantly smaller MSP. We'd grown to about 50 people, and he's great at a 10- or 15-person shop because he loves being the person who knows everything, the "buck stops here" guy. He was great for that MSP, and they weren't going to get much bigger than that. That was their model. He did great there, and we helped him get that job by providing references and all of that.
How to know when to hire before your team burns out
Brook Lee: The second prong. Let's say my MSP is humming along really well. I've got 10 or 15 people and I don't have a bad turnover rate. One thing I see MSPs struggle with over and over again is how to know when to hire the next person. I don't mean waiting until your people complain that they're working too hard, or worse, until they leave because they're working 60, 70, 80 hours a week with no relief in sight. That's the one that bites people all the time: "I'm working 60, 70 hours a week. Nobody's telling us anything. I'm sitting on the service desk, we're all grinding every day. Are we hiring somebody? Is anyone coming to help?" So if you're not as big as you are, with metrics and tools, what can an MSP owner or operator look for that says, "This is when I need to start looking for somebody," so they're ahead of it and not waiting until the team is in grind mode?
Jennifer Roy: That's such an important point, because so many times in my career I've seen teams burn out, or clients start to churn because of response or resolution times. And you're right, a lot of those are lag indicators. By that time it's too late. The ship has sailed. There are the traditional KPIs: response time, resolution time, revenue per head count. You can look at all of those, but a lot of it you have to go on gut feel, and especially when you're a small business, you sometimes have to take some risks. I talk a lot about risks.
Brook Lee: Hiring before you need that person.
Jennifer Roy: Yes. If you've got a healthy pipeline and a decent probability of that closing, you don't want to hire someone after you've onboarded a new client and onboarding is a mess. You want to hire before, so they have time to actually onboard into your business and understand your PSA and your tool set, especially if they don't have an MSP background. I call them investment hires. You hire before you hit 85 or 90% utilization. You hire when you're at 78% utilization, knowing that you're investing in your business to grow.
Should you hire a tier three without MSP experience?
Brook Lee: That's a really good point. You mentioned onboarding, and I talk to people about that a lot because I think it's make or break. If you have a really great onboarding experience for your clients, they'll stay with you for a really long time. If you have a bad one, you're asking for trouble right off the bat.
Brook Lee: You were talking about investing in people and hiring. I've gotten into plenty of arguments, dust-ups at the lobby bar, about this one. At an MSP, I will not hire a tier three if they don't have previous MSP experience. They're not used to doing work the way we do. They don't like documenting, they don't like doing time entries, they don't like putting stuff in the PSA, and I have never had that work well. Anybody below that level, I can train, because I see the potential. But in some markets I'm paying a tier three 150 or 200, and I'm not going to fight with you for your time entries. I'm not going to fight with you to document. If your time entry for two and a half hours says "fixed server," that's not going to work for me, and it's not going to work for my clients. Do you have any rules in your hiring? People you will or won't hire from certain industries, or without certain experience? Anything that's a deal breaker for you?
Jennifer Roy: I wouldn't say I have any hard and fast rule. However, going back to investing in your people, I will invest in my tier ones and tier twos to get them to the tier three level any day of the week instead of hiring externally. It's better for culture and it's better for your clients. Any time I can, I'm going to promote from within. When I hire externally, I prefer MSP experience whenever possible, but I've had some great hires who came from enterprise and were looking for something more fast-paced.
Brook Lee: I came from government, and I hated it. Then I was in enterprise for a long time, and it was set it and forget it. I built the network, so I'm sitting around thinking, "Nothing's breaking today. Are we going to lunch at 10:30?" There was nothing to do. When I moved to the MSP space, I very quickly realized I wasn't nearly as smart as I thought I was. It was 100 networks instead of just the one, and I didn't know what was happening.
Jennifer Roy: That's exactly it. You have to look for somebody who really has grit. I talk a lot about grit. The MSP space is not for everybody. It's very fast-paced. I love it, and I can't imagine being in any other industry at this point. But it's not for everybody.
Brook Lee: And I tell people, it doesn't mean that person isn't a good tech, or isn't smart, or isn't great at what they do. Not everybody is cut out to work in an MSP, just like not everybody is cut out to work in enterprise or mid-market. There's space for everybody, but you need to have some honest conversations, especially if you're going to give it a go and bring in somebody from outside this space.
Hire slow, fire fast, and hire for culture first
Brook Lee: I'm also a big "hire slow, fire fast" girl.
Jennifer Roy: Same.
Brook Lee: At an MSP, it probably takes 90 days, easy, before a new person starts earning their keep, and that's a long time to see no return on a tech or engineer. That's why I want to hire really slow and make sure the person is the right fit. I think MSPs overlook how important culture is. I can train anything, but if a person doesn't care, if they don't want to be part of a team, I can't fix that. No amount of training will fix culture fit.
Jennifer Roy: I agree so much with that. I hire for culture first, and I fire for culture first. Performance, you can train. You can help educate people, have them job shadow. There's a ton you can do to get them experience. But if they're damaging to your culture, it's going to hurt your brand, your employees and your clients. It's not worth it. I will 100% hire for culture and invest in training.
The hand-up mentality
Brook Lee: I call it the hand-up mentality. When I first went to work at that MSP and realized how little I actually knew, there was a guy who had been the glue of the company on the tech side. This was many years ago, and he kept everything in notebooks. But I realized fast that he was the one who knew everything, so I attached myself to him like Velcro. When he said, "We're going to rebuild this network at 2 in the morning," my hand was up: "I'm your girl. I'll go with you." That's how I learned cable management and all kinds of things we'd never done before, and he was incredibly gracious to let me do it. To me, that hand-up mentality shows me so much more about a person than whether they know how to prep a WatchGuard firewall or an access point.
Jennifer Roy: Agreed, and it's very similar for me. I'm not technical. At my first MSP, they took a chance on hiring a non-technical support manager. They hired me because I was focused on employee experience and client experience, and I was process-driven. Within five minutes, I knew I was never going to be the smartest person in the room. But I knew I could outwork everybody. So I put my hand up for everything. Any project they needed, I'd do it. An upset client someone needs to call? I'll handle it. That became the brand I developed: being a very hard worker. It's served me super well, even today. If you talk to my team, or anyone I've worked with or for, they'll say, "Jen's incredibly hardworking." That's a personal brand I still love. I'll never be the smartest, but I can work really hard.
Never be the smartest person in the room
Brook Lee: I tell people that if I'm the smartest person in the room, I don't have the right people in the room. I should never be the smartest person there. I should always be hiring people who are smarter than me, who know more than me and have different ideas from me. If it's just me and a bunch of yes men, the wrong people are in the room, and we're never going to get better.
Jennifer Roy: Agreed. That's why my CTO is so wonderful.
Brook Lee: Carl?
Jennifer Roy: Yes. Carl is wonderful because he'll be the first to say, "Your vision is terrible. We need to do this better. Here's what we're going to do." He doesn't sugarcoat. You get what you get: "Hey, this didn't work. You need to figure out how to make it better."
Brook Lee: That's why I like Carl too. Thank you so much for joining me today. I appreciate it.
Jennifer Roy: Thanks for having me.
Brook Lee: Thank you, everybody, for tuning in. This was MSP Unfiltered, from the studio at the Rev.io office. We'll do a few more of these if I can round up more people. If you're in Atlanta and want to come hang out at the office, give us a call, because that's exactly how this one happened: Jennifer was in town and we invited her over. Otherwise, we'll see you on the next episode. Have a great day.