I’m Erik, a solution developer, architect and product consultant. I partner with companies helping them figure out what to build, how to architect it, and how to actually ship it.

My background spans software engineering, solution architecture, and product ownership, which means I’m comfortable at the whiteboard defining system design and equally comfortable down in the details when the details are what matter. Over the years I’ve worked across mobile, web, and cloud platforms, and more recently I’ve been going deep into AI-integrated systems, agents, and MCP-based workflows.

What I’ve learned along the way is that the hardest part of building software is rarely the technology itself. It’s the decisions and the trade-offs every decision quietly carries with it. That’s why I started Leading Through Systems: to share the thinking behind those choices, not just the final answers. The real lessons never came from documentation. They came from real projects, real constraints, and the occasional expensive mistake.

If you design, build, or lead complex systems, and you care about understanding Why something works, not only How, I think you’ll feel at home here. And if you need someone to think through your architecture, challenge your assumptions, and help you ship something real, let’s talk.