Why small website changes eat your week
A round of client feedback on a website is usually twenty or thirty comments, and most of them take minutes to fix. The time goes on everything around the fix: finding the right page, working out which element the client meant, opening the editor or the code, making the change, then telling the client it's done. Multiply that by every client and every round.
AI coding tools can now make these changes well, but only if they know exactly what to change. Pasting a client's email into a chat doesn't work: “the button at the top looks off” means nothing without the page, the element and what the client saw. And nobody wants an AI changing a live client site on its own.
To use AI for website feedback safely, you need three things: feedback attached to the exact element, a person deciding what the AI may touch, and every change landing somewhere you can check before it goes live.
How it works
How to do it with Scopepin
- 1
Collect feedback on the site
Clients pin comments on the live or staging site with no login. Each pin carries the page, the element, a snapshot of what they saw, their screen size and browser.
- 2
Choose what the AI fixes
Review feedback as usual. Press Fix in Claude on a pin, or on Pro and Agency add a round of pins to the Claude queue with a note where it helps, like “use the brand blue”. On client projects, only work you've confirmed in scope goes without asking.
- 3
Send it to Claude
Claude opens in a new tab with the prompt filled in. Claude reads each pin, finds the element in your Webflow site or your code, and makes the smallest change that does what the client asked.
- 4
Check, publish and resolve
Every pin shows what changed and a link to the staging page or pull request, or why the AI handed it back. You check the fixes, publish, and resolve the items.
What helps
The exact element, not a guess
Each pin gives the AI the client's comment, the page, and the pinned element's code and text as the client saw it, so it changes the right thing.
One pin or a whole round
Fix a single pin from its page on any plan. On Pro and Agency, queue a round, reorder it, add notes and send it as one batch.
Staging or a pull request
Changes land on your Webflow staging site or in one pull request per batch. The AI never publishes a site or merges code.
Scope comes first
On client projects, only pins you've confirmed in scope go without asking. Extra work needs a click to approve, so nothing gets fixed for free by accident.
See also:Connect ClaudeCheck feedback against scopeInstall on Webflow
Claude
Fix Scopepin batch #12 for Northwind Bakery.
Fixed 3 of 4 pins on staging, in one pull request:
- #14 Shortened the signup button so it fits on phones
- #15 Swapped the hero photo for the new one
- #17 Changed "Contact" to "Book a call"
#16 handed back: there are two menus on the page, which one?
Review the pull request
Example
A client sends 26 comments on the staging site of a Webflow build. You confirm 19 in scope and mark four as extra work. Twelve of the in-scope pins are text, image and spacing changes, so you add them to the Claude queue and press Fix all in Claude. Claude fixes eleven on staging and hands one back: “there are two menus on this page, which one?” You check the eleven, answer the question, publish, and move on to the seven changes that need you.
How to get good results from AI on client feedback
- Send the small, clear changes: copy, images, links, colors, spacing and simple layout. Keep new features and redesigns for yourself.
- Give the AI context it can't see. A short note like “match the card above” or “use the H2 style” saves a round of guessing.
- Always work on staging or a branch. A fix you can check is worth more than a fast one.
- Batch the changes. One pull request for a round of feedback is easier to review than twenty.
- Let the AI say no. A tool that hands back what it isn't sure about is safer than one that guesses.
Questions
Which AI tools does it work with?
Claude (on the web, desktop and mobile), Claude Code, Cursor and VS Code. Each connects in one step from the Integrations page and signs in through your browser.
Does Scopepin run the AI or charge for it?
No. The AI is your own Claude or Cursor account, on your own plan. Scopepin holds the feedback and tracks what happens to each pin; it never runs an AI on your behalf.
Can the AI change my live site?
No. It works on your staging site or in a pull request and never publishes a site or merges code. You check every change before it goes live.
Does it work with Webflow?
Yes. Connect Webflow in Claude, and Claude edits your staging site through it. For sites built in code, such as Next.js, WordPress themes or static sites, Claude opens a pull request in your repository.
Can it fix feedback automatically as it arrives?
No, and that's on purpose. Pins wait in the queue until you press Fix all in Claude, so a person always decides what the AI works on. You can choose to add pins to the queue when you confirm them in scope.
What does the AI see?
Only the pins you send: the client's comment, your note, the page address, the pinned element's code and text, and the screen size and browser. Form fields are masked in snapshots.
What if the AI gets it wrong?
You see what it changed and a link to check it before anything goes live. If a change isn't right, send the pin again with a note, or fix it yourself. Pins are never resolved until you resolve them.
Is it free?
Yes. The Free plan fixes up to 50 pins a month, one at a time, on one project. Starter removes the monthly limit, and Pro and Agency add the Claude queue, which sends a whole round of feedback as one batch.
More ways agencies use Scopepin
Let AI fix the small stuff. You publish.
Free for one project, with unlimited clients and reviewers.