What to Do When a Client Stops Replying on an AI Project

What do you do when a client stops replying in the middle of a project? Send a short, specific follow-up that makes the next step easy, then escalate on a fixed schedule over about three weeks: a nudge at day three, a clear deadline at day seven, a pause notice at day fourteen and a written close-out at day twenty-one. Meanwhile, protect yourself by capping any costs that are running on your accounts and by recording exactly where the work stands.

Silence is rarely hostility. Clients get busy, lose track of who owes whom a decision, or feel awkward about a delay. The sequence below treats it that way, polite but not endless, and it works for freelancers and small agencies who build apps and automations with AI.

Why silence costs more on an AI project

On a traditional design job, a silent client mostly costs you time. On an AI-built app, several things can keep running without anyone looking at them:

• API usage. If a test version calls a model API under your key, a forgotten loop or a public demo link keeps spending. Our guide to setting spending limits for AI agents shows how to cap it.

• Hosting and subscriptions. Preview deployments, databases and paid tool seats bill monthly whether or not the client is engaged.

• Accounts in your name. If the project lives in your accounts, you carry the risk of anything that goes wrong while the client is away.

• Context. AI-assisted work moves fast, and a two-week gap means requirements, models and tools may have changed under you.

So the first move is not a message. It is a ten-minute audit of what is running and who is paying for it.

Step zero: the ten-minute audit

1. List every service tied to this project: model APIs, hosting, databases, domains, paid seats.

2. Set a spending cap or alert on each, or pause anything non-essential.

3. Write a short status note: what is done, what is blocked, what you need from the client, the date.

4. Save the last confirmed scope and the last message where they agreed to it.

Keep the note. It is the first paragraph of every message that follows.

Which kind of quiet is it

Update, 23 October 2026. Before you start the sequence, work out which kind of silence this is, because the right response differs. AI projects have their own version of the second row: clients often stall when asked to review a prototype or judge between model outputs, because they are unsure how to judge it. Asking "does this answer look right to you, yes or no?" gets a faster reply than "please review".

What to do when a client stops replying: the three-week sequence

Count days from your last unanswered message, and send each one through the same channel the client used before, plus email so there is a written record.

Day 3: the nudge

Make it easy to answer in one line. Avoid "just checking in", which asks for nothing.

Hi Sam, quick one to keep things moving: do you prefer option A (the calendar view) or option B (the list view) for the bookings screen? A one-word reply is enough, and I can have it ready for you to review on Thursday.

Day 7: the deadline

State the consequence without drama, and offer an easy out.

Hi Sam, I have not heard back on the bookings screen, and the next stage depends on it. If I have your decision by Friday 30 October, we stay on schedule for the 20 November launch. If now is a busy time, tell me and we can pick a new date together. Otherwise I will hold the project from Monday so I am not working on assumptions.

Day 14: the pause notice

This one should be formal, and it should come from the contract or the agreed terms, not from irritation.

Hi Sam, as I have not had a reply since 20 October, I am pausing work on the project from today, as per section 6 of our agreement. The build is saved and nothing is running that will cost you extra. When you are ready to continue, reply to this email and we will agree a restart date. Work completed so far will be invoiced on the existing milestone schedule.

Day 21: the close-out

Hi Sam, I have not heard back, so I am closing the project file today. Attached is the invoice for the work delivered to date and a handover note with where everything stands. If you would like to resume later, I am glad to discuss a new start date and any updated pricing.

Adjust dates and section numbers to your actual agreement. The examples above use an invented client.

Use AI to draft, not to decide

An AI assistant is handy for turning your status note into a message in the right tone, and for producing three variants of a nudge so you can pick the one that sounds like you. Give it the facts and the constraint, such as "friendly, one question, under 60 words". Do not let it send the messages for you, and do not let it soften the deadline into mush. A message that does not name a date and a consequence does not move anyone.

Fix it in the contract so it does not recur

Most of the pain here is avoidable with two clauses agreed before work begins: A third is worth adding: a kill fee clause that states what is owed if the client cancels outright rather than going quiet.

1. A response window. For example, the client agrees to give feedback within five working days, and the delivery schedule moves by the same number of days for each day they are late.

2. A pause and restart clause. If the client is silent beyond a set period, you may pause work, any running costs are billed to them, and a restart may carry a rescheduling fee.

Tie both to your payment schedule so the milestones you have already earned are not at risk. Payment milestones for an AI project covers structuring those, and how to handle scope creep on an AI project pairs well with the response-window idea. If the relationship ends and you need to hand things over cleanly, see how to hand over an AI-built app to a client.

When it is time to stop

If the sequence reaches day twenty-one with no answer, and the contract allows it, close the project file, send the invoice for completed work, and move on. If you are in the United Kingdom, the government publishes guidance on late commercial payments, and other countries have equivalents. If a large sum is at stake, get advice that fits your jurisdiction rather than relying on a blog post.

If the relationship is going wrong repeatedly, how to fire a client on an AI project is the longer treatment. For the wider business picture, the pillar guide on AI monetization strategies frames where client work fits.

Frequently asked questions

How long should I wait before following up with a client who goes quiet?

Three working days is reasonable for a first nudge, as long as it asks one specific question. Waiting a full week before saying anything usually lets small delays harden into long ones.

Should I keep working while the client is not replying?

Only on work that is clearly in the agreed scope and that does not depend on their decisions. Building on assumptions risks rework you cannot bill for. Pause what is blocked and say so in writing.

Can I charge a client for the time the project was on hold?

Only if your agreement says so. A pause or rescheduling clause makes this clear. Without one, you can usually still invoice completed work on the agreed schedule, but charging for waiting time is hard to enforce.

What if the client has paid a deposit and then disappears?

Check your agreement for what the deposit covers and whether it is refundable. Keep a record of the work done and the follow-ups sent, and take advice for your country if the amount matters.

Should I use AI to write the follow-up messages?

It is fine for drafting, since it saves time and can adjust tone. Review each message yourself, include a specific date and next step, and send it from your own account.