Why Design an MSP Role Before You Hire?
You design the role first because the role is what tells you whether a great person is the right hire, and without it the owner ends up reshaping the job around the candidate instead of the business. Josh Peterson's rule of thumb is to put in the 50 to 70 hours it takes to define the role, the comp plan, and the onboarding plan before you post the ad. For related reading, see why job descriptions should guide the people already in the seat and how a dispatcher supports your support team.
In this episode, Josh Peterson, CEO of Bering McKinley, and Gary Boyle, COO and Management Consultant, talk through service manager promotions, sales hires, team clarity, and a quick self-test for roles that were never designed.
Why Design an MSP Role Before You Hire?
Because the role is the yardstick for every candidate, including the ones who show up unexpectedly. Josh described a pattern he saw three times in two weeks: an owner agrees on the role to hire for, then a few weeks later reports finding an amazing person. When Josh asks whether that person meets the minimum criteria for the role, the answer is no. The candidate may be excellent, but that isn't the role being hired. Josh's fix is to put the planning first. Decide where the business is going this year, work out which roles that plan needs, design each one thoroughly, and only then go find the person. When a strong candidate appears, your head should snap to the plan, not the candidate. If the plan didn't call for this person, Josh suggests putting the decision on ice for at least a week to work out whether adding them really improves the plan and which role they would fill.
- Define the role first, then measure every candidate against it.
- Check a surprise candidate against this year's plan before acting.
- Wait at least a week before hiring someone the plan didn't call for.
Should You Promote Your Best Tech to Service Manager?
Usually not, unless the tech still wants the job once it is clearly defined. Josh has told owners for years not to make their best tech the service manager, yet he said BMK still sees it about 15 times a year. Gary pointed to familiarity: the tech knows the systems, knows the owner, and feels like an easy fit for the next level. Without a defined role, the promoted tech becomes a lead tech and the highest escalation point. Later the owner learns what service department gross profit is and starts pressing a manager who has never managed to it. Josh defines the role by one number. BMK's standard for service department gross profit is 55% of service revenue, and the question for the role, in Josh's words, is "Can you convert labor costs into profit?" Once the job is stated that plainly, most techs know it isn't for them, and you can open it to candidates who are strong users of technology rather than top technicians.
- Define the service manager role by its financial outcome before you offer it.
- Let internal candidates apply for the defined role, not inherit it.
- Expect many strong techs to decline once the job is clear.
Why Does a New Manager Struggle to Earn the Team's Respect?
Usually because the team was never told where the company is going, so the new role looks like one more change. Gary raised the respect problem: a technical service manager tends to get pulled back into doing the work, while one without technical depth can struggle to set expectations the team accepts. Josh called the fix a cultural shift. The whole company has to know where it is going and stop defining itself only as a technology company. He credits his mentor with the idea that you have to have a vision, evangelize it, and fund it, and that evangelizing is a finite exercise: state the direction, explain why, and ask who is on board, three times. "Not four, not two, not seven," Josh said. Until that happens, whoever fills the new role carries the team's frustration. Gary added that owners often feel such relief at handing off work that they stop guiding the new hire, which is abdicating rather than delegating.
- State where the company is going before you add a management role.
- Ask the team to respect the role and the goal, not just the person.
- Keep guiding a new manager after the relief of handing off work.
Why Do MSP Sales Hires Fail So Often?
Because owners often hire a salesperson before laying the foundation for one. Josh said BMK regularly hears an MSP owner mention that a salesperson starts tomorrow. His follow-up questions cover the job description, the role table, the comp plan, the onboarding plan, and how the owner will manage the rep and set expectations. Often the hire happened because a friend recommended it or an event was motivating, not because the role was built. Josh described the predictable result: the rep arrives, the business isn't ready, the rep gets frustrated, the owner decides salespeople don't work, and about two years pass before the owner tries again. His advice is to slow down, know why you are making the hire, and put in the 50 to 70 hours it takes to prepare. He compared it to a fighter, whose fight is won outside the ring. By the time you post the ad, the hard work should be done.
- Write the job description, role table, comp plan, and onboarding plan first.
- Be clear about the return you expect from the new role.
- Budget real preparation time, not just interview time.
How Can You Tell a Role Was Never Designed?
Look for seats that carry work belonging to another role. Josh and Gary closed with a short self-test. If your sales manager also carries a sales quota, Josh said, you are falling into the trap. The same is true if your dispatcher handles first-level calls, or if your service manager carries more than an hour a week of billable work. Gary added a fourth sign: a business partner who takes more than a 10% to 15% split but never shows up to work. Josh stressed that none of these means the business is about to fall apart. They are prompts to ask how each person got into the role, whether they are doing well, and, if not, whether a role that was never designed is the reason. From there the work is to unwind the problem and avoid repeating it. Gary's advice for the next pop-up opportunity was simple: stay away from that chaos until you are ready.
- Audit each leadership seat for work that belongs to another role.
- Ask how each person got into the seat they hold today.
- Unwind the mismatches you find and plan to avoid new ones.
Frequently Asked Questions
Why should an MSP design a role before hiring?
A designed role gives you a yardstick for every candidate. Without one, owners tend to hire a great person and figure out the job later, which puts the right person in the wrong seat. Josh Peterson recommends deciding where the business is going, defining the roles that plan needs, and only then recruiting.
Should I promote my best technician to service manager?
Not by default. Josh Peterson warns that a promoted tech often becomes a lead tech and escalation point instead of a manager of profitability. Define the role by its financial outcome first, then let internal candidates apply. Many strong techs decide the job isn't for them once it is described clearly.
What is a service manager responsible for at an MSP?
In Josh Peterson's view, the job comes down to one question: can you convert labor costs into profit? BMK's standard for service department gross profit is 55% of service revenue. Keeping clients happy and the team engaged matters, but the service manager owns that profit number above everything else.
How long should you prepare before hiring an MSP salesperson?
Josh Peterson puts it at 50 to 70 hours. That time goes into the job description, role table, comp plan, onboarding plan, and how you will manage the rep. Skipping it often leads to a frustrated rep, an owner who decides salespeople don't work, and a long wait before trying again.
How do you plan MSP hires before growth forces them?
Gary Boyle suggests forecasting growth, checking your service department's capacity, and spending a weekend mapping the roles that growth would require, including a 90-day onboarding plan for each. Josh Peterson adds that a rough plan you talk through with an AI tool beats no plan, and a full goal and milestone plan is better still.
What are the signs of a poorly designed role at an MSP?
Josh Peterson and Gary Boyle named four: a sales manager who also carries a sales quota, a dispatcher handling first-level calls, a service manager with more than an hour a week of billable work, and a partner taking more than a 10% to 15% split who never shows up to work.
Episode Highlights
- Finding a great person before the role is defined.
- Why the best tech rarely makes the best service manager.
- The one number a service manager owes the business.
- Earning the team's respect for a new manager through company-wide clarity.
- Evangelizing your vision three times, then moving on.
- Delegating versus abdicating when you hand off work.
- Preparing 50 to 70 hours before a sales hire.
- Planning roles ahead of growth instead of reacting to it.
- A self-test for roles that were never designed.
About the Co-Host: Gary Boyle
Gary Boyle is COO and Management Consultant at Bering McKinley. He ran his own MSP before joining BMK and works with MSP leadership teams on operations, planning, and execution.
About the Host: Josh Peterson
Josh Peterson is the CEO of Bering McKinley and host of The BMK Vision Podcast. Since 2004, Josh has worked with hundreds of MSP owners to build operationally sound, profitable businesses through consulting, peer teams, and direct coaching.
Connect with Josh Peterson on LinkedIn →
Related Resources from Bering McKinley
- To hire or not hire a sales manager: how MSPs decide
- From planning to execution: turning business goals into performance targets
- Organizational strategic planning for business performance
Want to Continue the Conversation?
If your hiring starts with the candidate instead of the role, the fix starts with a plan. Vision gives your MSP a strategic plan, a consultant who holds your team accountable every month, and your numbers tracked against BMK's standards.
%20logo.png?width=1083&height=200&name=BMK%20(just%20text)%20logo.png)