Sales Proposal

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 

Where `` 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)

1. Decision makers: Who will review and approve this proposal
2. Competitive context: What alternatives they are evaluating
3. Urgency factors: Why they need this now (contract expiry, market window, board pressure)
4. Client's own language: Specific phrases, terminology, or priorities they have used in conversations
5. 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 system that generates X" not "We will configure software and run campaigns."

Paragraph 4 — Hint at Outcomes (2-3 sentences): Share the expected results with conservative projections. Reference a comparable client result. "Based on results with [similar company], we project [specific outcome] within [timeframe]."

Paragraph 5 — Create Urgency (1-2 sentences): One factual reason to act now — market window, competitive pressure, cost of delay, seasonal opportunity. Never manufactured urgency.

Rules:

• The entire executive summary must fit on one page (approximately 250-350 words)
• No bullet points in the executive summary — it should read as a compelling narrative
• Every sentence must earn its place — remove any filler

---

Section 3: Situation Analysis (1-2 Pages)

Demonstrate deep understanding of the client's current state. This section proves you have done your homework and builds trust.

3.1 Current State: Describe their current situation in 2-3 paragraphs. Include:

• How they currently handle [the area your solution addresses]
• What tools, processes, and resources they currently use
• What is working and what is not (framed diplomatically)
• Quantified impact of the current approach (costs, time, efficiency, missed opportunities)

3.2 Opportunities Identified: List 3-5 specific opportunities you have identified through discovery and research. For each:

• The opportunity (one sentence)
• Why it exists (what is causing it)
• The estimated impact of addressing it (quantified if possible)

3.3 Competitive Context (if applicable): Brief overview of the competitive landscape and where the client stands relative to peers. Frame as: "Companies in your space that [take action X] are seeing [results Y]."

3.4 Key Challenges: List 2-3 challenges that must be addressed for the engagement to succeed. This demonstrates realism and builds trust — a proposal that claims everything will be easy is not believable.

Rules:

• Frame challenges as opportunities, never as failures
• Reference specific data points, conversations, or research (e.g., "As you mentioned in our call on [date]...")
• If COMPANY-RESEARCH.md or PROSPECT-ANALYSIS.md exists, pull specific data from those files

---

Section 4: Proposed Solution (2-3 Pages)

This is the core of the proposal — what you will do and how. Structure it as a phased approach.

4.1 Strategic Framework: Open with a brief description (3-5 sentences) of your overall approach and methodology. Explain WHY this approach works, not just what it is.

4.2 Phased Approach:

Structure the engagement in three phases. Use aspirational phase names, not generic ones ("Foundation" not "Phase 1").

Phase 1: [Foundation / Discovery / Blueprint] (Weeks 1-X)

• Objective: [What this phase achieves]
• Key activities:
• [Activity 1] — [Specific deliverable]
• [Activity 2] — [Specific deliverable]
• [Activity 3] — [Specific deliverable]
• Milestone: [How you know this phase is complete]
• Client involvement: [What they need to do]

Phase 2: [Build / Growth / Activation] (Weeks X-Y)

• Objective: [What this phase achieves]
• Key activities:
• [Activity 1] — [Specific deliverable]
• [Activity 2] — [Specific deliverable]
• [Activity 3] — [Specific deliverable]
• [Activity 4] — [Specific deliverable]
• Milestone: [How you know this phase is complete]
• Client involvement: [What they need to do]

Phase 3: [Scale / Optimize / Accelerate] (Weeks Y-Z)

• Objective: [What this phase achieves]
• Key activities:
• [Activity 1] — [Specific deliverable]
• [Activity 2] — [Specific deliverable]
• [Activity 3] — [Specific deliverable]
• Milestone: [How you know this phase is complete]
• Ongoing: [What continues after this phase]

Rules:

• Activities must be specific and measurable — "Implement automated email sequences targeting 3 buyer personas" not "Set up email marketing"
• Each phase should build on the previous one — show progression
• Client involvement requirements set realistic expectations upfront

---

Section 5: Scope of Work (1-2 Pages)

Define exactly what is included and what is not. This protects both parties and sets clear expectations.

5.1 Deliverables: List every specific deliverable with quantities where applicable:

• [Deliverable 1] — [quantity/frequency]
• [Deliverable 2] — [quantity/frequency]
• [Deliverable 3] — [quantity/frequency]
• Continue for all deliverables

5.2 Meeting Cadence:

• Kickoff meeting: [Format and duration]
• Weekly/bi-weekly status meetings: [Format and duration]
• Monthly/quarterly reviews: [Format and duration]
• Ad-hoc communication: [Channel and expected response time]

5.3 Response Times:

• Email inquiries: [SLA, e.g., "within 4 business hours"]
• Urgent requests: [SLA, e.g., "within 2 hours during business hours"]
• Report delivery: [SLA, e.g., "by end of day Friday weekly"]

5.4 Tools and Technology Included:

• [Tool 1] — [What it is used for]
• [Tool 2] — [What it is used for]
• Note: List only tools YOU provide. Do not list tools the client needs to provide.

5.5 Explicit Exclusions: Clearly state what is NOT included to prevent scope creep:

• [Exclusion 1] — [Why it is excluded and how to add it if needed]
• [Exclusion 2] — [Why and how to add]
• [Exclusion 3] — [Why and how to add]

5.6 Client Responsibilities: What the client must provide for the engagement to succeed:

• [Responsibility 1] — [Timeline for delivery]
• [Responsibility 2] — [Timeline]
• [Responsibility 3] — [Timeline]

Rules:

• Be exhaustive with deliverables — ambiguity creates conflict later
• Exclusions are as important as inclusions — list at least 3
• Client responsibilities set expectations early and prevent blame if results lag

---

Section 6: Timeline (1 Page)

Create a visual timeline showing phases, milestones, and key dates.

### Project Timeline

| Week | Phase | Key Activities | Milestone |
|------|-------|---------------|-----------|
| 1 | Foundation | [Activities] | [Milestone] |
| 2 | Foundation | [Activities] | |
| 3 | Foundation | [Activities] | [Phase 1 Complete] |
| 4 | Growth | [Activities] | |
| ... | ... | ... | ... |

### Key Dates

| Date | Event |
|------|-------|
| [Date] | Project kickoff |
| [Date] | Phase 1 complete — [Deliverable] |
| [Date] | Phase 2 complete — [Deliverable] |
| [Date] | Phase 3 complete — [Deliverable] |
| [Date] | First results review |

Rules:

• Include buffer time — unrealistic timelines destroy trust
• Mark key decision points where the client needs to approve or provide input
• If the client is on a deadline, work backward from their target date

---

Section 7: Investment (1-2 Pages)

Present pricing using a three-tier model (Good-Better-Best) with pricing psychology built in.

Pricing Psychology Rules:

• Name tiers aspirationally, not as "Basic-Standard-Premium." Use names that reflect outcomes: "Growth," "Accelerate," "Transform" or "Starter," "Professional," "Enterprise."
• The highest tier is the anchor — it makes the middle tier look reasonable by comparison.
• Mark the middle tier as "RECOMMENDED" or "MOST POPULAR" — this is where you want them.
• Show ROI math for each tier — the price is meaningless without context.
• If the client stated a budget, the middle tier should align with it.

### Investment Options

| | [Tier 1: Starter Name] | [Tier 2: Recommended Name] ★ | [Tier 3: Premium Name] |
|---|---|---|---|
| **Monthly Investment** | $[Price] | $[Price] | $[Price] |
| **Annual Investment** | $[Price] (save X%) | $[Price] (save X%) | $[Price] (save X%) |
| [Feature/Service 1] | [What's included] | [What's included] | [What's included] |
| [Feature/Service 2] | [Limited/Not included] | [Included] | [Included + extra] |
| [Feature/Service 3] | [Not included] | [Included] | [Included + extra] |
| [Feature/Service 4] | [Not included] | [Not included] | [Included] |
| **Expected ROI** | [X]x return | [X]x return | [X]x return |
| **Best For** | [Description] | [Description] | [Description] |

★ Recommended based on your goals and budget

ROI Justification (include for each tier):

[Tier Name] ROI Math:
- Monthly investment: $[Price]
- Expected monthly return: $[Projected value] (based on [assumption])
- Breakeven: [Month X]
- 12-month ROI: [X]% ([Dollar amount] return on [Dollar amount] investment)

Rules:

• Never present price without ROI context
• Include both monthly and annual pricing (with annual discount) if applicable
• The "Best For" row helps the client self-select the right tier
• If budget is known, ensure the recommended tier falls within or slightly above their range

---

Section 8: ROI Projection

Provide a detailed ROI projection that builds confidence in the investment decision.

### Current State vs. Projected State

| Metric | Current State | Projected (Conservative) | Projected (Moderate) | Projected (Aggressive) |
|--------|-------------|------------------------|---------------------|----------------------|
| [Metric 1] | [Current value] | [Conservative] | [Moderate] | [Aggressive] |
| [Metric 2] | [Current value] | [Conservative] | [Moderate] | [Aggressive] |
| [Metric 3] | [Current value] | [Conservative] | [Moderate] | [Aggressive] |
| [Revenue/Cost metric] | [Current] | [Conservative] | [Moderate] | [Aggressive] |

### ROI Calculation

| Scenario | Annual Value Created | Annual Investment | Net ROI | ROI % |
|----------|---------------------|-------------------|---------|-------|
| Conservative | $[Amount] | $[Amount] | $[Amount] | [X]% |
| Moderate | $[Amount] | $[Amount] | $[Amount] | [X]% |
| Aggressive | $[Amount] | $[Amount] | $[Amount] | [X]% |

### Assumptions
- [Assumption 1] — [Basis for this assumption]
- [Assumption 2] — [Basis]
- [Assumption 3] — [Basis]

Rules:

• Always show three scenarios (conservative, moderate, aggressive) — presenting only the best case feels dishonest
• Clearly state assumptions so the client can evaluate the projections
• Base projections on real d

…

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: zubair-trabzada
• Source: zubair-trabzada/ai-sales-team-claude
• License: MIT
• Homepage: https://www.skool.com/aiworkshop

Install and usage instructions live in the source repository linked above.