{"slug": "how-to-set-up-a-web-design-agency-run-by-a-team-of-grok-bots-every-site-on", "title": "How to set up a web design agency run by a team of Grok Bots (every site on Novence)", "summary": "A developer described a workflow for running a small web design agency with four scheduled Grok Bot agents — Growth, Builder, Ops and Content — each assigned a single role and held to approval gates for outreach emails, production deploys and client DNS changes. Client sites are built in Astro and hosted on Novence, with deploys handled either through the Novence MCP server or its CLI, and lead generation run on a weekday-morning schedule that drafts outreach for human approval rather than sending it.", "body_md": "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.\n\nThis is the setup I'd use if I was starting a web design agency from scratch today with [Grok Bot](https://x.ai/bot). Each bot has one job, runs on a schedule, and every client site lands in one place on [novence.ai](https://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.\n\nNo made up numbers in here. Where I show a figure it's labelled as an example.\n\nThe bits that matter for an agency:\n\nThe 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.\n\nFour bots is plenty to start. One owner per step, no overlap.\n\n| Bot | Owns | Never does | \n|---|---|---|\n| **Growth** | Finding leads, scoring them, drafting outreach | Sends anything without approval | \n| **Builder** | Building sites in Astro, deploying previews and production to Novence | Touches DNS on a live client domain without approval | \n| **Ops** | Uptime, forms, broken links, monthly reports, renewals | Emails clients directly | \n| **Content** | Blog posts, case studies, client page updates from briefs | Publishes to a client site without a preview link first | \n\nWrite each bots role into its profile. Short and blunt works better than long. Something like:\n\n```\nYou are Builder for my web agency. You build small business sites in Astro\nand host every site on novence.ai. You deploy previews freely. Production\ndeploys, custom domains and anything that touches a client's DNS need my\napproval first. Keep every client in /workspace/clients/<slug>/.\n```\n\nThe one connector that makes this whole thing work is deploys. Builder needs to ship a site without me copying files around.\n\nTwo options, both fine:\n\n**MCP.** Add the Novence MCP server as a custom connector:\n\n```\nhttps://api.novence.ai/mcp\n```\n\nThen the bot can create sites and deploy straight from a tool call.\n\n**CLI.** Builder has a terminal on its computer, so this works too:\n\n```\ncd /workspace/clients/smith-plumbing\nnpm run build\nnpx novence deploy ./dist\n```\n\nI 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.\n\nOther 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.\n\nThis runs weekday mornings. It's the one I'd tune the most.\n\n```\nEvery weekday at 9am:\n1. Search for local businesses in <city> in these trades: plumbers,\n   physios, cafes, accountants. Skip any I've already logged in\n   /workspace/leads/leads.csv.\n2. For each one, open their website in the browser. Note: is it\n   WordPress, is it mobile friendly, does it load slow, is the\n   contact form broken, is the copyright year old.\n3. Pick the 5 with the clearest single problem. For each, write one\n   line on the problem and attach a screenshot.\n4. Draft a short outreach email for each (under 80 words, one concrete\n   issue, no pitch deck). Do NOT send. Put the drafts in front of me\n   for approval.\n5. Append everything to leads.csv.\n```\n\nThe 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.\n\nThis 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:\n\n```\nWhen I give you a new client brief:\n1. Create /workspace/clients/<slug>/ from my Astro starter.\n2. If they have an old WordPress site, export the pages and posts,\n   convert to content collections, and build an old-to-new URL map\n   into public/_redirects.\n3. Put editable stuff (hours, prices, team, specials) in\n   /data/*.json so the client can change it later from /edit\n   without needing me.\n4. Use the native Novence form for the contact page.\n5. Build, then deploy a preview with npx novence deploy.\n6. Run the pre-launch checks: every page 200, every redirect 301,\n   form submits, no wp-content URLs left in dist/, Lighthouse\n   mobile above 90.\n7. Send me the preview URL and the check results.\n8. Only after I say \"ship it\": deploy to production and walk me\n   through the custom domain DNS records. Do not change DNS yourself.\n```\n\nI'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.\n\nFirst business day of the month, for every client:\n\n```\nOn the 1st of every month at 8am, for each site in\n/workspace/clients/sites.json:\n1. Load the homepage and contact page. Flag anything not 200.\n2. Submit a test on the contact form and confirm it arrived.\n3. Pull last month's Novence analytics: visits, top pages, top\n   referrers, 404s.\n4. Add any real 404s to that site's _redirects and redeploy the\n   preview. List them for me.\n5. Write a 3 bullet summary per client in plain english. Use only\n   numbers from the analytics. If a number is missing say so,\n   never guess.\n6. Give me all the summaries as drafts. I'll send them.\n```\n\nExample of what comes back (example data, not a real client):\n\n```\nsmith-plumbing (example)\n- 1,240 visits, up from 1,100. Most from Google Maps.\n- \"Emergency plumber\" page is the top page again.\n- 2 broken old links fixed with redirects, preview ready.\n```\n\nThat no-guessing line in step 5 is important. Without it a model will happily round things or fill gaps.\n\nI'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.\n\nThis is the whole list for me:\n\nSet 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.\n\nThe 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.\n\nIf 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.", "url": "https://wpnews.pro/news/how-to-set-up-a-web-design-agency-run-by-a-team-of-grok-bots-every-site-on", "canonical_source": "https://dev.to/lincchad/how-to-set-up-a-web-design-agency-run-by-a-team-of-grok-bots-every-site-on-novence-43j7", "published_at": "2026-11-21 00:06:08+00:00", "updated_at": "2026-11-21 00:12:31.279228+00:00", "lang": "en", "topics": ["ai-agents", "agent-protocols", "ai-tools"], "entities": ["Grok Bot", "xAI", "Novence", "Astro", "GitHub"], "also_reported_by": [], "takeaway": "Splitting agency work across four single-role bots with explicit approval gates — drafts before cold email, previews before client publishing, approval before production deploys or DNS changes — keeps a human in the loop on irreversible actions.", "recommendation": {"advice": "Give each bot one role with its own sources and schedule, and require human approval before any irreversible action like sending outreach, publishing to a client site or touching DNS.", "playbook": "agent-architecture", "playbook_url": "https://wpnews.pro/playbooks/agent-architecture"}, "alternates": {"html": "https://wpnews.pro/news/how-to-set-up-a-web-design-agency-run-by-a-team-of-grok-bots-every-site-on", "markdown": "https://wpnews.pro/news/how-to-set-up-a-web-design-agency-run-by-a-team-of-grok-bots-every-site-on.md", "text": "https://wpnews.pro/news/how-to-set-up-a-web-design-agency-run-by-a-team-of-grok-bots-every-site-on.txt", "jsonld": "https://wpnews.pro/news/how-to-set-up-a-web-design-agency-run-by-a-team-of-grok-bots-every-site-on.jsonld"}}