Using AI as a Consultant or Fractional Executive
Where AI actually earns its keep in a consultant or fractional executive's real week, three prompts built for scoping engagements and pricing value, and which documented consulting frameworks are worth loading alongside it.
A consultant or fractional executive's week runs on a smaller number of high-stakes calls than a team-based agency's does, but each one carries more weight per decision: is this engagement actually scoped to what the client needs, or has it quietly drifted, is the fee structure actually tied to the value delivered or just to hours billed, is a client relationship still built on trust or running on inertia. Generic AI use treats each as a fresh question. The more useful use treats them as the same few recurring calls, run the same structured way every time.
What does a consultant or fractional executive's actual week look like?
The recurring calls are fewer than an agency owner's but heavier: whether an engagement that started with a clear brief has quietly drifted into something else entirely, whether the fee agreed at the outset still reflects the value actually being delivered now, whether a client relationship that used to involve real candor has settled into polite compliance, and, for a fractional executive specifically, whether a decision landing on your desk is actually yours to make or should be escalated back to the client's own leadership. None of these show up as a single dramatic moment. They show up as a slow drift that's obvious in hindsight and easy to miss in the moment, week over week, until the gap between what was agreed and what's actually happening has grown too large to raise casually.
Solo practice compounds the problem in a specific way: there's no colleague down the hall to notice the drift before you do, and no second opinion in the room when a pricing or scope question comes up mid-engagement. The judgment calls that a larger firm might catch through internal review land entirely on one person, usually while that person is already deep inside the work and least positioned to see it from the outside.
Where does generic AI actually help here, and where does it quietly fail?
Unaided, it's genuinely useful for translating a described engagement outcome into an actual value estimate, and for drafting a scope document precisely once you've described what's actually included.
It's weak at anything requiring knowledge only you have: whether this specific client's budget has quietly tightened, whether their internal politics have shifted since the engagement started, whether the polite compliance you're getting now is trust or its absence. Feed it a request without that context and it will still produce a confident-sounding answer.
What are the three prompts worth running this week?
These run in Claude, ChatGPT, or Gemini as written.
"Here's the original engagement scope: [paste it]. Here's what I've actually been asked to do over the past month: [describe it]. Where has this drifted from the original scope, and by how much?"
Why it works: scope drift happens gradually enough that no single request feels like the moment it happened, and comparing the current pattern against the original document in one pass surfaces the accumulated gap that no individual week would have shown.
"This engagement is producing [describe the outcome, revenue impact, risk avoided, time saved] for the client. Translate that into a dollar estimate of value, not a rate for my time, and tell me what fee that would justify."
Why it works: most consultants can describe what they did but struggle to translate it into the client's own financial terms, and forcing the translation usually produces a number well above an hourly calculation.
"Here's what's changed in this client relationship recently: [describe it]. Score whether the issue looks like a credibility problem, a reliability problem, or an intimacy problem, and whether I might be contributing through my own self-orientation."
Why it works: separating the four inputs forces a specific diagnosis instead of a vague sense that the relationship feels different, and the self-orientation check catches the one input most people are least willing to examine in themselves.
What's the honest limit here, even with all three run?
Run all three and this engagement's scope, pricing, and trust read will be sharper than gut feel alone. What you won't have is knowledge of the client's actual budget ceiling, their internal politics, or what they tried and rejected before they hired you. The gap isn't this engagement; it's that no prompt substitutes for the read a consultant builds from being inside the relationship, watching how the client actually behaves under pressure.
Which documented frameworks actually fit a consultant, and why?
David Maister's Trust Equation, developed jointly with Charles Green and Robert Galford in The Trusted Advisor, Trustworthiness equals Credibility plus Reliability plus Intimacy, divided by Self-Orientation, gives a structured diagnostic for exactly the trust-erosion pattern consultants hit most. Peter Block's Flawless Consulting argues that authentic engagement with the real, sometimes uncomfortable problem matters more than technical correctness in whether an engagement actually lands. Alan Weiss's documented value-based fees method, published across Million Dollar Consulting and Value-Based Fees, makes the case for pricing against the value created rather than the hours spent.
Each targets a different failure mode: Maister for a relationship quietly running on compliance instead of candor, Block for engagements that stay technically correct but never touch the real issue, Weiss for fees that have drifted below the value actually being delivered. A single engagement can genuinely need all three at different points, diagnosing the relationship early, staying engaged with the real problem throughout, and repricing before the fee quietly falls behind the value.
How do you actually load one of these into Claude, ChatGPT, or Gemini?
In Claude, each installs as a Skill: go to Settings → Skills → Add skill and upload the .zip. Claude reads the skill's description and auto-invokes it when your question matches, or you can force it with /peter-block-framework at the start of a message. Claude Code users get the same thing via ~/.claude/skills (every project) or a project's .claude/skills folder (that project only).
In ChatGPT, the plain .md file goes into a Custom GPT: Create a GPT → Configure → Instructions, paste the framework's content in. Standard Custom Instructions (the "About me" fields) cap out at 1,500 characters, too short for a full framework, so use a Custom GPT specifically, not Custom Instructions.
In Gemini, paste the .md content directly into the system prompt if the interface you're using supports one, or lead your first message with it: "Here is a thinking framework to apply throughout this conversation. Read it carefully, then answer using this framework's approach," followed by the file's contents.
Where should a consultant actually start?
The Consultant & Advisor category collects Maister, Block, and Weiss alongside Blair Enns and David C. Baker, each a documented method for a different part of the same practice. For the pricing conversation specifically, Pricing Decision is a $99 tool built to structure exactly that call before you send the quote.
All the copy-paste prompts from this guide, and the rest of the AI Practice series, live at /prompts too, free to copy without reading the guide first.
Frequently asked questions
How is this different from the agency owner guide already on the site?
The recurring decisions overlap since both roles sell expertise, but the shape differs. An agency owner is usually managing a team and a client book at once; a solo consultant or fractional executive is usually managing one engagement's scope and one client's trust at a time, often across multiple part-time clients rather than one full-time team. The prompts here are built for that specific rhythm.
Can AI actually help me price an engagement, or just talk about pricing in the abstract?
It can help you translate a client's likely value from an engagement into an actual number, if you describe what the engagement produces for them, concretely and specifically. It cannot know what a specific client will actually agree to pay, since that depends on their budget reality and their alternatives, neither of which it has access to unless you tell it directly.
Is it dishonest to use AI to draft a proposal or engagement scope?
Not for structuring one, which is what these prompts are built for. Using AI to generate the underlying diagnosis of a client's problem, the part that's actually your expertise, would be a different and more troubling use of it. Structuring how you present a diagnosis you've already made yourself is closer to what a proposal template or a good editor does for a piece of writing.
What's the single biggest mistake consultants make asking AI for help here?
Asking it whether to take an engagement instead of asking it to lay out what the engagement actually requires versus what's being offered. A direct take-it-or-leave-it answer sounds confident regardless of whether it has the full picture of your calendar, your specialization, or what you're actually trying to build toward this year specifically, none of which it can see unless you say so.
Does this apply to a fractional executive the same way as an independent consultant?
Yes, with one difference worth naming. A fractional executive typically holds a title and ongoing authority inside the client's organization, while a consultant is usually brought in for a defined engagement, so the trust-building and scope-setting prompts below apply to both, but the fractional executive's version usually needs a clearer boundary on decision rights, not just deliverables and hours, since authority without a stated boundary tends to drift too.
Can these prompts replace an actual conversation with the client about scope?
No, and they're not meant to. They're built to sharpen what you bring into that conversation, a clearer sense of what's actually in scope, what the engagement is worth, and where trust might already be thinning, not to replace the actual conversation where the client hears your read and responds to it directly, which no prompt can do on your behalf.
What's the honest limit of using AI for consulting decisions?
It has no access to the client's actual budget ceiling, their internal politics, or what they've already tried and rejected before hiring you in the first place. Use it to structure your own reasoning about scope, value, and trust; the judgment about this specific client and this specific engagement still has to be yours, built on what you know that it doesn't.
Written by Gareth Hoyle. Last updated 26 September 2026. Part of the authority.md guides library.
More guides.
Bringing AI Into a Creative Project Without Ruining It
What generic AI brainstorming actually gives a creative project and what it quietly flattens, four prompts that help today without taking over, and what changes when the AI applies Rick Rubin's documented listening practice instead of generic idea generation.
AI for Hiring Decisions: Where Claude and ChatGPT Actually Help
A grounded look at what generic AI use gets right and wrong when you're deciding on a hire, four prompts that genuinely sharpen the decision, and what changes when the AI applies a documented evidence-based hiring framework instead of generic interview advice.
Using AI to Prep for a Negotiation: What Actually Works
Generic AI negotiation advice is genuinely useful and genuinely limited. Here's what Claude and ChatGPT get right before a negotiation, four prompts that work today, and what changes once the AI has a documented framework instead of a generic one.