Most client work does not end at launch. It turns into a long tail of small requests: change the opening hours, swap this photo, fix a typo, update a price, add a sentence to the About page. Each one takes minutes, and each one arrives at an inconvenient time, with a short message and no context.
AI assistants are well suited to this kind of work, and used carelessly they are just as capable of making a mess of it. The difference is mostly workflow, not the tool. This is the workflow that keeps the speed and loses the risk.
What to hand to an assistant
Give it work that is small, clear and easy to check. Typos and grammar. Rewording a paragraph to be shorter or friendlier. Making headings across several pages consistent. Writing alt text for images. Updating the same detail, such as an address or a phone number, everywhere it appears. Turning a client’s rambling email into the two clean sentences it was trying to be.
These share a quality: you can tell at a glance whether the result is right. That is the test for delegating anything. If checking the work is as slow as doing it, keep it.
What to keep for yourself
Anything with a price, a legal claim, a medical or financial statement, or a promise to customers needs a human who is accountable for it. Assistants state wrong things in a confident tone, and a made-up opening hour or a wrong price on a live site costs a client real money.
Structure also stays with you. New layouts, new features, integrations and anything that changes how the site is built are the work you are paid to do well. An assistant can help you draft them, but it should not be the one deciding.
Brief it like a new colleague
The quality of the result depends mostly on the quality of the brief. A one-line request produces a generic answer. A short, specific one produces something you can use.
Say who the audience is and what the business sounds like. “This is a family-run dental practice. The tone is warm and plain, no jargon.” Say what must not change, such as names, prices and legal wording. Say how long the result should be. And give it the actual current text instead of asking it to guess, since an assistant that has not seen the page will invent something plausible.
If you have the same client often, keep a short style note for each one: voice, words they like, words they hate, things never to say. Paste it in at the start. It turns a generic assistant into one that sounds like the client.
Keep the change in a draft
The most important habit is where the change lands. An assistant should never be the last step before something goes live. Whatever tool you use, make sure its output goes to a draft, a branch or a pull request first, and that a person looks at it before it is published.
This is the idea behind connecting an assistant to a tool like Baton through MCP. The assistant can read the pages and write the new wording as drafts, and the live site does not change until the owner reviews it and presses Publish. You get the speed of the assistant without handing it the keys.
A five-point review before anything goes live
Read the result out loud. It catches awkward phrasing faster than reading silently, and it is how a client would hear it.
Check every fact against the client’s own words: names, numbers, dates, prices, opening hours, addresses. Do not accept any figure you cannot trace to something the client told you.
Look at what changed and nothing else. A good draft shows exactly which words moved. If the assistant touched more than you asked, discard it and tighten the brief.
Check the page itself, not only the text. Longer or shorter wording can break a layout, wrap a button onto two lines or push a section out of place.
Keep a way back. Every publish should be saved as a version that can be restored in one step, so a mistake is a thirty-second fix instead of an emergency.
Be honest with the client
You do not need to announce every tool you use, but you should never pass off an unchecked draft as finished work. Clients are paying for your judgement, and the review is where it lives. If a client asks, a straight answer works: you use assistants to speed up the routine edits, and you check every change before it is published.
Some clients will want to try it themselves, which is fine. Give them the same rule you follow: the assistant writes, a person decides.
Where this leaves your time
Done well, the long tail of small edits shrinks from a constant interruption to a short batch you clear once or twice a week. That frees real time for the work that clients actually value you for, and it keeps the small requests from souring a good relationship. The tool is the easy part. The discipline of draft first, review second and publish by hand is what makes it safe.