25 AI Prompts for Writing Proposals That Win

TL;DR: The AI prompts that win RFP-style proposals extract before they draft: pull every requirement into a compliance matrix, weight sections against the evaluation criteria, then build the executive summary, methodology, pricing narrative, and risk register from that scaffold. This pack has 25 of them, ending with a reviewer prompt that scores your draft the way an evaluator will.

What are the best AI prompts for writing proposals that win?

The best proposal prompts do not open with "write me a proposal." They open with extraction: pulling the RFP's actual requirements, evaluation weights, and constraints out of the document before any prose gets drafted. From there, the work moves through eight stages that mirror how a formal proposal actually gets scored, not how a blog post imagines it gets written.

If you need a fast, well-structured proposal for a normal client pitch, our free client proposal prompt generator is the faster path: one form, one draft, done in a couple of minutes. This pack is for the other kind of proposal, the one going to a formal RFP, a procurement committee, or a client sophisticated enough to score submissions against a published rubric. There, compliance decides more of the outcome than prose quality does. A beautifully written proposal that misses a mandatory requirement scores zero on that line item regardless of how well the rest reads.

The eight stages below, in order: qualifying whether to bid at all, extracting requirements into a compliance matrix, the executive summary, approach and methodology, team and past-performance framing, the pricing narrative, the risk register, and a final review pass. Each stage gets a working prompt template with bracketed placeholders you swap for your own project details. If you write smaller, faster proposals for individual clients rather than formal bids, the broader 40 AI prompts for freelancers covers outreach and general client work more directly than this pack does.

Most formal RFPs score submissions against a published rubric: technical approach, management approach, past performance, and price, each carrying a stated weight the evaluator is required to apply. A proposal that reads well but skips a scored line item loses points nobody can hand back later, regardless of how the rest of the document performs. That is the practical meaning behind "compliance decides the outcome": not a figure of speech, an actual line on an actual scoresheet, filled in by someone whose job is to check your document against a checklist, not to admire your prose.

How do you decide whether to bid at all?

Qualify before you draft. A bid/no-bid pass run against the RFP's actual scope, before a single section gets written, is cheaper than discovering the mismatch after two days of writing.

Prompt 1: Bid/No-Bid Scorecard

Act as a business development advisor reviewing a bid decision. Here is the
RFP summary: [PASTE RFP SUMMARY OR SCOPE SECTION].

Our capabilities: [LIST RELEVANT EXPERIENCE, TEAM SIZE, PAST PROJECTS].
Our current capacity: [AVAILABLE HOURS/TEAM BANDWIDTH OVER THE PROJECT PERIOD].
Our target margin: [MINIMUM ACCEPTABLE MARGIN OR RATE].

Score this opportunity from 1-5 on: strategic fit, our capability match,
capacity to deliver on the stated timeline, and price competitiveness given
our margin target. For each score, state the specific evidence from the RFP
or our profile that produced it. End with a one-line bid/no-bid recommendation.

Prompt 2: Capability Gap Check

Compare this RFP's stated requirements against our team's actual capabilities:
[RFP REQUIREMENTS LIST]
[OUR TEAM'S SKILLS, CERTIFICATIONS, AND PAST PROJECT TYPES]

List every requirement we cannot currently meet without a subcontractor or new
hire. For each gap, suggest whether it is closeable before submission (and how)
or whether it should factor into the bid/no-bid decision.

Prompt 3: Competitive Position Check

Given this RFP: [RFP SUMMARY], and what we know about likely competitors for
this type of contract: [LIST KNOWN OR LIKELY COMPETITORS, IF ANY], assess where
we are genuinely differentiated versus where we are likely competing on price
alone. Be honest about categories where we have no real edge.

Run all three before you write anything. Prompt 1 produces a number; prompts 2 and 3 explain it. A high fit score sitting on top of a real capability gap is a different decision than a high fit score backed by a genuine edge, and only the narrative under each score tells you which one you are actually looking at.

How do you turn a messy RFP into a compliance matrix?

Extract requirements before you write. A compliance matrix is a table that maps every mandatory requirement in the RFP to where your proposal answers it, and it is often the first thing an evaluator checks.

Prompt 4: Requirement Extraction

Read the following RFP text and extract every requirement stated with
"shall," "must," "will," or an equivalent mandatory word. Output a numbered
list. For each requirement, include the exact quoted text and its section
number in the source document.

RFP TEXT: [PASTE FULL RFP OR RELEVANT SECTIONS]

Prompt 5: Build the Compliance Matrix

Using this requirements list: [PASTE OUTPUT FROM PROMPT 4], generate a table
with four columns: Requirement, RFP Section, Our Response Location (leave
blank for me to fill in), and Compliance Status (Compliant / Partial /
Open). Group requirements by proposal section (e.g., Technical Approach,
Management Plan, Past Performance) so I know which section each belongs to.

That prompt produces something close to this shape:

Re-run Prompt 5 after every major revision, not just once at the start. A compliance matrix built from the first draft and never updated will still say "Compliant" next to a section that got cut in edit three. When an evaluator scores against their own copy of the requirements, they are checking your document against their checklist, not against what you meant to include.

Prompt 6: Ambiguity and Conflict Flagging

Review this RFP text for requirements that are ambiguous, contradict each
other, or reference an attachment that was not provided: [PASTE RFP TEXT].
List each issue and draft a short, professional question for the buyer's
Q&A period that would resolve it without revealing a weakness in our approach.

Prompt 7: Evaluation-Criteria Weighting

Here are the RFP's stated evaluation criteria and their weights:
[PASTE EVALUATION CRITERIA SECTION, e.g. "Technical Approach 40%, Past
Performance 25%, Price 25%, Management Plan 10%"].

Recommend how much space (as a rough percentage of total page count) each
proposal section should get based on these weights. Flag any mismatch between
a heavily weighted criterion and a section we tend to under-write.

This step catches a mistake that is easy to make under deadline pressure: three pages on a technical approach the RFP weights at 20%, and a single paragraph for past performance worth 30%. Page count should follow the rubric, not habit.

Prompt 8: Submission Checklist

From this RFP's instructions section: [PASTE INSTRUCTIONS/SUBMISSION SECTION],
generate a submission checklist covering format (font, margins, page limit),
required forms and signatures, number of copies or file format, submission
method, and the exact deadline including time zone. Flag anything that would
cause automatic disqualification if missed.

How do you write an executive summary that gets read?

Lead with the buyer's problem, not your company. An evaluator reading dozens of submissions decides in the first paragraph whether yours understood the assignment.

Prompt 9: Draft the Executive Summary

Draft an executive summary for our proposal in response to this RFP:
[RFP SUMMARY]. Open with the buyer's stated problem or goal in their own
words, not with our company background. Then state our win themes:
[LIST 2-4 KEY DIFFERENTIATORS OR REASONS WE'RE THE RIGHT CHOICE]. Keep it
to [PAGE OR WORD LIMIT] and end with a single clear statement of what we
are proposing to deliver.

Evaluators reading a stack of submissions decide fast which pile a proposal lands in. A summary that opens with the buyer's own stated goal, in language recognizable from the RFP itself, reads as attentive. One that opens with "Founded in [year], our company has served clients since..." reads as a form letter with the client's name swapped in. Save the company history for the section that actually asks for it.

Prompt 10: Mirror the RFP's Own Language

Here is our draft executive summary: [PASTE DRAFT]. Here is the RFP's
language for describing the project's goals and evaluation focus:
[PASTE RELEVANT RFP LANGUAGE]. Rewrite the summary so it echoes the buyer's
own terminology and priorities back to them, without changing what we
actually said we would deliver.

Prompt 11: Tighten to a Strict Limit

Cut this executive summary to exactly [WORD OR PAGE LIMIT] while keeping
every win theme intact: [PASTE DRAFT]. Prioritize cutting explanation and
qualifiers before cutting any stated differentiator or the opening problem
statement.

How do you write the approach and methodology section?

Translate your delivery plan into the buyer's terms. This section usually carries the heaviest evaluation weight, and it is the one most likely to read as generic if you skip the RFP's own vocabulary.

Prompt 12: Turn a Rough Plan into a Methodology Section

Here is our internal delivery plan in rough notes: [PASTE NOTES OR BULLET
LIST OF PHASES/TASKS]. Turn this into a formal methodology section with
named phases, a one-paragraph description of each phase, and the specific
deliverable produced at the end of each one. Match the terminology this RFP
uses for phases or milestones: [PASTE RFP TERMINOLOGY IF STATED].

The fastest way to make a methodology section sound generic is to describe your standard process in your own vocabulary and hope it lines up with what the buyer asked for. The fix is mechanical: pull the phase names, deliverable terms, and milestone language directly from the RFP's own scope section, and feed them into the prompt as constraints, not background color.

Prompt 13: Milestone and Timeline Narrative

Given these project phases and durations: [LIST PHASES WITH ESTIMATED
DURATIONS], write a timeline narrative paragraph plus a simple milestone
table (Milestone, Target Date, Deliverable) that a non-technical evaluator
can follow without a project management background.

Prompt 14: Assumptions and Dependencies

List the assumptions and client-side dependencies this proposal relies on,
based on this scope: [PASTE SCOPE OR APPROACH SECTION]. Write each as a
single clear sentence (e.g., "We assume the client will provide API access
within 5 business days of contract signature"). Flag any assumption that,
if wrong, would materially change the timeline or price.

Prompt 15: Quality Assurance Paragraph

Write a short paragraph describing our quality assurance approach for this
project: [DESCRIBE YOUR REVIEW/TESTING/CHECK-IN PROCESS IN PLAIN NOTES].
Make it specific to this engagement rather than a generic "we value quality"
statement, and tie at least one QA step to a deliverable named earlier in
the proposal.

Prompt 16: Address a Stated Technical Constraint

The RFP states this constraint: [PASTE SPECIFIC TECHNICAL, REGULATORY, OR
OPERATIONAL CONSTRAINT]. Write a short paragraph for our approach section
explaining specifically how our methodology accounts for this constraint,
not just that we are "aware" of it.

How do you frame team and past performance without sounding like a brag sheet?

Match your team's bios and case studies to what the RFP actually asked to see, not to a generic resume. Past-performance sections score higher when the relevance is explicit rather than implied.

Prompt 17: Client-Facing Team Bio

Turn this internal resume/bio into a client-facing team bio for a proposal:
[PASTE RESUME OR ROUGH BIO NOTES]. Emphasize the experience most relevant
to this project: [PROJECT TYPE/REQUIREMENTS]. Keep it to 3-4 sentences,
third person, and cut credentials that are true but irrelevant to this bid.

Prompt 18: Past-Performance Case Study

Turn this past project into a proposal case study: [DESCRIBE THE PAST
PROJECT: CLIENT TYPE, PROBLEM, WHAT WE DID, OUTCOME]. Structure it as
Situation, Action, Result in 100-150 words, and explicitly connect the
result to the capability this RFP is asking us to demonstrate:
[RELEVANT RFP REQUIREMENT OR EVALUATION CRITERION].

Prompt 19: References Section

Draft a references section listing these past clients: [LIST NAMES,
PROJECT TYPE, CONTACT INFO IF SHARABLE]. For each, add a one-sentence note
on the project's relevance to this RFP's scope, so an evaluator does not
have to make that connection themselves.

Choose case studies by relevance to the stated evaluation criteria, not by which project you are proudest of. A mid-sized project that matches this RFP's scope and sector will usually outscore a flagship project in an unrelated industry, because the evaluator is checking for evidence you can do this specific work, not evidence you can do impressive work in general.

How do you write a pricing narrative that justifies the number?

Explain the price; do not just state it. A pricing table with no accompanying narrative leaves the evaluator to guess why the number is what it is, and that guess rarely favors the vendor.

Prompt 20: Pricing Narrative

We are proposing a price of [PRICE/RATE STRUCTURE] for this project. The
scope includes: [LIST DELIVERABLES]. Write a pricing narrative paragraph
that explains what is included, connects the investment to the value or
outcome the client gets, and states our payment terms: [TERMS, E.G.
30% UPFRONT, NET 30].

The most common pricing mistake in a formal proposal is presenting a number with no accompanying reasoning, then hoping the technical section upstream does the persuading on its behalf. An evaluator scoring price as its own criterion is reading the pricing section on its own terms. If it does not explain itself, it reads as a number picked to win the bid, not a number that reflects the actual work.

Prompt 21: Scope Boundaries and Exclusions

Based on this scope: [PASTE SCOPE], list what is explicitly excluded from
this price (e.g., revisions beyond round 2, third-party licensing costs,
travel). Write these as a short, clearly labeled "Out of Scope" list so
there is no ambiguity if the client asks for more later.

Prompt 22: Handling the Price Objection

This RFP's evaluation criteria weight price at [X%]. Our price may not be
the lowest bid. Write a short paragraph, without directly mentioning
competitors, that explains why our price reflects the value and risk
reduction described in the rest of this proposal, aimed at an evaluator who
weighs price alongside quality.

How do you build a risk register that reads as competence, not liability?

Name the top risks before the client does. A short, specific risk register signals that you have actually thought about how the project could go wrong, which reads as more trustworthy than a proposal that pretends nothing could.

Prompt 23: Generate the Risk Register

Based on this approach and scope: [PASTE APPROACH/SCOPE SECTION], identify
the top 3-5 risks to project success. For each, output a table row with:
Risk, Likelihood (Low/Medium/High), Impact (Low/Medium/High), and Mitigation
Approach. Keep mitigations specific and actionable, not generic reassurance.

Prompt 24: Risk Narrative for the Proposal Body

Turn this risk register into a short narrative paragraph for the proposal
body (not a table): [PASTE RISK REGISTER]. Frame it as evidence of planning
rather than a list of things that could go wrong. Lead with the highest-
impact risk and how it is mitigated.

Keep the risk section proportionate to what the RFP actually asks for. A one-paragraph risk narrative satisfies a proposal where risk is a minor scored item; a full register with likelihood and impact ratings suits an RFP that names risk management as its own evaluation criterion. Match the effort to the weight, the same rule that governs every other section in this pack.

How do you do the final review pass before you submit?

Read your own draft the way an evaluator will: against their stated criteria, not against your sense of good writing. This is the step most proposals skip, and it is the one that catches the gaps that actually lose points.

Prompt 25: Evaluator Simulation Review

Act as an evaluator scoring proposals against this RFP's stated evaluation
criteria: [PASTE EVALUATION CRITERIA]. Here is our draft proposal:
[PASTE FULL DRAFT OR SECTION-BY-SECTION SUMMARY]. Score each criterion 1-5
and explain, for any score below 4, exactly what is missing or unclear that
would cost us points. Then list any RFP requirement from our compliance
matrix that this draft does not clearly address.

Run the evaluator-simulation prompt once for whichever criterion carries the most weight, then again for price alone, then again for compliance alone. A single generalist pass tends to average the feedback out; three narrower passes surface the specific gap that a broad review misses.

Run Prompt 25 against every major revision, not just the final draft. Treat this stack the way you would treat code you intend to reuse across bids: worth versioning, since the wording that actually correlates with wins is worth keeping track of. Our post on prompt discipline for developers, Prompt Versioning: Treat Your Prompts Like Code, covers the same idea applied to a codebase instead of a bid file.

Winning the bid is not the finish line. The same discipline that got the proposal through evaluation, specific scope, clear deliverables, defined pricing, carries straight into the paperwork that follows signature. If your next step is turning an accepted proposal into a scope document, kickoff email, and invoice, our Proposal-to-Invoice Prompt Templates picks up exactly where this pack leaves off. The prompts differ, but the habit is the same one this whole pack has been building: extract what the other side actually asked for, then write to that, not to a template that only vaguely resembles it.