Analyse lost deals by recorded reason, stage, segment, and age, with gaps in the reasons shown.
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 for closed-lost deals over a stated period, from a dated export.
Count lost deals and their value. Then count how many have a loss reason, how many use "other" or a free-text note, and how many reasons were added long after the close date. If more than a quarter lack a usable reason, say so first; the breakdown will be weak.
Break losses down by:
Compare with won deals over the same period where you can. Quote rep notes or customer words only as written, with the deal id.
State what the records cannot show: reasons picked from a short list, deals lost before they were entered, and reps who log reasons differently. Suggest the smallest next check, such as five calls with lost buyers.
Never fill a blank loss reason with a guess or infer one from the amount. Do not edit deals in the CRM; propose changes to the reason list for approval.
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.