Skip to content
Fox photography representing the AI Prompts section

AI Prompts

AI Client Communication Prompts

Five prompts for the client messages that are awkward to write: delays, extra requests, unpaid invoices and clear project updates.

  • 5 copy-ready prompts
  • Freelance and agency
  • Calm and clear

The prompts

Prompt 1

Write a clear project update

Regular progress updates that clients actually read.

Write a project update for [client name].

Project: [name]
Period covered: [dates]
Completed: [list]
In progress: [list]
Next: [list]
Blockers or decisions needed from the client: [list]
Anything that has changed in scope, cost or timeline: [details or "nothing"]

Format:
- A one-sentence status at the top (on track, at risk, delayed).
- Short bullet lists under each heading.
- A clear "what I need from you" section with dates.

Keep it under 200 words. Do not add progress I did not list.

Why it works: Put the status first. Clients with a busy week will read only the top line.

Prompt 2

Respond to a scope change request

The client asks for something extra and you need to protect your time without damaging the relationship.

A client has asked for this addition:
"""
[paste request]
"""

Original agreed scope: [summary]
Extra time it would take: [estimate]
Extra cost: [amount or "to be quoted"]
Effect on deadline: [none or new date]

Write a reply that:
- Confirms I understand the request.
- Explains that it is outside the original scope, without sounding rigid.
- Offers options: add it for the extra cost, schedule it as phase two, or leave it out.
- Is friendly and under 150 words.

Why it works: Always give a choice. Saying "no" with no alternative feels like a refusal; offering options feels like service.

Prompt 3

Chase a late payment

An invoice is overdue and you need to be firm without being hostile.

Write a payment reminder for an overdue invoice.

Client: [name]
Invoice number: [number]
Amount: [amount]
Due date: [date]
Days overdue: [number]
Reminder number: [1st, 2nd, final]
Payment details or link: [how to pay]

Tone for this reminder: [friendly / firm / final notice]

Include:
- The invoice details in one line.
- A direct request for payment by a specific date.
- An invitation to tell me if there is a problem.

Do not make legal threats. Keep it under 100 words.

Why it works: Have a three-step schedule ready: friendly, firm, final. It removes the emotion from late payments.

Prompt 4

Deliver bad news early

A deadline will be missed or something has gone wrong.

I need to tell a client that [problem, e.g. the delivery will be late].

What happened: [honest, brief explanation]
What it affects: [deliverables, dates, cost]
New realistic timeline: [date]
What I am doing to fix or limit it: [actions]
What I need from the client: [decisions, patience, nothing]

Write a message that:
- States the problem in the first two sentences.
- Takes responsibility where it is mine, without over-apologising.
- Gives the new plan with dates.
- Ends with a clear next step.

No excuses, and no blaming other people.

Why it works: Clients forgive delays communicated early far more readily than those they discover on the due date.

Prompt 5

Wrap up a project and ask for a testimonial

A project is done and you want a review and possibly repeat work.

Write a project wrap-up message to [client name].

Project: [name]
What I delivered: [list]
Results or outcomes so far: [real, specific results]
What happens next: [handover, support period, maintenance option]

Include:
- A brief thank-you that mentions something specific.
- A short summary of what was delivered and how to use it.
- A request for a short testimonial, with 2-3 simple questions to answer.
- A soft mention that I am available for future work.

Keep it warm and under 180 words.

Why it works: Ask for the testimonial while the result is fresh, and make it easy by giving questions to answer.

Client communication is most of the job

Clients rarely leave because the work was poor. They leave because they felt uninformed, surprised or ignored. Clear communication is a service in its own right.

Regular beats long

A short update sent on a predictable day builds more trust than a long message sent when something goes wrong. Choose a rhythm, such as a Friday summary, and keep it brief: what is done, what is next and what you need.

Hard messages, easier

  • Lead with the news. Do not bury a delay in the third paragraph.
  • Bring a plan. A problem with a proposed solution is far easier to receive.
  • Be specific on dates. "Soon" invites worry; "Thursday" gives certainty.
  • Keep a written record. Confirm decisions in writing after calls.
  • Stay calm. Draft the first version, step away, then edit.

Set expectations at the start

Many problems vanish when the first conversation covers response times, who approves work, how changes are handled and when payment is due. Put those answers in writing and refer back to them.

Related resources

Win the work with the Freelance Proposal Prompts, run the business with the Freelance Developer Roadmap, and sharpen your writing with the Communication Skills Roadmap.

Frequently asked questions

How often should I update a client?

Weekly works for most projects. Agree the rhythm at the start and send updates even when progress is slow.

What should I do if a client does not pay?

Send a polite reminder, follow with firmer ones, and pause work where your contract allows. For large sums, seek professional or legal advice.

Keep going

Related resources

Hand-picked pages that pair well with this one.

Roadmaps

Freelance Developer Roadmap

Go from building projects to getting paid for them: skills, first clients, pricing, contracts and keeping work coming in.

Open