home / skills / ncklrs / startup-os-skills / proposal-writer

proposal-writer skill

/skills/proposal-writer

This skill crafts winning sales proposals and pricing presentations by framing buyer outcomes, reducing friction, and guiding action across executive summaries

npx playbooks add skill ncklrs/startup-os-skills --skill proposal-writer

Review the files below or copy the command above to add this skill to your agents.

Files (13)
SKILL.md
6.0 KB
---
name: proposal-writer
description: Expert sales proposal and pricing presentation strategist. Use when writing proposals, executive summaries, ROI business cases, pricing presentations, SOWs (Statement of Work), RFP responses, or competitive positioning documents. Covers proposal structure, terms positioning, design formatting, follow-up strategy, and win-rate optimization.
---

# Proposal Writer

Strategic expertise for crafting winning sales proposals, pricing presentations, and RFP responses that close deals.

## Philosophy

Great proposals don't describe your product. They describe your buyer's **future success**.

The best sales proposals:
1. **Lead with outcomes, not features** — Buyers care about their results, not your capabilities
2. **Make the decision easy** — Remove friction, objections, and confusion
3. **Tell a story** — Context → Challenge → Solution → Success
4. **Respect the reader's time** — Every section earns its place

## How This Skill Works

When invoked, apply the guidelines in `rules/` organized by:

- `structure-*` — Proposal architecture, components, flow
- `executive-*` — Executive summary, C-level communication
- `pricing-*` — Pricing presentation, anchoring, packaging
- `sow-*` — Statement of Work, deliverables, timelines
- `rfp-*` — RFP response strategy, compliance, win themes
- `design-*` — Formatting, layout, visual hierarchy
- `strategy-*` — Competitive positioning, follow-up, negotiation

## Core Frameworks

### The Proposal Pyramid

```
                    ┌─────────────────┐
                    │   Executive     │  ← Why this matters (1 page)
                    │    Summary      │
                    ├─────────────────┤
                    │   Solution &    │  ← How we solve it (2-3 pages)
                    │    Approach     │
                    ├─────────────────┤
                    │   Investment &  │  ← What it costs (1-2 pages)
                    │    Timeline     │
                    ├─────────────────┤
                    │   Proof &       │  ← Why trust us (1-2 pages)
                    │   Credibility   │
                    └─────────────────┘
```

### Proposal Types by Deal Stage

| Type | Purpose | Length | Timeline |
|------|---------|--------|----------|
| **One-Pager** | Early qualification | 1 page | Same day |
| **Solution Brief** | Mid-funnel engagement | 3-5 pages | 2-3 days |
| **Full Proposal** | Final presentation | 8-15 pages | 5-10 days |
| **RFP Response** | Formal bid | Variable | Per deadline |
| **SOW** | Contract scope | 3-10 pages | Post-verbal |

### The CLOSE Framework

Every proposal section should CLOSE:

- **C**ontext — Where the buyer is today
- **L**oss — What it's costing them (pain)
- **O**utcome — The desired future state
- **S**olution — How you get them there
- **E**vidence — Proof it works

### Pricing Presentation Matrix

| Element | Purpose | Placement |
|---------|---------|-----------|
| **Value Summary** | Anchor on ROI before price | Before pricing |
| **Investment Options** | Give control, not ultimatum | 2-3 tiers |
| **Package Comparison** | Make preferred option obvious | Side-by-side table |
| **Terms & Conditions** | Reduce friction | After pricing |
| **Next Steps** | Create momentum | Final section |

### Proposal Win Factors

```
┌─────────────────────────────────────────────────────────────┐
│                    PROPOSAL SUCCESS                         │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│   40% — Relationship & access (built before proposal)       │
│   25% — Solution fit (do you solve the problem?)            │
│   20% — Presentation (is it compelling and clear?)          │
│   15% — Pricing (is it defensible and competitive?)         │
│                                                             │
└─────────────────────────────────────────────────────────────┘
```

## Proposal Components

| Component | Required | Purpose | Common Mistakes |
|-----------|----------|---------|-----------------|
| **Cover Page** | Yes | First impression, branding | Generic, no personalization |
| **Executive Summary** | Yes | Decision-maker snapshot | Too long, feature-focused |
| **Understanding** | Yes | Prove you listened | Assumptions, not discovery |
| **Solution Overview** | Yes | What you propose | Feature dump |
| **Approach/Methodology** | Depends | How you'll do it | Too technical |
| **Timeline** | Yes | When they get value | Unrealistic dates |
| **Investment** | Yes | Total cost of ownership | Hidden costs surface later |
| **Team/About Us** | Optional | Build confidence | Self-congratulatory |
| **Case Studies** | Recommended | Social proof | Irrelevant industry |
| **Terms & Conditions** | Yes | Protect both parties | Buried gotchas |
| **Next Steps** | Yes | Drive action | Vague, no urgency |

## Anti-Patterns

- **Feature dumping** — Listing everything you can do vs. what they need
- **One-size-fits-all** — Using templates without customization
- **Price-first** — Showing cost before establishing value
- **Competitor bashing** — Direct attacks backfire; focus on your strengths
- **Wall of text** — No visual hierarchy, hard to scan
- **Jargon overload** — Internal terminology the buyer doesn't know
- **Missing next steps** — Proposal ends with no clear action
- **Over-promising** — Timelines and outcomes you can't deliver
- **Ghosting** — No follow-up strategy after sending

Overview

This skill is an expert sales proposal and pricing presentation strategist that helps craft proposals, executive summaries, ROI cases, SOWs, RFP responses, and competitive positioning docs. It focuses on outcome-led messaging, win-rate optimization, and clear decision pathways to make buying easy. Use it to tighten structure, defend pricing, and increase close probability.

How this skill works

When invoked, the skill applies a structured ruleset covering proposal architecture, executive messaging, pricing strategy, SOW structure, RFP compliance, design and follow-up. It uses the Proposal Pyramid and the CLOSE framework to shape content: establish context, quantify pain, present outcomes, describe the solution, and provide evidence. It also recommends pricing matrices, tiered packaging, and next-step sequencing to remove friction.

When to use it

  • Drafting an executive summary or one-pager for a C-level decision maker
  • Creating a mid-funnel solution brief or a full proposal for a formal pitch
  • Preparing pricing presentations with defensible anchoring and tiering
  • Responding to RFPs with compliant, win-themed answers
  • Writing or reviewing an SOW to align deliverables, timeline, and risk

Best practices

  • Lead with outcomes and ROI before showing price; make value undeniable
  • Keep each section purposeful and scannable; every paragraph must earn its place
  • Offer 2–3 investment tiers with a clearly preferred option and side-by-side comparison
  • Use credibility — short case studies and quantifiable evidence — near the ask
  • Include explicit next steps and a short decision timeline to create urgency

Example use cases

  • Convert a technical demo into a 3–5 page solution brief that executives will read
  • Turn an informal scope into a defensible SOW with milestones, acceptance criteria, and payment terms
  • Build a pricing slide deck that anchors ROI, shows 3 packages, and highlights the recommended package
  • Prepare an RFP response that aligns win themes to evaluation criteria and minimizes compliance risk
  • Revise a full proposal to follow the Proposal Pyramid and CLOSE framework for clarity and persuasion

FAQ

How long should a full proposal be?

Typically 8–15 pages for final presentations; keep focused on decision-maker needs and move detailed specs to appendices.

When should I include an SOW vs. a full proposal?

Use a full proposal to sell the solution and SOW after verbal agreement to lock scope, milestones, and commercial terms.