What it does
Turns customer conversations into research your team can point at.
Tacari reads interviews, calls and support conversations the way an analyst would: pulling out individual, citable claims instead of a paraphrased summary. Every finding it produces carries its evidence forward. Anyone reading it, on your team or another one, can trace a claim back to the person who actually said it, in the exact conversation it came from.
Founders, PMs, and product teams
At growing B2B software companies, usually 10 to 75 people, who run their own customer conversations.
No dedicated researcher
There's no separate research function at this size. Whoever runs the call is doing discovery on top of their actual job, and what they learn can easily stay with just them.
Findings survive scrutiny
When a stakeholder asks who actually said that, there's an answer on the page, not a scramble back through call recordings.
Where it goes
One evidence base. Ask it in whatever shape the moment needs.
A PM runs the interviews, but the evidence isn't only useful to the PM. There's no fixed menu of document types, you write what you need in plain language, and it's drawn from the same grounded evidence every time, whether that's a product brief, notes for a sales call, or a summary for leadership. Nobody re-does the research to get a different answer out of it.
Ask it the moment the call's in
Evidence is extracted and citable as soon as a conversation is ingested, not after someone re-listens and writes it up. Ask a question the same day you ran the call, not just when you're ready to write. If the answer's worth keeping, save it as a document with its citations intact, in one click.
Built for the team
One evidence base. Everyone on the project sees it.
Add a teammate to the project and they're not reading someone's notes from a meeting they missed, they're working from the same evidence, the same trust decisions, the same citations, live. The person who ran the interview doesn't become the bottleneck for everyone who needs what was said in it.
How it works
Three steps. Nothing skipped.
You add a conversation
A call transcript, a support thread, a usability session. Read by conversation, not by keyword.
It selects, not summarises
Each discrete claim becomes its own record, classified and linked to the exact moment it was said.
A document that shows its work
Every finding carries its citations forward. Thin evidence is labelled thin, never dressed up as a pattern.
Most people abandon checkout at the shipping-frequency step , not at price . "I didn't actually know if I was signing up for every month or every three." "The price was fine, I just wanted to know when it would actually charge me."
The difference
It isn't the writing. It's what's underneath it.
"Users consistently struggle with the setup flow, indicating a clear need to simplify onboarding."
Two participants independently misread the same billing step as the point they nearly quit.
FAQ