I Survived: The Client Who Called Me at 3am Because Their Printer Was Low on Toner
Learn how to set boundaries in our MSP Contract Checklist and know your Fair Work Rights.
I need to tell you about the client that broke me. Not because they were恶意 — actually, most of the time they were perfectly pleasant. They broke me because nobody at my MSP had the spine to set a boundary. And because when your company's revenue depends on one client, boundaries become optional.
The Client
Dealing with a similar situation? Our How to Leave an MSP guide covers exit strategies.
Let's call them "Vertex." Vertex was a property development firm in the eastern suburbs of Melbourne. About 80 staff. Good client. Solid revenue. They paid their bills on time (mostly). And their office manager — let's call her Karen, because of course it was Karen — had my personal phone number.
I was a service desk lead at a large MSP. We had about 40 clients, but Vertex was one of the big ones. Their MSA was worth $2 million a year. That number was sacred at the MSP. It was spoken about in hushed tones in management meetings. It was the reason Vertex got whatever they wanted.
And what Vertex wanted was me. Specifically, they wanted me available whenever they decided something was an emergency.
The Pattern
It started small. A text on a Saturday morning: "Hey, the printer on Level 3 is out of toner. Can you order some?" I'd explain that toner was a consumable they needed to manage themselves — it wasn't a support issue. Karen would say, "Just this once." It was never just once.
Then it escalated. Sunday evening, 8pm: "My email is loading slowly. Can you check?" Monday morning, 6am: "The WiFi isn't working in the boardroom." (It was. Karen just hadn't turned on her laptop yet.)
Then the real calls started.
Friday night, 11pm: "I can't access the shared drive from home." (She'd forgotten her VPN password.)
Saturday, 7am: "The air conditioning is making a weird noise." I told her that wasn't IT. She said, "You guys manage everything here, can you just look at it?"
Christmas Day. Christmas. Day. 2:30pm. "The office is hot. The air conditioning isn't working. Can someone come in?"
I wasn't joking about the air conditioning. They genuinely called me on Christmas Day about HVAC.
Why It Continued
I raised it with my manager. Multiple times. "We need to set boundaries with Vertex. They're treating the after-hours support line like a concierge service."
My manager — a good guy, honestly, just terrified of losing the account — would nod and say, "I know, I know. Let me handle it."
He never handled it. Because every time he thought about setting a boundary, someone in management reminded him: "$2 million a year. If we upset them, they walk. And they're 15% of our revenue."
The math was simple. My sanity was worth less than 15% of the quarterly target. That's what it came down to.
The Burnout
By the end, I was sleeping with my phone on loud. Every notification sent a spike of adrenaline through me. I'd check my email before I checked on my kids in the morning. I'd calculate dinner plans around whether I might get a call.
My wife noticed. "You flinch every time your phone buzzes," she said. She was right.
I was averaging about 4-5 after-hours contacts per week from Vertex alone. Not counting the other 39 clients. I was doing a full workday, plus 10-15 hours of after-hours work that nobody paid me for, because my salary was "competitive" and "included reasonable additional hours."
Reasonable. There's that word again.
The straw that broke me was a Wednesday. I'd been at work since 7am. Left at 6pm. Got a call at 9pm about a "server issue" at Vertex. Spent two hours troubleshooting remotely. It was a user error — someone had accidentally changed a Outlook setting. Fixed it by 11pm. Got back online at 7am Thursday. Karen called at 10am to ask if I could come on-site to "walk her through how to set up a printer." For her new laptop.
I was there by 11am. I walked her through it. Smiled. Nodded. Drove back to the office. Sat at my desk. And realised I couldn't do this anymore.
The Exit
I resigned the next week. No counter-offer. My manager said, "I'm sorry we couldn't do more about the client boundaries." I said, "You could have. You chose not to."
I work in internal IT now. A mid-size company where IT is a department, not a service. If someone calls me at 3am, it's because the building is on fire. If it's not on fire, it can wait until morning. My manager understands this. My colleagues understand this. My family understands this.
The pay is $5K less. My wife says I'm a different person. She's right.
What I'd Tell Others
Revenue concentration creates power imbalances. When one client is a significant percentage of your MSP's revenue, that client can demand anything. And "anything" usually means your time, your evenings, and your sanity.
"The client is always right" is a business philosophy, not a support strategy. Good client management means setting expectations, documenting scope, and saying "that's not included in your MSA" when it isn't. An MSP that can't do this is selling its staff, not its services.
Your after-hours phone number is not a client asset. If a client has your personal number, that's a process failure. After-hours contact should go through a dedicated line with clear escalation rules. Not your personal mobile.
Christmas Day HVAC calls are not IT issues. Full stop. If your MSP can't explain this to a client, the MSP has a management problem, not a staffing problem.
The client you're afraid to lose is the client that's costing you the most. Vertex was worth $2M a year in revenue. They were also costing the MSP its best staff. When I left, two other senior techs followed within six months. The "cost" of losing Vertex would have been less than the cost of the team attrition.
What I Learned
- Scope creep applies to after-hours availability, not just project work. If your after-hours support keeps expanding to cover non-IT issues, that's scope creep. Address it before it becomes normalised.
- MSAs should clearly define after-hours scope. What constitutes an emergency? What's the escalation path? What's the response time? If this isn't in the contract, it should be. It protects both the MSP and the staff.
- "Competitive salary" is MSP code for "we're not paying you overtime." If your salary is "competitive" but you're working 50+ hours a week, your effective rate is lower than you think. Know the difference.
- Client size doesn't dictate respect. A $2M client should be managed, not indulged. The best MSPs are the ones that can tell a client "no" without losing them. The worst ones are the ones that sacrifice staff to avoid an awkward conversation.
- Internal IT is not a step down. I went from an MSP to internal IT. Same technical skills. Better boundaries. Better culture. Less money. Best trade I've made since leaving the MSP world.
Have your own story? Submit it anonymously
Was this helpful?