Horizon Visma Online

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 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. horizon visma

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. Visma’s strategy, often dubbed the “house of brands,”