AmassAI research for life sciences, with every claim traced to its source.

A laptop on a wooden desk showing the Amass homepage: “Amass consolidates your data. Every claim cited to source.”

At a glance

Design thinking: Show the working before asking anyone to believe it. The plan comes before the run, and a source sits on every claim.

Problem: An AI research answer can draw on many sources at once, and nobody could tell by eye where a claim came from.
Approach: Each area was explored more than one way on real screens, and the version people could scan and edit won.
Outcome: Five product areas reworked, from the first question to a cited, reusable output. Our colour changes were merged into the live website.

Role: Lucie on product design, working with Emil Cronval, Head of Go-to-Market, and CEO Henrik Jensen. On the website, supporting Niels Andersen.
What we designed: Product strategy
UX/UI design
AI product design
Prototyping
Website design
Platforms: Web app
Website

Four UX principles the whole product follows.

01Show the plan before it runsObjective, sources and steps are visible and editable while changes are still cheap.
02Ask only what changes the planOne question at a time, with a suggested default and a way to skip.
03Keep every claim next to its sourceEvidence is there at the moment a reader doubts a statement.
04Let evidence outlive the taskSources stay in the workspace, ready for the next project.

We tried a canvas, then chose a plan people can read.

An early experiment laid research out as answer nodes on a canvas. A plan has to be scanned and edited, so it moved beside the chat, in three sections that expand on demand.

A later task: the chat on the left, and a plan on the right with output type, objective, data context and research steps.

From a question to a report the team can reuse.

A finished report goes back into the drive, ready to be a source for the next task.

01DriveFiles you upload or connect
02Data contextPrivate or team datasets
03TaskScoped to the chosen data
04QuestionIn a conversation, or in research mode with steps
05AnswerFollow-ups open a child node in the same context
06TemplatePrivate, team or premade
07OutlineDrafted from the task, or fixed with placeholders
08ReportSaved as an asset
Available as a source

From Report, the flow returns to Drive: Available as a source.

A scroll story: scattered evidence ends up on one shelf.

As you scroll, evidence scattered across teams and tools settles onto one shelf. Niels Andersen and the Amass team built the site; we supported them in its repository, reviewing colour and pacing on live previews.

The amass.tech home page: “Evidence you can check, not answers you have to trust.” over a dotted cream ground.

Colour marks the evidence, and everything else stays neutral.

The content spines went warm orange, the headlines neutral and the core cards cream, so colour marks the evidence and nothing else. The change was merged into the live site.