Review pipeline stage age against team rules and identify stalled deals, weak next steps, stale records, and owner actions.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this on a CRM export or deal table.
Get the team's stage definitions and age limits. Record the report time, stage entry date, last customer action, next step, next-step date, owner, amount, and close date source. Flag repeated close-date moves only from close-date change history; without it, mark that check insufficient data. Do not apply generic limits when the team has its own.
Use within limit, due for review, stalled, or insufficient data. Flag missing or past next-step dates, repeated close-date moves, stage changes with no customer evidence, and records whose last activity is internal only.
Rank by age breach and deal impact. For each flagged deal state the dated facts, why it is flagged, the question that must be answered, owner, and next action. Show totals by stage and owner, but keep the deal rows available for audit.
Do not change stages, close dates, forecast classes, or owners. Do not treat record age alone as proof that a deal is lost.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.