Return My TimeBook a Discovery Call

Revenue Operations

Create a Pipeline Next-Best-Action Review

Prioritize evidence-backed next actions across supplied opportunities while exposing missing data, conflicts, and human decisions.

By Nick Spisak

Quick facts

Best for
Owners · Founder-operators · Sales leaders
Prompt type
Effectiveness
Expected result
A prioritized next-best-action table with evidence-backed reasons, missing evidence, timing, stop conditions, owners, proposed CRM changes, and deferred items.
Time saved
60-90 minutes per pipeline review
Required inputs
PIPELINE STAGE · PRIOR CONTACT HISTORY · VERIFIED OBJECTIONS · PROMISED ACTIONS · DECISION PROCESS · RELEVANT DATES · OFFER · CRM FIELDS · FOLLOW-UP OWNER
Works with
ChatGPT + Claude

What this prompt does

  • Ranks proposed follow-up work using only supplied stage, history, obligation, and timing evidence.
  • Shows the reason, missing evidence, stop condition, and named owner behind each recommendation.

When to use

  • During a recurring service-business pipeline review when owners need an explainable queue rather than an opaque model score.

When not to use

  • Do not use it to auto-prioritize people by protected traits, overwrite CRM data, or execute customer-facing actions.
  • Do not place unauthorized records or unnecessary personal, sensitive, or confidential data in an AI system.

The prompt

#CONTEXT:
Review one or more supplied service-business opportunities and draft an explainable next-best-action queue. Use only the supplied records. Recommendations are for human review and do not change a live system.

#INPUTS:
- Verified pipeline stage for each opportunity: [PIPELINE STAGE]
- Contact history, responses, channels, and consent facts: [PRIOR CONTACT HISTORY]
- Objections explicitly stated by each buyer: [VERIFIED OBJECTIONS]
- Actions explicitly promised by either party: [PROMISED ACTIONS]
- Known decision participants, criteria, and process: [DECISION PROCESS]
- Relevant dates, deadlines, and review window: [RELEVANT DATES]
- Approved service offer, scope, and claims: [OFFER]
- Supplied CRM fields, including blanks and conflicts: [CRM FIELDS]
- Named human follow-up owner or ownership map: [FOLLOW-UP OWNER]

#INSTRUCTIONS:
1. Create a verified evidence block for each opportunity. Preserve conflicts and blanks.
2. Do not invent, infer, or fabricate commitments, quotes, dates, objections, decisions, contact facts, or CRM state. Mark unsupported details Unknown and identify the missing evidence.
3. Recommend a next best action only when supplied evidence supports it. Otherwise recommend evidence collection or human review.
4. Prioritize seller obligations, supplied deadlines, buyer-requested actions, and unresolved record conflicts before speculative outreach.
5. Explain every priority using cited input facts. Do not create a probability, deal score, value, close date, or urgency level that was not supplied.
6. Do not rank or prioritize a person using a protected trait or a proxy for a protected trait.
7. For each row, provide reason, missing evidence, proposed timing, stop condition, named owner, and the human decision needed. Keep proposed CRM edits separate.
8. Use only authorized records in an approved AI workspace or approved AI vendor. Minimize the supplied data and redact or omit unnecessary personal, sensitive, or confidential data. Follow company retention and vendor policy.
9. Do not send, contact, schedule, update a live CRM, make a commitment, or present an offer. A named human owner must approve the exact draft and each consequential action before use.

#RESPONSE FORMAT:
## Source limits and conflicts
- Opportunity — verified evidence — Unknown or conflict — missing evidence

## Prioritized next-best-action table
| Priority | Opportunity | Verified stage | Proposed next action | Evidence-backed reason | Missing evidence | Proposed timing | Stop condition | Named owner | Human decision needed |
|---|---|---|---|---|---|---|---|---|---|

## Proposed CRM field changes
| Opportunity | Field | Current supplied value | Proposed value | Evidence | Approval required |
|---|---|---|---|---|---|

## Deferred opportunities
- Opportunity — why no action is supportable — evidence needed

## Review checklist
- Every priority traces to supplied evidence
- Unknowns remain visible
- Consequential actions and record changes await named human approval

Input checklist

  • PIPELINE STAGE
  • PRIOR CONTACT HISTORY
  • VERIFIED OBJECTIONS
  • PROMISED ACTIONS
  • DECISION PROCESS
  • RELEVANT DATES
  • OFFER
  • CRM FIELDS
  • FOLLOW-UP OWNER

Example input

Fictional example — PIPELINE STAGE: Juniper Facilities=Proposal reviewed; Alder Legal Operations=Discovery. PRIOR CONTACT HISTORY: Juniper replied July 28 by consented email; Alder completed a video call July 30; no other contact facts supplied. VERIFIED OBJECTIONS: Juniper=training time; Alder=two-hour workshop limit. PROMISED ACTIONS: Juniper seller owes an implementation outline by August 2; Alder seller owes a workshop option by August 4. DECISION PROCESS: Juniper operations director approves; Alder approver unknown. RELEVANT DATES: Review date July 31; obligations due August 2 and August 4; no verified close dates. OFFER: Northstar Workflow Assessment approved scope; no pricing supplied. CRM FIELDS: Juniper next_step blank; Alder close_date=2026-08-15 without source evidence. FOLLOW-UP OWNER: Juniper=Elena; Alder=Mina.

Expected output structure

  • A prioritized next-best-action table with evidence-backed reasons, missing evidence, timing, stop conditions, owners, proposed CRM changes, and deferred items.

Customize this prompt

  • Supply explicit priority rules if the team uses more than obligation dates and verified buyer requests.
  • Review proposed record edits independently from the action queue to avoid turning recommendations into hidden automation.

Guardrails

  • Do not invent, infer, or fabricate commitments, quotes, dates, objections, decisions, contact facts, or CRM state; mark unsupported details Unknown with the missing evidence.
  • A named human owner must approve every external send, external message, contact, and scheduling action before any action.
  • A named human owner must approve every live CRM record or account update before any update.
  • A named human owner must approve every commitment, promise, offer, price, policy exception, permission, and legal commitment before any action.
  • A named human owner must approve every payment, billing, financial, tax, or pricing decision before any action.
  • Use only authorized records in an approved AI workspace or approved AI vendor; minimize data, redact or omit unnecessary personal, sensitive, or confidential data, and follow company retention and vendor policy.
  • A named human owner must approve every deletion, closure, suspension, termination, revocation, deactivation, disablement, or archive action before any action.
  • Do not prioritize people using protected traits or proxies; the assistant must not execute actions or edit systems.

KEEP BUILDING

Related prompts

NEXT STEP

Next step

Map where revenue is leaking.