WEB & DESIGN AGENCIES
The project should not stall because the logo files never arrived.
Design agencies lose weeks waiting. Waiting on brand files, on copy, on the one approval from the client’s partner who is on vacation. We connect discovery, asset collection, scope, approvals, revisions, launch, and retainers so the waiting is visible and somebody is chasing it.
A day that will sound familiar
Week five of a six-week website build
The homepage mockup is finished. It has a gray box where the logo goes, because in week one the client sent a screenshot of their logo from social media and the vector files are “with the guy who did it.” The copy for the services page is a document the client’s marketing person started and stopped. The designer has moved on to the about page to stay useful. The account manager sends the third reminder for the files, from memory, because there is no list anywhere of what the client still owes.
Round two of revisions came back this morning as a nine-minute voice note and four screenshots with circles drawn on them. Two of the requests are in scope. One is a new page. One undoes something the client approved in round one. The account manager has to sort out which is which, write it all up, and price the new page, while the launch date on the contract stays exactly where it was. In the same hour a retainer client emails asking why the blog post they sent ten days ago is not live. It is in someone’s inbox.
Five workflows
What changes for web and design agencies.
-
01Discovery
TodayAn intro call, then a questionnaire that half the clients fill in, then a second call to cover what the questionnaire was supposed to.
ConnectedThe questionnaire is attached to the inquiry, and the sections that decide the project, pages, existing site, brand assets, and who approves, are completed before the call is booked. The record shows what is still missing before anyone dials.
-
02Asset collection
TodayAssets are requested by email in whatever order they come to mind. Reminders go out when someone notices the gap.
ConnectedA request list is built from the scope: logo files, brand guide, photos, copy per page, logins. The client sees the list. Reminders go out until each item is in, and the project shows which deliverable is blocked by which missing file.
-
03Scope and approvals
TodayThe proposal describes pages loosely. Approvals happen in email, and “looks good” from anyone at the client counts as one.
ConnectedThe scope lists pages, rounds, and deliverables. Each stage has a named approver, the approval is recorded on the record, and the next stage does not open without it.
-
04Revisions
TodayFeedback arrives as voice notes, screenshots, and phone calls. Rounds bleed into each other and nobody agrees which round this is.
ConnectedFeedback for each round goes to one place. Every item is marked in scope, out of scope, or a reversal of an earlier approval. Out-of-scope items open a change request, and the client can see how many rounds are left.
-
05Launch handoff and retainers
TodayThe launch checklist is in the developer’s head. After launch, retainer work is whatever arrives by email.
ConnectedThe launch checklist is opened from the scope: domain, hosting access, forms tested, redirects, handover of logins. After launch the retainer opens with its own request queue, hours, and renewal date, and every client request is logged and acknowledged.
Where it breaks
Four places the process usually fails.
- THE GRAY BOXA finished design waiting on one file. The designer moves to something else, the client thinks the project is on track, and the week is gone before anyone counts it.
- THE VOICE-NOTE ROUNDFeedback that has to be transcribed before it can be sorted, and sorted before anyone knows whether it is free. The account manager becomes the bottleneck.
- THE APPROVAL THAT WAS NOT ONESomeone at the client said “looks good.” It was not the person who signs. The real approver sees it in round three and starts over.
- THE RETAINER INBOXPost-launch work lives in email. Requests are answered in whatever order they are seen, and the client’s idea of the hours used never matches yours.
One handoff, before and after
Round two feedback arriving as a voice note
- A nine-minute voice note and four screenshots land on the account manager’s phone.
- She listens twice, writes notes, and pastes them to the designer in chat.
- The designer does all of it, including the new page, because nobody flagged it as new.
- The new page ships unbilled and the launch slips a week.
- The client hears about the new date on the day it was supposed to go live.
- The feedback is posted to round two on the project, whatever form it arrived in.
- The account manager tags each item: in scope, out of scope, or a reversal of round one.
- The new page opens a change request with a price and the effect on the launch date.
- The client approves it or drops it. The scope, the invoice, and the launch date update together.
- The designer works from the approved round-two list, and the client can see the new date.
What to track
The numbers that tell you whether it is working.
We do not promise a percentage. We show you which numbers to watch, and we measure them before and after.
- Days each project spends waiting on client assetsThis is usually the biggest single reason a six-week build takes eleven.
- Feedback items arriving outside a roundEach one is a change that will be argued about later.
- Change requests issued versus out-of-scope work delivered unbilledThe difference is the new pages you built for free.
- Approvals recorded per stage, by the named approverAn unrecorded approval is one you will be asked to prove.
- Launch dates moved per projectEvery move is a conversation you would rather not have, and a sign the waiting was invisible until too late.
- Retainer requests open past their agreed turnaroundRetainer clients leave over small delays, quietly, at renewal.
Questions web and design agencies ask us
01What does AI for a web design agency do that a project tool does not?
It chases. The project tool holds a list of what the client owes. Nobody in it sends the third reminder, notices the launch is at risk because the copy is late, or flags that a voice note contains a new page. We build that layer on top of the tools you already use, so the account manager is not the one remembering.
02Our clients send feedback however they want. Can we still make them use a form?
You do not have to. Feedback can keep arriving as voice notes, screenshots, and calls. What changes is that it gets logged to the round and sorted, so the client keeps their habits and you keep the record.
03Who decides what is out of scope?
Your account manager does, in about ten seconds per item, with the signed scope next to it. The work we remove is the transcribing, the writing up, the pricing document, and the follow-up. The judgment stays with your team.
04We are a two-person studio. Is a launch checklist really something to build?
At two people, the launch checklist is the difference between a clean handoff and an evening spent finding the hosting login. Small studios lose more time to the forgotten step than large ones, because there is nobody to catch it.
05Can this run our retainers as well as the builds?
Yes. Each retainer has its hours, its turnaround, and its renewal date on the record. Requests are logged and acknowledged when they arrive, usage is visible to both sides, and the renewal conversation starts on a date rather than when the hours run out.
START WITH ONE PROCESS
Bring us the website build that is stuck waiting on the client.
We will map how it works today, find where it waits or gets repeated, and tell you whether fixing it is worth the effort.
- The mapOne process in your business, drawn end to end on a single page
- The waitEvery place it stalls or gets repeated, and who is carrying it today
- The answerWhat fixing it would take, or a straight answer that it is not worth fixing