PageApprove
Click-to-comment feedback for website projects
I run a web development business, and one of the most annoying parts of client website projects has always been feedback.
Not the actual feedback itself, that’s fine. The messy part is where the feedback lives.
One comment comes through email.
Another comes through WhatsApp.
Someone sends a screenshot with a circle around half the page.
Then, on a call, the client says something like, “Can we just change that section near the top?”
And suddenly you’re trying to work out what page they were on, what device they were using, whether they were looking at the latest version, and whether that comment was already handled somewhere else.
The other problem is final approval.
A client might say the site is approved, but did they actually check mobile? Did they review the right page? Were there still unresolved comments? Was the approval just a quick “looks good” in a WhatsApp message?
That’s what pushed me to build PageApprove.
PageApprove is a lightweight website feedback and approval tool for freelancers, web developers, designers, and small agencies.
The idea is simple:
Clients get a review link, leave feedback directly on the website, check the required devices like desktop and mobile, and approve the project before launch.
I’m trying to keep it intentionally focused. I don’t want it to become another bloated project management tool. It’s not a CRM, not an invoicing system, not a full client portal.
The core promise is:
Collect clearer website feedback and capture client approval before launch.
The part I’m most interested in is device-aware approval. A lot of feedback tools focus on comments, but in real website projects, the question is often: “Did the client actually review this properly before approving it?”
That’s where PageApprove tries to be different.
I’ve also created a WordPress plugin for it, because a huge part of the target market builds and reviews WordPress sites.
Right now I’m launching with a simple lifetime access offer and trying to get the first real users using it on actual client projects.
I’d love feedback from other freelancers, developers, designers, and agency owners:
How do you currently handle client feedback and final sign-off before launching a website?
And more importantly, what part of that process still drives you mad?
1 Comment
I like that you're drawing a hard line around the product. Feedback isn't usually what delays launches—it's uncertainty about whether everyone actually reviewed the right version on the right devices before saying "looks good." Owning the approval step instead of trying to become another project management tool feels like a much clearer position.