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.
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.
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.
The published numbers also disagree, which is itself the lesson. Twilio's documentation says . Microsoft's guidance for its own service says . Different providers give different estimates, and both say "typically."