To understand the dichotomy, one must look at the founders’ DNA. Visma, founded in Norway in 1996, grew from a traditional consulting firm into a private equity darling. Its modus operandi was simple yet ruthless: acquire hundreds of local accounting and payroll firms, standardize their backends, but retain their local branding. Horizon, on the other hand, emerged from the Dutch software scene, focusing on building a unified ERP (Enterprise Resource Planning) suite that could scale from the sole trader to the mid-market. Where Visma saw fragmentation as a feature, Horizon saw it as a bug.
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. horizon visma
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. To understand the dichotomy, one must look at