open to collaboration · Trondheim, Norway

← All articles

From field MVP to public-adjacent AI: UDI, Link, and VEI

2026-09-20

#UDI#LINKAI#VEI#GovTech#Norway

From field MVP to public-adjacent AI: UDI, Link, and VEI

Building AI next to public processes is different from shipping a consumer chatbot. Timing, trust, and clarity of ownership matter as much as model quality. This note closes the short series: LINK AI · VEI · this path.

What happened (PUBLIC facts)

  1. A fast MVP of an AI assistant for everyday reception questions was built and demonstrated to reception leadership and UDI stakeholders — interest was real.
  2. Delivery then continued in the Link / operator context as LINK AI (PWA + knowledge-grounded chat).
  3. The wider product vision moved into an independent modular home: VEI — so language, vision, commune navigation, and longer LTV could grow beyond the first months.

I do not publish confidential meeting notes, personal case files, or internal contract details here. Hire conversations can go deeper on request via contact.

Lessons for Product / AI leads

Where to look

Asset Link
LINK MVP link.axi.so assistant
LINK presentations page 182 · deck 205
VEI hub / pitch vei.axi.so · prez 708 · 4D 467
Portfolio axi.so/projects

Open to work

I’m based in Trondheim, open to Product Owner / AI integration roles and focused delivery. Also exploring Arbeidstrening with a host company via NAV.

FAQ

Did UDI fund or own the product?

Public summary only: there was interest after the MVP presentation. Ownership and commercial structure of later work live under LINK AI / VEI as described on Projects. Details for employers on request.

Why publish this series on axi.so?

So hiring managers and partners can see a coherent arc — field MVP → operator tool → modular ecosystem — with demos, not only claims.