1001 Reasons Not to Be an MSP
-
You have to wear too many hats. Sales, Marketing, Customer Relations, you are rarely just the IT guy.
-
@coliver said:
You have to wear too many hats. Sales, Marketing, Customer Relations, you are rarely just the IT guy.
That's big. Being good at IT doesn't imply that you are good at sales, marketing, business or accounting. Very few people are good at all of those. At best you are a renaissance man and will have to task switch like crazy. At worst you will have to hire lots of people to do each of those things. It takes a lot of people to support a single full time IT pro.
-
I love not being an MSP.
-
@Breffni-Potter said:
I love not being an MSP.
ha ha. /sarcasm
-
Well I had to say something
-
Making the leap from one man MSP to a functional multi-person company is not an organic one. Only in the rarest cases can you just go from working alone to having a team. The cost of bringing on that first employee has to come from somewhere and unless you can bring on new clients that pay for the new staff at the exact same time as the new staff you will have major financial overhead to carry.
-
@scottalanmiller said:
Making the leap from one man MSP to a functional multi-person company is not an organic one. Only in the rarest cases can you just go from working alone to having a team. The cost of bringing on that first employee has to come from somewhere and unless you can bring on new clients that pay for the new staff at the exact same time as the new staff you will have major financial overhead to carry.
I know someone in that boat.
-
Do I get a co-writer credit for providing the title?
reason #427: The customer is rarely right, but you still have to kiss ass to get their money.
-
@scottalanmiller said:
Making the leap from one man MSP to a functional multi-person company is not an organic one. Only in the rarest cases can you just go from working alone to having a team.
Would this not also apply to businesses of other shapes and sizes?
If you want to go from a single restaurant to 2 locations, there is a cost, there is a leap you have to make, a decision which carries risks but it could be an investment that pays off, many times it does not but on the occasions it does pay off, wow.
-
@scottalanmiller said:
Making the leap from one man MSP to a functional multi-person company is not an organic one. Only in the rarest cases can you just go from working alone to having a team.
@Breffni-Potter said:
Would this not also apply to businesses of other shapes and sizes?
If you want to go from a single restaurant to 2 locations, there is a cost, there is a leap you have to make, a decision which carries risks but it could be an investment that pays off, many times it does not but on the occasions it does pay off, wow.
It does, but the leap form single to more than one is huge. It maybe less people or tings than opening a second location, but it is a much different animal in other ways.
-
@Dashrender said:
@scottalanmiller said:
Making the leap from one man MSP to a functional multi-person company is not an organic one. Only in the rarest cases can you just go from working alone to having a team. The cost of bringing on that first employee has to come from somewhere and unless you can bring on new clients that pay for the new staff at the exact same time as the new staff you will have major financial overhead to carry.
I know someone in that boat.
I've known many over the years.
-
@Breffni-Potter said:
@scottalanmiller said:
Making the leap from one man MSP to a functional multi-person company is not an organic one. Only in the rarest cases can you just go from working alone to having a team.
Would this not also apply to businesses of other shapes and sizes?
If you want to go from a single restaurant to 2 locations, there is a cost, there is a leap you have to make, a decision which carries risks but it could be an investment that pays off, many times it does not but on the occasions it does pay off, wow.
I think that people opening restaurants have a very different situation. Sure, opening another location has costs, but the existence of the restaurant, in theory, brings in revenue itself just by being open. Adding staff to an MSP does not do that. You have to have the staff and then figure out how to generate work for them. Just having the extra staff does not itself generate work.
-
Because no customer "to be" knows what you do and you have to educate every single one of them before even finding out if they might make a good customer. It is really tough working in an industry where the people who need you most have no idea what you do.
-
@scottalanmiller the "free initial site evaluation" saved me a lot of pain - excellent tip for any MSP out there.
-
@JaredBusch said:
@scottalanmiller said:
Okay, I'll start: The field is over saturated,with poorly trained people that should not be running a business service.
FTFY
So True..
-
@Dashrender said:
@scottalanmiller said:
Making the leap from one man MSP to a functional multi-person company is not an organic one. Only in the rarest cases can you just go from working alone to having a team. The cost of bringing on that first employee has to come from somewhere and unless you can bring on new clients that pay for the new staff at the exact same time as the new staff you will have major financial overhead to carry.
I know someone in that boat.
Don't you be talkin bout me
-
You have to agree it's hard though isn't it?
-
OMG, it's super hard. I was at the end of the diving board, digging through resume's meeting with folks, and lost a key client to a big box MSP round here, had to climb back down the ladder, eat a piece of humble pie, and figure out how to grow...
-
Running an MSP is not for the faint of heart. There a days you don't sleep, oh wait that's months you don't sleep. There are days you don't eat or shower or pee. Work is your life when you are on your own.
-
and have an 8 month old
whatever. I'd be bored if I had a normal job
