How IntraPhone Went From Legacy Code Bottleneck to Outrunning Its Own Roadmap

IntraPhone builds planning and care registration software for Sweden’s home care sector. Their platform is used by 80 of Sweden’s roughly 260 municipalities, making them one of the largest players in their market. They’ve written every line of code themselves for 20 years, with no consultants and no outsourcing. That gives them deep institutional knowledge of their codebase and the ability to move fast. It also means they’re carrying two decades of legacy.

After 20 years of continuous development, IntraPhone’s codebase had grown dense. Features accumulated, development slowed, and the team needed to find more velocity without starting from scratch. They’d attempted wholesale rewrites before, with limited success. What they needed was a way to work faster within the codebase they had.

The thornier challenge was that IntraPhone’s developers had encountered AI coding tools before and hadn’t been impressed. A year or even six months ago, those tools could be hit-and-miss, so it wasn’t unreasonable for the team to dismiss the idea based on their own real experience.

A directive wasn’t going to win them over, but a demonstration might.

Robert Lindgren has a long history at IntraPhone, holding roles across development, infrastructure, and customer-facing work, before settling into product ownership a decade ago. He decided to make the case for Kilo himself.

Working alone with approval from the CEO, he built a full proof of concept of a new IntraPhone system from scratch: new backend, web application, route optimization, and apps for both iOS and Android. He revealed it to the team just before Christmas.

The tech lead, initially the most skeptical, spent the holiday break quietly rewriting a companion product using Kilo. When the team returned in January, he was nearly done. That rewrite is now in production.

When Robert started using Kilo on IntraPhone’s legacy code, he expected friction. Instead, Kilo not only identified a bug correctly from a single support ticket, it went further, spotting an existing pattern in the codebase and offering to apply it to new code rather than introducing something new.

“It said, ‘I would have done it this way, but I see you’ve been using this method before, so I’ll apply that to the new code. Is that okay with you?’ That was the real eye-opener.”

The legacy code, instead of being a liability to work around, was context Kilo could actually use.

For Robert personally, the transformation went further than anyone expected. In a recent release cycle, he shipped seven features, including Android dark mode (getting to production quality in about four hours) and a persona-switching shortcut for super users. He has also used Kilo to generate a 14-page sales specification directly from the codebase, and two company websites built from Figma designs. He uses CodeScene as an MCP to quality-gate everything Kilo generates.

None of the seven features he contributed came back with review comments.

IntraPhone’s developers are now moving 5–10x faster than before. For Robert, the bigger change is what he’s doing with the time he’s recovered: prototyping ideas, acting on customer feedback before the moment passes, shipping things that would previously have sat on the backlog for months.

The team’s iOS app—attempted multiple times over the years, but never shipped—is on track to release before summer. A customer prototype rated 9.9 out of 10. Friday morning demos, introduced three weeks ago, have become a highlight of the week: every developer comes prepared with something to show.

The moment the shift really landed was when Robert realised IntraPhone had run out of tickets. Development was no longer holding anything back. Asked what it feels like to work this way now:

“I feel like Superman. It’s so much fun to fly around and find problems to solve.”