From answering phones to running a multimillion-dollar MSP, John Snyder's 26-year journey proves that patience, learning from catastrophic failures, and actually listening to your team matter way more than an MBA. We're breaking down what his rise to the corner office teaches us about surviving—and thriving—in tech leadership.
How a Field Technician Became a Tech CEO (And Why His Secret Isn't What You'd Expect)
How a Field Technician Became a Tech CEO (And Why His Secret Isn't What You'd Expect)
There's this mythology in tech leadership that goes something like this: smart kid learns to code at 14, drops out of college, raises $5 million in venture capital by 26, and becomes a billionaire by 30.
It's a fun story. It's also completely divorced from reality for most tech professionals.
Enter John Snyder, CEO of North Carolina-based MSP Net Friends. His origin story is almost boringly normal—except it's actually the most instructive kind of normal. He wasn't the third person at his company because he was a visionary founder. He became a visionary because he stuck around for 26 years and paid attention to what worked and what didn't.
That's not inspirational fluff. That's actually the template more tech leaders should follow.
The Unglamorous Path to the Top
Let's be real: there's nothing sexy about starting as a gopher-level field tech. You're not disrupting industries. You're not debugging code at 2 AM fueled by energy drinks and existential purpose. You're fixing printers, running cables, and probably getting yelled at by someone whose password they definitely wrote on a sticky note under their keyboard.
But here's what Snyder figured out that a lot of MBA graduates never do: when you're at that level, you're actually learning the business from the ground up.
You're seeing where systems fail in real time. You're talking to customers when they're frustrated (or, occasionally, grateful). You're understanding the economic reality of delivering a service—not just the theoretical side of it from a business school case study.
The mindset shifts required at each rung of the ladder aren't about becoming a different person. They're about asking better questions. As a field tech, you ask: "How do I fix this issue?" As a team lead, you ask: "How do we prevent this issue?" As a CEO, you ask: "How do we build a sustainable system where good outcomes happen by default?"
Snyder spent 26 years living through those transitions. Most people would have either burned out or left. The fact that he didn't tells you something important about how he approaches pressure.
When Everything Falls Apart (And You Learn Who You Really Are)
Here's the part of the career narrative that business podcasts usually gloss over: the catastrophic failure.
Snyder's company experienced a $2 million cybersecurity-contracts implosion. That's not a rounding error. That's not "we had to cut back on team lunches." That's the kind of hit that kills companies.
What followed was worse in some ways: layoffs. The kind where you have to look people in the eye and tell them there's no job for them tomorrow. The kind that keeps you awake at night, probably wondering if you made the right calls.
But here's what most people miss about these situations: they're actually where leadership gets forged or revealed.
The companies that survive catastrophic failures are the ones whose leaders admit what went wrong, make hard decisions quickly, and then show up differently for the people who remain. Snyder clearly did that—Net Friends is still standing, and the fact that we're hearing from him years later suggests the team rebounded.
That's not luck. That's a leader who understood that crisis management is 10% business strategy and 90% human psychology.
Doing It In-House (Even When Outsourcing Seems Smarter)
One of the most counter-intuitive decisions Snyder made was building an in-house marketing team of three instead of outsourcing to agencies. On paper, this doesn't always make financial sense. Agencies have economies of scale. They have specialists. They have experience across dozens of companies.
But here's what Snyder understood: when you're building a pure-play managed service provider, you need people who understand your actual business, not just the generic playbook.
An in-house team of three people is cheaper than you might think when you factor in account management overhead, contract minimums, and the constant friction of explaining your business model to external partners who're working for five other clients simultaneously.
More importantly, those three people become extensions of your leadership. They see customer calls. They understand where the product works beautifully and where it doesn't. They can move fast because there's no approval chain. They're not optimizing for billable hours—they're optimizing for outcomes.
Is this advice for everyone? No. But it's the kind of decision that separates companies that have marketing from companies where marketing is part of the DNA.
Robotic Process Automation Isn't Just a Buzzword
Snyder's company leverages RPA (robotic process automation) to deliver what he calls "lightning-fast IT outcomes." This is where a lot of leaders' eyes glaze over because RPA sounds complicated.
It's really not. It's basically: "What repetitive task are we doing manually that a script can handle?"
For an MSP, that might be:
- Automating password resets
- Running routine security scans on a schedule
- Provisioning new user accounts with standard configurations
- Generating compliance reports
The boring stuff. The stuff that eats time but isn't intellectually challenging. Automate it. Free up your team to do work that actually requires a human brain.
The companies winning in tech right now aren't the ones doing more things. They're the ones doing the same things but better and faster because they've eliminated the busywork.
The Mentorship Angle (And Why It's Not Just Feel-Good Talk)
Snyder spends time on mentorship and team trust, especially after crisis. That might sound like corporate wellness propaganda, but there's actual strategy here.
When a company survives a major catastrophe (like that $2 million hit), the team is running on trust fumes. People wonder: "Are we actually going to make it? Is leadership making the right calls? Should I have already updated my LinkedIn?"
A leader who takes mentorship seriously—who actually invests time in helping people grow—is sending a signal: "I believe in this company's future, and I believe in your future here." That's not manipulation. That's evidence-based leadership.
Trust isn't something you build with a memo. It's built through consistent action over time.
The Real Takeaway
Snyder's climb from field tech to CEO isn't unusual in the path it took. What's unusual is that he stayed long enough to actually master the business instead of jumping to the next rung to maximize ego and salary.
That's patient ambition. That's the kind of leadership that builds things that last.
If you're eyeing the C-suite—or if you're already there and wondering what you're doing wrong—the real lesson isn't about some secret hack. It's about:
- Being ruthlessly honest when things go wrong
- Understanding your business from the ground up
- Building a team you'd actually trust in a crisis
- Automating the boring stuff so humans can do human work
- Investing in the people around you
None of that is revolutionary. It's just... good business. And for some reason, in an industry obsessed with disruption, that's the rarest thing of all.
Interested in learning more about how tech leaders navigate crises and build sustainable businesses? Keep an eye on industry podcasts and mentorship opportunities in your network. The lessons are out there—you just have to be willing to listen.
Tags: ['tech leadership', 'msp management', 'career growth', 'crisis management', 'business strategy', 'robotic process automation', 'organizational culture']