Proposal Development

Manage the full business development lifecycle for consulting engagements: assess opportunities, develop proposals, draft SOWs, build pitch decks, and articulate value propositions. This covers the business development lifecycle from opportunity assessment through proposal submission. For creating deliverables during an engagement (steering committee decks, final reports), see client-deliverables.

Determine which stage of the BD lifecycle the user needs, then execute accordingly. A full pursuit flows through these stages in order, but the user may enter at any point.

Stage 1: Opportunity Assessment

Analyze an RFP, inbound request, or proactive pursuit to decide whether and how to respond.

1a. Parse the Opportunity

Accept and parse the source material (RFP document, client conversation notes, or opportunity brief). Identify:

Client organization and background
Problem statement — what challenge are they trying to solve?
Scope of work — what are they asking for?
Deliverables — what will be required?
Timeline — key dates and deadlines
Budget — if disclosed (flag as risk if not)
Evaluation criteria — how will responses be scored?
Submission requirements — format, length, required sections

For proactive pursuits where there's no RFP, work with what's available: client conversations, news, strategic context, known pain points.

1b. Score the Opportunity

Assess fit before investing effort:

## Opportunity Assessment

- **Fit score**: [High / Medium / Low]
- **Estimated value**: [Range if available]
- **Win probability**: [Initial assessment with rationale]
- **Resource requirement**: [High / Medium / Low]
- **Strategic value**: [Does this open a new account, practice area, or market?]

Go/No-Go signals:

Do we have the right people and relevant experience?
Is the timeline realistic?
Are there signs of a preferred vendor? (unusual or overly specific requirements, insider language)
Does the economics work at our rate card?
Is this strategically important beyond this single engagement?

1c. Analyze Evaluation Criteria

For RFPs with explicit criteria, break down the evaluation framework:

Criterion	Weight	Interpretation	Our Strength
[Criterion]	X%	[What they really want]	[High/Med/Low]

Key questions:

What matters most? (highest weight)
What is differentiated vs. table stakes?
What are they explicitly vs. implicitly evaluating?

Note whether weightings are explicit or inferred. For informal pursuits, identify the implicit evaluation criteria from client conversations and context.

1d. Assess Competitive Position

Map the competitive landscape:

Known competitors: Who is likely bidding?
Our advantages: Where do we win against each?
Our vulnerabilities: Where do we need to mitigate?
Gaps: What do we need to address?

If multiple stakeholders are involved, note different evaluation perspectives (technical vs. commercial vs. strategic).

1e. Identify Win Themes

Develop 3-5 win themes locked to what the client is actually evaluating. Each theme needs a "why" (not just a "what"), evidence, and explicit alignment to evaluation criteria:

### Theme: [Name]
- **Why it wins**: [Client pain point] is their priority — this addresses it directly
- **Evidence**: [Quantifiable case study or track record with measurable outcomes]
- **Alignment**: [Maps to evaluation criterion X]

Win themes carry forward into every subsequent stage. They're the backbone of the proposal narrative.

Stage 2: Value Proposition

Articulate the differentiated value that underpins the pursuit. This work feeds into the proposal, pitch deck, and client conversations.

2a. Define Value Drivers

Structure value using this framework:

What value do we create?

Primary value: cost reduction, revenue growth, risk mitigation, capability building
Quantified impact: specific numbers, percentages, timeframes

Why does this matter to THEM?

Connect value to their specific priorities, not your capabilities
Use their language and terminology
Address their biggest fear or aspiration

Why should they believe us?

Methodology with track record
Relevant experience with named outcomes
Credentials, certifications, or third-party validation

What makes us different?

Differentiators that only we can claim
Why those differentiators are sustainable
Why competitors cannot easily replicate them

How do we deliver and prove it?

Delivery model
Track record with quantified results from similar engagements
How we de-risk the engagement for the client

2b. Develop Messaging Hierarchy

Layer messaging for different audiences and contexts:

Headline Value Proposition One sentence: For [target client] who [need], our [offering] delivers [primary benefit] unlike [alternative] because [key differentiator].

Elevator Pitch (30 seconds) 3-4 sentences a partner could deliver naturally:

Hook: the client problem
Solution: what we do differently
Proof: one compelling result
Action: what happens next

Stakeholder-Level Messages

Audience	Focus	Proof
C-Suite	Enterprise value, competitive advantage, shareholder impact	Board-level metrics
Functional Leaders	Capability improvement, team effectiveness, operational metrics	Operational KPIs
Practitioners	Methodology, tools, skill development, daily improvement	Practical examples, peer references

Competitive Positioning

Dimension	Our Position	Competitor A	Competitor B
[Key dimension]	[Our stance]	[Their stance]	[Their stance]

2c. Validate the Messaging

Run the value proposition through four tests:

Clarity: Can someone explain it in 30 seconds? Is the benefit immediately obvious?
Relevance: Does it address their specific pain? Would they care?
Differentiation: Could a competitor make this same claim? Is it specific?
Belief: Is it credible? Do we have proof points?

If any test fails:

Clarity fails: simplify, remove jargon, cut to one core benefit
Relevance fails: you may be solving the wrong problem — re-examine client needs
Differentiation fails: dig into methodology, team, or IP — replace generic claims with specifics only you can claim
Belief fails: strengthen proof points with quantified case studies, named references, third-party validation

Stage 3: Proposal Development

Write the full proposal document. Carry forward win themes and value proposition work from earlier stages.

3a. Gather Context

Confirm or gather:

Client background: Industry, market position, recent initiatives, current challenges
Engagement scope: Problem statement, desired outcomes, scope boundaries, timeline
Decision process: Who decides, timeline, evaluation criteria
Our positioning: Win themes, value proposition, differentiation

3b. Structure the Proposal

Lead with their challenges, not your credentials:

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, restructure to match the required format while preserving this narrative flow within each section.

3c. Develop Each Section

Executive Summary (1 page max)

Write this LAST but position it FIRST. It must stand alone — it may be the only thing read. Lead with client outcomes:

[Client Name] seeks to [objective]. We propose [approach] that will deliver [quantified outcome].

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

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

Our Approach
[Methodology] over [timeline], structured in [number] phases.

Investment
[Range or structure]

Next Steps
[One clear, low-friction action]

Understanding Your Challenges

Demonstrate client knowledge. Reference their specific challenges, use their terminology, acknowledge their constraints. This section earns the right to propose a solution.

Our Recommended Approach

Present methodology as the solution to their specific challenges:

Phase 1: [Name] — [Duration]
Objective: [What we achieve]
Key Activities: [Activities]
Deliverables: [Deliverables]

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

Critical Success Factors
- [Factor 1]
- [Factor 2]

What This Delivers

Quantified outcomes, ROI, impact — tied directly to their stated priorities. Show how each outcome maps back to a challenge they raised.

Why [Our Firm]

Specific, not generic. Industry depth with relevant statistics. Methodology differentiators. Case studies with quantified results.

Team

Key team members with role on this engagement, relevant experience (2-3 bullets each), and notable credentials. Include an org chart for larger teams.

Client References

Relevant case studies structured as Challenge → Approach → Results (quantified). Select cases that mirror the client's situation.

Investment

Present pricing clearly:

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

Include what's covered, what's excluded, and key assumptions. Make payment terms align with deliverable milestones.

Next Steps

One clear, low-friction action. Not a menu of options.

3d. Persuasion Principles

Throughout the proposal:

Lead with outcomes in every section (what this delivers for them)
Use specificity over generality (client names, data, quantified results)
Evidence-based credibility (case studies with measurable impact, not just credentials)
Every section connects back to their stated objectives
Compliance + responsiveness + persuasion + credibility, in that order

Stage 4: Statement of Work

Draft the SOW that formalizes scope, deliverables, timeline, governance, and commercial terms. The SOW protects both parties. Vague SOWs create scope creep and disputes.

4a. Define Project Context

Gather or confirm:

Background: Business context, rationale, strategic importance
Objectives: Primary objective (what success looks like), secondary objectives, success metrics
Scope: What's IN scope, what's explicitly OUT of scope, key assumptions

4b. SOW 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. Critical SOW Sections

Scope of Work — In and Out

Be exhaustive. The out-of-scope list is as important as the in-scope list:

In Scope
- [Activity or deliverable]
- [Activity or deliverable]

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

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

Dependencies
- [External dependency — client action required]
- [External dependency — third-party action required]

Deliverables

Specify each deliverable precisely with description, format, and timing:

Deliverable	Description	Format	Timing
D1.1	[Name]	[Format]	[When]

Success Criteria

Measurable, not aspirational:

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

Governance

Match the governance structure to the engagement's complexity and the client's organization:

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

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

Commercial Terms

Fee structure (fixed, T&M, or blended), payment schedule aligned to milestones, expense policy, and change control process:

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

Acceptance Criteria

Define specific, measurable acceptance criteria for each deliverable. Include:

What "done" looks like for each deliverable
Review period (X business days)
Acceptance process (delivery → review → accept or feedback → revision)
Grounds for rejection (failure to meet criteria, material scope deviation, factual errors)
Deemed acceptance if no feedback within the review period

Team & Roles

Both sides. Consulting team with role, name, level, and commitment percentage. Client team with role and responsibilities. Client responsibilities are critical — engagements fail when client obligations aren't spelled out.

4d. Change Control

Include a process for scope modifications. Any change to scope, timeline, or cost requires:

Written change request describing the modification
Impact assessment (scope, timeline, cost)
Approval from designated decision makers on both sides
Amendment to the SOW

Stage 5: Pitch Deck

Build a persuasive deck for client presentations. Decks complement written proposals; they're the vehicle for oral delivery and discussion.

5a. Determine Deck Objectives

Clarify before building:

Audience: C-suite, board, working team (each gets different treatment)
Occasion: Initial pitch, follow-up, final presentation, oral defense
Time available: Drives slide count and depth
Key messages: What do we want them to remember?
Desired action: What do we want them to do?

5b. Standard Structure (15-20 slides)

Opening (1-2 slides)
  1. Title

The Challenge (2-3 slides)
  2. Context and situation
  3. The problem / opportunity
  4. Why now?

Our Solution (4-6 slides)
  5. Our approach
  6. Methodology
  7. Key differentiators
  8. What makes us unique

Results & Credentials (3-4 slides)
  9. Relevant case study 1
  10. Relevant case study 2
  11. Team experience

The Deal (2-3 slides)
  12. Scope and approach
  13. Investment
  14. Timeline
  15. Next steps

Closing (1-2 slides)
  16. Summary
  17. Q&A

Adjust length for context. A 30-minute slot with discussion gets 10-12 slides. A detailed capabilities presentation may need 25+.

5c. Slide Development

The Challenge section creates tension. Show you understand their world:

Context: industry trends, market forces, current position
The problem: current state vs. desired state (make the gap visceral)
Why now: market timing, competitive pressure, cost of inaction

Our Solution section resolves the tension:

Approach: phased methodology framed as the answer to their challenge
Differentiators: what makes us different, presented as evidence not assertion

Capability	Our Difference	Proof
[Area]	[What makes us different]	[Evidence]

Results & Credentials section builds belief:

Case studies: Challenge → Approach → Results (quantified). Include client testimonials if available
Team: relevant experience, combined track record

The Deal section makes it concrete:

Scope (in and out), investment by phase, timeline with milestones, clear next steps

5d. Storytelling Principles

One message per slide — anchor every element to the slide's thesis
Start with why — create urgency before presenting the solution
Quantify everything — facts build credibility
Create tension — problem → solution → result narrative arc
End with action — specific, time-bound next steps
Stay on the storyline — if a slide doesn't advance the argument, cut it
Answer first — lead with recommendations, support with analysis
Design for the room — white space, clarity over density, visuals over text walls

Response Strategy Framework

When developing an RFP response, layer the strategy in tiers:

Tier 1: Compliance and Responsiveness

Must-pass requirements (non-negotiable criteria)
Scored requirements (weighted criteria to address well)

Tier 2: Strength-Based Win Themes

Primary win themes aligned to highest-weighted criteria
Differentiators that set us apart from competitors

Tier 3: Persuasion and Evidence

Case studies with quantifiable results
Methodology credentials and track record

Tier 4: Credibility and Trust

Relevant certifications and team credentials
Client references and testimonials

Response principles:

Lead with their priorities, not your history
Open with solution, not capabilities
Use data visualization to demonstrate impact
Client-focused, outcome-oriented, specific tone throughout

Output Format

Output depends on the stage requested. Each stage generates its primary artifact:

Opportunity Assessment → Analysis document with fit score, evaluation breakdown, competitive landscape, win themes, response strategy, and go/no-go recommendation

Value Proposition → Master value proposition, elevator pitch, stakeholder-level messages, competitive positioning table, validation results

Proposal → Complete proposal document with cover page, executive summary, all sections, and appendices

Statement of Work → Complete SOW with cover page, all sections, signature block, and appendices

Pitch Deck → Slide-by-slide content with titles, bullets, visual suggestions, and optional speaker notes

After generating any artifact, offer relevant next steps:

Move to the next stage in the lifecycle
Adjust tone, emphasis, or scope
Add specific case studies or credentials
Create alternative versions (e.g., shorter deck, T&M vs. fixed-fee SOW)

Notes

Win themes developed in Stage 1 should thread through every subsequent artifact
The executive summary may be the only thing read. Make it standalone
Quantify results wherever possible. Specific numbers beat vague promises
Out-of-scope lists prevent more disputes than in-scope lists
Payment terms should align with deliverable milestones
Design decks for the audience. C-suite gets strategic framing; working teams get operational detail
Test value propositions against the four validation criteria before committing to positioning
For complex RFPs, recommend breaking response development into sections with review gates
Always note if evaluation criteria weightings are explicit or inferred
If budget is not disclosed, flag it as a risk factor
Flag any unusual requirements that may indicate a preferred vendor

proposal-development