Identify Pain Points and Buying Triggers

Extract buyer pains and trigger events from discovery notes, then rank them by urgency, impact, and sales relevance.
Sales - Discovery - Identify Pain Points and Buying Triggers

Who it's for

Sales reps, Account executives, SDRs, Sales managers, Founders

Get Ready

Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.

How to use this prompt

1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.

🔒

Unlock the Full Workflow

Get access to this workflow and 1000+ others designed to save hours and get better results with AI.

Workflow Prompt

				
					You are a sales opportunity analyst. Your task is to identify the buyer's real pain points and buying triggers from provided notes, then rank them by urgency, impact, and relevance to the offer.

### Required Input
- Offer: [What you sell, e.g. managed IT support for distributed teams]
- Buyer or Account: [Company, segment, and primary contact role]
- Discovery Notes: [Raw notes, transcript excerpts, CRM notes, or call summary]
- Current Solution or Process: [What the buyer uses today, if known]
- Stated Reason for Conversation: [Why they agreed to talk, e.g. renewal review, growth plans, poor service]
- Desired Outcome: [What they want to improve or achieve]
- Known Timing: [Any deadline, renewal date, internal project date, or urgency signal]

### Input Validation
Review all inputs before analysis. If discovery notes, offer, or stated reason for conversation are missing or too vague, ask targeted clarification questions. Pause and wait for clarification before generating the final output.

### Instructions
Read the discovery notes carefully and distinguish between symptoms, root pains, and buying triggers. A symptom is what the buyer notices. A pain point is the underlying problem that creates cost, risk, wasted time, lost revenue, frustration, or missed goals. A buying trigger is an event, deadline, pressure, or change that makes action more likely now.

Do not exaggerate weak signals. Label each item as confirmed, implied, or uncertain. Use the buyer's language where available, but translate it into clear sales terms.

Rank pain points by likely business impact, urgency, emotional weight, and connection to the offer. Rank buying triggers by how strongly they suggest timing, budget movement, executive attention, or risk of inaction.

Look for triggers such as leadership change, growth, budget cycle, renewal, failed initiative, compliance issue, customer complaint, operational bottleneck, cost pressure, missed target, hiring plan, product launch, market shift, or vendor dissatisfaction.

For each pain and trigger, explain what the seller should confirm next. Keep the output useful for planning the next conversation, not just documenting the last one.

### Output
Provide the analysis in this format:

1. Executive Summary of Buyer Motivation
2. Confirmed Pain Points
3. Implied Pain Points
4. Possible Root Causes
5. Buying Triggers Identified
6. Urgency Assessment
7. Impact Assessment
8. Fit With the Offer
9. Risks or Weak Signals
10. Priority Follow-Up Questions
11. Recommended Sales Angle for the Next Conversation
				
			

Optional advanced instructions

				
					Add a confidence score for each pain point and buying trigger using High, Medium, or Low.
				
			

Example output

1. Executive Summary of Buyer Motivation

Offer: Managed IT support for distributed professional services teams

Buyer or Account: Brightlane Advisory, 180-person consulting firm with a COO as primary contact

Brightlane appears motivated by a combination of operational disruption and risk management. The buyer agreed to talk because remote employees are waiting too long for IT support, the internal IT team is overloaded, and leadership is concerned that device management has not kept pace with hybrid work.

2. Confirmed Pain Points

  • Slow support response for distributed employees. Status: Confirmed. Ranking: High urgency, high operational impact, strong relevance to offer.
  • Internal IT team is overloaded. Status: Confirmed. Ranking: High operational impact, medium emotional weight, strong relevance.
  • Remote device management is inconsistent. Status: Confirmed. Ranking: High risk impact, medium urgency, strong relevance.

3. Implied Pain Points

  • Consultant productivity may be affected by IT delays. Status: Implied.
  • Security risk may be increasing as hybrid work expands. Status: Implied.
  • Current vendor mix may create accountability gaps. Status: Implied.

4. Possible Root Causes

  • Support demand has outgrown the internal IT team.
  • Contractors may solve local issues but not provide consistent service management.
  • Remote work policies may have expanded faster than IT governance.
  • Device inventory, endpoint security, and support workflows may not be integrated.
  • Leadership may lack visibility into IT performance metrics.

5. Buying Triggers Identified

  • Security renewal in 75 days. Strength: High. Creates budget and vendor review timing.
  • Hybrid-work policy update this quarter. Strength: Medium to high. May require stronger support and device standards.
  • Rising ticket backlog. Strength: High. Indicates current operating pain and potential productivity cost.
  • Vendor or contractor dissatisfaction. Strength: Medium. Current delivery model may not be trusted, but more evidence is needed.

6. Urgency Assessment

Urgency is medium to high. The security renewal provides a time-bound event, and the ticket backlog suggests an existing operational strain.

7. Impact Assessment

The likely impact includes lost employee productivity, lower consultant utilisation, increased security exposure, delayed onboarding, and IT team burnout.

8. Fit With the Offer

Fit appears strong. Managed IT support directly aligns with support response, distributed employee coverage, endpoint management, and relieving the internal IT team.

9. Risks or Weak Signals

  • No confirmed budget beyond the upcoming security renewal.
  • Decision makers beyond the COO are not yet identified.
  • Current IT team may resist outsourcing if positioned poorly.
  • Pain has not yet been quantified in downtime, ticket volume, or cost.
  • Security renewal may only cover tools, not services, unless budget can be expanded.

10. Priority Follow-Up Questions

  • How many support tickets are open at any given time, and how long do employees typically wait?
  • Which IT issues most often interrupt billable client work?
  • What parts of remote device management concern leadership most?
  • Who owns the security renewal decision?
  • Are you evaluating only endpoint security, or broader IT service delivery as well?
  • What would your internal IT team want to keep versus hand off?
  • What needs to be decided before the renewal date?

11. Recommended Sales Angle for the Next Conversation

Position the next conversation around reducing distributed workforce disruption and creating a scalable co-managed IT model before the security renewal.

When to reuse this workflow

You may also like...

🔒

Unlock the Full Workflow

Get access to this workflow and 1000+ others designed to save hours and get better results with AI.

No guesswork. Just proven systems.

  • Copy & paste ready prompts
  • Step-by-step instructions
  • Works with ChatGPT instantly

BANT-Based Discovery Call Qualification Script

Qualify leads using the BANT framework to determine fit, urgency, and readiness for sales progression.

Proof Points and Case Study Insertion

Strategically insert proof points and case studies into presentations to increase credibility.

Presentation Objection Anticipation

Prepare for likely objections before a sales presentation to improve confidence and outcomes.

Unlock the full library.

Get access to all workflows, across every sector, with structured systems built for better results.

Get Free Access