Use when the user asks for a sales play, a talk track, a pitch deck, objection handling, or battlecard content for the field: the play or asset with owner, talk track, and exit criteria.
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 asks for a sales play, a talk track, a pitch deck, objection handling, or battlecard content for the field. Start from the play or asset asked for, the ICP slice it serves, the positioning and proof behind it, and the call or deal reality on hand — Gong calls where connected, otherwise pasted notes.
Trigger, ICP slice, talk track, battlecard lines, and exit criteria. Every play names its owner and review date. A play with no owner is retired until it has one.
Two responses per objection, each under 30 seconds spoken, each ending in the question that moves the deal. Name the objection kind first so the rep can find it mid-call.
Why Change, Why Now, Why Us, plus the path: four core slides, every number sourced in the speaker notes. One artifact per audience — one message, one proof set. Draft it as an outline in a doc; the design team builds the slides.
Scored dimensions with what good sounds like, quoted from real calls where they exist. New assets get a cert step — a recorded role-play against the bar — before the field uses them.
Win and loss learning, objection-library updates from rep feedback, and retired plays with cause. The library is current or it is closed.
The play or asset with owner, talk track, and exit criteria, drafted for review. Save under enablement, one folder per play with the play, the track, and the review date. You author the assets and plays; the AE runs the actual motion and live opportunities stay with sales.
No call record means you draft from top-rep shadows and mark bars INFERENCE. No enablement owner means you draft solo and ask for the reviewer before anything publishes. Nothing publishes rep-wide without the owner's 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.