Proposal and RFP Writer

A proposal is not a document; it is an argument with a price on the last page. In an RFP, it is an argument delivered under compliance rules that disqualify the careless before anyone reads a word. This skill turns discovery notes or an RFP packet into a response that is compliant line by line, skimmable by an executive in four minutes, and structured so the evaluators' scoresheet practically fills itself in.

When to use this skill

• Responding to a formal RFP, RFI, or tender with stated requirements and a deadline
• Writing a proactive proposal after discovery calls with a warm prospect
• A past bid lost with the debrief "they did not address our requirements" — the process failure this workflow exists to prevent
• Standardizing a proposal skeleton the team can reuse without cloning stale boilerplate

Workflow

1. For RFPs, build the compliance matrix before writing anything. One row per stated requirement, numbered from their document: the requirement verbatim, your status (comply, partial, alternative), and where in your response it is addressed. Unanswered rows are how strong vendors lose to complete ones.
2. Extract the evaluation reality. Who scores this, against which criteria, at what weights? If the RFP states weights, allocate your page count in the same proportions. In a proactive proposal the criteria are the buyer's stated problems from discovery — quoted in their words.
3. Write the body answer-first. Every section opens with the direct answer in its first sentence, then evidence, then detail. Evaluators skim vertically, so reward the skim: headings phrased as their questions, one idea per paragraph, a table wherever prose would hide a comparison.
4. Order the narrative sections deliberately: their situation (proof you listened), the proposed approach in phases, outcomes and how they will be measured, team and relevant evidence (only proof that maps to this scope), plan and timeline, pricing, terms.
5. Handle competitors without naming them. Where you know the likely alternative's weakness, plant the evaluation question that exposes it — "ask any vendor to show migration without downtime" — never disparage, always arm the evaluator.
6. Write the executive summary last and place it first. One page: their problem in their words, your approach in three bullets, the expected outcome with a number, why you, and the price headline if permitted. It must stand alone; assume half the committee reads nothing else.
7. Run the two proofs before submission. Compliance proof: every matrix row resolved and cross-referenced. Cold-read proof: someone who has not seen the deal reads only headings, first sentences, and the summary — if they cannot reconstruct the offer, restructure before polishing.

Output format

Deliver four artifacts: the compliance matrix (for RFPs); the one-page executive summary; the full response in the section order above; and a pricing page readable standing alone — options labeled, assumptions stated, validity period explicit, no surprises undisclosed in the body.

Quality bar

• Zero requirements left unaddressed; partial and alternative answers say so plainly with reasons
• The buyer's vocabulary appears throughout; your internal jargon appears nowhere
• Every capability claim is paired with evidence — an example, a metric, a named artifact
• No paragraph survives that a competitor could paste into their own proposal unchanged
• Deadlines and format rules from the RFP are treated as hard gates, because they are

Failure modes to check on the final pass

The three that lose otherwise-winnable bids: an executive summary that describes your company instead of their outcome; pricing that introduces items the body never mentioned, reading as ambush; and boilerplate case studies whose scale or industry contradicts the specifics claimed two pages earlier. Any one of these costs more points than a typo ever will.