EnterIT Book a call ENCZDEPL
Back to the overview Case studies

Three systems, described to the depth a buyer actually needs.

Scope, architecture, the human approval points and the measured outcome — for one engagement from each kind of work we do. Clients are described by type; the named reference comes to the meeting.

Manufacturing · Energy · Investment management

Discuss a similar system
01
Manufacturing group · Manufacturing · ~600 people

One governed data and agent layer over Business Central.

Orders, supplier documents, warehouse movements and production data lived in Business Central and around it — in mailboxes, spreadsheets and people's heads. Every report and every daily lookup started with someone reassembling the same numbers, and no two departments were sure they were looking at the same ones.

What we built
  • A governed data layer that reads from Business Central, validates against it and writes back safely — one set of numbers under everything.
  • Document intake: incoming orders and supplier paperwork are extracted and matched to ERP records instead of being retyped.
  • An agent layer on top for lookups, checks and reporting, working from the same governed data as the people do.
Measured outcome

Specific figures for this engagement are under NDA. We bring the measured numbers, and the reference behind them, to the meeting.

Status: In production, operated under SLA.

A document open beside the ERP record it has to reach, on one screen. How it runs Writes into the ERP go through validation and defined approval points; every change lands in an audit trail. The people who owned the process still own it — the reassembly work is what disappeared.
02
Energy group · Energy services

87% faster response to new inquiries, around the clock.

New inquiries arrived by chat, email and web forms into a team working business hours. Response times stretched with the queue, and the first qualified conversation often happened days after the first contact — long enough for a prospect to keep shopping.

What we built
  • One agent across chat, email and forms, answering from the company's own product database — with the source attached.
  • Qualification built into the conversation: the agent gathers what sales actually needs before a meeting is worth booking.
  • Calendar integration: a qualified inquiry leaves with a booked meeting, not a promise of a callback.
Measured outcome

Status: In production.

87%faster response to a new inquiry24/7coverage without growing the team+35%qualified meetings booked
Someone from the support team at a customer service portal, headset on. How it runs The agent answers what the product data supports and hands anything else to a person, with the full conversation attached. Sensitive commitments stay human.
03
Investment group · Finance · 100+ portfolio companies

Portfolio intelligence over a hundred-plus companies.

Monthly reporting from more than a hundred portfolio companies arrived in a hundred formats. The analyst team spent its capacity collecting and normalizing instead of analyzing, and questions across the portfolio took days to answer.

What we built
  • Automated intake and normalization of portfolio reporting into one queryable base.
  • Agentic analysis on top: cross-portfolio questions answered in minutes, with the underlying figures traceable.
  • Autonomous monitoring that flags deviations instead of waiting for someone to look.
Measured outcome

Status: In production, scaling.

10×analyst team productivity100+companies under one analytical layer
Analysts and clients around one table, the figures on a laptop between them. How it runs Analysts direct the questions and own the conclusions; the agent does the collecting, normalizing and first-pass analysis they used to lose their week to.
04
Case studies

Discuss a similar system