How DevPin works
DevPin collects point-and-click feedback on a web page and carries it all the way to a verified fix. This page is the mental model; Install has the copy-paste snippets.
Sending this to a client or tester? Forward them How to give feedback instead, it is written for them and needs no technical background.
The two kinds of people
This is the distinction that explains everything else.
- Reviewers (clients, QA, stakeholders) submit feedback through the widget. They never get a dashboard account, are never charged for, and are unlimited on every plan. They only ever see the page they are reviewing plus their own verification link.
- Team members sign in to the dashboard and triage. Roles are owner (billing and deletion), admin (settings and team), and reviewer (view and triage pins).
The lifecycle of one piece of feedback
- 1Reported. A reviewer clicks the spot on the page, draws on the auto-captured screenshot, and writes what is wrong. DevPin attaches the browser, OS, viewport, the element selector, console errors, and failed network requests automatically.
- 2Triaged. The pin lands in your project as Open. You assign it, set it aside, fold duplicates together, or send it straight to a fix.
- 3Fixed. Turn the pin into an AI fix-prompt, a GitHub / Linear / Jira issue, or, with the Claude Code Action installed in your repository, a pull request opened by Claude. All the captured context travels with it.
- 4Awaiting check. You press Mark fixed, or your AI agent marks it fixed through the MCP server. That is a claim, not a closure, so DevPin emails the reporter and everyone who said "me too", with their screenshot next to a picture of the fix and a link to check it, if you or the agent added them.
- 5Verified. Each of them can open their link (no account needed) and pick "Looks fixed" or "Still broken". Confirming closes it as Verified. Rejecting reopens it with their note attached and emails the project owners, admins and the assignee. Each pin and the project header show what was fixed by an agent or the team, confirmed by the client, or reopened.
A pin can also be Dismissed if it is not something you will act on. Only the reporter can mark something Verified, which is why the board does not offer it as a move.
Setting up a project
- Create the project and copy the one-line snippet into your preview, staging, or production build.
- Choose who can leave feedback. Open lets anyone on the page submit, which suits a public beta. Invite-only restricts it to the email addresses you list, which suits client UAT. The check is enforced on the server, not just hidden in the widget.
- Choose the review mode. Feedback is the default pin-an-issue flow. Approval (Team plan) turns the widget into a per-page sign-off: reviewers approve or request changes, and you get a sign-off log.
- Choose what a pin becomes. AI fix-prompt renders pins as prompts for Cursor, Claude Code, or Copilot. Bug report renders them as human-readable issues.
Getting fixes out of it
- Fix prompt, copy a ready-to-paste task, carrying the page, element, geometry, and captured diagnostics.
- Create fix PR, after you confirm you have read the reviewer's words, files a GitHub issue tagged
@claude; if the Claude Code Action is installed in your repository, it opens a pull request. - Export to your tracker, one click into GitHub, Linear, or Jira, assignee included. With two-way sync (Pro), when the issue is closed there, the pin is marked fixed and the reviewer is asked to check; reopened there, the pin reopens.
- Your AI coding tool, connect Claude Code, Cursor or any tool that supports remote MCP servers to DevPin's hosted MCP server at
devpin.app/mcpwith a project token. Nothing to install. See Install.
Staying in the loop
- Slack, connect an incoming webhook and new feedback posts to your channel as it lands.
- Webhooks, we POST a JSON payload on pin creation for your own automation.
- Reporter email, sent automatically when you mark something Addressed. Every one carries an unsubscribe link.
Triage views
List groups pins by page, which is how you work through a review round. Board shows Open, Awaiting check, Verified, and Dismissed as columns, which is how you run a sprint. Filters cover status and assignee, including "assigned to me".
Duplicates
When several reviewers hit the same bug, fold the repeats under one primary. The list then shows the primary with an "N similar reports" expander, and building a fix prompt from it bundles every reporter's wording into a single task.
Review rounds
A round groups one batch of review, such as "Homepage, round 2": the pages to look at, a deadline, the reviewers you invite and the client who signs off. DevPin emails the invites, reminds reviewers who have not looked a day before the deadline, shows how many items are fixed and confirmed, asks the client to sign off when everything is done, and gives you a report to send them. Rounds are on the Pro plan.
What each plan includes
- Free: one project, unlimited reviewers and pins, screenshots and drawing, fix prompts and bug reports, the hosted MCP server, tracker export, and the client's confirm-the-fix email.
- Pro: unlimited projects, screen recordings, two-way tracker sync, and review rounds with the client's sign-off. AI-polished fix prompts are coming soon.
- Team: everything in Pro, plus white label and approval mode.
Paid plan features are free during early access, except white label, which needs the Team plan. See Pricing.
Frequently asked
Does the widget need to be on every page? No. One script tag in your app shell covers every route it renders.
Do reviewers need an account? No, ever. They type an email once and stay recognised on that device.
Can I use it on production? Yes. Invite-only mode means only the addresses you list can see or submit anything.
Does it slow my site down? The widget is a single small script, loaded with defer, and renders inside a shadow DOM so it cannot affect your styles.
What if the same person reports two things? Each pin is tracked and verified independently.
Still stuck?
Email info@impactconsulting.ai. You will reach the people who build it.