The same app beyond the factory floor

A university has the same problem as a plant

Around two thousand employees spread across a campus: administration, technical services, academic staff. What they share is that they rarely sit at a desk with a company computer open on the intranet.

The information exists — in the intranet, the calendar, the announcements — just scattered across places you have to deliberately go and check. It is exactly the same situation as in a manufacturing plant, only the shop floor is a campus.

The solution

Signing in with the university account

The app uses the identity the university already has — sign-in goes through the corporate Microsoft directory, so nobody creates new accounts or manages separate passwords. Access is protected by biometric login.

Content is pulled from the university's existing site instead of being written a second time. People without an account see a guest view — with what is public anyway.

What runs inside the app

News, an events calendar you can respond to, push notifications on the phone, and campus navigation — a map with buildings and directions to the place you picked.

On top of that, an AI assistant answering questions, trained on the university's own materials — not a generic chatbot from the internet, but one that knows how this particular organisation works.

The commercial model

Source code on the client's side

The university chose the perpetual licence with full source code. The app belongs to them, their own team develops it, and everything runs on university infrastructure.

This answers the question that surfaces sooner or later in every major tender: what happens if the supplier disappears or the contract ends. Here the answer is — nothing. The code stays.

And yet the collaboration continues: code reviews, help with the harder bugs, publishing new releases to the stores. Not because the university has to, but because it is faster that way. We do not sell dependence on us — we sell a shortcut.

There are two routes. A subscription — billed per employee, or only for those who actually use the app. Or a perpetual licence — no subscription, full source code and the right to develop it independently. The choice depends on whether the organisation has its own team and its own security policy.