Skip to content
← Journal
AI Assistants11 min read21 Oct 2026

An AI Workflow for Web Design Agencies: Copy, Access and Approvals

How a web design agency can track page copy, client access and staged design approvals in one blocker list, while designers, developers and clients keep every approval and launch decision.

VDVarnan EditorialAI-assisted editorial production
An AI Workflow for Web Design Agencies: Copy, Access and Approvals — AI workflow for web design agencies

An AI workflow for web design agencies works best with one narrow job: keeping track of what stands between a finished design and a launched site. Page copy, brand assets, hosting access and client approvals arrive from different people, through different channels, on different days. The project manager needs one place that shows which of them are still missing.

This guide explains how to set up that workflow for a US agency running several builds at once. It covers the permissions the assistant needs, an illustrative stalled project, the approval process, a launch checklist and the mistakes that make coordination tools noisy. Designers, developers and clients keep every creative and launch decision.

What an AI workflow for web design agencies should track

A web build already has a project plan, and the workflow should not duplicate it. Its job is narrower: notice when a task cannot move because an input from someone else is missing, record who owes it, and make that gap visible before it delays the next stage.

Most blockers fall into four categories: content, assets, access and approvals. Content means page copy, product descriptions and legal text. Assets means logos, photography and brand files. Access means hosting, domain, analytics and plugin accounts. Approvals means signed-off design rounds, scope decisions and the final go-ahead.

Each blocker needs five fields: the page or task it affects, what is missing, who owes it, when it was requested and where the request lives. With those fields, a project manager can sort by launch date and see which builds are at risk without opening a single inbox.

This is the same follow-through model behind the AI assistant for web design agencies. Like the wider AI business assistant, it sits on top of the agency’s existing tools rather than replacing them, and it treats every gap as something a person resolves.

The workflow reports what is missing, never what is acceptable. Whether a revised homepage is good enough, or whether supplied copy needs editing, stays a judgment for the designer and the account lead.

Permissions and prerequisites before connecting anything

Start with the project register. For most agencies that means a ClickUp space, an Asana board or a shared Google Sheet where each build has its pages, stages and owners. If the register is incomplete, the assistant cannot tell a missing input from a task nobody created.

Next, decide which sources it may read. A typical scope covers the project register, one Google Drive folder per client, the Figma files under active review, the internal Slack channel for each build and the Gmail threads tied to that project. Anything outside that scope stays invisible to it.

Google’s Drive API lets an app list and search files and folders using query parameters, but what it can see still depends on the access the account was granted. Scope the folder, not the whole drive. A shared client folder is enough to check whether a copy document has been filled in.

Client systems need extra care. The workflow should track whether a hosting or domain invitation was granted, never the password itself. Ask the client to invite the agency account through the service’s own user management, and keep credentials in a password manager the assistant cannot read.

Finally, name the approval owner for each category: the project manager for content and access reminders, the lead designer for revisions, the account lead for scope questions and the client for launch. A blocker without an owner is just a note.

An illustrative exception: the services page that never got copy

Consider an illustrative build: a marketing site with a homepage, an about page, a services page and a contact page. Design is approved, and the developer is working through pages on the WordPress staging site in order.

The services page task moves to its build stage in ClickUp. The linked copy document in the client’s Drive folder still holds the headings from the kickoff template and nothing else. The client’s marketing lead believes the founder is writing it; the founder believes the agency is.

The workflow notices the mismatch between the task stage and the empty document. It marks the page as blocked on content, records the original request date from the kickoff thread and drafts a short reminder that names the page, the sections needed and the person who agreed to supply them.

The project manager reads the draft, softens one line and sends it from Gmail. In the Gmail API, a draft is an unsent message carrying the DRAFT label, and sending it is a separate step. That separation is where the human approval lives.

At the next review point the document is still empty. The workflow does not send a second reminder on its own. It moves the item up the project manager’s review list, and the project manager decides to raise it on the weekly client call instead.

Meanwhile the developer moves on to the contact page, and the launch readiness list shows one content blocker with a named owner. Nobody discovers placeholder text in the days before launch.

The approval process for design rounds and launch

Approvals are where agency projects most often lose their thread, because feedback arrives in several places at once. A client might comment in Figma, reply to an email and mention a change on a call, all about the same round.

The workflow handles this by tying all feedback to a named round. When the client is asked to review the second homepage concept, the request, the Figma frames shown and the date comments are due are recorded in ClickUp as that round.

New Figma comments are grouped by frame and split into questions and change requests. The lead designer decides which become revisions, which need a conversation and when the round goes back to the client. The assistant records those decisions; it does not make them.

A round closes only when a named client contact approves it in writing. Silence is not approval, and neither is a passed deadline. If the approval is ambiguous, such as a thumbs-up on a superseded version, the round stays open and the project manager is asked to confirm.

Launch follows the same rule. Before the planned date, the workflow assembles a readiness list: pages on placeholder copy, unapproved rounds, missing access and open scope questions. The client signs off with that list in front of them, and a developer moves the site live.

The assistant never deploys a live site. It has no publishing rights on WordPress, so every public change has a developer behind it and a client approval on record.

A practical checklist for the first workflow

Use this ordered checklist when setting up the workflow on a single live project. Finish each step before starting the next one, because later steps depend on the records the earlier ones create.

  1. Pick one active build with a real launch date and several open inputs.
  2. List every page and its stage in the project register, with one owner per task.
  3. Create a Drive folder per client and link each page task to its copy document.
  4. Record each access request as its own task, with the service, the client contact and the date requested.
  5. Define what closes each blocker: a filled document, a granted invitation or a written approval.
  6. Name the approval owner for reminders, revisions, scope questions and launch.
  7. Set the review point when the project manager reads the blocker list, such as the start of each working day.
  8. Run the workflow alongside the existing process, compare its list with what the team already knows and fix the gaps before adding a second project.

If a step feels hard to complete, treat that as useful information. Unclear ownership is often the real blocker, and no assistant fixes it on its own.

Trade-offs and what the workflow should not do

A blocker list is only as current as the records behind it. If designers keep feedback in private messages, or the register is updated once a week, the list will lag. The workflow rewards teams that already keep their project tool honest.

It also adds a review step. Every reminder is a draft someone has to read, and every scope flag is a note someone has to answer. For a small studio with one project at a time, that overhead may not pay off. The value grows with the number of parallel builds and client contacts.

Some work stays out of scope by design. The workflow does not generate layouts, write final site copy, choose a design direction or estimate effort. It does not send client messages, approve revisions or publish to WordPress. It is a delivery coordination layer, not an AI website builder.

Agencies coordinating freelancers or partner studios can extend the same pattern through team update chasing and follow-up automation. Add each new source only after the first project runs cleanly.

Common mistakes when automating agency follow-up

Connecting everything at once. Giving the assistant every Slack channel and the whole Drive produces a long, noisy list. Start with one project and the few sources that actually hold its inputs.

Treating a reply as a resolution. A client answering an email does not mean the copy arrived or the design is approved. The blocker closes only when its defined condition is met and recorded.

Letting reminders send themselves. Automatic nudges feel efficient until one reaches a client at the wrong moment. Tone matters in agency relationships, so keep a person on every outgoing message.

Tracking credentials instead of access. A workflow that stores client passwords creates a security problem it was never meant to solve. Track invitations and grants, and leave secrets in the client’s own tools.

Skipping the manual fallback. Write down how a project manager would run the same process without the assistant. If nobody can explain it, the workflow is hiding a process the agency never defined.

The broader AI assistant for marketing agencies applies the same ownership rules to retainers and campaign work, where the inputs differ but the approvals still belong to people.

Frequently asked questions

What does the assistant need access to?

It needs read access to the project register, the client’s Drive folder, the Figma files under review and the project’s Slack channel and Gmail threads. Discovery confirms which of these can be connected on the agency’s accounts. It does not need, and should not have, client passwords or publishing rights on any live WordPress site.

Who approves external messages?

A person on the agency team approves every message that reaches a client. Usually the project manager handles content and access reminders, while the account lead handles scope questions. The assistant prepares drafts with the page, request and owner filled in, but the wording, timing and decision to send stay with that person.

What happens when information is missing?

The item stays open and visible until its defined condition is met. If a copy document is empty, an invitation has not arrived or an approval is unclear, the workflow records the gap, its owner and its source. It escalates by moving the item up the review list rather than by sending more messages.

How do we test the first workflow?

Run it alongside the existing process on one active build. Compare its blocker list with what the project manager already knows, note anything it missed or flagged wrongly, and adjust the register or the closing conditions. Add a second project only after the list matches reality for a full review cycle.

Can it publish the finished site?

No. Publishing is a developer’s job, done after the client signs off on launch in writing. The workflow can prepare the readiness list and record the approval, but it has no permission to deploy, publish or overwrite content on a live site. That keeps one accountable person behind every public change.

Next steps

Pick one build that is close to launch and list everything it is waiting on. Give each item an owner, a source and a clear condition that closes it. That list is the core of the workflow, whether or not any tool is connected yet.

The AI assistant for web design agencies applies the same structure across active projects, with designers, developers and clients keeping every approval. A strategy call can look at how the agency chases copy, access and sign-off today, and which tools can be connected.

Want an assistant built around how your business runs?

Book a strategy call →

Build an assistant around your business.

Discuss one recurring workflow, the tools it uses and the decisions your team needs to approve.

Book a strategy call