Turn user feedback into a backlog you can trust.

Record a call, a session, or a meeting. Sense transcribes, finds the insights, and drops the next steps into your backlog — each linked to its exact source.

1/3
app.revolut.com/payments/send
REC
MC
Payments

Send money

MC
JM
John Martin
Personal ·•• 4821
Recipient
You send
€1,250.00
Balance after transfer · €3,842.16
Fee
€0.00
Arrival
In seconds
Something went wrong. Please try again.
Sense
maya@revolut.com
Internal tester
Capture into
Workspace
Revolut · Product QA
Project
Card controls
private · member
Payment flows
private · member
Mobile onboarding
private · member
Ready to record feedback
Start recording
0:04
Finish
Sense_
9+
Revolut · Product QA
Home
Backlog
Projects3
Payment flows
Card controls
Mobile onboarding
New project
MC
Maya Chenmaya@revolut.com
Payment flows Signal • Screen recording
app.revolut.com/payments/send
Send money
€1,250.00
Send money
Something went wrong
TRANSCRIPT Copy Download
Maya · Internal QA0:08

I'm testing a bank transfer to John Martin for €1,250. The recipient and balance both look correct, but clicking “Send money” returns “Something went wrong” and the transfer is not created. Retrying gives me the same error, so this blocks the payment completely.

Overview
Insights
Anchors
INSIGHTS 1

Bank transfer fails at final confirmation

payments bank-transfer blocking-bug

A valid bank transfer fails after final confirmation with a generic error. The failure is reproducible and blocks the tester from sending money to an existing recipient.

1 Anchor attached
“Clicking ‘Send money’ returns ‘Something went wrong’...”
Revolut · Payment flows / Backlog

Backlog

Board
Table
Backlog12

Fix bank transfer failure at final confirmation

Bug1 insight
MC
To do0
Nothing here
Done38

Clarify beneficiary confirmation before transfer

Improvement1 insight
MC
featured on
Sense - Feedbacks in, shipped features out | Product HuntSense - Feedbacks in, shipped features out | Product HuntFazier badge
how it works

Watch one sentence become an action item.

However the feedback arrives—testing sessions, user reports, or meetings—it all runs through one pipeline. Follow a real transcript from capture to backlog, where every insight stays linked to the exact words a user said. Pick a use case below to see it in action.

Worked exampleCapture → backlog

Every capture becomes a signal, and the insights land in your backlog as action items.

  1. CaptureSomeone records what happened, however suits them.
    app.example.com/reportsREC
    1:08Finish
  2. SignalIt lands here as a transcript — timestamped, searchable, with the recording attached.
    0:02PriyaFiltering to open items, then opening one to check the detail view.
    0:09PriyaWait — the filter reset itself when I hit back. That definitely worked last week.
    0:15TomSame on mine. Sort order goes too, not just the filter.
  3. AnchorsRead against your 4 goals, the passages that answer one get pulled out and tagged.
    0:02PriyaFiltering to open items, then opening one to check the detail view.
    0:09PriyaWait — the filter reset itself when I hit back. That definitely worked last week.
    0:15TomSame on mine. Sort order goes too, not just the filter.
    Regressions
  4. InsightsThe anchors group into an insight — often spanning more than one goal.
    Going back from a detail view drops both the filter and the sort order
    3 anchorsRegressionsUsability & polish
  5. BacklogInsights become prioritizable action items, each linked to its evidence. Copy prompt hands one — with all its context — to whoever picks it up, coding agent included.
    Preserve filter and sort state on back navigationTodo
    Copy prompt
Worked exampleCapture → backlog

Every report becomes a signal, and the insights land in your backlog as things to fix or build.

  1. CaptureSomeone records what happened, however suits them.
    Give us feedbackRecord your screen and voice to walk us through what you ran into.
    Record an audioRecord your screen or tab
  2. SignalIt lands here as a transcript — timestamped, searchable, with the recording attached.
    0:01MayaI'm pulling the quarterly numbers out like I do every Monday.
    0:06MayaI tried to export the report three times and it just spun forever. Ended up screenshotting the whole thing.
    0:14MayaThe date picker also jumps back to this month every time I reopen it.
  3. AnchorsRead against your 4 goals, the passages that answer one get pulled out and tagged.
    0:01MayaI'm pulling the quarterly numbers out like I do every Monday.
    0:06MayaI tried to export the report three times and it just spun forever. Ended up screenshotting the whole thing.
    0:14MayaThe date picker also jumps back to this month every time I reopen it.
    Bugs & breakage
  4. InsightsThe anchors group into an insight — often spanning more than one goal.
    Exporting a full quarter hangs, so people screenshot the report instead
    3 anchorsBugs & breakageUsability friction
  5. BacklogInsights become prioritizable action items, each linked to its evidence. Copy prompt hands one — with all its context — to whoever picks it up, coding agent included.
    Fix report export timeout on large rangesTodo
    Copy prompt
Worked exampleCapture → backlog

Every meeting becomes a memo, and the decisions and commitments land in your backlog.

  1. CaptureSomeone records what happened, however suits them.
    DRSKRECSense
    Sense Bot joined the call
  2. SignalIt lands here as a transcript — timestamped, searchable, with the recording attached.
    0:03DanaThe calculator is the only thing still blocking the pricing page.
    0:11SamLet's ship the pricing page without the calculator and add it in the follow-up.
    0:18DanaWorks for me. I'll own the follow-up and get a date by Thursday.
  3. AnchorsRead against your 4 goals, the passages that answer one get pulled out and tagged.
    0:03DanaThe calculator is the only thing still blocking the pricing page.
    0:11SamLet's ship the pricing page without the calculator and add it in the follow-up.
    0:18DanaWorks for me. I'll own the follow-up and get a date by Thursday.
    Decisions
  4. InsightsThe anchors group into an insight — often spanning more than one goal.
    Pricing page ships without the calculator, with Dana owning the follow-up
    3 anchorsDecisionsAction items & owners
  5. BacklogInsights become prioritizable action items, each linked to its evidence. Copy prompt hands one — with all its context — to whoever picks it up, coding agent included.
    Ship pricing page v1, calculator deferredTodo
    Copy prompt

Stop guessing what to build next. Let the evidence decide.

Book a Call

Feed real user feedback directly into your coding agent.

Tell us a little about what you're building. We'll plug Sense into a slice of your real user feedback and walk you through what it generates.

  • 30-minute, founder-led walkthrough
  • Talk about your specific needs
  • Decide about a trial — no pressure
1 / 6What are you building?Book a Call

What are you building?

Tell us what you're building first