4 ms·
In sysadmin work it's easier to make large consulting fees. The problem you have is that no one spends the money for good sysadmin architecture/infrastructure.
by johngalt 14y ago
In sysadmin work it's easier to make large consulting fees. The problem you have is that no one spends the money for good sysadmin architecture/infrastructure. So you can't sell "good practices". Instead just focus your work in loss aversion, not value creation. People will spend more for a emergency room doctor/hospital than a gym membership.
The keys are two simple things:
1. Be able to quickly fix expensive problems.
2. Make sure people with expensive problems know about you.
I've routinely seen multi-million dollar projects held up for months over things a skilled sysadmin can solve in a day. You just have to be at the receiving end of that 911 call, and not afraid to quote a big flat fee for problem resolution.
- samstave 14y ago>The problem you have is that no one spends the money for good sysadmin architecture/infrastructure. I disagree with your statement. I am currently in Chicago just completing the infrastructure implementation for a large enterprise client where I specifically was brought on to do their tech infrastructure. They pay a lot for this service. Here is my scope of work: Physical cable plant design Physical network design (based on their corporate logical architecture) Physical/Logical implementation (Procure, track, receive, rack, patch, power, config, test, coordinate, hand-off) Turn up and test Day-one operational support and hand-off. Doing this for all their global offices.
- zenocon 14y agoI bet Team Romney / Orca would have paid handsomely for this at zero-hour, despite all the cost-cutting they did up front.
- ams6110 14y agoYeah but some things aren't possible. A poorly architected system can't be fixed in an hour, or a day, in most cases.