The tool that should have existed.
Built by someone who got tired of waiting.
Solo founder. Deep background leading engineering teams at enterprise scale. Bootstrapping while working full-time — because the problem is real and the tool didn't exist.
I started in the early days of the web — various startups before going back to get my degree in commercial software development. From there I moved into building and coaching engineering teams in the US, and spent the last several years leading Agile Centres of Excellence at large financial services organizations — the kind of role where you're responsible for how hundreds of engineering teams work, not just whether they ship. The 50 protocols aren't theoretical. They're the things that actually separate high-performing teams from ones that look fine until something goes wrong.
Then AI arrived. And the question got urgent.
AI coding tools didn't create the gap between velocity and practice — they just made it impossible to ignore.
Faster development doesn't fix weak practices — it amplifies whatever's already there. The existing tools weren't built for this moment. Compliance platforms check controls. Engineering metrics platforms track delivery speed. Nobody is observing whether the underlying practices are keeping pace. That's the gap Concordance was built to close.