Best ChatGPT Prompts for Consultants (2026): Copy-Paste and Get Results

You are a management consultant preparing for an initial discovery session with a new client. Generate a structured intake questionnaire for this engagement. The questions should uncover: the business problem or opportunity at the center of this engagement, the current state vs. desired state, key stakeholders and their motivations, constraints (budget, timeline, politics), previous attempts to solve this problem and why they failed, and how success will be measured.

Keep questions open-ended. Group them under 4–5 clear categories. The questionnaire should be professional enough to send to a C-suite executive.

ENGAGEMENT CONTEXT:
- Client name and industry: [CLIENT NAME], [INDUSTRY]
- Engagement type: [e.g. operational efficiency review / go-to-market strategy / post-merger integration]
- What I know so far: [BRIEF DESCRIPTION OF THE SITUATION]
- Primary contact and title: [NAME, TITLE]

I've completed a discovery phase with a client and need to synthesize my notes into a crisp, executive-ready problem statement. Based on the notes below, write a problem statement that:
1. Names the core business problem in one sentence (not symptoms — the root problem)
2. Quantifies the impact of the problem where possible (revenue, cost, time, risk)
3. States why solving it matters now (urgency or strategic context)
4. Names what success looks like in concrete terms

This will be used at the top of a proposal. It should be 150–200 words. No jargon. A board member should be able to read it and immediately agree: "Yes, that's the problem."

DISCOVERY NOTES:
[PASTE YOUR NOTES — interview summaries, observations, data points, quotes]

I'm starting a consulting engagement and need to map the stakeholder landscape. Based on the context below, produce a stakeholder analysis with the following structure for each key stakeholder:
- Name and role
- Level of influence on this engagement (High / Medium / Low)
- Likely stance toward this project (Champion / Neutral / Skeptic / Unknown)
- Primary concern or motivation — what do they want from this?
- Recommended engagement approach (how to work with them)

Then: identify the 2–3 stakeholders who are most critical to manage, and the 1–2 most likely points of resistance.

ENGAGEMENT CONTEXT:
- Client organization: [COMPANY NAME AND INDUSTRY]
- Engagement objective: [WHAT WE'RE TRYING TO ACCOMPLISH]
- Known stakeholders and their roles: [LIST NAMES AND TITLES]
- Any political dynamics I've observed: [NOTES — or "unknown"]

Act as a management consultant facilitating a structured root cause analysis. Using the problem and symptoms described below, apply a 5-Why analysis to identify the most likely root cause. Then:
1. State the surface symptom
2. Walk through the 5-Why chain
3. State the most probable root cause
4. Flag 1–2 alternative root causes if the evidence is ambiguous
5. Recommend the minimum data or interviews needed to confirm the root cause before recommending solutions

Be diagnostic, not prescriptive — the goal is to identify what's actually wrong, not to jump to solutions.

PROBLEM CONTEXT:
- Client: [INDUSTRY AND COMPANY TYPE — no name needed]
- Observable symptom or problem: [DESCRIBE WHAT THEY'RE EXPERIENCING]
- Data or evidence available: [METRICS, ANECDOTES, OBSERVATIONS]
- What they believe is causing it: [CLIENT'S OWN HYPOTHESIS — or "unknown"]

Write a one-page executive summary for a consulting proposal. This should be the first page a client reads — it should make them want to read the rest. Structure it as:
1. The problem (2–3 sentences — what's at stake, why it matters now)
2. Our recommended approach (what we will do and why this approach)
3. What success looks like (the specific outcomes they can expect)
4. Why us (1–2 sentences — specific to this engagement, not generic credentials)
5. Engagement overview (timeline and investment — brief)

Tone: confident, direct. No filler. This is not a cover letter — it's a compressed version of the whole case for hiring us.

ENGAGEMENT DETAILS:
- Client: [CLIENT NAME AND INDUSTRY]
- Core problem: [THE PROBLEM IN 1–2 SENTENCES]
- Proposed solution: [WHAT YOU'LL DO]
- Expected outcomes: [SPECIFIC RESULTS]
- Timeline: [DURATION]
- Engagement fee: [$AMOUNT]
- Why your firm: [RELEVANT CREDENTIAL OR DIFFERENTIATOR]

Write a professional Statement of Work (SOW) for the consulting engagement described below. Include these sections:
1. Engagement objective (what this engagement will accomplish)
2. Scope of work (what is included — specific deliverables and activities)
3. Out of scope (what this engagement explicitly does not cover)
4. Deliverables (list each deliverable with a brief description and acceptance criteria)
5. Timeline and milestones
6. Roles and responsibilities (what we deliver vs. what the client provides)
7. Fees and payment schedule
8. Change management (how out-of-scope requests are handled)

Write this as a working agreement between equals. Be specific enough that scope disputes can be resolved by referring to this document.

ENGAGEMENT DETAILS:
- Client: [NAME AND COMPANY]
- Engagement type: [TYPE OF CONSULTING]
- Key deliverables: [LIST]
- Timeline: [START DATE → END DATE, key milestones]
- Engagement fee: [$AMOUNT and payment structure]
- Client team involved: [WHO FROM THEIR SIDE WILL PARTICIPATE]

Help me write a 200–250 word pricing narrative to include in a proposal where the fee may cause sticker shock. I'm not discounting — I'm helping the client understand the value. Focus on:
1. The cost of the problem continuing (not solving it is expensive)
2. The ROI or risk reduction the engagement delivers
3. What's embedded in the fee (expertise, speed, methodology — things they couldn't replicate internally)
4. A brief comparison to the alternative (hiring internally, doing nothing, or a cheaper vendor)

Do not use generic lines like "our rates reflect the quality of our work." Be specific to this engagement.

CONTEXT:
- Engagement type: [WHAT YOU'RE DELIVERING]
- Fee: [$AMOUNT]
- Expected outcome or result: [WHAT THEY GET — specific]
- Cost of the problem (if known): [REVENUE IMPACT, RISK, COST — or estimate]
- Why a cheaper option wouldn't work: [SPECIFIC REASON]

Write a 1-page capability statement tailored to a specific consulting opportunity. This is not a generic firm bio — it should be written to answer the client's implicit question: "Do these consultants understand our problem and have they solved something like it before?"

Structure:
1. Opening statement: who we are and what we're known for (2 sentences, specific to this client's situation)
2. Relevant experience: 2–3 brief project summaries that map directly to this engagement (client type, problem, outcome — no names unless public)
3. Methodology or approach: how we work and why it's right for this
4. Team (optional): 1–2 relevant credentials or backgrounds
5. Closing: one sentence on what working with us looks like

OPPORTUNITY CONTEXT:
- Prospective client: [INDUSTRY AND COMPANY TYPE]
- What they need: [ENGAGEMENT TYPE AND PROBLEM]
- Our most relevant past work: [BRIEF DESCRIPTIONS OF 2–3 PROJECTS]
- Our key differentiator for this engagement: [WHAT MAKES US THE RIGHT CHOICE]

I need to build a consulting slide deck and want to draft the narrative structure before I design the slides. Based on the engagement context below, write a slide-by-slide narrative outline that:
1. Names each slide (clear, declarative titles — "Revenue growth has slowed 3 years running," not "Revenue Analysis")
2. States the one point each slide must make
3. Lists the supporting evidence or data that goes on each slide
4. Flags where a chart, framework, or model should appear

Use the Pyramid Principle: lead with the conclusion, support with evidence. The narrative should stand alone as a document — a reader should understand the argument without seeing the visuals.

DECK CONTEXT:
- Client: [CLIENT NAME AND INDUSTRY]
- Purpose of the deck: [e.g. findings readout / strategy recommendation / board update]
- Core argument or recommendation: [THE MAIN POINT YOU'RE MAKING]
- Key findings: [LIST THE MAIN THINGS YOU FOUND]
- Audience: [WHO IS IN THE ROOM — titles and decision-making authority]
- Desired outcome of the meeting: [WHAT YOU WANT THEM TO DO OR DECIDE]

Write a consulting recommendations memo based on the engagement findings below. Format it as a professional memo a client can circulate internally. Use this structure:
1. Background (2 sentences — why this engagement was conducted)
2. Key findings (3–5 bullets — specific, evidence-based, no editorializing)
3. Recommendations (numbered list — each recommendation starts with an action verb, includes rationale in 1–2 sentences)
4. Prioritization (which recommendation to act on first and why)
5. Next steps (specific actions, owners, and timeframes)

Tone: direct and decisive. This memo should read like it was written by someone who has a point of view, not someone afraid to commit to a recommendation.

ENGAGEMENT CONTEXT:
- Client: [CLIENT NAME AND INDUSTRY]
- Engagement scope: [WHAT THE ENGAGEMENT COVERED]
- Key findings: [LIST WHAT YOU FOUND — data, observations, interviews]
- Recommendations you want to make: [YOUR THINKING — bullet points are fine]
- Priority recommendation: [THE MOST IMPORTANT ONE]

I have data from a client engagement that I need to turn into a consulting insight — a specific, defensible point of view, not just a summary of what the numbers say. Based on the data below:

1. State the insight in one sentence (the "so what" — what should a decision-maker do or believe based on this?)
2. Identify the 2–3 most important data points that support it
3. Flag any data that contradicts or complicates the insight
4. State what additional data would strengthen or change the conclusion
5. Suggest one visual (chart type) that would best communicate this to an executive audience

An insight is not "revenue declined 12%." It's "the revenue decline is concentrated in the mid-market segment, where churn has tripled — and that pattern points to a pricing problem, not a product problem."

DATA:
[PASTE YOUR DATA, TABLES, OR FINDINGS]

Write an implementation roadmap for the consulting recommendation described below. The roadmap should be specific enough to hand off to a client team to execute without additional guidance. Include:

1. Phases (3–4 phases with clear names and objectives)
2. Key activities in each phase (bullet list — specific, not generic)
3. Milestones and success criteria (what does "done" look like for each phase?)
4. Dependencies (what has to happen before the next phase can start?)
5. Resource requirements (internal team, external support, tools/systems)
6. Risk flags (the 2–3 most likely things that could derail implementation)

Format this as a table or structured outline a client can share with their leadership team.

RECOMMENDATION CONTEXT:
- Client: [CLIENT NAME AND INDUSTRY]
- Recommendation: [WHAT YOU'RE RECOMMENDING THEY DO]
- Starting point: [CURRENT STATE — what exists today]
- End state: [WHAT SUCCESS LOOKS LIKE IN 12–18 MONTHS]
- Client team available: [WHO WILL EXECUTE THIS INTERNALLY]
- Timeline constraint: [DEADLINE OR TARGET DATE — if any]

Write a concise project status update email for a client. Format it so a busy executive can read it in under 60 seconds:

1. Status: one sentence — on track / at risk / behind, and why
2. Work completed since last update: brief bullets
3. Work in progress: brief bullets with expected completion
4. Decisions needed: anything requiring client input to move forward
5. Next milestone: what happens next and when

No padding. No cheerful filler like "things are progressing well." If something is at risk, name it directly with the reason and proposed resolution.

ENGAGEMENT DETAILS:
- Client: [CLIENT NAME]
- Project: [ENGAGEMENT NAME OR DESCRIPTION]
- Reporting period: [DATE RANGE]
- Current status vs. plan: [ON TRACK / AT RISK / BEHIND — and the specific reason]
- What's done: [LIST]
- What's in progress: [LIST]
- Decisions needed: [LIST OR "none"]
- Next milestone: [WHAT AND WHEN]

Help me prepare for a difficult conversation with a client. Give me:
1. A suggested opening statement (how to start the conversation directly without being aggressive — 2–3 sentences)
2. The 3 most important things to communicate in this conversation
3. The 2–3 most likely pushback responses and how to address each one
4. A proposed resolution or next step to bring to the table
5. What I should NOT say — language or framings that would escalate or undermine the conversation

Difficult conversations in consulting go better when you arrive with a point of view and a proposed path forward, not just a description of the problem.

SITUATION:
- Client name: [NAME]
- What the difficult issue is: [DESCRIBE CLEARLY — missed deadline, scope dispute, quality concern, relationship tension, etc.]
- My position: [WHAT I BELIEVE AND WHAT I'M ASKING FOR]
- What I think they'll say: [ANTICIPATED REACTION]
- Desired outcome of the conversation: [WHAT A GOOD RESULT LOOKS LIKE]

Write a short email requesting structured feedback from a client after delivering a major engagement output. The email should:
- Reference what was delivered and when
- Ask 3 specific questions (not "what did you think?") that will give me actionable input
- Set a clear response deadline that keeps the project on schedule
- Stay under 100 words — this is a working request, not a relationship email

CONTEXT:
- Client name: [NAME]
- Deliverable submitted: [WHAT YOU SENT — report, deck, analysis, etc.]
- Submission date: [DATE]
- Feedback needed by: [DATE]
- The 3 specific things I need input on: [LIST THEM — e.g. "Are the recommendations actionable for your team?", "Is the data framing accurate to your context?", "What's missing?"]

Write a professional end-of-engagement message to send when wrapping up a consulting project. This should serve four purposes: (1) confirm all deliverables were completed, (2) summarize what was accomplished, (3) plant a seed for future work without being pushy, and (4) ask for a brief testimonial or referral in a way that feels natural.

Tone: warm but efficient. This is a relationship message that also closes the business loop.

ENGAGEMENT CONTEXT:
- Client name: [NAME]
- Project completed: [ENGAGEMENT NAME AND BRIEF DESCRIPTION]
- Deliverables provided: [LIST]
- Key outcome or result achieved: [WHAT GOT DONE — metric or observable change]
- Logical next engagement (if applicable): [WHAT WOULD MAKE SENSE TO DO NEXT]
- My name and firm: [YOUR INFO]

Write a LinkedIn post that positions me as a credible, practicing consultant — not a content marketer. The post should share a specific insight or observation from real consulting work, be useful to a reader in [TARGET AUDIENCE — e.g. ops leaders / CFOs / founders], and end with a question or provocation that invites engagement. Under 250 words. No hashtag spam. No "I'm excited to share." Start with a specific observation or counterintuitive claim, not "I."

CONTENT INPUT:
- Observation or insight I want to share: [DESCRIBE — a pattern you've seen, a mistake clients make, a framework that's working, etc.]
- The industry or context it comes from: [INDUSTRY — no client names]
- Who I want to read this: [TARGET AUDIENCE — their title or role]
- What I want them to take away: [THE ONE THING]
- What I do (so the post ties back naturally): [YOUR SPECIALTY IN ONE LINE]

Write a cold outreach email to a prospective consulting client. The email should be under 150 words, lead with a specific observation about their business or industry (not a generic compliment), name the problem you solve without over-explaining, and end with a low-friction ask. Do not use phrases like "I hope this finds you well," "I wanted to reach out," or "I'd love to connect."

This should read like it was written by a practitioner who did 5 minutes of real research — not a sales template.

CONTEXT:
- Prospect name and company: [NAME, COMPANY]
- Their industry and what's happening in it right now: [INDUSTRY + 1 SPECIFIC TREND OR CHALLENGE]
- What I noticed about their business specifically: [OBSERVATION — from their website, news, job postings, or public filings]
- The problem I solve: [YOUR SPECIALTY IN 1 SENTENCE]
- One relevant credential or result: [PAST PROJECT OUTCOME OR CLIENT TYPE]
- My ask: [e.g. "15-minute call" / "quick reply if this is relevant"]
- My name and firm: [YOUR INFO]

Write a follow-up email to a prospective client who has had my proposal for [X] days without responding. The email should be short (under 100 words), not apologetic, and add a small piece of value — a relevant data point, a brief observation about their industry, or a clarifying question that advances the conversation. Do not re-pitch the proposal. End with an easy out: it's fine if the timing is off, but I want to know either way.

CONTEXT:
- Prospect name: [NAME AND COMPANY]
- What I proposed: [BRIEF DESCRIPTION OF THE ENGAGEMENT]
- How long since I sent the proposal: [X DAYS]
- One relevant thing I can add: [INSIGHT, RECENT DEVELOPMENT, OR CLARIFYING QUESTION]
- My name and firm: [YOUR INFO]

Write a one-page consulting case study for my firm's website or proposal library. Use this structure:
1. The Client (1 sentence — industry, company type, no name unless approved)
2. The Situation (the problem they had before hiring us — specific, not generic)
3. Our Approach (what we did and why — 3–4 sentences covering method, not just activities)
4. The Outcome (specific results — quantified where possible; qualitative if no metrics)
5. Key Insight (1 sentence: what made this engagement work, or what others can learn from it)

Tone: authoritative but readable. Write for a prospective client, not an academic audience. Under 350 words.

PROJECT DETAILS:
- Client type: [INDUSTRY, COMPANY SIZE]
- The problem they came to us with: [SPECIFIC SITUATION]
- What we did: [APPROACH AND METHODOLOGY]
- The result: [OUTCOME — with numbers if you have them]
- What made it work: [THE KEY FACTOR]