Publicly documented examples

Six Nordic examples of AI in practice

From machine learning and knowledge search to generative AI and customer-service agents. See what the companies built, which results they report themselves, and what others can learn from them.

Comparison overview

Six different workflows

  1. Denmark · large life-sciences company

    Novo Nordisk

    Workflow
    Clinical study reports
    AI type
    Generative AI with RAG
    Result
    About 12 weeks to about 10 minutes
    Company-reported result
  2. Denmark · foundry group

    Vald. Birn

    Workflow
    Price calculation
    AI type
    Machine learning
    Result
    Nearly 90% less time
    Company-reported result
  3. Denmark · tool sharpening

    TN Værktøjsslibning

    Workflow
    Finding technical information
    AI type
    AI-supported ERP search
    Result
    About 20 minutes to about 20 seconds
    Company-reported result
  4. Denmark · digital bank

    Lunar

    Workflow
    Customer-service calls
    AI type
    GenAI voice assistant
    Status
    Beta for selected customers
    Goal or expectation
  5. Norway · consumer technology

    reMarkable

    Workflow
    Support cases and IT help
    AI type
    Customer-service agent
    Result
    37% of support cases resolved autonomously
    Vendor source
  6. Global · Ingka Group

    IKEA / Ingka Group

    Workflow
    Remote customer service
    AI type
    Chatbot and remote selling
    Result
    About 47% of enquiries
    Documented result

Detailed examples

Read the sources in context

Explore DI’s AI case archive External resource · checked 3 August 2026

01Novo NordiskDenmark · generative AI and RAG12 weeks → 10 minutes Company-reported

NovoScribe creates drafts of clinical study reports. The sources describe a highly regulated documentation workflow where expert review and approval remain necessary.

Challenge

Clinical study reports can be extensive and require contributions from statisticians, scientists and technical writers across a long process.

Solution

NovoScribe combines generative AI, retrieval-augmented generation and domain-approved content. Anthropic and MongoDB describe it as a customer example.

Company-reported results

  • MongoDB reports a clinical study report moving from around 12 weeks to around 10 minutes.
  • Anthropic reports 90% less report-writing time. This is separate from end-to-end cycle time.

Goals and expectations

MongoDB says NovoScribe handled around 30% of reports at the time, with an expectation of more than 90% by year-end.

What this shows

A bounded, document-heavy workflow can change substantially when data, review and accountability are part of the solution.

Documentation limitations

The 50-to-three writers and redeployment information comes from a secondary article. It is not used here as a primary documented result. We also exclude an annual-AI-spend comparison with a writer’s salary.

Sources

02Vald. BirnDenmark · machine-learning price calculationNearly 90% less time Company-reported

Vald. Birn uses machine learning to generate price drafts. People retain the final commercial decision.

Challenge

Manual price calculation for enquiries took time and needed to be performed consistently.

Solution

The company implemented a machine-learning price-calculation algorithm using historical calculations to suggest a price draft.

Company-reported results

  • Time per calculation fell by nearly 90%.
  • Testing found a hit rate of at least 90%, meaning the model price often matched the company’s own calculation.
  • At source time, it generated price drafts for around 20% of enquiries.

What this shows

The AI result is a price draft. Structured historical data can speed preparation while people retain final commercial judgement.

Documentation limitations

DI reports the company’s own information and does not provide total financial effect or an error distribution beyond the stated hit rate.

Sources

03TN VærktøjsslibningDenmark · AI-supported ERP search20 minutes → 20 seconds Company-reported

The solution is an AI-supported search solution integrated with the company’s ERP system - not an ordinary chatbot.

Challenge

Employees needed to find information in complex ERP data, and some enquiries took around 20 minutes to answer.

Solution

The company put a user interface on top of an AI integration with its ERP system so relevant information became easier to find in day-to-day work.

Company-reported results

  • Response time is described as around 20 minutes to around 20 seconds.
  • DI quotes that a first workable solution was built in around one and a half months.

Goals and expectations

DI reports an expectation that employees can be trained in around three months rather than up to two years. This is not a measured result.

What this shows

ERP data becomes useful in an AI solution when users can find, understand and amend relevant information in their own workflow.

Documentation limitations

The industry case archive contains company statements, not comparable ROI or long-term impact evidence.

Sources

04LunarDenmark · GenAI voice assistantBeta and 75% ambition Goal or expectation

This is an implementation and ambitions case. It primarily documents launch status and an intended operating model, rather than a realised result.

Challenge

Customer service needed availability outside regular hours and a way to handle both simple and more complex questions.

Solution

Lunar launched a GenAI voice assistant in beta for selected customers to collect feedback and refine the service. 24/7 availability and human handover are designed properties.

Status and goals

  • Lunar positioned the launch itself as “a first in European banking”.
  • Lunar expected the assistant to handle around 75% of customer calls over time. It was not a measured result at source time.
  • Tech.eu wrote on 24 October 2024 that Lunar was not hiring as fast after introduction, without job cuts at that time.

What this shows

An agent launch can start as a controlled beta. Availability, escalation and accountability should be described before impact is assessed.

Documentation limitations

75% is a company expectation. The hiring and no-job-cuts statement is a dated 2024 observation, not a timeless outcome.

Sources

05reMarkableNorway · customer-service agent37% autonomously resolved Vendor source

reMarkable launched Mark as an AI customer-service agent and Saga for internal IT support. The numbers below come from Salesforce customer stories.

Challenge

Support needed to meet growing needs. Knowledge-base articles were long and lacked summaries and metadata that made information easier for the agent to find.

Solution

Mark uses a structured Salesforce knowledge base for service and can hand a human the conversation history, related articles and attempted solutions.

Company-reported results

  • 37% of support cases resolved autonomously.
  • 32,000 customer conversations since launch.
  • 21% of customers voluntarily chose Mark over a human.
  • NPS on par with human agents.

What this shows

An agent depends on a knowledge base that can be found and used. Feedback loops and human handover are operational requirements.

Documentation limitations

Salesforce is the vendor and publisher of both customer stories. We exclude a comparison with 20% of a 115-person support team because it is not documented in the cited sources.

Sources

06IKEA / Ingka GroupGlobal · chatbot and remote sellingAbout 47% of enquiries Documented

Ingka Group describes how its Billie chatbot and remote-selling capability development form part of one customer-service channel.

Challenge

Customer service needed availability across time zones while co-workers needed more time for higher-value conversations.

Solution

Billie handles simpler enquiries around the clock. Ingka says co-workers were reskilled in remote interior design, digital retail sales and related work.

Documented results

  • From 2021 to 2023, Billie resolved around 47% of customer enquiries received.
  • Ingka says this equals 3.2 million resolved interactions and nearly EUR 13 million in savings.
  • 8,500 call-centre co-workers were reskilled.
  • Sales through all Ingka remote customer meeting points reached EUR 1.3 billion at FY22 end.

Goals and expectations

Ingka wrote that it aimed to grow remote selling’s total-sales share to 10% in the following years.

What this shows

Automation and capability development can belong to the same operating model. The human role moves toward complex problem-solving and advice.

Documentation limitations

EUR 1.3 billion is revenue for the entire remote-selling channel, not revenue attributable to the chatbot. We exclude 57%, an absolute “without layoffs” claim and a remaining-53%-analysis story because the cited primary source does not document them.

Sources