By PromptLeadz · Reading time 25 minutes · 100 AI consulting prompts across 5 categories · Calibrated for 2026 frontier models

What this pack covers

Consulting sits at the intersection of three disciplines: structured thinking (MECE decomposition, hypothesis-driven analysis, pyramid principle synthesis), framework application (Porter's Five Forces, value chain, 2x2 matrices done well not done lazily, financial models, capability assessments), and client management (stakeholder navigation, workshop facilitation, executive communication, scope management, expectation setting). Most consulting content circulating online optimizes for performing the framework aesthetic and ignores the rigor underneath. Most consulting work in practice is the rigor with framework aesthetic on top.

This pack of 100 AI consulting prompts is calibrated for all three buckets. The discovery and scoping prompts produce RFP responses, intake guides, scope memos, engagement letters, and kickoff plans that protect both consultant and client. The research and analysis prompts produce market sizing, competitive analysis, framework application, and data synthesis at junior-consultant draft quality the senior consultant can refine. The frameworks and deliverables prompts produce strategy memos, decks, recommendation frameworks, and decision matrices with named axes and named tradeoffs. The client communication and workshops prompts produce interview kits, workshop designs, status updates, and hard-conversation scripts. The practice operations prompts produce pricing memos, BD pipeline reviews, profitability analyses, hiring rubrics, and practice strategy memos that build the firm beyond any single engagement.

The pack does not produce McKinsey-deck cliche about value creation and synergies. The pack also does not produce final client deliverables on its own. The artifacts require partner review (or solo-consultant senior peer review) before client delivery. Engagement letters and MSAs require counsel review. Treat the prompts as drafting accelerators that get you to a working draft in minutes, freeing your time for the judgment, the verification, and the client conversation that actually require human practitioner work.

Five categories. The consulting engagement end to end.

The five categories map to the five disciplines that determine whether a consulting practice compounds reputation or accumulates client churn. Client Discovery and Scoping comes first because scope sets the engagement up to succeed or fail before work begins. Research and Analysis comes second because the rigor of the analysis determines whether the recommendation is defensible. Frameworks and Deliverables comes third because how the analysis is communicated to the client determines whether it produces decisions. Client Communication and Workshops comes fourth because the engagement experience and stakeholder management determine whether the recommendation gets adopted. Practice Operations comes fifth because pricing, BD, profitability, hiring, and IP reuse are what build a practice that compounds beyond any single engagement.

1. RFP response architecture

RFP: [paste named client, scope, budget signals, timeline]. Our capability fit: [paste]. Draft a 700-word RFP response architecture: named executive summary tied to client's stated problem, named approach with phases and milestones, named team composition with senior involvement, named pricing structure and assumptions, named differentiation from likely competitors, named references relevant to the client context, named next steps. RFP responses that lead with firm history before client problem produce no shortlist position.

2. RFP rejection (when not a fit)

RFP: [paste]. Reason for declining: [paste, e.g. capacity, capability, conflict, pricing, fit]. Draft a 200-word rejection: named factual decline without burying it, named reason category (without legal exposure), named alternative if appropriate (referral to peer firm, scope narrowing, future engagement), named open door for the right future engagement. Declines that try to explain too much produce client doubt about future engagements.

3. Initial client intake call agenda

Prospect: [paste named role, company, stated need]. Time: [paste, typically 30-45 minutes]. Draft a 300-word intake agenda: named opening (5 minutes, mutual context), named problem-statement probes (15-20 minutes), named context and constraints (5 minutes), named expectations and process (5 minutes), named next steps (5 minutes). Intake calls run as pitches without discovery produce ill-scoped engagements.

4. Discovery interview question bank

Engagement type: [paste, e.g. strategy, operations, transformation]. Client context: [paste]. Draft a 500-word interview question bank: named opening questions on context and history, named problem-statement probes (what is happening, what should be happening, what is the gap), named stakeholder mapping questions, named constraint and timeline questions, named success criteria questions, named closing questions on engagement expectations. Question banks built around frameworks rather than client problem produce surface-level discovery.

5. Scope of work memo

Engagement: [paste objective, phases, expected outputs]. Client context: [paste]. Draft a 700-word SOW memo for counsel review: named engagement objective in client language, named scope in and scope out explicitly, named phases with milestones and durations, named deliverables per phase, named team composition with seniority and time allocation, named client responsibilities, named change management process. SOWs without explicit scope out produce scope creep disputes.

6. Engagement letter draft

Engagement: [paste scope summary, fees, timeline, named parties]. Standard terms: [paste]. Draft a 700-word engagement letter draft for counsel review: named engagement scope and objectives, named fees with payment terms and milestones, named term and termination, named confidentiality, named IP and work product ownership, named indemnification, named limitation of liability, named governing law. Engagement letters without counsel review produce dispute exposure at engagement end.

7. Project kickoff agenda

Engagement: [paste]. Attendees: [paste client and consultant teams]. Time: [paste, typically 90 minutes]. Draft a 400-word kickoff agenda: named introductions and roles, named engagement objectives in client language, named approach and phases, named timeline and milestones, named team and roles on both sides, named communication and cadence, named action items and decisions needed. Kickoffs run as introductions without commitments produce ambiguous early-engagement direction.

8. Stakeholder map for engagement

Client organization: [paste structure, named individuals if known]. Engagement scope: [paste]. Draft a 500-word stakeholder map: named decision-maker(s) with authority level, named influencers with engagement requirement, named blockers with mitigation approach, named users or beneficiaries, named gatekeepers (procurement, legal, finance), named communication cadence per group, named risks if any group is under-engaged. Stakeholder maps without named individuals (where possible) produce abstract maps that fail in practice.

9. Hypothesis tree for engagement

Engagement question: [paste central question]. Available context: [paste]. Draft a 600-word hypothesis tree: named central hypothesis statement, named MECE branches at first level (3-5 typically), named sub-hypotheses per branch, named test or evidence required per sub-hypothesis, named priority of test sequence, named decision points based on test outcomes. Hypothesis trees built without MECE discipline produce overlapping branches and missed dimensions.

10. Engagement objectives memo

Engagement scope: [paste]. Client stated goals: [paste]. Draft a 400-word objectives memo: named primary objective in client language, named secondary objectives, named non-objectives explicitly excluded, named measurable success criteria per objective, named timing of evaluation. Objectives memos with vague success criteria produce dispute at engagement close on whether the engagement succeeded.

11. Mutually-agreed-success-criteria document

Engagement: [paste]. Client and consultant view of success: [paste]. Draft a 400-word success criteria document: named criteria signed by client sponsor (typically 5-7), named measurement methodology per criterion, named timing of evaluation, named consequences of meeting or missing criteria. Success criteria not agreed in writing produce dispute risk at engagement close.

12. Risk register for engagement

Engagement: [paste]. Identified risks: [paste]. Draft a 500-word risk register: named risk-by-risk with likelihood and impact, named mitigation per risk with owner, named trigger events that elevate risk, named escalation path, named review cadence. Risk registers without named owners and triggers atrophy.

13. Resource plan for engagement

Engagement: [paste, scope, duration]. Available team: [paste]. Draft a 500-word resource plan: named team members with role and time allocation by phase, named gaps and named contractor or partner support, named utilization and burn analysis, named contingency for over-run, named named ramp and ramp-down. Resource plans without contingency produce burnout or over-staff drift.

14. Engagement schedule with milestones

Engagement scope: [paste]. Duration: [paste]. Key deliverables: [paste]. Draft a 500-word schedule memo: named phase-by-phase with start and end dates, named deliverable milestones with named review points, named client decision points, named dependencies and risks to schedule, named change management for schedule shifts. Schedules without named dependencies produce schedule slippage with no diagnosis.

15. Pre-engagement client material review

Available client materials: [paste named documents, recent earnings, strategy decks, public information]. Engagement scope: [paste]. Draft a 600-word pre-engagement review memo: named factual summary of client context, named strategic priorities surfaced, named open questions for the kickoff, named hypotheses for the engagement, named knowledge gaps to fill in week 1. Pre-engagement reviews skipped produce ill-prepared kickoffs.

16. Initial findings memo (week 1)

Engagement: [paste]. Week 1 research and interview findings: [paste]. Draft a 700-word initial findings memo: named factual summary, named emerging hypotheses with supporting evidence, named hypotheses rejected with rationale, named open questions, named recommended focus areas for next phase, named client validation needed. Findings memos that read as work logs produce no engagement direction.

17. Engagement plan revision memo

Original plan: [paste]. Reason for revision: [paste, e.g. scope expansion, findings, client constraint]. Draft a 500-word revision memo: named change with rationale, named impact on timeline and budget, named impact on deliverables, named client sign-off required, named risk implications. Revisions made without client sign-off produce surprise at engagement close.

18. Pricing assumptions memo

Engagement scope: [paste]. Internal pricing rationale: [paste hours, rates, margin target]. Draft a 500-word pricing assumptions memo (internal): named scope assumptions, named time and team assumptions, named risk and contingency assumptions, named pricing structure (fixed, T&M, milestone-based, value-based), named alternative structures considered, named profitability target. Pricing without explicit assumptions produces dispute when assumptions break.

19. Scope creep response framework

New client request: [paste]. Original scope: [paste]. Draft a 400-word scope creep response: named factual analysis of the request vs original scope, named options (absorb within scope, change order with named fee, defer to next engagement, decline with respect), named recommendation with rationale, named conversation framework with client. Scope creep absorbed silently produces margin erosion and disgruntled consultant teams.

20. Engagement closure memo

Engagement: [paste]. Outcomes delivered: [paste]. Draft a 600-word closure memo: named factual recap of engagement, named outcomes against success criteria, named open items handed off, named recommended follow-up engagements with rationale, named case study eligibility with client approval, named lessons learned. Closures without case study eligibility ask produce missed BD opportunities.

21. Market sizing (TAM, SAM, SOM)

Market: [paste category, geography, time horizon]. Available data: [paste]. Draft a 700-word market sizing memo: named TAM calculation with methodology and sources, named SAM with explicit narrowing assumptions, named SOM with bottom-up and top-down reconciliation, named sensitivity to key assumptions, named growth projection with methodology, named comparison to public benchmarks. Sizing memos that pick a number from an analyst report without methodology produce client pushback.

22. Competitive landscape analysis

Industry: [paste]. Named competitors: [paste]. Strategic question: [paste]. Draft a 700-word competitive landscape: named competitors mapped on named axes relevant to strategic question, named positioning per competitor with evidence, named strategic moves and signals, named white space or contested space, named competitive dynamics implications, named recommendations. Competitive landscapes mapped on size-vs-share without strategic axes produce thin insight.

23. Industry trend analysis

Industry: [paste]. Time horizon: [paste]. Available signals: [paste]. Draft a 600-word industry trend analysis: named trends ranked by impact and certainty (5-7 typical), named drivers behind each trend, named timing implications, named winners and losers per trend, named client positioning implications. Trend analyses that list every trend without ranking produce noise.

24. SWOT analysis with named sources

Subject: [paste company, division, or initiative]. Available data: [paste]. Draft a 500-word SWOT with sources: named strengths with evidence and source, named weaknesses with evidence and source, named opportunities with sizing, named threats with likelihood and impact, named strategic implications. SWOTs with adjectives in each quadrant without evidence produce no decision input.

25. Porter's Five Forces analysis

Industry: [paste]. Strategic question: [paste]. Draft a 600-word Five Forces analysis: named buyer power with evidence and trajectory, named supplier power with evidence and trajectory, named threat of new entrants, named threat of substitutes, named competitive rivalry, named industry profitability implication, named client strategic implications. Five Forces applied as a checklist without strategic implications produces consulting theater.

26. Customer segmentation analysis

Customer base: [paste]. Available data: [paste behavioral, firmographic, value]. Draft a 700-word segmentation analysis: named segmentation criteria with rationale, named segment definitions with size and economics, named segment-specific behaviors and needs, named segment-level recommendations, named operational implications for client. Segmentation by demographic without value implications produces strategy that does not change.

27. Value chain mapping

Industry or company: [paste]. Strategic question: [paste]. Draft a 600-word value chain memo: named primary activities, named support activities, named value capture per activity, named cost structure per activity, named strategic levers for client, named recommended focus areas. Value chains that list activities without value capture produce description without insight.

28. Benchmarking analysis

Subject: [paste, e.g. operational metric, process, capability]. Comparison set: [paste]. Draft a 600-word benchmarking analysis: named benchmark sources and methodology, named comparison metrics, named client position vs benchmarks, named gap analysis, named cause hypothesis for gaps, named closing-the-gap recommendations. Benchmarking that reports gaps without cause hypothesis produces no actionable recommendation.

29. Capability assessment

Client organization: [paste]. Strategic ambition: [paste]. Draft a 700-word capability assessment: named capabilities required for strategic ambition, named current capability state per dimension (people, process, technology, organization), named gap per capability, named build vs buy vs partner per gap, named timeline and investment. Capability assessments without gap-by-capability detail produce vague org change recommendations.

30. Data validation memo

Data set: [paste source, scope]. Analysis being run: [paste]. Draft a 400-word data validation memo: named data quality checks (completeness, consistency, accuracy, timeliness), named anomalies found with hypothesis, named adjustments made with rationale, named caveats for downstream analysis, named confidence level. Analyses run on unvalidated data produce client distrust at the first questioned number.

31. Survey design for client research

Research question: [paste]. Target respondents: [paste, sample size]. Draft a 600-word survey design memo: named research hypotheses to test, named question structure with required statistical rigor, named sample frame and recruitment, named response targets for significance, named analysis plan, named timeline. Surveys designed without statistical sample sizing produce results with no significance.

32. Interview synthesis memo

Interviews conducted: [paste named individuals, themes from notes]. Draft a 700-word synthesis memo: named consensus themes with named supporting quotes (attributed by role not name where confidential), named contested themes with named perspectives, named outlier insights worth pursuing, named hypothesis validation status, named follow-up interviews needed. Interview syntheses that report verbatim transcripts produce no insight.

33. Case study research compilation

Client question: [paste]. Available case study sources: [paste]. Draft a 600-word case study memo: named relevant cases with brief summary, named applicable lessons per case, named caveats on applicability (industry, scale, era), named pattern across cases, named recommendation derived. Case study memos that quote cases verbatim without pattern synthesis produce no client insight.

34. Regulatory environment scan

Industry: [paste]. Jurisdictions: [paste]. Strategic question: [paste]. Draft a 600-word regulatory scan for legal review: named applicable regulations and authorities, named recent regulatory changes and proposed changes, named compliance implications for client, named strategic implications, named monitoring requirements. Regulatory scans done without legal counsel input produce client exposure if treated as legal advice.

35. Technology landscape assessment

Technology category: [paste]. Client context: [paste]. Draft a 600-word technology assessment: named vendors and solutions ranked by named criteria, named maturity assessment per solution, named client fit assessment, named implementation considerations, named build-buy-partner recommendation. Technology assessments that rank by vendor marketing without fit assessment produce poor client decisions.

36. Financial benchmarking analysis

Client financials: [paste]. Comparison set: [paste public peers, private peers if available]. Draft a 600-word financial benchmarking: named per-metric comparison (margins, working capital, capital efficiency, growth), named percentile positioning, named drivers of variance, named operational implications. Financial benchmarking without operational drivers produces conclusion without recommendation.

37. Cost structure analysis

Client cost base: [paste by category]. Industry benchmarks: [paste]. Draft a 600-word cost structure analysis: named category-by-category cost vs benchmark, named drivers of variance, named structural vs cyclical components, named optimization opportunities ranked by impact and feasibility, named tradeoff considerations. Cost structure analyses without tradeoff considerations produce slash-and-burn recommendations.

38. Make-buy economic analysis

Need: [paste]. Make option: [paste cost and capability]. Buy options: [paste vendors and pricing]. Draft a 700-word make-buy analysis: named total cost of ownership per option over named horizon, named strategic considerations (control, differentiation, scalability), named risk assessment per option, named recommended path with rationale, named transition plan. Make-buy analyses on price alone miss the strategic dimensions.

39. Sensitivity analysis methodology

Model with key assumptions: [paste]. Driver variables: [paste]. Draft a 500-word sensitivity analysis memo: named sensitivity variables ranked by impact, named methodology (one-at-a-time, Monte Carlo, scenario), named output (tornado chart, scenario matrix), named decision implications under different scenarios. Sensitivity analyses run without methodology produce false precision in client recommendations.

40. Research synthesis to insights

Raw research findings: [paste]. Engagement question: [paste]. Draft a 700-word synthesis memo: named top 3-5 insights with supporting evidence, named MECE structure of insights, named so-what for each insight, named recommendation framework derived, named open questions remaining. Research synthesis that reports findings without insight produces deliverables that the client reads but does not act on.

The best consulting deliverable answers the question the client did not know how to ask. The pack is built for deliverables like that.PromptLeadz AI Consulting Pack

41. Strategy memo (1-page executive summary)

Engagement findings: [paste]. Recommendation: [paste]. Draft a 350-word executive summary: named recommendation in the first sentence, named rationale in three to four bullets, named expected outcomes with named metrics, named investment required, named decision asked of executive. Executive summaries that bury the recommendation produce executive frustration.

42. Strategy memo (10-page deep dive)

Engagement findings: [paste]. Recommendation: [paste]. Draft a 2500-word strategy memo: named executive summary, named context and problem statement, named approach and methodology, named findings with evidence, named options considered with tradeoffs, named recommended path with rationale, named implementation roadmap, named risks and mitigations, named expected outcomes and measurement. Strategy memos that perform thoroughness without structure produce unread documents.

43. Recommendation memo with options

Engagement question: [paste]. Three viable options: [paste]. Draft a 600-word recommendation memo: named option-by-option summary, named evaluation criteria with weights, named scoring per option per criterion, named tradeoffs honestly named, named recommended option with rationale, named caveats and risks. Recommendation memos that pre-cook the answer without honest tradeoffs produce client distrust.

44. Decision matrix design

Decision: [paste]. Options: [paste]. Criteria: [paste]. Draft a 500-word decision matrix memo: named criteria with explicit weighting, named option-by-option scoring with evidence, named sensitivity to weighting, named recommended option, named caveats. Decision matrices with arbitrary weights produce false precision.

45. 2x2 strategic prioritization framework

Items to prioritize: [paste]. Strategic context: [paste]. Draft a 400-word 2x2 framework memo: named axes with explicit definitions, named quadrant interpretations, named items mapped with rationale, named recommended actions per quadrant. 2x2s with vague axes produce decorative content; this prompt forces axis definitions.

46. Phased implementation roadmap

Recommendation: [paste]. Available implementation resources: [paste]. Draft a 700-word phased roadmap: named phase 1 (typically 90-day) with explicit scope and outcomes, named phase 2 (typically 6-month), named phase 3 (typically 12-month), named dependencies between phases, named milestones and decision points, named owner per workstream. Phased roadmaps without named owners produce wishlist documents.

47. Quick-wins memo

Engagement findings: [paste]. Available quick-win candidates: [paste]. Draft a 500-word quick-wins memo: named 3-5 quick-wins with specific actions, named expected impact with quantification, named timeline (typically 30-90 days), named resource requirement, named risk to broader engagement if quick-wins distract. Quick-wins memos that include items requiring 6 months are mislabeled.

48. Business case memo

Investment or initiative: [paste]. Strategic rationale: [paste]. Draft a 700-word business case: named investment with cost phasing, named expected benefits with timing and quantification, named ROI and payback, named sensitivity, named alternatives considered, named kill criterion, named decision asked. Business cases without explicit alternatives produce approve-by-default decisions.

49. ROI calculation methodology

Initiative: [paste]. Available financial assumptions: [paste]. Draft a 500-word ROI methodology memo: named cost build with assumptions, named benefit build with assumptions and probability, named discount rate or hurdle rate with rationale, named time horizon, named sensitivity analysis, named risk-adjustment. ROI calculations without explicit methodology produce client questions on the first review.

50. Risk-adjusted recommendation

Recommendation: [paste]. Identified risks: [paste]. Draft a 500-word risk-adjusted memo: named risk-by-risk assessment, named impact on outcome, named mitigation plan, named contingency, named risk-adjusted expected value, named recommendation with named caveats. Recommendations without explicit risk adjustment produce client surprise when risks materialize.

51. Executive deck outline (10 slides)

Engagement: [paste]. Audience: [paste, typically C-level]. Draft a 700-word 10-slide outline: slide 1 named recommendation (one sentence), slide 2 context and problem, slide 3 approach summary, slides 4-6 findings with evidence, slide 7 options considered, slide 8 recommended path, slide 9 implementation roadmap, slide 10 decisions asked. Executive decks that lead with context before recommendation lose the room.

52. Board deck outline (5 slides)

Engagement: [paste]. Audience: board or audit committee. Draft a 500-word 5-slide outline: slide 1 named recommendation and decision asked, slide 2 named context and rationale, slide 3 named expected outcomes with metrics, slide 4 named risks and mitigations, slide 5 named implementation summary and next steps. Board decks that exceed 5 slides on a single topic produce board pushback.

53. Working session deck (15 slides)

Working session: [paste topic, attendees]. Goal: [paste]. Draft a 700-word 15-slide working session outline: named opening framing slides (2-3), named content slides for discussion (8-10), named decision and next-step slides (2-3), named workshop activities or polls if applicable, named timing per slide. Working sessions that present at the room without activities produce no decisions.

54. Appendix construction methodology

Main deck: [paste topics]. Supporting materials: [paste]. Draft a 400-word appendix methodology memo: named appendix items with reference to main deck, named structure (one topic per appendix slide), named decision rule for what makes main deck vs appendix (5-second test, executive must-see vs analyst reference), named cross-reference discipline. Appendices that pad the main deck produce reader fatigue.

55. Storyline pyramid (MECE)

Engagement findings: [paste]. Recommended action: [paste]. Draft a 600-word pyramid storyline: named top-line recommendation, named MECE supporting arguments (3-4 typically), named evidence per argument, named structure that a partner can challenge at any level. Pyramids that are not MECE at each level produce overlapping or missing arguments.

56. Pyramid principle synthesis

Raw analysis findings: [paste]. Draft a 500-word pyramid synthesis: named top-line answer in one sentence, named three-to-four supporting points that fully support the top line, named evidence supporting each point, named anti-arguments considered and rejected. Pyramids built bottom-up without top-line clarity produce structured but pointless documents.

57. Anchor chart design

Key insight or recommendation: [paste]. Available data: [paste]. Draft a 400-word anchor chart design memo: named chart type that fits the insight (not the data), named data treatment (filtering, aggregation, period selection), named labels and annotations that point to the insight, named source attribution, named accessibility considerations. Anchor charts that show all the data without pointing to the insight produce viewer confusion.

58. Process maps for client workflows

Process: [paste current state from interviews and observation]. Draft a 600-word process map memo: named process steps with named owner per step, named hand-offs and dependencies, named cycle times and friction points, named exception handling, named recommended future state with named changes, named change impact. Process maps that describe current state without future state recommendation produce no client value.

59. Org design recommendation memo

Current org: [paste structure, span, layers]. Strategic ambition: [paste]. Draft a 700-word org design recommendation: named proposed structure with rationale tied to strategy, named named role descriptions and seniority, named spans and layers, named transition plan, named comp implications, named change management. Org design recommendations made without change management produce structure that does not stick.

60. Implementation plan memo

Recommended initiative: [paste]. Available resources: [paste]. Draft a 700-word implementation plan: named workstreams with named owners, named milestones with dates, named dependencies and critical path, named resource and budget per workstream, named governance and decision rights, named change management and communication, named risk and contingency. Implementation plans without named owners produce strategy that does not implement.

61. Stakeholder interview kit

Stakeholder: [paste role, function, prior context]. Engagement scope: [paste]. Draft a 500-word interview kit: named opening framing (3 minutes), named context questions (5-10 minutes), named topic-specific probes (15-20 minutes), named open-ended invitation (5 minutes), named closing and follow-up (5 minutes), named topics to avoid. Interview kits that interrogate stakeholders without rapport produce defensive responses.

62. Difficult stakeholder navigation memo

Stakeholder: [paste, position, concerns]. Engagement context: [paste]. Draft a 500-word navigation memo: named honest assessment of stakeholder concerns, named root cause hypothesis (resistance to change, prior bad consultant experience, political position, legitimate concern), named engagement approach per cause, named alignment with sponsor or named escalation, named named conversation framing. Difficult stakeholder situations ignored produce engagement failure.

63. C-suite interview prep

Executive: [paste role, time available]. Engagement question: [paste]. Draft a 400-word C-suite prep: named opening that establishes context efficiently (1-2 minutes), named priority probes for executive perspective, named topics that may need executive decision or unblocking, named named close that respects executive time and confirms next step. C-suite interviews that spend 10 minutes on context waste the time slot.

64. Workshop design (full-day)

Workshop goal: [paste]. Attendees: [paste roles, count]. Available time: full day. Draft a 800-word workshop design: named opening and ground rules (45 minutes), named context-setting (60 minutes), named structured exploration activities (3-4 hours with breaks), named synthesis and decision activities (90 minutes), named close and commitments (30 minutes), named facilitation methods per activity, named output capture. Full-day workshops that present at the room without activities produce low engagement and no outputs.

65. Workshop design (half-day)

Workshop goal: [paste]. Attendees: [paste]. Time: half day. Draft a 600-word half-day workshop design: named opening (20 minutes), named one major exploration activity (90 minutes), named synthesis (45 minutes), named decision and commitments (30 minutes), named close (15 minutes). Half-day workshops trying to cover three major topics produce shallow coverage of all.

66. Workshop facilitation script

Workshop design: [paste]. Facilitator level of experience: [paste]. Draft a 600-word facilitation script: named opening script with exact framing, named transition phrases between activities, named handling for common scenarios (dominant voice, silence, conflict, off-topic), named timing checks, named close. Facilitation scripts that read as PowerPoint scripts without scenario handling produce stuck facilitation.

67. Workshop output synthesis

Workshop conducted: [paste named activities and raw outputs]. Draft a 600-word synthesis memo: named themes that emerged, named consensus decisions, named contested topics with positions, named action commitments with named owner and timing, named follow-up workshops if needed. Workshop syntheses that report verbatim sticky-note content produce no decision input.

68. Status update email (weekly)

Engagement week: [paste]. Progress and risks: [paste]. Draft a 300-word weekly status email: named factual progress against named milestones, named risks with named mitigation status, named decisions needed from client, named next-week plan, named stakeholder asks. Status updates that report activity without decisions needed produce reading without engagement.

69. Status update deck (bi-weekly)

Engagement progress: [paste two weeks of work]. Draft a 500-word bi-weekly status deck outline: slide 1 named summary and headline, slide 2 named progress vs plan, slide 3 named risks and mitigations, slide 4 named decisions needed, slide 5 named look-ahead, slide 6 named open items. Status decks that exceed 6 slides waste sponsor time.

70. Bad news delivery memo

Bad news: [paste, e.g. milestone slip, scope reduction, finding that complicates recommendation]. Draft a 400-word bad news delivery memo: named factual delivery in one sentence (no preamble), named cause honestly, named impact on engagement, named recovery or revised plan, named ownership of the situation, named what the client should do. Bad news buried in three paragraphs of softening produces worse trust damage than direct delivery.

71. Client pushback response framework

Client pushback: [paste their objection or concern]. Underlying analysis: [paste]. Draft a 500-word pushback response framework: named acknowledgment of the specific concern (not dismissal), named factual basis for our position, named common ground or legitimate consideration in their concern, named recommended path forward, named escalation if alignment is not reached. Pushback met with defensive justification produces escalation; this prompt acknowledges and reframes.

72. Client decision-making meeting facilitation

Decision needed: [paste]. Attendees and decision rights: [paste]. Draft a 500-word decision meeting facilitation guide: named opening that frames the decision and the constraint, named options presented clearly with tradeoffs, named structured discussion (each option, each stakeholder), named named decision rule and process, named documentation and follow-up. Decision meetings that meander without structured facilitation produce inconclusive outcomes.

73. Steering committee preparation

Steering committee meeting: [paste cadence, attendees, scope]. Engagement state: [paste]. Draft a 600-word steering committee prep memo: named engagement summary, named progress vs plan, named decisions needed from steering committee, named risks requiring committee awareness, named asks of individual members. Steering committees that read activity reports without decisions produce engaged-but-not-useful committees.

74. Working session facilitation

Working session goal: [paste]. Attendees: [paste]. Draft a 500-word working session facilitation guide: named opening framing, named structured activities, named time allocations, named facilitation methods, named output capture, named close and commitments. Working sessions facilitated without explicit method produce wandering discussions.

75. Workshop debrief synthesis

Workshop completed: [paste]. Internal team observations: [paste]. Draft a 500-word internal debrief memo: named what worked, named what did not, named lessons for next workshop, named client signal worth noting, named follow-up commitments by internal team. Workshop debriefs skipped produce repeated facilitation patterns.

76. Off-site planning memo

Off-site goal: [paste]. Attendees: [paste]. Duration and location: [paste]. Draft a 700-word off-site planning memo: named agenda by day or session, named pre-work for attendees, named external speakers or activities if applicable, named output goals, named logistics and budget, named follow-up plan. Off-sites planned without explicit output goals produce expensive team-bonding without business outcomes.

77. Cross-team alignment memo

Cross-team friction: [paste]. Goals: [paste]. Draft a 500-word alignment memo: named friction sources with diagnosis, named shared goals and metrics, named named handoff agreements, named cadence of cross-team reviews, named escalation paths. Alignment memos without shared metrics produce blame cycles.

78. Stakeholder action commitment matrix

Workshop or meeting outputs: [paste named decisions and commitments]. Draft a 400-word commitment matrix: named action with named owner, named due date, named dependencies, named success criterion, named status tracking method. Action items without named owners and dates produce unowned to-do lists.

79. Client feedback collection memo

Engagement phase complete: [paste]. Draft a 400-word feedback collection memo: named feedback methods (interviews, surveys, sponsor 1:1), named questions calibrated to surface candid input, named timing, named handling of feedback (acknowledgment, action, escalation), named close-the-loop commitment. Feedback collected without close-the-loop produces engagement-fatigue.

80. Engagement final readout deck

Engagement complete: [paste outcomes, deliverables, recommendations]. Draft a 700-word final readout deck outline: slide 1 named engagement summary and headline outcome, slide 2 named context recap, slide 3 named approach and methodology, slides 4-7 named findings and recommendations, slide 8 named implementation roadmap handed off, slide 9 named open items and risks, slide 10 named close with named follow-up engagement opportunities. Final readouts that summarize work without forward-looking framing produce no follow-up engagement.

81. New engagement pricing memo

Engagement scope: [paste]. Internal cost structure: [paste]. Market comp: [paste benchmarks]. Draft a 600-word pricing memo: named bottom-up cost build, named market-comparable benchmarks, named pricing structure recommendation (fixed, T&M, milestone, value-based), named pricing range with rationale, named approval needed. Pricing memos without explicit cost build produce margin erosion.

82. Multi-year master services agreement

Client: [paste]. Multi-year engagement framework: [paste]. Draft a 800-word MSA draft for counsel review: named master terms (term, fees structure, payment, IP, confidentiality, indemnification, limitation of liability), named SOW reference structure for individual engagements, named change management, named termination, named governing law. MSAs without counsel review produce dispute exposure across multiple engagements.

83. Practice utilization tracking memo

Practice team: [paste consultants and roles]. Target utilization: [paste]. Draft a 500-word utilization memo: named consultant-by-consultant utilization, named billable vs non-billable breakdown, named patterns (over-utilized, under-utilized), named root cause, named action (BD focus, pipeline reallocation, hiring, training time). Utilization tracked aggregate without consultant-level cuts hides burnout and underdevelopment patterns.

84. BD pipeline review

Pipeline state: [paste opportunities by stage, value, probability]. Capacity: [paste]. Draft a 500-word pipeline review: named pipeline coverage vs target, named at-risk opportunities, named bookings forecast, named BD action priorities, named partner involvement asks. Pipeline reviews that report value without coverage and risk produce surprise bookings misses.

85. Proposal win-rate diagnostic

Recent proposals: [paste wins and losses with named reasons]. Draft a 600-word win-rate diagnostic: named win rate overall and by segment, named win pattern themes, named loss pattern themes with cause hypothesis, named structural improvements to proposal approach, named coaching for proposal teams. Win-rate diagnostics that report aggregate without pattern hypothesis produce no improvement.

86. Engagement profitability review

Recent engagements: [paste billings, costs, margin]. Draft a 600-word profitability review: named engagement-by-engagement margin, named cause of high and low margin, named structural improvements (pricing, scoping, staffing, scope creep management), named lessons for next engagement pricing. Profitability reviews skipped produce repeated low-margin engagements.

87. Reusable IP library development

Practice IP assets: [paste frameworks, methodologies, templates, case studies]. Draft a 600-word IP library memo: named asset inventory with owner, named taxonomy and discoverability, named refresh and curation cadence, named contribution incentives for consultants, named IP protection considerations. IP libraries that accumulate without curation atrophy into stale content.

88. Case study writeup

Engagement: [paste with client approval, scope, outcomes]. Draft a 600-word case study: named client and context (with permitted detail), named challenge or question, named approach and methodology, named outcomes with quantification where possible, named lessons or replicable insight, named client quote if obtained. Case studies written without quantified outcomes produce thin marketing material.

89. Thought leadership content brief (for the practice)

Topic: [paste]. Target audience: [paste]. Practice expertise: [paste]. Draft a 500-word thought leadership brief: named central thesis the practice defends, named supporting arguments with evidence, named publication or distribution target, named author and reviewer, named timeline, named follow-up engagement angle. Thought leadership without explicit thesis produces forgettable content.

90. Practice positioning memo

Current positioning: [paste]. Competitive landscape: [paste]. Draft a 600-word practice positioning memo: named target client and engagement type, named differentiation from named competitors, named proof points (case studies, named consultants, named methodologies), named gaps and investments to strengthen positioning. Practice positioning that tries to be everything produces no clear client choice.

91. Junior consultant onboarding plan

New junior consultant: [paste background, level]. Practice context: [paste]. Draft a 600-word onboarding plan: named first-30-days (research, shadow, deliverable observation), named first-60-days (drafting and review), named first-90-days (own a deliverable end to end), named training (methodology, frameworks, tools, IP library), named mentor and feedback cadence, named success criteria. Junior consultant onboarding without explicit deliverable progression produces extended ramp.

92. Consultant performance review

Consultant: [paste role, level, tenure, review period]. Performance data: [paste engagements, utilization, client feedback, peer feedback]. Draft a 600-word review: named outcome metrics, named specific behavior strengths with examples, named growth areas with evidence, named development plan, named trajectory, named compensation implication. Performance reviews that praise generally and criticize vaguely produce no behavior change.

93. Manager and Director hiring rubric

Role: [paste level, scope, specialization]. Required dimensions: [paste e.g. client management, methodology depth, BD, people development]. Draft a 700-word hiring rubric: each dimension with leveling, named behavioral evidence patterns, named scenarios in interviews, named calibration anchors, named anti-bias considerations. Hiring rubrics built on tenure rather than evidence produce inconsistent quality.

94. Network of advisors development

Practice strategy: [paste]. Existing advisor relationships: [paste]. Draft a 500-word advisor network memo: named advisor archetypes needed (industry expertise, functional expertise, named market access), named engagement model (paid, equity, referral, reciprocal), named cadence of engagement, named knowledge management for advisor input. Advisor networks built ad-hoc without strategy produce underused relationships.

95. Conference and event strategy

Practice strategy: [paste]. Available events: [paste]. Draft a 500-word event strategy memo: named events to attend with rationale (BD, brand, learning), named sponsorship or speaking opportunities, named pre-event outreach plan, named in-event objectives, named post-event follow-up, named success metric. Event strategy without explicit BD objective produces expensive networking without pipeline.

96. Annual practice strategy review

Year performance: [paste bookings, utilization, margin, named engagements, team health]. Draft a 800-word annual practice review: named year-over-year movements on KPIs, named investments that paid off, named investments that did not, named structural changes, named next-year priorities, named hiring and capacity plan, named named asks. Annual reviews that report activity without causal analysis produce no organizational learning.

97. Practice marketing memo

Practice positioning: [paste]. Available channels: [paste]. Draft a 600-word marketing memo: named target audiences and named ICP, named content pillars tied to positioning, named distribution channels (LinkedIn organic, named publications, events, named partnerships), named investment by channel, named success metric. Practice marketing without explicit ICP produces broad content with no conversion.

98. Engagement quality review framework

Engagement completed: [paste]. Quality review purpose: [internal learning, partner accountability, client feedback]. Draft a 500-word quality review framework: named dimensions (client outcomes, deliverable quality, engagement management, team development), named scoring methodology, named documentation requirement, named feedback loop to team, named pattern analysis across engagements. Quality reviews scored on vibes without dimensions produce inconsistent feedback.

99. Knowledge management system memo

Practice IP and engagement learnings: [paste current state]. Draft a 600-word knowledge management memo: named content types (case studies, methodologies, templates, lessons learned, industry knowledge), named storage and discoverability system, named contribution incentives, named curation cadence, named search and retrieval expectations. Knowledge management systems that grow without curation produce searchable cruft.

100. Practice succession and exit memo

Practice leader scenario: [paste, e.g. retirement, transition, exit]. Practice state: [paste]. Draft a 700-word succession memo for counsel review: named succession options (internal promotion, external hire, sale, wind-down), named valuation and economics per option, named client relationship transition plan, named team retention considerations, named timeline, named legal and tax considerations. Practice succession unaddressed produces client and team panic when transition becomes urgent.

How the prompts fit a real consulting engagement and year

Engagement-level cadence: RFP and proposal (weeks before kickoff), scope and engagement letter (week 0), kickoff (week 1), discovery and research (weeks 1-3), analysis and synthesis (weeks 2-6), framework development and deliverable drafting (weeks 4-8), client review and refinement (weeks 6-9), final readout and closure (week 9-10).

Weekly cadence: status updates, internal team check-ins, partner reviews of major deliverables, BD pipeline check, utilization check, client sponsor 1:1s.

Monthly cadence: engagement profitability review, BD pipeline forecast, practice marketing review, IP library curation, performance check-ins, hiring pipeline review.

Quarterly cadence: proposal win-rate diagnostic, practice profitability review, capacity planning, conference and event review, partner performance review.

Annually: annual practice strategy review, hiring plan, IP library refresh, advisor network review, succession planning, named methodology updates.

A good consulting deliverable produces a client decision. A good engagement produces a client testimonial. A good practice produces case studies that earn the next engagement. The consulting job is framework work, judgment work, and relationship work in combination.PromptLeadz AI Consulting Pack, Section 6

Five mistakes that wreck consulting prompts

1. Filling the prompt with vibes instead of named client context, named hypotheses, named evidence. The prompts ask for specific client, specific scope, specific data sources, specific decision needed. Filling with "a strategy engagement" or "a transformation initiative" produces output that performs consulting aesthetic without substance.

2. Treating the output as the final deliverable. The prompts produce drafts. The actual deliverable is the draft after partner review, client-context refinement, removal of LLM-cliche phrasing, and verification of every claim. Delivering raw LLM output to a paying client is professional malpractice.

3. Skipping the partner review step. Several prompts depend on senior judgment that the LLM cannot replicate (industry context, prior client patterns, political sensitivity, methodology nuance). The cost of a sloppy LLM draft delivered without partner review is high.

4. Treating frameworks as decorations. 2x2s with vague axes, SWOTs with adjectives, Five Forces applied as checklists. The prompts force axis definitions, evidence, and strategic implications because frameworks without rigor produce consulting theater.

5. Skipping the engagement letter and MSA legal review. The pack includes prompts that produce drafts of legal documents (engagement letters, MSAs, IP and confidentiality clauses). The drafts require qualified counsel review before signing.

Sources and further reading

Barbara Minto's The Pyramid Principle remains the most rigorous public work on structured communication for consulting deliverables. The pack's structure prompts draw directly on Minto.

Ethan Rasiel's The McKinsey Way and The McKinsey Mind are the foundational practitioner reading on MECE thinking, hypothesis-driven analysis, and consulting methodology.

Vault and Management Consulted provide practitioner-grade content on consulting firms, practice areas, and case interview methodology.

Ardor and Consulting Quest are useful resources for boutique and independent consultants on practice development.

The IBM Consulting publications and the McKinsey, BCG, Bain, Deloitte, EY, and PwC firm blogs publish public-facing thought leadership that demonstrates the consulting voice the pack is calibrated for.

Tom Peters' In Search of Excellence and Peter Drucker's body of work remain the foundational reading on management itself, which consulting builds on.

About PromptLeadz

PromptLeadz publishes free component-built prompt packs and the production-grade Drop-in utilities that wrap them. The franchise covers role-based packs (PM, EM, CSM, Sales Leader, AE, Operator, Data Analyst, VC, HR, CMO, Customer Support, Recruiter, Finance, Consultants), format-based packs (.md agent files in breadth and depth), and the underlying frameworks (the 8-Component Skeleton, the Anti-Prompt-Engineering Manifesto).

Every pack rejects the LinkedIn-influencer voice at the prompt level by banning the genre's signature phrases inline. The result is output calibrated for memos that survive peer review, not threads that go viral. Free packs ship with no email gate at promptleadz.com.

Questions people ask about AI consulting prompts

The franchise: free packs, frameworks, and the manifesto

The thesis: The Anti-Prompt-Engineering Manifesto. The framework: The 8-Component Skeleton.

Free packs, no email gate · Calibrated for 2026 frontier models · promptleadz.com