mcpField
P
proposal-writer

proposal-writer

github.com/ncklrsMarketing & growth53596 installsUpdated 35w ago
Repository

About proposal-writer

A sales-proposal writing skill for teams preparing proposals, pricing presentations, SOWs, and RFP responses. It provides guidance on proposal structure, buyer-focused messaging, pricing, design, and follow-up.

Key features

  1. 01按交易阶段选择提案类型
  2. 02以买方成果组织内容
  3. 03执行摘要与提案结构指导
  4. 04定价方案和套餐比较
  5. 05RFP 与 SOW 撰写指导
  6. 06版式、谈判和跟进建议

Use cases

  1. 01为潜在客户准备解决方案提案
  2. 02整理报价选项和套餐对比
  3. 03撰写 RFP 回复或 SOW

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ncklrs/startup-os-skills --skill proposal-writer

After installing, type/proposal-writerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

rules/
_sections.md
design-formatting.md
executive-stakeholder-alignment.md
executive-summary-writing.md
pricing-presentation.md
pricing-roi-business-case.md
rfp-response-strategy.md
sow-writing.md
strategy-competitive-differentiation.md
strategy-followup.md
structure-proposal-architecture.md
structure-terms-conditions.md

Details

From the project README

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
TypePurposeLengthTimeline
One-PagerEarly qualification1 pageSame day
Solution BriefMid-funnel engagement3-5 pages2-3 days
Full ProposalFinal presentation8-15 pages5-10 days
RFP ResponseFormal bidVariablePer deadline
SOWContract scope3-10 pagesPost-verbal
The CLOSE Framework

Every proposal section should CLOSE:

  • Context — Where the buyer is today
  • Loss — What it's costing them (pain)
  • Outcome — The desired future state
  • Solution — How you get them there
  • Evidence — Proof it works
Pricing Presentation Matrix
ElementPurposePlacement
Value SummaryAnchor on ROI before priceBefore pricing
Investment OptionsGive control, not ultimatum2-3 tiers
Package ComparisonMake preferred option obviousSide-by-side table
Terms & ConditionsReduce frictionAfter pricing
Next StepsCreate momentumFinal 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

ComponentRequiredPurposeCommon Mistakes
Cover PageYesFirst impression, brandingGeneric, no personalization
Executive SummaryYesDecision-maker snapshotToo long, feature-focused
UnderstandingYesProve you listenedAssumptions, not discovery
Solution OverviewYesWhat you proposeFeature dump
Approach/MethodologyDependsHow you'll do itToo technical
TimelineYesWhen they get valueUnrealistic dates
InvestmentYesTotal cost of ownershipHidden costs surface later
Team/About UsOptionalBuild confidenceSelf-congratulatory
Case StudiesRecommendedSocial proofIrrelevant industry
Terms & ConditionsYesProtect both partiesBuried gotchas
Next StepsYesDrive actionVague, 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

Comments

Markdown supported