Skill

proposal-generator

Orchestrate proposal creation by gathering deal context, validating inputs, invoking proposal-writer skill, and ensuring quality output.

From majestic-sales
Install
1
Run in your terminal
$
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-sales
Tool Access

This skill is limited to using the following tools:

Read Write Edit Grep Glob WebSearch WebFetch
Skill Content

Proposal Generator

Guide proposal creation by gathering context, validating inputs, applying the proposal-writer skill, validating output quality, and recommending delivery.

Step 1: Gather Context

Collect deal information:

  1. Prospect: Company name, industry, size
  2. Stakeholders: Who will read this? (Titles and their concerns)
  3. Discovery findings: What problems did they share? What's the business impact?
  4. Solution: What are you proposing? (Products, services, scope)
  5. Pricing: What's the investment? (Or range if flexible)
  6. Competition: Are they evaluating alternatives?
  7. Timeline: When do they need to decide? When to implement?
  8. Objections: Any concerns raised during sales process?

Step 2: Validate Inputs

Before proceeding, verify:

Required InputValidation
Prospect infoCompany name + industry present
StakeholdersAt least 1 decision-maker identified
Discovery findingsSpecific pain points, not generic
SolutionClear scope of what's proposed
PricingNumber or range provided

If missing: Ask follow-up questions. Do not proceed with incomplete context.

Step 3: Analyze Deal

FactorAnalysisImpact
Deal Size<$10K / $10-50K / $50K+Determines proposal length
Stakeholder CountSingle / MultipleDetermines sections needed
CompetitionNone / ActiveDetermines differentiation emphasis
Objection HistoryList concerns raisedMust address proactively
Timeline PressureUrgent / StandardAffects urgency framing

Step 4: Apply Proposal Writer Skill

Apply proposal-writer with structured context:

context:
  prospect: [company, industry, size]
  deal_size: [<$10K | $10-50K | $50K+]
  stakeholders: [list with concerns]
  pain_points: [from discovery]
  solution: [what we're proposing]
  pricing: [amount or options]
  competition: [who, their weakness]
  objections_to_address: [list]
  timeline: [decision date, implementation date]

Step 5: Validate Output

Must Pass

  • Executive summary can stand alone (decision-maker reads only this)
  • Pain points use prospect's words from discovery
  • Outcomes are measurable (numbers, percentages, timeframes)
  • Pricing presented strategically (options, anchoring)
  • Each stakeholder's concern addressed somewhere
  • Clear next steps with dates and owners
  • Proposal length matches deal size
  • No generic or boilerplate language
  • Valid until date creates appropriate urgency

Red Flags (Fix Before Delivery)

IssueProblemFix
Leads with company historyThey stop readingLead with their pain
Generic scope languageFeels like templateReference specific discovery
Pricing buried at endSeems evasivePut in exec summary
No clear next stepsDeal stallsAdd action table with dates
Missing ROI justificationPrice feels highAdd payback calculation

Step 6: Recommend Delivery

Deal SizeFormatDelivery Method
<$10KPDFEmail with brief note
$10K-$50KPDFScreen share walkthrough
>$50KPDF + DeckIn-person or video presentation

Always recommend: "Walk them through it rather than just sending. Control the narrative."

Handling Edge Cases

SituationAction
Missing discovery contextAsk: "What did they say was their biggest challenge?"
No clear pricingAsk: "What's your target price point or range?"
Unknown stakeholdersAsk: "Who else will be involved in the decision?"
Output too genericRe-apply skill with more specific pain points
Proposal too longRequest condensed version for deal size

Deliverables

  1. Complete proposal (markdown or requested format)
  2. Delivery recommendation
  3. Suggested talk track for walkthrough
  4. Follow-up timing recommendation
Stats
Parent Repo Stars31
Parent Repo Forks6
Last CommitMar 15, 2026