Six ways feedback reaches you. One way it becomes work.
A user reporting a bug, a teammate dogfooding, a call you sat in on, an interview, a testing session, a demo you narrated — each arrives differently and each needs different things pulled out of it. Sense ships a purpose-built project for all six, and every workspace gets all of them on day one.
End users report bugs and ideas through an embedded widget.
Teams whose users are outside the building — nobody on your team is in the room when the frustration happens.
Your team dogfoods and captures issues before users hit them.
The team itself, testing its own product before a release.
Turn meetings into decisions, action items, and open questions.
Anyone whose decisions get made on calls and then evaporate.
Interview users to learn which problems are worth solving.
Product teams doing problem-space research before committing to a solution.
Watch real users attempt tasks in your product, live on a call.
Teams running moderated usability sessions — the same activity as internal testing, with a different person at the keyboard.
Record a walkthrough and turn it into notes on how it works.
The only template whose subject is your product rather than a user — founders and PMs narrating their own screen for onboarding, sales, or handover.
Not a theme. A preset built out of five things.
Picking a template does not change how the page looks. It changes what the AI is asked to find, what you reach for first when you capture, and what the project promises to give back.
Four or five extraction prompts telling the AI what to pull out of every transcript in this project.
The capture card reorders itself so the one method this situation calls for is what you reach for first.
One line on what comes out the far end — shown in the create preview and again while the project is still empty.
A real transcript, one anchored line, and what it becomes at each stage of the pipeline.
Which capture zone the project tour spotlights, and what its final button says.
Every template runs the same five hops.
Whatever the source, the path is identical — and nothing along it is a summary. Each hop keeps a link to the one before, so an item on your backlog still opens onto the sentence that produced it.
- Capture
One recording, upload, paste, or widget submission.
- Signal
It lands as a timestamped transcript with the recording attached.
- Anchors
The lines that answer a goal get pulled out verbatim and tagged.
- Insights
Anchors group into a finding, often spanning more than one goal.
- Backlog
Findings become action items, each linked back to its evidence.
A theme is a pattern across signals: it bundles related insights under a goal and ranks them by how many anchors sit underneath. Insights stay inside one signal; themes are what make the twelfth interview worth more than the first.
All seven capture methods are available in every project. A template only decides what you see first.
Rewrite, remove, or add to the preset goals at any time. A project holds up to five.
A new workspace is seeded with one project per template. Nothing is locked behind a choice you make on day one.
Every anchor carries its citation offsets into the transcript, so each claim traces back to the words that were said.
Every workspace starts with this project already in it.
Create a workspace and all six projects are seeded for you — this one included, goals and capture order set up. Nothing to configure before your first capture.