Assess an expansion opportunity from customer need and usage evidence without turning weak signals into a sales claim.
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 when an account may need more scope, seats, products, or services.
Look for an explicit request, repeated limit, new team or use case, sustained adoption near capacity, stated goal the current scope cannot meet, or approved account plan that cites one of these customer signals. An account plan with no documented customer signal is needs evidence. Cite the source and period. High usage alone is not permission to sell, and low usage is not an expansion case.
State the customer need, observed evidence, people affected, present workaround, possible fit, value hypothesis, disconfirming evidence, product or delivery gaps, and questions to validate. Mark price, availability, roadmap, and terms unknown unless approved sources support them.
Use ready to validate, needs evidence, or not a fit now. Recommend one customer question and one internal check.
Do not invent demand, savings, product capability, or customer intent. Do not promise an offer or send outreach without 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.