AI for Client Work

Dear reader,

Client work can change in one short message.

The signed plan says five pages. A new message asks for seven. The client may think it is a small change. You may already see two more days of work.

It can be hard to answer when you are tired or annoyed. An AI app can help you sort the facts and draft calm words. It cannot remember a meeting it did not attend. It cannot decide what you owe. It cannot set your fee.

This book shows you one simple habit: find the record, ask for a draft, and check every claim.

You do not need special computer skills. You can use a phone or iPad. Move one page at a time.

Your agreement is the record. The app is only a writing helper. You stay in charge.

Stop here: Think of one client message you need to answer this week. Do not paste it yet.

You will use an AI app to help make one clear client message from facts you already have.

Mara has a signed outline for five web pages. A later message asks for two more. She does not ask the app who is right. She first finds the signed page count.

Tap these steps

1. Pick one client job.
2. Find the small part of the record that matters.
3. Copy a short line from this book.
4. Paste it into ChatGPT, Claude, or Gemini.
5. Add your facts where you see square brackets.
6. Check the draft against the real record.
7. Send only words you approve.

The app may help you sort, shorten, or soften a message. It may not agree to work, set a price, promise a date, or speak for the client.

Watch out: A smooth answer can still be wrong.

Stop here: Find your signed outline, approved email, or other real record.

These five words will help you use the book.

• Prompt: The words you type or give to an AI app.
• Copy box: The cream box in this book. Copy its short lines into the app.
• Paste: Put copied words into the message area of the app.
• Check: Compare the answer with your agreement, notes, numbers, and messages.
• Official app: The real ChatGPT, Claude, or Gemini app from its maker. Check the maker's name before signing in.

Square brackets show where your own words go. For example, replace [page count] with five pages.

Never put a password, access key, private ID number, or secret client file into a chat. Follow your contract and workplace rules. Use only the small excerpt you are allowed to share.

The app drafts. You check. You decide.

Stop here: Open the official app you plan to use. Do not upload a full client folder.

What you are doing: You are finding the exact line that shows what the job includes.

Mara sees ideas, promises, and “maybe later” notes in one thread. She needs to separate them.

Tap these steps

1. Open the signed plan or approved outline.
2. Copy only the lines about the item in question.
3. Add the new request below those lines.
4. Ask the app to show the difference.
5. Compare its answer with the source.

Do not: Let an idea from a meeting become a promised item.

Next: Move any item with weak support into “not clear.”

Stop here: Do not write to the client until each claim points to a real line.

What you are doing: You are asking for missing facts without reopening settled work.

The price and page count are set. Access, the final decision-maker, and review dates are not.

Tap these steps

1. Write down what is already settled.
2. List what you still need to start.
3. Ask for short questions.
4. Remove any question that offers extra work.
5. Choose the three questions that matter most.

Do not: Ask broad questions such as “What else would you like?” That can invite a new job before you discuss time or cost.

Next: Put the three must-answer questions first. Save the rest for a follow-up.

Stop here: Check who truly has power to approve. Do not let the app guess.

What you are doing: You are naming progress and delay without blame.

Mara delivered the home page. Two product pages slipped while a review was open. She wants the note to stay calm and true.

Tap these steps

1. List what is done.
2. List what changed.
3. Write the real next action.
4. Add a date only if you can keep it.
5. Ask for a short note.

Do not: Let “waiting for the client” become an attack. The app does not know anyone's motive.

Next: Read the changed line alone. Keep dates and actions. Remove blame and excuses.

Stop here: Check every date before you send.

What you are doing: You are making extra work visible before discussing money.

Ben agreed to build a site in two languages. The client now asks for a third. He first needs a clean list of added work.

Tap these steps

1. Copy the original scope line.
2. Copy the new request.
3. Ask the person doing the work what it adds.
4. List open questions.
5. Discuss price only after the list is checked.

Do not: Let the app call the request small, large, easy, or unreasonable. Those words can push the discussion before the facts are ready.

Next: Check the added work with the person who will do it. You choose the fee and date later.

Stop here: Do not send a price based on a guessed task list.

What you are doing: You are arranging your own hours and showing the math.

Ben has hour ranges for three tasks. A fourth task has no estimate. A neat total must not hide that blank.

Tap these steps

1. Write each task on its own line.
2. Add only hours you or your team supplied.
3. Add your confirmed rate if needed.
4. Ask the app to show each calculation.
5. Recheck the math outside the chat.

Do not: Accept a guessed rate, hour count, tax, discount, fee, or middle value. A correct total can still rest on a made-up number.

Next: Use a calculator to check every row. Delete any total built from a missing number.

Stop here: An hour range is an estimate, not a promise.

What you are doing: You are sorting comments without agreeing to extra work.

A marked PDF has typo fixes, new ideas, and two comments that are hard to understand. They do not all belong in the same pile.

Tap these steps

1. Number the comments.
2. Add the scope lines that matter.
3. Ask for three groups: in scope, possible change, and not clear.
4. Check each group yourself.
5. Reply without promising action yet.

Do not: Change “please review” into “we will do this.” Sorting a request is not accepting it.

Next: Use words such as “noted,” “reviewing,” and “needs confirmation” until you decide.

Stop here: Ask about vague comments before planning the work.

What you are doing: You are separating decisions from talk and ideas.

After a call, Mara's notes and two messages tell different stories about a color choice. Repetition does not make an idea approved.

Tap these steps

1. Gather the permitted notes and messages.
2. Remove private material that is not needed.
3. Ask for confirmed, open, and conflicting items.
4. Require exact supporting words.
5. Send the list to the real decision-makers.

Do not: Treat a suggestion, silence, or repeated idea as final approval.

Next: Send the draft record to the people who can correct it. Their answer becomes part of the record.

Stop here: The app's list is not an approval.

What you are doing: You are saying what stops without guessing the contract terms.

Ben's client says, “We need to pause.” Two files are done. One is half built. “Pause” does not always mean “end.”

Tap these steps

1. Copy the client's exact request.
2. List finished and unfinished work.
3. List what you will stop now.
4. Note any files or access that need care.
5. Leave money and legal terms for a human check.

Do not: Turn a pause into a cancellation. Do not invent a refund, fee, right, threat, storage promise, or restart date.

Next: Read the agreement or ask the right adviser before adding contract terms.

Stop here: Send only the practical facts you understand.

What you are doing: You are checking proof and permission before sharing a client success story.

Mara has good screenshots. She has no measured result and no permission to name the client. A polished story would be too early.

Tap these steps

1. List the work that was truly delivered.
2. List results you can prove.
3. Copy only real client quotes.
4. Write the permission you have.
5. Mark everything else as private or unproved.

Do not: Invent praise, results, quotes, names, permission, or a promise that someone cannot be identified.

Next: Ask for proof and permission as two separate checks.

Stop here: Delivery proves that work was made. It does not prove that the work caused a result.

What you are doing: You are showing what is finished and what still needs a handoff.

Ben's main work is done. One login transfer and two source files remain. A warm goodbye should not hide those loose ends.

Tap these steps

1. List accepted items with proof.
2. List anything you still owe.
3. List client next actions only when they are known.
4. Check file names and access steps.
5. Give each open item a real owner or mark it open.

A close-out note can use four short headings:

• Delivered
• Remaining handoff
• Client next steps
• Open items

Do not say the client is happy, the project is complete, or all results were reached unless the record supports those words.

Watch out: A polished summary can make unfinished work disappear.

Next: Finish, assign, or date each handoff item. Confirm that private access has moved safely. Never put passwords in the chat or in the close-out note.

Stop here: Send the goodbye only after the practical handoff is clear.

A first answer may sound sure even when it is wrong. Use one short correction. If the basic facts are wrong, start again.

Tap one repair

• It added work: “Use only the scope lines I pasted. Mark the rest not clear.”
• It accepted a request: “Describe the request. Do not agree to it.”
• It made up a number: “Delete every number I did not supply.”
• It hid a delay: “State what changed, when it changed, and the next real action.”
• It blamed someone: “Remove motives and judgment. Keep facts, dates, and actions.”
• It created an approval: “Show exact proof of approval or mark it open.”
• It sounds legal: “Use plain business words. Do not add rights or contract terms.”
• It invented praise: “Delete results, quotes, and praise that lack proof.”

Check the new answer against the original record. Do not keep polishing a false answer. Better wording does not make a false claim true.

Watch out: Each rewrite can make a mistake sound more believable.

Stop here: If the structure is wrong, open a new chat with the smallest safe excerpt.

Use this plan for one live client issue. You may do it in one sitting or over several days.

1. Find the record. Open the signed scope, approved outline, or confirmed message. Find the smallest part that answers today's question.
2. Name the change. Write one plain sentence about what is different. Do not add blame.
3. Check the work. Ask the person doing the work what the request adds. Do not guess hours or effort from the client's wording.
4. Draft the message. Use the copy box that fits the job. Add only facts you are allowed to share.
5. Check the draft. Check names, dates, work items, quotes, numbers, approvals, and promises.
6. Make the decision. You choose whether to agree, ask, price, pause, or decline. The app does not choose.
7. Save the record. Send through the normal client channel. Keep the final message where the project record belongs.

Watch out: A side message may be missed later, even if its words are perfect.

Stop here: Choose the one client issue you will handle first.

Read the source, not just the smooth draft.

1. Scope: Can you point to the line that supports what is included?
2. Numbers: Did every hour, rate, fee, date, total, and percent come from you?
3. Approval: Was there a real approval, or only a discussion?
4. Quotes: Are quoted words exact, needed, and safe to use?
5. Promises: Did the draft promise work, timing, access, storage, or results you did not approve?
6. Next step: Is it clear what happens next without a guessed owner or date?
7. Place: Are you sending it through the normal project channel?

Now read it as the client. Is the boundary clear without knowing your private frustration?

Read it as the person doing the work. Did you promise something they cannot deliver?

Read it aloud once. Shorten any sentence that makes you lose the point.

Watch out: Good tone cannot fix a false date or unsupported promise.

Stop here: Send only when the facts, decision, and next step are yours.

When client work changes, remember these five lines:

1. Find the signed or approved record.
2. Show the old work beside the new request.
3. Ask the worker what the change adds.
4. Let the app draft calm words.
5. Check every fact and make the decision yourself.

The app did not attend kickoff. It did not hear the promise. It cannot know which message carried approval unless you show the record. It also cannot know your cost, your risk, or the working relationship as well as you do.

Use it for a draft, a list, or a clearer sentence. Do not use it as a witness, manager, lawyer, or signer.

If the record is weak, say the point needs confirmation. That is better than filling the gap with a likely answer.

If you feel angry, wait before pasting. Write three lines for yourself:

• What was agreed?
• What changed?
• What will I do next?

Then use only the facts.

Stop here: Keep the record. Check the draft. Make the decision.

These sources support the writing habits in this book. They do not prove who is right in a client dispute.

OpenAI and NBER — “How People Use ChatGPT”

The 2025 study reports that writing is a large part of work use. Much of that writing use involves changing text supplied by the user. This supports starting with real source words instead of asking the app to invent the record.

https://openai.com/index/how-people-are-using-chatgpt/

https://www.nber.org/papers/w34255

Anthropic — “Be clear and direct”

This guide advises giving clear instructions. For long or complex material, it also advises putting the source material before the final request. Its reported test result is guidance, not a promise about your project.

https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/be-clear-and-direct

Google Cloud — “Prompt design strategies”

This guide explains practical parts of a clear request, including the goal, background, limits, and desired answer shape.

https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/prompts/prompt-design-strategies

Research may help you use an app with more care. Only your real agreement, messages, hours, approvals, and records can support your client claim.