Objection Log Analysis
Turn call notes into patterns and fixes.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Analyze our objection log. Log data (date, deal, stage, objection in the buyer's words, outcome, rep notes): [PASTE_OBJECTION_LOG]. Our sales stages: [SALES_STAGES]. Product and pricing context: [PRODUCT_AND_PRICING]. Return: 1. A coding table: Theme (price, timing, authority, risk, competitor, fit, process, trust, other) | Count | Share | Stage where it appears | Win rate when it appeared (compute from the data) | Example quote. 2. The top five themes by frequency and by impact on win rate; note that correlation is not causation. 3. For each top theme, a root-cause hypothesis (is it a messaging problem, a pricing problem, a product gap, a qualification problem?) and a test. 4. Recommended changes: messaging, collateral, qualification criteria, product feedback, training topics. 5. A list of objections that are actually signals of poor fit (and what to do earlier). 6. A dashboard layout and a monthly review agenda. Show the arithmetic for shares and win rates. If the log has fewer than 30 entries, say that patterns are tentative. Do not invent log entries.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.