Needs Analysis Summary Template

Turn discovery notes into a clear needs analysis summary with pains, goals, gaps, risks, and next steps.
Sales - Discovery - Needs Analysis Summary Template

Who it's for

Sales reps, Account executives, Sales managers, SDRs, 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 analyst. Your task is to turn raw discovery notes into a structured needs analysis summary that helps the seller understand the buyer's situation, priorities, risks, and likely next step.

### Required Input
- Prospect: [Company or buyer name, e.g. Acme Manufacturing]
- Buyer Role: [Primary contact role, e.g. VP Operations]
- Offer: [What you sell, e.g. sales enablement software for mid-market teams]
- Discovery Notes: [Paste raw notes, transcript excerpts, or bullet points from the conversation]
- Business Context: [Relevant company situation, e.g. expanding to two regions while reducing support costs]
- Known Goals: [What the buyer wants to achieve, e.g. shorten onboarding time by 30%]
- Known Constraints: [Budget, timing, internal blockers, existing vendor, compliance, resources]
- Next Step Needed: [What you need after the summary, e.g. prepare proposal, recap email, qualification review]

### Input Validation
Review all required inputs before producing the summary. If the offer, discovery notes, buyer role, or business context is missing, unclear, or too thin to support a useful analysis, ask specific clarification questions. Pause and wait for clarification before generating the final output.

### Instructions
Analyse the discovery notes as a sales operator, not as a note taker. Separate what the buyer explicitly said from what can reasonably be inferred. Do not invent facts, budgets, timelines, decision makers, or pain severity.

Identify the buyer's current situation, the operational or commercial problems behind it, and the impact those problems may be creating. Convert scattered notes into crisp business language that could be shared internally with a sales manager or customer-facing team.

Assess whether each pain is strategic, financial, operational, personal, or technical. Look for urgency signals such as deadlines, executive pressure, growth targets, failed initiatives, customer complaints, rising costs, missed revenue, or compliance exposure.

Map the buyer's stated goals to the offer without forcing a fit. Where the connection is weak, mark it as an open question rather than overstating alignment. Highlight missing information that must be confirmed before proposing a solution.

Keep the output practical and deal-focused. Use concise bullets, but include enough context that someone who missed the call could understand the opportunity.

### Output
Provide the needs analysis summary in this format:

1. Buyer Situation Summary
2. Stated Goals and Desired Outcomes
3. Confirmed Pain Points
4. Likely Underlying Problems
5. Business Impact
6. Buying Triggers and Urgency Signals
7. Solution Fit Assessment
8. Risks, Gaps, and Unknowns
9. Recommended Next Step
10. Questions to Confirm Before Advancing
				
			

Optional advanced instructions

				
					Rewrite the summary in a more executive-ready style suitable for a sales manager or deal review meeting.
				
			

Example output

1. Buyer Situation Summary

Prospect: Northstar Components

Buyer Role: VP Operations

Offer: Workflow automation platform for mid-market manufacturers

Northstar Components is a 420-person manufacturing company expanding from one primary production site into two additional regional facilities over the next twelve months. The VP Operations described a current operating model that relies heavily on spreadsheets, email approvals, and manual handoffs between production planning, quality, procurement, and customer service.

The buyer explicitly said the team is “losing time chasing status updates” and that plant managers do not trust the weekly operations report because information is often outdated by the time it reaches leadership.

2. Stated Goals and Desired Outcomes

  • Reduce manual status tracking across production, procurement, and quality teams.
  • Improve visibility into order readiness, exceptions, and delayed approvals.
  • Shorten new-site onboarding by creating more standardised operating workflows.
  • Reduce escalation volume caused by unclear ownership or missing updates.
  • Give senior leadership a more reliable view of operational bottlenecks before they affect customers.

3. Confirmed Pain Points

  • Manual handoffs are slowing operational execution. Pain type: Operational. Evidence: Buyer said teams rely on spreadsheets and email approvals.
  • Leadership reporting lacks trust. Pain type: Strategic and operational. Evidence: Buyer said plant managers do not trust the weekly report.
  • Status visibility is poor across departments. Pain type: Operational and technical. Evidence: Buyer said teams chase updates and information is stale.
  • Expansion is increasing process complexity. Pain type: Strategic. Evidence: Business is opening two regional facilities.

4. Likely Underlying Problems

  • No single source of truth for operational workflow status.
  • Process ownership may be inconsistent across functions and facilities.
  • Reporting appears dependent on manual updates rather than live workflow data.
  • Existing processes may be built around one-site habits that will not scale to three locations.
  • Exceptions may be handled reactively instead of through structured escalation rules.

5. Business Impact

  • Possible delays in production readiness and customer order fulfilment.
  • Increased management time spent reconciling information instead of resolving issues.
  • Higher risk of inconsistent processes across new facilities.
  • Reduced confidence in operational reporting during a growth phase.
  • Potential customer experience risk if delays are not visible early enough.

6. Buying Triggers and Urgency Signals

  • Regional expansion over the next twelve months is the strongest trigger.
  • Executive pressure is likely because leadership needs reliable reporting during expansion.
  • The buyer’s concern about trusted reports suggests existing tools are already creating management friction.
  • The urgency is moderate to high, but the exact decision deadline and budget timing are not yet confirmed.

7. Solution Fit Assessment

The offer appears relevant because workflow automation could directly support standardised approvals, status visibility, exception management, and cross-site reporting. The strongest fit is around replacing spreadsheet-based coordination with structured workflows.

The fit should not be overstated until the seller confirms integration requirements, current systems, budget ownership, implementation resources, and which workflows matter most in the first phase.

8. Risks, Gaps, and Unknowns

  • No confirmed budget or approved project owner yet.
  • Unknown whether IT or operations owns workflow technology decisions.
  • Unknown current ERP or production planning systems.
  • Unknown whether the buyer wants automation, reporting, process redesign, or all three.
  • Unknown timeline for selecting a vendor before the first new facility opens.
  • Risk that the seller proposes too broadly before prioritising the first workflow use case.

9. Recommended Next Step

Prepare a focused follow-up discovery session with the VP Operations and one plant manager. The goal should be to map the highest-friction workflow, quantify impact, confirm the expansion timeline, and identify who must approve a workflow automation project.

10. Questions to Confirm Before Advancing

  • Which operational workflow creates the most delay or escalation today?
  • What happens when the weekly report is wrong or late?
  • Which metrics does leadership need to trust during the expansion?
  • What systems currently hold production, procurement, and quality data?
  • Who owns process standardisation across the new facilities?
  • Is there an approved budget for operational systems tied to expansion?
  • What decision deadline would allow implementation before the next site goes live?

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.

Demo Customisation Framework

Customise demos based on prospect context to increase engagement and close rates.

Unlock the full library.

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

Get Free Access