
National Public Broadcaster
Case summaries from a containerised LLM pipeline, each with full source citation.
Every project on this page runs with real users under real constraints: a legal department, a hosting provider’s support queue, an insurance data pipeline, a company switchboard, two sales organisations with nationwide installer networks. Some of it we can only describe anonymised, because that was the condition for building it at all.

Case summaries from a containerised LLM pipeline, each with full source citation.

Built on webgo's own infrastructure under strict data sovereignty.

Multi-stage LLM scoring and a GDPR-compliant data flow.

A modular voicebot framework deployed on Azure.

Around 80,000 installers identified nationwide, qualified by offering and competence, and reconciled against the existing CRM. Delivered as an import-ready export back into the client's own system, repeated annually since 2023.

Landscaping and outdoor-build trades identified, qualified by degree of professionalisation, and matched against the existing partner base. Up to six parallel sources were merged into one record per business, traceable back to where each entry came from.
Six industries, six stacks, very different budgets. The same four conditions decided whether each one made it into production.
Broadcaster: anonymised. webgo: entirely on their own hardware. Tjara: a GDPR-compliant flow designed before the first prototype existed. In each case the deployment model was a requirement rather than an afterthought, which is also what narrowed the model choice.
None of these systems decides on its own. They summarise, score, retrieve and draft; a specialist accepts, corrects or rejects. That review step is also where the labelled cases came from that we used to widen coverage.
Case summaries cite the passage they came from. Retrieval answers name the document. Scores expose the features behind them. Without that, nobody in a regulated department signs off on day-to-day use.
Each project ended with a named owner on the client side, a written operating model and monitoring they can read themselves. The projects that quietly stall are the ones where this last step was treated as optional.
The tools and platforms behind every Blue Avenir engagement.
Cloud, private cloud, or entirely on your own infrastructure. The webgo pipeline runs on-premise under strict data sovereignty.
GDPR-compliant data flows are designed in from the first prototype, not retrofitted before go-live.
Where state, embeddings and artefacts live.
Chosen per use case, and replaceable. No architecture is tied to a single provider.
How a model reaches your knowledge, and how the surrounding steps are sequenced.
What the running system is built and shipped with.

We help you close the gap between a promising pilot and a system your teams rely on every day.