Alex Ivantsov
Operations Manager. Systems Engineer. Builder of Things That Work.
About Me
I've spent my career in the managed services space, where IT meets real business operations. Started out as an engineer solving technical problems, and somewhere along the way I became the person solving business problems with technology.
Today I lead operations at a growing MSP. My role crosses engineering, sales, compliance, and strategy, often in the same afternoon. I build the automation workflows that connect our tools, run the client relationships, design the compliance programs, and train the team that delivers it all.
I'm not a specialist who goes deep on one thing. I'm a generalist who goes deep on whatever matters most at the time. I've gotten comfortable operating where technical execution meets business strategy, and the work I care about most is finding the constraint: the one thing actually holding an operation back, and solving that before anything else.
I think the MSP model is underrated. We sit at the workflow layer, not the feature layer. We see the whole picture: finance, operations, compliance, IT. We can draw direct lines between technology decisions and business outcomes. That perspective shapes everything I do.
What I Do
Automation & Integration Engineering
I design and build the connective tissue between business tools. Webhook-driven workflows, API integrations, AI-augmented processes, whatever it takes to eliminate manual handoffs and make systems talk to each other. My primary platform is N8n, backed by PowerShell scripting and REST APIs across the entire MSP stack.
IT Strategy & Client Engagement
I serve as the strategic IT advisor for our clients, running quarterly business reviews, building technology roadmaps, and translating business goals into actionable IT plans. I also design our sales process, build proposals, and create client-facing materials. The approach is always the same: start with the client's constraints and goals, then draw a direct line from IT to outcomes.
Cybersecurity & Compliance
I build and manage compliance programs grounded in real security, not checkbox exercises. My work spans CMMC frameworks, incident response planning, secure configuration management, and security tooling deployment. I care about red team / blue team thinking and making compliance meaningful rather than performative.
Operations & Process Design
I architect internal operations from dispatch workflows to change management processes, drawing on Theory of Constraints and continuous improvement principles. The goal is always the same: make the work visible, eliminate bottlenecks, and build systems the team actually follows.
Technical Expertise
I operate across a wide technical surface area. Here's where I go deepest.
MSP & Business Stack
Microsoft 365 & Entra
Core Infrastructure
Security & Compliance
Backup & Disaster Recovery
Voice, Video & Other Verticals
Hardware
Sales & Client Engagement
AI & Misc
How I Think
"Find the constraint first."
Every system has a bottleneck. The Theory of Constraints teaches that unless you're directly addressing the thing that's actually limiting throughput, every other improvement is an illusion. I apply this to everything: client IT strategy, internal operations, sales conversations, and my own prioritization. The first question is always the same. What's the one thing holding this back?
"Make the work visible."
Unplanned work is the silent killer of IT operations. I'm influenced heavily by The Phoenix Project and improvement kata, the idea that every task should be visible, tracked, and intentional. When work is invisible, priorities are imaginary. I build systems and processes that force clarity: what are we doing, why, and what's blocked.
"Build when it gives you control. Buy when it saves your sanity."
I'm not dogmatic about building everything in-house. If a vendor solves the problem well and shifts the maintenance burden off my team, that's often the right call. But when control and long-term ROI matter, when the integration layer is the product, I build it myself. The automation platform I've built on N8n exists because no off-the-shelf tool could tie our stack together the way we needed. Knowing when to build and when to buy is one of the most important judgment calls in operations.
Work I'm Proud Of
The Automation Layer
Built an automation platform that replaced our entire integration stack.
I designed and built a workflow engine on N8n that processes PSA ticket webhooks, routes security alerts through conditional logic based on JSON payload structure, enriches ticket data with AI, and syncs billing information across systems. It replaced multiple Zapier workflows, reduced manual intervention, and gave us full control over how our tools communicate. It's not pretty code. It's effective code, and it runs every day without complaint.
Constraint-Based Sales
Redesigned our entire sales approach around one question: what's your constraint?
I rebuilt our sales deck and discovery process around three core business metrics: financial accuracy, operational efficiency, and legal compliance, all anchored by the Theory of Constraints. Instead of leading with a feature list and hoping something sticks, we ask prospects about their business goals and constraints, then draw a direct line from IT to outcomes. It repositioned us from "IT support company" to "strategic business partner" in every conversation.
Full-Stack Operations Buildout
Built the operational backbone of a growing MSP from scratch.
SOPs for helpdesk, dispatch, escalation, and project management. Legal frameworks including MSA and services guide. Vendor stack evaluation and deployment, from RMM to PSA to compliance tooling. Technical documentation library. Engineer training programs. Sales process. I didn't inherit a playbook. I wrote one, and then trained the team to run it. Most of it was built solo, under pressure, with shifting priorities. And it works.
Beyond Work
Father first, engineer second. When I'm not building systems or chasing constraints, I'm spending time with my family, tinkering in my home lab, or finding something new to learn. I run a Proxmox server with 18+ services because I genuinely enjoy the problem-solving — it doesn't stop being fun just because the workday ends. I'm a lifelong tech nerd who still gets excited about cool hardware, clever automation, and elegant solutions to messy problems.
Want to work together, talk shop, or just say hello?