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.
中文简介正在准备中。当前显示原文说明。
Use when a deal needs its buying center mapped, a new thread opened, or a single-threaded deal rescued before it stalls.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Use this when a deal needs its buying center mapped, a new thread opened, or a single-threaded deal rescued before it stalls.
The account name, the deal sheet with qualification state, the names already in their notes, and anything pasted such as a thread, attendee list, or org chart.
Start from the names they already have. Someone in their notes matters more than anyone found cold. Confirm each title from a source you can link: the company's team page, a profile the person keeps, or a press release.
Tag each person champion, economic buyer, end user, executive sponsor, technical buyer, legal/procurement, gatekeeper, influencer, evaluator, blocker, coach, or unknown. A champion proves out only when they sell inside the room and open the buyer door — enthusiasm alone is a coach. Economic buyer needs a named person plus a buyer quote. Mark per-person sentiment (champion, neutral, skeptical, blocker) plus an influence band, and hold empty roles open as named placeholders.
Say the gaps out loud: which roles have nobody, which named person you know nothing about, and the buyer-access test — a deal with no path to the economic buyer closes far less often, so name the path or the gap. Aim by deal size: four-plus engaged threads over $50K, five to seven with dual sponsors over $150K.
Open the next thread with an evidenced-only warm path: rank High/Med/Low from public connections only, never invented mutuals, and draft the connector ask as text they approve first. Equip the champion with a pack for the internal sell: one forwarding line, a one-page ROI summary, an exec summary, and the objection answer for the CFO and procurement. Never go around the champion without their permission.
Show the map in chat with thread state per person (open, met, engaged, stalled), take one round of edits, then save it. Re-run when a new name shows up.
Output: the stakeholder map with roles, gaps, warm paths, and the next-thread drafts, saved to file.
A person with no public footprint gets "not findable publicly" in their row. Never guess a title, a reporting line, or a contact. A stealth team means you ask the user to name one insider.
Approval gate: connector asks and champion lines are drafts only, never sent without your explicit yes.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
中文简介正在准备中。当前显示原文说明。
Write ad variants that each test one idea, within platform limits and supported claims.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
中文简介正在准备中。当前显示原文说明。