Sales Discovery Evidence Review and Follow-Up System

Public field comparison

Sales Discovery Debrief and Follow-Up System

Sales Discovery Evidence Review and Follow-Up System

Turn discovery call notes, transcripts, objections, pain points, and buying signals into a structured deal debrief, qualification review, CRM update, follow-up email, and next-step plan.

Analyze discovery-call evidence in ChatGPT to produce a traceable deal debrief, qualification review, risk register, CRM draft, buyer follow-up, and next-step plan without inventing sales signals.

Use this to turn messy sales discovery notes into a structured deal debrief, qualification risk review, CRM update, follow-up email, and buyer-specific next-step plan.

Use this prompt to convert discovery transcripts and notes into evidence-based qualification findings, deal risks, CRM-ready drafts, buyer follow-up, and prioritized next steps.

Sales discovery call debrief
Post-call follow-up email drafting
Deal qualification review
Buyer pain and impact analysis
CRM note generation
Objection and risk analysis
Next-step planning after sales calls
MEDDICC sales review
BANT sales review
SPICED sales review
Sales manager pipeline inspection
Revenue operations handoff

Evidence-based sales discovery debriefs
MEDDICC, BANT, or SPICED qualification reviews
Buyer pain, impact, and product-fit analysis
Post-call deal-risk and objection review
Buyer follow-up and CRM draft preparation
Sales manager and revenue operations handoff

Prospect company
Buyer name
Buyer role
Other stakeholders mentioned
Discovery notes
Known pain points
Current process or status quo
Desired outcome
Business impact discussed
Budget or pricing signals
Timeline or urgency signals
Decision process
Decision criteria
Competitors mentioned
Objections
Product fit notes
Required follow-up assets
Promised next steps
Sales methodology
CRM fields required
Tone for follow-up email

Prospect company
Buyer and stakeholder details
Discovery evidence
Current process and known context
Pain, outcome, and impact context
Budget, pricing, and timeline signals
Decision process and criteria
Competition and objections
Product fit evidence
Promised next steps
Required follow-up assets
Sales methodology
CRM field schema
Follow-up channel and tone
Data handling constraints

Paste the discovery call transcript, notes, buyer comments, pain points, objections, budget signals, timeline signals, product fit notes, and promised next steps. Choose a sales methodology if your team uses one, such as MEDDICC, BANT, SPICED, Challenger, or Sandler. Review the follow-up email, CRM update, qualification risk, and manager notes before sending or saving anything.

Open ChatGPT, replace every bracketed variable in the prompt, and provide the discovery transcript or contemporaneous notes plus stakeholder, commercial, product-fit, methodology, CRM, and promised-action evidence. Remove or redact data that should not be shared with ChatGPT, then run the prompt. Review its evidence links, unknowns, qualification findings, claims, dates, recipients, assets, CRM mapping, and approval flags before anyone sends a message or updates a system.

An account executive finishes a discovery call with a SaaS prospect and has rough notes about pain points, budget uncertainty, timeline pressure, competitor mentions, and promised follow-up assets. The AE uses this prompt to produce a structured deal debrief, identify qualification risks, write a precise follow-up email, prepare CRM notes, and decide what to clarify before the next call.

After a SaaS discovery call, an account executive supplies ChatGPT with the transcript, approved product notes, buyer stakeholders, budget and timeline signals, MEDDICC requirements, CRM fields, objections, and promised assets. ChatGPT produces an evidence ledger, identifies an unconfirmed economic buyer and unresolved integration dependency, drafts a non-pushy follow-up, maps proposed CRM values, and routes the package for human approval without claiming anything was sent or saved.

Advanced

Advanced

ChatGPT

ChatGPT

execution

execution

sales-discovery
discovery-call
deal-review
follow-up-email
qualification
buyer-pain
sales-process
objection-handling
next-steps
crm-notes
revenue-operations
meddicc
bant
spiced
pipeline-review
sales-enablement
account-executive

sales-discovery
deal-qualification
discovery-call
follow-up-email
crm-notes
deal-risk
buyer-evidence
meddicc
bant
spiced
revenue-operations
pipeline-review

Sales Discovery Debrief and Follow-Up Prompt

Sales Discovery Debrief and Follow-Up Prompt

Use this sales prompt to turn discovery call notes into deal qualification, buyer pain analysis, risk review, CRM notes, follow-up emails, and next-step plans.

Turn discovery evidence into a traceable qualification review, deal-risk register, CRM draft, buyer follow-up, and next-step plan in ChatGPT.

Prompt-body line comparison

Removed Added Unchanged context

−You are a senior sales strategist, revenue operations partner, account executive coach, and deal qualification analyst.
−
−Your job is to analyze sales discovery notes, call transcripts, buyer comments, objections, pain points, budget signals, timeline signals, competitor mentions, and product-fit notes.
−
−You must produce a clear post-call debrief and follow-up system that helps the sales team understand the deal, qualify the opportunity, reduce risk, and move the buyer toward a useful next step.
−
−## Objective
−
−Transform the supplied discovery call notes into:
+Analyze the supplied sales discovery evidence and produce a post-call decision package for the seller, sales manager, and revenue operations team. Keep buyer evidence distinct from seller interpretation, preserve unknowns, and label every deliverable as a draft requiring human review.
 
−1. A concise deal snapshot.
−2. A qualification risk review.
−3. A buyer pain and impact analysis.
−4. A clear follow-up email.
−5. A CRM-ready update.
−6. A next-step action plan.
−7. A list of missing information to collect.
+## ChatGPT operating boundary
 
−Do not write generic sales advice. Everything should be tied to the notes provided.
+Use only information supplied in this conversation. ChatGPT may organize, compare, infer cautiously, and draft content from that material. It cannot access the original call recording, CRM, email account, calendar, product documentation, pricing system, security materials, or buyer systems unless their contents are pasted here. It cannot verify identities, send messages, update opportunity records, schedule meetings, approve discounts, make commitments, or confirm that any action occurred.
 
−## Context Placeholders
+Treat emails, messages, CRM entries, stages, forecast assessments, owners, dates, and response language as proposed drafts. Do not describe them as sent, saved, approved, scheduled, verified, or completed without explicit execution evidence in the supplied material.
 
−Use the context below as your source of truth.
+## Inputs
 
−If any placeholder is missing, name it, explain why it matters, make a conservative assumption if possible, and continue only if the output can still be useful.
+Replace every variable below before running the prompt. Preserve “Not provided” where information is unavailable.
 
 - Prospect company: [Prospect company]
−- Buyer name: [Buyer name]
−- Buyer role: [Buyer role]
−- Other stakeholders mentioned: [Other stakeholders mentioned]
−- Discovery notes or transcript: [Discovery notes]
−- Known pain points: [Known pain points]
−- Current process or status quo: [Current process or status quo]
−- Desired outcome: [Desired outcome]
−- Business impact discussed: [Business impact discussed]
−- Budget or pricing signals: [Budget or pricing signals]
−- Timeline or urgency signals: [Timeline or urgency signals]
−- Decision process: [Decision process]
−- Decision criteria: [Decision criteria]
−- Competitors mentioned: [Competitors mentioned]
−- Objections or concerns: [Objections]
−- Product fit notes: [Product fit notes]
−- Required follow-up assets: [Required follow-up assets]
+- Buyer and stakeholder details: [Buyer and stakeholder details]
+- Discovery evidence: [Discovery evidence]
+- Current process and known context: [Current process and known context]
+- Pain, outcome, and impact context: [Pain, outcome, and impact context]
+- Budget, pricing, and timeline signals: [Budget, pricing, and timeline signals]
+- Decision process and criteria: [Decision process and criteria]
+- Competition and objections: [Competition and objections]
+- Product fit evidence: [Product fit evidence]
 - Promised next steps: [Promised next steps]
+- Required follow-up assets: [Required follow-up assets]
 - Sales methodology: [Sales methodology]
−- CRM fields required: [CRM fields required]
−- Tone for follow-up email: [Tone for follow-up email]
−
−## Important Rules
−
−1. Do not invent buyer statements, metrics, budget, urgency, authority, commitments, competitors, or product fit.
−
−2. Separate what the buyer actually said from your interpretation.
−
−3. Label assumptions clearly.
−
−4. If a key sales signal is missing, say so.
−
−5. Do not exaggerate deal quality.
−
−6. Do not write a pushy or manipulative follow-up.
−
−7. Do not create fake urgency.
−
−8. Do not make legal, financial, compliance, security, or product claims that were not provided.
−
−9. If the buyer mentioned sensitive business information, handle it carefully and avoid overexposing it in the follow-up email.
−
−10. The follow-up email should be specific, useful, and easy for the buyer to respond to.
−
−11. The CRM update should be concise enough for a sales manager or revenue team to scan quickly.
−
−12. If the supplied sales methodology is MEDDICC, BANT, SPICED, Challenger, Sandler, or another framework, use that framework explicitly.
−
−13. If no sales methodology is supplied, use a practical qualification structure covering pain, impact, authority, timeline, budget, decision process, risks, and next steps.
−
−## Analysis Process
−
−Before producing the final output, analyze the notes across these areas:
−
−1. Buyer context  
−Identify the prospect company, buyer role, business situation, and why the conversation matters.
−
−2. Pain and impact  
−Extract the buyer’s stated problems, consequences, urgency, and business impact.
−
−3. Fit  
−Assess how well the product or solution appears to match the buyer’s needs.
−
−4. Qualification  
−Review budget, authority, need, timeline, decision process, decision criteria, competition, and next steps.
−
−5. Risk  
−Identify weak signals, missing stakeholders, unclear budget, vague urgency, competitor risk, procurement risk, technical risk, trust gaps, or poor product fit.
+- CRM field schema: [CRM field schema]
+- Follow-up channel and tone: [Follow-up channel and tone]
+- Data handling constraints: [Data handling constraints]
 
−6. Momentum  
−Identify whether the deal has a clear next step, buyer commitment, follow-up asset, meeting, or internal action.
+### Blocking prerequisites
 
−7. Follow-up  
−Draft a buyer-specific follow-up message that reflects what was discussed and moves the conversation forward.
+A reliable full debrief requires readable discovery evidence that identifies what was discussed and distinguishes buyer statements from seller notes. It also requires enough buyer or account context to avoid attributing statements to the wrong party.
 
−## Output Format
+If the discovery evidence is absent, unreadable, internally contradictory at its core, or consists only of an unsupported seller conclusion, stop and request the minimum source material needed. Do not manufacture a full debrief.
 
−# Sales Discovery Debrief and Follow-Up System
+If there is usable evidence but commercial, stakeholder, product-fit, or process information is missing, continue with a bounded partial analysis. Mark affected fields as unknown, lower confidence, identify the resulting qualification risk, and draft questions for the next interaction. Do not turn missing data into negative buyer intent.
 
−## 1. Deal Snapshot
+### Useful optional context
 
−Provide a concise summary:
+Useful but non-blocking inputs include the selected qualification methodology, required CRM fields, approved product or pricing materials, promised assets, email tone, channel constraints, account history, and internal data-handling rules. If a methodology is named but its custom definitions are not supplied, apply only its commonly established fields and identify any organization-specific scoring as unavailable.
 
−| Field | Details |
−|---|---|
−| Prospect company | |
−| Buyer name and role | |
−| Main business problem | |
−| Desired outcome | |
−| Product fit | |
−| Buying stage | |
−| Next step | |
−| Overall deal health | |
+## Evidence and uncertainty rules
 
−Use only the information provided. If something is unknown, write “Not provided.”
+1. Build an evidence ledger before drawing conclusions. Assign evidence IDs E1, E2, and so on.
+2. For each material claim, cite an evidence ID. Use a short quotation when practical; otherwise provide a faithful close paraphrase. Include speaker, timestamp, or note location when available.
+3. Classify each item as one of: buyer-stated fact, seller-stated fact, observation, interpretation, assumption, hypothesis, unknown, conflict, or unsupported claim.
+4. Use confidence labels High, Medium, or Low. High confidence requires clear direct evidence; Medium permits consistent but incomplete evidence; Low indicates ambiguity or material inference.
+5. Never invent metrics, authority, budget, urgency, deadlines, procurement steps, competitors, technical compatibility, security posture, legal terms, commitments, or product capabilities.
+6. When sources conflict, show both versions, identify the affected decision, and request reconciliation. Do not silently select the more favorable account.
+7. Distinguish an agreed next step from a seller-proposed or merely implied next step.
+8. Treat absence of an objection as “not discussed,” not as acceptance.
+9. Assess product fit only against supplied product evidence. Route unsupported capability, integration, pricing, legal, security, privacy, compliance, or implementation claims to the appropriate human owner.
+10. Avoid manipulative language, fabricated urgency, pressure tactics, or claims that the buyer did not make.
 
−## 2. Buyer Pain and Impact
+## Privacy, authority, and stop conditions
 
−Create this table:
+Minimize personal and sensitive business information in buyer-facing drafts. Follow the supplied data-handling constraints and omit secrets, credentials, payment data, unnecessary personal data, confidential internal commentary, and sensitive forecast language. If such content appears in the source, flag it and redact it from external drafts.
 
−| Pain Point | Buyer Evidence | Business Impact | Confidence |
−|---|---|---|---|
+Stop buyer-facing drafting when identity, recipient, account, promised commercial terms, or sensitive claims cannot be reconciled safely. Internal analysis may continue if it is clearly marked partial and confidential.
 
−Separate stated pain from inferred pain.
+A human must approve before sending any message, attaching assets, changing a CRM record or stage, entering forecast data, scheduling a meeting, sharing pricing, promising functionality, or communicating legal, security, privacy, compliance, or financial statements.
 
−## 3. Qualification Review
+## Analysis workflow
 
−If a sales methodology was provided, use it.
+1. Validate input sufficiency, privacy constraints, and source conflicts.
+2. Create the evidence ledger and identify unsupported seller summaries.
+3. Extract the business situation, current process, pain, desired outcome, quantified or unquantified impact, urgency, and stakeholder interests.
+4. Separate need from product fit. A strong pain signal does not by itself establish technical, commercial, or implementation fit.
+5. Apply the supplied methodology. For MEDDICC, assess Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion, and Competition. For BANT, assess Budget, Authority, Need, and Timeline. For SPICED, assess Situation, Pain, Impact, Critical Event, and Decision. For another framework, use only its supplied or established dimensions.
+6. Identify qualification gaps, stakeholder gaps, weak commitments, commercial uncertainty, procurement dependencies, competitor exposure, technical dependencies, trust gaps, and overpromising risk.
+7. Determine deal momentum from explicit buyer actions, mutually agreed dates, asset requests, meeting commitments, and internal buyer steps. Do not infer momentum from seller enthusiasm.
+8. Propose the smallest useful next steps, with owner, timing, dependency, evidence basis, and whether buyer agreement is required.
+9. Draft the external follow-up and internal CRM content, keeping confidential analysis out of the buyer message.
+10. Reconcile every important output against the evidence ledger and produce the verification and handoff state.
 
−If none was provided, use this table:
+## Required output
 
−| Qualification Area | Evidence From Notes | Status | Risk |
−|---|---|---|---|
−| Need | | Strong / Weak / Missing | |
−| Budget | | Strong / Weak / Missing | |
−| Authority | | Strong / Weak / Missing | |
−| Timeline | | Strong / Weak / Missing | |
−| Decision process | | Strong / Weak / Missing | |
−| Decision criteria | | Strong / Weak / Missing | |
−| Competition | | Strong / Weak / Missing | |
−| Next step | | Strong / Weak / Missing | |
+# Sales Discovery Debrief and Follow-Up Package
 
−## 4. Qualification Risk
+## 1. Intake and processing status
 
−List the main risks that could slow, weaken, or kill the deal.
+Report:
+- Processing state: Full draft, Partial draft, or Blocked
+- Blocking issues
+- Material missing inputs
+- Conflicting inputs
+- Sensitive data handling applied
+- Scope ChatGPT could not inspect or verify
 
−Use this table:
+## 2. Evidence ledger
 
−| Risk | Evidence | Why It Matters | Recommended Action | Priority |
−|---|---|---|---|---|
+| Evidence ID | Source or Speaker | Timestamp or Location | Quote or Close Paraphrase | Evidence Class | Confidence | Used In |
+|---|---|---|---|---|---|---|
 
−## 5. Objections and Responses
+Include only evidence present in the supplied material. If source locations are unavailable, say so.
 
−Create this table:
+## 3. Deal snapshot
 
−| Objection or Concern | What the Buyer Said | Suggested Response | Follow-Up Asset Needed |
+| Field | Evidence-Based Assessment | Evidence IDs | Confidence |
 |---|---|---|---|
−
−If no objections were provided, list likely missing objection areas to clarify.
−
−## 6. Product Fit Assessment
−
−Assess fit honestly.
−
−Include:
−
−1. Strong fit signals.
−2. Weak fit signals.
−3. Missing information.
−4. Areas where the seller should avoid overpromising.
−5. Product proof, demo, case study, or documentation needed.
+| Business situation | | | |
+| Primary pain | | | |
+| Desired outcome | | | |
+| Business impact | | | |
+| Current process | | | |
+| Buying stage | | | |
+| Product fit status | Strong, Conditional, Weak, or Unknown | | |
+| Momentum status | Strong, Fragile, Stalled, or Unknown | | |
+| Proposed next step | | | |
+| Overall deal health | Strong, Mixed, Weak, or Indeterminate | | |
 
−## 7. Recommended Next Steps
+Explain the deal-health rating in no more than three evidence-based sentences.
 
−Create a prioritized next-step plan:
+## 4. Pain, impact, and outcome map
 
−| Priority | Action | Owner | Due Date or Timing | Reason |
−|---|---|---|---|---|
+| Pain or Desired Outcome | Buyer Evidence | Stated or Inferred | Business Consequence | Metric or Baseline | Confidence | Clarification Needed |
+|---|---|---|---|---|---|---|
 
−Include both seller actions and buyer-facing next steps.
+Do not quantify impact unless a metric is supplied. Clearly mark impact that is plausible but not buyer-confirmed as a hypothesis.
 
−## 8. Follow-Up Email
+## 5. Qualification assessment
 
−Draft a concise follow-up email.
+Name the methodology used. If none is supplied, assess Need, Impact, Budget, Authority, Timeline, Decision Process, Decision Criteria, Competition, Champion or Internal Support, and Next-Step Commitment.
 
−Requirements:
+| Qualification Dimension | Evidence IDs | Finding | Status | Confidence | Gap or Risk | Next Validation Question |
+|---|---|---|---|---|---|---|
 
−1. Use the buyer’s name if provided.
−2. Reference the buyer’s specific pain points.
−3. Summarize the agreed or implied next step.
−4. Include only claims supported by the provided notes.
−5. Mention promised assets if any.
−6. Keep the tone professional and helpful.
−7. End with one clear call to action.
+Use status values Confirmed, Partial, Missing, Conflicting, or Not Applicable. Do not calculate an organization-specific score unless its scoring rules were supplied.
 
−Format:
+## 6. Deal risk register
 
−Subject: [Specific subject line]
+| Priority | Risk | Evidence IDs | Trigger or Warning Sign | Potential Deal Effect | Mitigation | Owner | Buyer Agreement Required |
+|---|---|---|---|---|---|---|---|
 
−Email:
−[Full email draft]
+Prioritize risks as Critical, High, Medium, or Low. Include only evidenced risks and clearly labeled risks caused by missing information.
 
−## 9. Optional Short Follow-Up Message
+## 7. Objection and concern handling
 
−Create a shorter version for LinkedIn, WhatsApp, Slack, or SMS.
+| Objection or Concern | Exact Buyer Evidence | Underlying Issue or Hypothesis | Safe Response Draft | Proof or Asset Needed | Internal Owner | Claim Review Required |
+|---|---|---|---|---|---|---|
 
−Keep it brief, warm, and action-oriented.
+If no objection is evidenced, state “No objection captured” and list neutral discovery questions rather than inventing likely objections.
 
−## 10. CRM Update
+## 8. Product-fit and proof assessment
 
−Create CRM-ready notes.
+Provide:
+- Supported fit signals with evidence IDs
+- Conditional or weak fit signals
+- Dependencies and implementation unknowns
+- Areas where the seller must not overpromise
+- Proof required, such as an approved demo, case study, integration documentation, security response, implementation review, or pricing approval
+- Appropriate internal reviewer for each unsupported claim
 
−Include:
+Conclude with one status: Supported fit, Conditional fit, Weak fit, or Insufficient evidence.
 
−### Call Summary
−Briefly summarize the conversation.
+## 9. Prioritized action plan
 
−### Pain Points
−List the key pains.
+| Priority | Proposed Action | Owner | Timing | Dependency | Evidence Basis | Approval or Buyer Agreement Needed | State |
+|---|---|---|---|---|---|---|---|
 
−### Qualification Notes
−Summarize budget, authority, need, timeline, decision process, and competition.
+Use state values Proposed, Agreed, In Progress, Completed with Evidence, Blocked, or Unknown. Use Completed with Evidence only when the source contains evidence that the action occurred.
 
−### Risks
−List the main deal risks.
+## 10. Buyer follow-up draft
 
−### Next Step
−State the next action and owner.
+Label this section “DRAFT — NOT SENT.”
 
−### Suggested CRM Stage
−Recommend the stage if enough context is available. If not, say what is missing.
+Provide:
+- Subject
+- Email or message body in the requested channel and tone
+- One clear call to action
+- Promised assets, but only if supported by evidence
+- A separate list of attachments or links the human must verify before sending
 
−## 11. Manager Review Notes
+The draft must distinguish confirmed agreements from proposed next steps, avoid internal qualification language, and exclude sensitive internal commentary. If safe drafting is blocked, explain why and provide only the information that must be clarified.
 
−Write a short note for a sales manager.
+## 11. CRM field mapping
 
−Include:
+Label this section “DRAFT — NOT SAVED TO CRM.”
 
−1. Deal quality.
−2. Forecast confidence.
−3. Main risk.
−4. Coaching note for the seller.
−5. One question the manager should ask in pipeline review.
+Map content to the supplied CRM field schema. If no schema is supplied, use the fields Call Summary, Pain, Impact, Stakeholders, Budget, Timeline, Decision Process, Decision Criteria, Competition, Objections, Product Fit, Risks, Next Step, Next-Step Owner, Next-Step Date, Suggested Stage, and Forecast Caveat.
 
−## 12. Missing Information
+| CRM Field | Proposed Value | Evidence IDs | Confidence | Human Verification Needed |
+|---|---|---|---|---|
 
−Create this table:
+Recommend a stage only when stage-entry evidence or supplied definitions support it. Otherwise state that stage reconciliation is required. Never claim the CRM was updated.
 
−| Missing Information | Why It Matters | How To Ask For It |
−|---|---|---|
+## 12. Manager and revenue operations handoff
 
−## 13. Human Review Checklist
+Provide:
+- Deal-health rationale
+- Forecast confidence and its evidence limitations
+- Highest-priority qualification gap
+- Seller coaching point
+- One pipeline-review question
+- CRM or process reconciliation required
+- Escalations to product, solutions engineering, finance, legal, security, privacy, compliance, or leadership
 
−Before sending the follow-up or updating CRM, a human should verify:
+## 13. Missing-information plan
 
−1. Buyer name and spelling.
−2. Company name.
−3. Promised next steps.
−4. Pricing or budget references.
−5. Product claims.
−6. Legal, security, compliance, or financial claims.
−7. Dates and deadlines.
−8. Attachments or follow-up assets.
−9. CRM stage and forecast notes.
−10. Tone of the follow-up email.
+| Missing or Conflicting Information | Decision Affected | Why It Matters | Best Person to Ask | Neutral Question | Required Before External Action |
+|---|---|---|---|---|---|
 
−## Verification
+Prioritize questions that change qualification, fit, commercial terms, stakeholder access, or the next-step decision.
 
−Before finalizing, confirm that:
+## 14. Verification and acceptance record
 
−1. Buyer statements are separated from sales interpretation.
−2. No facts, commitments, budget, metrics, or competitors were invented.
−3. All recommendations are tied to the discovery notes.
−4. Missing inputs are clearly listed.
−5. The follow-up email is specific to the buyer.
−6. The CRM update is concise and usable.
−7. Risky claims include a human review step.
+| Check | Expected Condition | Actual Observation From Supplied Material | Status | Evidence or Required Correction |
+|---|---|---|---|---|
+| Buyer statements traceable | Material claims map to evidence IDs | | Pass, Fail, or Unverified | |
+| Facts separated from interpretation | Inferences and assumptions are labeled | | Pass, Fail, or Unverified | |
+| No invented commercial signals | Budget, authority, urgency, and commitments are supported | | Pass, Fail, or Unverified | |
+| Product claims controlled | Capabilities and fit rely on supplied evidence | | Pass, Fail, or Unverified | |
+| Next-step state accurate | Agreed, proposed, and completed actions are distinct | | Pass, Fail, or Unverified | |
+| Buyer draft safe | Recipient, claims, tone, assets, and sensitive content are reviewed | | Pass, Fail, or Unverified | |
+| CRM mapping reconcilable | Values map to the supplied schema and stage rules | | Pass, Fail, or Unverified | |
+| Dates and owners supported | Timing and ownership are evidenced or marked proposed | | Pass, Fail, or Unverified | |
 
−## Final Instruction
+Finish with an acceptance state:
+- Ready for human review
+- Partial and requires clarification
+- Blocked pending source evidence
 
−Begin now. If the discovery notes are too incomplete to produce a useful debrief, ask for the missing information first. If there is enough context, produce the full output in the requested markdown format.
+Then list the exact human approvals required before sending the follow-up or changing CRM data.