How to Grow from a One Man Operation to Two
-
A small "MSP" has the chances a rock band has of both sustainability let alone large scale success.
Its got me thinking, and maybe a good topic for another thread, what is the "hot business" now that is accessible for a small startup. Something where customers are actually seeking out solutions the way small offices needed a server, email and netowrk help in the late 90's and early 2000's?
-
@bigbear said in How to Grow from a One Man Operation to Two:
A small "MSP" has the chances a rock band has of both sustainability let alone large scale success.
Its got me thinking, and maybe a good topic for another thread, what is the "hot business" now that is accessible for a small startup. Something where customers are actually seeking out solutions the way small offices needed a server, email and netowrk help in the late 90's and early 2000's?
If we only knew.
-
@bigbear said in How to Grow from a One Man Operation to Two:
Something where customers are actually seeking out solutions the way small offices needed a server, email and netowrk help in the late 90's and early 2000's?
Small businesses still need help with networking, wireless setups, and email. (mostly in the form of o365 migrations.)
-
Yeah but I was around at the beginning of this, when we were teaching people what email was and replacing banyan vines with PC's and token ring or ethernet.
The money onboarding a new customer just isn't there. In fact, the cost to acquire an IT customer on a consistent basis is enormous compared to the good ol days.
It is difficult for veterans of the industry to accept, but with the passing of one thing there must be something on the horizon that is accessible to a small business owner.
-
@mike-davis said in How to Grow from a One Man Operation to Two:
@bigbear said in How to Grow from a One Man Operation to Two:
Something where customers are actually seeking out solutions the way small offices needed a server, email and netowrk help in the late 90's and early 2000's?
Small businesses still need help with networking, wireless setups, and email. (mostly in the form of o365 migrations.)
And to your point, I know there is revenue and opportunity but it is a trickle compared to the early days of internet and private networks, SMB particularly.
-
Curious on everyone's thoughts on how skilled this first employee should be, and how much they should get paid. Are you cheap like the typical SMB and get someone for $40k? or do you pay for actual talent at $70-100K?
-
@irj said in How to Grow from a One Man Operation to Two:
Curious on everyone's thoughts on how skilled this first employee should be, and how much they should get paid. Are you cheap like the typical SMB and get someone for $40k? or do you pay for actual talent at $70-100K?
I would say that if you don't want a rotten apple, you don't go to the barrel, you go to the tree. I've hired high school and college students. I'll pay them minimum wage and give them raises as they earn it.
As part of the hiring process, I explain that I can pay them what they are worth as they can do more advanced tasks. One reason I left corporate IT is that in a small company you can hit the ceiling pretty fast. As an MSP if you master the daily task, you have an incentive to automate things.
-
With that said, if a skilled employee left, you wouldn't have much of a choice but to look for a skilled employee.
-
@bigbear said in How to Grow from a One Man Operation to Two:
Yeah but I was around at the beginning of this, when we were teaching people what email was and replacing banyan vines with PC's and token ring or ethernet.
The money onboarding a new customer just isn't there. In fact, the cost to acquire an IT customer on a consistent basis is enormous compared to the good ol days.
It is difficult for veterans of the industry to accept, but with the passing of one thing there must be something on the horizon that is accessible to a small business owner.
It's true. Acquisition used to be trivial and the amount of work needed was high. Today, cost of acquisition is enormous and customers need almost zero work.
-
@mike-davis said in How to Grow from a One Man Operation to Two:
@irj said in How to Grow from a One Man Operation to Two:
Curious on everyone's thoughts on how skilled this first employee should be, and how much they should get paid. Are you cheap like the typical SMB and get someone for $40k? or do you pay for actual talent at $70-100K?
I would say that if you don't want a rotten apple, you don't go to the barrel, you go to the tree. I've hired high school and college students. I'll pay them minimum wage and give them raises as they earn it.
As part of the hiring process, I explain that I can pay them what they are worth as they can do more advanced tasks. One reason I left corporate IT is that in a small company you can hit the ceiling pretty fast. As an MSP if you master the daily task, you have an incentive to automate things.
I'm 100% with Mike here. It's rare that I want to hire someone mature in the field. It happens, the right person is the right person. But especially when looking for someone that will change roles over time, getting students or pre-pro level staff means that they grow with you, grow specifically with your needs, grow up in your culture, etc.
-
@mike-davis said in How to Grow from a One Man Operation to Two:
With that said, if a skilled employee left, you wouldn't have much of a choice but to look for a skilled employee.
Until you get big enough to absorb staff changes.
-
I would think first hire to be low end, entry level looking to make his way. 30 hours per week and someone who is flexible to work less hours or more.
No big salary guys until you have revenue to pay you, them, and everything else.
-
@bigbear said in How to Grow from a One Man Operation to Two:
I would think first hire to be low end, entry level looking to make his way. 30 hours per week and someone who is flexible to work less hours or more.
No big salary guys until you have revenue to pay you, them, and everything else.
I would not hire a tech at all as my first employee. I'd be hiring back office before that. Make sure that I (assuming I'm an IT tech owner) was doing zero non-tech work before bringing on tech skills. The tech skills are expensive and risky (because you can take on work that they can then hold you hostage to provide) whereas backend skills are cookie cutter and non-critical. Can't bill for a week, customers don't get mad. Can't fix their networking for a week, they go with the staff that just quit on you.
You want a solid support organization for yourself before you start offloading the tech work and keep paying yourself the big bucks to do low value paper pushing.
-
@scottalanmiller said in How to Grow from a One Man Operation to Two:
There is no organic path from one to two people in the MSP game
I would never do it. 50/50 ownership structures or 49/51% tend to implode poorly.
-
@bigbear said in How to Grow from a One Man Operation to Two:
I would think first hire to be low end, entry level looking to make his way. 30 hours per week and someone who is flexible to work less hours or more.
The problem is it's a VERY narrow spectrum between "So low cost, and so low skilled that he generates more clean up work, and bill credits than he is worth" and "valuable enough that he takes clients and runs, or get someone to pay him 40 hours and a proper salary" You are danging on a knife edge, and given you lack proper hiring process's, back ground checks, and other procedures the odds are you'll screw up somewhere...
I never hired guys with zero experience, because they cost me more than they made me vs. the premium to pay someone for 40 hours and benefits who was... useful and I could bill at $120-140 an hour.
-
@storageninja said in How to Grow from a One Man Operation to Two:
I never hired guys with zero experience, because they cost me more than they made me vs. the premium to pay someone for 40 hours and benefits who was... useful and I could bill at $120-140 an hour.
Zero experience means you have to ask about the home lab. If they really have an interest in something they will probably be doing it in their free time. If they have zero professional experience and no lab experience, I wouldn't be interested either.
-
@mike-davis said in How to Grow from a One Man Operation to Two:
@storageninja said in How to Grow from a One Man Operation to Two:
I never hired guys with zero experience, because they cost me more than they made me vs. the premium to pay someone for 40 hours and benefits who was... useful and I could bill at $120-140 an hour.
Zero experience means you have to ask about the home lab. If they really have an interest in something they will probably be doing it in their free time. If they have zero professional experience and no lab experience, I wouldn't be interested either.
So if they have a home lab and professional experience , you're gonna still pay minimum wage?
-
@mike-davis said in How to Grow from a One Man Operation to Two:
@storageninja said in How to Grow from a One Man Operation to Two:
I never hired guys with zero experience, because they cost me more than they made me vs. the premium to pay someone for 40 hours and benefits who was... useful and I could bill at $120-140 an hour.
Zero experience means you have to ask about the home lab. If they really have an interest in something they will probably be doing it in their free time. If they have zero professional experience and no lab experience, I wouldn't be interested either.
Home lab worked for networking (WAN networking, and MPLS, and OSPF scale well from labs to enterprise shops). There's a lot more clearly defined best practices in networking, than in the systems world.
On the systems side, it's not the same. My shop didn't do desktop support, so the traditional low-end windows stuff didn't exist to work people up. Our lowest tier was doing VDI support (clustered storage, hypervisors, GPO in environments with 8000 users). There are people who run VDI at their house and run NSX for security services but they are few and far between and they certainly aren't cheap.
-
@irj said in How to Grow from a One Man Operation to Two:
So if they have a home lab and professional experience , you're gonna still pay minimum wage?
If they have professional experience, you have to figure out how valuable that experience is to you. If it's professional experience in something that you don't touch, minimum wage might be appropriate. OTOH they might be able to make more somewhere else, so it's not a good fit. They are worth more - just not to your business.
-
@irj said in How to Grow from a One Man Operation to Two:
Zero experience means you have to ask about the home lab. If they really have an interest in something they will probably be doing it in their free time. If they have zero professional experience and no lab experience, I wouldn't be interested either.
So if they have a home lab and professional experience , you're gonna still pay minimum wage?
I paid a guy who was doing part-time desktop support at IKEA, and had a 5 router home lab, with a VMware cluster ~38K to hire. At 90 day I moved him up to 56K. He got brisk (Sometimes twice a year raises) and was over 100K in under 3 years. I could also bill his time at 200-250 an hr (and had work backed up for weeks sometimes for him. It was clients requesting him specifically for him). I got lucky and found someone who had a curiosity and capability but that is useless without the work for him to grow into. I was constantly throwing him into projects that were above what he had done. Do you have that kind of work available? I hired away a lot of guys from Small MSP's who had guys with VCP/CCNA's skill ranges fixing printers, and desktops. The initial cost to hire them was never that bad (45-70K) but it was the upside. of growth to 6 figures (and the skills to demand even more) that brought them on. I hired one guy from a low end MSP for 44K OTE, and ended up having to give him a raise to 70K in under 2 years. He got bored quickly and left (he's running NSX/vRA automation deployments for an airline for ~180K OTE now). If you can't keep the work to keep someone interested it can be more disruptive onboarding, and offboarding them than it's worth. I tried to shoot for ~2 years tenure as my value target.
