Horizon Visma Online
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.
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
Yet, Visma had a secret weapon: private equity. Backed by Hg and later CVC Capital, Visma could outspend Horizon on R&D and acquisitions. When Horizon faltered in mobile user experience, Visma bought the best mobile-first startup in the region. When Horizon struggled with e-invoicing standards, Visma simply acquired the company that wrote the standard. The watershed moment arrived with the EU’s Open
For the student of business strategy, the Horizon-Visma dynamic teaches a painful lesson: In European SaaS, perfect software loses to perfect distribution. Visma’s messy, human-centric, acquisition-led empire has not only survived but thrived, proving that in the Nordic SaaS wars, the pen (and the local accountant) is mightier than the algorithm. Visma’s strategy, often dubbed the “house of brands,”
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.
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.
Today, the lines have blurred. Horizon has been largely subsumed into broader groups (with parts sold to Visma’s allies), while Visma has finally unified its core data model under “Visma.net.” The essay’s verdict is this: Horizon won the product war—its architecture was cleaner, its APIs more robust. But Visma won the market war—its understanding of local trust, distribution, and financial engineering proved unbeatable.
