Privacy tip
When using these prompts, always adhere to your organisations AI Use Policy. If in doubt, check with your Driver or internal contact and avoid including organisational details or specific information. This helps maintain privacy while still getting valuable AI assistance.
The prompt collection
Industry research brief
When to use: Before engaging with prospects in an unfamiliar industry.
Objective: Quickly build industry credibility and identify relevant talking points.
Optional uploads:
- Public industry reports or whitepapers
- Published news articles about sector trends
- Your product’s marketing collateral or capability overview
Prompt:
Act as a Senior Consultant specialising in the [INDUSTRY] sector within [REGION].
I am preparing to meet with a [ROLE TYPE, e.g., Operations Leader] at a company in this space.
Task 1: Identify the top 3 industry trends currently impacting companies in this region.
Task 2: Explain how a solution focused on [PRIMARY BENEFIT, e.g., workflow automation] would connect to these trends.
Task 3: Draft one open-ended discovery question using industry-specific terminology.
[If uploading] Review the attached materials for additional context.
Discovery meeting prep
When to use: Before a first discovery call or qualification meeting.
Objective: Create a structured briefing to guide conversation and demonstrate preparation.
Optional uploads:
- The prospect company’s public “About Us” or “Our Story” webpage (copy/paste text)
- Recent press releases from the company
- Your product’s one-pager or solution brief
Prompt:
Act as a Senior Account Director. I am preparing for a discovery meeting with a [ROLE TYPE] in the [INDUSTRY] sector.
My solution helps companies [MAIN BENEFIT].
Generate a briefing document with:
1. Icebreaker Suggestions
- Suggest 2-3 general conversation starters appropriate for this role and industry.
2. Budget Timing Check
- Based on the industry (Government, Education, Corporate), estimate the likely financial year end.
- Suggest one question to understand their current budget cycle.
3. Strategic Alignment
- Identify common strategic priorities for this role/industry.
- Draft a 2-sentence opener connecting my solution to a typical goal.
4. Discovery Questions
- Question A (Operational): Day-to-day friction points
- Question B (Strategic): Risk, compliance, or governance concerns
- Question C (Aspirational): "If you could change one thing..."
[If uploading] Use the attached company information to tailor the briefing.
Pitch translator
When to use: When adapting a standard pitch for a specific industry or audience.
Objective: Reframe generic messaging using industry-relevant language and references.
Optional uploads:
- Your current pitch deck or sales script
- Your product’s marketing website copy
- Industry glossary or terminology guide
Prompt:
Here is my standard pitch:
[INSERT PITCH OR REFERENCE UPLOADED DOCUMENT]
Rewrite this for a [INDUSTRY] audience.
Constraints:
1. Terminology: Replace generic terms with industry-specific language.
- Example: "Customers" → "Patients" (Healthcare) or "Members" (Associations)
- Example: "Revenue" → "Funding" (NFP) or "Shareholder Return" (Corporate)
2. Tone: Adjust to be [Professional / Urgent / Innovative].
3. Region: Use [REGION] spelling conventions and reference relevant local regulations or standards.
[If uploading] Translate the attached pitch document using these constraints.
Objection roleplay
When to use: To prepare for common objections before a meeting or negotiation.
Objective: Anticipate pushback and rehearse effective responses.
Optional uploads:
- Your product’s FAQ or objection handling guide
- Competitor comparison matrix (public/marketing version)
- Case studies or testimonials
Prompt:
I am selling a [SOLUTION TYPE] to a [ROLE TYPE] in the [INDUSTRY] sector.
The prospect is likely concerned about [OBJECTION THEME, e.g., implementation time / cost / compliance].
Task:
1. Roleplay as this skeptical buyer. Give me their likely verbal objection, referencing a realistic industry constraint.
2. Script a response that:
- Acknowledges their concern
- Reframes with relevant context or evidence
- Redirects toward value
[If uploading] Use the attached materials to strengthen the rebuttal with specific proof points.
Account expansion mapper
When to use: When looking for cross-sell or up-sell opportunities within an existing account.
Objective: Identify new departments or use cases and draft an internal referral request.
Optional uploads:
- The client company’s public organisational overview (from their website)
- Their publicly available annual report or investor presentation
- Your product’s use case library by department/function
Prompt:
I currently sell [SOLUTION TYPE] to the [CURRENT DEPARTMENT] function at an existing client in the [INDUSTRY] sector.
Task:
1. Identify 2 other departments that would logically face similar challenges.
2. Draft a 3-sentence email I can send to my current contact asking for an introduction to those teams.
3. Use [STRATEGIC THEME, e.g., operational efficiency / customer experience] as the connecting thread.
[If uploading] Use the attached company overview to identify specific expansion opportunities.
Demo story script
When to use: Before a product demonstration to make it narrative-driven rather than feature-focused.
Objective: Transform feature explanations into relatable “day in the life” scenarios.
Optional uploads:
- Your product’s feature documentation or release notes
- Existing demo script or talk track
- Customer success stories or use case briefs
Prompt:
I am giving a product demo to a [ROLE TYPE] in the [INDUSTRY] sector.
They are struggling with [PAIN POINT].
I need to demonstrate [FEATURE/CAPABILITY].
Task: Script a 2-minute story, not a technical walkthrough.
Structure:
- Before: Describe a frustrating morning for this person dealing with the pain point. Use industry-relevant details.
- After: Show how the feature resolves it.
- Tone: Empathetic and visual.
[If uploading] Reference the attached feature documentation to ensure accuracy.
Executive summary writer
When to use: When you need to distil a detailed proposal into a one-page overview for senior stakeholders.
Objective: Create a compelling business case summary for executive decision-makers.
Optional uploads:
- Your draft proposal or scope document
- ROI calculator outputs or business case template
- Published case studies with quantified outcomes
Prompt:
I need to write a 1-page Executive Summary for a [C-LEVEL ROLE] in the [INDUSTRY] sector.
Structure:
1. Context: Acknowledge their likely strategic priority (e.g., growth, efficiency, risk reduction).
2. Problem: Summarise the operational or business risk of maintaining the status quo.
3. Solution: High-level overview of the proposed approach (no technical jargon).
4. Expected Outcomes: 3-4 bullet points on efficiency gains, cost impact, or risk mitigation.
[If uploading] Synthesise the attached proposal into this executive format.
Procurement response
When to use: During final negotiations when facing price objections or competitive comparisons.
Objective: Justify value and differentiate from competitors without being defensive.
Optional uploads:
- Your product’s pricing rationale or value justification document
- Public competitor comparison (features, not pricing)
- TCO (Total Cost of Ownership) framework or calculator
Prompt:
I am in final negotiations with a [INDUSTRY] client. Their procurement team is pushing back on price, citing a lower-cost alternative.
Task: Draft a response that:
1. Acknowledges the price difference respectfully.
2. Pivots to Total Cost of Ownership—highlight hidden costs of cheaper alternatives (implementation, support, compliance gaps, etc.).
3. Reinforces our differentiation around [KEY VALUE POINT].
4. Tone: Firm but collaborative.
[If uploading] Use the attached value documentation to strengthen the TCO argument.
Customer success handoff
When to use: After closing a deal, to brief the onboarding or customer success team.
Objective: Structure sales cycle insights into a clear handoff document.
Optional uploads:
- Your company’s standard handoff template
- Onboarding checklist or implementation timeline
- Customer’s signed scope or statement of work (if shareable internally)
Prompt:
I just closed a deal and need to brief the Customer Success team.
Task: Help me structure a handoff document covering:
1. Why They Bought: The primary pain point or trigger.
2. Previous Attempts: What solutions they tried before (and why those failed).
3. Stakeholder Notes: Key contacts, decision-makers, and any sensitivities.
4. Commitments Made: Specific deliverables or timelines promised during the sales process.
5. Success Metrics: How they will measure value in the first 90 days.
[If uploading] Use the attached template to format the handoff.
