How to Collect Client Feedback on Web Projects (Without the Email Chaos)
We build a lot of websites at Grow My Business, and for a long time the hardest part of a project was not the design or the development. It was collecting clean feedback from the client. Feedback would arrive as a screenshot with an arrow in an email, a note in a text that said “make the blue bit bigger”, and a phone call about a heading without saying which page it was on. We would then spend longer working out what the client meant than actually making the change.
Over dozens of builds we settled on a process that cut our revision rounds roughly in half and made launches far less stressful. Here is how we collect client feedback on web projects now, and why we changed.
The real problem is not the client, it is how feedback is collected
When feedback is scattered across email, chat and calls, three things go wrong. Comments lose their context, so you cannot tell which page or element they refer to. Feedback trickles in over a week instead of arriving in one go, so you never quite know when a round is finished. And nothing is ever formally signed off, so “I thought we agreed on this” becomes a conversation you have after launch.
None of that is the client being difficult. It is the tools. Ask someone to describe a visual change in words and you will get a vague description. Ask them to point at it and you will get something you can action.
Step one: one review link, not ten email threads
Instead of asking clients to describe changes, we send a single link to the live site and let them leave comments pinned directly onto the page, on the exact element they mean. No account, no login, nothing for them to install. The comment sits on the button or the heading in question, with the page and device recorded automatically.
We use our own client feedback tool, Reviso, for this, in part because we could not find anything that let clients comment without a login and kept the data on our own server. Full disclosure: Reviso is a product we build. But the principle matters whatever you use. Get the feedback pinned to the page, in one place, and most of the guesswork disappears.
Step two: action feedback in one batch
Once the feedback is in one place, we work through it in a single pass rather than reacting to each comment as it lands. Batching is faster, it stops you half-fixing things, and it gives the client a clear sense of progress as items are marked done. A round has a start and an end, rather than dribbling on for a fortnight.
Step three: close every round with a recorded sign-off
This is the step most agencies skip, and it is the one that saves the most grief. Before we move on, we ask the client to formally approve the page, and we keep a timestamped record of that approval tied to the specific page. A verbal “looks good” is not sign-off. A documented approval protects both sides and ends the round in a clear place.
If you want a starting point, we published the exact process we use as a free client sign-off checklist. It works regardless of which tools you use.
Why we keep the feedback on each site
One deliberate choice: our client feedback is self-hosted, so every comment, screenshot and email stays on each WordPress site rather than on a third-party platform. For an agency handling client data, that means fewer processors to worry about, no per-seat fees as projects scale, and no risk of a tool disappearing and taking the project history with it. It is not the right trade-off for everyone, but for us the control is worth it.
The result: fewer rounds, faster launches
Tightening this one part of the process changed our projects more than any design tweak. Feedback is specific, it arrives in one round, and every launch ends with a clean approval on record. Revisions stopped being the thing that dragged a project past deadline.
If your web projects keep stalling in the feedback stage, start with the collection method, not the client. Give them one link, one place to comment, and a clear point where the round is signed off. The rest gets a lot easier from there.