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
Publicly documented examples
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
Denmark · large life-sciences company
Denmark · foundry group
Denmark · tool sharpening
Denmark · digital bank
Norway · consumer technology
Global · Ingka Group
Detailed examples
Explore DI’s AI case archive External resource · checked 3 August 2026
NovoScribe creates drafts of clinical study reports. The sources describe a highly regulated documentation workflow where expert review and approval remain necessary.
Clinical study reports can be extensive and require contributions from statisticians, scientists and technical writers across a long process.
NovoScribe combines generative AI, retrieval-augmented generation and domain-approved content. Anthropic and MongoDB describe it as a customer example.
MongoDB says NovoScribe handled around 30% of reports at the time, with an expectation of more than 90% by year-end.
A bounded, document-heavy workflow can change substantially when data, review and accountability are part of the solution.
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.
Vald. Birn uses machine learning to generate price drafts. People retain the final commercial decision.
Manual price calculation for enquiries took time and needed to be performed consistently.
The company implemented a machine-learning price-calculation algorithm using historical calculations to suggest a price draft.
The AI result is a price draft. Structured historical data can speed preparation while people retain final commercial judgement.
DI reports the company’s own information and does not provide total financial effect or an error distribution beyond the stated hit rate.
The solution is an AI-supported search solution integrated with the company’s ERP system - not an ordinary chatbot.
Employees needed to find information in complex ERP data, and some enquiries took around 20 minutes to answer.
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.
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.
ERP data becomes useful in an AI solution when users can find, understand and amend relevant information in their own workflow.
The industry case archive contains company statements, not comparable ROI or long-term impact evidence.
This is an implementation and ambitions case. It primarily documents launch status and an intended operating model, rather than a realised result.
Customer service needed availability outside regular hours and a way to handle both simple and more complex questions.
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.
An agent launch can start as a controlled beta. Availability, escalation and accountability should be described before impact is assessed.
75% is a company expectation. The hiring and no-job-cuts statement is a dated 2024 observation, not a timeless outcome.
reMarkable launched Mark as an AI customer-service agent and Saga for internal IT support. The numbers below come from Salesforce customer stories.
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.
Mark uses a structured Salesforce knowledge base for service and can hand a human the conversation history, related articles and attempted solutions.
An agent depends on a knowledge base that can be found and used. Feedback loops and human handover are operational requirements.
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.
Ingka Group describes how its Billie chatbot and remote-selling capability development form part of one customer-service channel.
Customer service needed availability across time zones while co-workers needed more time for higher-value conversations.
Billie handles simpler enquiries around the clock. Ingka says co-workers were reskilled in remote interior design, digital retail sales and related work.
Ingka wrote that it aimed to grow remote selling’s total-sales share to 10% in the following years.
Automation and capability development can belong to the same operating model. The human role moves toward complex problem-solving and advice.
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.