Back to the library

Workflow Library · Revenue

Sales Pipeline Workflow

Turn messy deal notes, stale CRM fields, and vague next steps into a tighter pipeline that actually moves after each conversation.

Summary

A sales-pipeline workflow for founders, closers, and lean revenue teams using AI to summarize calls, update stages, flag deal risk, and generate the next follow-up instead of letting pipeline admin stall momentum.

What this workflow gets you

Start with discovery notes, pipeline context, and a rough sense of the deal. Leave with a cleaned-up stage update, risk summary, follow-up message, and next action plan you can use the same day.

Step by step

The workflow outline

Each step is designed to reduce ambiguity between the raw input and the final deliverable, which is usually where generic prompt packs break.

Step 1

Capture the live deal context

Pull the current stage, buyer goal, blockers, budget signal, and decision timeline into one working brief before the deal gets buried across notes and CRM tabs.

Input

Call notes, CRM record, previous follow-up, and pipeline stage

Output

A deal brief with current status, stakeholder context, and buying signals

Step 2

Summarize the conversation into stage evidence

Prompt AI to separate polite talk from the signals that justify moving the deal forward, holding it in place, or marking it at risk.

Input

Deal brief plus transcript or call recap

Output

A stage recommendation with evidence, objections, and confidence notes

Step 3

Clean up the CRM update

Translate the conversation into the exact fields your team needs: opportunity notes, close probability, next meeting, owner tasks, and missing information.

Input

Stage recommendation and CRM field requirements

Output

A structured CRM-ready update with clear next actions

Step 4

Write the follow-up that keeps momentum

Generate a follow-up message that reflects the actual call, confirms the next step, and closes any ambiguity around timing or ownership.

Input

CRM update, buyer objections, and desired next meeting

Output

A post-call follow-up email or message with agreed actions and CTA

Step 5

Review the pipeline for risk and priority

Use AI to flag stalled deals, missing champions, unclear timelines, and the highest-value next moves so the pipeline gets triaged instead of merely logged.

Input

Updated deal record plus adjacent pipeline context

Output

A priority list with deal risks, escalation notes, and recommended focus

Example inputs and outputs

What the workflow looks like in practice

Sample prompt

Input

Turn this discovery-call recap into a pipeline update for a $12k services deal. Include stage recommendation, buyer urgency, known objections, next step, and a follow-up email that confirms the proposal deadline.

Output

A CRM-ready update plus a concise follow-up email that matches the actual conversation and moves the deal toward the next commitment.

Sample checklist

Input

Create a pipeline hygiene checklist for weekly deal reviews. It should cover stale stages, missing close dates, unclear next steps, absent decision-makers, and deals that need a re-engagement plan.

Output

A reusable sales-ops checklist grouped into data quality, buyer momentum, risk signals, and next-action review.

Workflow action

Input

Review these five active deals and identify which ones should advance, which ones need a follow-up today, and which ones are at risk of slipping based on the notes and last-contact dates.

Output

A ranked action list with stage recommendations, risk notes, and immediate follow-up priorities for the revenue owner.

Before and after

The difference between vague prompting and a reusable workflow

Before

Deals live in scattered notes, the CRM gets updated late, and the next follow-up depends on memory instead of a repeatable post-call process.

After

Each conversation turns into a clear stage update, a sharper follow-up, and a more accurate pipeline view, so momentum is easier to protect.

Related products

Use the workflow as the demo. Use the product when you need the full pack.

These pages are public by design. When you want the reusable prompts, examples, and deeper systems behind them, start here.

Why these pages convert better

They show the workflow, not just the promise.

Short promise and clear audience

Step-by-step input/output framing

Before/after proof plus product pathways