Present scope trade-off options to demanding clients
Say yes with realistic conditions instead of an abrasive no. Use this when a client demands extra deliverables mid-project.
You getClient Email Draft, meeting Talking Points and internal Guardrail
Prompt
Act as an agency client services director. Draft a diplomatic, constructive client reply to the out-of-scope request below.
Rules:
- Never say an outright no; frame constraints around project quality, delivery dates, and budget reality.
- Present two clear choices that protect the original contract deadline.
- Keep the tone polite, consultative, and firm.
- Avoid defensive phrasing or blaming the client.
Output format:
1. Client Email Draft (ready to send, professional and collaborative)
2. Meeting Talking Points (3 short bullets for live conversations)
3. Internal Guardrail (what the internal team must strictly monitor)
Here is the client request and current project context:Example output
Paste your client's email or message and your current deliverables into ChatGPT, Gemini, or Claude. For a tighter message, ask the model to reduce the draft email to under 120 words while keeping both choices intact.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Define post-launch support and warranty handoff terms
Establish firm boundaries between warranty bug fixes and paid ongoing support. Use this during project closure to prevent unpaid scope creep from clients.
Draft a formal deliverable sign-off request email
Secure clear written approval for completed deliverables to formally trigger warranty periods or final billing. Use this when final milestones are ready for client acceptance.
Align project metrics with business OKRs
Connect operational project deliverables directly to high-level company goals. Perfect for building executive stakeholder buy-in before project kickoff.
Analyze timeline and budget trade-offs for scope requests
Turn vague stakeholder feature requests into clear trade-off scenarios. Use this when clients or leaders request additions without considering cost or delay.
Audit a RACI chart for split accountability
Identify dangerous governance flaws, duplicate owners, and delivery bottlenecks in an existing RACI matrix. Use this before launching high-stakes projects.
Build a RACI matrix from deliverables
Assign clear operational roles across all major project workstreams. Use to eliminate delivery confusion and establish single-point task accountability.
- Classify task dependencies by finish and start types
- Create a client asset and credential handoff checklist
- Create a shared milestone alignment brief across teams
- Define out-of-scope boundaries before kickoff
- Design a client training plan for project launch
- Identify silent stakeholders before locking requirements