How Ida Infront Is Taking a Whole Engineering Organization Agentic

Ida Infront builds secure communication systems, case management tools, and digital archiving solutions for Swedish and Nordic government authorities. The company was established in 1984, and the platform underlying everything they build is over 25 years old.

For a company like IDA Infront, with a long product history and public sector customers, compliance concerns, risk analysis, and legacy infrastructure can limit AI experimentation. CTO Magnus Grimsell recognized the risk that a younger competitor might erode their platform value by building faster and cheaper. But he's driving the team to move early:

“We want to address that risk and take advantage of the opportunity by being early adopters.”

Ida Infront has an ambitious goal: double development speed by the end of the year. You don’t get there through random experimentation.

After evaluating several AI coding assistants and agentic tools, Ida Infront standardized on Kilo Code and built a structured onboarding program. Magnus had watched peer companies leave adoption to chance—telling developers to use whatever AI tools they wanted, then waiting—and seeing nothing happen.

Ida Infront did the opposite: one tool, organizational commitment, and a three-workshop program to bring every team through the transition together. The first workshop covers agentic engineering fundamentals, the second addresses issues that the teams run into in practice, and the third is non-technical: exploring the phases of Ida Infront’s AI adoption framework and the team’s feelings about where they are on that journey, their concerns and expectations. There’s a structured exercise for surfacing fears and hopes that allows team members to feel heard and work through any resistance.

Early adopter teams are trained to coach the teams that follow. The program was built in close collaboration with Kilo:

“We didn’t just receive support for the product, but expertise that I’ve valued as well. It’s great to have somebody come in and say, ‘This is how we do agentic engineering.’”

Ida Infront is still in the early stages of adoption, but early indicators are promising. Developers who had already been using a coding assistant expected incremental improvement with Kilo. “With an assistant, you’re working the same way as before, just a little faster,” Magnus says. “With agents, the developer role itself starts to change.”

Now, having seen Kilo in action, teams are eager to get onboarded, and other companies in Ida Infront’s parent group are already looking to replicate the model. Magnus shared a sense of excitement and possibility:

“I’ve been through the shift from waterfall to agile. This is the same kind of shift. It affects everything. And I’d rather be shaping what that looks like than waiting to find out.”