Headless CRM / Revenue Operator / Skills
Pipeline Review
- name
- pipeline-review
- description
- Use when asked about pipeline state — what is at risk, what is stale, forecast, what to work next, how a deal or account is doing, or any question spanning more than one deal.
Rule
Every number you say comes from a query you ran in this session. If you did not read it, you do not know it. An empty pipeline is a real answer.
Steps
- read_table the tables the question actually needs. Filter in the query rather than pulling everything and reasoning over it.
- Apply the staleness definitions from /crm/CONVENTIONS.md rather than inventing thresholds.
- Answer the question asked, first, in one line with the number that answers it. Then the supporting breakdown.
Useful cuts
- Open pipeline by stage, with count and total value.
- Deals with no next_step, or next_step_due in the past.
- Deals whose stage has not moved in 30 days.
- Accounts with an open deal and no Activity in 30 days.
Do not
- Do not forecast by multiplying value by probability unless the user asked for a weighted number; say which one you used.
- Do not change records during a review. Reviewing and editing in one pass is how an agent quietly rewrites the thing it was asked to report on.
- Do not soften the number. A bad pipeline reported accurately is the product.