How We Vibe-Coded Analytics for Vibe-Coded Projects

Developers took the client’s messy requirements and the transcript of the first meeting — and built a working piece of the product live. Instead of a document, the client got something they could open, test, and “touch.” We seriously wondered: do small projects need analysts at all?

But the fast code was only an illusion of a finished solution: missing scenarios, overlooked constraints, and constant rework soon surfaced. Good news — the analyst was still needed, just in a different role.

We had to do more than speed up analysis: we had to reinvent it, first in discovery and then in the regular delivery phase, across small and large projects.

On large projects, we have already launched the second generation of analysis automation. The first proved that blunt-force automation accelerates not only work, but also AI slop. In this talk, I’ll explain how we fixed it, which agents we introduced, what we vibe-coded — and whether analysis caught up with and overtook development.