ホーム/技术写作/proposal-writer
P

proposal-writer

by @ncklrsv
4.6(11)

プロの営業提案および価格提示戦略家として、このスキルはユーザーが説得力のあるビジネス提案を作成し、明確で効果的な価格表示を設計して顧客を獲得するのに役立ちます。

Business Proposal WritingGrant WritingTechnical WritingPersuasive CommunicationMarket ResearchGitHub
インストール方法
npx skills add ncklrs/startup-os-skills --skill proposal-writer
compare_arrows

Before / After 効果比較

1
使用前

営業提案書と価格提示プレゼンテーションは戦略性に欠け、顧客を惹きつけにくく、成約率が低い。内容の構成が混乱しており、製品の価値と利点を効果的に強調できていません。

使用後

専門家による戦略的指導を受け、非常に説得力のある営業提案書と価格提示プレゼンテーションを作成します。製品の価値を効果的に示し、顧客の信頼を高め、成約率を大幅に向上させます。

description SKILL.md


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

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

forumユーザーレビュー (0)

レビューを書く

効果
使いやすさ
ドキュメント
互換性

レビューなし

統計データ

インストール数760
評価4.6 / 5.0
バージョン
更新日2026年3月16日
比較事例1 件

ユーザー評価

4.6(11)
5
0%
4
0%
3
0%
2
0%
1
0%

この Skill を評価

0.0

対応プラットフォーム

🔧Claude Code
🔧OpenClaw
🔧OpenCode
🔧Codex
🔧Gemini CLI
🔧GitHub Copilot
🔧Amp
🔧Kimi CLI

タイムライン

作成2026年3月16日
最終更新2026年3月16日