Artificial Idea | AI careers · practical prompts · no hype Thursday, January 15, 2026 · Issue #48 · Prompt Tutorial
The proposal stack
The client proposal prompt: how consultants are closing deals faster with AI
Most proposals fail not because the solution is wrong but because the argument for it is weak. These five prompts build the argument before you write the proposal.
Monday's issue identified six conditions that determine how quickly accumulated AI capability becomes visible to the market. The fifth of those conditions was professional network visibility. The sixth was the ability to teach. Both require one thing before they are possible: you need to have produced work that is worth showing and worth explaining.
For the professionals in consulting, business development, legal services, financial advisory, and every other function where the proposal is the primary mechanism by which work is won, that work starts with the proposal itself. The proposal is where the combination of domain expertise and AI fluency described in Issue #47 either becomes visible to clients and decision-makers or does not. A professional whose AI-augmented analytical work is genuinely better but whose proposals still follow the same generic structure they used three years ago is failing the fifth and sixth conditions at the moment that matters most.
This is the prompt stack that closes that gap.
The foundational principle
Before the prompts, the principle that underlies all of them is worth stating directly because it changes how each one is used.
A proposal is not a document about you. It is a document about the person receiving it. Specifically, it is a document that demonstrates, in the sequence and language most likely to be persuasive to that specific person, that you understand their problem better than they expected you to, that your solution addresses the specific aspects of that problem they most care about, and that the risk of choosing you is lower than the risk of not choosing you or choosing someone else.
Every prompt below is designed to force that perspective rather than the default one, which is the perspective of the person who has built the solution and wants to explain it. The default perspective produces proposals that are technically competent and persuasively inert. The perspective these prompts enforce produces proposals that move decisions.
Prompt 1: The problem reframer
The problem it solves: ensuring that the problem your proposal addresses is framed in the language and at the level of specificity that the decision-maker experiences it, rather than in the language of the solution you have already built.
Most proposals start from the solution and work backward to a problem description that justifies it. The problem description that results is accurate but not resonant, because it describes the problem as the solution-provider understands it rather than as the decision-maker lives it. Decision-makers do not buy solutions to problems they do not recognise as their own.
You are a senior consultant helping me reframe
the problem my proposal addresses from the
perspective of the decision-maker rather than
the solution-provider.
My solution and what it does: [describe]
The decision-maker I am writing for:
[their role, their organisation, their current
situation, what they have said about their
priorities, and what you know about the pressures
they are under right now]
The problem as I currently frame it:
[describe how you currently introduce
the problem in your proposals]
Please:
1. Reframe the problem from the decision-maker's
perspective: what are they experiencing,
what is it costing them, and what have they
already tried that has not worked
2. Identify the language they are most likely
to use when describing this problem to their
own colleagues, as opposed to the language
I use when describing it to potential clients
3. Identify the aspect of the problem they
care most about that my current framing
underweights or omits entirely
4. Write a two-paragraph problem statement
that would make this decision-maker feel
understood before they reach the section
where I describe my solution
The test for this problem statement is simple:
would the decision-maker read it and think
"this person understands what I am dealing with"
rather than "this person wants to sell me something."
The test at the end is not rhetorical. It is the actual standard the problem statement needs to meet. A decision-maker who reaches the solution section already feeling understood is in a fundamentally different evaluative state than one who reaches it still waiting to be convinced that the proposal writer understands their situation. The former evaluates the solution. The latter evaluates the proposal writer.
Prompt 2: The value architecture builder
The problem it solves: constructing the specific value argument for your solution in the terms the decision-maker uses to evaluate decisions, rather than in the terms that feel most natural to the person who built the solution.
Value arguments fail when they describe features rather than outcomes, when they use generic benefit language that could apply to any solution in the category, or when the outcomes described are not the ones the decision-maker is held accountable for producing.
You are a value proposition specialist helping
me build the specific value argument for
a proposal I am writing.
My solution: [describe what it is and what it does]
The decision-maker: [role, organisation,
what they are measured on, what success
looks like for them personally in their role]
The context: [what is driving this decision now,
what alternatives they are considering,
and what the cost of doing nothing is]
Please build a value architecture covering:
1. The primary value driver: the single most
important outcome my solution produces
for this decision-maker, stated in the
metric they care about most, not the
metric that makes my solution look best
2. The secondary value drivers: two or three
additional outcomes that strengthen the
case without diluting the primary argument
3. The risk reduction argument: what risk
my solution reduces or eliminates that
the decision-maker is currently carrying
4. The cost of inaction: what continuing
without this solution costs over the
decision-maker's relevant time horizon,
stated specifically enough to be felt
rather than acknowledged
5. The differentiation argument: why this
specific solution rather than the
alternatives the decision-maker is
likely considering, stated in terms
of the outcomes that differ rather
than the features that differ
For each element, flag where I have not
given you enough specific information
to make the argument credible rather
than generic.
The instruction to flag where information is insufficient is the constraint that makes this prompt produce useful diagnostic output as well as persuasive content. A value argument that cannot be made specifically from the information available is a signal that the proposal writer does not yet know enough about the decision-maker's context to write a proposal worth sending.
Prompt 3: The objection anticipator
The problem it solves: identifying the reservations the decision-maker will have about your proposal before they raise them, and building responses into the proposal rather than waiting to address them in a follow-up conversation that may never happen.
Most proposals are written as if the decision-maker will read them in a state of open-minded receptiveness. Most decision-makers read proposals in a state of active skepticism, looking for the reasons not to proceed rather than the reasons to do so.
You are helping me anticipate and address
the objections my proposal is most likely
to encounter before they are raised.
My proposal summary: [describe the solution,
the value argument, and the ask]
The decision-maker: [their role, their known
concerns, their previous experience with
similar proposals or solutions, and anything
you know about what has made them skeptical
of similar proposals in the past]
The organisational context: [any internal
politics, budget constraints, competing
priorities, or stakeholder dynamics likely
to affect how this proposal is evaluated]
Please:
1. Identify the five most likely objections
to this proposal, in order of the
probability that they will be raised
or felt even if not voiced
2. For each objection, assess whether it
is best addressed proactively in the
proposal body, acknowledged briefly
in passing, or reserved for a
conversation after the proposal is read
3. For the two objections most likely to
kill the proposal if not addressed,
draft a specific response that is
honest rather than dismissive
4. Identify any objection that reveals
a genuine weakness in my proposal
that needs to be resolved before
the proposal is sent rather than
addressed rhetorically within it
Do not suggest I dismiss or minimise
legitimate concerns. An objection that
reflects a real weakness in the proposal
is information, not an obstacle to manage.
Point four is the output most worth attending to. The proposal writing process has a natural tendency toward advocacy that can make genuine weaknesses invisible until the rejection arrives. This prompt is designed to surface those weaknesses when there is still time to address them.
Prompt 4: The structure optimiser
The problem it solves: organising the content of a proposal in the sequence most likely to be persuasive to a specific decision-maker, rather than in the sequence most natural to the person who built the solution.
The default proposal structure, problem, solution, credentials, price, is calibrated to no one in particular, which means it is suboptimal for everyone in particular.
You are a proposal structure specialist
helping me organise the content of a proposal
in the sequence most persuasive to a
specific decision-maker.
The content I have developed:
[summarise the problem framing, value argument,
objection responses, and any other content
you have prepared]
The decision-maker: [their role, their prior
familiarity with the solution category,
their known evaluation criteria, and their
typical decision-making style if known]
The decision context: [is this a competitive
tender, an invited proposal, a follow-up to
a conversation, or an unsolicited approach]
Please:
1. Recommend a specific structure for this
proposal, section by section, with a
rationale for why each section appears
where it does rather than in the default order
2. Identify the single most important section
in this proposal and where in the sequence
it should appear to have maximum effect
3. Identify any content that should not be
in the main proposal body but belongs
in an appendix, a follow-up conversation,
or a separate document
4. Recommend the appropriate length for this
proposal given the decision-maker and context
5. Identify the opening sentence of the proposal:
the single sentence that should be the first
thing the decision-maker reads, calibrated
to create the reading state most conducive
to the rest of the proposal landing well
A structure recommendation that could apply
to any proposal is not useful.
Point five, the opening sentence calibrated to create the right reading state, is the structural detail most proposals get wrong and the one with the highest leverage per word. The first sentence determines whether the decision-maker reads the proposal as someone evaluating a solution or as someone being sold to.
Prompt 5: The close builder
The problem it solves: writing the close of a proposal in a way that makes the next step clear, low-friction, and calibrated to the decision-maker's likely state after reading, rather than ending with a generic invitation to get in touch.
Most proposals end weakly. They describe everything the solution will do, build a reasonable value case, and then close with a sentence that essentially asks the decision-maker to decide what happens next.
You are helping me write the close of a proposal
that creates clear next steps without applying
pressure that makes the decision-maker
pull back.
My proposal summary: [brief description]
The decision-maker's likely state after reading:
[what questions will they still have, what will
they need to discuss internally, and what is
the most likely reason they would delay
rather than move forward]
The next step I want them to take:
[be specific: a meeting, a call, a trial,
a signature, something else]
Please:
1. Write a closing section of 150 to 200 words
that summarises the core value argument
in two sentences, proposes a specific
next step, and makes that next step as
easy as possible to take
2. Identify the one concern the decision-maker
is most likely to be holding after reading
the proposal and address it in the close
without making it the focus of the close
3. Write a subject line for the email
accompanying the proposal that creates
enough interest to ensure the attachment
is opened without overpromising what
is inside
4. Write a two-sentence follow-up message
to send if you have not heard back in
five working days, that is confident
without being pushy and that adds
one piece of value rather than just
asking for an update
The close should feel like the natural end
of a persuasive argument, not like the
beginning of a negotiation.
The connection back to Monday
Issue #47 identified the ability to produce and articulate high-quality work as the foundation of professional visibility in 2026. The proposal is where that ability is most directly tested and most directly rewarded.
The six conditions from Monday map onto the proposal in a specific way. Domain depth determines whether the problem framing is credible. The named application determines whether the value argument is specific. Documented output quality improvement is what goes into the credentials section. The senior advocate is the reference who makes the proposal's claims verifiable. Professional network visibility is what makes the decision-maker already familiar with your name before they open the document. The ability to teach is what makes the solution explanation clear enough to close rather than confuse.
A proposal written after running these five prompts is built on a foundation that reflects all six conditions. A proposal written without that foundation and then edited to sound better is still built on the wrong foundation.
The total time for the five prompts is approximately forty-five minutes for a proposal where you have done the client research. The McKinsey sales effectiveness research published in 2025 is consistent on the return: proposals written from a foundation of specific client understanding win at a rate 2.6 times higher than proposals written from a foundation of solution description.
Forty-five minutes. 2.6 times. The investment calculus is not complicated.
Monday we are looking at a theme that has been building quietly through the past several issues and that the January hiring data is now making explicit: the specific advantage that professionals who have been consistently reading this newsletter since August hold over those who are just beginning to engage with the AI transition in earnest. It is not the advantage most people would guess, and understanding it changes how the next ninety days should be used.
The advantage is real. Monday explains what it is and how to use it before it compresses.
— Team Artificial Idea
