For municipalities and public institutions
One supplier. Three doors.
A municipality runs a library, a school and a museum. Each has its own staff, its own systems and its own obligations — and each is being judged against the same standard by the same residents.
01 / The case
The same layer serves all three surfaces, so a municipality runs one process, one contract and one supplier relationship rather than three parallel ones.
One supplier is not one system. Each institution gets its own deployment, which is also how the library's material stays out of the school's answers.
The catalogue, the learning platform and the collections database keep their owners and their administrators. We connect to them; we do not replace them.
Librarians, teachers and curators keep the judgment calls, and get the console that lets them change what the agent does without a ticket.
02 / Before the first meeting
The answers your procurement office will ask for.
Send us the questionnaire and we will answer it in writing, in a form you can paste into a requirements document. The short version:
The full detail, including where each provider sits and what changes if you ask for a frontier US model, is on the trust page.
03 / What a rollout looks like
04 / In production
Send us your procurement questions before the meeting.
We will answer them in writing. Then we will show you a live deployment and tell you plainly what we don't do.