AI prompt for sales pitches

Create a sales pitch for the prospect below using only verified information and the details I provide. Do not invent a trigger event, business problem, metric, customer result, executive priority, or personal detail.

What I sell: [OFFER]
Prospect and account facts: [PROSPECT FACTS]
Likely problem or opportunity: [PROBLEM HYPOTHESIS]
Proof I can use: [PROOF]
Sales context: [SALES CONTEXT]
Desired next step: [DESIRED NEXT STEP]

First, assess the fit in two sentences. Separate confirmed account facts from the hypothesis, and say when the hypothesis is too weak for a direct claim.

Then produce:
1. Core pitch: 90–130 words for [SALES CONTEXT]. Open with a relevant observation or stated problem, connect it to one concrete business consequence, explain the specific mechanism of the offer, and end with the desired next step. Use plain language and one central outcome; do not list every feature.
2. Three opening lines: one for a cold email, one for a discovery call, and one for an in-person or video meeting. Each must be tailored to the supplied facts without pretending familiarity.
3. Discovery questions: five questions that test the problem hypothesis before pitching. Include questions about current process, cost of inaction, decision criteria, stakeholders, and timing.
4. Objection responses: concise responses to “we already have a solution,” “no budget,” and “send information.” Each response should acknowledge the objection, avoid pressure, and guide toward a relevant next action.
5. A 40-word CRM note that labels facts, hypothesis, and next action separately.

Before answering, check that every personalization point appears in my inputs and that the CTA is proportional to the evidence and sales stage. Flag claims that need legal, security, pricing, or product approval. Ask up to three clarifying questions only if a required input is missing.

Write a cold email to [CONTACT AND ROLE] at [COMPANY] for [OFFER]. Use only these verified facts: [ACCOUNT FACTS]. The possible problem is [HYPOTHESIS], which must be framed as a possibility, not a claim. Use this approved proof: [PROOF]. Write two subject lines and an email of 80–110 words with one clear CTA: [CTA]. Avoid flattery, feature lists, false familiarity, and unsupported urgency. Check each personalized statement against the supplied facts. Ask up to three questions only if a required input is missing.

Prepare a three-minute discovery-call opening for [OFFER] with [CONTACT AND ACCOUNT]. Known facts: [FACTS]. My hypothesis: [HYPOTHESIS]. Produce a 45-second opening, six sequenced questions that uncover current process, pain, impact, priorities, stakeholders, and timing, plus two transitions into a relevant product discussion. Do not assume the hypothesis is true or present product claims outside [APPROVED CLAIMS]. End with the next-step ask [CTA]. Check that questions are open enough to learn rather than lead. Ask up to three questions only if a required input is missing.

Draft a post-demo recap email to [BUYER] at [COMPANY] using [CALL NOTES]. We demonstrated [PRODUCT AREAS] and discussed [CONFIRMED NEEDS]. Produce a 150-word email with: their stated priorities, the capabilities shown that relate directly to those priorities, unanswered questions, agreed next steps and owners, and date only if supplied. Include [APPROVED PROOF] only if it matches the use case. Do not turn assumptions into commitments or promise implementation outcomes. Check each statement against the call notes. Ask up to three questions only if a required input is missing.