---
name: proposal-sow-builder
description: Build a client-ready proposal or statement of work that sells the outcome and controls scope. Use this skill whenever a user needs a proposal, SOW, scope document, engagement outline, or pricing summary for a prospect, or says 'put together a proposal', 'scope this engagement', 'send them pricing', or 'draft the SOW'. Trigger whenever described work needs to become a document that closes and protects the engagement.
---

# Proposal and SOW Builder

## What this does and why it matters
A proposal is a selling document, not a paperwork exercise. Most read like internal specs and lose to competitors who framed the outcome better. This skill leads with the client's result, defines scope tightly enough to stop scope creep before it starts, and presents pricing with confidence, so the document advances the sale instead of stalling it.

## Inputs to gather
1. The client and the problem being solved.
2. The solution and deliverables.
3. Pricing model (fixed fee, retainer, time and materials, per user) and the numbers.
4. Timeline and milestones.
5. Assumptions, exclusions, and client responsibilities.

## Method

### 1. Open with the outcome, not the process
The first section names the client's problem and the result they get. Buyers fund outcomes, not activity.

### 2. Define scope by including and excluding
List what is in scope and, with equal care, what is explicitly out. Scope creep is born in vague proposals; an exclusions section is the cheapest insurance in professional services.

### 3. Turn deliverables into milestones with timing
Concrete milestones with dates or relative timing make the engagement feel real and manageable.

### 4. Present pricing with conviction
Name the model and show totals. If tiers exist, show them side by side so the buyer chooses among your options rather than whether to buy at all. Anchor to value where possible.

### 5. Guardrail with assumptions and client responsibilities
Every dependency the client must meet goes here, so a missed client obligation does not become your overrun.

### 6. Close with a clear next step and acceptance
A named signer, a dated acceptance line, and one obvious next action.

## Output format
ALWAYS use:

# Proposal: [Engagement Name]
## The situation
## Objectives and outcomes
## Scope of work (included)
## Out of scope
## Deliverables and milestones
## Investment (model named, totals shown, tiers side by side if any)
## Assumptions and client responsibilities
## Timeline
## Terms and acceptance
## Next step

## Anti-patterns to avoid
- Leading with your process and credentials instead of their outcome.
- No exclusions section (guaranteed scope creep).
- Burying or apologizing for the price.
- A single take-it-or-leave-it number when tiers would let the buyer self-select up.

## Compliance note
Pricing and legal terms come from the user, never invented. Flag missing numbers or terms as placeholders rather than guessing.

## Example
For an AI implementation, the proposal opens with "cut manual reporting from 12 hours a week to under 1", scopes three deliverables, excludes data cleanup beyond one source, and offers Standard and Plus tiers side by side.