A script goes on the site, and has to come back off
Feedbucket collects feedback by embedding a snippet in the page. That is what makes the comments land accurately, and it is also two jobs bolted onto every project.
The first is at the start. Before a client can leave a single comment, the snippet has to be added to the site, which means access, a deploy, and sometimes waiting on whoever owns the hosting. A review that should take five minutes to set up takes as long as the next release window.
The second is at the end, and it is the one that actually bites. The snippet has to be taken out before the site goes live. Nobody schedules that, it sits in a launch checklist, and the failure mode agencies report is not forgetting to add the script. It is forgetting to remove it, and shipping a client's live site with a feedback widget still attached to it.
There is also work you simply cannot take on. A prospect's existing site, a competitor page you want to mark up, an inherited build hosted by someone else: none of it can be reviewed, because you cannot put code on a site you do not control.

