How do you collect small website changes months after launch?

JangDongHyek — Mon, 07 Sep 2026 14:43:13 +0000

Disclosure: this is product research for a local prototype built with AI assistance. AI also helped draft this question.

I’m investigating how freelance web developers collect small change requests while maintaining client sites after launch. The question I’m trying to answer is whether there is a recurring problem that existing tools leave unresolved.

Email and chat let a client use a familiar channel, but a request still needs enough context to identify the page and the change. A visual feedback tool can attach a request to a location. A self-hosted tool gives the developer control over the installation, while also leaving them responsible for running it. I’m interested in which of those tradeoffs actually matters in maintenance work.

If you maintain client sites, could you describe one recent example?

Where did the request arrive, and what extra information, if any, did you need before making the change?
Does your current free or paid tool handle this well? If something gets in the way, is it missing context, keeping old requests accessible, price, or something else?
Would running a small feedback tool on your own server solve a problem for you, or add maintenance you would rather avoid?

I’ve found free self-hosted alternatives already, so avoiding a subscription is not enough by itself to justify another tool. Experiences where the current setup works well are useful too. Please leave out client names, private URLs, and account details.

DEV Community: JangDongHyek

How do you collect small website changes months after launch?