I build an AI agentAn AI agent keeps watching and takes routine steps you have tested and approved, while anything needing judgment comes to you. that follows up when client feedback is due. It keeps each request tied to the right item and version. A reply stops the reminders, but you decide what counts as approval.
Most of the setup happens in writing, on your schedule.
Write to meA draft is ready. The next part of the project is waiting on an answer. The request goes out, and the due date now lives in your head. The client may comment in the design tool or reply by email. They may call instead, while the old reminder still looks due somewhere else.
Someone says “looks good,” but nobody has pinned down which item or version they meant. A reminder goes out after the client already responded somewhere else. You can see the project and the sent email, but not one reliable answer to “Who owes what next?”
This is for businesses that send the same kind of work for client review across projects. You want the due date and next follow-up out of your head.
Your files and comments stay where they already are. I set up the follow-up. Revisions and the rest of the project stay with you. This works when you are waiting on one person, not when several people must approve in sequence.
I map what happens after work is sent for review. Your files and feedback stay where they are; I add the item, version, named responder, and due date around them. You decide when the request comes back to you. We agree on the reminder voice and timing before I build.
I build the agent and tracker, then test it with sample requests, including changes that should stop a reminder. With your approval, I send one real message by email and one through the other method while you watch.
After both contact methods work as planned, I give you the agent, tracker, guide, and recording in accounts you control. Then I remove my access.
The tracker keeps the item and version with the record that a response arrived. It also keeps track of the person you are waiting on and when the answer is due, so the next reminder does not ignore what already happened. The feedback itself stays where the client left it.
Nothing runs on its own at first. After you watch one routine request or reminder work, you can turn that step on or off. Any response stops what would follow.
Only a person at your business decides whether the named responder approved the current item or version and what happens next. When a response arrives, later reminders stop and the request comes back to you. You read and handle the feedback where it arrived. Silence never becomes approval.
You invite me into only the accounts needed for the build. I never ask for a shared password, and I remove my access when I hand it over. You keep the finished setup and everything needed to run it. There is no required retainer or subscription to me.
In the first design, changing the review link or version after a request was sent could rewrite its history. I removed that shortcut. The corrected workflow keeps the old request in the record and requires a separate request for the changed work.
The corrected design passed twelve sample requests and eighteen checks locally. This was not a live client setup or result.
$750 for this setup, paid in two $375 installments.
Founding rate for the first three clients across these services.
Write to meThe price covers one kind of client review. It tracks the item, version, named responder, and whether a response arrived; the feedback stays where the client left it. Before you sign, I confirm how responses from both contact methods are recorded. Clients hear from it by email and one other method chosen before work begins. You approve the reminder voice and timing. You decide which tested steps may run and get a record of what happened.The price also includes the written guide, recorded walkthrough, one round of changes, and 30 days of fixes after handoff.
Reading from another place or connecting another tool is separate work. So is contacting clients another way or giving the agent a new job. Your files and revisions stay where they are, along with the rest of the project. This setup follows one person's answer. It does not manage a chain of approvals.
$375 is due to begin. The second $375 is due after you approve the plan, before I build.If any part of the setup needs a paid account, I tell you the expected cost before you sign. That cost is separate from the $750, and the account stays yours.
Your client can keep leaving feedback where they already do, such as email or an existing review tool. Tell me what you use and I'll tell you plainly whether this setup fits.
The tracker records that a response arrived for the item and version. Later reminders stop, and the request comes back to you. You read the response where it arrived and decide whether it refers to the current version. You also decide what the feedback changes and whether it counts as approval.
You answer a short set of questions in writing and show me where the review request lives and where clients reply. Later, you review the finished setup and walkthrough. Once it is running, you step in when a response changes the work instead of checking every routine request or reminder.
It uses the client or project name and the item or version. It also uses the person whose response is due and a record of whether that response arrived. It does not read the feedback itself or the rest of the project. Before I connect it, I show you what the agent will read and which outside services will receive that information.
A few lines is enough. I’ll tell you whether this setup fits.
