proposal-writer
$
npx mdskill add mohitagw15856/pm-claude-skills/proposal-writerWrites commercial proposals that win business — structured around the prospect problem, not the product.
SKILL.md
.github/skills/proposal-writerView on GitHub ↗
--- name: proposal-writer description: "Write a structured sales proposal or commercial proposal for any deal. Use when asked to write a proposal, sales proposal, commercial proposal, statement of work, or quote document. Produces a complete proposal with problem statement, solution, investment, and next steps." --- # Proposal Writer Skill Writes commercial proposals that win business — structured around the prospect problem, not the product. ## Required Inputs - **Prospect company and contact** - **Their problem or goal** (from discovery — be specific) - **Your proposed solution** - **Commercial terms** (pricing, payment terms, contract length) - **Timeline** - **Key stakeholders** who will read this - **Tone** (formal / conversational / technical) ## Output Structure --- # Proposal: [Brief description of what you are solving] **Prepared for:** [Contact, Title] | [Company] **Prepared by:** [Name] | [Your Company] **Date:** [Date] | **Valid until:** [Date] --- ### Understanding Your Situation [2-3 paragraphs. Demonstrate you listened. Describe their situation, problem, and impact of not solving it in their words. This section should make them think "yes, exactly." Generic boilerplate here = proposal goes in the bin.] **The key challenge:** [One sentence — the core problem] **The impact:** [What this costs them] **What you have tried:** [Acknowledge prior attempts] --- ### Our Proposed Approach **What we will do** (3-5 deliverables or phases) **Phase 1: [Name]** (Timeline: [Weeks 1-2]) [What happens, what is delivered, what customer input is needed] **Phase 2: [Name]** (Timeline: [Weeks 3-6]) **What you will get** (outcomes, not features) - [Outcome 1] - [Outcome 2] **What success looks like** [How both parties know this worked] --- ### Why [Your Company] [3-4 sentences. Specific to their situation. Reference similar customers. Generic "why us" sections are skipped.] --- ### Investment | Item | Description | Investment | |---|---|---| | [Component 1] | [Description] | £[amount] | | **Total** | | **£[total]** | **Payment terms:** [Terms] **Included:** [What is in] **Not included:** [What is out — prevents scope disputes] --- ### Timeline | Milestone | Date | |---|---| | Contract signed | [Date] | | Kickoff | [Date] | | Delivery | [Date] | --- ### Next Steps 1. [Sign / reply / schedule] by [date] 2. We will send contract and confirm kickoff 3. [Any immediate action] ## Quality Checks - [ ] "Understanding Your Situation" reflects what was learned in discovery (not generic) - [ ] Outcomes are listed (not just deliverables or features) - [ ] "Not included" section is explicit to prevent scope disputes later - [ ] Next steps include a specific date and named action - [ ] "Valid until" date is included to create urgency ## Example Trigger Phrases - "Write a proposal for [prospect] to [solve their problem]" - "Draft a statement of work for [project]" - "Turn my discovery notes into a proposal"
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
- ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
- accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
- account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
- aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.