The Challenge
Scaling delivery without losing visibility
Bokio is a fast-growing fintech, part of the Visma portfolio, building accounting and bookkeeping software for small businesses across Europe. As the engineering organisation scaled and teams restructured, leadership faced a challenge familiar to any high-growth company: delivery output was high, but the ability to see and manage that delivery was falling behind.
Before Plandek, Bokioβs engineering managers had no consistent, data-backed way to answer the questions that mattered most: Are we delivering value or fighting fires? Where are the real bottlenecks? How do we prove what weβre achieving to the board?
The team was under increasing pressure from the top. As Niklas Lundborg, CTO, put it: βThereβs a tremendous amount of pressure on the product teams to think in terms of customer value β and learning that they have both limited time and limited scope.β Against that backdrop, gut feel wasnβt enough.
The Solution
Data-driven delivery across a Kanban engineering organisation
Plandek was introduced to give Bokio a single, consistent source of truth across all engineering teams β connecting their Azure DevOps data to a framework built around four pillars: Focus, Speed, Predictability, and Quality.
Because the majority of Bokioβs teams operate in Kanban rather than Scrum, the engagement was shaped accordingly. Sprint-based metrics were deprioritised in favour of flow-based ones β cycle time, lead time, time to merge PRs, and a throughput quotient that accounts for team size. This gave engineering managers a view that reflected how their teams actually work.
Plandek also introduced Bokio to its industry benchmarking data, drawn from 2,500+ teams, allowing leadership to see their metrics in context β not just against their own history, but against the wider engineering industry.
The Outcome
Measurable improvement across speed and quality
The results across Bokioβs performance tell a clear story of continuous improvement.
Quality has transformed dramatically. Bug resolution time fell to 2.9 days by Q4 2025 and into Q1 2026 β placing Bokio among the fastest in Plandekβs entire customer base.
Speed signals are strong. Cycle time has remained consistently in the top quartile at around 5 days, and lead time to value sits at approximately 14 days β well ahead of the industry median. Throughput quotient is firmly in the upper mid to top quartile, showing that Bokioβs engineers arenβt just fast, theyβre productive.
PR review processes have improved noticeably. Time to merge PRs improved from 40 hours in Q1 to 27 hours by Q3, driven by genuine gains across all three stages of the PR lifecycle: time to review, time to approve, and time to merge.
One area in active focus is deployment cadence. Plandekβs data surfaced that time to deploy had ballooned as Bokioβs manual release bundling became a constraint β a finding that immediately sparked the internal conversation about moving to continuous deployment. As Niklas reflected: βThis is so not modern from an engineering point of view. But this is room to improve, and we have good actions.β
Key outcomes at a glance
Bug resolution time reduced to 2.9 days β top quartile across 2,500+ teams
Cycle time consistently in the top quartile at ~5 days
Time to merge PRs improved by 33% from Q1 to Q3
Throughput quotient in the upper mid to top quartile
AI analytics deployed to measure real productivity impact of AI tooling
The Future
AI impact and the Visma opportunity
With a strong delivery foundation in place, Bokio is now using Plandek to tackle its next frontier: understanding the real impact of AI-assisted development.
As the team accelerates adoption of GitHub Copilot and agentic coding tools β with some engineers running multiple agents simultaneously β Plandek is being used to answer a critical question: is AI actually making them faster and maintaining quality? Using Plandekβs AI analytics, Bokio can now track PR contributions by AI agents, compare time-to-merge for AI-authored versus human-authored code, and monitor whether increased velocity is coming at the cost of escaped defects.
This matters at a strategic level. As Niklas explained: βOne of our long-term goals is that every single developer is able to deliver a significant update each week with the help of AI. But we need to understand what a significant update means, and how we measure whether it positively impacts Bokio.β
Plandek is also being extended to include product managers β connecting ticket hygiene, epic tracking, and delivery data to business outcomes in a way that closes the loop between engineering effort and commercial value.
As a Visma portfolio company, Bokioβs journey with Plandek represents a broader opportunity. The ability to benchmark engineering performance across portfolio companies, establish a consistent data language for delivery, and demonstrate R&D return to group leadership makes Plandek a natural fit for Vismaβs wider engineering excellence agenda.
See how your engineering efforts translate into measurable business impact
Measure delivery performance, AI impact, and engineering productivity with hundreds of metrics, OOTB dashboards and custom configurations.
Contact us
π¬π§
πΊπΈ
ο
UK Office
Unit 313 The Print Rooms, 164-180
Union St, London SE1 0LH
ο
US Office
Floor 4, 1515 Mockingbird Ln,
Charlotte, NC 28209, USA