10 AI Prompts I Use as a Consultant (Proposals, Discovery, Client Reports)
After three years of consulting — strategy work, technical advisory, and fractional roles — I've built a small library of AI prompts that handle the repetitive, high-stakes writing every consultant does: proposals, discovery notes, scope letters, status reports, and the awkward "this is out of scope" email.
Every prompt below follows the same structure: Role → Context → Constraints → Output. That structure is why they work. A vague prompt gives you vague copy. A constrained prompt gives you something you can actually send to a client.
I sell a broader collection of these at the end, but the 10 below are free. Copy them, test them, adapt them.
1. The Proposal That Forces Scope Before Price
The biggest mistake consultants make in proposals is quoting before scoping. This prompt reverses that: it produces a proposal that locks scope first, then ties price to that scope — making scope creep harder to argue later.
Prompt:
Role: You are a senior consultant writing a project proposal.
Context: The client is [CLIENT DESCRIPTION]. Their problem is [PROBLEM].
The engagement is [DURATION]. The deliverables are [DELIVERABLES].
Constraints:
- Start with a 2-sentence "What you get" summary a non-technical
buyer can repeat to their boss.
- List exactly 4 deliverables, each with a one-line "done looks like"
definition. No more than 4.
- Include a "Not included" section with at least 3 explicit exclusions.
- State the price only AFTER the scope and exclusions.
- Ban these words: comprehensive, robust, scalable, leverage, synergy.
Output: A proposal section, not a full document. Under 400 words.
Why it works: The "Not included" section is the most valuable part. Clients remember what you didn't list as excluded far more than what you listed as included. Three explicit exclusions set the boundary before the contract is signed.
2. Discovery Questions That Surface the Real Problem
Clients rarely state their actual problem in the first conversation. They state a symptom. This prompt generates discovery questions designed to find the gap between what they say they want and what they actually need.
Prompt:
Role: You are a consultant preparing for a discovery call.
Context: The client says their problem is [STATED PROBLEM].
They are in [INDUSTRY]. Their team size is [SIZE].
Constraints:
- Generate exactly 8 questions.
- The first 3 must be about the current state (what's happening now,
how it's measured, who feels the pain).
- The next 3 must be about the desired future state (what changes
if this is solved, how they'll know, what success looks like in
revenue or time).
- The last 2 must be "the questions they hope you don't ask" —
the ones that surface hidden constraints, political dynamics,
or budget realities.
- No question may be answerable with yes/no.
- After each question, include a one-line "why I'm asking this"
note in parentheses.
Output: Numbered list, ready to paste into a meeting doc.
Why it works: The "questions they hope you don't ask" section is where the real engagement value lives. A client who answers those honestly has decided to trust you. A client who dodges them has told you something equally important.
3. The Scope-Creep Defense Letter (Polite, Firm, On Record)
Every consultant needs a template for "that's a great idea, and it's not in the scope we agreed on." This prompt produces a professional, non-confrontational response that creates a paper trail without damaging the relationship.
Prompt:
Role: You are a consultant responding to a client's new request
that falls outside the agreed scope.
Context: The original scope was [ORIGINAL SCOPE]. The new request
is [NEW REQUEST]. The client is [CLIENT NAME].
Constraints:
- Open with genuine acknowledgment of the request's value
(1 sentence, specific, not generic praise).
- State clearly that it is outside the current scope, using the
word "scope" explicitly.
- Offer exactly 2 paths forward: (a) add it as a change order with
an estimated cost range, or (b) defer it to a future phase.
- Do NOT apologize. Do NOT use "unfortunately." Do NOT hedge
with "I wish I could."
- Close with a question that moves the decision back to them.
- Under 150 words.
Output: An email ready to send. Subject line included.
Why it works: The two explicit paths prevent the client from hearing "no" — they hear "here's how we can do this" instead. The word "scope" creates the legal anchor. The question at the end prevents the conversation from stalling.
4. The Stakeholder Status Report (Written for a VP Who Skims)
Consultants write status reports for two audiences: the day-to-day client contact (who wants detail) and that contact's boss (who wants the bottom line). This prompt optimizes for the boss — because if the boss can't parse your report in 20 seconds, your contract doesn't get renewed.
Prompt:
Role: You are a consultant writing a weekly status report.
Context: This week we [COMPLETED TASKS]. Next week we plan to
[NEXT TASKS]. The main risk is [RISK].
Constraints:
- First line must be exactly one of: "On track" or "At risk" or
"Blocked" — no other opening allowed.
- Second line: one sentence on what was accomplished, in past tense,
with a concrete metric if possible.
- Third section: "Next week" with max 3 bullet points, each starting
with a verb.
- Fourth section: "Risks / decisions needed" — max 2 items. If a
decision is needed from the client, bold the ask and name who needs
to decide.
- Total length under 200 words. No jargon. No "we continued to."
Output: A report formatted for email, ready to paste.
Why it works: The forced status opener ("On track" / "At risk" / "Blocked") is the single most important line a VP reads. Everything else is supporting detail. The bolded decision asks prevent the "I didn't realize you needed me to decide that" failure mode.
5. The Discovery Call Summary That Prevents "You Never Said That"
The post-call summary email is your legal protection. If a client later claims you promised something you didn't, this email — sent within 24 hours — is your evidence. This prompt produces a summary that's thorough without being a transcript.
Prompt:
Role: You are a consultant writing a discovery call follow-up.
Context: The call was with [CLIENT]. The discussed problem was
[PROBLEM]. Key points raised: [RAW NOTES — paste everything].
Constraints:
- Structure: "What I heard" → "What I understand the goal to be"
→ "Open questions" → "Proposed next step."
- In "What I heard," preserve at least 2 verbatim quotes from the
client's notes (mark them with quotation marks). Do not paraphrase
these — the exact wording matters.
- In "What I understand the goal to be," restate the problem in one
sentence. If the client said "we need X" but you suspect they need
Y, state BOTH: "You described needing X. Based on what you shared,
I believe the underlying goal is Y. Is that accurate?"
- "Open questions" must have at least 2 items the client needs to
answer before a proposal can be written.
- Close with a specific next step and a date, not "let me know."
Output: An email, under 350 words.
Why it works: The verbatim quotes are the protection layer. The "you described X, but I believe the goal is Y" structure surfaces misalignment before you scope the work — which is the single most expensive mistake in consulting.
6. The Case Study That Doesn't Sound Like Marketing
Consultants need case studies, but most case studies read like sales pages. This prompt produces a case study that sounds like an honest retrospective — which is far more persuasive to skeptical buyers.
Prompt:
Role: You are a consultant writing a case study from a completed
engagement.
Context: Client was [CLIENT]. Problem was [PROBLEM]. What we did
was [APPROACH]. Outcome was [OUTCOME].
Constraints:
- Structure: "The situation" (2 sentences) → "What we tried first"
(1 sentence, and it should be something that partially failed or
needed adjustment) → "What actually worked" (3-4 sentences) →
"The result" (1-2 sentences with a metric) → "What I'd do
differently" (1-2 sentences of honest reflection).
- The "What we tried first" section must include something that
didn't work perfectly. Honesty about failure builds credibility.
- Ban: transformative, game-changing, revolutionary, seamless,
cutting-edge, world-class, industry-leading.
- Include one specific number in "The result" — revenue, time saved,
error rate reduced. If no number is available, say "the client
reported" and describe the qualitative change.
Output: 300-500 words. Written in first person.
Why it works: The "What we tried first" failure section is the credibility engine. A case study that admits a mid-course correction reads as authentic; a case study that describes a flawless execution reads as fabricated.
7. The Retainer Pitch (For Project Clients Who Keep Coming Back)
Converting one-off project clients to retainers is the highest-leverage move a consultant can make. This prompt produces a retainer proposal that frames the ongoing relationship as risk reduction for the client, not as a revenue play for you.
Prompt:
Role: You are a consultant pitching a retainer to an existing
project client.
Context: We just completed [PROJECT]. The client is [CLIENT].
The work touched [AREAS].
Constraints:
- Do NOT lead with price. Lead with the problem the retainer solves:
"knowledge transfer decay" — the fact that in 60 days, the context
from this project will start to fade from their team's memory.
- Frame the retainer as 3 things: (1) continuity — someone who
remembers the decisions and why, (2) on-call advisory for the
inevitable follow-up questions, (3) a quarterly check-in to catch
drift before it becomes a problem.
- State the retainer as a monthly amount with a clear "what's
included" list (hours, response time, deliverables).
- Include a "month-to-month, cancel anytime" clause. Retainers that
require commitment create friction; let the value retain the client.
- Under 250 words.
Output: An email proposing the retainer. Ready to send.
Why it works: The "knowledge transfer decay" framing is the real value proposition — and it's one clients feel viscerally but rarely articulate. Naming it makes you look like you understand their problem better than they do.
8. The Pricing Tiers Page (Honest, Not Manipulative)
Most pricing pages use dark patterns: hiding the real price, using fake "most popular" badges, or creating artificial scarcity. This prompt produces a pricing page that converts through honesty — which, for B2B consulting, outperforms manipulation.
Prompt:
Role: You are a consultant writing a pricing page for your services.
Context: You offer 3 engagement tiers. Tier 1: [SCOPE] at $[PRICE].
Tier 2: [SCOPE] at $[PRICE]. Tier 3: [SCOPE] at $[PRICE].
Constraints:
- Name each tier by what it does, not by precious metal names or
superlatives. (E.g., "Focused Project," "Embedded Engagement,"
"Full Transformation" — not "Basic / Pro / Enterprise.")
- For each tier, list: what's included (3-4 bullets), who it's for
(1 sentence), and who it's NOT for (1 sentence of honest
disqualification).
- Do NOT use "Most Popular" badges or fake countdown timers.
- Do NOT hide the price behind a "Contact us" button unless the
work is genuinely custom.
- Include a one-line note: "If you're unsure which tier fits, start
with [TIER 1]. You can upgrade mid-engagement at prorated rates."
- End with a single CTA, not three competing buttons.
Output: Pricing page copy, ready for a landing page.
Why it works: The "who it's NOT for" disqualification is the conversion driver — it signals confidence and saves both sides from a bad fit. The "start with Tier 1, upgrade later" reduces the decision anxiety that kills deals.
9. The Project Kickoff Doc That Aligns Everyone Before Day One
The kickoff document is where misaligned expectations hide. This prompt produces a one-page doc that forces alignment on scope, communication, and success criteria before any billable work begins.
Prompt:
Role: You are a consultant creating a project kickoff document.
Context: The project is [PROJECT]. The client team is [TEAM — roles
and names]. The duration is [DURATION].
Constraints:
- Sections: "Objectives" → "Scope" → "Out of scope" → "How we'll
work" → "Success criteria" → "Key dates."
- "Objectives": exactly 2, each starting with a verb, each measurable
or observable (not "improve efficiency" — "reduce report generation
time from 3 days to 1 day").
- "Scope": max 6 bullets. Each bullet is a deliverable with a
"done looks like" definition.
- "Out of scope": min 3 bullets. This is non-negotiable — every
project has exclusions.
- "How we'll work": communication channel, response time expectation,
meeting cadence, and who the single point of contact is on each side.
- "Success criteria": 2-3 criteria the client will use to judge
whether the project was worth it. These must be stated by the
client, not by you.
Output: One page. Bullet-heavy. No paragraphs over 3 sentences.
Why it works: The "success criteria stated by the client" section is the renewal insurance. If you can point to it at project end and say "here's what you said success looks like — here's how we delivered against it," the conversation shifts from "was this worth it?" to "what's next?"
10. The End-of-Engagement Letter (That Opens the Next One)
The last deliverable of every engagement is the relationship-maintenance letter — the note that converts a one-time project into a long-term client. Most consultants skip it. This prompt makes it easy.
Prompt:
Role: You are a consultant writing the final note at the end of
an engagement.
Context: The project was [PROJECT]. The outcome was [OUTCOME].
The client contact was [NAME].
Constraints:
- Structure: "What we accomplished" (2 sentences, factual, with one
metric) → "What I'd watch going forward" (2-3 genuine observations
about risks or opportunities the client should monitor — not
generic advice, specific to what you saw during the work) → "How
I can help in the future" (2-3 specific ways, not "reach out
anytime").
- Do NOT ask for a referral directly. Instead, end with: "If you
know someone facing a similar challenge, I'm always happy to have
an initial conversation — no pressure, no pitch."
- Do NOT use "it's been a pleasure" or "I've enjoyed working with
you." Show, don't tell — reference one specific moment from the
engagement that you genuinely appreciated.
- Under 250 words.
Output: An email. Ready to send on the last day of the engagement.
Why it works: The "What I'd watch going forward" section is the seed of the next engagement — it plants a specific concern or opportunity that the client will think about in 3-6 months, and when they do, you're the person they call. The specific-moment reference (instead of "it's been a pleasure") makes the note feel written by a human, not generated.
How I Test These Prompts (So You Don't Have To Guess)
Every prompt above went through this process:
- Run it 3 times with the same inputs. If the outputs vary wildly, the prompt is too vague — tighten the constraints.
- Run it on a different problem. A prompt that works only for one industry is over-fit. Test it on something unrelated.
- Read the output aloud. If it sounds like AI wrote it, the prompt needs stronger negative constraints (the "ban these words" lines).
- Cut anything generic. If a line could appear in any consultant's document, delete it from the template. Specificity is what makes a prompt reusable across different engagements.
Where to Get More
These 10 prompts are a subset of a larger library I built and tested over the past year. If you want the full collection — including prompts for contract review, competitive analysis, pricing strategy, client onboarding sequences, and quarterly business reviews — they're available here:
- Developer Product-Launch Prompt Pack ($9) — 7 prompts for shipping products, launch tweets, Show HN posts, changelogs. If you build anything.
- Developer Productivity Prompt Library ($49) — 30 prompts for code reviews, debugging, architecture decisions, technical documentation.
- SaaS Marketing Copy Prompt Pack ($49) — 25 prompts for landing pages, cold emails, ad copy, pricing pages. If you sell anything.
- AI Startup Operations Prompt System ($199) — 50+ prompts and 10 workflows for running an entire operation: hiring, roadmaps, metrics, investor updates, retros. The most relevant pack for consultants doing fractional/strategy work.
- AI Business Transformation Playbook ($999) — 100+ prompts and 12 workflows. The complete system for an AI-augmented consulting practice.
Or browse everything at innovate01.gumroad.com.
If you found this useful, the biggest thing you can do is share it with one consultant or freelancer you know who's drowning in proposals and client communication. These prompts exist because I was that person.
Top comments (0)