A client who does not understand the process will assume the worst one. Usually that a robot is editing their site at night.
The three sentences
- “An agent read your site and the sources you connected, and wrote down one change it thinks will help.”
- “Nothing touches your website until I approve it, and the record says that I did.”
- “If you say no, nothing ships, and the reason stays with the item.”
Those three hold when every change arrives as a pull request you merge. They answer the worry without overselling anything.
1. an agent read your site and the sources you connected, and wrote
down one change it thinks will help
2. nothing touches your website until I approve it, and the record
says that I did
3. if you say no, nothing ships, and the reason stays with the item
The questions, with answers
Ridgeline Roofing, a fictional client, first review call.
| Question | Answer |
|---|---|
| Did AI write the copy? | An agent drafted it from your own business context. I read it and changed two lines before it went anywhere. |
| Could it publish by itself? | No. The publishing step needs my approval, recorded against my account. |
| What if it is wrong? | We revert it, because the previous version is in the record. |
| Does it learn my business? | It reads the brand document you approved. It does not train on your site. |
| What does it cost? | My fee is fixed each month. Research calls spend credits, and each one shows its cost before it runs. |
| Can I see what changed? | Yes. Every shipped change has a date, the pages it touched, and what happened after. |
| What if I disagree? | You say no, and the item keeps your reason so it does not return next month. |
The two answers that must stay short
The approval answer and the revert answer. Those are the worries behind every other question, and a long answer reads like a defence.
Acceptance: the meeting went well when
- the client can say who approves a change
- the client knows where to see what shipped
- the client knows the monthly fee is separate from research credits
- nobody in the room believes an agent can publish on its own
- the next decision has a date
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| The client asks about “the AI” generally | The process was never named | Name the three steps: reads, proposes, approves |
| They ask for a ranking guarantee | Sales language met reality | Offer the record of what changed instead |
| They worry about data leaving | Unclear which sources read what | Walk the connections list, page by page |
| They want to approve every line | Fair, and expensive | Agree which categories need review |
| They think it is free | Credits were never mentioned | Show one priced call, and the allowance |
Two objections to expect
“So you are not doing the work any more.” The honest answer is that the reading and the first draft moved, and the judgement did not. Offer to show the queue from last month, with the changes you declined.
“What if it changes my prices by accident?” Show the approval record and the previous values. A price change needs the same approval as any other, and the revert is one pull request.
Both objections come from the same place: the client wants to keep control without checking every line. The record is what buys that.
Limits
Some clients will prefer the work described as ordinary maintenance. That is fine, and it is accurate.
The selling point is the process: a decision, an approval and a record, whoever or whatever prepared the change.