We're building thefeedback tool we always needed.
Visual feedback for design and product teams — built to replace the chaos of scattered comments across tools.
Why we exist
“Feedback doesn't belong in Slack threads, email chains, or meeting notes. It belongs on the thing you're building.”
Design feedback is broken. Your team reviews a website in a meeting, someone takes notes, another person drops a screenshot in Slack, and a third sends an email with a PDF of marked-up screenshots. A week later nobody remembers what was resolved.
We built layernote because we lived this problem every day. Pinned to the pixel, assigned to the right person, tracked until it ships — that's how feedback should work.
What we do
Annotate
Live URLs, Figma files, images, PDFs — click anywhere to pin feedback to the pixel.
Collaborate
Share a link. Clients leave feedback without an account. Live cursors, real-time updates.
Ship
Prioritize, assign, set deadlines. Track everything on a kanban board until it's done.
The founder
Dino Murselovic
Founder & Developer
@dino_mursBuilding layernote from the Netherlands. Previously worked as a web developer at agencies where design feedback was scattered across Slack, Notion messages, and countless other tools. That experience became the blueprint for layernote, a tool built by someone who lived the problem.
info@layernote.ioWe write about feedback, product updates, and the lessons we learn along the way.
Get started
Because feedback shouldn'tbe the hard part.
Give your clients a clear way to review. Give your team a clear way to resolve. Done.
