AI-Assisted Sales Discovery Playbook: Build a Correctable Record

Discovery breaks when a seller finishes a call with many notes but no buyer-confirmed problem, evidence, or owner for the next decision. Use the five-step discovery card below to prepare, agree on the job, map evidence, choose one next decision, and confirm ownership. AI may assist with preparation and records; the seller owns judgment and commitments.

Completion standard

• Start state: an eligible buyer request with an assigned seller and approved context.
• End state: the buyer can correct a record of facts, unknowns, decisions, and one useful next action.
• Evidence: source-linked preparation, buyer corrections, accepted handoff, and dated action owners.
• Time horizon: prepare before the conversation; send the reviewed record within the team's approved service window.

Roles and prerequisites

Role	Owns	Approves	Receives handoff
Seller	Conversation and final record	Claims and next action	Buyer corrections
Sales manager	Question tree and QA	Exceptions	Coaching cases
Specialist	Domain evidence	Material commitment	Escalated question

Before starting, confirm purpose and permission, current source versions, a neutral question tree, record access, and a rollback path for proposed CRM changes.

In a small team, the seller may also perform the manager and record-review work. A true specialist is still required for material domain, price, security, legal, or contractual claims. First action: copy the five phase headings into a document and list three sourced facts plus three unknowns.

See the card in a completed run

A fictional operations lead, Huy, asks how to assess inconsistent qualification. Before the conversation, seller Sara completes the promised preparation record:

• Sourced fact 1: Huy's request asks for an assessment of inconsistent qualification (source: fictional request message R-17).
• Sourced fact 2: Team A's current approved process note uses definition A-3 (source: fictional process note PA-3).
• Sourced fact 3: Team B's current approved process note uses a different definition, B-2 (source: fictional process note PB-2).
• Unknown 1: Why the two definitions differ.
• Unknown 2: Whether the difference affects handoffs or results.
• Unknown 3: Who can approve a shared definition.

During the conversation, Sara verifies the definition difference but does not assume it causes lost revenue. Huy accepts ownership of a definition sample due 22 August 2026 ICT. Sara sends a source-linked summary; no product recommendation is made.

Phase 1: prepare a bounded hypothesis

• Owner: seller.
• Inputs: buyer request, approved account context, current sources.
• Actions: list three sourced facts, three unknowns, and a proposed agenda; label every inference.
• Output: preparation brief.
• Exit gate: every claim has a source or hypothesis label.
• Escalation/rollback: remove stale context; send unsupported domain claims to a specialist.

Phase 2: agree on the job

• Owner: seller.
• Inputs: preparation brief and buyer purpose.
• Actions: confirm time, agenda, current process, desired change, constraints, and permission to ask follow-ups.
• Output: buyer-approved discovery scope.
• Exit gate: the buyer confirms or corrects the job.
• Escalation/rollback: stop the script and reset scope when the buyer's purpose differs.

Phase 3: build the evidence map

• Owner: seller; AI may draft labels.
• Inputs: buyer statements and approved sources.
• Actions: separate confirmed fact, hypothesis, unknown, decision, and action; preserve source wording.
• Output: evidence map with provenance.
• Exit gate: no hypothesis is recorded as fact and every unknown has a disposition.
• Escalation/rollback: revert proposed CRM edits when provenance or identity is uncertain.

Atlassian's meeting-notes template separates context, decisions, and actions. It supports this record mechanism, not a sales-result claim. Review the template.

Phase 4: choose the smallest next decision

• Owner: seller; specialist approves material claims.
• Inputs: confirmed problem, evidence gaps, constraints.
• Actions: compare approved next steps; choose the smallest step that resolves a confirmed gap.
• Output: bounded recommendation or honest stop.
• Exit gate: buyer understands purpose, owner, and acceptance condition.
• Escalation/rollback: withdraw unsupported price, security, legal, or contractual language and route it to its owner.

Phase 5: confirm and hand off

• Owner: seller.
• Inputs: reviewed evidence map and next decision.
• Actions: read back corrections; show proposed record changes beside current values; assign dates and acceptance owner.
• Output: buyer-correctable summary and accepted action packet.
• Exit gate: recipient accepts ownership or the record shows no next action.
• Escalation/rollback: do not send or write disputed content; preserve the prior record and escalate unresolved ownership.

Use this handoff and quality card

Trigger	Severity	Owner	Required context
Unsupported material claim	High	Specialist	Buyer wording, source gap
Buyer disputes summary	Medium	Seller	Original note and correction
No action owner	Medium	Sales manager	Decision and candidates

Trigger	Respond by	If nobody can accept
Unsupported material claim	Before any commitment	State the limit
Buyer disputes summary	Before CRM write	Preserve prior value
No action owner	Before follow-up	Close with no action

QA checks: permission and identity; source/version labels; neutral questions; buyer corrections; dated owners; accepted handoff; no silent CRM overwrite.

Metric	Definition	Baseline	Decision threshold
Correctable record rate	Reviewed records the buyer can correct / reviewed records	Pilot sample	Set before expansion
Complete action rate	Actions with owner, date, and acceptance / all actions	Pilot sample	Set before expansion
Reversal rate	CRM writes reversed for factual/provenance error / CRM writes	Pre-pilot audit	Pause threshold set before launch

Metric	Review owner	Cadence
Correctable record rate	Sales enablement	Weekly pilot
Complete action rate	Sales manager	Weekly
Reversal rate	RevOps	Monthly

Early failure signals are leading questions, hypotheses promoted to facts, repeated buyer corrections, and unaccepted handoffs. Correct by narrowing the question tree, fixing sources, or returning ownership to the seller.

What to do after completion

Review the record upward with the lead-qualification guide, use the objection playbook for an evidence challenge, or create the accepted packet with the post-meeting template.

Evidence and limitations

No sales outcome, methodology superiority, recording permission, integration, or Easy AI capability is claimed.