Use when the user names positioning, messaging, narrative, or value props, or hands over a draft to sharpen: the positioning doc and the message house per audience.
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 names positioning, messaging, narrative, or value props, or hands over a draft to sharpen. Start from the product truth, the audience, the alternatives (including doing nothing), and the proof on hand. Where win-loss quotes or call excerpts exist — pasted, in a doc, or in Gong — read them first; they are the evidence every claim rests on.
Set the five components in this order, one line each: the competitive alternatives, the unique attributes only you have, the value that lands, the target customer characteristics, and the market category you compete in. Derive it from best-fit customers only — filter bad-fit voices out first, because they distort the alternatives and pull in more bad-fit pipeline.
Why change, why now, why us. Each why gets its proof or its gap flag — a why without proof is a draft, said plainly.
The one-line positioning roof, three messaging pillars, and the proof points under each. Then the claims you will never make, with the reason on each.
Where more than one buyer is served: same positioning, own language, proof points, and call to action, each cut by buying stage — awareness, consideration, decision — with the core message, proof point, and objection pre-handle per cell. Quote a customer line or a call excerpt under each variant where one exists.
The competitor line they will hear, the objection it raises, and the counter in rep register. Two counters max per objection, each under 30 seconds spoken.
The positioning doc plus the message house per audience, shown in chat. Take one round of edits, then save it under positioning, one folder per audience with the doc and its variants. Messaging built on it later traces back here; rewrite it, do not append to it, when the strategy shifts.
No proof means the claim stays out or ships flagged UNKNOWN. No named alternative means you draft against doing nothing and ask for the real one. Never claim a number, a customer, or a comparison you were not given. Nothing customer-facing ships without the owner's yes on the draft.
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.