Use when a buyer pushes back on price, timing, competition, or terms, or when a deal needs its pricing and procurement plan.
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 a buyer pushes back or a deal needs its pricing and procurement plan. Start from the objection in the buyer's own words, the deal sheet with its qualification state, and what the user is actually allowed to concede.
Name it first: price, timing, authority, competition, status quo, or terms. Then run LAER — listen, acknowledge, explore, respond. Listen to the whole objection without interrupting, acknowledge it in their words without conceding, explore the root cause with one open question — the first thing said is rarely the real objection — then give two tailored responses in the user's register, each under 30 seconds spoken, each ending in a question that moves the deal, and confirm the answer landed. Never concede, discount, or promise terms inside a draft response. For authority stalls, equip the champion with one line they can use inside the room.
The ask line, a current-vs-proposal comparison with cited numbers only, the evidence behind it, and the concession you want in return. Every number is FACT with a source or it stays out. Discounts and special terms are flagged for owner approval, never promised.
Name each step (security review, legal redlines, procurement sign-off), its owner on both sides, and its date. Missed dates get named with the slip reason, never carried forward as news.
You play the buyer in their words, the user answers, and you grade the answer with one fix.
The objection type, the two responses, the counter or paper-process plan when needed, and the drill verdict when run.
An objection with no deal behind it means objection handling only, no pricing talk. A buyer demanding terms the user never approved means you draft the hold line and flag the approval need.
Nothing customer-facing and no pricing, discount, or term is promised 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.