I’m a frontend developer and one thing that always bothered me on client projects was the feedback process.
Clients would send things like:
“Make this button bigger”
“Change this section”
“Use another image here”
…but the feedback would come through WhatsApp, screenshots, email, or random messages, so half the work was figuring out what they were actually referring to.
I recently built ClientPin to solve this.
The idea is simple:
Client opens the website ** → **clicks the exact element → leaves a comment → developer gets the page, screenshot, browser context, and feedback in one place.
Clients don’t need to create an account just to leave feedback.
It is launched recently and have a try.
Thanks
Top comments (1)
No-account feedback for clients is the right call; asking them to sign up is where these tools usually lose the client. The hard part I'd test early is what happens to a pin after you redeploy. With Tailwind or CSS-module class names, the selector a comment was anchored to often doesn't exist on the next build, and the pin silently floats to the wrong place or disappears. Storing a few fallbacks (the element's text, its position among siblings, and a cropped screenshot) and marking a comment "element changed since this was left" keeps old feedback honest. Also worth capturing the viewport width with each comment, since "this button is too small" from a phone and from a laptop are two different bugs. How are you anchoring pins today?