>Lots of long-term freelancers will drop the hourly stuff ASAP too.

Hm. See, I've been thinking about this. I'm a sysadmin. A computer janitor. The essence of my job is that when something breaks, I fix it. (I'm actually way better at that part of the sysadmin role than at the architecture part, though I can do that, too; there are many sysadmins who are better architects than I am. However, there is this phenomena; the more senior a sysadmin is, the harder it is to make him or her carry a pager. I carry a pager, and in /that/ set, well, I look pretty good.)

So yeah, what I'm charging you for is something you probably won't need much at all of (I mean, I'll help you apply patches and do backups and other simple bullshit, but I'll probably make my PFY do that, or train up one of your kids.) My real value is that when something breaks at 3am on a Sunday morning, I'll wake up and deal with it. Really, unless you are twitter, I've got enough spare hardware that your stuff could literally catch fire and as long as I've got backups, we're good.

Problem is, how to charge? I've got a bunch of folks wanting to pay me $50/month. Which I could do if I automated all the PFY work. (which, I could do if I didn't give you root, and I only let you use my versions of the programs I chose to support.) but it's one of those things where I'd need thousands of customers to make it worth my time. At that point, we need to do shifts, etc, etc... I mean, it's a realistic business, but a deep/hard one.

I mean, I'm going to want like two to four grand for the two or three days of my time that a full "shit caught fire at 3am" cleanup is going to take (not that you'd be down for two or three days; I'll get you back up the first day, but I'm not going to be particularly useful for the next few days... which presents something of a problem if these things happen in succession.)

But that's the thing, I can do a better job if I'm there all along, and I can say "don't do that" when you are setting the thing up, and I can make sure you have accessible backups and stuff.

I've sent out some feelers at the $500-$1000/month range, were I keep a spare going (which means more ongoing work for me, keeping the spare up to date, but it means much less pain when shit does break.) But, eh, I haven't gotten interest, and frankly, I'm not sure if that's enough to make it worth the brainspace. And that's the thing, if you get up to $4000-$5000, well, you can get a midwesterner or an indian or a russian mostly kinda sorta full-time, and yeah, at that rate, they aren't going to be as good as I am, but there is a lot of value in having someone mostly full time (which I would not be, even at that rate.) So maybe the right model for me is "wake me up, place a five grand deposit; I keep the money if I fix your shit in the next X hours" or something. I could be talked into that, if I had some reasonable assurance of getting paid.

I think the root cause might be that most small companies use "the cloud" and don't feel they need that kind of sysadmin experience (and spare pool... "the cloud" vastly diminishes the market value of my giant spare pool, probably even more than it does my SysAdmin experience.) and larger companies would prefer to have someone on-staff full-time.

Also, well, I'm very good at marketing "value" - e.g. most of my experience is competing on price (yes, yes, I know I'm behind the curve. I am working on it. You do not understand how much I am working on it.) and, well, this is not an area where I want to compete on price. I'm pretty okay getting woken once a week. If I get woken 3 times a week, for more than one week in a row? things start to get bad. Wake me up every night? well, I've had times in my life when all I did was sleep and respond to emergencies; I can do it, but I'd really prefer not to go back there. So yeah; I have a very limited number of "wake me up" slots I can sell. They need to be expensive.