Condens

What it is

Condens is a UX research repository: you drop in recordings, transcripts, notes and survey exports, then highlight, tag, and cluster them into findings you can share as a linked report. The AI layer handles the mechanical parts — transcription, suggested tags on highlights, session summaries, and asking questions across a whole project — while deliberately stopping short of “press the button and receive your insights.” Condens is unusually public about that boundary; it publishes its own survey of 330+ researchers showing AI helps speed far more than it helps quality.

Our verdict

The honest middle option in research repositories. It does the same core job as the category leaders — evidence in, tagged quotes out, every finding traceable back to the person who said it — at an entry price a two-person product team can sign off on without procurement. The tagging flow is fast, the analysis board handles affinity-mapping without a detour into a whiteboard tool, and shared reports expand each claim into the clip behind it, which is what makes research survive contact with a skeptical exec.

Where it falls short: the gap between tiers is brutal — €15/mo to €500/mo billed yearly, with nothing in between, so the moment you need a few collaborators your cost jumps roughly 30x overnight. There is no free plan at all, only a 15-day trial. And it’s a smaller vendor with a thinner integration ecosystem than Dovetail: pulling feedback in automatically from support tools or sales calls means more manual export work than you’d like.

Get value in 10 minutes

1. Start the 15-day trial (no card) and create one project named after a live question you actually have — e.g. “Why do trials stall at day 3?”
2. Upload two or three interview recordings and let Condens transcribe while you do something else.
3. Skim the first transcript and highlight as you read. Don’t pre-build a taxonomy: tag with the words the user used (too many steps, didn't know what to do next), and treat the AI’s suggested tags as something to accept or reject, not something to start from.
4. Open the analysis board, drag highlights into three to five clusters, and name each cluster as a claim rather than a topic — “Users stall because setup needs data they don’t have yet,” not “Onboarding.”
5. Share the report link into the channel where the decision gets made. The point is the click-through: every claim opens the clip of a real person saying it.