Your team reviews every line of code. Nobody reviews the product.
Record yourself using a build and talk through what you are unsure about. Butter returns timestamped findings — with the frames and quotes behind them — that your team accepts, discusses, or dismisses one at a time.
A finding carries its evidence.
Generic interface advice is easy to produce and easy to ignore. Everything Butter files points at the frame, the quote, or the event it came from.
Payment submission has no immediate feedback
- narration
- “when I hit Pay there's a slight delay here”
- keyframes
- 02:14.2 and 02:16.1 are identical
- click
- submit at 02:14.180
It says when it does not know
An open question names the data that would settle it instead of guessing confidently. Correlation is not reported as cause.
Dismissals are answers
Marking something intentional records that it was deliberate, so the next person finds the reason instead of reopening the argument.
Tied to the build
Every review carries its branch and commit, so a finding points at a version of the product rather than a memory of it.
Reviewed like a PR
Each finding is addressed on its own — accepted, discussed, dismissed with a reason, or sent to GitHub or Linear as an issue.
Git remembers what changed. Nothing remembers why.
Implementation history is preserved carefully — commits, pull requests, review threads. Product reasoning is not. It lives in Slack threads, meeting notes, recordings nobody rewatches, and people's memories.
Six months later, why is checkout one page? has no answer, so the decision gets relitigated from scratch by people who were not there the first time.
Butter keeps the reasoning attached to the moment it was made — the recording, the narration, the discussion, and what the team decided.
How a review moves
Record
Capture the screen while you use the build. Clicks, route changes and viewport are captured on the same clock.
Narrate
Say what you are unsure about. A concern you voice outranks anything the review finds on its own.
Review
Findings land on the timeline as issues, suggestions and questions, each with its evidence attached.
Decide
Accept, dismiss with a reason, or convert to an issue. The decision and its rationale are kept.
Record your next build
Butter is early and built in the open. Sign in with GitHub, record a demo, and tell us whether the findings were worth reading.