Case study · kutty.ai on-premise ERP AI assistant
How an on-premise ERP AI assistant answers business questions from live ERP data
kutty.ai is our on-premise ERP AI assistant. It answers plain-English questions about live ERP data, sends every write-back through workflow approval, and runs on the client's own hardware.
Client profile
| ERP | On-premise ERP (vendor not named) |
| Deployment | On the client's own hardware, inside their network |
| Questions | Plain English, answered from live ERP data |
| Changes | Workflow approval on every write-back |
The client is not named on this page.
The challenge
The team needed answers from their ERP without waiting for reports, and without giving every user access to every screen. Any change to ERP data had to stay under the same approval controls as before.
Why on-premise
ERP data holds the most sensitive numbers a business has: prices, margins, customer balances and supplier terms. For this client, sending that data to an outside AI service was not acceptable.
kutty.ai was therefore deployed on the client's own hardware, inside their network. Questions, ERP data and answers stay on premises, and access follows the client's existing ERP roles.
Solution & architecture
kutty.ai sits next to the ERP as an AI layer. Nothing was migrated and the ERP remains the system of record.
- Direct ERP integration. A connector reads live ERP data with read-only access for answering questions.
- Plain-English questions. Users ask questions in their own words. kutty.ai turns them into ERP queries, checks the results and answers with the figures and source records.
- Workflow approval on every write-back. When a user asks for a change, kutty.ai prepares it and sends it to an approver. Nothing changes in the ERP until it is approved.
- Audit log. Every question, query, proposed change and approval is recorded.
- On-premise deployment. Runs on the client's own hardware inside their network.
- User question"Which customers are 60+ days overdue?"
- kutty.aiQueries the ERP on-premise and answers with sources.
- Workflow approvalAny write-back, such as a credit hold, waits for an approver.
- ERPApproved change posted and logged.
Timeline
From kickoff to go-live, in four steps.
Discover
Questions, users and approval rules agreed.
Connect
Read-only ERP connection on client hardware.
Pilot
First users asking real questions.
Roll out
Write-back with approval, more teams.
Results
What is already true.
Usage figures are published here once the client has confirmed them. Until then, these are the facts of the deployment.
FAQ
Common questions.
Is kutty.ai a product we can buy?
kutty.ai is our own on-premise ERP AI assistant. We deploy and configure it for clients as the foundation of the ERP Knowledge Agent.
Does kutty.ai need internet access?
It is designed to run inside your network on your own hardware. Whether any external service is used is decided with you during discovery.
Can kutty.ai change data in our ERP?
Only through workflow approval. It prepares the change, an approver accepts or rejects it, and every step is logged.
Which ERPs can kutty.ai connect to?
Any ERP we can reach through an API, database views or exports, including older on-premise systems.
Works with leading ERPs, CRMs and helpdesks — cloud, hybrid or on-premise.
ERPCRMHelpdeskEmail inboxDocument storageDatabases & data warehousesCloud, hybrid or on-premiseSee an AI agent running on your ERP data in 4–6 weeks.
Fixed scope · fixed price. Human approval on every write. We reply within 1 US business day.