20 AI Prompts for Consultants (Free, Copy and Paste)

Q: Are these prompts specific to a consulting specialty?

The prompts work across strategy, operations, technology, and HR consulting. Most variables are industry-neutral by design, so you swap in your sector and client context without rewriting the underlying structure.

Q: Can I use these prompts across ChatGPT, Claude, and Gemini?

Yes. Every prompt in this pack is written in plain language, with no model-specific syntax, so it runs on all four platforms Convergence supports.

Q: What if a prompt produces generic output?

Add specificity. The single most effective fix is replacing bracket variables with real client names, actual figures, and concrete constraints. Generic input produces generic output on every model.

Q: Should I share these prompts with junior staff?

That depends on your workflow, but shared prompts are one of the fastest ways to raise the floor on junior work. Convergence shared folders let the whole team pull from the same library without copying files around.

Q: Do AI prompts replace consultant judgment?

No. These prompts handle structure and drafting. Judgment about what the client actually needs, and whether the output is right, stays with you.

AI prompts for consultants are pre-written instructions that help consulting professionals complete common tasks faster and more consistently, using any major AI tool. A good prompt handles the structural work: drafting a scope document, building a stakeholder map, generating discovery questions, or structuring a slide deck. What it cannot do is replace the judgment that makes consulting valuable. The strategic read of a client's situation, the recommendation that will actually land, the political nuance in a room: that still comes from you. Used well, ai prompts for consultants free up the hours you spend on scaffolding so you can spend more time on the thinking that matters.

AI prompts for consultants are pre-written instructions that help consulting professionals complete common work tasks faster and more consistently, using any major AI tool. This page covers a curated pack of 20+ prompts organized by consulting workflow, from client discovery through to deliverable review. It is for independent consultants, small consulting firms, and in-house advisory teams who want to stop writing the same prompt from scratch every time.

What is in this pack

This pack covers the core workflows a consultant returns to repeatedly: scoping new engagements, structuring findings, drafting client-ready documents, and preparing for difficult conversations.

The prompts are grouped into five categories. Each one includes a copyable template with variables you fill in, a note on when to reach for it, and a line on what to change first when adapting it to your context.

One honest caveat up front: prompts will not replace the judgment that makes consulting valuable. They handle first drafts, structural scaffolding, and research synthesis. The strategic read of a client's politics, or knowing which recommendation will actually land, still comes from you.

For prompts built around other professional roles, see the full prompts-by-role library.

The prompts, by category

These prompts cover the work consultants do most often: scoping projects, structuring findings, writing deliverables, and managing clients. They are grouped by the phase of an engagement where you will most likely need them.

A note before you start: AI does well on structure and drafting, but it does not know your client's industry the way you do. Every output needs your judgment applied before it leaves your hands. These prompts are a starting point, not a finished product.

The categories below move roughly in project order, from initial scoping through to follow-on work. Variables appear in [BRACKETS]. Change those first before running any prompt.

Category	Prompts	Best phase
Scoping and discovery	5	Before kickoff
Findings and analysis	4	Mid-engagement
Slide decks and reports	4	End of engagement
Client communication	4	Throughout
Proposals and sales	3	Pre-engagement

Scoping and discovery

Draft a project scope document from a client brief

Variables: [CLIENT BRIEF], [ENGAGEMENT TYPE], [DELIVERABLES], [TIMELINE], [BUDGET RANGE]

You are an experienced management consultant. Using the client brief below, draft a project scope document that includes:
- A one-paragraph engagement summary
- Objectives (3 to 5 bullet points)
- In-scope and out-of-scope items as two separate lists
- Key assumptions
- Proposed deliverables: [DELIVERABLES]
- Suggested timeline: [TIMELINE]
- Budget range: [BUDGET RANGE]
- A risks and dependencies section

Engagement type: [ENGAGEMENT TYPE]

Client brief:
[CLIENT BRIEF]

Write in plain business English. Flag any gaps in the brief that would need to be resolved before signing off on scope.

When to use it: At the start of an engagement, after your first client call but before the SOW is drafted. What to change first: Swap [DELIVERABLES] for the actual outputs your engagement will produce.

[NEEDS REAL OUTPUT]

Build a stakeholder map from an org chart or attendee list

Variables: [ORG CHART OR ATTENDEE LIST], [PROJECT GOAL]

I am a consultant working on [PROJECT GOAL]. Below is an org chart or list of meeting attendees. For each person or role, identify:
1. Their likely interest in this project (high / medium / low)
2. Their likely influence over outcomes (high / medium / low)
3. One potential concern they may raise
4. A suggested engagement approach (e.g. keep informed, seek input, manage closely)

Present the output as a table.

Org chart or attendee list:
[ORG CHART OR ATTENDEE LIST]

When to use it: Before your stakeholder engagement plan is finalized, ideally before the kickoff meeting. What to change first: Replace [PROJECT GOAL] with a single clear sentence about the engagement outcome.

Generate discovery interview questions for a specific function

Variables: [FUNCTION], [ENGAGEMENT TOPIC], [CLIENT INDUSTRY]

I am preparing for discovery interviews with [FUNCTION] leaders at a [CLIENT INDUSTRY] company. The engagement focuses on [ENGAGEMENT TOPIC].

Write 12 open-ended interview questions that will surface:
- Current-state pain points and workarounds
- Root causes, not just symptoms
- Unstated priorities and political sensitivities
- Data and evidence the team already relies on

Avoid yes/no questions. Sequence them so that rapport is built before harder questions appear.

When to use it: In the week before discovery interviews. Run it once per function you are interviewing. What to change first: [FUNCTION] matters most here. HR interviews need very different questions than finance or operations.

Identify risks and constraints from a project description

Variables: [PROJECT DESCRIPTION], [INDUSTRY], [ENGAGEMENT DURATION]

Review the project description below and identify:
1. The top five execution risks, with likelihood (high/medium/low) and potential impact
2. Three to five constraints (time, resource, data, organizational) that could limit the engagement
3. One critical assumption that, if wrong, would materially change the scope

Present as a structured table. Be direct. Flag risks even if they reflect on the client's readiness.

Project description:
[PROJECT DESCRIPTION]
Industry: [INDUSTRY]
Engagement duration: [ENGAGEMENT DURATION]

When to use it: Before your scoping call, or as a sense-check before submitting a proposal. What to change first: Be specific in [PROJECT DESCRIPTION]. A vague input produces a generic risk list.

[NEEDS REAL OUTPUT]

Write a kickoff meeting agenda

Variables: [ENGAGEMENT NAME], [DURATION], [ATTENDEES], [KEY OBJECTIVES]

Draft a kickoff meeting agenda for [ENGAGEMENT NAME]. The meeting will last [DURATION] and will include [ATTENDEES].

The agenda should cover:
- Welcome and introductions
- Project objectives and success criteria: [KEY OBJECTIVES]
- Scope, timeline, and key milestones
- Roles and responsibilities (consultant team and client team)
- Working norms and communication protocols
- Open questions and parking lot
- Next steps and meeting cadence

For each agenda item, include a suggested time allocation and who leads that section. Keep the tone professional but direct.

When to use it: Two to three days before kickoff. Share with the client sponsor for input before finalizing. What to change first: Adjust [DURATION] and compress or expand sections accordingly.

Findings and analysis

Synthesize interview notes into key themes

Variables: [INTERVIEW NOTES], [ENGAGEMENT QUESTION]

Below are notes from [NUMBER] stakeholder interviews conducted as part of a consulting engagement. The central engagement question is: [ENGAGEMENT QUESTION].

Synthesize the notes into:
1. Three to five recurring themes, each with supporting evidence from the interviews
2. Contradictions or tensions between stakeholder views
3. Gaps where more data is needed
4. A one-paragraph executive summary of what the interviews reveal

Do not invent evidence. Only draw on what is in the notes.

Interview notes:
[INTERVIEW NOTES]

When to use it: After completing a round of discovery interviews, before writing your findings deck. What to change first: Paste in real notes. The quality of synthesis depends entirely on the quality of input.

[NEEDS REAL OUTPUT]

Turn raw data observations into an insight statement

Variables: [DATA OBSERVATION], [CONTEXT], [AUDIENCE]

I have the following data observation from a client engagement:
[DATA OBSERVATION]

Context: [CONTEXT]
Audience: [AUDIENCE]

Write an insight statement that:
- States what the data shows in plain language
- Explains why it matters to the client's situation
- Suggests what it implies for their decision or next step

Keep it to three sentences. Avoid jargon. Do not overstate causation where the data only shows correlation.

When to use it: When you have a finding but are struggling to articulate why it matters to the client. What to change first: [AUDIENCE] changes the framing significantly. A CFO needs a different angle than an operations director.

Write a gap analysis comparing current and future state

Variables: [CURRENT STATE DESCRIPTION], [DESIRED FUTURE STATE], [DIMENSION LIST]

Write a structured gap analysis comparing the current state and desired future state of [CLIENT/FUNCTION/PROCESS].

Analyze the following dimensions: [DIMENSION LIST]

For each dimension:
- Describe the current state
- Describe the desired future state
- Identify the gap
- Rate the gap severity (high / medium / low)
- Suggest one action that would begin to close the gap

Present as a table. Current state: [CURRENT STATE DESCRIPTION]. Desired future state: [DESIRED FUTURE STATE].

When to use it: Mid-engagement, when you have enough discovery data to characterize both states. What to change first: [DIMENSION LIST] should reflect the dimensions that matter for this specific engagement, not a generic list.

Draft a so-what statement for a set of findings

Variables: [FINDINGS LIST], [CLIENT DECISION]

Below are a set of findings from a consulting engagement. The client needs to make the following decision: [CLIENT DECISION].

For each finding, write a one-sentence "so what" that connects the finding to the client's decision. Then write a single paragraph that synthesizes all findings into a clear recommendation.

Findings:
[FINDINGS LIST]

When to use it: When you have findings but they are sitting as a list rather than a coherent argument. What to change first: [CLIENT DECISION] anchors everything. If the decision changes, the so-whats change too.

[NEEDS REAL OUTPUT]

Slide decks and reports

Write an executive summary slide in SCR format

Variables: [SITUATION], [COMPLICATION], [RESOLUTION], [AUDIENCE ROLE]

Write an executive summary slide using the Situation-Complication-Resolution (SCR) structure for a consulting deliverable aimed at [AUDIENCE ROLE].

Situation: [SITUATION]
Complication: [COMPLICATION]
Resolution: [RESOLUTION]

For each element, write two to three sentences that are direct and evidence-grounded. Avoid vague language. The resolution should be specific enough that the audience knows what action is being recommended.

When to use it: When writing the opening slide of any findings or recommendations deck. What to change first: [RESOLUTION] is where most drafts go vague. Make it an actual recommendation, not a direction.

Create a slide-by-slide outline for a recommendations deck

Variables: [ENGAGEMENT TOPIC], [KEY FINDINGS], [RECOMMENDATIONS], [AUDIENCE], [SLIDE COUNT]

Create a [SLIDE COUNT]-slide outline for a consulting recommendations deck on [ENGAGEMENT TOPIC] for [AUDIENCE].

The deck should follow a logical narrative arc: context, problem, findings, implications, recommendations, next steps.

Key findings: [KEY FINDINGS]
Recommendations: [RECOMMENDATIONS]

For each slide, provide:
- A suggested headline (written as an insight, not a topic label)
- Two to three bullet points on what content goes on that slide
- A note on what visual or data would support the message

When to use it: Before writing any slides. A clear outline prevents structural rewrites later. What to change first: [SLIDE COUNT] should match the time you have with the client, not the amount you want to say.

Write an action-oriented slide headline from a bullet-point finding

Variables: [FINDING], [IMPLICATION], [AUDIENCE]

Convert the following finding into an action-oriented slide headline of 10 words or fewer, suitable for [AUDIENCE].

Finding: [FINDING]
Implication: [IMPLICATION]

The headline should state the insight or recommendation, not just the topic. Avoid starting with "The" or using vague words like "opportunities" or "challenges". Write three headline options and explain the trade-off between them.

When to use it: When your slide titles are reading as topics ("Cost Structure") rather than messages ("Overhead costs are running 18% above sector median"). What to change first: Make [FINDING] specific. The more precise the finding, the sharper the headline.

Write a report executive summary from a full report draft

Variables: [REPORT DRAFT OR SECTION SUMMARIES], [WORD LIMIT], [PRIMARY READER]

Using the report content below, write an executive summary of [WORD LIMIT] words for [PRIMARY READER].

The summary should:
- Open with the single most important finding or recommendation
- Cover the two or three supporting points that matter most to this reader
- End with the immediate decision or action required
- Use plain language, no jargon

Report content:
[REPORT DRAFT OR SECTION SUMMARIES]

When to use it: After the full report is drafted. Do not write the executive summary first. What to change first: [PRIMARY READER] changes the emphasis. A board summary reads differently from one for an operations team.

Client communication

Write a project status update email

Variables: [PROJECT NAME], [REPORTING PERIOD], [PROGRESS], [ISSUES], [NEXT STEPS]

Write a project status update email for [PROJECT NAME] covering [REPORTING PERIOD].

Structure it as:
- One-sentence summary of overall status (on track / at risk / off track)
- Progress this period: [PROGRESS]
- Issues or blockers requiring client input: [ISSUES]
- Next steps and owners: [NEXT STEPS]
- Any decisions needed from the client before the next update

Keep it under 250 words. Professional but not stiff. The client should be able to read it in 90 seconds and know exactly where things stand.

When to use it: For weekly or biweekly updates to the client sponsor. Adapt the structure to match your engagement's reporting rhythm. What to change first: Be honest in [ISSUES]. If something is at risk, name it here rather than softening it.

Draft a difficult client email (scope creep, delay, or missed deadline)

Variables: [ISSUE TYPE], [FACTS], [PROPOSED RESOLUTION], [TONE]

Draft an email addressing the following issue with a client: [ISSUE TYPE].

Facts: [FACTS]
Proposed resolution: [PROPOSED RESOLUTION]
Tone: [TONE] (e.g. direct, diplomatic, firm but constructive)

The email should:
- State the issue plainly in the first two sentences
- Acknowledge impact without being defensive
- Propose a concrete resolution or next step
- Be under 200 words

Do not use passive voice to avoid accountability. Do not over-apologize.

When to use it: When a situation has gone off track and you need to communicate it clearly before a call. What to change first: [FACTS] must be accurate. Drafting around incomplete facts produces a response that backfires.

[NEEDS REAL OUTPUT]

Write meeting notes and action items from a transcript or raw notes

Variables: [RAW NOTES OR TRANSCRIPT], [MEETING TITLE], [ATTENDEES]

Using the notes or transcript below, write a clean meeting summary for [MEETING TITLE] with [ATTENDEES].

Include:
- Meeting objective (one sentence)
- Key decisions made
- Action items (owner, action, due date)
- Open questions still to be resolved
- Any parking-lot items

Format action items as a table with columns: Owner | Action | Due Date | Priority.

Do not add interpretation or recommendations that were not discussed. Stick to what is in the source material.

Raw notes or transcript:
[RAW NOTES OR TRANSCRIPT]

When to use it: Within two hours of any client meeting, before memory fades. What to change first: Add context to [MEETING TITLE] so the summary reflects the meeting's purpose, not just its agenda.

Write a talking-points document for a difficult client conversation

Variables: [CONVERSATION TOPIC], [CLIENT CONCERN], [YOUR POSITION], [DESIRED OUTCOME]

I need to have a difficult conversation with a client about [CONVERSATION TOPIC]. 

Client concern: [CLIENT CONCERN]
My position: [YOUR POSITION]
Desired outcome from the conversation: [DESIRED OUTCOME]

Write a talking-points document that includes:
- An opening statement that acknowledges the client's concern without conceding the point
- Three to four key points to make, each with supporting rationale
- Anticipated client pushback and a suggested response to each
- A closing that moves toward the desired outcome

Keep it concise. This is for preparation, not a script to read aloud.

When to use it: Before any high-stakes client call where the positions are not aligned. What to change first: [DESIRED OUTCOME] should be realistic. If the goal is too ambitious, the talking points read as adversarial.

Proposals and sales

Draft a consulting proposal from a project brief

Variables: [PROJECT BRIEF], [FIRM NAME], [CLIENT NAME], [ENGAGEMENT TYPE], [FEE RANGE]

You are an experienced consultant at [FIRM NAME]. Draft a consulting proposal for [CLIENT NAME] based on the project brief below.

The proposal should include:
- Executive summary (one paragraph)
- Our understanding of your situation (problem and context)
- Proposed approach (phases, activities, deliverables)
- Team and qualifications (placeholder names)
- Timeline and milestones
- Investment (fee structure: [FEE RANGE])
- Why us (two to three differentiators)
- Proposed next steps

Write in a confident, client-focused tone. Avoid generic consulting language.

## Real example outputs

The five prompts marked [NEEDS REAL OUTPUT] below show captured model responses. Each includes a "what to notice" line pointing out something specific about the output's structure or phrasing that makes it useful or worth editing.

| Prompt | Model used | What to notice |
|---|---|---|
| Stakeholder objection map | [NEEDS REAL OUTPUT] | [NEEDS REAL OUTPUT] |
| Project status email | [NEEDS REAL OUTPUT] | [NEEDS REAL OUTPUT] |
| Hypothesis tree | [NEEDS REAL OUTPUT] | [NEEDS REAL OUTPUT] |
| Slide headline rewrite | [NEEDS REAL OUTPUT] | [NEEDS REAL OUTPUT] |
| Risk register draft | [NEEDS REAL OUTPUT] | [NEEDS REAL OUTPUT] |

All five are placeholders until a team member runs them against a live model and pastes in the output. That step matters. Outputs vary by model version, phrasing, and the specifics you drop into the variables. A captured output from your own project is more useful to your team than a generic example, because it shows them the quality bar to expect and the edits that were actually needed before the deliverable went to a client.

## How to adapt these for your team

The prompts above work as-is for solo consultants. For a team, the main job is making the variables explicit so anyone can pick one up and run with it.

Start by replacing the generic placeholders with your firm's actual defaults. `[CLIENT INDUSTRY]` might always be financial services. `[DELIVERABLE FORMAT]` might default to your standard deck structure. Hardcoding those removes a decision and cuts the chance of off-brand output.

Two things are worth doing before you share a prompt with colleagues:

- **Test it yourself first.** Run it on a real project and note where the output needs editing. That edit is the instruction you add to the prompt before handing it over.
- **Add a one-line context header.** Something like "We are a strategy boutique; our clients are mid-market manufacturers" at the top of every prompt does more work than most people expect.

:::keypoint heading="Worth pausing on"
The prompts that fail on your team are almost never bad prompts. They are prompts without enough context about your firm, your client, or what "good" looks like in your practice.
:::

If your team works across ChatGPT, Claude, or Copilot, store these in [shared folders on Convergence](/product/shared-folders) so edits propagate to everyone at once rather than living in someone's personal notes.

## Save this folder to your workspace

Every prompt above lives in a Convergence folder you can save once and reuse across ChatGPT, Claude, Copilot, and Gemini without copying and pasting between tools.

If you run a small practice solo, the free plan covers the basics. Where this pays off more clearly is on teams: a senior consultant refines a proposal prompt, saves it, and everyone else gets the updated version automatically. No shared Google Doc to maintain, no Slack message saying "use the new version."

You can also lock variables, so a junior team member fills in `[CLIENT NAME]` and `[ENGAGEMENT TYPE]` without accidentally editing the underlying prompt logic.

:::cta heading="Want your whole team running these prompts consistently?"
Convergence [shared folders](/product/shared-folders) let you organize prompts by role, lock the parts that should stay fixed, and push updates to everyone at once.
:::

If you mostly work alone and switch models depending on the task, the folder still earns its place. One organized library beats six browser tabs of half-finished prompts every time.

## Frequently asked questions

### Are these prompts specific to a consulting specialty?

The prompts work across strategy, operations, technology, and HR consulting. Most variables are industry-neutral by design, so you swap in your sector and client context without rewriting the underlying structure.

### Can I use these prompts across ChatGPT, Claude, and Gemini?

Yes. Every prompt in this pack is written in plain language, with no model-specific syntax, so it runs on all four platforms Convergence supports.

### What if a prompt produces generic output?

Add specificity. The single most effective fix is replacing bracket variables with real client names, actual figures, and concrete constraints. Generic input produces generic output on every model.

### Should I share these prompts with junior staff?

That depends on your workflow, but shared prompts are one of the fastest ways to raise the floor on junior work. [Convergence shared folders](/product/shared-folders) let the whole team pull from the same library without copying files around.

### Do AI prompts replace consultant judgment?

No. These prompts handle structure and drafting. Judgment about what the client actually needs, and whether the output is right, stays with you.