One of the big challenges with AI in organisations is not just building something that works. It is making the solution easy to adopt, easy to maintain and easy to share with others.
That was the background for an important part of the launch in our webinar about AI apps on Promte. We did not only show that you can build AI apps on the platform. We also showed how apps can be installed, shared and carried forward between organisations through an app library.
That is an important difference. Because when AI solutions become shareable, their value increases significantly.
In the webinar, we presented two closely connected things.
One part is a framework for building AI apps on Promte. Here, organisations can develop their own apps with the interfaces and functions they need, while building on Promte's existing layers for hosting, backend, models and user management.
The other part is an app library with prebuilt apps that can already be installed and used. Examples included the recruitment assistant, impact assessment drafts, a Word translator and the interpreter app from Kalundborg Municipality.
The two parts reinforce each other. The framework makes it possible to build. The library makes it possible to adopt and share further.
In many organisations, the same needs arise at roughly the same time.
One municipality wants to automate first drafts of citizen letters. Another wants to make translation work more efficient. A third needs help with document-heavy assessments or internal notes. The needs are not identical, but they are often similar enough that you can learn from what others have already built.
That is exactly where an app library makes sense.
Instead of every organisation starting from zero, you can start from existing apps. Some solutions can be installed directly. Others can be used as inspiration or developed further for local needs.
It does not only save development time. It also creates a more mature ecosystem around AI apps, where good ideas do not remain in silos.
In the webinar, we also showed the practical side: an app can be installed directly from the library into the organisation's own Promte setup.
That may sound like a small thing, but it is crucial in practice. An app only creates value once it actually reaches users.
When installation and distribution are part of the platform, the path becomes shorter from "this looks interesting" to "my colleagues can use this". It also makes it easier to work with updates, because apps do not have to be handled as loose standalone projects without a shared home.
At the same time, it means sharing is not only theoretical. If an organisation chooses to do so, its app can become available to others in a way that is far more concrete than a loosely described idea in a meeting or PDF.
Another important point from the webinar was that Promte also makes examples and packages available, so organisations do not have to invent everything themselves.
That includes both open source examples and the tools that make it easier to call functions and work with app logic. This kind of material is often underestimated, but it matters a lot in the early phase. Many people get started faster when they can see a real solution rather than only read a theoretical description.
It is especially useful for organisations that can develop themselves, but do not want to spend unnecessary time building the same basic elements again and again.
Shareability is therefore not only about sharing finished apps. It is also about sharing building blocks.
When people talk about AI in municipalities and larger organisations, it can quickly sound as if every solution has to be a large custom project. In reality, much of the value emerges when small and medium-sized solutions can be reused, adapted and carried forward.
An app library supports exactly that kind of adoption. It makes it possible to start smaller, learn faster and build on what already works.
It is also a more realistic model for organisations that want momentum without starting a new development process for every idea.
If another organisation has already solved 70 percent of the task, it is often more sensible to build from there than to begin from scratch.
The perhaps most important point is that sharing makes AI more useful as a shared capability.
When apps can be installed, adapted and shared across organisations, AI is no longer something that lives only in individual experiments. It becomes something more people can benefit from without every organisation carrying the full burden alone.
That fits well with the reality many municipalities are facing. There is a need for both local adaptation and solutions that do not have to be invented from the ground up every time.
That is why we see the app library as more than a collection of apps. It is a way to make AI work more practical, more mature and more shareable.
If you want to get started quickly, it may be obvious to begin with the apps that are already ready. And if you have a process that is better suited to a custom-built solution, you can build your own app and share it further if that makes sense.
