BonCode doesn’t just provide numbers around software quality, it provides clarity. We measure hundreds of metrics and roll them up into a single maintainability score. That score helps managers see where progress is being made and where risk lies, across their software portfolios.
People often see static code analysis as a tool for engineers, which is true, but it’s only half the story. When using aggregated data based on code analysis, (like BonCode’s maintainability score), this is where the benchmarking possibilities arise. The real value comes when organizations start comparing their own systems, teams, and technologies or even benchmark themselves against the wider industry.
Internal benchmarking: turning data into direction
Internal benchmarking is the idea of comparing software projects and software systems within your own organization. It is one of the most immediate and practical applications of BonCode’s data. Organizations can compare performance across teams, vendors, or even technologies. One public sector organization uses BonCode’s benchmarking data to guide investment decisions across dozens of projects.
“The client runs an internal benchmark with more than 25 software projects across four technologies. Using maintainability scores, they can see which systems are performing well, which need attention, and where to allocate budgets. Sometimes the older system is healthier than the newer one. And this kind of insight sparks non-political internal discussions, which lead to budget allocations or other management discussions that are supported across the whole organisation.”
– Jan Willem Klerkx, CEO, BonCode
From portfolio management to vendor oversight, benchmarking provides the facts leaders need to prioritize, justify, and defend critical software decisions. BonCode CCO Harm Garvelink adds that this kind of comparison extends beyond teams. “It’s not just which team or vendor is performing better,” he says. “It’s also about which technology stack performs better. Benchmarking lets clients make data-driven decisions about which technologies to use next.”
Benchmarking as a networking event
Benchmarking isn’t just about dashboards, it’s also about people. Every quarter, BonCode brings together a group of customers to share benchmarking data in a trusted environment.
“We position it as a networking event,” says Jan Willem. “Because the meeting takes place under the Chatham House rules, all participants can openly and confidently share their experiences.”
These sessions often evolve into vibrant user communities.“It’s knowledge sharing across peers,” adds Harm. “They discuss how they tackle challenges, what works, what doesn’t, even which vendors they prefer. It’s incredibly valuable.”
The power of positive peer pressure
One of the most surprising outcomes of these events, Jan Willem highlights, is a form of ‘positive peer pressure’. When customers meet every few months, they want to show improvement. If nothing’s changed, it’s a bit awkward. That gentle pressure encourages continuous improvement, and that’s good for everyone.
Benchmarking, in BonCode’s hands, becomes both a technical measure and a human motivator, turning data into dialogue, and dialogue into progress. Whether it’s evaluating legacy systems, choosing technologies, or guiding vendor management, BonCode’s benchmarking transforms abstract code metrics into business insight.
“No matter what,” Jan Willem reflects, “benchmarking is always useful. If you’re doing well, it’s something to be proud of. If you’re struggling, the data helps you convince other stakeholders that something needs to change. ”
To learn more about how benchmarking can bring clarity, confidence, and collaboration to your software strategy, follow BonCode on LinkedIn for insights and updates from the team.
