What started as straightforward systems integration work evolved into something more specific: helping organizations preserve the reasoning behind critical decisions, not just the systems themselves. Technical expertise is still essential, but durable execution depends on preserved reasoning.

That gap, between what's written down and what people actually know, is where business risk hides.

I started enfusion-group because I’ve always been drawn to the puzzles other people avoid: the ones where things don’t quite fit, or seem too tangled to fix. Finding patterns in the mess, and making things work together when they shouldn’t has always driven me.

Over 20 years, I built a practice entirely through referrals, taking on complex challenges and delivering solid technical work. Organizations brought me in for infrastructure problems. I solved them. They referred me again.

But over time, I noticed a pattern.

The same problem kept surfacing, regardless of the specific technical challenge: organizations had invested heavily in infrastructure and documentation, yet struggled when key people left or priorities shifted. The documentation told you what was built, but rarely captured why decisions were made, how systems actually operated, or where the temporary workarounds were hidden.

Years later, while hoping to get into veterinary school, I worked for the University's Computing and Communications Services department helping students in residence get connected to the Internet, which was in its infancy. Within months, I'd completed more successful connections than all of the other installers combined and was subsequently given the complex installs that came up. That same curiosity and determination enabled me to dig in until things worked.

I haven’t outgrown that curiosity. The satisfaction of understanding how parts work together, and helping others see that clearly too, still drives this work.

The systems are more complex now. The parts include people, trade-offs, assumptions, and institutional memory alongside technical infrastructure.

Preserving that reasoning, not just fixing the systems, is what this work has become.

When I was young, I was fascinated with watching people build and fix things. What always stuck with me is that if you really want to fix something, you need to dismantle it, see the parts, figure out what they do, and ensure they work together properly.

With determination, patience and the right tools, anything could be made to work again.

I’ve always been curious about how things work, and why they were built that way.

Why This Work Matters to Me—

Dismantle it, understand the parts, ensure they work together properly.

The Work—

I still specialize in network architecture and infrastructure design — that’s the bread and butter. But technical work is rarely the biggest challenge now. Understanding the reasoning behind systems someone else built, identifying who actually holds critical knowledge, and bridging the gap between documentation and operational reality is.

Most engagements start with a specific project: resolving a network issue, a technology assessment, a security architecture review. The real value emerges from understanding both the technical details and the organizational context, and identifying knowledge gaps before they become failures.

That’s why many client relationships evolve from project-based work to retained consulting partnerships. Not because I sell them on it, but because consistent presence preserves reasoning — and preserved reasoning protects execution.

The Approach—

That means understanding who knows what, why past approaches succeeded or failed, and what’s been tried before. It means engaging the team members others avoid, the ones who push back, who remember why things were done certain ways, and who hold critical knowledge that isn’t written down.

Technical problems usually have technical solutions. But many business risks present as technical issues. Those require an approach that values institutional knowledge and preserved reasoning as much as technical objectives.

I integrate people before systems, because systems only work as well as the reasoning behind them.

Most long-term relationships begin with a specific technical need, then expand as the value of sustained involvement becomes clear. The pattern is consistent: execution first, then preserved understanding, then strategic partnership.

Specific technical challenges: integration, migrations, assessments, architecture design, security reviews. Clear scope, defined outcomes, often where the relationship begins.

Project Engagements

Retained Consulting

Ongoing involvement that provides strategic perspective without the friction of repeated project scoping. Think of it as sustained access, consistent presence that protects reasoning over time.

Integration Support

M&A technical due diligence, leadership transition planning, and structured knowledge transfer. Especially when business risk concentrates around what people know rather than what’s documented.

How We Work—

Systems are more complex than ever. Teams are more distributed. Knowledge is more fragmented. Institutional memory disappears faster than most organizations realize.

Documentation captures configurations but misses reasoning. Diagrams show connections but not trade-offs. Runbooks explain procedures but not the subtle expertise that makes them work.

Organizations facing mergers, transitions, or rapid growth can’t afford to discover gaps in reasoning mid-execution.

Why This Matters Now—

Institutional memory doesn't wait for you to notice it's missing.

Senior executives, CTOs, CEOs, and Directors of Infrastructure who recognize that technical complexity becomes business risk during transitions. Leaders who understand that their competitive advantage isn’t just in their systems, but in the reasoning behind how those systems evolved.

Organizations where:
  • Key technical team members are retiring, transitioning, or have already left
  • Mergers or acquisitions require reconstructing systems someone else built
  • Growth has outpaced documentation and knowledge transfer
  • Technical decisions need to preserve continuity, not just immediate functionality

Who I Work With—

Twenty years of systems integration consulting, built entirely through referrals until recently. Deep expertise in architecture, infrastructure design, and the preservation of institutional reasoning alongside technical execution.

Based in the Toronto area, working with clients across North America who value clear thinking over jargon, durable solutions over quick fixes, and long-term outcomes over technical perfection.

When I'm not connecting dots for organizations, I'm with my 2 kids, 2 dogs, 2 cars, way too many cameras, guitars, even more computers, and one beautiful better half.

The Foundation—

Let’s protect the reasoning behind what you’ve built.