3 ms·
we're a small managed private+public cloud services provider and we only have 2 full time operations engineers to support 30+ client companies. we also have a
by taway20171214 9y ago
we're a small managed private+public cloud services provider and we only have 2 full time operations engineers to support 30+ client companies. we also have a handful of consultants that do specialized work, working a handful of hours each month. they seem to be serving a small cluster of customers each also.
we could support 40, our existing 2 engineers are basically under-worked - we have 2 because it would be insanely irresponsible to have just 1, aside from company ownership (which is able to do the work also, if needed). if we absolutely had to, we could cut that down to 1 full time guy. let that sink in; 1 full time guy to manage 40 customers.
having said that, we're still growing as a business, because we've embraced the new reality, but it hasn't been without turnover and pain. we're also putting money into developing products.
the kicker is, even with the R+D, we're more profitable now than 5 years ago, with LESS ops folks (ostensibly less people to do the actual work, though we all know that's not what's really happening). i imagine the same exact thing is playing out with larger in-house staff, as you describe.
this is the new model. WAY more output from less but higher paid full time people, small networks of high-$ specialized consultants, and smaller firms and IT groups working in mercenary fashion. embrace it, or you will bleed yourself dry in less time than you think.
- imhoguy 9y agoHow do you want to do 24/7 with 1 full-time ops eng? Even 2 is small, do they take any time off?
- bomb199 9y agoReads to me like "We've significantly reduced the quality of life for our employees, but greatly increased profits!" More part-time contractors who don't have steady work and fewer FTEs who are on constant call.
- taway20171214 9y agonice guess, but it's the owners who pick up the slack, i.e. me and my partners. we don't have junior people on the payroll i.e. people who would be frequently on call. second, we manage run-of-the-mill web applications, not a bunch of internal IT stuff that is constantly breaking due to user abuse and poor planning. two different types of clients. the problem with running a small tech company is you get accused of all of the downsides of a big company, but enjoy none of the associated upsides. so in your mind, i'm an evil capitalist squeezing every last dime out of my workers, but at the same time, i'm unreliable. in reality none of these things are true, because it's my company and my responsibility to run it. do you see how that works? this is how large companies get away with terrible practices -- because nobody gives business to the smaller ones, usually for reasons that are made up on the spot, like you just did. keep that in mind next time you talk to a small vendor.