Product thinking
An AI answer is more useful when you can inspect it.
Designing a source-aware answer around context, review and human judgment.
3 min read

A confident sentence is not the same as a useful explanation. In a financial interface, the explanation should help a person check the answer and decide what to do next.
Put context next to the answer
An answer about spending needs a period, a definition and a comparison. Is it cash paid, expenses recognized or commitments made? The same question can have different answers depending on those choices.
Make the source easy to reach
Source labels work best when they point to a record someone can inspect. A source name alone is not proof. A live implementation should preserve the route from a statement to the data and calculation behind it.
Keep review in the workflow
A useful assistant can reduce the distance between a question and a first explanation. It should also make it easy to notice missing context, challenge an assumption and bring a person into the decision.
The Aven assistant is a local interface demonstration. Its sample answers are written examples, not responses from a connected AI service.
Explore the product
↗