# How Visma uses CodeRabbit

**24 learnings**: “Our devs created 24 learnings in the last 30 days.”

As published on [coderabbit.ai](https://www.coderabbit.ai/case-studies/how-visma-found-the-enhance-code-quality-and-streamline-reviews). Captured by usedby on 2026-10-06.

- Company: [Visma](https://www.usedby.ai/companies/visma.md)
- Tool: [CodeRabbit](https://www.usedby.ai/tools/coderabbit.md)
- Teams: R&D, Product development and research

## What the story says

Visma's R&D unit uses CodeRabbit to review pull requests on a large, 20-year-old ASP.NET ERP codebase. It flags bugs and edge cases that human reviewers miss and generates summaries and sequence diagrams that make changes easier to understand.

Summary written by usedby from the source page, in English. The figures are those of CodeRabbit and Visma, not ours.

> Since they implemented CodeRabbit, it has caught several critical bugs during Visma’s pull request stage, significantly reducing the number of incidents they have.

- **600**: “Human reviewers carefully examined their team’s 600 monthly pull requests (a process still central to their workflow).”
- **3 million**: “The application's central repository contains more than 3 million lines of mostly legacy code dating back to the early 2000s.”

> It's the edge scenarios that are usually difficult to catch. It's a good tool to get these edge scenarios.
>
> Seref Boyer, Chief Architect

## What usedby checked

We compared the story with its live page on 2026-10-06.

- Checked: the figure 24 learnings is printed word for word on the page, near the name of Visma.
- Checked: the passage quoted above is copied word for word from the page, near the name of Visma.
- Checked: each number in our summary is printed on the page.
- Checked: Visma uses CodeRabbit. Confirmed line. Latest check across sources: 2026-10-06.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/visma-coderabbit · How we check: https://www.usedby.ai/methodology