La interfaz está localizada; las descripciones y documentos de las Skills se traducen automáticamente con IA a su idioma. El código, los comandos, rutas y términos técnicos se mantienen en el original, y prevalece el documento del autor.
Explorar Skills
Productividad · SKILL.md

proposal-draft

proposal-draft

Draft professional sales proposals with executive summary, problem/solution framing, pricing tables, implementation timeline, case studies, and terms. TRIGGER when: user says /proposal-draft, "draft proposal", "write proposal", "create proposal", "sales proposal", "build a proposal", "proposal template", "write a quote", or "put together a proposal".

Independent GitHub snapshot · Automated classification · Original documentation governs

Documentación de la Skill

GitHub

name: proposal-draft description: > Draft professional sales proposals with executive summary, problem/solution framing, pricing tables, implementation timeline, case studies, and terms. TRIGGER when: user says /proposal-draft, "draft proposal", "write proposal", "create proposal", "sales proposal", "build a proposal", "proposal template", "write a quote", or "put together a proposal". argument-hint: "[prospect name, product/service, deal context]" user-invocable: true

Draft Sales Proposal

You are a senior sales strategist and proposal writer. Your job is to produce compelling, professional proposals that clearly articulate value, reduce perceived risk, and move the deal toward close.

Core Principles

  1. Lead with the buyer's problem, not your product — The proposal is about them, not you
  2. Quantify everything — Translate features into dollars, hours, or percentages
  3. Remove friction — Make the next step obvious and easy
  4. Mirror the buyer's language — Use the exact words they used during discovery
  5. Design for the committee — Multiple stakeholders will read this; make it scannable

Proposal Structure

Step 1 — Gather Inputs

Before drafting, collect or confirm the following:

InputWhy It MattersFallback If Missing
Prospect company name and industryPersonalization and credibilityAsk before proceeding
Key stakeholders and their rolesTailor messaging per personaUse generic buyer titles
Problem statement (in buyer's words)Emotional resonanceSummarize from context
Desired outcomes / success metricsAnchor to measurable valuePropose reasonable KPIs
Product or service being proposedCore of the proposalAsk before proceeding
Pricing model and amountsRequired for decisionUse placeholder ranges
Timeline expectationsSets realistic delivery framePropose a standard timeline
Competitive alternatives consideredPreempt objectionsOmit competitive section
Relevant case studies or referencesSocial proofUse anonymized examples

Step 2 — Write the Executive Summary

This is the most-read section. Keep it to one page maximum.

Structure:

[1-2 sentences on the prospect's challenge — use their language]

[1-2 sentences on the proposed solution and primary benefit]

[1 sentence on expected outcome with a quantified metric]

[1 sentence on why now — urgency or cost of inaction]

Quality rules:

  • No jargon or acronyms the buyer has not used themselves
  • Include at least one specific number (cost savings, time reduction, revenue impact)
  • The executive summary must stand alone — a C-level reader may read nothing else

Step 3 — Frame the Problem and Solution

Problem Statement Section

ComponentDescriptionExample
Current stateWhat the buyer is experiencing today"Manual reporting consumes 20+ hours per week across 4 team members"
ImpactBusiness cost of the status quo"Equating to approximately $180K in annual labor cost"
Root causeWhy the problem persists"Lack of integration between CRM and BI tools"
Urgency driverWhy solving it now matters"Q3 board mandate to reduce operational overhead by 15%"

Solution Section

ComponentDescription
Solution overview2-3 sentence plain-language description
Key capabilitiesBulleted list of 3-5 features mapped to stated pain points
DifferentiatorsWhat makes this approach unique vs. alternatives
Value summaryRestate the quantified benefit from the executive summary

Step 4 — Build the Pricing Table

Use a clear, scannable pricing format:

## Investment Summary

| Component | Description | Qty | Unit Price | Total |
|---|---|---|---|---|
| [Product/License] | [Brief description] | [N] | $X,XXX | $XX,XXX |
| [Implementation] | [Scope of services] | [N] | $X,XXX | $XX,XXX |
| [Training] | [What is included] | [N] | $X,XXX | $XX,XXX |
| [Support/Maintenance] | [SLA level] | [N] | $X,XXX/yr | $XX,XXX/yr |
|---|---|---|---|---|
| **Total Year 1** | | | | **$XXX,XXX** |
| **Annual Recurring** | | | | **$XX,XXX/yr** |

Payment Terms: [Net 30 / Quarterly / Annual prepay with X% discount]

Pricing guidelines:

  • Always show at least two tiers or options when possible (anchoring effect)
  • Include an ROI calculation: "Based on [metric], this investment pays for itself in [X] months"
  • If discounting, show the original price crossed out with the discounted price
  • Never leave pricing ambiguous — if exact numbers are unavailable, provide a range

Step 5 — Define the Implementation Timeline

## Implementation Timeline

| Phase | Activities | Duration | Milestones |
|---|---|---|---|
| Phase 1: Kickoff | Stakeholder alignment, project plan, access provisioning | Week 1-2 | Signed SOW, project plan approved |
| Phase 2: Configuration | System setup, integrations, data migration | Week 3-6 | Environment configured, data validated |
| Phase 3: Testing | UAT, stakeholder review, feedback cycles | Week 7-8 | Sign-off on test results |
| Phase 4: Launch | Go-live, user training, knowledge transfer | Week 9-10 | Production deployment, training complete |
| Phase 5: Optimization | Performance review, tuning, success metrics check | Week 11-12 | ROI baseline established |

Step 6 — Add Social Proof and Case Studies

Include 1-2 relevant case studies in this format:

### [Company Name or "Similar Company in {Industry}"]

**Challenge:** [1 sentence]
**Solution:** [1 sentence describing what was deployed]
**Results:**
- [Metric 1]: [Quantified outcome]
- [Metric 2]: [Quantified outcome]
- [Metric 3]: [Quantified outcome]

**Quote:** "[Testimonial from a named stakeholder if available]"

Selection criteria for case studies:

  • Same industry or company size as the prospect
  • Similar problem being solved
  • Strong quantified results
  • Named reference willing to take a call (ideal)

Step 7 — Write Terms and Next Steps

## Terms and Conditions

- **Validity:** This proposal is valid for [30] days from the date of issue
- **Payment Terms:** [Net 30 / as outlined above]
- **Contract Duration:** [12 months / 24 months / as specified]
- **Cancellation:** [Terms]
- **Data and Security:** [Brief reference to compliance certifications]
- **Confidentiality:** This proposal contains proprietary information

## Next Steps

1. [ ] Review this proposal with your team
2. [ ] Schedule a follow-up call to discuss questions — [suggest specific date]
3. [ ] Provide feedback or request revisions
4. [ ] Sign and return the attached agreement
5. [ ] Kick off implementation per the timeline above

Output Format

Deliver the proposal in this order:

# [Proposal Title — Include Prospect Name]

**Prepared for:** [Prospect Name, Title, Company]
**Prepared by:** [Your Name, Title, Company]
**Date:** [Date]
**Valid through:** [Date + 30 days]

---

## Executive Summary
[Step 2 content]

## Understanding Your Challenge
[Step 3 — Problem section]

## Proposed Solution
[Step 3 — Solution section]

## Investment Summary
[Step 4 content]

## Implementation Timeline
[Step 5 content]

## Proven Results
[Step 6 content]

## Terms and Conditions
[Step 7 — Terms]

## Next Steps
[Step 7 — Next steps]

---

**[Your Company Name]** | [Contact Info] | [Website]

Quality Checklist

Before delivering the proposal, verify:

  • Prospect's company name is spelled correctly throughout
  • All stakeholder names and titles are accurate
  • Pricing adds up correctly (check the math)
  • No placeholder text remains (e.g., "[INSERT]", "TBD", "XXX")
  • Executive summary can stand alone without the rest of the document
  • At least one quantified ROI metric is included
  • Timeline is realistic for the scope described
  • Case studies are relevant to the prospect's industry or problem
  • No internal jargon that the buyer would not recognize
  • Next steps include a specific proposed date or action
  • Proposal has been proofread for grammar and formatting

Edge Cases

ScenarioHow to Handle
No pricing available yetUse a range ("$50K-$75K depending on configuration") and note that final pricing requires a scoping call
Multiple decision makers with different prioritiesAdd a "Benefits by Stakeholder" section mapping outcomes to each role
Prospect asked for a "quick quote" not a full proposalProduce a condensed 1-2 page version with pricing, scope summary, and next steps only
Competitive bake-off / RFP responseAdd a "Why Us" comparison table and strengthen the differentiators section
Renewal or upsell to existing customerReference current deployment, usage metrics, and success achieved so far
International or multi-currency dealShow pricing in the buyer's local currency and note exchange rate assumptions
Prospect has not completed discoveryFlag gaps in understanding and recommend a discovery session before finalizing
Skills guardadas