Review the sales pipeline and prepare the day’s priorities
Inspect CRM records together with permitted correspondence, meeting notes and calendar evidence. Highlight deal changes, unresolved next steps and conflicting status for the owner to review.
How this works
Inspect customer-system records on a schedule and highlight deals, follow-ups, and data issues needing attention.
Review pipeline records for operational attention rather than predict deal outcomes. Compare CRM state with permitted correspondence, meeting notes and calendar evidence. Stale stages, absent next steps and conflicting records are reasons to ask the owner, not proof that a deal is lost.
Before you start
Review scope and owner
Choose the pipeline, review cutoff, permitted sources and person who accepts the daily brief. Use authorized exports when connectors are unavailable.
Stage and activity rules
Use documented stage definitions, review intervals, business calendars and owner assignments. A planned decision date may explain a long stage age.
Source coverage
Identify which CRM, email, meeting and calendar records can be read for these deals. Missing source access remains a coverage gap.
Prepare the inputs
- pipeline_snapshot
- Required
Deal IDs, account IDs, stages, owners, stage-entry dates, expected close dates and recorded next actions.
Record extraction time, filters and complete scope; preserve separate deals within one account.
- stage_rules
- Required
Expected evidence and review intervals
Use the organization’s agreed definitions.
- owner_map
- Required
Deal owner and escalation route
Keep unassigned records visible.
- review_window
- Required
Schedule and cutoff
Avoid mixing snapshots from different periods.
- activity_evidence
- Optional / conditional
Permitted correspondence, meeting notes and calendar records with deal links, participants and timestamps.
Needed for cross-source findings. Separate customer replies from seller outreach, proposed dates from confirmed bookings, and bookings from completed meetings.
- prior_snapshot
- Optional / conditional
Previous pipeline snapshot with the same scope and definitions.
Required to report movement between reviews. Without it, describe current state rather than inventing newly moved deals.
Implementation, step by step
Freeze the current pipeline and comparison scope
- Retrieve the selected pipeline and save its cutoff, filters and extraction time. Reconcile counts and retain records with missing owners or identifiers.
- If comparing reviews, match deals by stable ID and classify new, stage-changed, closed and missing records separately. A disappearing row may reflect a changed filter, not a closed deal.
Checkpoint: Current coverage and any valid comparison population are explicit.
Connect deal state to recent activity
- Read permitted linked correspondence and meeting notes for the selected deals. Capture the latest customer reply, stated blocker, agreed next step and supporting reference.
- Check calendar milestones separately. Retain CRM and conversation conflicts; a recent seller email does not establish customer engagement, and a booked meeting has not necessarily occurred.
Checkpoint: Each cross-source finding identifies the correct deal, timestamp and evidence.
Apply the agreed review rules
- Identify stale stages, missing next steps, repeated date changes and contradictory required fields using the supplied rules. Record the specific condition behind each flag.
- Check later replies and agreed future decision dates before labeling silence or delay. Keep incomplete activity coverage unknown; do not infer loss, churn or salesperson performance.
Checkpoint: Each flag is supported by a rule and current evidence rather than record age alone.
Prepare a focused daily brief
- Group deals into evidenced movement, owner attention and data correction. Prioritize using approved urgency rules and state the next question or action.
- Show the customer statement separately from internal interpretation. Include verified future milestones and unresolved ownership without forcing every deal into a healthy or unhealthy label.
Checkpoint: The brief explains what changed, what needs attention and why.
Let owners resolve conflicts and select follow-ups
- Give owners the relevant references and proposed questions. Keep their confirmed status or correction distinct from an automated flag.
- When requested, draft a follow-up from the current thread and agreed next step. Do not invent a deadline, promise, recipient or customer commitment; keep sending within separately established authorization.
Checkpoint: Owner decisions and optional drafts are reviewable without changing deal stages.
Refresh and hand off the reviewed result
- Refresh material records changed since the cutoff or label them stale. Preserve corrections and the comparison basis for the next review.
- Return the brief, unresolved questions and any requested drafts. Record externally applied actions only with receipts; stage changes and closing a deal remain under owner control.
Checkpoint: The handoff distinguishes observed activity, proposed follow-up and confirmed owner action.
Decisions along the way
A stage is old but a future decision date is agreed.
Show the context and avoid automatically marking the deal unhealthy.
A deal has no owner.
Route to the designated assignment queue rather than inventing responsibility.
Snapshot retrieval is incomplete.
Label coverage partial and avoid comparing totals with a complete prior day.
The CRM says no next step but a customer-confirmed meeting exists.
Show the calendar reference and propose a record correction; do not overwrite the CRM automatically.
A seller sent several messages but no customer reply is visible.
Report seller outreach separately from customer response and disclose any missing inbox coverage.
A calendar milestone was moved more than once.
Present the dated changes and any stated reason for owner review; do not infer the deal will fail.
What you will produce
sales-pipeline-health-brief-result.json
JSONA daily pipeline-health brief. Label proposed and completed states separately.
Include: deal_id · flag · supporting_fields · stage_age · next_step · owner · review_question · status · evidence_reference · review_note · latest_customer_activity · next_milestone · source_conflicts · change_state · coverage
sales-pipeline-health-brief-review.md
MarkdownOwner questions, evidence conflicts and optional requested follow-up drafts. A draft is not a sent message.
Include: source_reference · question · owner · next_action · follow_up_draft · draft_status
Check the result
- Check every flag against a documented rule and the latest accessible customer evidence.
- Reconcile deal counts, movement categories and unmatched owners without equating missing rows with closed deals.
- Verify that email threads, meetings and calendar events belong to the exact opportunity.
- Check that calendar bookings, completed meetings, customer replies and seller outreach retain distinct meanings.
When something goes wrong
Snapshot retrieval is incomplete
Label coverage partial and hold comparisons to a complete prior review; continue supported record-level checks.
An activity thread maps to several deals
Keep it unassigned until a stable reference or owner confirms the correct opportunity.
The owner reports activity outside accessible sources
Record the dated owner confirmation and coverage gap; do not claim the system independently observed that activity.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Prepare the daily review with current CRM, correspondence and calendar evidence.
Inputs
Synthetic: D2 has been in evaluation 20 days, but the customer agreed a decision on 15 October. Its CRM next step is blank; a confirmed review meeting is booked for 12 October. D3 has three seller emails, no visible customer reply, and no owner.
Expected result
Keep D2 as a milestone check and propose correcting its missing CRM next step, citing the customer reply and meeting. Route D3 to assignment and response review; three outbound emails do not establish engagement. Do not declare either deal lost.
Run a small pilot
Start small
Review two daily snapshots containing a planned long stage, a changed milestone, missing ownership and partial inbox coverage.
Record the baseline
Record manual preparation time, unsupported flags and owner corrections on the same deals.
Agree success criteria
Every priority item has a rule and source; movement totals reconcile and owner corrections are preserved.
Stop or revise
Pause affected comparisons if changed filters, wrong deal links or missing activity sources create false movement or silence.
Keep the scope clear
- The assistant does not change stages or close deals automatically.
- A record’s age is a review signal, not a verdict about the customer or salesperson.
- Do not turn operational signals into forecast probabilities or change customer commitments without the responsible owner.
Check before using
Record age is not proof that a deal is lost. Verify missing context and keep stage changes under owner control.
Business activities
- Run sales conversations and proposals
- Review business performance
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Current pipeline records · Stage rules and ownership · Review schedule · Permitted deal correspondence, meeting notes and calendar evidence
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow