Evidence before theater
Stephan cares less about AI demos that look clever and more about whether a team can explain what happened after the run is over.
CEO · Kommit
Stephan
Moerman
CEO of Kommit and an experienced CTO with 10+ years of experience building software products and scaling technical teams.
Operator lens
Former CTO
Experience
10+ years
Domains
SaaS · healthcare · fintech
Why Kommit
Fast output is not the same as accountable work.
Stephan has spent more than a decade working as a CTO and engineering leader across SaaS, healthcare, fintech, and other regulated environments. The recurring challenge was rarely whether a team could build something. It was whether the organization could operate it responsibly once real systems, policies, and people were involved.
Kommit comes from that operating reality. As AI agents take on more consequential work, teams need clear ownership, enforceable boundaries, human review, and an evidence trail that survives beyond the pilot. Stephan is building Kommit to make those controls part of the work itself.
How he works
Builder first, governance by design.
Controls inside the work
Kommit is shaped around approvals, boundaries, ownership, and logs living where the agentic work happens, not in a separate compliance afterthought.
Senior engineering judgment
His CTO background shows up in the product: clear systems, practical trade-offs, and a bias for software teams can actually operate.
Current focus
Making autonomous AI legible to the people who carry the responsibility.
That means giving founders, engineering leaders, compliance teams, and finance a shared record of what agents did, why they were allowed to do it, and where a human took responsibility.