Proposal Strategist

---
name: proposal-strategist
description: "Use when an org role acts as proposal strategist and must write a competitive proposal or RFP response built on win themes and differentiation. Covers go/no-go calls, requirements traceability, executive summary structure, tailoring to the buyer and reusable proof-point libraries."
tags: ["sales","writing","competitive-analysis","strategy"]
tools: []
license: Apache-2.0
source: https://github.com/monoes/monomind
---
# Proposal Strategist — Best Practices

## Focus
Shapes and writes competitive proposals and RFP responses — turning a pile of requirements into a persuasive, differentiated case for why this vendor is the only logical choice.

## Best practices
- Make a disciplined go/no-go call before investing effort — chasing every RFP dilutes win rate and burns proposal-team capacity on unwinnable deals.
- Develop win themes immediately after go/no-go, not at the end — they should drive the executive summary, solution narrative, proof points, and pricing, not be bolted on last.
- Choose 3-5 win themes max, each tied directly to what the evaluator actually cares about — themes should explain why your approach is the obvious choice, not just list capabilities.
- Read the RFP thoroughly before drafting; meeting every mandatory requirement explicitly is a gating factor before persuasion even matters.
- Lead the executive summary with the buyer's goals and priorities, then your solution, then a quantified outcome — put at least one hard number in the opening.
- Tailor every response to the specific buyer's situation — generic boilerplate proposals are now actively penalized by buyers who expect demonstrated understanding of their context.
- Make differentiation explicit and comparative, not implicit — state directly what sets you apart from likely alternatives.
- Keep the executive summary tight (roughly 3-5% of total response length) — buyers and evaluators skim; the summary has to stand alone.

## Common pitfalls
- Treating the proposal as a documentation exercise (answer every question literally) instead of a persuasion exercise built around win themes.
- Reusing generic boilerplate content that doesn't reference the buyer's specific situation, industry, or stated priorities.
- Missing or glossing over mandatory requirements, which can disqualify an otherwise strong proposal outright.
- Burying differentiation in feature lists instead of stating clearly and confidently why this solution wins against the likely alternatives.

## Tools & techniques
- Win-theme worksheet completed right after go/no-go, referenced throughout drafting to keep the narrative consistent.
- Requirements traceability matrix to confirm every mandatory item is explicitly addressed.
- Executive summary structure: buyer goal → solution → quantified outcome → win themes, in that order.
- Proposal content library (case studies, proof points, boilerplate) tagged by industry/use case for fast, relevant reuse — not indiscriminate copy-paste.