All plays › Agencies and marketing

Agencies and marketingGrok Bot

A week or two of change order back and forth done in about 45 minutes with no person on it

Picked and checked by Olga Pearson, host of The Practical AI Show · Published

Result

self-reported

A change order he says would probably have been a week or two long process ("Here's your $3,000 change order") happened with no human in about 45 minutes, and he woke up to it. He says that one Slack message was maybe $1,000 of cost he isn't paying, it happens several times a day, and it's saving them tens of thousands of dollars a month.

Justin Sainton runs Zao, a small WordPress agency. Grok Bot listens to every client Slack channel and decides whether a message is something it can act on. When a ski magazine client asked questions about a custom classified system, it spun up the work in Cursor agents, opened a pull request, ran it through a QA agent, compared the result to the original request and drafted the reply to the client in Slack. With clients 12 hours ahead, he says that by the time he wakes up, the work is often done, reviewed and approved by the client. He still checks in and reviews, and he chose not to charge the client a change order for it.

Who did it

Justin SaintonZao (WordPress agency)Justin Sainton on the WPDev YouTube interview · Oct 10, 2026

Try it now

  1. Give the bot read access to your client Slack channels and your code repo.
  2. Have it sort each message: something it can act on, or just a hello.
  3. For real requests, let it build the change on a separate branch and open a pull request.
  4. Run every change through a QA check against the client's original request.
  5. Have it draft the reply to the client with what changed, and review it before it goes out.
Copy-paste prompt
Watch our client Slack channels. When a client asks for a change you can act on, build it on a new branch, open a pull request, test it against their original request and draft a reply explaining what changed. Ask me before merging anything or sending the reply.

Make it run every week

A play works once. Turn it into a routine in three small steps:

  1. Run it once and check the result yourself.
  2. Give your AI a schedule. Tell it when to run this play (every week, or every month) and to message you with what it found before you act.
  3. Keep a log. One line per run: what was checked, anything flagged, what you did.

See how owners turn plays into systems →

What to watch out for

Self-reported in a video interview. The $1,000 and "tens of thousands of dollars a month" are his own estimates of cost he isn't paying, not an audit. In his setup the reply can go to the client before he has looked at it. Safer version: have the bot hold every client reply and every merge until you approve it. Build it with Page: a client portal page where each request and its status live in one place.

Did it work?

PageMotor keeps this site free.