sales-script
Sales Script
When to Use
- Preparing for a discovery call, product demo, or closing meeting
- Responding to an RFP/RFI and need coverage gap analysis
- Building a competitive feature comparison matrix against rivals
- Planning or scoring a proof-of-concept (POC) engagement
- Preparing a technical demo script with stakeholder-specific talking points
- Handling objections or conducting win/loss analysis
Context Required
From startup-context or the user:
- Product/service — What you sell, who it is for, key capabilities
- Target persona — Role, seniority, typical pain points
- Deal context — Stage, deal size, stakeholders involved, known objections
- Competitive landscape — Who else they are evaluating, your differentiators
- Proof points — Metrics, case studies, customer quotes
- RFP/RFI details — If responding to a formal request, the requirement categories and priorities
More from shawnpang/startup-founder-skills
terms-of-service
When the user needs to draft, review, or update terms of service for their SaaS product or web application.
65pitch-deck
When the user wants to create, review, or restructure a fundraising pitch deck for seed or Series A. Also activates when the user mentions "deck", "pitch", "investor presentation", or "slide structure".
55competitive-analysis
When the user needs to evaluate competitors, understand the competitive landscape, or position their product against alternatives.
53review-mining
When the user wants to research customer pain points, complaints, or sentiment using review platforms like Trustpilot, G2, Capterra, or app stores. Also use when the user mentions "what are users saying", "competitor reviews", "pain points", or "voice of customer research".
53data-room
When the user wants to prepare a due diligence data room for fundraising, or when an investor has requested additional materials after a pitch. Also activates for "data room", "due diligence", "DD checklist", or "what documents do investors need?".
51prd-writing
When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec.
49