Review the pipeline every Monday

A one-screen Monday plan from the CRM: slipped dates, deals with no next step, stale deals, concentration risk and five moves.

Works inClaudeClaude CodeCodexCursorGemini CLIGitHub CopilotChatGPTNeeds: CRM accessv1.0 · November 20, 2026
weekly-pipeline-review/SKILL.mdDownload
name
weekly-pipeline-review
description
Use this skill when a seller or sales leader runs the Monday pipeline review. It reads the CRM and returns a one-screen plan: close dates that slipped, deals with no next step, stale deals, concentration risk, data gaps and the five moves for this week. Thresholds sit at the top and can be changed.
license
CC-BY-4.0

Review the pipeline every Monday

This skill reads the open pipeline and returns one screen: what slipped, what has no next step, what has gone stale, where the pipeline depends on too few deals, and the five moves that matter this week. Use it on Monday morning, alone or before the team meeting. It proposes CRM changes; it applies none without approval.

Inputs

  • CRM access (read) to open deals and their activities. Without it, ask for a CSV export of open deals with: deal name, account, owner, stage, amount, close date, created date, last activity date, next activity date and, if the CRM has it, the date the deal entered its current stage.
  • Scope: one seller, a team or a pipeline. Default: the deals owned by the person asking.
  • Thresholds, which the user can change. Defaults: stale means no activity in 14 days (7 days for deals in proposal or later); stuck means more than 30 days in the same stage; concentration means one deal above 30% of the open amount, or one account above 40%.
  • Last week's review (optional), to show what moved.

Steps

  1. Print the thresholds first, in one line, so the user can change them before reading the numbers.
  2. Total the pipeline. Count, open amount, and what closes this month. Use the CRM's own probability field for a weighted figure only if it exists; never invent probabilities.
  3. Slipped close dates. Open deals with a close date before today. If the CRM keeps field history, also list deals whose close date moved later in the last 7 days and how many times it has moved. Without history, say "close date history not available" instead of guessing.
  4. No next step. Open deals with no task or activity dated in the future. Sort late stages first.
  5. Stale and stuck. Deals past the stale threshold, and deals past the stuck threshold. A deal can be on both lists; show it once, with both labels.
  6. Concentration. Share of the open amount held by the largest deal and the largest account. For a team, also the share held by each owner. Flag anything above the thresholds in one sentence that says what happens if it slips.
  7. Data gaps. Count the open deals with no amount, no close date or no contact. They distort every figure above, so name the count and the five largest.
  8. Choose five moves. Each move is one deal, one action, one owner, one date and a dated reason. Order: late-stage deals with no next step, then slipped deals where the buyer gave a real date, then stuck deals to requalify. A deal with no activity for over 60 days and no reply to the last two touches is proposed for closing as lost, with the reason.
  9. Compare with last week when the previous review is available: what closed, what moved stage, which flags cleared.
  10. Propose CRM changes as a numbered list: new tasks for the five moves, close dates to correct, deals to close as lost. Apply only the numbers the user approves.

Output

Keep it to one screen: at most five rows per list, then a count of the rest.

Pipeline review · week of Monday 2026-11-23 · owner: you
Thresholds: stale 14 days (7 from proposal on) · stuck 30 days in stage ·
concentration 30% per deal, 40% per account

Open: 34 deals · $612,000 · 9 close in November ($148,000)

Slipped (6)
| Deal                         | Stage       | Close date | Moved | Last activity |
| Pinecrest, field pilot       | Proposal    | 2026-11-15 | 2x    | 2026-11-03    |
| ...                          |             |            |       |               |

No next step (5)
| Deal                         | Stage       | Amount   | Last activity |
| Vale Alto, fleet rollout     | Negotiation | $55,000  | 2026-11-12    |

Stale or stuck (7)
| Deal                         | Stage       | Days idle | Days in stage |

Concentration
Summit Ag Supply, warehouse rollout is 31% of the open amount ($190,000).
If it slips past December, the quarter misses.

Data gaps: 4 deals with no amount, 2 with no close date.

Five moves this week
1. Vale Alto, fleet rollout · book the pricing call · you · by Tue 2026-11-24 ·
   buyer asked for revised terms on 2026-11-12, no reply since
2. ...

Since last week: 2 closed won, 3 moved forward, 1 new stale.

Proposed CRM changes (nothing applied yet)
1. Task "Book pricing call", Vale Alto, due 2026-11-24
2. Close date Pinecrest field pilot: 2026-11-15 to 2026-12-15 (buyer's date in note of 2026-11-03)
3. Close as lost: Harbor Line, scanners (no activity since 2026-08-28, last two emails unanswered)
Reply with the numbers to apply.

Guardrails

  • Reads: open deals, stages, activities, notes and field history in the CRM, or the export the user provides.
  • Writes: nothing by default. With approval, tasks, close dates and stage changes from the numbered list.
  • Asks before: every CRM change, including closing a deal as lost.
  • MUST show the thresholds used, and recompute when the user changes them.
  • MUST give every move a dated reason taken from the record.
  • MUST say when a figure rests on incomplete data (missing amounts, no field history).
  • NEVER invent a probability, a close date or a buyer commitment.
  • NEVER close, delete or reassign a deal without a yes for that line.

Sources

Made by ALTARA, the AI sales agent your team texts. More skills: https://www.altaratech.com/toolkit

Use it with