Background & Opportunity
Roaring began with a problem that appears simple but becomes difficult at scale: organizations need trustworthy information about businesses and individuals, yet the relevant data is dispersed across official and commercial sources. Founded in 2016, the company set out to collect, enrich and make that information immediately available to customers. Its initial answer was an API platform. Through APIs, customers could connect verified data to their own systems and use it in customer onboarding, supplier review, compliance checks and related processes. That architecture addressed the needs of technically capable buyers. Banks, financial institutions, enterprises and public-sector organizations could integrate data into existing workflows rather than manually search and re-enter information. Roaring’s developer documentation describes more than 65 APIs and Webhooks, covering business and personal data, with sandbox testing, OAuth authentication and production integration. These capabilities show a substantive delivery infrastructure rather than a simple database interface. Yet an API-first model also creates adoption friction. A customer has to understand the endpoints, assign technical resources, test the connection and complete integration before many operational users can benefit. For a compliance or operations team, the immediate question may not be how to build an integration. It may be whether a person or supplier can be checked now, whether information has changed, or whether a review can be documented consistently. A platform can be technically strong and still be slower to activate for users who do not control development resources. Roaring’s own history identifies this gap as the important transition. In 2023, after customer needs changed, the company developed a product that had originally showcased its API platform into Lookup, an application usable without integration. This was not a retreat from the API business. It was a packaging decision. APIs remained available for embedded, automated workflows, while Lookup gave customers a direct path to value. The company could therefore address technical buyers and users whose priority was immediate access to verified information. The new proposition became broader than “access our API.” Roaring positioned APIs, Lookup, data monitoring and reporting around high-value workflows: KYC, AML, customer and supplier due diligence, risk assessment, compliance and fraud prevention. Each element contributes a different form of usefulness. Lookup can support a direct check. APIs and Webhooks can connect checks to production systems. Monitoring can identify changes over time. Reports can help organize information for review and evidence. The combination makes the product easier to explain in business terms. This matters because compliance demand is recurring. A customer or supplier may need to be checked at onboarding and reviewed again later. A bank or public-sector organization may need processes that are consistent across many cases. A company may want to reduce manual entry while preserving access to the underlying information. A ready-to-use application can lower the first-use barrier; a deeper integration can follow when the workflow proves valuable. The product can thus support a staged adoption path without requiring every buyer to begin with a development project. The company reports commercial evidence consistent with this direction. Revenue rose from SEK 19 million in 2022 to approximately SEK 56 million in 2025, roughly 2.95 times higher, with an average annual growth rate above 43 percent. Roaring also reports that employees increased from 17 to 40, approximately 135 percent, and says the company remains profitable. These figures indicate substantial expansion by the company’s disclosed account. They do not, however, independently isolate the effect of Lookup from other factors such as market demand, customer mix, product development or sales execution. The numbers also require measurement discipline. Allabolag lists approximately SEK 55.987 million in revenue for Roaring Group AB’s accounting year from July 1, 2024 to June 30, 2025, with 30 employees. Roaring’s public announcement presents approximately SEK 56 million as 2025 revenue and reports 40 employees. The revenue amounts are close, but the accounting period and employee measure differ. They should therefore not be treated as identical indicators or combined as if they used one definition. Roaring says its customers and markets include banks, companies and public-sector organizations. These segments value reliable identity, company and risk-related information, but they also impose demanding requirements. Procurement may be slow. Security, data rights, accuracy and continuity may be examined before production deployment. Source-provider relationships may affect coverage and economics. Larger customers may have negotiating power, while customers may compare Roaring with internal development, other API providers or alternative data sources. The customer evidence is encouraging but limited. Roaring’s SPP case says the customer-start process moved from days to minutes and became fully digital after using Roaring. That statement illustrates the kind of operational result the combined proposition seeks. It is a customer testimony, however, and the public material does not disclose an independent measurement method, sample size, baseline population or verification process. The claim should therefore be used as directional evidence rather than as a universally proven performance metric. The strongest strategic insight is that Roaring changed the unit of value it presented to the market. An API is a capability. A Lookup application is a usable task. Monitoring and reporting are continuing controls. When the capability is connected to KYC, AML, due diligence and fraud prevention, the customer can evaluate it against an important business outcome rather than against technical specifications alone. This can broaden the conversation from developers to compliance, risk, operations and procurement stakeholders. The choice also protects optionality. Keeping APIs and Webhooks means customers that require embedded automation do not have to move to a simpler product. Adding Lookup means organizations can begin without integration. If a direct-use workflow becomes important, the customer may later require API connectivity, monitoring or reports. The fact sheet does not provide conversion data, so this should be understood as a strategic mechanism, not a verified funnel result. Still, it explains why the combination can be more resilient than either an API-only or application-only offer. The January 2026 financing announcement reinforces the direction. Existing shareholders invested SEK 20 million to continue developing the platform, strengthen proprietary analytical capabilities and expand solutions already used by banks, companies and public-sector organizations. Roaring also stated that it would not chase short-term AI hype. The financing is not proof of future growth, but its stated use is consistent with investing in the core data and analysis capability rather than abandoning it for an unrelated narrative. Roaring’s growth story should therefore be framed with both confidence and restraint. The company reports a strong increase in revenue and employees, a wider product surface and customer use across regulated markets. Its transition from an API-platform showcase to Lookup appears to have reduced adoption friction and made the data capability relevant to more workflows. The evidence supports management’s strategic interpretation, but most public evidence comes from Roaring itself. Independent validation would need to examine source access, licensing, data quality, retention, customer economics, procurement time, switching costs and the contribution of each product. The case ultimately demonstrates how infrastructure businesses can move closer to the user without discarding their technical foundation. Roaring did not choose between APIs and applications. It made both available, then connected them to monitoring, reporting and risk-management jobs. For regulated customers, that packaging can make a complex data service easier to adopt, explain and extend. The reported outcome is success, but the durable lesson is the design of multiple paths from data capability to operational value.
Original Problem / Model
Roaring’s original API proposition solved access for technical customers, but integration could delay value for compliance and operations teams. In 2023, the company responded by turning an API-platform showcase into Lookup, a ready-to-use application. The strategic insight was not that APIs had failed. It was that different users needed different starting points. Lookup could support an immediate check, while APIs and Webhooks remained available for embedded automation. This reduced the distance between a customer’s information problem and a usable answer without discarding the underlying infrastructure. The change also addressed a practical sequencing problem. A compliance user could begin with a direct search rather than waiting for development resources, testing and production integration. If the workflow later required scale or automation, the same customer could use APIs and Webhooks. Roaring’s broader positioning connected these access paths to KYC, AML, customer and supplier due diligence, risk assessment, monitoring, reporting and fraud prevention. The fact sheet does not provide conversion data, so this is a strategic adoption mechanism, not proof of a measured funnel or causal revenue effect.
Turning Point
The repositioning focused on workflows where information has direct regulatory and operational importance: KYC, AML, customer and supplier due diligence, risk assessment, compliance and fraud prevention. These use cases give the product a business context stronger than a generic data-access message. Monitoring and reporting extended the proposition from a single lookup to continuing oversight. The fact sheet supports this positioning, but does not independently quantify how much revenue came from any individual workflow or product.
Core Decision
The evidence is positive but qualified. Roaring reports revenue increasing from SEK 19 million in 2022 to approximately SEK 56 million in 2025, while employees rose from 17 to 40. It also reports continued profitability. Allabolag shows a similar revenue level for a different accounting period and 30 employees, so the measures require careful comparison rather than direct merging.
Execution / Model / Acquisition Changes
The product combination creates several adoption paths. A user can begin with Lookup without integration, while a technical team can use more than 65 APIs and Webhooks with sandbox testing, OAuth and production integration. Monitoring and reporting can support recurring review. This architecture is particularly relevant where organizations must check customers or suppliers repeatedly, document decisions and manage change. Roaring’s SPP case, which describes a shift from days to minutes and full digitization, illustrates the intended operational benefit, although it is a customer testimony without disclosed independent measurement. The combination also lets Roaring address different buying and deployment constraints. Lookup can demonstrate value to compliance or operations teams before a technical project is approved, while APIs and Webhooks can connect verified information to onboarding or review systems. Monitoring and reporting are relevant when customers must revisit records, identify changes and retain evidence. This supports a staged path from direct use to embedded automation, but the fact sheet does not report conversion rates, retention, or revenue by product. SPP’s days-to-minutes claim remains customer testimony rather than independent proof.
Measurable Results
Execution depends on more than product packaging. Roaring must maintain access to official and commercial data sources, protect data quality and operate within relevant permissions. Banks and public-sector organizations may have long purchasing processes and demanding requirements. Internal development, competing APIs and alternative providers can substitute for the service. Customers and source providers may hold bargaining power. The fact sheet identifies these issues as areas requiring further verification, so the revenue and employee figures should be read as company-reported outcomes, not as complete proof of durable advantage. These constraints matter because a data platform’s commercial promise depends on coverage, accuracy and lawful use, not only interface convenience. The company must also balance product investment with procurement cycles that may delay deployment. Competitors include internal builds, alternative APIs and other data providers, while large customers and source providers may negotiate from stronger positions. Revenue growth and employee growth are therefore encouraging indicators, but they do not establish retention, margins, source durability, switching costs or a lasting competitive advantage.
Lessons
The January 2026 announcement of a SEK 20 million investment from existing shareholders points toward continued platform and proprietary-analysis development. Roaring says the capital will support solutions used by banks, companies and public-sector organizations and that it will not chase short-term AI hype. The broader lesson is practical: retain infrastructure depth, but package it around urgent user workflows. Roaring’s reported growth suggests that this combination can widen access, while independent validation remains necessary for causal claims.