5 Claude Prompts for Consultant Client Communication

<task>Turn these meeting notes into a structured follow-up email with action items, owners, and deadlines.</task>

<context>
Meeting: [e.g., Weekly project status meeting — Phase 2 of operational efficiency engagement]
Date: [e.g., Tuesday, March 4, 2026]
Attendees: [e.g., Sarah Chen (VP Operations, Client), Mark Davis (Director of Logistics, Client), Lisa Park (Engagement Manager, Our Team), James Wright (Analyst, Our Team)]
Duration: [e.g., 60 minutes]

Raw notes:
[e.g.,
- Reviewed warehouse process mapping results — client confirmed the 3 bottleneck areas we identified
- Sarah flagged that the union contract renewal is in June — any shift restructuring needs to be agreed before then
- Mark wants us to include the regional distribution center in scope — says same issues exist there. Discussed whether this is a scope change or covered by existing agreement — Lisa to review and propose
- Vendor demos for routing software scheduled: VendorA on March 10, VendorB on March 12, VendorC on March 14
- James needs access to the ERP cost data for the past 24 months — Mark will submit the IT access request
- Draft recommendations due to client March 21 — internal review on March 18
- Sarah asked if we can present findings to the full leadership team on March 28 — Lisa to confirm availability
- Next weekly meeting: March 11 at 2pm ET]
</context>

<instructions>
- Write a professional follow-up email suitable for sending to all attendees
- Structure: brief thank you, key discussion summary (4-6 bullets), decisions made, action items table, next meeting confirmation
- Action items should include: specific action, owner (by name), deadline, and any dependencies
- Tone: professional, warm, and action-oriented
- Keep the email concise — clients respect brevity
- Flag the scope question diplomatically — it is a business discussion, not a conflict
</instructions>

<format>
Professional email format. Use bullet points for the summary and a clear list format for action items. Total length: under 400 words.
</format>

<task>Write a weekly project status update email for our consulting engagement.</task>

<context>
Engagement: [e.g., Customer retention diagnostic — Week 4 of 6]
Client contact: [e.g., VP Customer Success]
Overall status: [e.g., On track — slightly ahead of schedule on data analysis, stakeholder interviews complete]

This week's accomplishments:
- [e.g., Completed all 18 stakeholder interviews — synthesized themes into 5 key findings]
- [e.g., Churn cohort analysis complete — identified the 90-day onboarding window as the primary driver]
- [e.g., Built draft customer health scoring model using product usage and support ticket data]

Next week's plan:
- [e.g., Finalize health scoring model with CS team input]
- [e.g., Begin drafting recommendations and implementation roadmap]
- [e.g., Schedule mid-point review with sponsor for Week 5]

Issues or risks:
- [e.g., Product analytics data for Q1 2025 has gaps — working with IT to reconstruct from backup. Impact: minor delay to health score validation, no impact to overall timeline]

Decisions needed:
- [e.g., Should the health scoring model include NPS data? CS team says yes, but the survey response rate is only 12%. Need your guidance on whether to include or exclude.]
</context>

<instructions>
- Write a concise, scannable status update email
- Use a RAG (Red/Amber/Green) status indicator at the top
- Accomplishments should highlight progress and value delivered, not just activity
- Next week should set expectations for what the client will see from us
- Issues should be presented with impact assessment and mitigation — never just a problem without a plan
- Decisions needed should be framed clearly with the options and your recommendation
- Keep under 300 words — sponsors appreciate brevity
</instructions>

<format>
Email format with clear section headers. Use color-coded status (green/yellow/red) and bullet points throughout.
</format>

<task>Draft a scope change communication for our client who has requested additional work beyond the original engagement scope.</task>

<context>
Original engagement: [e.g., Operational efficiency assessment of the warehouse division — $85,000 fixed fee, 8-week timeline]
Additional work requested: [e.g., Client wants us to also assess the regional distribution center and include it in recommendations. Estimated additional effort: 2 weeks, 1 additional consultant for 3 weeks, ~$30,000-$35,000 in additional fees]
Relationship context: [e.g., First engagement with this client — want to build a long-term relationship. They are a potential source of 2-3 additional projects this year]
Our position: [e.g., Happy to accommodate but need to formalize the scope change to protect the engagement economics and set the right precedent]
Client contact: [e.g., VP Operations — the project sponsor who made the request in this week's status meeting]
</context>

<instructions>
- Write a professional, diplomatic email that addresses the scope change request
- Frame it positively: we are glad the work is valuable enough that they want to expand it
- Clearly explain what the additional scope includes and why it requires a change order
- Present the additional investment and timeline impact transparently
- Offer 2 options if appropriate: (1) add the scope now with a change order, or (2) complete the current engagement and address the DC as a follow-on project
- Close with a willingness to discuss and find the right approach together
- Tone: partnership-oriented, not defensive or transactional
</instructions>

<avoid>
- Making the client feel like their request is unwelcome or burdensome
- Being vague about costs — ambiguity breeds resentment later
- Over-explaining why scope changes cost money — they understand, they just need it formalized
- Passive-aggressive language about scope creep
</avoid>

<task>Write a professional check-in email to a past consulting client to maintain the relationship and explore future engagement opportunities.</task>

<context>
Client: [e.g., VP Operations at a mid-market manufacturer]
Last engagement: [e.g., Completed an operational efficiency assessment 3 months ago — delivered recommendations for warehouse optimization and automated routing]
Engagement outcome: [e.g., Client implemented Phase 1 recommendations within 60 days. Positive feedback at close-out meeting.]
Relationship status: [e.g., Strong — client expressed interest in future work around their supply chain planning process]
Industry development to reference: [e.g., Recent supply chain disruptions in their industry due to new tariff regulations announced last month]
Tone: [e.g., Professional but warm — we built good rapport during the engagement]
</context>

<instructions>
- Write a check-in email that feels genuine, not like a sales cadence
- Open with a specific reference to their business or the work we did together — show you remember and care
- Reference the industry development naturally — position it as something that made you think of them
- Ask how implementation is going — show interest in outcomes, not just our next invoice
- Lightly open the door to future work without being pushy
- Close warmly with an easy next step (coffee, call, or just a reply)
- Keep under 150 words — respect their inbox
</instructions>

<avoid>
- Generic "just checking in" language
- Anything that reads like a marketing email or newsletter
- Asking for referrals — that is a separate conversation
- Being pushy about follow-on work
</avoid>

<task>Draft an email to our client communicating that a key deliverable will be delayed, along with the reason, impact, and remediation plan.</task>

<context>
Deliverable: [e.g., Draft recommendations report — originally due March 21]
Delay: [e.g., 5 business days — new delivery date March 28]
Reason: [e.g., The ERP data we received had significant gaps in Q1 2025 — our team spent an additional week reconstructing the cost baseline from backup data. The analysis is now complete but the delay compressed our drafting timeline.]
Impact on overall engagement: [e.g., The final presentation originally scheduled for April 4 will shift to April 11. No impact on the quality of recommendations or the overall engagement scope.]
What we are doing about it: [e.g., Adding a second analyst for the next 2 weeks to compress the drafting timeline. We will deliver a preliminary findings summary on March 21 (the original due date) so the client has visibility into our direction.]
Client contact: [e.g., VP Operations — project sponsor]
Relationship context: [e.g., First engagement — trust is still being built]
</context>

<instructions>
- Be direct about the delay — do not bury the news
- Own the situation even if the data gap was on the client's side — we should have identified it earlier
- Present the revised timeline with confidence — do not apologize excessively
- Emphasize what we are doing to mitigate: the interim deliverable and the additional resources
- Reassure that quality will not be compromised — the delay is about doing it right, not about being behind
- Close with availability to discuss — offer a call, not just an email
- Tone: professional, accountable, and forward-looking
</instructions>

<avoid>
- Blaming the client for the data gap — even if it was their issue
- Over-apologizing — once is enough, then move to the plan
- Being vague about the new timeline — specificity builds trust
- Minimizing the delay — acknowledge it honestly
</avoid>