Don’t describe it.
Pin it.
Sidenote turns “the button looks weird on the checkout page, I think?” into a structured pin on the exact element — severity, intent, and selector included. No engineering degree required.
chrome · edge · brave — works on any site — zero code changes
Primary CTA is the same shade as the disabled state — three testers clicked it expecting it to be inactive.
Same feedback. One click, zero archaeology. Your team sees the exact element, page, and context.
If you can point at it,
you can review it.
Feedback tools keep getting built for engineers. Sidenote works for whoever spotted the problem — pin first, triage later.
Feedback used to take days.
Now it takes a click.
From “this looks broken” to someone reproducing it. Average, if nobody’s on PTO.
Click the element, pick severity + intent, type a line. The pin carries everything else.
Run it for your team.
Three sliders. The napkin below redraws as you drag — then send the result to whoever needs to see it.
sidenote — your inputs
Payroll spent on “which button?”
$4400,000000per year
Time back
4466 hours / month
32 items a week × 20 payroll-minutes saved each. The napkin below shows where those minutes go.
Three minutes of a designer’s time is cheap.
Twenty-three isn’t.
At ≈ $1.20 a minute — your salary slider — here’s the back-of-the-napkin cost of one piece of UI feedback, each way.
× 32 items a week ≈ 11 hours — or about $40,000 a year — spent asking “which button?”
Same bar. Same scale. The sliver on the left is the whole job now — the rest was archaeology.
— the budget case · show it to whoever owns the money —
The roadmap argument
Your team ships 32 pieces of UI feedback a week. Each one costs 23 payroll-minutes; pinned, it costs 3. That’s 46 hours of product time back every month — roughly a quarter of a headcount, without hiring it.
The budget argument
$40,000 a year of payroll currently goes to describing, clarifying, and re-finding UI feedback — at $1.20/minute of loaded cost. The fix is a browser extension that’s free during beta. This is the easiest line item you’ll cut this quarter.
The craft argument
Every “which button?” thread burns $27.64 of design time describing pixels instead of fixing them. Sidenote pins critique to the pixel — severity, intent, and element attached — so review happens on the work, not in a thread about the work.
The reproduction argument
Every report arrives with the exact CSS selector and page URL — reproduction drops from ~8 minutes to zero. Across 32 items a week, that’s 19 engineering hours a month not spent re-finding bugs someone already found.
— the empowerment case · for the people who stop waiting on tickets —
Review the launch page yourself
The campaign goes live at 9. You spot the buried CTA at 8:40. You don’t file a ticket and hope — you pin it.
- Click the live page — no staging access, no dev tools, no engineer translating
- The pin carries the exact element. Never again “the button in the top-ish area”
- “Approve” pins double as timestamped sign-off before things ship
Edit on the page, not in a doc
The rewrite lives on the sentence it rewrites — with the layout, tone, and button it has to work next to.
- Pin the paragraph, paste the new copy in the comment
- “Change” intent says it’s wording, not a bug — no triage confusion
- No more spreadsheet column called “where on the page”
Pin what customers hit
Five tickets about the same screen this week? Walk to that screen and pin it, quoting the customer.
- Turn ticket patterns into pins product actually sees — in realtime
- You set the severity. You’re the one reading the tickets
- Your evidence beats a quarterly “voice of customer” deck
Everything sticks.
Nothing gets lost.
Pins stick to elements
Not screen coordinates — the actual DOM node. Pins survive layout shifts, breakpoints, and refactors.
Severity built in
Blocking, important, or suggestion — chosen at capture, color-coded everywhere. Your dashboard sorts itself.
Intent removes tone
Fix, change, question, or approve. “Is this a demand or a musing?” is no longer a thread of its own.
Live team canvas
Pins land in the shared dashboard the instant they’re placed. No refresh, no polling, no “did you see my message?”
Orgs & projects
Row-level security scopes everything to your org. Invite by link, control by role. Client work stays walled off.
Pin → Linear ticket
One click converts a pin into a Linear issue with the comment, selector, page, and screenshots carried over.
Teams are pinning.
Our design review meetings went from 60 minutes of screen-sharing to 15 minutes of walking the pin list.
Marketing reviews the launch page without me now. I get pins with selectors instead of “the text near the top”.
Legal flagged a compliance issue as Blocking, pinned to the exact claim. We caught it before the campaign went out.
Clients finally give feedback we can act on. “Approve” pins alone were worth the install.
Support pins the screens customers complain about. Product finally sees what we see.
Our design review meetings went from 60 minutes of screen-sharing to 15 minutes of walking the pin list.
Marketing reviews the launch page without me now. I get pins with selectors instead of “the text near the top”.
Legal flagged a compliance issue as Blocking, pinned to the exact claim. We caught it before the campaign went out.
Clients finally give feedback we can act on. “Approve” pins alone were worth the install.
Support pins the screens customers complain about. Product finally sees what we see.
Start pinning.
Setup takes about a minute. Your first “wait, which button?” thread can be your last.