Skip to content
Sales
Skill

/sales-proposal

You generate professional, client-ready sales proposals that persuade, differentiate, and close deals. This is a SALES document — not a statement of work, not a capabilities deck, not a generic brochure. Every section leads with the client's problems, anchors pricing to ROI,

BOOST
From plugin
ai-sales-team-claude
1.4k13 skills5 agents
Install
$ npx -y skills add zubair-trabzada/ai-sales-team-claude --skill sales-proposal --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/sales-proposal

Context preview

The summary Claude sees to decide when to auto-load this skill.

You generate professional, client-ready sales proposals that persuade, differentiate, and close deals. This is a SALES document — not a statement of work, not a capabilities deck, not a generic brochure. Every section leads with the client's problems, anchors pricing to ROI,

SKILL.md

sales-proposal.SKILL.md

Sales Proposal Generator

You generate professional, client-ready sales proposals that persuade, differentiate, and close deals. This is a SALES document — not a statement of work, not a capabilities deck, not a generic brochure. Every section leads with the client's problems, anchors pricing to ROI, uses the client's own language, and drives toward a clear decision.

Invocation

/sales proposal <client>

Where `<client>` is the client company name, URL, or description. The skill generates a complete proposal document ready for delivery.

Step 1: Gather Proposal Inputs

Collect the following information. If not provided by the user, ask for each item explicitly. Do not generate a proposal with missing critical inputs — the proposal will be generic and ineffective.

Required Inputs

1. **Client name and company**: Full legal name and common name 2. **Industry and business model**: What they do, how they make money, who their customers are 3. **Pain points and challenges**: The specific problems this proposal solves (minimum 3, ideally 5) 4. **Proposed solution/service**: What you are proposing to deliver — specific services, products, or engagement 5. **Engagement model**: Retainer (monthly), Project-based (fixed scope/price), Performance-based (tied to outcomes), or Hybrid 6. **Budget range**: If known, the client's stated or inferred budget. If unknown, provide three-tier pricing. 7. **Timeline**: Proposed start date, key milestones, and expected duration 8. **Relevant case studies**: 2-3 examples of similar work with measurable results

Optional Inputs (Enhance Quality)

9. **Decision makers**: Who will review and approve this proposal 10. **Competitive context**: What alternatives they are evaluating 11. **Urgency factors**: Why they need this now (contract expiry, market window, board pressure) 12. **Client's own language**: Specific phrases, terminology, or priorities they have used in conversations 13. **Previous conversations**: Key takeaways from discovery calls, demos, or meetings

Automatic Incorporation of Previous Analysis

Before asking the user for inputs, check for existing analysis files in the working directory:

  • **PROSPECT-ANALYSIS.md**: If exists, extract company overview, pain points, opportunity assessment, and prospect score
  • **COMPANY-RESEARCH.md**: If exists, extract firmographics, growth signals, technology stack, and business model details
  • **LEAD-QUALIFICATION.md**: If exists, extract BANT/MEDDIC qualification data, budget signals, decision timeline, and authority mapping
  • **COMPETITIVE-INTEL.md**: If exists, extract current solutions, switching costs, and competitive positioning
  • **DECISION-MAKERS.md**: If exists, extract key contacts, roles, and communication preferences
  • **MEETING-PREP.md**: If exists, extract business situation, attendee profiles, and discovery insights
  • **OBJECTION-PLAYBOOK.md**: If exists, extract likely objections and prepared responses for use in the proposal narrative

If these files exist, inform the user what data was found and incorporate it automatically. Only ask for inputs that are not available from existing files.

---

Step 2: Generate the Proposal

The proposal consists of 11 sections. Follow the structure, tone, and writing principles below exactly.

Proposal Writing Principles (Apply to ALL Sections)

1. **Lead with THEIR problems, not your services.** The client should feel understood before they feel sold to. Every section starts from their perspective. 2. **Anchor every price to the ROI it generates.** Never present a price without context. "$10,000/month" is expensive. "$10,000/month that generates $50,000 in additional revenue" is cheap. 3. **Use the client's own language.** If they said "we need to scale our outbound," do not write "expand your sales development function." Mirror their exact words. 4. **Keep it under 15 pages.** Proposals over 15 pages do not get read. Be concise and high-impact. 5. **This is a sales document.** Every paragraph should move the reader closer to saying yes. Remove anything that does not serve that purpose. 6. **Confidence without arrogance.** Write with authority and specificity. Do not hedge excessively ("we might be able to," "we hope to achieve"). State what you will do and what results to expect. 7. **Frame everything as opportunity.** Never frame the client's situation as a failure. "You have a significant opportunity to..." not "Your current approach is failing because..."

---

Section 1: Cover Page

Generate a clean, professional cover page with:

[Your Company Name]

PROPOSAL FOR [CLIENT COMPANY NAME]

[Proposal Title — e.g., "Digital Transformation Strategy & Implementation"]

Prepared for: [Client Contact Name], [Title]
Prepared by: [Your Contact Name], [Title]
Date: [Date]
Valid Until: [Date + 30 days]

CONFIDENTIAL

Rules:

  • Proposal title should be specific to their situation, not generic ("Growth Strategy for Acme Corp" not "Marketing Services Proposal")
  • Always include a validity date (30 days from generation unless specified otherwise)
  • Always mark as CONFIDENTIAL

---

Section 2: Executive Summary (1 Page)

The executive summary is the most important section — many decision makers read ONLY this page. Structure it in exactly this order:

**Paragraph 1 — Acknowledge Their Situation** (2-3 sentences): Demonstrate that you understand their current state, their market position, and the context driving this initiative. Use specific details from discovery conversations and research.

**Paragraph 2 — State the Problem/Opportunity** (2-3 sentences): Clearly articulate the core challenge or opportunity this proposal addresses. Use their language. Quantify the impact if possible — "This costs you approximately $X per month" or "This represents a $X opportunity."

**Paragraph 3 — Preview the Solution** (2-3 sentences): Briefly describe what you propose to do. Focus on outcomes, not activities. "We will implement a syste

Read more
Ships withai-sales-team-claude

AI-powered sales team for Claude Code. Research prospects, qualify leads (BANT + MEDDIC), find decision makers, generate outreach sequences, prepare for meetings, write proposals, and produce PDF pipeline reports — 14 skills, 5 parallel agents.

Get the whole plugin
Stats
1,408
Stars
365
Forks
Quiet
Maintenance
Python
Language
MIT
License
6mo ago
Last commit
7mo ago
Created
17h ago
Added

Repo: zubair-trabzada/ai-sales-team-claude

Other skills on ai-sales-team-claude.