Proposals & SOWs in Minutes

I'm setting up a Claude Project for generating sales proposals. Here's my company's proposal context. Please confirm you understand each section and flag anything that's missing.\n\nCOMPANY OVERVIEW:\n[2-3 paragraphs about what your company does, key differentiators, and market position]\n\nPRICING TIERS:\n[Your pricing structure — tiers, per-seat costs, implementation fees, etc.]\n\nSTANDARD TERMS:\n- Payment terms: [e.g., Net 30]\n- Contract length: [e.g., 12 months]\n- Implementation timeline: [e.g., 4-6 weeks]\n- Support included: [e.g., dedicated CSM for Enterprise]\n- SLA: [e.g., 99.9% uptime]\n\nCASE STUDIES (summarize 3-5):\n[For each: Company name, industry, challenge, solution, results with specific numbers]\n\nCOMMON OBJECTIONS AND RESPONSES:\n[Top 5 objections you hear and how you handle them]\n\nPROPOSAL TEMPLATE STRUCTURE:\n1. Executive Summary\n2. Understanding of Needs\n3. Proposed Solution\n4. Implementation Plan\n5. Investment & Terms\n6. Case Studies\n7. Next Steps

Generate a proposal for this deal using our standard template and pricing.\n\nPROSPECT:\n- Company: [company name]\n- Contact: [name, title]\n- Industry: [industry]\n- Company size: [employees, revenue if known]\n\nDEAL CONTEXT:\n- Their pain points: [what they told us they're struggling with]\n- Requirements: [specific features or capabilities they need]\n- Current solution: [what they use today and why they're looking to switch]\n- Budget signals: [anything they've said about budget or pricing expectations]\n- Timeline: [when they want to implement]\n- Decision process: [who else is involved, what approvals are needed]\n- Competition: [other vendors they're evaluating, if known]\n\nOUR RECOMMENDED SOLUTION:\n- Tier/package: [which pricing tier fits]\n- Add-ons: [any additional services needed]\n- Custom elements: [anything non-standard for this deal]\n\nSPECIAL INSTRUCTIONS:\n- [Any deal-specific requirements, e.g., 'They emphasized ROI metrics — include an ROI section' or 'The CFO will read this — lead with financial impact']\n\nGenerate a complete proposal following our template. Make the executive summary compelling and specific to their situation. Use concrete numbers where possible. Match the case studies to their industry.

Here's the transcript from our sales call with [company]. Extract everything relevant to writing a proposal, then generate a complete first draft.\n\nTRANSCRIPT:\n[Paste the full call transcript here]\n\nAfter reading the transcript:\n1. First, list the key proposal inputs you extracted: pain points, requirements, budget signals, timeline, decision makers, competitors mentioned\n2. Flag anything that's unclear or that I should clarify before sending the proposal\n3. Then generate the full proposal using our standard template\n4. Include a recommended pricing tier based on what you heard about their needs and budget\n5. Draft the cover email I should send with the proposal attached

Generate a detailed Statement of Work based on this deal.\n\nCLIENT: [company name]\nCONTACT: [name, title]\nPROJECT: [project name or description]\n\nSCOPE:\n- What we're delivering: [list deliverables]\n- What's explicitly out of scope: [list exclusions]\n\nPHASES AND TIMELINE:\n[Describe each phase, even roughly — Claude will structure it]\n\nTEAM:\n- Our side: [who's involved and their roles]\n- Their side: [what we need from them — access, approvals, SMEs]\n\nPRICING:\n- Total project value: [amount]\n- Payment structure: [milestone-based, monthly, upfront, etc.]\n- Expense policy: [any pass-through costs]\n\nASSUMPTIONS:\n[List any assumptions you're making — number of revisions, response times, access to systems, etc.]\n\nGenerate a professional SOW with these sections:\n1. Project Overview\n2. Scope of Work (with explicit inclusions and exclusions)\n3. Deliverables (with acceptance criteria for each)\n4. Timeline & Milestones\n5. Team & Responsibilities (RACI-style)\n6. Investment & Payment Schedule\n7. Assumptions & Dependencies\n8. Change Order Process\n9. Term & Termination\n\nMake the deliverables specific and measurable. Include acceptance criteria so there's no ambiguity about what 'done' looks like.

I need to present 3 pricing options for [company]. Create a Good / Better / Best comparison that makes the middle option the obvious choice.\n\nTheir needs: [summary of what they need]\nOur pricing: [your pricing tiers]\nDeal context: [budget signals, who's approving, what matters most]\n\nFor each option:\n1. Give it a name that describes the outcome, not the tier (e.g., 'Foundation' not 'Basic')\n2. List what's included\n3. Price and payment terms\n4. Best for: who should pick this option\n5. Trade-offs: what they give up compared to the next tier up\n\nMake the middle option the clear winner by loading it with the features they specifically asked about. The top tier should include things they'd want but haven't asked for yet — plant the expansion seed.

The prospect is currently using [competitor] and considering switching to us. Generate a proposal that addresses the switch directly.\n\nCurrent vendor: [competitor name and what they use it for]\nWhy they're looking to switch: [their stated reasons]\nSwitching concerns: [what they're worried about — migration, training, downtime, etc.]\n\nIn addition to our standard proposal sections, include:\n1. A 'Why Switch Now' section that validates their decision to evaluate alternatives\n2. A migration plan section with specific steps and timeline\n3. A risk mitigation section addressing their switching concerns\n4. A total cost of ownership comparison (don't trash the competitor — focus on value gaps)\n5. A 'First 30 Days' section showing exactly what happens after they sign\n\nTone: confident but not arrogant. We're here to solve their problem, not bash the competition.

Review this proposal draft and evaluate it against these criteria. Be critical — I'd rather fix issues now than lose the deal.\n\n[Paste your proposal draft here]\n\nEvaluate:\n1. SPECIFICITY: Does it reference their specific situation, or could this proposal be sent to anyone? Flag every generic sentence.\n2. VALUE FRAMING: Does each section connect features to business outcomes? Or are we just listing capabilities?\n3. RISK REDUCTION: Have we addressed their likely concerns about switching, implementation, and ROI?\n4. EXECUTIVE READABILITY: Could a busy executive scan this in 3 minutes and understand the value? Is the executive summary actually compelling?\n5. COMPETITIVE POSITIONING: If they're comparing us to alternatives, does this proposal make the comparison easy to win?\n6. NEXT STEPS: Is there a clear, low-friction next step? Or does it just end?\n7. PRICING PRESENTATION: Is the pricing easy to understand? Are there any surprise costs that could create friction?\n\nFor each issue you find, suggest a specific fix with replacement language.

Draft a cover email to deliver this proposal to [name] at [company].\n\nContext:\n- What we discussed on our last call: [key points]\n- The main thing they care about: [their primary driver]\n- The next step we agreed on: [what should happen after they review]\n- Anyone else who needs to see this: [other stakeholders]\n\nThe email should:\n1. Be under 150 words\n2. Open with a reference to our conversation (not 'As discussed' — something specific)\n3. Frame the proposal around the outcome they want, not the document itself\n4. Include one specific number or result from a relevant case study\n5. End with a concrete next step and a specific suggested time\n6. If other stakeholders need to review, make it easy for [name] to forward — include a one-line summary they can paste