We wanted to get on with the changes.

In our studio, feedback came through project tools, email and shared documents. On one client project, we had more than 200 correction requests in Basecamp, with more arriving through Google Docs and email.

Before making a change, someone had to find the page, understand the comment and pass it on. A few days later, picking up the work could mean finding it all again.

This was before Voicedot. Making the correction was only part of the job. Getting it ready for someone else took work too.

We used Marvel to share visual designs and leave comments on them. Later, we began building working page mockups directly in code with coding agents.

We still needed to review the work together. But now the thing being reviewed was a real page, not a separate design file.

The conversation belonged on that page. One person could point and explain; the next could pick up the same comment and get to work.

Gabi is my wife and business partner. She uses Voicedot to review the websites we build in our studio.

In one review of our Holy Studio page mockups, she left 22 voice comments across four pages. The comments were attached to the parts of the pages she was talking about.

She could point and explain without preparing a separate document of screenshots. Her voice became text. I could read the comments and get on with the review.

I retrieved all 22 comments through Voicedot’s MCP connection in Codex, with the page and element details. The agent could organise the feedback while keeping it connected to the original comments.

Now I can discuss a point at the relevant view and bring that feedback into my agent. I have a starting point for the change, with the context already there.

We still choose what to change, ask questions and check the result. Voicedot keeps the explanation at hand while we do that work.

We want useful comments to lead to better work. That starts with making them easy to give and easy to act on.

People can speak or type. The team receives text. The conversation stays with the right place, and the same context reaches a developer or coding agent.

Make the changes. Finish the project. Move on to the next thing worth building. That is the point.