Proposal & Statement of Work

Important: This skill assists with proposal and SOW development but does not provide legal advice. All proposals, terms, and pricing should be reviewed by qualified legal and financial professionals before submission to clients.

Framework for developing client-facing proposals, statements of work (SOWs), and engagement letters. Covers scoping methodology, pricing models, rate structures, RFP response strategy, and workflows for moving from discovery to finalized engagement terms.

Proposal Structure

A professional proposal should position the firm as capable while clearly setting expectations around scope, resources, and investment.

Executive Summary

The executive summary appears first but should be written last. It provides a one-page overview of the engagement: the client's challenge, your recommended approach, the expected outcomes, the team, and the financial investment. Keep to 150-200 words and use client language rather than internal jargon.

Components to include:

Problem statement: Restate the client's challenge in their terms to demonstrate listening
Proposed solution: High-level overview of the approach without excessive technical detail
Key outcomes: What the client will have or understand by the end of the engagement
Team composition: Number and seniority of team members assigned
Total investment: Single-line investment amount and engagement duration
Timeline: Approximate start date and duration in weeks or months

Understanding of Client Need

Demonstrate that you understand the client's situation, constraints, and strategic context. This section is critical for winning trust and differentiating from competitors.

Approach:

Summarize the client's business context and industry dynamics
Articulate the specific challenge or opportunity as presented
Identify the key stakeholders who will be affected by the engagement
Call out constraints or interdependencies the client mentioned
Show awareness of competing initiatives or budget pressures
Reference client-specific data, recent announcements, or known initiatives

Do not: Repeat the RFP verbatim or reference a generic approach. This section must demonstrate engagement with the client's unique situation.

Proposed Approach

Break down your methodology into phases, workstreams, or work steps. Each phase should have a clear objective, deliverables, duration, and resource allocation.

Standard engagement structure (adapt as needed):

Phase 1: Discovery & Assessment (Weeks 1-2)

Conduct stakeholder interviews with key operational and financial leaders
Review historical performance data, systems, and processes
Document current-state process maps and organizational structure
Deliverable: Discovery report with findings summary and preliminary observations

Phase 2: Analysis & Recommendations (Weeks 3-4)

Perform root cause analysis on identified problem areas
Develop 2-3 scenario alternatives with pros/cons analysis
Model financial or operational impact of each recommendation
Conduct validation workshop with client team
Deliverable: Recommendations report with financial impact analysis

Phase 3: Implementation Planning & Handoff (Weeks 5)

Develop detailed implementation roadmap with milestones
Create job descriptions or transition plans for restructured roles
Prepare training materials and implementation guides
Conduct knowledge transfer workshop with client team
Deliverable: Implementation playbook and transition plan

Clarify assumptions at the end of this section (see Assumptions & Exclusions below).

Team & Staffing

Provide biographies, relevant experience, and roles for each team member. Lead with your most senior / credible resource. Include a 3-5 sentence bio for each person emphasizing relevant prior engagements.

Table format example:

| Role | Name | Seniority Level | FTE Allocation | Key Experience | |------|------|-----------------|-----------------|-----------------| | Engagement Lead | [Name] | Partner / Principal | 0.5 | [2-3 relevant engagements in this industry/function] | | Senior Consultant | [Name] | Senior Consultant | 1.0 | [Specific expertise relevant to this engagement] | | Consultant | [Name] | Consultant | 1.0 | [Supporting skills and industry experience] |

Note that your most senior resource should have majority of the engagement touchpoints, while junior resources support analysis and documentation.

Timeline & Milestones

Present a visual timeline showing phasing, key decision gates, and client deliverable dates. Include required client participation points.

Example timeline:

| Week | Milestone | Deliverable | Client Involvement | Status | |------|-----------|-------------|-------------------|--------| | 1-2 | Discovery | Current-state report | 5 interviews, 1 workshop | TBD | | 3-4 | Analysis | Recommendations report | Validation workshop | TBD | | 5 | Implementation Planning | Playbook & transition plan | Knowledge transfer session | TBD |

Ensure the timeline is realistic — propose 1-2 days of client time per week minimum.

Pricing

Present the total investment, payment schedule, and any assumptions about out-of-scope work. See Pricing Models section below for detailed guidance on fee structures.

Standard format:

Engagement Investment:        $XX,XXX
Duration:                     X weeks / X months
Monthly burn rate:            $X,XXX
Payment Schedule:
  Initial payment (due with signature):    $XX,XXX (XX%)
  Progress payment (due [date]):           $XX,XXX (XX%)
  Final payment (upon delivery):           $XX,XXX (XX%)

Include language that out-of-scope work will be billed at daily rates (define rates by level in appendix) or require a change order.

Terms & Conditions

Include a brief section on key terms, or reference a standard engagement letter as an exhibit. Critical terms include:

Engagement duration: Specific start and end date
Resource commitment: FTE allocation and expected availability
Confidentiality: Standard confidentiality obligations
Liability limitations: Limitation of liability clause (capped at fees paid)
Termination: Either party can terminate with written notice; fees earned to date are due
Change order process: Process for approving scope changes and adjusting fees

Statement of Work Structure

An SOW is a more detailed, contractually binding document than a proposal. It formalizes the engagement terms and serves as the primary operational reference during delivery.

Scope Definition

Clearly state what is included and excluded in the engagement. Use specific, observable language.

Include statement:

Develop a comprehensive operational assessment of the [function/process] organization including current staffing, systems, and decision-making workflows
Recommend organizational structure and process improvements to improve efficiency by [metric if available]
Facilitate change readiness workshops with leadership and key stakeholder groups
Deliver implementation guides and training materials
[X] days of on-site engagement time

Exclude statement:

Implementation of recommended changes (separate engagement if desired)
Redesign of systems or data architecture (requires technical specialist engagement)
HR or legal consultation on employment matters
Executive recruitment services or interim staffing
Revision cycles beyond [X] rounds of feedback

Deliverables List

Itemize specific deliverables with format (written report, presentation deck, data model, etc.) and delivery dates.

Example:

| # | Deliverable | Format | Delivery Date | Acceptance Criteria | |---|-------------|--------|---------------|-------------------| | 1 | Current-state assessment report | PowerPoint deck + appendix | [Date] | Covers scope items 1-5; 15-20 pages main deck; identifies data gaps | | 2 | Operational metrics dashboard | Excel workbook | [Date] | Tracks 8-10 key metrics; includes 24-month historical trend; automated refresh | | 3 | Organizational structure options | PowerPoint + org charts | [Date] | 3 scenarios; FTE count and estimated salary impact for each | | 4 | Implementation roadmap | Gantt chart + narrative | [Date] | 12-month timeline; resource requirements by phase; risk assessment | | 5 | Training materials | PDF guide + video walkthroughs | [Date] | Covers 5 key process changes; accessible to end users with [X] knowledge |

Assumptions & Exclusions

Document critical assumptions and limitations clearly to avoid scope disputes later.

Assumptions:

The client will provide access to key stakeholders for interviews within [X] days of request (5-10 business days typical)
Historical data, reports, and system access will be provided without delays
A client project manager will be designated to coordinate logistics and approvals
The client will not substantially reorganize or reduce staffing during the engagement
[Specific tool / platform] will remain operational during the engagement
Client feedback on draft deliverables will be provided within [X] business days

Exclusions:

Salary benchmarking or individual compensation analysis (outside scope)
Custom system development or data migration
Change management support beyond workshops and materials
Ongoing advisory or retainer-based support (requires separate engagement)
Work on weekends or outside standard business hours (requires advance notice and may incur premium rates)

Acceptance Criteria

Define explicitly what constitutes delivery and acceptance of each deliverable. This prevents disputes about quality and completeness.

Example: "Deliverables are deemed accepted when the client confirms in writing that [specific deliverable] meets the stated Acceptance Criteria. If the client identifies gaps, we will provide up to [X] rounds of revisions at no additional cost. Revisions requested after [X] rounds, or revisions that expand scope, will be billed as out-of-scope work at daily consulting rates."

Billing Schedule & Change Order Process

Specify payment terms, invoicing frequency, and the formal process for handling scope changes.

Billing schedule format:

Upfront payment (due upon signature): XX% of total fee = $[amount]
Progress payment (due end of Week X): XX% of total fee = $[amount]
Final payment (due upon delivery): XX% of total fee = $[amount]

Change order process:

Client submits written request for scope change to project lead
Project lead reviews and prepares impact assessment within [X] business days
Impact assessment includes: scope description, resource impact, timeline delay, and fee adjustment
Client approves or negotiates change order before work begins
Approved change order is signed by both parties and becomes amendment to SOW
Work begins only after change order is signed

References

For detailed templates, frameworks, and field-level guidance, read:

references/proposal-sow-reference.md — Complete framework details, templates, and examples

Read this file when the task requires:

Scoping Methodology
Pricing Models
Rate Card Framework
RFP Response Best Practices
Engagement Workflow
Proposal Scoring Rubric
Common Proposal Mistakes
Negotiation Tactics