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.
Use when the user needs the right people inside a named account: who decides, who influences, and how to reach each one.
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 the user needs the right people inside a named account. Start from the company name, the account brief when one exists, and who the user already knows there.
Rank contacts director-plus first: economic buyer, champion, technical evaluator, procurement or legal, then users and coaches. Each entry carries name, title, role tag, and a dated hook with a source URL when one exists. Apply the buyer-access test: a deal with no path to the economic buyer closes far less often, so name the warm path or the gap. A champion proves out only when they will sell inside the room and open the buyer door — enthusiasm alone is a coach.
Confirm each title from a source you can link: the company's team or about page, a profile the person keeps themselves, or a press release naming them. Deduplicate against the target list and against CRM ownership the user confirms, and say who you skipped and why.
No patterned emails, no assumed profile URLs. A contact goes in only when published and linkable; otherwise the field stays blank with UNKNOWN.
Show the ranked table in chat with one line per person on why they made the list, take one round of edits, then append the new rows to the target list as new.
The ranked decision-maker table saved as target-list rows, with gaps named.
No verifiable buyer means you name the closest reachable title and the warm path to ask for (a referral line is drafted, never sent). A stealth or tiny team means you ask the user to name one insider. Drafts to these people wait for your yes.
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.