Visma’s strategy, often dubbed the “house of brands,” leveraged the trust inherent in local providers. A Finnish accountant would rather use a product named “Procountor” (a Visma acquisition) than a generic European brand. This allowed Visma to dominate market share rapidly. However, this came at a cost: technical debt. Integrating dozens of legacy codebases into a single cloud ecosystem (Visma Sky) has been a Herculean, decade-long task.
The watershed moment arrived with the EU’s Open Banking directives (PSD2) and the forced shift to cloud compliance. Visma’s fragmented model initially struggled with API standardization—getting a payroll app in Oslo to talk to an inventory app in Copenhagen was a nightmare. Horizon, with its monolithic cloud architecture, sailed through this transition, offering bank feeds and automated reconciliation years ahead of its rival. horizon visma
The true battleground was not the software, but the accountant. Visma understood that in Europe, the accountant is the ultimate decision-maker for SME software. By acquiring accounting firms themselves (a controversial move), Visma locked in users. Horizon, sticking to a pure software vendor model, relied on partner channels. During the COVID-19 pandemic, when governments needed rapid payroll loan processing, Visma’s owned accounting firms could pivot overnight. Horizon, reliant on independent partners, suffered a two-month lag. Visma’s strategy, often dubbed the “house of brands,”