Feedback that sticks right to the page.

Every web project ends the same way: the client sends a screenshot with a red circle, a Slack thread, two emails and a voice note. Half of it says "the button on that one page", and you spend the afternoon guessing which button, which page, which browser.

Tools for this exist. But they all want your client to create an account first, and clients don't create accounts. The feedback goes back to email, and the tool goes unused.

So I built the one I wanted on my own client work: one script tag on the staging site. The client clicks anywhere, types their name once, and the comment sticks to the element they actually meant.

Everything: product, brand, interface, widget, backend, launch. The product decisions that matter most are the ones that remove friction, and a few of them were hard to get right:

• No reviewer accounts. A guest types their name once; behind the scenes each comment carries its own edit key, so people can still fix their typos without ever signing up.
• Pins that survive change. A comment anchors to its element plus the click position inside it; if the page shifts, it falls back to matching the element's text. If all else fails it says "orphaned" instead of pointing at the wrong thing.
• A kill-switch for production. The widget refuses to run on the live domain, checked in the browser and again on the server, so client feedback can never leak to real visitors.
• One script tag that can't hurt the host page: isolated styles, and if anything inside fails, it fails silently.

The hard part was the pins. A CSS selector alone breaks the moment a dev renames a class, so every pin stores three ways home: the selector, the click position as a percentage of the element, and a snippet of the element's text. Watching a comment survive a redesign and still point at the right button is the whole product in one interaction.

I also kept the honest trade-offs: the dashboard updates live over subscriptions, while the widget quietly polls every few seconds. Nobody reviewing a staging site needs more, and it keeps the embed tiny.

Thirteen days from first commit to launch: spec first, then the widget, the backend, the dashboard, the hardening. Built the way I now build for clients: with AI in the loop, so a one-person team moves like a full one without skipping the hard parts. Live at coohoo.app, featured on Product Hunt.