How Frontline Made Exadel Colleague Part of Its Team How Frontline Made Exadel Colleague Part of Its Team

By the end of the first phase, Exadel Colleague ran across dozens of tickets on seven live repositories(at the beginning it was 2), and Frontline's engineers merged its work into production code.

To resolve a critical defect in the accounts payable module where payments were failing due to missing payee details, the issue was assigned to Exadel Colleague on a Friday afternoon. Within seven minutes, Colleague autonomously analyzed the codebase, implemented the fix, and generated a pull request. The reviewing engineer awarded the fix a 100% accuracy score and merged it directly into production.

Tests before implementation.

Frontline's team was already strong on implementation, and quality assurance was where releases waited. Colleague is built test-first: the testing agent writes the tests before any production code exists, and the programming agent implements against them and runs them on its own work. The tests are committed with the change, so they run again on every change after it.

‍

Manual procedures become agentic workflows.

Frontline's invoice testing ran as a manual Postman procedure that only one person could execute. Exadel Colleague turned it into a repeatable, consistent agentic workflow the whole team can run, and it lives with the code so it survives handovers.

‍

How it runs

The clearest pattern across the pilot was that output quality tracked one thing: how well the repository described itself. Where tickets and specification files matched the code as it stands, results were consistently strong. Where they described an architecture that a refactor had already replaced, Colleague inherited that drift.

Frontline's own engineers spotted it first:

Our ticket content had drifted from the work that had actually been done. A month ago we moved the consumer service out of a microservice repo into Dispatch, and the tickets never reflected that. Any other AI solution would have struggled with it, and it pushed us to tighten up how we document.
Frontline Engineer, ticket comment

That finding is worth more than the ticket count. Establishing repository context at onboarding was already how Colleague starts. What Frontline showed is that a single pass does not hold: the code and the business keep moving, and repository context has to move with them. The practice now is a recurring refresh that keeps context in step with both, plus a readiness check before any deployment.