Skip to content
be-human.ai
← Back to the journal

AI by industry

Superintelligence Prep for Web Design Agencies: Sites and Change Requests

Should your agency manage change requests, hosting records and handoff notes as one system? A plain guide to agent-readable sites from launch day.

Be Human typographic cover with the title: Superintelligence Prep for Web Design Agencies: Sites and Change Requests
Conceptual illustration created with AI · Be Human

For a web design agency, superintelligence preparation starts with records most teams already have but rarely organize: client change requests, hosting and domain details, and the handoff notes written at launch. Whether these should become a managed system depends on how many people touch each site and how much an agent would need to read before acting. Building every new site so an agent can read its structure, history and permissions from day one is the practical preparation, and it is mostly disciplined documentation done the same way every time.

Key takeaways

  • Change requests, hosting records and handoff notes are the three places agency knowledge usually disappears after launch.
  • Treat them as one managed system with an owner, a format and a review rhythm, not as scattered folders and inboxes.
  • Make every new site agent-readable at launch: a documented structure, explicit permissions, a reference to where secrets live and a change log that starts on day one.
  • Keep approval boundaries explicit. An agent may draft and stage a change, but a named person approves anything that touches live content, DNS, billing or customer data.
  • Start with one role and one observable success criterion, such as every open change request having a named owner and a recorded decision.

Why client changes are the real operating system

After launch, the work that decides whether a client stays confident is rarely the original design. It is the steady flow of small requests: replace a hero image, move a contact form, update opening hours, add a landing page for a campaign. Each request carries context that does not fit inside the request itself: who asked, which version was approved, what was refused and why, and which other pages depend on the change.

When that context lives in email threads and one designer's memory, it disappears the first time someone changes roles or a client forgets what was agreed. An agent is only as useful as the record it can read. A queue of change requests, with a status and a recorded decision for each, is the first thing worth making machine-readable. Agencies that run ongoing retainers feel this most, and the problem is close to the one managed service providers face when they hold memory for many clients, as described in managed service provider memory.

Should hosting records become a managed system?

Hosting records are the facts behind every action on a live site. They include which provider runs it, who owns the domain and when it renews, where backups are kept, which content management system and plugins are in use, and who holds access. Many agencies keep these in a password manager, a spreadsheet and the memory of whoever set up the server. That works until a renewal is missed or a plugin update breaks a form that nobody thought to test.

The question is not whether to write these facts down, because every agency should. The question is whether they should become a managed record that an agent can query and that a named person reviews. Use this guide to decide.

  • Keep a shared document if one person handles every site, changes are rare, and no automated process reads the records.
  • Move to a managed record once a second person edits sites, a renewal or backup has been missed, or a client asks who approved a change.
  • Require a managed record before any agent reads or drafts actions on hosting, domains or access, because the agent needs current facts and clear limits.

Access deserves its own rule. The OWASP authorization guidance treats access control as a check made on each request, based on the role and the resource, rather than on whether someone was trusted once. For hosting, that means staff and agents receive role-based access to what they need, the access is reviewed on a schedule, and nobody inherits a shared administrator login from an old project.

What makes a site readable by agents from launch

A site is readable by an agent when someone else, human or software, can find out what it is, what it depends on and what may change without asking. That is a design decision made at launch, and it is far cheaper than reconstructing it months later from screenshots and old emails. The agency does not need specialized tooling to begin. It needs a consistent place and a consistent format, which is what lets an agent read the record accurately.

Each new site should leave the agency with the following:

  • A site map that gives the purpose, owner and last approved version of every page.
  • An inventory of components: forms, booking or payment integrations, analytics tags, third-party scripts, and where each one is configured.
  • A rule for each content type, such as which edits a designer may publish and which need the client's written approval.
  • A credentials reference that says where secrets are held and who may request them, without containing the secrets themselves.
  • A change log that begins at launch, with each request, the decision and the person who made it.
  • A launch note listing what must not be touched, for example a legal disclosure block or a tracking tag that a campaign depends on.

With this in place, a new request can be checked against the site's own record before anyone touches the layout. Without it, every request depends on whoever remembers the last conversation.

Handoff notes an agent can actually use

Most handoff notes fail for one of two reasons. Either they declare the project complete and leave out the open items, or they run so long that nobody reads them. Good context is short, current and sorted by what the next person must decide. Anthropic's guidance on context engineering makes a related point for agents: the useful work is keeping the context small, relevant and up to date, rather than loading everything that might be useful.

A handoff note for a site should separate three things. First, what is settled, which becomes a fact an agent can rely on. Second, what is open and who owns each open item, which becomes a task with a name attached. Third, what is forbidden or needs approval, which becomes a boundary written in plain language.

Illustrative scenario: a studio hands a booking website to the operations lead at a salon. The note states that the service menu is final, that two gift card pages still await copy from the owner, that the booking integration stays with the studio until the owner accepts it in writing, and that any price change needs the owner's written confirmation. Later, a request to update a promotion arrives. The agent can see the price rule, route the request to the owner, and draft the promotional copy without touching the checkout settings.

The same discipline appears in other operations. Teams running stores beyond customer chat face it in ecommerce operations beyond customer chat, and engineering firms keep it in project memory.

Where agents stop and people approve

An agent that drafts a change is useful. An agent that publishes one to a live checkout without review is a liability. Set approval boundaries by consequence. Copy edits on a draft page can be drafted and staged. Anything that changes live pricing, legal text, DNS records, billing, or customer data needs a named person to approve it before it goes live.

Client-supplied text needs a specific precaution. A change request pasted from an email, a form submission, or a page copied from another website can contain instructions aimed at an automated reader. The OWASP prompt injection guidance advises treating such content as data to be evaluated, not as commands to be followed. Keep tool permissions narrow so that even a manipulated draft cannot reach the hosting panel or the billing settings.

How Be Human approaches this

Be Human starts with one defined role, for example a change-request agent for an agency's active client sites. The first engagement defines the memory the role may read, such as site inventories and the change log, and the tools it may call, such as a staging environment and a ticket queue. It also defines the actions that require approval and one success criterion the agency can observe, such as every open request having an owner and a recorded decision within the agency's own review cycle. Managed operations then cover monitoring, recurring evaluations of drafts against the approved scope, permission review, incident response when a site breaks, and controlled improvements to the role. The OpenTelemetry observability primer offers a useful vocabulary for the logs, traces and metrics that make those reviews possible.

Choosing the first task

Start with the record that is most often missing when something goes wrong, usually the change log or the handoff note for the site with the most traffic. Give it an owner, a format and a review rhythm, then decide whether an agent should read it, draft from it, or act on it. Each step should leave the agency with one role it can observe and one boundary it can explain to a client. If you want to find the first task worth handing to an agent, the free Be Human AI diagnostic is a practical place to begin.

Frequently asked questions

Does every web design agency need a managed system for change requests? Not necessarily. A shared document can be enough when one person handles every site and no automated process reads the records. The need grows when several people edit sites, when renewals are missed, or when an agent must read the records before it acts.

What should an agent be allowed to do on a client site? Usually drafting, staging and routing requests to the right person. Live publishing, pricing, legal text, DNS, billing and customer data should require a named approver. Permissions should be role-based and reviewed on a regular schedule.

Is it safe to let an agent read client emails and form submissions? It can be, with narrow permissions and a clear rule that submitted text is treated as data rather than instructions. The OWASP prompt injection guidance describes this risk in detail. An agent that reads untrusted text should not also hold tools that can change hosting or billing.

How do we know the agent is doing its job? Define one success criterion before the role starts, such as every open request having an owner and a recorded decision. Review a sample of drafts against the approved scope on a recurring schedule, and keep a log of decisions so that every change can be traced later.

Your next step

See where an AI agent fits in your company first.

Take the free Be Human AI diagnostic. A few questions about your work show which task to hand to an agent first, what it needs to know and where a person approves.

Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.

Less busywork. More room for you.

Bring us the work you wish you had time for.

Book a call to try a personalized AI agent free for 7 days ↗Or take the free AI diagnostic →