I've been running client sites with a coding agent for a while now. The next step was obvious: stop being the glue between every tool and let a small team of bots do the boring daily stuff, while I keep the decisions.
This is the setup I'd use if I was starting a web design agency from scratch today with Grok Bot. Each bot has one job, runs on a schedule, and every client site lands in one place on novence.ai. I'll keep it practical: which bots, what they own, the actual routine prompts, and where you (the human) stay in the loop.
No made up numbers in here. Where I show a figure it's labelled as an example.
The bits that matter for an agency:
The docs say it plainly: give work its own bot when it has its own sources, schedule or approval needs. That maps really well to an agency.
Four bots is plenty to start. One owner per step, no overlap.
| Bot | Owns | Never does |
|---|---|---|
| Growth | Finding leads, scoring them, drafting outreach | Sends anything without approval |
| Builder | Building sites in Astro, deploying previews and production to Novence | Touches DNS on a live client domain without approval |
| Ops | Uptime, forms, broken links, monthly reports, renewals | Emails clients directly |
| Content | Blog posts, case studies, client page updates from briefs | Publishes to a client site without a preview link first |
Write each bots role into its profile. Short and blunt works better than long. Something like:
You are Builder for my web agency. You build small business sites in Astro
and host every site on novence.ai. You deploy previews freely. Production
deploys, custom domains and anything that touches a client's DNS need my
approval first. Keep every client in /workspace/clients/<slug>/.
The one connector that makes this whole thing work is deploys. Builder needs to ship a site without me copying files around.
Two options, both fine:
MCP. Add the Novence MCP server as a custom connector:
https://api.novence.ai/mcp
Then the bot can create sites and deploy straight from a tool call.
CLI. Builder has a terminal on its computer, so this works too:
cd /workspace/clients/smith-plumbing
npm run build
npx novence deploy ./dist
I use the CLI inside build scripts and MCP when I'm asking for one off stuff in chat. Every client on one host means one place to check, one bill, one set of redirect and form rules.
Other connectors worth adding: your email (Gmail or Outlook) for drafts, GitHub if you keep client sites in a repo, and whatever you use for invoices.
This runs weekday mornings. It's the one I'd tune the most.
Every weekday at 9am:
1. Search for local businesses in <city> in these trades: plumbers,
physios, cafes, accountants. Skip any I've already logged in
/workspace/leads/leads.csv.
2. For each one, open their website in the browser. Note: is it
WordPress, is it mobile friendly, does it load slow, is the
contact form broken, is the copyright year old.
3. Pick the 5 with the clearest single problem. For each, write one
line on the problem and attach a screenshot.
4. Draft a short outreach email for each (under 80 words, one concrete
issue, no pitch deck). Do NOT send. Put the drafts in front of me
for approval.
5. Append everything to leads.csv.
The key line is step 4. Growth drafts, I approve. Cold email under my name is not something I want a bot doing on its own, and Grok Bot is built to ask first before sending anyway.
This one isn't on a timer. Growth or I hand it a brief when a client says yes. I save it as a skill so it runs the same every time:
When I give you a new client brief:
1. Create /workspace/clients/<slug>/ from my Astro starter.
2. If they have an old WordPress site, export the pages and posts,
convert to content collections, and build an old-to-new URL map
into public/_redirects.
3. Put editable stuff (hours, prices, team, specials) in
/data/*.json so the client can change it later from /edit
without needing me.
4. Use the native Novence form for the contact page.
5. Build, then deploy a preview with npx novence deploy.
6. Run the pre-launch checks: every page 200, every redirect 301,
form submits, no wp-content URLs left in dist/, Lighthouse
mobile above 90.
7. Send me the preview URL and the check results.
8. Only after I say "ship it": deploy to production and walk me
through the custom domain DNS records. Do not change DNS yourself.
I've written up most of those individual steps before (redirect maps, forms, client editing). The point here is chaining them so a bot does it end to end and stops at the two places where a mistake actually costs something: going live and DNS.
First business day of the month, for every client:
On the 1st of every month at 8am, for each site in
/workspace/clients/sites.json:
1. Load the homepage and contact page. Flag anything not 200.
2. Submit a test on the contact form and confirm it arrived.
3. Pull last month's Novence analytics: visits, top pages, top
referrers, 404s.
4. Add any real 404s to that site's _redirects and redeploy the
preview. List them for me.
5. Write a 3 bullet summary per client in plain english. Use only
numbers from the analytics. If a number is missing say so,
never guess.
6. Give me all the summaries as drafts. I'll send them.
Example of what comes back (example data, not a real client):
smith-plumbing (example)
- 1,240 visits, up from 1,100. Most from Google Maps.
- "Emergency plumber" page is the top page again.
- 2 broken old links fixed with redirects, preview ready.
That no-guessing line in step 5 is important. Without it a model will happily round things or fill gaps.
I'd add this bot once there's 5+ clients. It writes blog posts or service pages from a brief, commits them to the client's folder, deploys a preview, and sends me the link. Clients who like editing their own stuff use /edit, everyone else gets content done by this bot with me reviewing.
This is the whole list for me:
Set these as ask first rules in each bots instructions, and check the approval prompts actualy show up before you trust it with a real client.
The bots don't replace the part of the job that's actually about people: picking clients, talking to them, deciding what's worth building. What they take is the daily grind of finding leads, building to a checklist, deploying, checking, and writing reports. That's a lot of hours back.
If you want to try the deploy side first, point your coding agent at https://api.novence.ai/mcp or run npx novence deploy on any Astro build and go from there.