I kept a 200-person company running alone as the only sysadmin for 8 yrs, but they denied every raise request bc “it is a cost center.” I left for 40% more. My replacement quit after 3 days. Now they’re paying $300/hour for what I handled for $75k…
My name is Ethan Mercer, and for eight years I was the only systems administrator keeping a two-hundred-person insurance company alive. If email failed, claims stopped. If the servers went dark, two hundred employees sat frozen. If backups died, client records vanished and regulators came knocking. Every critical system passed through my hands.
I managed Exchange, virtual machines, the firewall, the VPN for remote staff, two office networks, security patches, backups, vendor contracts, license renewals, workstation rollouts, printer disasters, and the executive panic that arrived whenever a screen froze for five minutes. It was a three-person job. There was only me.
I took the role after a layoff and accepted low pay because I needed stability. I told myself it was temporary. It was not. They bumped my salary twice, then the number stopped moving. Every year I asked for a raise. Every year I brought proof: uptime reports, recovery plans, local market data, and the cost of a serious outage. Every year the same man shut me down.
Martin Hale, our CFO, had one favorite phrase: “IT is a cost center.” He said it with the certainty of someone who never touched the systems he dismissed. He approved office renovations, new sales laptops, and executive retreats without hesitation. But when I asked for a redundant server or a password management platform, he acted as if I was asking for a yacht.
The money bothered me, but the contempt was worse. Martin talked about my work like everything ran on autopilot. As if networks patched themselves, as if backups were optional, as if the reason nobody noticed me was because I did not matter. He ignored my written warnings about single points of failure. He ignored my request for a junior administrator. He ignored my recommendation to centralize critical credentials. Quietly, I built protections anyway. I documented everything in an internal wiki and stored critical passwords in an encrypted vault because no one would fund anything better.
Then a recruiter found me.
The new company was two hours away. Similar size, real infrastructure, actual teammates, a rotating on-call schedule, and a salary forty-six percent higher than mine. I read the offer three times. My wife, Angela, looked over my shoulder and said, “Take it before they convince you that suffering is loyalty.”
So I did.
I typed a two-paragraph resignation letter, printed it, and walked into Martin Hale’s office. He read it, leaned back in his chair, and laughed. Not nervous laughter. Not shocked laughter. A small, dismissive laugh, like I had made a childish move in a game he had already won.
“Where are you going?” he asked.
I told him.
“For how much?”
I told him that too.
His face tightened for half a second, then went flat again. “That’s your decision,” he said. “We’ll just hire someone. IT guys are a dime a dozen.”
I stood there with my resignation in his hand and eight years of invisible labor in my chest, and I realized something he still did not understand: he had just insulted the only man who knew where every weakness in that company was buried.
I spent my final two weeks meticulously updating the wiki. I recorded the quirks of the legacy Exchange server, the specific sequence for rebooting the aging SAN, and the login for the HVAC controller that—for some reason—was tied to the primary domain controller.
Martin didn’t bother to find a replacement until my final three days. He hired a guy named Marcus. Marcus was young, carried himself with the confidence of someone who had only ever worked in brand-new, cloud-native environments, and looked at our server room like it was a museum of the Bronze Age.
“I’ll have this all migrated to the cloud in a month,” Marcus told Martin during his orientation.
Martin beamed at me, a smug *see-how-easy-this-is* expression on his face. “Efficiency, Ethan. That’s what a ‘cost center’ needs.”
I handed Marcus the encrypted vault keys, showed him the wiki, and walked out the door at 5:00 PM on Friday without a single “thank you” or a gold watch. I didn’t look back.
### The Silence of the First Week
Monday at my new job was a revelation. I had a budget. I had a boss who asked, “What do you need to succeed?” instead of “Why does this cost so much?” I had a team of four other admins. For the first time in nearly a decade, my phone didn’t buzz once during dinner.
Tuesday passed in peace. Wednesday was even better.
Then came Thursday. At 10:15 AM, my personal phone lit up. It was an unknown number from my old area code. I ignored it. Ten minutes later, a text arrived from a former coworker in the claims department: *Ethan, help. Everything is down. Marcus is screaming in the server room. Martin is looking for you.*
I deleted the text and went back to my meeting.
### The Three-Day Limit
That evening, I got the full story from a friend still inside.
Marcus hadn’t read the wiki. He’d tried to “optimize” the firewall rules on Wednesday afternoon, accidentally cutting off the VPN for the entire remote workforce. When he tried to roll it back, he realized he hadn’t backed up the config. In his panic, he tried a hard reset on the core switch, which triggered a power surge that the aging UPS—the one Martin had refused to replace for three years—couldn’t handle.
The SAN crashed. Hard.
Marcus looked at the blinking red lights, looked at the 200 angry employees standing outside the glass, and realized he was the only captain on a sinking ship he didn’t know how to sail. On Thursday morning, he left his badge on the server rack, walked out, and sent a one-line email: *“I quit. This is a disaster.”*
### The Bill Comes Due
On Friday morning, my phone rang again. This time, I recognized the number. It was Martin Hale. I let it ring until the final second, then picked up.
“Ethan,” he said, his voice stripped of all its usual condescension. He sounded like a man who hadn’t slept. “We’re having some… technical hurdles. Marcus had an emergency. We need you to come in for a few hours to stabilize the SAN.”
“I have a new job, Martin,” I said calmly. “I’m busy.”
“We’ll pay you for your time! Name a price.”
“My price is that I don’t work for you anymore,” I replied. “You said IT guys were a dime a dozen. Go find another dime.”
I hung up.
An hour later, I heard through the grapevine that they had called an emergency Managed Service Provider (MSP). This wasn’t a standard contract; it was a “Forensic Recovery and Emergency Restoration” request.
Because the systems were so specialized and the documentation hadn’t been followed, the MSP classified the site as a “Critical Environment.” They sent two senior engineers and a project manager.
**Their rate? $300 an hour, per person.**
### The Final Calculation
It took the MSP four days of around-the-clock work to bring the insurance company back online. They had to rebuild the routing tables from scratch because Marcus had wiped the backups during his “optimization.”
The final invoice for that one week of “emergency services” was nearly **$40,000**.
When the dust settled, the MSP told Martin they wouldn’t touch the account moving forward unless the company signed a long-term maintenance contract. The cost of that contract, which only covered “basic stability,” was **$180,000 a year**—more than double what I had asked for in my final raise request.
I saw Martin one last time, months later, at a local business mixer. He looked older. He avoided my eyes, drifting toward the buffet table as soon as he saw me approaching.
I just smiled and took a sip of my drink. I was making six figures now, working forty hours a week, and my new company had just approved my request for a redundant server cluster without a single complaint.
Martin was right about one thing: IT *is* a cost center. But as he eventually learned, it’s nothing compared to the cost of a vacuum.
