Proposal development

Proposal Development

Run the full business development lifecycle for a consulting pursuit: assess the opportunity, articulate value, write the proposal, draft the SOW, build the pitch deck. This covers everything up to award. For deliverables produced during an engagement (steering committee decks, final reports), see client-deliverables.

A full pursuit flows through the five stages in order. Most users enter mid-stream. Identify which stage the request lands in, confirm the inputs that stage needs, then execute. Do not walk someone through opportunity scoring when they hand you a signed engagement and ask for a SOW.

One rule threads through all five stages: work from real inputs. Ask for the client's actual words, the actual RFP text, the firm's actual case results. When you need an illustrative number to show structure, label it as an example and flag it for validation. Never invent engagement experience, competitor intelligence, or dollar figures. Frame outcome claims conditionally ("organizations that consolidate vendors this way tend to cut spend 8-15%") unless the user supplies real firm data with a source.

Stage 1: Opportunity Assessment

Decide whether and how to respond before anyone burns hours on a draft. This stage is where pursuits are won or wasted, so give it real attention.

1a. Parse the opportunity

Read the source material (RFP, inbound request, conversation notes, or opportunity brief) and pull out:

• Client organization: who they are, their situation, why they are buying now
• Problem statement: the challenge they are actually trying to solve, which is often not the one the RFP names
• Scope: what they are asking for
• Deliverables: what must be produced
• Timeline: key dates, including the submission deadline
• Budget: if disclosed. If not, flag it as a risk and plan to size it yourself
• Evaluation criteria: how responses get scored
• Submission requirements: format, page limits, mandatory sections

For proactive pursuits with no RFP, work from what exists: client conversations, public filings, news, known pain points, the relationship history.

1b. Score the opportunity

Assess fit before investing. Fill each field with a real judgment, not a label:

## Opportunity Assessment
- Fit score: [High / Medium / Low] plus one sentence on why
- Estimated value: [range, with the basis for the estimate]
- Win probability: [directional estimate with rationale]
- Resource requirement: [High / Medium / Low] and what it displaces
- Strategic value: [does this open a new account, practice, or market?]

Win probability and value here are directional estimates. Say so. They sharpen once you know the competitive set and the buyer's real budget.

Go / No-Go signals. Answer each one honestly. A pursuit that fails two of these usually should not be chased.

• Do we have the right people and directly relevant experience, or are we hoping to learn on their dime?
• Is the timeline real, or does it force a rushed, generic response?
• Are there signs of a wired deal? Watch for oddly specific requirements, incumbent-favoring language, or criteria that read like someone's resume.
• Does the economics work at our rate card, or are we buying the logo?
• Is this strategically worth more than the fee (a beachhead account, a reference-able name, a new capability)?

1c. Analyze evaluation criteria

For RFPs with explicit criteria, break down what each one is really testing:

Criterion	Weight	What they actually want	Our strength
[Criterion]	X%	[Interpretation, 1-2 sentences]	[High/Med/Low]

Fill the interpretation cell with judgment, not a restatement of the criterion. "Relevant experience, 30%" really means "prove you have done this in our industry at our scale without a learning curve." Then answer three questions: What carries the most weight? What is differentiated versus table stakes? What are they scoring implicitly (culture fit, risk, chemistry) that never appears in the rubric?

Note whether weightings are stated or inferred. For informal pursuits, reconstruct the implicit criteria from the conversations you do have.

1d. Assess competitive position

Map the field:

• Likely bidders: who else fits this profile
• Our advantages: where we beat each named competitor, specifically
• Our vulnerabilities: where we are exposed and how we blunt it
• Gaps: what we must fix or subcontract to be credible

If multiple buyers sit on the panel, note where their priorities diverge (technical wants proof, commercial wants price certainty, the sponsor wants career-safe delivery). Do not fabricate competitor intelligence. If you do not know who is bidding, say so and reason from the client's profile.

1e. Identify win themes

Develop 3-5 win themes, each locked to something the client is actually evaluating. A theme is not a capability. It is a reason we win this deal. Give each one a "why," real evidence, and an explicit tie to a criterion:

### Theme: [Name]
- Why it wins: [Their stated priority] is their top concern, and this addresses it head-on
- Evidence: [A quantified case result or track record. Use real firm data or mark it as a placeholder to fill]
- Alignment: [Maps to evaluation criterion X, the one weighted Y%]

Win themes are the spine of the whole pursuit. They carry into the value proposition, the proposal narrative, and every slide. Get them right here and the rest gets easier.

Stage 2: Value Proposition

Articulate the differentiated value under the pursuit. This feeds the proposal, the deck, and every partner conversation.

2a. Define value drivers

Structure value against five questions. Answer each in the client's terms, not yours:

• What value do we create? Name the primary lever (cost reduction, revenue growth, risk mitigation, capability building) and quantify the impact. Use conditional framing until real numbers exist.
• Why does it matter to them? Connect the value to their stated priorities, not your service lines. Use their language. Speak to their biggest fear or ambition.
• Why should they believe us? Methodology with a track record, named outcomes, third-party validation.
• What makes us different? Differentiators only we can claim, and why a competitor cannot copy them quickly.
• How do we deliver and prove it? Delivery model, quantified results from comparable work, and how we de-risk it for them.

2b. Build the messaging hierarchy

Layer the message for different rooms.

Headline value proposition (one sentence): For [client] who [need], our [offering] delivers [primary benefit], unlike [alternative], because [differentiator].

Elevator pitch (30 seconds, 3-4 sentences a partner can say naturally): hook on their problem, state what we do differently, cite one compelling result, name the next step.

Stakeholder messages:

Audience	Focus	Proof that lands
C-suite	Enterprise value, competitive position, shareholder impact	Board-level metrics
Functional leaders	Capability lift, team effectiveness, operational gains	Operational KPIs
Practitioners	Methodology, tools, skills, day-to-day improvement	Working examples, peer references

Competitive positioning:

Dimension	Our position	Competitor A	Competitor B
[Dimension]	[Our stance, specific]	[Their stance]	[Their stance]

2c. Validate the messaging

Run the value proposition through four tests before committing. This is the highest-leverage 10 minutes in the stage.

• Clarity: Can someone repeat the benefit in 30 seconds? Is it one core idea, not five?
• Relevance: Does it hit their specific pain? Would the buyer actually care?
• Differentiation: Could a competitor make the identical claim? If yes, it is not a differentiator.
• Belief: Is it credible, with proof behind it?

When a test fails, the fix is specific:

• Clarity fails: cut jargon, collapse to one benefit.
• Relevance fails: you may be solving the wrong problem. Go back to their stated needs.
• Differentiation fails: dig into methodology, team, or IP and replace generic claims with things only we can say.
• Belief fails: add quantified case results, named references, or third-party validation.

Stage 3: Proposal Development

Write the proposal. Carry the win themes and value proposition forward. Do not restart the thinking.

3a. Confirm context

Gather or confirm four inputs. If any is missing, ask rather than assume:

1. Client background: industry, market position, recent moves, live challenges
2. Engagement scope: problem statement, target outcomes, boundaries, timeline
3. Decision process: who decides, on what timeline, against what criteria
4. Our positioning: win themes, value proposition, differentiation

3b. Structure

Lead with their world, not your logo:

1. Executive Summary
2. Understanding Your Challenges
3. Our Recommended Approach
4. What This Delivers
5. Why [Our Firm]
6. Team
7. Client References
8. Investment
9. Next Steps

For RFP responses, remap to the required format and section order, but keep this outcome-first flow inside each section.

3c. Develop each section

Executive Summary (1 page). Write it last, place it first. Assume it is the only page a decision-maker reads. Open with their outcome, not your firm:

[Client] seeks to [objective]. We propose [approach] that delivers [quantified outcome].

The Outcome You'll Achieve
- [Primary outcome with metric]
- [Secondary outcome with metric]

Why [Our Firm]
[Differentiator 1], [differentiator 2], [differentiator 3].

Our Approach
[Methodology] over [timeline], in [n] phases.

Investment
[Range or structure]

Next Steps
[One clear, low-friction action]

Understanding Your Challenges. Prove you know their situation. Reference their specific challenges, use their terminology, acknowledge their constraints. This section earns the right to propose. Skip it and everything after reads as a template.

Our Recommended Approach. Present the methodology as the answer to their challenge, phase by phase:

Phase 1: [Name], [Duration]
Objective: [What this phase achieves]
Key Activities: [Activities]
Deliverables: [Deliverables]

Phase 2: [Name], [Duration]
[...]

Critical Success Factors
- [Factor]

What This Delivers. Quantified outcomes, ROI, and impact tied to their stated priorities. Map each outcome back to a challenge they raised. Label any illustrative figure as an example to validate.

Why [Our Firm]. Specific beats generic every time. Industry depth with real numbers, methodology differentiators, case studies with quantified results. Cut anything a competitor could also say.

Team. Named members with their role on this engagement, 2-3 bullets of directly relevant experience each, and notable credentials. Add an org chart for larger teams.

Client References. Case studies as Challenge to Approach to Results (quantified). Pick cases that mirror this client's situation. Use real firm cases or clearly mark placeholders.

Investment. Present pricing cleanly:

Phase	Fee	Timing
Phase 1	$XX	[Date]
Total	$XX

State what is covered, what is excluded, and the key assumptions. Align payment to deliverable milestones.

Next Steps. One clear, low-friction action. Not a menu.

3d. Persuasion principles

Apply these throughout, in this priority order: compliance, responsiveness, persuasion, credibility.

• Lead every section with the outcome for them.
• Choose specificity over generality: client names, data, quantified results.
• Build credibility from evidence (measurable case impact), not from adjectives.
• Tie every section back to a stated objective. If a paragraph does not, cut it.

Stage 4: Statement of Work

Draft the SOW that formalizes scope, deliverables, timeline, governance, and commercial terms. The SOW protects both sides. Vague SOWs breed scope creep and disputes, so precision here is the whole point.

4a. Define project context

Confirm:

• Background: business context, rationale, strategic weight
• Objectives: what success looks like, secondary objectives, success metrics
• Scope: what is in, what is explicitly out, and the assumptions behind both

4b. Structure

1. Engagement Overview
2. Objectives & Success Criteria
3. Scope of Work
4. Approach & Methodology
5. Deliverables
6. Timeline & Milestones
7. Team & Roles
8. Governance
9. Assumptions & Dependencies
10. Commercial Terms
11. Acceptance Criteria

4c. The sections that prevent disputes

Three sections do the protective work. Draft them carefully.

Scope of Work, in and out. Be exhaustive. The out-of-scope list stops more arguments than the in-scope list, because disputes come from what the client assumed was included.

In Scope
- [Activity or deliverable]

Out of Scope, Explicitly Excluded
- [Activity the client might assume is included]

Assumptions
- [Assumption about client resources, access, or decisions]

Dependencies
- [Client action required]
- [Third-party action required]

Deliverables. Specify each one precisely:

Deliverable	Description	Format	Timing
D1.1	[Name and what it contains]	[Format]	[When]

Acceptance Criteria. Define what "done" means for each deliverable, plus the review period (X business days), the process (deliver, review, accept or return with feedback, revise), the grounds for rejection (fails stated criteria, material scope deviation, factual errors), and deemed acceptance if no feedback arrives inside the review window. Ambiguity here is where fees get held.

Success Criteria (measurable, not aspirational):

#	Criterion	Measurement	Target
1	[Criterion]	[How measured]	[Target]

Governance. Match the structure to the engagement's size and the client's org. Do not bolt a steering committee onto a six-week project.

Forum	Frequency	Attendees	Purpose
Steering Committee	[Bi-weekly/Monthly]	[C-suite], Partner	Strategic decisions
Working Sessions	[Weekly]	Team leads	Work progress
Status Reviews	[Bi-weekly]	Manager, Client lead	Status, issues

Add escalation paths by issue type (technical, commercial, strategic) and state decision rights.

Commercial Terms. Fee structure (fixed, T&M, or blended), a payment schedule tied to milestones, expense policy, and change control. Payments example below is illustrative, adjust to the deal:

Milestone	Payment	Timing
Contract signature	20%	[Date]
Milestone 2 complete	30%	[Date]
Milestone 4 complete	30%	[Date]
Final delivery	20%	[Date]

Team & Roles. Both sides. Consulting team with role, name, level, and commitment percentage. Client team with role and responsibilities. Client obligations are load-bearing: engagements fail when client duties (data access, decisions, SME time) go unstated.

4d. Change control

Include a scope-change process. Any change to scope, timeline, or cost requires: a written change request, an impact assessment (scope, timeline, cost), approval from named decision-makers on both sides, and a signed SOW amendment.

Stage 5: Pitch Deck

Build the deck for the oral. It complements the written proposal and carries the room. Standard structure is 15-20 slides, adjusted to the slot: a 30-minute meeting with discussion wants 10-12 slides, a full capabilities session may run 25 or more.

Core arc: Opening, then The Challenge (build tension), then Our Solution (resolve it), then Results & Credentials (build belief), then The Deal (make it concrete), then Close. For the full slide-by-slide template, the storytelling rules, and the slide-development guidance, load references/pitch-deck.md.

Two principles override everything on a deck: one message per slide, and answer first (lead each slide with the recommendation, support with the analysis). If a slide does not advance the argument, cut it.

Response Strategy Framework

For an RFP response, layer the strategy in tiers and build in that order:

Tier 1, Compliance and Responsiveness. Every must-pass requirement, then every scored requirement addressed well. Fail a must-pass and the rest does not matter.

Tier 2, Strength-Based Win Themes. Primary themes aligned to the highest-weighted criteria, plus the differentiators that separate us from named competitors.

Tier 3, Persuasion and Evidence. Quantified case studies and methodology credentials.

Tier 4, Credibility and Trust. Relevant certifications, team credentials, client references.

Response principles: lead with their priorities over our history, open with the solution over our capabilities, use data visualization to show impact, and hold a client-focused, outcome-oriented, specific tone throughout.

Output Format

Each stage produces its primary artifact:

• Opportunity Assessment: analysis with fit score, evaluation breakdown, competitive landscape, win themes, response strategy, and a go/no-go recommendation.
• Value Proposition: master value proposition, elevator pitch, stakeholder messages, competitive positioning table, validation results.
• Proposal: complete document with cover page, executive summary, all sections, appendices.
• Statement of Work: complete SOW with cover page, all sections, signature block, appendices.
• Pitch Deck: slide-by-slide content with titles, bullets, visual suggestions, and optional speaker notes.

Fill every table cell and template slot with real reasoning and evidence (2-3 sentences of substance), not one-word placeholders. A proposal full of brackets is not a deliverable. After generating an artifact, offer the useful next move: advance to the next stage, adjust tone or scope, add specific cases or credentials, or produce a variant (shorter deck, T&M versus fixed-fee SOW).

Notes

• Win themes from Stage 1 thread through every later artifact. Keep them consistent.
• The executive summary may be the only page read. Make it stand alone.
• Quantify wherever real data allows. Specific numbers beat vague promises. Label illustrative figures and flag them for validation.
• Out-of-scope lists prevent more disputes than in-scope lists.
• Align payment terms to deliverable milestones.
• Design decks for the room: C-suite gets strategic framing, working teams get operational detail.
• Test the value proposition against the four criteria before locking positioning.
• For complex RFPs, split response development into sections with review gates.
• Always note whether evaluation weightings are stated or inferred.
• If budget is undisclosed, flag it as a risk and size the effort yourself.
• Flag unusual or oddly specific requirements that may signal a wired deal.