Work / Neverlook
Neverlook
Making autonomy understandable.
- Client
- Neverlook
- Project
- Brand architecture, positioning and digital customer journeys
- Year
- 2026
- Sector
- Financial automation, AI
- My role
- Brand architecture · Positioning · UX strategy
- Themes
- AI, Technology, Trust, Future systems
- Sheet
- 03

I helped turn autonomous invoice-processing technology into a product people could understand and trust, defining the brand architecture, category, positioning and digital customer journey for Neverlook and FabricAI within Visma.
01 System
A product built around confidence
Invoice processing sits inside a business’s financial routines. Introducing autonomy into that process makes trust central to the buying decision. Software partners need to understand how a product fits into their platform. Accounting firms need to understand how it changes daily work, what happens when an invoice needs attention and how performance can be assessed.
My task was to make the technology’s role clear across the brand and the customer experience.
02 Story
Giving the names a clear relationship
The architecture gave each name a job. Neverlook is the autonomous invoice-processing product for software partners. FabricAI is the company and technology behind it, with a continuing customer-facing role in accounting. Visma Solutions Oy is the owner and corporate home.
I helped define the category as autonomous invoice processing. That description established the scope of the product and gave the commercial story a consistent starting point. The message hierarchy then addressed the different priorities of software vendors and accounting firms.
Never Look Rate: the proportion of invoices processed with zero human handling or checking.
03 Society
Making the promise measurable
The strategy established Never Look Rate as the central proof metric: the proportion of invoices processed with zero human handling or checking. It translates a technical capability into an outcome customers can follow over time.
Trust also needed to be visible in the experience. The principles included demonstrations on customers’ own invoices, understandable pricing and outcomes, a full audit trail and clear exception handling. Confidence thresholds determine when the system can process an invoice automatically. When human attention is required, the exception comes with an explanation.
Never Look Rate, exception rate and human touches together provide a practical way to discuss performance and oversight.

04
Designing the path to adoption
My UX work covered customer journeys, website messaging, demonstrations, conversion paths, onboarding and performance visibility. The journey needed to answer a sequence of questions: what does this do, will it work for our situation, how do we introduce it, and how will we know it is delivering value?
The resulting framework connected the category promise to the evidence and experience needed to support adoption. It gave the product a clear name, a clear role and a clear way to demonstrate its value.

- My role
I defined the brand architecture, category, positioning and digital customer journey, including the UX strategy for messaging, demonstrations, conversion, onboarding and performance visibility.
- What we created
- Brand architecture
- Category definition
- Positioning and message hierarchy
- Proof metric: Never Look Rate
- Trust and oversight principles
- Customer journeys and UX strategy

