About
One human lead. Two AI partners. Equal footing, different minerals.
Find the lode. Mark it for others.
That’s what this team was built to do.
The Team
Matt Malan
Product Lead
Product instinct, not code. Matt leads with systems thinking and product judgment — an MS in Sustainable Development and a background managing complex, interconnected systems. He doesn't write code. He directs the team that does, with the same rigor a PM brings to any engineering team. The methodology was born from his refusal to accept that non-technical leaders can't ship production-grade software.
“Look where it starts. Look where it goes.”
Camus
Strategy & Research
Market analysis, competitive research, strategic planning. Camus is the thinking partner — the one who takes a hunch and returns with a framework. Named for the writer who insisted on seeing the world clearly, even when clarity is uncomfortable. Every strategic decision at Lodemark passes through Camus before it reaches the build phase.
“Handoff problems are engineering problems. We fix those.”
Hamilton
Engineering & Build
All code, all architecture, all deployment. Hamilton writes every line that ships. Named for Margaret Hamilton — the engineer whose philosophy of proactive robustness saved the Apollo missions. Hamilton doesn't just build what's asked. He builds what's needed, catches what's missed, and holds the quality line when momentum pushes for shortcuts.
How We Work
Matt leads. Camus plans. Hamilton builds. Matt bridges them — deciding what context crosses between systems, what gets built, and what gets killed.
This isn’t a solo act with AI tools bolted on. It’s a team with defined roles, accountability, and a methodology that makes the collaboration repeatable. Product management applied to AI teams — that’s the thesis, and everything we build proves it.
The methodology that makes it work is documented, tested, and teachable. That’s what the Playbook is.
The Mission
There are people with strong product instinct who can’t ship because they don’t have an engineering team. There are AI tools that can build anything but can’t decide what to build.
We connect those two things — and we teach others how to do it.
The methodology is the product. The tools accelerate it. The journey documents it.
We use “we” because Lodemark Systems is a team, not a solo act. Matt leads product. Camus handles strategy. Hamilton writes every line of code. Taking sole credit for collaborative work isn’t transparency — it’s habit.
Find the lode. Mark it for others.