Resource
50 prompts for tech and cybersecurity sellers (GPT and Claude)
ASTRA Ready editorial ·
Who this sheet is for
This resource is for salespeople, pre-sales professionals, channel teams and customer-success staff who use AI to prepare for customer conversations, organise deal evidence or draft clearer follow-up. Every prompt is evidence-bound: you paste the material, the AI works only from it, and the output must expose what the material does not establish.
The prompts are intentionally usable in both GPT and Claude. They do not ask either model to research a customer, product, vendor or law from memory.
What the AI can and cannot do for you
AI can organise messy notes, compare documents, rewrite technical material, surface contradictions, draft customer language and turn evidence into a clearer decision record. Used well, it saves preparation time and makes reasoning easier to inspect.
It cannot verify whether pasted material is true, current or complete. It cannot turn a supplier statement into independent proof, confirm a security control, determine legal obligations, or know what happened in a customer environment unless your evidence shows it. A polished answer is still only a draft.
Treat AI as a structured writing and reasoning assistant, not as customer evidence. Before anything goes to a buyer, trace every factual statement back to the pasted source, preserve qualifications and exclusions, confirm owners and dates, and ask the responsible specialist when evidence is incomplete. Nothing AI writes becomes evidence merely because it sounds confident to a customer.
Relevant ASTRA Ready programmes: Explore the ASTRA Tech Sales Associate programme, ASTRA Tech Sales Advisor programme and ASTRA Cybersecurity Sales Specialist programme at https://www.astraready.com/programmes/
Using the same prompts in GPT and Claude
Model-use note — based on my general model-behaviour knowledge, not vendor documentation or a sourced product comparison. The fifty prompts below are deliberately model-neutral. Paste the same evidence and instruction into either GPT or Claude; the evidence boundary matters more than changing the prompt for the model.
Three small phrasing adjustments can help if an answer drifts. First, both models respond well to an explicit evidence boundary, but if a long source pack produces unsupported filling-in, repeat the sentence “work only from the pasted material” immediately before the task. Second, structured outputs can be reinforced differently without changing the task: a numbered output schema or exact table columns are a useful restatement in GPT, while clearly delimited evidence blocks such as <evidence>...</evidence> can be a useful restatement in Claude. Both approaches are optional formatting aids, not different reasoning rules. Third, if either model starts writing before you have pasted all the evidence, tell it that the source pack is incomplete and not to analyse until you write END OF MATERIAL.
Do not assume one model has verified what the other has not. In both, re-check the final customer wording against the original material.
How to use the sheet
- Choose the prompt that matches the job you are doing.
- Paste only material you are authorised to use.
- Replace
[PASTE HERE]with the evidence. - Keep the instruction that limits the AI to the pasted material.
- Check the output against the original source before it reaches a customer.
1. Discovery and buyer mapping
1. Build a buyer decision map
When to use it: After a discovery call when you need to see who owns which decision.
Prompt — ready to paste
I will paste my call notes below. Work only from those notes. Do not add likely stakeholders, processes or requirements from your own knowledge. Create a buyer decision map with these columns: decision to be made, named owner or participant, evidence from my notes, unresolved question, and next seller action. Separate confirmed ownership from guessed or unclear ownership. If two people appear to own the same decision, flag the conflict instead of resolving it yourself. PASTED CALL NOTES: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that every named owner and decision can be traced to the notes; remove any role or responsibility the AI inferred.
2. Find the real buying group from an email thread
When to use it: When several people are copied into a thread and you need to distinguish participation from authority.
Prompt — ready to paste
I will paste an email thread. Use only the thread. Do not infer job authority from titles alone and do not add people who are not named. Identify each person mentioned and classify what the thread actually shows them doing: requesting information, evaluating, approving, influencing, coordinating, contracting, operating or unknown. Quote or paraphrase the evidence for each classification. Highlight where a title sounds senior but the thread does not prove decision authority. PASTED EMAIL THREAD: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Verify that the AI has not converted seniority, copying on email or meeting attendance into approval authority.
3. Turn discovery notes into unanswered questions
When to use it: When a conversation felt productive but you are unsure what still needs to be learned.
Prompt — ready to paste
I will paste discovery notes. Work only from them and do not answer missing questions yourself. Group the unresolved issues under: business outcome, current process, technical environment, security or assurance, commercial process, stakeholders, timing and acceptance criteria. For each issue, write one neutral follow-up question and explain which customer decision that answer would change. Do not ask for information already present in the notes. PASTED DISCOVERY NOTES: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Remove any question whose answer is already in the notes and any question that assumes the customer has a problem not evidenced there.
4. Create an evidence-based qualification brief
When to use it: When you need an internal qualification summary without filling gaps with sales assumptions.
Prompt — ready to paste
I will paste notes, emails and any qualification fields I already have. Use only that material. Create a brief with: confirmed need, confirmed stakeholder interest, confirmed timing, confirmed process step, confirmed technical or security dependency, open risks, and the next evidence needed. Label each statement as Confirmed, Suggested by the material, or Unknown. Do not turn enthusiasm, meeting attendance or a requested demo into proof of budget or purchase intent. PASTED MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that budget, authority, urgency and intent are marked unknown unless the pasted evidence states them.
5. Spot stakeholder contradictions
When to use it: When different buyers have given different versions of the requirement or approval path.
Prompt — ready to paste
I will paste notes or messages from multiple stakeholders. Use only those records. Create a contradiction table with: topic, statement from stakeholder one, statement from stakeholder two, whether the statements truly conflict, and the clarification question to ask. Keep differences in preference separate from factual contradictions. Do not choose which stakeholder is right unless the pasted evidence establishes it. PASTED STAKEHOLDER MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Confirm that each reported contradiction is visible in the source and that the AI has not treated normal differences in emphasis as conflict.
6. Design the next discovery meeting
When to use it: When you have evidence from a first meeting and need a focused second conversation.
Prompt — ready to paste
I will paste the first meeting notes and any follow-up emails. Use only that material. Build a meeting plan with a short objective, no more than five priority questions, the named person best placed to answer each question if the evidence shows one, and the decision each answer should unlock. Include one section for topics that should not be reopened because the material already resolved them. PASTED MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that every agenda item advances an unresolved decision rather than repeating general discovery.
7. Separate the stated problem from the desired outcome
When to use it: When customer language mixes symptoms, requirements and proposed solutions.
Prompt — ready to paste
I will paste customer notes or an email. Work only from that text. Separate the material into: observed problem, business consequence stated by the customer, desired outcome, proposed solution language, constraints, and unknowns. If the customer has jumped straight to a solution, show which underlying outcome is stated and which is still unclear. Do not invent causes or benefits. PASTED CUSTOMER MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Make sure causes, business impact and desired outcomes are not upgraded from assumptions to facts.
8. Map approval gates before a proposal
When to use it: When a deal has technical, security, procurement or governance steps but the sequence is unclear.
Prompt — ready to paste
I will paste the account notes, process notes or customer emails. Use only those materials. Build an approval-gate map in the order supported by the evidence. For each gate, show the decision, named owner if stated, prerequisite evidence, dependency on another gate, and current status. If the sequence is not explicit, say that rather than inventing one. PASTED MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that sequence and ownership come from the pasted process, not from a generic enterprise-sales template.
9. Create a mutual-next-step map from agreed actions
When to use it: When you need a clean record of what each side actually agreed to do.
Prompt — ready to paste
I will paste meeting notes and follow-up messages. Work only from them. Extract only explicit commitments. Create a table with action, owner, stated timing, dependency, evidence that it was agreed, and status if known. Put tentative ideas in a separate section called Discussed but not committed. Do not assign dates, owners or obligations that were not stated. PASTED MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Compare each action with the source and remove anything that was merely suggested rather than agreed.
10. Prepare a discovery handoff
When to use it: When one seller is passing an opportunity to another without losing evidence or overstating qualification.
Prompt — ready to paste
I will paste the source seller's notes, emails and meeting recap. Use only that material. Write an internal handoff with: customer context, confirmed outcome, people involved, decisions already made, evidence gathered, unresolved questions, commitments already made, risks, and the next recommended conversation. Mark any uncertain point as uncertain. Do not convert a seller opinion into a customer fact. PASTED HANDOFF MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check the handoff against the source so the next seller can tell customer facts from internal interpretation.
2. Turning technical material into customer language
11. Translate a datasheet into customer language
When to use it: When a datasheet is accurate but too technical for a business conversation.
Prompt — ready to paste
I will paste a technical datasheet or product note. Use only the pasted material. Rewrite it as a customer-facing explanation with four sections: what it does, what has to be in place, what the material proves, and what the material does not say. Preserve limitations and conditions. Explain technical terms in plain English without introducing new capabilities or outcomes. PASTED TECHNICAL MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Compare each customer-facing claim with the datasheet and remove any benefit or capability that is not explicitly supported.
12. Explain an architecture note without overselling it
When to use it: When a customer needs the commercial meaning of an architecture diagram or design note.
Prompt — ready to paste
I will paste an architecture description or notes taken from a technical diagram. Work only from that material. Explain the flow in plain English: what starts the process, which components participate, what crosses a boundary, where human or system approval occurs, and where the flow ends. Then state the customer consequence of each boundary only when the source supports it. Do not infer performance, resilience or security from architecture alone. PASTED ARCHITECTURE MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that the explanation describes architecture facts rather than turning design elements into unproven outcome claims.
13. Turn an API note into a seller brief
When to use it: When you need to discuss an integration without pretending an interface document proves deployment success.
Prompt — ready to paste
I will paste API documentation, interface notes or a technical summary. Use only what I provide. Create a seller brief covering: intended interaction, required inputs, returned outputs, authentication or permission statements if present, limits or error behaviour if present, dependencies, and what still needs testing in the customer's environment. Distinguish documented capability from tested customer behaviour. PASTED INTERFACE MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Make sure documentation is not described as proof that the customer's integration already works.
14. Turn a security feature into a bounded value statement
When to use it: When a feature sounds impressive but you need language that survives buyer scrutiny.
Prompt — ready to paste
I will paste the feature description and any supporting technical evidence. Work only from those materials. Write three versions: a one-sentence plain-English explanation, a customer-value statement, and a careful proof statement. Keep the proof statement limited to what the evidence demonstrates. Do not claim that a feature by itself achieves a broader security outcome unless the pasted material explicitly establishes that relationship. PASTED FEATURE AND EVIDENCE: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that the value statement does not quietly become a compliance, risk-reduction or control-effectiveness claim without evidence.
15. Explain a technical limitation constructively
When to use it: When you need to tell a customer what is not supported without sounding evasive.
Prompt — ready to paste
I will paste the technical limitation, support note or engineering response. Use only the pasted text. Draft a customer explanation that states the limitation directly, explains the practical consequence supported by the material, identifies any documented workaround, and states what decision or test remains. Do not invent a workaround or minimise the limitation. Keep the tone calm and useful. PASTED TECHNICAL MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Confirm that the workaround, consequence and next step all exist in the source rather than being generated to soften the message.
16. Summarise logs for a customer conversation
When to use it: When technical logs need to become an understandable incident or test summary.
Prompt — ready to paste
I will paste selected logs plus any engineer notes that explain them. Work only from those records. Summarise what happened in chronological order, what the records directly show, what the engineer notes interpret, and what remains uncertain. Keep observed events separate from inferred cause. Do not diagnose a root cause unless the pasted material explicitly does so. PASTED LOGS AND NOTES: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Verify timestamps, event order and causes against the source; remove any root-cause statement not explicitly supported.
17. Compare deployment options from supplied documentation
When to use it: When a buyer is choosing between deployment models and you need a neutral comparison.
Prompt — ready to paste
I will paste documentation for two or more deployment options. Use only those documents. Create a comparison covering operating ownership, customer prerequisites, data or traffic flow, administration, stated limitations, support boundary and migration implications where documented. Use 'not stated' instead of guessing. End with the decisions the customer still needs to make, not a recommendation unless the evidence includes decision criteria. PASTED DEPLOYMENT MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that the comparison has not imported generic advantages or disadvantages of deployment models.
18. Explain a data flow in business terms
When to use it: When a technical data-flow description needs to be understandable to sales, procurement or governance stakeholders.
Prompt — ready to paste
I will paste a data-flow description, diagram notes or implementation summary. Work only from that material. Describe what data enters, where it goes, what processing is stated, where it is stored if stated, who or what can act on it if stated, and how it leaves or is deleted if stated. Then create a short list of customer questions for any missing lifecycle step. Do not infer retention, residency, ownership or access. PASTED DATA-FLOW MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Make sure retention, access, storage location and deletion are marked unknown unless the source says otherwise.
19. Turn release notes into a seller briefing
When to use it: When product changes need to be explained without turning a release note into a marketing claim.
Prompt — ready to paste
I will paste release notes and, if available, an internal technical explanation. Use only that material. Create an internal seller briefing with: what changed, who may notice, prerequisite or configuration changes, stated limitations, customer questions the change may trigger, and claims sellers should avoid because the source does not establish them. Do not infer customer benefit from the existence of a feature. PASTED RELEASE MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Compare every claimed change and limitation with the release note; remove any invented customer outcome.
20. Convert a technical FAQ into a conversation guide
When to use it: When sellers need accurate talking points from an approved technical FAQ.
Prompt — ready to paste
I will paste an approved technical FAQ. Work only from it. Create a conversation guide with: customer question, plain-English answer, evidence or source line behind the answer, boundary or qualification, and when to involve a specialist. Do not add answers for questions the FAQ does not cover. Keep the wording suitable for a live customer conversation. PASTED FAQ: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check each answer against the FAQ and remove any specialist escalation reason the source does not justify.
3. Proof, POCs and assurance evidence
21. Define a proof-of-concept decision
When to use it: When a customer wants a PoC but the decision it should answer is still vague.
Prompt — ready to paste
I will paste the customer requirement, proposed test scope and any technical notes. Use only those materials. Turn them into a PoC decision brief with: the customer question, test population or environment, success evidence, failure evidence, named owner for acceptance if stated, exclusions, and the next decision the result should support. Do not invent thresholds, test steps or acceptance criteria. PASTED MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that every success condition and owner comes from the pasted material rather than from a generic PoC template.
22. Write a PoC result without overclaiming
When to use it: When a test has finished and you need to explain exactly what it proved.
Prompt — ready to paste
I will paste the PoC plan, observed results and reviewer notes. Work only from them. Write a result summary with: what was tested, what was observed, any exceptions, which success criteria were met, which were not resolved, and the decision the evidence supports. Keep sandbox, pilot and production evidence distinct. Do not extend the result to populations, environments or periods not tested. PASTED POC EVIDENCE: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Trace every conclusion to a result or acceptance criterion and remove any extension beyond the tested scope.
23. Summarise a partial or failed evaluation
When to use it: When a customer test did not fully succeed and you need a useful, honest close-out.
Prompt — ready to paste
I will paste the test plan, observed failures, successful checks and technical notes. Use only those records. Create a close-out with: completed tests, successful evidence, failed evidence, blocked tests, stated cause if established, open cause if not established, and the next decision available to the customer. Do not hide failed checks or invent remediation. PASTED EVALUATION MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Confirm that causes are labelled unknown unless the technical notes explicitly establish them.
24. Map an assurance report's evidence boundary
When to use it: When a buyer asks whether an assurance report answers a specific security question.
Prompt — ready to paste
I will paste an assurance-report summary or approved extract plus the customer's question. Work only from those texts. Create an evidence-boundary table showing: customer claim being tested, report service or system in scope, period, criteria or control area if stated, relevant finding, exclusion or customer responsibility, and whether the report supports the claim fully, partly or not at all. Explain the classification only from the pasted material. PASTED REPORT MATERIAL AND CUSTOMER QUESTION: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Verify that scope, period and exclusions are visible in the report material before using them in a customer answer.
25. Answer a security questionnaire from supplied evidence
When to use it: When you have approved evidence and need a first draft of questionnaire responses.
Prompt — ready to paste
I will paste the questionnaire items and approved evidence. Use only the approved evidence to draft answers. For each question, return: proposed answer, exact evidence relied on, qualification or scope boundary, and status of Supported, Contradicted or Not established. Never convert Not established into a positive answer. Do not import security practices from general knowledge. PASTED QUESTIONS: [PASTE HERE] PASTED APPROVED EVIDENCE: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check every positive statement against a specific pasted source line and route unsupported items for clarification.
26. Translate a penetration-test summary safely
When to use it: When a customer needs a commercial explanation of a supplied test summary.
Prompt — ready to paste
I will paste an approved penetration-test summary or security-team extract. Work only from it. Draft a customer-ready explanation of the tested scope, test period if stated, finding status, remediation or retest evidence if stated, and any exclusions. Do not turn a penetration test into proof of controls the test did not examine. Do not infer that an unmentioned finding does not exist. PASTED TEST SUMMARY: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Compare the final wording with the supplied scope and make sure it does not imply broader assurance than the test provides.
27. Build a claim-to-evidence matrix
When to use it: When a proposal or presentation contains security claims that need to be checked before use.
Prompt — ready to paste
I will paste proposed customer claims and the evidence pack available to me. Use only those materials. Create a matrix with: claim, supporting evidence, scope match, period match if relevant, owner or source, contradiction if any, and status of Supported, Needs qualification or Not established. Suggest a narrower wording only when the evidence supports one. PASTED CLAIMS: [PASTE HERE] PASTED EVIDENCE: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Remove any revised wording that relies on knowledge not present in the evidence pack.
28. Find the evidence gaps before a customer claim
When to use it: When a seller wants to make a strong claim but needs to know what proof is missing.
Prompt — ready to paste
I will paste the proposed claim and all evidence currently available. Work only from those materials. Break the claim into factual components. For each component, state whether the evidence establishes it, partly supports it or leaves it unknown. Name the exact missing evidence needed to close each gap without inventing a document that must exist. If the claim is already fully supported, say so. PASTED CLAIM AND EVIDENCE: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that the AI asks for evidence categories rather than assuming a particular certificate, report or test must exist.
29. Separate pilot evidence from production readiness
When to use it: When a successful pilot is being used to justify a wider rollout.
Prompt — ready to paste
I will paste the pilot scope, results, production requirements and any open technical notes. Use only those materials. Create two columns: Established by the pilot and Still required for production. Compare environment, population, permissions, integrations, failure handling, operating ownership and acceptance only where the source addresses them. Then write one bounded customer sentence that accurately describes readiness. PASTED MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Make sure the readiness sentence does not assume production parity where only pilot evidence exists.
30. Track exceptions and remediation evidence
When to use it: When a security review contains findings and the customer asks what has actually been closed.
Prompt — ready to paste
I will paste the finding summary, remediation notes and retest records. Use only those sources. Create a tracker with: finding, original status, remediation action stated, owner if named, retest evidence, current evidenced status and remaining uncertainty. Distinguish 'fixed', 'retested', 'accepted' and 'not evidenced' instead of treating them as synonyms. PASTED FINDINGS AND EVIDENCE: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that no finding is marked closed unless the supplied evidence supports that current status.
4. Commercial: quotes, renewals, coverage
31. Read a quote for scope, not just line items
When to use it: When you need to explain what a quote actually includes and excludes.
Prompt — ready to paste
I will paste a quote or order summary with commercial figures removed if necessary. Use only the pasted material. Map each line item to its stated deliverable, term, quantity or entitlement, implementation responsibility, support boundary, exclusions and acceptance condition where present. Put anything ambiguous in a separate Open questions section. Do not assume that a subscription includes implementation or managed service work. PASTED QUOTE: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check each included service and exclusion against the quote rather than relying on how similar offers are usually packaged.
32. Compare two quotes without using unstated assumptions
When to use it: When a customer is choosing between two offers and you need a scope-only comparison.
Prompt — ready to paste
I will paste two quotes or proposal extracts. Work only from them. Compare entitlement, duration, quantity basis, implementation, support, customer responsibilities, exclusions, renewal language and acceptance conditions. Mark a field Not stated when one quote is silent. Do not infer that silence means included or excluded. End with the decisions a customer would need to make to compare the offers fairly. QUOTE ONE: [PASTE HERE] QUOTE TWO: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Verify that every difference is stated in one of the quotes and that missing information stays marked as missing.
33. Check a renewal against the current entitlement
When to use it: When a renewal arrives and you need to verify what is actually being continued.
Prompt — ready to paste
I will paste the current entitlement record, renewal document and any approved change record. Use only those materials. Create a renewal reconciliation showing: current entitlement, proposed renewal entitlement, quantity or coverage change, term change, removed items, added items, approval evidence and unresolved mismatch. Do not treat past usage, an old proposal or a seller note as authority unless the pasted material says it governs the renewal. PASTED RENEWAL MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check each change against the governing entitlement and approved change records before describing it as authorised.
34. Find support and service coverage boundaries
When to use it: When a customer asks whether a requested activity is covered.
Prompt — ready to paste
I will paste the support terms, service description and the customer's request. Work only from them. Break the request into activities and classify each as Included, Excluded, Conditional or Not stated. Quote or paraphrase the clause supporting each classification. Identify any stated service window, response boundary, customer prerequisite or escalation path relevant to the request. PASTED TERMS AND REQUEST: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Confirm that coverage labels come from the written service terms, not from what a seller thinks support should include.
35. Map supplier, partner and customer responsibilities
When to use it: When a multi-party deal is unclear about who contracts, delivers, supports or approves.
Prompt — ready to paste
I will paste the partner agreement extract, customer proposal and any responsibility notes. Use only those materials. Create a responsibility map for contracting, ordering, implementation, support, customer acceptance, external claims, approvals and renewal ownership where stated. Use Not established when authority is missing. Do not give a partner authority merely because it introduced or services the account. PASTED MULTI-PARTY MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check every authority statement against an explicit clause or note and remove any role inferred from relationship status.
36. Reconcile an order form with a statement of work
When to use it: When the documents appear to describe the same deal differently.
Prompt — ready to paste
I will paste an order form and statement of work. Work only from those documents. Create a reconciliation table for scope, quantities, term, implementation deliverables, customer dependencies, acceptance, support, exclusions and document precedence if stated. Highlight true conflicts separately from details that simply appear in one document only. Do not choose which document wins unless precedence is explicit. ORDER FORM: [PASTE HERE] STATEMENT OF WORK: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that conflicts are genuine and that the AI has not invented a document hierarchy.
37. Build a renewal risk brief from evidence
When to use it: When a renewal is approaching and you need to separate known risks from seller anxiety.
Prompt — ready to paste
I will paste usage notes, support history, stakeholder messages, entitlement records and renewal correspondence. Use only those materials. Create a renewal brief with: confirmed positive signals, confirmed risks, unresolved service or entitlement issues, stakeholder changes, commitments already made, and next evidence needed. Label interpretation separately from customer-stated facts. Do not infer churn risk or renewal intent from silence alone. PASTED RENEWAL EVIDENCE: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Remove any churn, expansion or intent claim that is not directly supported by the pasted evidence.
38. Reconcile usage with entitlement
When to use it: When observed usage and contracted entitlement may not match.
Prompt — ready to paste
I will paste the entitlement record and a usage extract for the same period. Work only from them. Compare the authorised unit, quantity, named population, period and any stated overage or restriction with the observed usage record. Flag mismatches and data gaps. Do not calculate financial impact and do not assume that observed usage changes the entitlement. PASTED ENTITLEMENT: [PASTE HERE] PASTED USAGE: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Verify the unit, population and period match before treating any difference as a true entitlement exception.
39. Create a commercial handover coverage matrix
When to use it: When a signed or near-signed deal needs to move from sales to delivery or customer success.
Prompt — ready to paste
I will paste the accepted proposal, order summary, implementation notes and seller commitments. Use only those materials. Create a handover matrix covering purchased entitlement, implementation deliverables, customer dependencies, support boundary, acceptance evidence, open commitments, partner responsibilities and renewal ownership where stated. Separate contractual commitments from informal seller promises. PASTED HANDOVER MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that informal notes are not presented as contracted scope unless the governing document supports them.
40. Prepare an approval checklist from the deal documents
When to use it: When you need to know which commercial approvals are actually required before the next step.
Prompt — ready to paste
I will paste the approval policy, quote, proposal notes and any exception request. Work only from those materials. List every approval explicitly required by the documents, the condition that triggers it, the named approver or role, evidence of approval already present, and status. Keep internal recommendation separate from formal approval. Do not add generic finance, legal or management gates that the pasted policy does not state. PASTED APPROVAL MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Compare the checklist with the supplied policy and remove any approval stage introduced from generic sales practice.
5. Writing: follow-ups, summaries, objections
41. Write a customer follow-up from call notes
When to use it: When you need a concise follow-up that reflects the meeting without adding commitments.
Prompt — ready to paste
I will paste my call notes and any agreed actions. Use only those materials. Draft a concise customer follow-up with: what I heard, decisions made, open points, agreed actions with owners where stated, and the next meeting or step only if it was agreed. Keep tentative ideas out of the commitments section. Do not add benefits, deadlines or promises that are absent from the notes. PASTED CALL NOTES: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Compare every commitment, owner and timing statement with the notes before sending.
42. Draft an executive deal summary
When to use it: When a senior stakeholder needs the decision in one screen rather than a full sales history.
Prompt — ready to paste
I will paste the latest account notes, customer messages and evidence. Work only from them. Write an executive summary with: customer outcome, current decision, evidence already established, open gates, named owners where stated, commercial or technical dependency, and recommended next action supported by the material. Keep internal recommendation visibly separate from customer-confirmed fact. PASTED ACCOUNT MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that the summary preserves uncertainty and does not convert internal confidence into customer agreement.
43. Answer an objection from the actual evidence
When to use it: When a customer challenges capability, risk, integration or delivery and you want a defensible response.
Prompt — ready to paste
I will paste the customer's objection plus the relevant approved evidence. Use only those texts. Draft a response that first acknowledges the exact concern, then answers only the parts supported by the evidence, states any qualification, and proposes a next evidence step for the unresolved part. Do not dismiss the objection or fill evidence gaps from general knowledge. CUSTOMER OBJECTION: [PASTE HERE] APPROVED EVIDENCE: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Verify that the response answers the customer's real objection and that every factual reassurance is supported.
44. Turn meeting notes into a neutral recap
When to use it: When several teams attended and you need a shared record that does not favour one interpretation.
Prompt — ready to paste
I will paste the meeting notes. Work only from them. Create a neutral recap with: purpose, material facts discussed, decisions made, unresolved questions, differing views if recorded, agreed actions, owners and stated timing. Do not decide disputes, add context that was not recorded or turn proposals into decisions. PASTED MEETING NOTES: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that the recap distinguishes discussion, decision and action exactly as the notes do.
45. Write an internal opportunity handoff note
When to use it: When a seller, pre-sales specialist or customer-success colleague needs the evidence without the sales spin.
Prompt — ready to paste
I will paste opportunity notes, customer emails and the latest agreed actions. Use only those materials. Write an internal handoff with: current customer objective, stage evidenced by the material, technical facts, commercial facts, stakeholder roles, commitments, open risks, evidence gaps and next action. Mark seller opinions as internal interpretation rather than customer fact. PASTED OPPORTUNITY MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Make sure the recipient can tell what the customer said, what documents establish and what the seller merely believes.
46. Write a partner follow-up without inventing authority
When to use it: When a reseller, distributor or service partner meeting creates actions for more than one organisation.
Prompt — ready to paste
I will paste the partner meeting notes, relevant agreement extract and agreed actions. Work only from those materials. Draft a follow-up that separates partner actions, supplier actions and customer dependencies. State approval or commitment authority only where the agreement or notes establish it. Keep proposed joint messaging separate from approved messaging. PASTED PARTNER MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that the partner is not given commercial, contracting, service or claim authority that the supplied agreement does not grant.
47. Write a cover note for a security questionnaire
When to use it: When you are returning evidence and need to set the scope before the buyer reads the answers.
Prompt — ready to paste
I will paste the completed questionnaire, evidence notes and unresolved items. Use only those materials. Write a short cover note stating what evidence is included, the scope or period that matters, which answers remain qualified or unresolved, and who will follow up if that owner is named. Do not say the questionnaire proves compliance or overall security unless the pasted material explicitly supports that conclusion. PASTED QUESTIONNAIRE MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Make sure the cover note does not make a broader assurance claim than the completed answers themselves.
48. Write a renewal follow-up from the record
When to use it: When a customer renewal discussion needs a clean summary of entitlement and open decisions.
Prompt — ready to paste
I will paste the renewal correspondence, current entitlement and agreed actions. Work only from those materials. Draft a customer follow-up summarising what is continuing, what is changing if established, open entitlement or service questions, customer and supplier actions, and the next agreed decision point. Do not infer renewal commitment from participation in the discussion. PASTED RENEWAL MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Confirm that the email does not describe a renewal as agreed unless the source actually records agreement.
49. Write a PoC close-out email
When to use it: When a technical evaluation has ended and the customer needs the result without marketing inflation.
Prompt — ready to paste
I will paste the agreed test scope, observed results, exceptions and acceptance notes. Use only those materials. Draft a close-out email that states what was tested, what the evidence showed, exceptions or unresolved checks, the customer decision now available, and the next step only if supported. Keep tested evidence separate from future capability or rollout assumptions. PASTED POC MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Compare the email with the test record and remove any statement that expands the result beyond the evaluation.
50. Draft an escalation note that stays factual
When to use it: When a deal issue needs senior attention without blame or speculation.
Prompt — ready to paste
I will paste the issue record, customer messages, internal notes and relevant commitments. Use only those materials. Write an escalation note with: issue, verified impact, timeline from the evidence, commitments affected, owner if established, decision needed, and unresolved facts. Separate observed events from interpretation. Do not assign fault, motive or root cause unless the pasted material explicitly establishes it. PASTED ESCALATION MATERIAL: [PASTE HERE] Finally, list what you could not establish from the pasted material.
Check before customer use: Check that every impact, owner and cause is evidenced and that emotionally loaded language has not replaced facts.