Cases
From manufacturing to finance and the public sector,actually used DARVIS
Profit analysis traced causes through to a report. Document retrieval was tested on 109 practical questions.
See how each workplace problem was addressed in the actual PoC case studies.
- 118Analyses closed, of 161 runs · 0 failed
- 4~6weeksTime to first rollout
- 5stagesSignal → evidence
Selected cases
Published adoption cases
Profit-variance analysis · PoC
Margins fell.Still gathering data to find out why?
Instead of assembling data across teams again, trace profit changes down to individual components. Ask follow-up questions in the same flow and compile the analysis into a PDF. This workflow was validated in a food-manufacturing PoC.
See how the ontology connects causes →
The totals were profitable; order by order, some were sold at a loss
Only after rebuilding the orders one by one did the loss-making stretch surface — and the same held on direct cost alone, before any overhead allocation. Counts, shares and amounts are the customer’s data and are not disclosed.
See the DARVIS-P screenPlant capacity and centre days-of-stock in one view, with people approving each transfer
Across distribution centres, production allocation, inter-plant transfers and near-expiry ageing sit on one screen. It covers an allocation and transfer recommendation screen, a settings page (per-centre plant priority and capacity) and an STO integration — people review the recommendation and decide the next action.
See the DARVIS-I screen- Electronic components
Three AI agents taken through a full PoC
An internal chatbot, DB sync automation and equipment-name validation — three problems solved the same way.
Read the full Company I case - System semiconductor
Validated in two weeks against 109 real questions
The PoC achieved 93.58% document-retrieval accuracy on practical workplace questions.
Read the full Semiconductor manufacturer case One question across the documents of a $700M-revenue maker
Documents scattered across internal systems, verified in three stages and pulled into one answer.
Read the full Global parts manufacturer caseFrom instrument data to an audit-ready report
We tested whether qualification reports could be produced without passing through human hands.
Read the full Pharmaceutical manufacturer case- Automotive parts
Material planning verified in real time
Scattered systems joined behind one chatbot, with the data context unified.
Read the full Company W case From interpreting a forecast model to company-wide data
It started with making the model’s reasoning readable to people.
Read the full Shipping company case- Financial data
150 SQL users find metrics in plain language
A 1.5-month PoC confirmed Text-to-SQL, plain-language profile search, report automation and access control. Quantified gains are still being measured.
Read the full Company K case - Public administration
Shorter response times in administration
Repetitive administrative work absorbed by an AI chatbot, shortening response times.
Read the full Public agency case
The common procedure
Every case goes through the same five stages
Signal detection
Items that drift outside their usual range are flagged first, so we know where to look.
Read-only connection
ERP, MES and cost sheets connected read-only. No changes to your systems and no redeployment.
Recalculation per order
Cost rebuilt per order and per item — starting from individual records, not from totals.
Breaking down the contribution
Against last month, which factor pushed how much — broken out in money.
Evidence assembled
Every answer is delivered with the table and column it came from.
How this differs from other tools
Different from a BI tool
BI shows you the metric. Here, when the metric drifts outside its range we flag it first, then leave the contribution and evidence together.
Different from a systems integrator
An SI fixes your systems. Here nothing is touched — we only read, and analyse.
Different from doing it in Excel
What someone recalculated by hand every close now runs every month on the same basis.
Read each case figure with the scope and conditions in its linked public source. PoC observations and projected effects are not realised savings or ROI.