telecom
Telecom operator: local-model knowledge base, network health response, and tender automation
A telecom operator needed a knowledge base running on a local model, an incident-response system watching network health, and a system to help win business-client tenders.
A telecom operator came to us with three connected problems rather than one. Their team needed answers about internal systems and procedures, but the answers had to come from a model running on infrastructure they controlled - a hosted LLM wasn't an option given the sensitivity of network operations data.
Local-model knowledge base. We built a knowledge assistant on a self-hosted model, integrated with their existing documentation and systems, so staff get grounded answers without any data leaving their infrastructure.
Network health monitoring and response. A second system watches network flow for failures and anomalies, and reacts with the appropriate response automatically instead of waiting on a human to notice and act.
Tender automation. The same operational discipline that made the first two systems work - mapping the process, then building the agentic system around it - applied to a very different problem: helping the team assemble and win tenders from business clients faster than manual proposal-writing allowed.
Three systems, one integration philosophy: build around the infrastructure already in place. Routine procedure escalations fell by 65%, flagged network incidents reached a first response in under three minutes, and the tender team submitted 2.5x more business-client bids per quarter.