Summary
Offer small-business clients a website care plan where change requests are as easy as sending an email. A Grok Bot running the Site Manager template handles the routine work: it confirms each request, edits the right site, deploys, verifies the live page, and replies Done. The owner keeps the client relationships, approves what matters, prices the bigger work, and runs the business.
The pitch to clients is simple: email your change, and it gets done, with a confirmation when it starts and a Done email with the link when it’s live. The pitch to the owner is just as simple: the small requests stop eating the day.
Who it's for
The operator
- Small web agencies and studios that maintain sites after launch
- Freelance web designers with a roster of past clients
- Hosting providers that want a care plan to sell alongside hosting
Their clients
- Small businesses whose sites change often but in small ways: hours, menus, prices, staff, events, photos
- Restaurants, shops, clinics, trades, studios, nonprofits
- Owners who don't want to learn a site builder or wait on a ticket queue
The offer and tiers
A monthly website care plan. Every tier includes a dedicated email address per site, a confirmation on every request, and a Done email with the link. Tiers differ by how much review happens and which extras are on.
Essentials
Auto-deploy for small text and photo edits. One requester address. Monthly uptime, SSL, and broken-link check.
Managed
Approve-first or preview-first on every change. The client's team can request. Scheduled changes, a per-client change log, and before-and-after screenshots.
Partner
Everything in Managed, plus priority handling, a monthly change digest and review call, quote-flagged project work, and SEO and accessibility touch-ups.
Define a “small change” in writing for every tier, for example: edits to existing pages, swapping images, adding an item to an existing list. New pages, new features, and redesigns are quoted separately.
How it runs day to day
- A client emails their site's address. The bot checks the sender, confirms, and restates the request.
- It edits that one site, builds, and tests. In Auto mode it deploys and verifies; in Approve-first mode it emails the owner a request ID and waits; in Preview-first mode it sends the client a preview.
- Requests that look like projects are flagged to the owner to quote instead of being done.
- Failures are reverted, and both the client and the owner are told.
- Once a week, the owner gets a digest of every change across every client, which doubles as the record for billing.
- Once a month, the health check runs and reports only what needs attention.
What the owner still does
- Relationships and sales. Onboarding calls, renewals, and anything that needs a human conversation.
- Approvals. One-word replies for approve-first clients, and the go-live for anything brand-sensitive.
- Quotes and projects. Pricing and doing (or overseeing) the work flagged as too big for a small change.
- Exceptions. Failed builds, unclear requests, and anything the bot hands back.
- Money, contracts, and anything in their name. Invoices, terms, and any client email sent as a draft for review.
- Turning up autonomy. Moving a client from approve-first to auto once the track record is there, one client at a time.
Pricing approach
Common models, which can be combined. Choose figures from your own costs, the time you save, and what your market will bear.
A flat monthly fee per site with an included allowance of small changes. Predictable for both sides; the most natural fit.
Requests priced by size, such as small, medium, or quoted. Good for clients who change their site rarely.
A lower monthly base with a set number of included requests, then a per-request rate beyond it.
Care folded into a hosting plan as a premium level, so it's one line on the invoice.
A discount for paying a year up front, which improves cash flow and retention.
Price on outcomes the client feels: speed, no ticket queue, a confirmation every time. Publish a fair-use limit, and revisit pricing after the first 90 days using real request volumes.
Costs to consider
- Grok Bot plan and usage for the bot that runs the sites
- Hosting, domains, and SSL for each client site, if you provide them
- Repository and deploy services (for example a git host and a static hosting platform)
- The owner's time for approvals, quotes, exceptions, and onboarding
- Contracts and terms of service, and professional or cyber liability insurance
- Bookkeeping, payment processing, and taxes; confirm the details with an accountant
Risks and safeguards
| Risk | Safeguard |
|---|---|
| A wrong or unwanted edit goes live | Approve-first or preview-first for new and brand-sensitive clients; verify before Done; reply UNDO to roll back; backups on every deploy |
| Someone pretends to be the client | Allowed-sender list plus required email authentication; mail from anyone else wakes nothing |
| Malicious instructions hidden in an email | Emails are treated as requests for that one site only; links are never opened; secrets are never revealed |
| One client's request touches another site | One routine and one source folder or repo per site |
| Scope creep | A written definition of a small change; big requests are flagged for a quote |
| A build or deploy fails | Automatic revert, and both client and owner are told |
| Client expectations on speed | Promise “usually the same day,” not a guaranteed turnaround; put response times in the terms |
| Depending on one platform | Keep every site's source in your own repos so the work is never locked in |
Go-to-market
- Start with existing clients. Offer the care plan to sites you already built or host; they already trust you.
- Demo it live. On a call, have the client email a small change and watch it go live before the call ends.
- Upgrade path from hosting. Present it as the next level up from a hosting-only plan.
- Referral partners. Local IT shops, marketing consultants, and accountants who hear “our website is out of date.”
- Show, with permission. Before-and-after examples and change logs from real clients, shared only with their consent.
First 90 days
Set up and prove it
Import the template, connect deploys, and run it on your own site. Onboard one or two friendly clients in approve-first mode. Write the small-change definition and the terms.
Roll out to existing clients
Offer the tiers to your current roster. Collect feedback on every request. Move clients with a clean track record to auto mode.
Refine and grow
Turn on the weekly digest and monthly health checks. Adjust pricing using real volumes. Start outreach to new clients with a live demo.
What to measure
Requests handled per site, time from email to Done, the share that needed approval or were flagged for a quote, reverts and failures, owner hours spent per client, and client renewals. Set your own targets once you have a baseline.
A business plan concept for discussion, not financial, legal, or tax advice.