Use when an account needs a running executive program: C-level connects, sponsorship gaps, briefings, and governance cadence.
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 needs a running executive program. Start from the account with its stakeholder map, the named exec sponsors on both sides, the sponsorship gaps, the last exec touch with date, and the next business review on the calendar.
Select key accounts on a weighted 1-10 scoring matrix across fit, size, revenue potential, process, tenure, solvency, relationships, and geo; start small with the top scorers. Every key account gets a role-tagged stakeholder map with the champion, economic buyer, technical evaluators, and blockers, plus a key-account plan holding the account's top priorities and needs, shared with internal stakeholders. Anything that leaves for an external stakeholder carries the minimum customer data the conversation needs, approved by the account owner and redacted first — never a link to everything held on the account. Label each exec thread mapped, engaged, or sponsoring. A sponsoring exec is a named person with evidence of advocacy, not a friendly title. Where a key-account manager takes over, run a full sales-to-key-account-manager handoff so none of the sales conversation is lost.
Name the sponsorship gaps plainly: which buying-center roles have no engaged exec, which single-threaded bets risk the deal, and which exec relationships went stale past 30 days. One gap, one close plan, one owner, one date.
Run the C-level connect program: dated touches per exec per quarter, each with a business topic, not a check-in. Peer-match every connect by seniority — your exec meets theirs — brief your sponsor the night before with logistics, company, contact, deal terms, agenda, and goal, then intro, set the agenda, and mute. Every touch ends with the next one dated. Follow every touch with a sourced recap: what they said, what it means, what moves next. Keep the sponsor on every subsequent thread until the deal closes.
Plan each executive briefing center visit and business review as a pack: the Why Change, Why Now, Why Us arc, the value delivered to date in FACT numbers, the decisions needed, and the follow-through with owners and dates. No pack, no briefing.
Hold account governance cadence with customer execs: a dated rhythm of reviews with shared success criteria and a joint issue log. Escalations go through the sponsors first, with the issue, the ask, and the date.
Key-account plans with scoring record, the sponsor-state map with dated gap closures, the executive connect calendar, the briefing pack with follow-through, and the governance cadence.
No stakeholder map means you build one from the CRM and call record and mark threads INFERENCE until verified. No exec access means you draft the warm-path ladder with evidence-only intros and ask for the first intro. Nothing goes to a customer exec without your explicit 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.