I've been in the MSP trenches since I was 19. What I've learned is that technology doesn't fail because of hardware. It fails because no one built the function that governs it.
Philosophy
Most organizations treat technology as something to manage: a ticket queue, a vendor list, a line item in the budget. That's not alignment. That's triage.
What I do is different. I build the systems that make technology intentional: the processes, the people, the decision frameworks, the feedback loops. The goal isn't to put out fires faster. The goal is to build an organization that's harder to set on fire.
This is what I call technical alignment: not a service you outsource, but a function you build. And like any function worth building, it requires systems thinking, not just technical knowledge.
The same mental model that makes a vCIO program work is what made a realty business and a marketing agency run. The industry changes. The thinking doesn't.
"Technology doesn't fail because of hardware. It fails because no one built the system around it."
The Work
Built the technical alignment service area from the ground up: a TAM + vCIO hybrid function that didn't exist before I started. Defined the methodology, built the team, established the processes. In the first 45 days, a team of 3.5 identified $1M in foundational projects across the client base. Today: 40 clients on 18-month technical roadmaps across an initial cohort, with the rest of the book being onboarded behind them.
Department Built from ZeroStarted, built, and ran my own managed service provider for five years. Wore every hat: technical, operational, financial. Closed it not because it failed, but because a better opportunity came along. That distinction matters to me.
Founded & OperatedThree different industries with nothing in common except the same operator running them. PPC marketing services, residential real estate, housekeeping. None required IT expertise. All required systems thinking: how do you build a process that works without you being in every decision? Turns out the answer is the same regardless of the industry.
Systems TransferStarted at 19. Grew up in the MSP world before anyone called it an MSP. Have seen this industry from nearly every angle: technician, engineer, owner, department head. The perspective that comes from doing all of it, not just one piece, is what informs how I think about technical alignment as a discipline.
Ground UpField Notes
Systems Thinking
I used to run three teams of ten engineers. We hit our KPIs. Then the organization shifted and I watched it all fall apart. Not because the people got worse. Because decisions were being made on vibes instead of a framework.
2026
vCIO / Technical Alignment
Most vCIOs are operating from one of two places: engineering lifecycle refresh thinking or sales quotas. The problem goes deeper than incentive misalignment. It starts with how the role thinks about clients.
2026
Leadership
Everyone says hire people better than you. The part nobody unpacks is what "better" actually means, because the advice stops making sense the moment you expect it to mean better across the board.
2026
AI / MSP Strategy
Everyone in the MSP space is either selling AI or hiding from it right now. Both camps are making the same mistake.
2026
Dallas Pedersen is the Director of Technical Alignment at Executech, where he built Utah's Technical Alignment and vCIO function from the ground up. He's been in the MSP and tech industry since 2011, has owned and operated businesses across IT, marketing, real estate, and home services, and thinks about every one of them the same way: as a system.
Contact
Whether you're thinking about technical alignment, building a vCIO practice, or just want to compare notes on what's actually working. My inbox is low-pressure. I'm currently employed and not shopping myself around, but good conversations are always worth having.