Use Claude to Turn a Sales Pipeline Snapshot into a Reviewable Follow-Up Queue

A pipeline snapshot can tell you what needs attention without telling you what to send next. This worked prompt turns a small fictional CSV into a reviewable follow-up queue. It keeps the source evidence beside each suggestion and leaves missing ownership or timing visible.

Reader and decision: You are a sales manager deciding which follow-ups deserve human review today. The artifact is a queue, not an automatic outreach list.

Evidence label: Documentation-based and illustrative. Claude supports CSV uploads in chat, and Anthropic recommends clear instructions, sequential steps, examples, and XML tags for mixed instructions and input. The files and output below are fictional. No Claude run or personal test is claimed.

What you need

• Claude on the web or desktop.
• An approved, non-sensitive CSV that you are allowed to upload.
• A human reviewer who knows the sales process.

Claude’s help page says you can upload a CSV with the plus button, and that uploaded files can be used in an individual chat or a project’s Files section. Use a copy or fictional export while you refine the prompt.

Fictional input

Save this as pipeline-snapshot.csv:

account,stage,last_contacted,next_step,owner,signal
Northstar Retail,Evaluation,2026-10-21,"Send security questionnaire",Mina,"Asked about SSO"
Lumen Foods,Proposal,2026-10-10,"",,"Proposal opened twice"
Harbor Works,Discovery,2026-10-23,"Book technical call",Jon,"No date agreed"
Pine Systems,Negotiation,2026-10-18,"Confirm legal review",Mina,"Legal contact not named"

The blank next_step and owner fields are deliberate. Keep them unknown in the review, marked NOT STATED, rather than fill them from context.

The worked prompt

1. Open Claude and attach pipeline-snapshot.csv with the upload control. If the control or account access differs, use the surface documented in your account.
2. Paste this prompt:

<role>
You are a careful sales operations analyst. Prepare a queue for a human reviewer. Do not contact anyone, change a CRM, or invent missing facts.
</role>

<task>
Read the attached pipeline snapshot and create a Markdown table with these columns:
account, stage, last_contacted, stated_next_step, owner, signal, review_reason, missing_information, suggested_human_action.

Keep one row per source row. Copy source values exactly. Use NOT STATED for a missing value. Do not turn a signal into a fact, a plan into a completed action, or a suggested action into an approved task.
</task>

<rules>
1. Use only the attached CSV.
2. Give one short review_reason tied to a source field.
3. Put missing owner, date, contact, or approval details in missing_information.
4. Suggested actions must be conditional and must not include outreach copy.
5. End with a source coverage check: source row count, output row count, and any rows needing human review.
</rules>

<output>
Return the table, then a section called "Source coverage check", then a section called "Questions for the sales owner".
</output>

3. Compare every output row with the CSV. Remove any invented owner, date, commitment, probability, or reason before sharing the queue.

Illustrative output

This is an editor-written target, not a captured Claude result. The table is shown as copyable Markdown so a narrow screen does not squeeze nine columns into tiny cells.

| account | stage | last_contacted | stated_next_step | owner | signal | review_reason | missing_information | suggested_human_action |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Northstar Retail | Evaluation | 2026-10-21 | Send security questionnaire | Mina | Asked about SSO | `signal`: "Asked about SSO". | NOT STATED: questionnaire scope, due date, recipient, completion status, approval to send. | If the questionnaire is still needed, ask Mina to confirm its scope and timing before any send. |
| Lumen Foods | Proposal | 2026-10-10 | NOT STATED | NOT STATED | Proposal opened twice | `signal`: "Proposal opened twice". | NOT STATED: next step, owner, prospect contact, follow-up date, approval to contact. | If the sales owner decides a follow-up is appropriate, confirm an owner and next step before any outreach. |
| Harbor Works | Discovery | 2026-10-23 | Book technical call | Jon | No date agreed | `signal`: "No date agreed". | NOT STATED: technical-call date, participants, approval to schedule. | If a technical call is still needed, ask Jon to confirm a date before scheduling. |
| Pine Systems | Negotiation | 2026-10-18 | Confirm legal review | Mina | Legal contact not named | `signal`: "Legal contact not named". | NOT STATED: legal contact, review date, approval to contact legal. | If legal review is still required, ask Mina to confirm the contact and timing. |

Source coverage check

• Source: pipeline-snapshot.csv, four data rows. Output: four rows. Northstar Retail, Lumen Foods, Harbor Works and Pine Systems each appear once; no account is added or dropped.
• account, stage, last_contacted, owner and signal copy the CSV values. stated_next_step copies next_step. The two blank Lumen Foods fields are represented as NOT STATED, not filled with guesses.
• Rows needing human review: all four. Northstar Retail lacks recorded questionnaire scope, due date, recipient, completion status and send approval. Lumen Foods lacks an owner, next step and follow-up authorization. Harbor Works says “No date agreed”. Pine Systems says “Legal contact not named”. Any additional timing or approval detail in missing_information is also NOT STATED in this snapshot.
• last_contacted records a past contact date, not a deadline or proof that a follow-up is overdue. No source field establishes task completion or permission to send a message, schedule a call or write to a CRM.

Questions for the sales owner

• Northstar Retail: next_step says “Send security questionnaire”; signal says “Asked about SSO”. Is the questionnaire still needed? If so, what scope, due date, recipient and send approval should Mina confirm? Those details and completion status are NOT STATED.
• Lumen Foods: signal says “Proposal opened twice”; next_step and owner are blank. Who owns this row, should any follow-up happen, and who is an approved prospect contact? Owner, next step, prospect contact, follow-up date and contact approval are NOT STATED. Proposal opens do not supply those answers.
• Harbor Works: next_step says “Book technical call”; signal says “No date agreed”. Is a call still required? If so, which date and participants should Jon confirm, and is scheduling approved? Date, participants and approval are NOT STATED.
• Pine Systems: next_step says “Confirm legal review”; signal says “Legal contact not named”. Is legal review still required? If so, whom should Mina consult, and when? Contact, review date and contact approval are NOT STATED.

Acceptance checks

• The output has four rows, matching the four source rows.
• Each stage, last_contacted, next_step, owner, and signal value matches the CSV or is marked NOT STATED.
• No row contains a probability, invented contact, invented deadline, or outreach message.
• The missing owner and next_step values for Lumen Foods stay visible.
• A human can trace every review reason back to one source field.
• The table includes all nine requested columns, followed by Source coverage check and Questions for the sales owner.
• Every suggested action is conditional; the queue grants no outreach, scheduling or CRM-write approval.

Troubleshooting

• Claude writes a polished outreach plan: repeat that the artifact is an internal review queue and add Do not draft or send messages.
• Blank cells disappear: add a test row with two blanks and require NOT STATED in the output.
• The output drops a row: ask for the source and output row counts, then compare account names one by one.
• A suggestion sounds like a commitment: change Do to Confirm whether or Ask the owner whether.

Limits and next step

Do not upload personal data, confidential deal terms, or a live CRM export unless your organization’s rules permit it. A queue is a review aid. It is not evidence that a prospect is ready, interested, or overdue.

For a small follow-up queue, TRY this workflow with a fictional or approved export. SKIP automatic outreach and CRM writes. USE the output only after a sales owner checks each row.

For a technical way to validate structured output before a handoff, see the Claude Code JSON review lesson. For a weekly practical AI workflow, get The Weekly Verdict.

Sources

• Upload files to Claude
• Prompt engineering overview
• Claude prompting best practices