What to tell a client while their AI build is in progress
Clients get nervous after signing because they see nothing happen. Here is the four-line weekly update that fixes it, how to explain waits nobody controls, and when the approach breaks down.
Lumina··7 min read
Tell the client three things once a week: what is done, what is waiting on someone and who, and the next date you will check in. Send it as a short written note, not a call, and most clients stop asking "is it ready yet?" Below: what goes in the note, how to talk about the waits nobody controls, and when this approach breaks down.
Why do clients get nervous during an AI build?
Because after they sign, they see nothing. A roofer who bought an AI receptionist has no truck in the driveway and no crew. The work happens in a platform they never open. Two quiet weeks feels like a vendor who took the money and moved on.
AI agency software for sales and fulfillment
Custom fulfillment from our engineering team, live AI demos, and a client portal, all 100% white-labeled.
The nervousness is not about the technology. Clients just cannot tell whether anyone is working. A weekly note answers that question before they ask it, and it costs you ten minutes.
It also protects your price. A client who feels ignored starts relitigating the deal. A client who gets a plain Thursday update does not.
What goes in the weekly update?
Keep it to four lines. This is the template I would use:
Done this week. One or two concrete items. "Your hours and service list are loaded. Your brand colors are applied."
Waiting on. Name the person. "Waiting on you: the calendar login. Waiting on the carrier: text message registration."
Not started yet, and why. "Test calls start after your calendar is connected."
Next check-in. An actual date.
The "waiting on" line does most of the work. It turns a vague delay into a visible queue with names on it, and it moves the client from watching to acting. If the item is theirs, they now know it is theirs. We covered the intake side of this in the client intake checklist, and the reminder cadence for slow responders in what to do when a client is slow to send info.
Send it from your agency address, under your brand. The platform also gives each client a branded portal with status, assets and next steps (see how it works), so point them there too. The email tells them it is moving. The portal is where they check without asking you.
How do you explain the waiting nobody controls?
Name it on day one, before it happens. The clearest example is text messaging. If a build sends texts, such as a missed-call text-back, the carrier side has a registration step with review times that no agency, and no platform, can speed up.
So do not promise a text feature date. Promise a range and a trigger: "Texting goes live after the carrier approves the registration. It usually takes about a week, sometimes more. Voice and chat can go live before then."
Twilio's page also says most failures happen at campaign registration, and the causes are mundane: vague descriptions, sample messages that do not match the description, no working website link, and consent that cannot be verified. That is a reason to collect clean business details early, which is exactly what your intake step is for. Our post on testing before go-live covers what to check once the pieces are in.
What should you say when there is nothing new?
Say that, in one line. "No change this week. We are waiting on the carrier. Next update Thursday the 20th." That is a complete and good update. Skipping it because there is nothing to report is the mistake. The note is not information, it is proof of attention.
Do not pad it or invent progress. Clients can tell, and a long note about nothing reads worse than a short honest one.
What do you promise, and what do you leave out?
Promise process, not outcomes. You can promise a weekly note, a named owner for each open item, and a date for the next one. You cannot honestly promise a go-live date until the client's inputs are in and any outside approvals are done.
Leave out detail the client cannot use. They do not care which node you rearranged. They want to know whether the thing will answer their phone, and by when.
One more rule: put the lead time in writing before you sell it. Whoever builds the deliverable should give you a range, and you should repeat that range in the proposal. Every build you order from Lumina Sales is priced on a 30-minute call (how that call works), and that call is the right moment to ask what the build depends on. The full sequence from signature to portal is in what happens after the close.
When is a weekly update the wrong move?
Three cases.
If the client is mid-crisis, say they just lost a technician or a storm is hitting their season, a templated note reads as tone deaf. Send a two-line message that says you have it handled and will not bother them until it matters.
If a client wants to be hands-on, weekly may be too slow. Some owners want to watch the portal daily and message you on Tuesday. Match them. The template is a floor, not a ceiling.
And if you run many builds at once, a hand-written note per client stops scaling once you spend more time writing them than selling. This is a real limit of the approach. Hold the four-line format, write from a saved template, and batch them in one block on the same day. If you cannot hold that, the answer is fewer concurrent builds, not longer notes.
This is also not a fix for a build that is actually stalled. If the problem is that the client has gone silent, updates will not unstick it. That needs the escalation sequence, not a status note.
FAQ
How often should I update a client during an AI build?
Weekly is a good default, on the same weekday so it becomes a habit on both sides. Add a message the same day anything blocks the work or finishes a major piece, such as a successful test call.
Should I send updates by email, text, or portal?
Email for the weekly note, since it makes a record you can point back to. The portal for self-service status. Text only for time-sensitive asks, like a login code or a same-day question.
What if the client asks for a go-live date I cannot guarantee?
Give the dependencies and a range. "Voice goes live when your calendar is connected and test calls pass, about a week after you send the login. Texting waits on carrier approval." A conditional date you keep beats a fixed date you miss.
Do I tell the client when a delay is my fault?
Yes, in the "waiting on" line, with your name on it and a new date. Owning it in one sentence costs less than the client discovering it later.
What do I do if the client never replies to the updates?
Keep sending them. A note that went unanswered still shows you kept them informed, which matters if the project drifts. If an open item is theirs and it is blocking, switch to the reminder sequence.
Next step
Take your most recent signed client and write the four-line note for this Thursday. Put one named item in "waiting on" and a real date in "next check-in." If you do not have a branded place to send them yet, the Lumina Sales onboarding and portal setup is $49 a month, and you can start here.