AI Assistant for ViewPoint

Making AI feel at home in a legacy product.

Designing how an AI assistant looks, behaves and fits into ViewPoint, an ERP for Dutch housing corporations, without rebuilding the product around it.

Year

2026

Role

Lead designer

Team size

Me, product owner, developers, stakeholders

Duration

4 months

Company

Itris BV, ViewPoint

Tools

Figma, FigJam, Miro, Jira, Claude Design



Live in 20+ customer environments.

Context

A new capability, in a product that wasn’t built for it.

ViewPoint is the ERP Itris builds for Dutch housing corporations. Case workers, helpdesk and CRM staff, finance employees and admins use it every day to manage tenants, properties, cases and payments.

Itris wanted an AI assistant inside the product. There were three reasons. People should find information faster. The helpdesk should get fewer routine questions. And it would lay the groundwork for workflow optimisation, where AI takes over tasks or at least makes them faster.

My brief: as lead designer, decide how AI shows up in ViewPoint, and how users can tell it apart from the rest of the product.

What the assistant does

The assistant answers questions and summarises information. It works with data and context from the customer’s own environment, including customer data and the page the user is on. That means a user can ask about what is in front of them instead of describing it first.

The constraint that shaped everything

My first instinct was a dedicated sidebar or a full AI page, with room to grow. Both were out. ViewPoint is built with iframes on an older web architecture, so a panel that reshapes the page wasn’t technically possible.

The solution was an assistant that sits on top of the existing screens. A floating button in the bottom right opens a small chat window. It works on any screen, and the product underneath stays untouched.

ai chat frame closed

Designing AI as its own layer

With placement fixed, my focus moved to the UI strategy for AI. Three questions guided the work:

  • How do we show clearly that something is an AI feature?

  • How does that differ from regular functions?

  • How do we show AI in a way that feels modern?

A gradient instead of solid colour. The assistant uses a purple gradient, fading from light to deep purple. Regular functions are flat and solid. AI is soft and dimensional, so the two never get confused.

Between old and new. The purple comes from the new ViewPoint look, set up in the Zaak en Taak project. I also worked on that project, and it ran at the same time. So I couldn’t use the new styling as a background. I designed against the old light-blue ViewPoint interface, and the purple assistant had to sit comfortably on top of it. The result also holds up as the product moves to the new look.

Honest by default. A short disclaimer under the input field says the assistant is AI and can make mistakes.

empty state

Motion as part of the AI identity

Colour alone wasn’t enough to set AI apart, so I added motion. The gradient is alive, and how it moves tells the user what the assistant is doing.

  • Opening. When the panel opens, the background gradient animates in. The assistant arrives as a deliberate moment instead of a box that simply appears.

  • Answering. While the assistant answers, the gradient moves faster. The change in pace shows that it is working, and it settles again once the answer is there.

I took cues from the standards Google has set with Gemini, so the behaviour feels familiar to people who already use AI products elsewhere.

text thinking state

How we got there

  • Stakeholder workshops to align on use cases and what the assistant should and shouldn’t do.

  • Research into how other products show AI.

  • Prototyping with AI tools (Claude Design) to test ideas quickly.

  • Customer feedback on the design along the way.

The result

The assistant is live in 20+ customer environments. The feedback is positive: it’s easy to use, and customers like how the AI looks. The foundation is also set up to take on more capabilities over time.

Reflection

  • A new way of working. I could build much of this with AI tools, which was a new and enjoyable way for me to work.

  • What I’d change. Given the choice, I would have built a better way to work with AI, such as a separate window or sidebar. That wasn’t feasible technically. Designing within a limit like that is a large part of working on a legacy product.