Bilal Shahid

The longer version

AI wrote your app. Who read it?

I build with AI every day, and before AxonBuild I led an AI team shipping chatbots and fine-tuned models for paying clients. I still spend part of my week as fractional product owner on an AI-first hotel operations platform for a UK hospitality group. So when I open an AI-built repository expecting to find problems, it isn't cynicism. It's familiarity.

You should be suspicious of a man who sells audits and finds problems in every repo he opens. So here's the part that costs me money: I've told clients not to hire me, because their problem had a cheaper, simpler fix with no AI in it. I don't need your repo to have problems. So when I tell you something in your repo is broken, it's broken.

AxonBuild exists because of one afternoon. I let AI build an internal tool for us, and the demo was flawless. Then I read the repository. Sign-in could be faked from the browser. Some endpoints never checked who was calling them. My live API keys were sitting right there in the code, and the AI's next suggestion was to push everything to GitHub. It knew about the keys. It just didn't think they were worth mentioning.

Reading what actually got built has become nobody's job. So I made it mine. 26 codebases later, the pattern barely changes: the founder is sharp, the app works, and two or three problems nobody has read yet are sitting in the code, waiting for your worst week. I find them before your customers do, and I put the evidence in writing.