VEI (“path” in Norwegian) is a modular, AI-first ecosystem for people navigating language, documents, and local services in Norway. It grew from the LINK AI chapter into a longer lifecycle product — one app idea that can evolve with the user instead of being deleted after the first months.
Series: LINK AI · VEI · UDI-adjacent path. Origin story: products from necessity.
Modules (public overview)
| Module | Job |
|---|---|
| Link / chat | Procedural Q&A and everyday orientation |
| Scan | Vision for letters, labels, signs, receipts |
| Translate | Context-aware translation feeding language learning |
| Språk | Norwegian practice tied to real situations |
| Kommune | Local services and process navigation |
Approach
- Start from lived friction, not a feature wishlist.
- Ship a narrow MVP, then expand modules without throwing away context.
- Design for privacy-aware document handling — keep sensitive scans inside a controlled product path instead of random consumer chatbots.
- Prepare pitch materials for municipalities and partners while the Scan prototype stays hands-on.
What you can open today
- VEI live hub
- VEI presentation
- VEI 4D architecture map
- Full case card + links: Projects
Result
Working Scan prototype, coherent multi-module vision, outreach materials for kommuner, and a clear hire/collaboration story: Product Owner + AI architect who can own delivery end-to-end.
Next in series: how this connects to public-adjacent interest (UDI / operator path) — read here.
FAQ
Is VEI only for newcomers?
Newcomers are the primary user story. The same stack (vision, translation, local navigation, language) also helps staff and partners who support them.
Where does product ownership show up?
Roadmap across modules, MVP scope, stakeholder narrative for public-adjacent partners, and the link between field pain and shippable architecture.