PromptZone - Leading AI Community for Prompt Engineering and AI Enthusiasts

Discovery, objections, and deal management

Deals are won and lost in conversations, not documents: the discovery call that never found the real problem, the objection answered with a feature list, the negotiation entered without a walk-away. Preparation is the only part of a conversation you control.

These prompts build that preparation from your real inputs — the actual notes, the actual objection, the actual pricing. Every one asks the model to commit to a recommendation and show its reasoning, and to say plainly when your inputs don't support an answer.

Curated

Answer an objection with only what's true

Craft a response to this objection using only the facts provided. Structure: acknowledge the legitimate core of the objection in one sentence (find it — every objection has one); answer with specific evidence from the facts, clearly separating what we know from what varies by customer; end with a verification step the prospect can run themselves (a pilot, a reference call, a document) rather than asking them to take our word. If the facts don't actually answer the objection, say that plainly and state what we'd need to provide instead — never paper over a gap. Objection: {{objection}} Facts: {{facts}}

Fill in: The objection as the prospect said it, and the verified facts you're allowed to use (results, pricing, references).

Known limits: An objection answered too smoothly reads as rehearsed — the verification step is what actually moves trust.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-nano

Input fixture
OBJECTION (from a VP Support evaluating Relay): "AI triage tools mislabel
edge cases. When a fraud complaint gets routed as a shipping question, that's a
lawsuit. We can't risk it."

FACTS: Relay routes with a confidence threshold — tickets under the threshold go to
the human queue untouched (threshold is customer-configurable; default sends ~20% to
humans). Misroute rate on the benchmark set is 1.8% at default threshold, all
recoverable via normal queue reassignment. Fraud/legal keywords force human routing
regardless of confidence (hard rule, not model-based). Pilots run on historical
tickets, so misroutes are measurable on THEIR data before anything touches the live
queue. Reference: Coastway Logistics support director available for calls.

Model output (unedited)

Acknowledgement: Your concern about AI triage mislabeling edge cases and the risk of a fraud issue being routed as shipping is legitimate.

What we know (facts applicable across customers)
- Relay uses a configurable confidence threshold. Tickets below the threshold go to the human queue; default is about 20% to humans.
- Misroute rate on the benchmark set is 1.8% at the default threshold, and every misroute is recoverable via normal queue reassignment.
- Fraud/legal keywords force human routing regardless of model confidence (this is a hard rule, not model-based).
- Pilots run on historical tickets, so misroutes are measurable on your own data before anything touches the live queue.
- Coastway Logistics’ support director is available for calls if you want to discuss in detail.

What varies by customer
- The threshold is configurable by you, so the actual misroute rate will depend on your chosen threshold and your data.
- The exact misroute rate you observe will differ from the 1.8% benchmark because it’s measured on your historical data.
- The need to reassign misroutes is universal, but the effort and speed of recovery depend on your queue setup and processes.
- The hard-rule for fraud/legal keywords remains in all configurations.

Verification steps you can run yourself
- Pilot on your own historical tickets: configure your threshold and run a pilot to measure how often misroutes occur and how easily they’re recovered in your workflow.
- Reference call: schedule a discussion with Coastway Logistics’ support director to review your data and confirm how fraud/keywords are handled in practice.
- Documentation check: request a concise data sheet or pilot results summary that lists the benchmark misroute rate (1.8% at default) and the recoverability to counter misroutes, so you can compare with your own data.

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

A proposal summary an exec actually reads

Write the executive summary page for this proposal. Order: their situation and cost of standing still, in their numbers (from the inputs — mark any missing number '[client number]' rather than inventing one); what changes with us, as outcomes not features; the investment, stated plainly with no asterisks; proof (the closest reference from our facts); the decision being asked for and by when. Write for an executive who reads only this page and makes a call — every sentence either informs the decision or gets cut. Begin your response with the summary itself. Inputs: {{inputs}} Our proof: {{proof}}

Fill in: The deal's numbers (their costs, your price, timeline), and your reference stories.

Known limits: An exec summary with invented client numbers gets fact-checked once and distrusted forever.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-mini

Input fixture
INPUTS: Prospect: Suncrest Solar, 300 field techs. Their stated numbers:
14% of appointments missed monthly; each missed window costs a re-roll (~$180 truck
cost) plus review damage (1-star reviews cite scheduling 3:1 over quality). Dispatch
runs on 3 tools + a spreadsheet; 6 dispatchers. Our quote: RouteHive at $54k/yr flat.
Implementation: 3 weeks, no field hardware. Decision asked: pilot 2 of 4 states for
Q4, decision by Sep 5.

PROOF: Alvarez Roofing (240 techs): missed windows 16%→6% in first quarter, verified
by their ops dashboard; reference call available. Solar-specific: none yet (say so
if relevant — honesty rule).

Model output (unedited)

Summary
Approve a Q4 pilot of RouteHive in 2 of Suncrest’s 4 states to reduce missed appointment windows (currently 14%), cut avoidable truck re‑roll costs (~$180 per missed window), simplify a 3‑tool + spreadsheet dispatch workflow handled by 6 dispatchers, and prove ROI — for an annual subscription of $54,000. Decision requested by Sep 5.

Situation and cost of standing still (Suncrest numbers)
- Field techs: 300.  
- Current missed appointment windows: 14% of scheduled appointments monthly.  
- Direct re‑roll truck cost per missed window: ~$180. Additional reputational cost from 1‑star reviews (scheduling cited 3:1 over quality) not yet quantified.  
- Dispatch complexity: 3 tools + a spreadsheet; 6 dispatchers managing dispatch.  
- Financial impact (what you can compute immediately): each avoided missed window saves ~$180; total monthly and annual savings = (current missed% − future missed%) × total monthly scheduled appointments × $180 — total monthly scheduled appointments = [client number].  
- Missing inputs needed to show exact dollar ROI now: total monthly scheduled appointments = [client number]; current annual cost attributed to 1‑star review damage = [client number]; dispatcher labor cost attributable to multi‑tool workflow = [client number].

What changes with RouteHive (outcomes, not features)
- Lower missed windows: in a comparable customer we converted 16% → 6% inside one quarter; expect similar absolute improvement (Suncrest: 14% → ~6%) as the pilot proves out.  
- Fewer truck re‑rolls and direct field cost reduction: every percentage point drop in missed windows reduces missed appointments by 1% of your scheduled volume and saves $180 per avoided re‑roll.  
- Fewer 1‑star reviews tied to scheduling: improved punctuality reduces scheduling complaints that currently outnumber quality complaints 3:1.  
- Simplified dispatch operations: eliminate the multi‑tool+spreadsheet workflow, reducing dispatcher friction and error rates (enables redeployment or slower headcount growth).  
- Fast proof: implement in 3 weeks with no field hardware; pilot captures measurable ops metrics in Q4.

Investment (stated plainly)
- RouteHive subscription: $54,000 per year, flat.  
- Implementation timeline: 3 weeks to live; no field hardware required. (Any additional implementation services or fees not specified here = [client number].)

Proof (closest reference)
- Alvarez Roofing (240 techs): missed windows reduced 16% → 6% in the first quarter after go‑live, verified via their operations dashboard; reference call available on request.  
- Solar‑specific customers: none yet (honest — no solar reference to date).

Decision requested (and by when)
- Approve a pilot of RouteHive covering 2 of Suncrest’s 4 states in Q4 so we can validate the outcomes above and produce a full ROI for company‑wide roll‑out.  
- Decision deadline: Sep 5. If approved, we will schedule a 3‑week implementation immediately to begin Q4 pilot measurements.

If you want a one‑line ROI plug‑in for your CFO, provide total monthly scheduled appointments and annual cost of dispatcher labor related to scheduling, and we’ll deliver a precise payback model before your Sep 5 decision.

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

Arm your champion for the internal fight

Your champion must sell this internally. From the deal context, write their ammunition: under 'The one-liner', how they should describe the purchase to an exec in a hallway; under 'The case', three arguments matched to what each named stakeholder cares about (from the context — finance argues differently than ops); under 'The objections they'll hit', the two most likely internal pushbacks with honest answers the champion can own; under 'What to ask for', the specific decision or meeting the champion should request. Everything grounded in the context — never invent ROI numbers; where a number is needed but missing, mark it '[their number needed]'. Context: {{context}}

Fill in: Deal context: the champion, the stakeholders and their concerns, the problem, your solution and price.

Known limits: Champions repeat your words under pressure — anything inflated here fails in a room you're not in.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-mini

Input fixture
CONTEXT: Champion: Jonas, enablement manager at Klarwerk, wants EchoLens
($38k/yr, 45 seats). Stakeholders: Priya (RevOps director) — cares about tool
consolidation and the Oct 1 Gong renewal deadline; CFO — post-down-round scrutiny,
approved a conversation-intelligence line item but flagged 'no tool sprawl'; VP Sales
(new, joined June) — measured on ramping 8 new AEs, board target is cutting ramp from
5 months to 3. Current state: Gong renewal quote covers 60 seats without coaching
module; adding Gong's coaching tier prices above EchoLens. Pilot data: none yet —
pilot scoping call is Thursday.

Model output (unedited)

The one-liner
- EchoLens gives us a cheaper, coaching-first conversation-intelligence option for 45 seats ($38k/yr) that can be piloted against the 8 new AEs to prove faster ramp without forcing us to upgrade Gong today — so we can protect the Oct 1 renewal window while testing a direct, lower-cost way to speed ramp.

The case — three arguments, tied to what each stakeholder cares about

- For Priya (RevOps director — tool consolidation + Oct 1 Gong renewal)
  - Argument: We can run a tight, time-boxed pilot of EchoLens that targets the exact need Gong currently doesn’t cover (coaching workflow). If successful, EchoLens replaces the coaching upgrade we’d otherwise add to Gong, so we achieve consolidation (one coaching tool, not two) rather than sprawl.
  - Ask I’ll own: I will deliver a seat map (who uses EchoLens vs Gong) and a clean off-ramp/replace plan before we commit to any Gong coaching spend. If pilot fails, we walk away and keep the current Gong-only setup.
  - Data point to confirm: exact Gong coaching upgrade price so we can compare total cost vs EchoLens (Gong coaching upgrade = [their number needed]).

- For the CFO (cost discipline after a down round; “no tool sprawl”)
  - Argument: EchoLens fits inside the approved conversation-intelligence line item and is lower-cost than adding Gong’s coaching tier ( EchoLens = $38k/yr for 45 seats ). We’ll run a scoped pilot with explicit KPIs and an automatic kill-switch so there’s no open-ended spend or vendor proliferation.
  - Ask I’ll own: I’ll structure the pilot to use the existing CI budget, publish success criteria up front, and include a contractual opt-out after the pilot. If it doesn’t move the needle, we walk away — no ongoing cost.
  - Data point to confirm: confirm whether the CFO needs the pilot to be zero-cost (trial) vs using part of the CI budget ([their number needed]).

- For the VP Sales (ramping 8 new AEs; board target: cut ramp from 5→3 months)
  - Argument: EchoLens is coaching-first and built to accelerate rep ramp through manager workflows, micro-coaching nudges, and targeted call feedback — we can pilot directly on the 8 new AEs and their managers to measure ramp improvement. This is a focused experiment to address the board metric without a full platform rip-and-replace.
  - Ask I’ll own: I’ll run a 6-week pilot (scoped to the 8 new AEs + their managers), track agreed ramp KPIs (time-to-first-close, quota attainment at 3 months, coaching frequency — exact metrics to be confirmed with you), and deliver a one-page scorecard for the exec review.
  - Data point to agree up front: the concrete KPI targets that will count as “success” for ramp reduction (e.g., acceptable improvement vs baseline = [their number needed]).

The objections they'll hit — two most likely pushbacks and honest answers Jonas can own

- Objection 1 — “We can’t add another vendor; CFO said ‘no tool sprawl’.”
  - Honest answer Jonas can own: Totally fair — this pilot is explicitly scoped as a potential replacement for the coaching capability we currently don’t have in our Gong renewal. I will:
    - Deliver a seat-by-seat map and integration plan within 48 hours of pilot approval showing how EchoLens would replace a Gong coaching upgrade (or show why it complements vs duplicates).
    - Negotiate pilot terms with a contractual opt-out and a clear conversion clause so there is no surprise ongoing spend.
    - If pilot fails vs agreed KPIs, we cancel EchoLens and keep the current Gong setup. No tool sprawl, no open-ended subscriptions.

- Objection 2 — “We don’t have proof EchoLens will cut ramp — we have no pilot data.”
  - Honest answer Jonas can own: Correct — we don’t yet have pilot data, which is why I’m asking to run a tightly scoped experiment. I’ll:
    - Start the scoping call Thursday, launch a 6-week pilot focused on the 8 new AEs + managers, and lock the KPIs now with the VP Sales.
    - Deliver interim weekly metrics and a final one-page scorecard showing whether we achieved the agreed ramp signals. If the results don’t meet the pre-agreed threshold, we won’t expand and we won’t renew.
    - If the execs want confidence before any contract, I will negotiate a limited pilot agreement (trial or pro-rated short-term license) rather than an immediate annual commitment.

What to ask for (specific decision / meeting to request)
- Ask: Greenlight a time-boxed pilot.
  - Request language Jonas should use to the execs: “Approve a 6‑week pilot of EchoLens scoped to the 8 new AEs and their managers, using the approved CI budget, with a mandatory executive review (Priya, CFO, VP Sales) the week after pilot completion to decide whether to convert to the 45-seat $38k/yr subscription or to walk away.”
- Commitments Jonas will get at that meeting:
  - Priya: agreement to pause any Gong coaching spend until pilot results are reviewed (or confirm what Gong spend threshold we must not exceed — [their number needed]).
  - CFO: agreement that pilot uses the existing CI allocation and includes an opt-out/kill-switch if KPIs aren’t met.
  - VP Sales: sign-off on the KPI success criteria for ramp improvement and permission to run the pilot on the 8 targeted AEs.
- Immediate next step Jonas should take after the scoping call Thursday:
  - Send a one-page pilot plan within 24–48 hours: seat map, KPIs (we’ll list proposed KPIs and ask stakeholders to confirm), pilot dates, and the exact decision date for the post-pilot exec review.

If you want, I can draft the one-page pilot plan Jonas should circulate after Thursday’s scoping call (seat map + proposed KPIs + decision-date template).

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

Decode what 'too expensive' actually means

The prospect said it's too expensive. From the deal context, diagnose which kind of price objection this most likely is — no budget exists, budget exists but value unproven, cheaper competitor anchoring, or a negotiation opener — and commit to one diagnosis with the evidence from the context (labeled 'Diagnosis:'). Then write the response for THAT diagnosis: each type gets a different move (qualify out honestly, build a value case on their numbers, reframe the comparison, or hold with a concession path). Never respond with an unprompted discount. If the context can't distinguish between two diagnoses, give the one question that would. Context: {{context}}

Fill in: The deal context: what they said exactly, deal stage, who said it, your price, and what they use today.

Known limits: Misdiagnosis is expensive in both directions — discounting a value problem trains bad buying; value-casing a no-budget prospect wastes a quarter.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-mini

Input fixture
CONTEXT: EchoLens deal with Klarwerk (180-person B2B analytics). Quote:
$38k/yr for 45 recorded seats. After the proposal review, their RevOps director said:
"Honestly this is 40% over what we planned. Gong's renewal offer came in lower than
your quote." Known: their Gong renewal covers 60 seats but excludes the coaching
module (their stated priority for ramping 8 new AEs); decision deadline Oct 1; the
CFO approved 'a conversation intelligence line item' in H2 budget (per the director,
last call). Champion (enablement manager) strongly prefers EchoLens coaching flows.

Model output (unedited)

Diagnosis: Cheaper-competitor anchoring.

Evidence:
- The director’s comment: “this is 40% over what we planned. Gong's renewal offer came in lower than your quote” — they’re explicitly anchoring to Gong’s price.
- Gong renewal covers 60 seats but explicitly excludes the coaching module — and the team stated coaching is their priority for ramping 8 new AEs.
- CFO already approved “a conversation intelligence line item” for H2 and the enablement champion strongly prefers EchoLens coaching flows — so budget and value interest exist, but the comparison is currently apples-to-oranges.

Recommended reply (reframe the comparison)
Hi [Name],

Thanks — I hear you on cost. One important point I want to make up front: Gong’s renewal and our quote aren’t the same product. Your team told us coaching flows are the priority for ramping the 8 new AEs — that coaching capability is included in our $38k/yr proposal (45 recorded seats). From a raw seat math perspective that’s ~$844/seat/year, but the real decision point here is whether the coaching module shortens ramp and drives earlier quota attainment for those 8 AEs — something Gong’s renewal wouldn’t deliver.

I don’t want the price comparison to obscure outcomes. Two quick next steps I can do in a 20‑minute call before your Oct 1 decision:
1) Run an apples‑to‑apples, outcome-focused comparison (EchoLens with coaching vs. Gong renewal without coaching) that shows time‑to‑payback for the 8 new AEs. For that I’ll need either your typical new-AE ramp time and expected quota, or I can use benchmark assumptions and show sensitivity to those numbers.
2) Or, if you prefer, I’ll produce a coaching-focused alternative quote (scope: coaching for the 8 ramping AEs) so you can compare the exact spend tied to the priority outcome — not an across‑the‑board seat count comparison.

Which would you prefer? If the ROI comparison, please send (or have handy on the call) these numbers:
- Current average ramp time for new AEs (weeks)
- Typical annual quota or ARR per AE
- Targeted improvement in ramp (if you have a target) or we can model 2/4/8-week improvements

I’ll prep the side‑by‑side and show the revenue/QA impact so you can see whether the up‑front delta vs Gong is justified by faster ramp and better AE performance.

Thanks — happy to jump on a 20‑minute call today or tomorrow. — [Your name]

Notes for internal use: do not offer a discount now; focus on quantifying ramp improvements and converting to an apples‑to‑apples coaching-only or ROI-based comparison.

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

Diagnose why a deal went quiet

This deal stalled. From the timeline, diagnose the most likely cause — champion lost power, priority shifted, a stakeholder objected off-stage, budget cycle, or we were the free education for a decision already made — and commit to one primary diagnosis with the timeline evidence (labeled 'Diagnosis:'), plus the strongest alternative and what would distinguish them. Then prescribe the single re-engagement move that tests your diagnosis without begging — a move that produces information whether or not they reply. If the timeline honestly supports 'this deal is dead', say so and prescribe the graceful close instead. Timeline: {{timeline}}

Fill in: The deal timeline: every touch, meeting, promise, and silence with dates, plus who did what.

Known limits: Diagnosis from one side's timeline — their org chart changes, reorgs, and fire drills are invisible to it.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-mini

Input fixture
TIMELINE: May 12 inbound demo request (RevOps director). May 20 demo —
enthusiastic, 'this solves our QBR reporting mess'. May 28 security questionnaire
returned by us same-week. Jun 6 pricing call — asked for 3-year TCO comparison,
delivered Jun 9. Jun 18 champion emails 'legal is looking, expect redlines next
week'. Jul 2 we nudge — 'still with legal'. Jul 15 nudge — no reply. Jul 29 nudge —
no reply. Aug 12: champion's LinkedIn now reads 'Senior Manager, Revenue Systems' at
the same company (was 'Director, RevOps' in May). No unsubscribe, no rejection.

Model output (unedited)

Diagnosis: Champion lost power / influence after an org change, causing the deal to stall.

Evidence from the timeline:
- May 20: strong, verbal champion buy-in ("this solves our QBR reporting mess") and subsequent, specific diligence requests (security questionnaire, 3‑yr TCO) — behavior of a real buyer.
- Jun 18 → Jul 2: legal review in motion (champion told you to expect redlines), then follow-up responses stop after “still with legal.”
- Aug 12: champion’s LinkedIn shows a title change from Director, RevOps → Senior Manager, Revenue Systems at the same company. That looks like reduced seniority/zone of influence mid‑process. No formal rejection/unsubscribe — consistent with loss of internal power rather than an active vendor decision.

Strongest alternative diagnosis: Legal or another stakeholder raised an off‑stage objection that blocked signoff.
- Why it’s plausible: champion explicitly said “legal is looking” and never produced redlines; legal could have raised contractual/security issues that stalled approval.
- What would distinguish it: if legal is the blocker, you’ll see activity from a corporate legal/procurement email (requests for more documentation, redlines, or direct questions) or an intro from the champion to legal/procurement. If the champion has lost power, you’ll instead get either no response or a handoff to a new owner (or the champion will point you elsewhere).

Single re‑engagement move that tests the diagnosis (non‑begging, yields information even without a reply):
Send one short, trackable email to the champion with a single attachment/page and two clear CTAs:

Subject idea: Quick — one‑page legal checklist to unblock purchase

Body (very short):
- 1 sentence reminder of the value: “You flagged this would solve your QBR reporting — we built a one‑page ‘Legal Quick Win’ that covers the exact answers and contract positions that have cleared for other customers in your space.”
- Attach a one‑page PDF titled “Legal Quick Win — standard concessions we accept / common redlines resolved” (include security cert links, the 3‑yr TCO callout, and 2–3 contract clauses you accept).
- Two tracked CTAs (buttons/links): A) “Introduce me to the right owner” and B) “Schedule 15‑min legal sync.”
- One closing line: “If your role changed and you’re not handling this now, clicking A takes you 2‑seconds to nominate who is best. If you’re still owning it, B books 15 minutes that gets legal unstuck. I’ll circle back after two weeks if no click.”

Why this tests the diagnosis and what each outcome means:
- Champion clicks “Introduce me to the right owner” (or replies with a new contact): confirms champion lost power/was handed off — proceed by engaging the new owner.
- Champion clicks “Schedule 15‑min legal sync” (or legal/procurement book the slot): indicates legal/stakeholder objections are the real blocker but solvable — the sync reveals specifics.
- Champion opens attachment / clicks neither CTA but the file is downloaded/viewed (tracked): still interest but low bandwidth — likely deprioritization; follow up once more at the next budget cycle.
- No opens/clicks after two weeks: strong signal the deal is effectively dead or deprioritized; recommend a graceful close (one final email offering to pause the opportunity and set a calendar reminder for next quarter).

If you want wording and a one‑page “Legal Quick Win” template I can draft (contract clauses + security checklist + a 2‑line TCO callout) so you can send the exact tracked email.

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

Discovery questions that surface the real problem

Build a discovery question plan for this call from the context given. Structure: under 'Must learn', the three unknowns that most determine whether this deal is real (from the context — not a generic BANT list); under 'Questions', an ordered sequence where each question earns the next, moving from their world to the problem to consequences — no question answerable by yes/no unless it's a deliberate commitment check, and no question whose answer is already in the context (asking those burns credibility); under 'Listen for', the specific answers that would qualify or disqualify. Context: {{context}} What we sell: {{product}}

Fill in: Everything you know going in (who booked, why, their company) and what you sell.

Known limits: A question plan is a map, not a script — reading it verbatim kills the conversation it was meant to open.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-mini

Input fixture
CONTEXT: Inbound demo request from Priya Shah, Director of Revenue
Operations at Klarwerk (B2B analytics, ~180 employees, series B). Form note: "evaluating
conversation-intelligence tools, currently on Gong renewal deadline Oct 1." She's
invited their sales enablement manager to the call. Klarwerk's careers page shows 8
open AE roles — aggressive sales team growth.

WHAT WE SELL: EchoLens — conversation intelligence priced per recorded seat, with
coaching workflows built for ramping new reps.

Model output (unedited)

Must learn (the three unknowns that most determine whether this deal is real)
1) Renewal/commitment flexibility and timeline: Can Klarwerk actually move vendors before or at the Gong renewal (contract terms, auto-renew, cancellation penalties, internal timeline)? If they are locked in or cannot switch until much later, the deal is timing-out regardless of fit.
2) Seat count today and growth plan (recorded-seat footprint): How many seats would need recording now and in the next 6–12 months given the hiring of AEs—because EchoLens pricing is per recorded seat and growth will determine deal size and fit.
3) Core decision criteria and stakeholders: What specific problems must be solved (coaching workflows, ramp time, analytics accuracy, integrations), who signs off, and whether Revenue Ops + Enablement are the actual buyers/influencers vs procurement/finance veto power.

Questions (ordered so each answer earns the next)
1) "Tell me about the revenue goals and priorities you and your team are focused on this quarter and through year-end."
   - Purpose: open starter to surface urgency and strategic context; primes for hiring and enablement priorities.
   - Listen for: growth targets tied to new hire ramp, quota-acceleration focus, or quality-of-deal objectives. Qualification: if growth + rapid hiring are priorities, EchoLens is relevant; if focus is solely on cost-cutting, lower priority.

2) "Walk me through your current go-to-market headcount and hiring plan for the next 6–12 months — how many AEs, SDRs, and managers do you expect to add, and how quickly?"
   - Purpose: establish seat baseline and near-term growth that drives per-seat pricing and deployment complexity.
   - Listen for: concrete numbers (e.g., 8 AEs open now + plans to hire 15 more = rapid seat growth → qualifies); vague or 'maybe hiring later' = weaker opportunity. Disqualifier: very small team (<10 seats) or no planned increase.

3) "How are you currently using Gong day-to-day for coaching and ramping new reps, and what parts are falling short for your enablement goals?"
   - Purpose: surface functional gaps EchoLens solves (coaching workflows, ramp tracking, searchability, accuracy).
   - Listen for: complaints about coaching UX, difficulty running structured coaching, poor call tagging, unclear ramp metrics, slow search; these qualify. If they say Gong is meeting all needs and enablement is happy → disqualify or low priority.

4) "What would have to change in your current workflow or outcomes for you to switch to a different conversation-intelligence tool?"
   - Purpose: expose must-have capabilities, non-negotiables, and how they measure change.
   - Listen for: needs like better coach workflows, time-to-ramp improvements, easier manager workflows, better transcription/insights, or pricing flexibility. If answers align with EchoLens strengths (coaching workflows + ramping new reps) → strong fit. If they only want raw analytics and not coaching → weaker fit.

5) "You mentioned you’re evaluating options during the Gong renewal window — can you walk me through the specific renewal terms or constraints (length, auto-renew, termination window, financial penalties) that affect whether you can change vendors?"
   - Purpose: clarify timing and legal/financial blockers that determine whether an Oct 1 churn is possible.
   - Listen for: ability to terminate at renewal, notice period, auto-renew clauses, early-termination fees. Qualify: flexible renewal or short notice window → actionable timeline. Disqualify: long locked-in term or prohibitive penalties.

6) "How many of your reps currently have recording-enabled seats versus how many you would want recorded if you moved to a new vendor, and how do you expect that number to change as hires come on?"
   - Purpose: finalize real seat count for pricing and pilot sizing.
   - Listen for: exact current recorded seats and projected headcount; qualifying if projected recorded seats match EchoLens pricing thresholds (e.g., mid-to-large seat counts). Disqualify: extremely small number of recording seats or no budget to expand.

7) "Who else needs to be involved to evaluate and approve a new conversation-intelligence platform, and what criteria will each stakeholder use to make a decision?"
   - Purpose: map the buying committee and decision criteria (Enablement, RevOps, Sales Leadership, Finance, Legal, IT).
   - Listen for: names / titles and criteria (ROI/ramp, TCO, security/compliance, integrations). Qualify: RevOps + Enablement as active champions and Finance open to business case. Disqualify: only procurement or security-led evaluation with long cycles and no enablement buy-in.

8) "What specific outcomes or metrics would you use to say a new tool is successful (for example: weeks to ramp, percentage increase in win rate, coaching usage, number of completed coaching sessions)?"
   - Purpose: identify success criteria to frame a pilot and ROI calculation.
   - Listen for: measurable targets (e.g., reduce ramp from 6→4 months, increase quota attainment by X%). Qualify: concrete targets → easy to structure pilot. If answers are vague or purely subjective → harder to land.

9) "If EchoLens met your functional needs and pricing, would you be willing to run a time-boxed pilot with a subset of hires/managers before committing to full rollout, and what would a successful pilot look like?"
   - Purpose: move toward a low-friction next step and commitment; deliberate yes/no commitment check allowed here.
   - Listen for: willingness to pilot, proposed pilot scope (number of reps, duration), success metrics, and timeline. Qualify: yes with clear pilot scope → immediate next step. Disqualify: insistence on full RFP or no pilot allowed.

10) Commitment/timeline check: "Assuming a pilot demonstrates the outcomes you want, what would your ideal decision and rollout timeline look like relative to the Oct 1 renewal?"
   - Purpose: confirm schedule and next milestones so you can propose a fitting demo/pilot plan.
   - Listen for: dates and milestones (pilot start, evaluation window, approval meetings). Qualify: timeline that allows pilot and procurement before or at renewal → good. Disqualify: timeline that pushes decision months beyond renewal with no chance to switch now.

Listen for (specific answers that qualify or disqualify)
- Qualifiers (positive signals)
  - Concrete headcount and rapid hiring: e.g., 8 open AEs now, plan to hire 15 more in 6 months → scales to a sizable per-seat deal.
  - Clear pain with current coaching workflows in Gong (managers avoid using it, no structured coaching flows, slow coaching adoption).
  - Flexible Gong renewal terms (notice period aligns with Oct 1; no heavy penalties) or explicit intent to not renew.
  - Enablement + Revenue Ops as active champions willing to run a pilot; named stakeholders and decision owners.
  - Measurable success metrics (weeks-to-ramp, coaching adoption %, conversion lift) that EchoLens can help influence.
  - Willingness to run a time-boxed pilot with defined scope and success criteria in the near-term.

- Disqualifiers (negative signals)
  - Contractual lock: Gong auto-renews for another year with high termination fees or long notice that prevents switching before many months.
  - Very small recorded-seat footprint now and no planned growth (<10 seats) making per-seat economics poor.
  - No pain or dissatisfaction with current solution (Enablement says Gong meets all needs and they’re happy).
  - Buying process controlled exclusively by procurement/finance/security with long RFP cycles and no champion to run a pilot.
  - No budget or unwillingness to consider per-recorded-seat pricing model.
  - Vague or non-measurable success criteria, indicating low urgency.

How to use this plan on the call
- Start broad (strategy, goals) then narrow into headcount and current tool pain to surface fit. Use the Gong renewal context to understand timing but don’t assume they’ll or won’t switch—ask specifics.
- Push for numbers (seat counts, hiring velocity, contract terms, target metrics) as early as possible — those three unknowns determine whether you should proceed to demo/pilot.
- If you hear qualifiers, propose a defined pilot during the call (scope, success metrics, timeline) as the next step. If you hear disqualifiers, flag timing or scope and either plan a future check-in or deprioritize follow-up.

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

Extract the lesson from a lost deal

Run a debrief on this lost deal. Separate three threads, each under its own heading: 'What we controlled' — our choices that hurt (speed, pricing moves, demo focus, who we engaged), with the evidence; 'What we didn't' — their factors (budget death, incumbent lock-in, politics) honestly labeled as outside our control, resisting the urge to self-flagellate over them; 'What changes' — at most three process changes that would have plausibly altered THIS outcome, each testable on the next deal, not platitudes. If the loss reason given by the prospect contradicts the timeline evidence, say so — stated reasons are often polite fictions. Deal history: {{history}}

Fill in: The full deal history: timeline, stakeholders, the loss notification, and any stated reason.

Known limits: One deal is an anecdote — patterns need three debriefs; changing process on every loss is thrash.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-mini

Input fixture
HISTORY: GridWatch vs incumbent at Ohio Valley Electric (mid-size
utility). Apr: warm intro via board member. May: technical deep-dive, their
engineers enthusiastic ('this catches what SCADA alarms miss'). Jun: proposal $120k
pilot. Jul: silence, two nudges. Aug 2: procurement email — 'we've decided to expand
our existing GE contract; your solution scored higher technically but vendor
consolidation won.' Stated reason: consolidation. Timeline notes: we never met
anyone from procurement or finance until the loss email; our champion was an
engineer with no purchasing authority; GE's expansion was reportedly discounted
30% mid-eval (per champion, after the fact).

Model output (unedited)

What we controlled
- Who we engaged: we built the deal around a single technical champion (engineer). Evidence: after the Apr warm intro and the enthusiastic May deep-dive, we never met procurement or finance until the Aug loss email.
- Qualification of the buying process and budget: we did not lock down budget, procurement criteria, or a timeline for decision before issuing a proposal. Evidence: $120k pilot proposed in Jun, then silence in Jul; no PO, no signed SOW, no budget confirmation.
- Commercial / competitive positioning and cadence: we left the proposal vulnerable to late incumbent moves and didn’t create a rapid path to commitment. Evidence: champion later reported GE offered a ~30% discount mid-eval; we had no procurement channel or escalation to counter a last-minute price concession. Also our outreach after sending the proposal was limited to two nudges in Jul — no structured follow-up or escalation to a sponsor.

What we didn't
- Incumbent leverage and procurement preferences: utilities often prioritize vendor consolidation and long-standing GE relationships. That reasoning (consolidation) is a legitimate external factor.
- Procurement tactics and discounting ability: GE’s ability to offer steep discounts and repackage scope quickly is outside our control.
- Internal political or contractual constraints at Ohio Valley Electric (board/finance/vendor consolidation policies) — we don’t control their internal rules or prior commitments.

Note on stated reason vs. evidence
- The customer’s stated reason (“vendor consolidation won”) is plausible, but the timeline suggests it may be a polite fiction that masks commercial tactics. Contradictory signals:
  - We were never introduced to procurement/finance until the loss — if consolidation was central, procurement would likely have been engaged earlier.
  - Champion’s post-hoc report of a ~30% GE discount implies price/competitive response played a material role.
- Reasonable read: consolidation was an acceptable external explanation for them to give publicly, while incumbent discounting and procurement negotiation (things we didn’t engage) were the proximate causes.

What changes (three testable process changes)
1) Mandatory “procurement + budget” checkpoint before proposal acceptance
   - Rule: do not issue a pilot proposal >$25k (adjust threshold to your typical deal size) until we have a documented procurement touchpoint and written confirmation of budget ownership (email from procurement/finance or signed funding note).
   - How to test: apply to next 6 pilot opportunities; track whether procurement/finance were engaged before proposal and measure closure rate and time-to-PO.
   - Expected impact: surfaces consolidation or incumbent requirements early, prevents surprise late-stage procurement decisions.

2) Require transactional commitment for pilots (signed SOW + PO or prepayment) within X days
   - Rule: all pilots require an SOW signed by a budget owner and a PO or 30% prepayment within 21 days of proposal issue; if not received, convert to a time-boxed demo project with no production-level commitments.
   - How to test: implement on next 3 pilot proposals; measure percentage that convert to signed SOW/PO and compare abandonment rate to prior baseline.
   - Expected impact: forces customers to make an accountable buying decision (and exposes budget or procurement blocks), reducing “silent” stalls.

3) Competitive response playbook + escalation trigger
   - Rule: if a competitor/integrator incumbent is mentioned or a pricing concession is suspected (e.g., procurement referenced consolidation or budget constraints), trigger an immediate CRO/Head of Sales escalation and one of three pre-approved responses: (a) limited-time conversion price cap for pilots, (b) guaranteed performance SLA with partial refund on failure, or (c) an executive-level reference call and joint roadmapping session to demonstrate enterprise alignment.
   - How to test: implement playbook and time-to-response metric on next 10 competitive situations; track outcomes where the playbook was used vs. not used.
   - Expected impact: allows rapid, controlled commercial countermeasures to last-minute incumbent discounts or procurement pressure and demonstrates enterprise-level fit beyond technical merit.

Brief closing
- Root cause: strong technical fit but weak buying-process control. The three changes above are narrowly focused, measurable, and would plausibly have exposed the consolidation/discount risk earlier or given us a commercial lever to preserve the opportunity.

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

Handle 'we're also looking at X' without trashing X

The prospect is comparing us to a named competitor. Write the response: respect the competitor honestly (name one thing they're genuinely good at, from the facts), then draw the real dividing line — the difference in approach or fit that decides which buyer should pick which product — and land on which side THIS prospect's situation falls, using their context. Give them one sharp evaluation question to ask both vendors that we win on merit. Use only the provided facts about both products; where competitor facts are missing, say 'verify with them' rather than guessing. Their statement: {{statement}} Our facts: {{ours}} Competitor facts: {{theirs}} Prospect context: {{context}}

Fill in: What the prospect said, verified facts about your product, what you reliably know about the competitor, and the prospect's situation.

Known limits: Everything you say about a competitor gets repeated to that competitor — write as if they'll read it.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-mini

Input fixture
STATEMENT: "We're also evaluating Gong. It's the safe choice — everyone
uses it."

OUR FACTS (EchoLens): per-recorded-seat pricing (~40% below Gong list at this size);
coaching workflows (scorecards, ramp plans, call libraries) are the core product, not
an add-on module; integrates with HubSpot and Salesforce; 180 customers, mostly
50-500 employee B2B; no revenue-forecasting module.

COMPETITOR FACTS (Gong, reliable): market leader, ~4000+ customers; strongest at
revenue intelligence/forecasting on top of calls; coaching exists but is a paid
add-on tier; enterprise-grade admin and security certifications.

PROSPECT CONTEXT: 180-person company ramping 8 new AEs; stated priority is coaching
and ramp speed; no forecasting pain mentioned; price-sensitive after a down round.

Model output (unedited)

Totally fair — Gong is the “safe” name. They’re the market leader (4,000+ customers) and best-in-class when you want revenue intelligence/forecasting layered on top of calls.

The real dividing line is product focus and economics, not popularity:
- Gong = best fit if your priority is enterprise-grade forecasting/revenue intelligence (and you need top-tier enterprise admin/security). Coaching is available, but it’s a paid add-on.
- EchoLens = best fit if your priority is coaching and ramp speed. Coaching workflows (scorecards, ramp plans, call libraries) are our core product, not an add-on, and our per-recorded-seat pricing runs about 40% below Gong list at this size. We also integrate with HubSpot and Salesforce and work with lots of companies in your size band (50–500 employees).

Given your situation — 180 people, ramping 8 new AEs, coaching/ramp speed is the stated priority, no forecasting pain called out, and you’re price-sensitive after a down round — EchoLens is the better pragmatic fit.

One sharp evaluation question to ask both vendors (we win this on merit):
"For a cohort of 8 new AEs, show a concrete 30/60/90-day ramp plan implemented in your product (include scorecards, example call libraries, and coach workflows), the measurable KPI improvements you expect at each milestone, and the total all-in cost (per-recorded-seat + any add-on fees) to deliver that ramp."
Finally — if enterprise-grade security or specific compliance certifications are a hard requirement, verify those certifications with both vendors before deciding.

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

MEDDPICC gap check that names the next move

Run this deal through MEDDPICC. For each letter — Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identified pain, Champion, Competition — give a labeled one-line status backed by evidence from the notes, using 'no evidence' where the notes are silent rather than inferring generously. Then, under 'The gap that kills', name the single weakest letter for THIS deal's stage and the concrete action (who to ask, what to ask for) that closes it this week. A deal late in stage with early- stage gaps deserves that said plainly. Deal notes: {{notes}}

Fill in: Your deal notes and the current deal stage.

Known limits: Frameworks organize evidence; they don't create it — a MEDDPICC review of thin notes just formats the thinness.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-mini

Input fixture
DEAL NOTES (stage: proposal sent, forecast 'commit' by the AE):
RouteHive-Suncrest Solar deal, $54k/yr. Ravi (Director Field Ops) is engaged,
responds same-day, calls us 'his project'. Missed-appointment metric documented:
14% monthly, $180/re-roll. Proposal sent to Ravi Aug 8. Ravi says 'ops budget covers
it' — we haven't seen a budget owner. Decision process per Ravi: 'me, then my VP
signs'. VP Operations has been CC'd twice, never replied, never met. No security or
legal requirements mentioned. Competition: Ravi says 'we'd just keep the
spreadsheet'. Pilot discussed but not scoped. Close date in CRM: Sep 5.

Model output (unedited)

Metrics: Defined — Missed-appointment metric documented as 14% monthly with a $180 re-roll cost (notes).  
Economic buyer: Weakly identified — VP Operations is the approver per Ravi ("me, then my VP signs") and is CC'd twice but never engaged; no confirmed budget owner seen (notes).  
Decision criteria: No evidence — notes contain no stated selection or evaluation criteria.  
Decision process: Partially defined — Ravi says decision flow is "me, then my VP signs"; VP has not responded to outreach (notes).  
Paper process: No evidence — no procurement/PO/legal/security steps or timelines described in notes.  
Identified pain: Clear — missed appointments (14% monthly, $180/re-roll) is documented and positioned as the use case (notes).  
Champion: Present and active — Ravi (Director Field Ops) is engaged, responds same-day, calls it "his project" and received the proposal Aug 8 (notes).  
Competition: Status quo — internal spreadsheet; Ravi explicitly said "we'd just keep the spreadsheet"; no vendor competitors mentioned (notes).

The gap that kills: Economic buyer engagement. This deal is late in stage (proposal sent; AE forecasting "commit") but the true approver (VP Operations) is unengaged and no budget owner confirmation or paper process is secured — that mismatch can kill a late-stage close.

Concrete action to close this week (who to ask, what to ask for):
- Who: AE should ask Ravi (champion) immediately.  
- What to ask for: Request a 15-minute calendar intro/meeting this week with the VP Operations (and any budget owner/procurement contact) and ask the VP, on-record, to (a) confirm they own/approve the ops budget for this spend, (b) commit to signing/approving the proposal by the CRM close date (Sep 5) or give the exact approval timeline, and (c) state any required procurement/legal/security steps and who owns them.  
- Deliverable required this week: a calendar invite or an email from the VP (or procurement owner) confirming budget ownership and sign-off timeline (or a firm date for needed approvals).

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

Mutual action plan that survives contact with reality

Draft a mutual action plan from signature backwards to today for this deal. Each step: owner (name from the context), the artifact that proves the step happened, and realistic duration — including THEIR internal steps (legal, security, procurement) which take longer than anyone admits; where the context doesn't say who owns a step, mark it '[owner needed]' as an explicit question for the prospect. Then flag the two steps most likely to slip and the early-warning sign for each. A plan the prospect co-edits is the point — end with the one-line ask that gets them to correct it. Deal context: {{context}}

Fill in: Deal context: target close date, known stakeholders, steps already done, their known process requirements.

Known limits: A MAP the prospect never touched is your fantasy with dates — the co-editing ask is the qualification test.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-mini

Input fixture
CONTEXT: EchoLens-Klarwerk deal. Target: signed by Sep 26 (their Gong
renewal Oct 1). Done so far: demo, pilot scoping call, SOC 2 sent under NDA Aug 15.
Ahead per champion: 2-week pilot on 10 seats (their admin needs Salesforce sandbox —
our SE booked for Aug 22), pilot readout to Priya + VP Sales, then security review
('1 week, questionnaire-based' per Priya), then legal ('MSA redlines took 3 weeks
last vendor' — champion's words), procurement is Priya herself. CFO signs above $30k.
Unknown: whether VP Sales wants to see the pilot readout live or async.

Model output (unedited)

Below is a mutual action plan laid out backwards from the target signature date (Sep 26) to today. Each step lists: owner (named where known; I’ve put [owner needed] where I need you to assign someone), the artifact that proves completion, and a realistic duration (including the internal reviews that usually stretch timelines). This is meant for you to co-edit — I’ve flagged two steps most likely to slip and the early-warning sign for each at the end.

Assumptions / important context used
- Target signature: Sep 26 (because Gong renewal Oct 1).  
- Pilot plan per your champion: 2-week pilot on 10 seats; EchoLens SE booked Aug 22.  
- SOC2 was delivered under NDA on Aug 15 (already done).  
- Procurement owner = Priya. CFO approval required for >$30k.  
- Unknowns I need you to confirm: champion name, their Salesforce admin, who on legal/security will own reviews, and whether VP Sales wants the pilot readout live or asynchronous.

Mutual action plan (backwards from signature)

1) Contract signed — Target date: Sep 26
- Owner: Their CFO (final signature)  
- Artifact: Fully executed contract (DocuSign/ PDF with signatures) and/or PO; confirmation email from CFO/finance.  
- Realistic duration: routed & signed same day if approvals ready; allow 1–3 business days for final routing + finance stamping.  
- Internal steps to expect: CFO routing, finance office/approver checks, accounts-payable setup.

2) Procurement final approval / sign-off (Purchase Order or written approval) — Complete by Sep 25
- Owner: Priya (procurement)  
- Artifact: Signed PO or written approval email to EchoLens AE; internal procurement form.  
- Realistic duration: 3–7 business days (Priya confirms budget, issues PO, routes internally).  
- Internal steps to expect: budget check, PO creation, internal approval email thread, PO issuance to vendor.

3) Legal finalize & agree MSA (redlines closed) — Finish by ~Sep 24
- Owner: [their Legal lead — owner needed] + EchoLens AE/legal  
- Artifact: Clean MSA document agreed in redline-tracking (or DocuSign-ready copy) and a redline resolution spreadsheet/email thread.  
- Realistic duration: 2–3 weeks (plan on 15 business days) — this matches your champion’s report that previous vendor took 3 weeks.  
- Internal steps to expect: initial internal legal review, GC escalation for unusual terms, rounds of redlines, internal commercial/legal committee sign-off, routing for signature.

4) Security review complete (questionnaire + attachments accepted) — Finish by ~Sep 14
- Owner: Priya (coordinator) + [their Security team contact — owner needed]  
- Artifact: Completed security questionnaire returned and formally accepted (email confirmation), and any required evidence (SOC2 receipt acknowledgement, security checklist signed).  
- Realistic duration: 1 week (questionnaire-based) + 3 business days buffer → plan 7–10 business days.  
- Internal steps to expect: security reviewer assignment, questionnaire completion, internal risk committee (if any), routing back to procurement/legal as needed.

5) Pilot readout to Priya + VP Sales (decision meeting or async delivery) — Target by ~Sep 7
- Owner: Champion (presenter) + EchoLens SE/AE (content, demo)  
- Artifact: Readout deck, meeting calendar invite and recording (if live) or shared recording + written executive summary (if async); readout notes with action items.  
- Realistic duration: 3–5 business days from pilot close to prepare slides, schedule VP meeting, and distribute materials.  
- Internal steps to expect: scheduling (VP calendar constraints), internal content review, approval of metrics/claims for executive audience.  
- Question: Does the VP Sales want a live readout or an asynchronous recording + summary? — [owner needed: VP Sales preference]

6) Pilot execution — 2-week pilot on 10 seats — Aug 22 → ~Sep 4 (pilot run); wrap-up through Sep 6
- Owner: Champion (customer-side) + EchoLens SE (delivery/support)  
- Artifact: Pilot report including usage metrics, success criteria checklist, admin logs, screenshots; weekly check-in notes.  
- Realistic duration: 14 calendar days for the pilot + 2–3 business days for wrap-up & metrics compilation.  
- Internal steps to expect (customer): scheduling internal reviewers, test scenarios run, admin access and logging, weekly status check-ins.

7) Salesforce sandbox provisioned & EchoLens SE granted access — Ready by Aug 22 (prior to pilot)
- Owner: their Salesforce admin — [owner needed: name/contact]  
- Artifact: Sandbox instance URL, admin credentials for the pilot user(s), screenshot/email confirmation of access for EchoLens SE.  
- Realistic duration: 1–3 business days typically, but allow up to 5–10 business days if change requests, data refresh or IT approval required.  
- Internal steps to expect: IT change ticket, data subset approval, security approval for external access, creation of test users/permissions.

8) EchoLens SE prep and kickoff session scheduled — Completed / scheduled for Aug 22
- Owner: EchoLens SE  
- Artifact: Calendar invite for kickoff, agenda, pre-kickoff checklist completed.  
- Realistic duration: scheduling done; allow 1–2 business days pre-kick for internal SE prep and trial provisioning.

9) SOC2 & security artifacts delivered under NDA — Completed Aug 15
- Owner: EchoLens Security (delivered)  
- Artifact: SOC2 report delivered, NDA on file (confirmation email).  
- Realistic duration: completed; used by customer security for their review.

10) Quote / Commercial terms & order form provided to customer — Start as needed; must be agreed before the legal/PO steps finish
- Owner: EchoLens AE  
- Artifact: Final quote / pricing sheet / order form and any discount approvals, line-item pricing in email or attached quote PDF.  
- Realistic duration: 1–3 business days to finalize and send; allow additional days if internal discount approvals needed.

Items I’ve left as explicit questions / [owner needed]
- Champion name / owner for coordination on your side — [owner needed]  
- Their Salesforce admin (name/contact) to provision sandbox — [owner needed]  
- Their legal lead / GC contact who will handle MSA redlines — [owner needed]  
- Their security owner (if different from Priya) — [owner needed]  
- VP Sales preference for readout: live or async — [owner needed]

Two steps most likely to slip (and early-warning signs)

1) Legal review (MSA redlines)
- Why high risk: your champion said redlines took 3 weeks on the last vendor — legal processes can add rounds and internal escalation.  
- Early-warning sign: no acknowledgement of EchoLens’ redline package from their legal team within 48–72 hours of delivery, or legal returns a first pass with a large number of new commercial asks (pricing/termination/indemnity) instead of line edits. If we see either, we should pause the target signature date and escalate to the champion/GC for prioritization.

2) Salesforce sandbox provisioning (blocks pilot start)
- Why high risk: pilot cannot run without a sandbox; IT/admin change processes often introduce hidden delays or security gating.  
- Early-warning sign: their Salesforce admin hasn’t confirmed sandbox creation + access to EchoLens SE at least 24 hours before the planned Aug 22 kickoff, or the SE reports repeated inability to login during the SE pre-kick check. If this happens, we must get the admin on a call immediately and, if needed, request a temporary demo dataset or extend the pilot window.

One-line ask (for you to co-edit/confirm)
Please update the items marked [owner needed] (champion name, Salesforce admin, legal contact, security contact, and VP Sales preference live vs async) or correct any durations so I can finalize this timeline.

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

Negotiation prep with a real walk-away

Prepare the negotiation for this deal. Under 'Their position', what they'll push for and the pressure behind it (from context); under 'Our levers', every concession available ranked cheapest-to-us first — trades that cost little but matter to them (terms, timing, seats, support) before any price move; under 'Trade rules', pair each concession with what we require in return (term length, case study, referral, payment timing) — a concession without a return is a donation; under 'Walk-away', the concrete floor and what we do the day after walking. Use only the deal facts given. Deal facts: {{facts}}

Fill in: Deal facts: price quoted, their counter or pressure, margins or floors you know, contract variables in play.

Known limits: A negotiation plan without an enforced walk-away is a discount schedule with extra steps.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-mini

Input fixture
DEAL FACTS: EchoLens quote $38k/yr, 45 seats, annual prepay. Their ask:
"match Gong's renewal at $29k or we stay." Our floor (from finance): $31k on annual
prepay, or $34k on quarterly. Levers available: 2-year term (worth 8% to us), Q4
start date flexibility, 10 extra seats at marginal cost, onboarding fee ($3k) waivable,
case-study participation (marketing wants a RevOps story badly), referral intro to
their sister company. Their pressures: Oct 1 Gong deadline, CFO scrutiny, champion
strongly prefers us, VP Sales needs ramp results by Q1 board meeting.

Model output (unedited)

Their position
- Primary ask: "Match Gong's renewal at $29k or we stay." They will push hard on price.
- Pressure behind it:
  - Oct 1 Gong deadline gives them a hard external timeline — they'll use the deadline to force a quick decision.
  - CFO scrutiny — the finance stakeholder will be looking for the lowest renewal number.
  - VP Sales needs visible ramp results by the Q1 board meeting — they want the fastest, cheapest path to show progress.
  - Internal champion strongly prefers EchoLens, which means they will push non-price arguments (product fit, ramp) but need a price that survives CFO scrutiny.

Our levers (ranked cheapest-to-us first — non-price concessions before any price move)
1. Q4 start-date flexibility (zero cash cost; matters to their ramp / board timeline)
2. Offer a 2‑year term (this is worth 8% to us — i.e., gives us financial benefit; cheap for us to accept)
3. Referral intro to their sister company (no direct cost to us; high strategic value)
4. 10 extra seats at marginal cost (low cash impact; helps their immediate user ramp)
5. Case-study participation (marketing wants a RevOps story badly — low direct cost, high marketing value)
6. Onboarding fee ($3k) waivable (direct cash concession — material relative to other items)
7. Billing frequency control (annual prepay vs quarterly): our finance floor differs by billing (annual prepay floor $31k; quarterly floor $34k) — this is a hard internal lever, used to protect cash.

Trade rules — every concession paired with a concrete return (no concession without a return)
- Q4 start-date flexibility
  - We will agree to a Q4 configurable start only if they sign a minimum 2‑year contract and commit to annual prepay at or above our annual floor ($31k). Rationale: start-date flexibility without term/prepay = pure scheduling donation.
- 2‑year term
  - If they accept a 2‑year term, we will apply up to the 8% commercial benefit (≈ $3,040 off $38k → approx $34,960). Any further move toward our annual floor ($31k) requires additional return items below (case study and intro).
- Referral intro to sister company
  - We will provide the referral intro only in exchange for either (a) a signed 2‑year annual-prepay agreement at ≥ $31k OR (b) a signed case-study commitment plus annual prepay. Intro is strategic, so it must be tied to a contract commitment.
- 10 extra seats at marginal cost
  - We will add 10 seats at marginal cost only if they provide a public case-study (or formal reference) and agree to the 2‑year term. Seats without a reference/term = donation.
- Case-study participation
  - In return for an approved case-study (public/usable by marketing), we will (choose one, but require commitment): either waive onboarding fee ($3k) OR supply the 10 extra seats. We will not both waive fee and give seats for just a case study — need one meaningful return per concession.
- Waive onboarding fee ($3k)
  - We will waive the $3k onboarding fee only if they: (a) sign a 2‑year term and (b) commit to annual prepay at ≥ $31k, and (c) provide a referral intro to their sister company within 60 days of go-live. A direct cash waiver requires multiple returns.
- Billing frequency (annual prepay vs quarterly)
  - If they insist on quarterly billing, our minimum acceptable price is $34k (finance floor). If they accept annual prepay, the minimum acceptable price is $31k. We will not accept a price below these floors for the respective billing choice.

Negotiation posture / walk-through (how to trade)
- First offer to them (no price move): Q4 start flexibility + 10 extra marginal-cost seats + referral intro in exchange for: signed 2‑year term + annual prepay at $31k + commitment to a marketing case-study. If they balk on price, peel back seats or require the case-study/referral before waiving onboarding fee.
- If they ask for a price move beyond the 8% 2‑year benefit (~$34,960), require the case-study and referral intro as mandatory returns to get to $31k.
- Never accept their $29k demand without receiving all three returns: 2‑year term, annual prepay, signed public case-study, and confirmed referral intro — even then $29k is below our stated annual floor, so we will not accept it.

Walk-away
- Concrete floor: we will not accept below our finance floors — $31,000 per year with annual prepay OR $34,000 per year on quarterly billing.
- If they insist on $29k (or any number below the applicable floor), we walk.
- Day after walking:
  - Communicate succinctly to their champion/CFO: restate our final position (floors and what we would have required in return) and why we declined to accept $29k.
  - Leave the door open: note we can re-engage if they are willing to meet the trade rules (2‑year + annual prepay + case-study/referral), and remind them of the Oct 1 Gong deadline and the VP Sales Q1 ramp need (allow them to reassess).
  - Internally: log loss, notify finance/marketing of outcome (so marketing can prioritize other case-study prospects), and redeploy the seats/onsite resources earmarked for this deal.

One-sentence internal reminder
- Concessions cost us only if given without return — tie every non-price concession to either a 2‑year term, annual prepay at our floor, a public case-study, or the sister-company referral; otherwise walk at $31k (annual) / $34k (quarterly).

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

Prep a renewal that isn't a hostage negotiation

Prepare the renewal conversation from this account history. Under 'Value delivered', the concrete results from the history — usage, outcomes, incidents resolved — stated in their terms, never padded; under 'Risk read', an honest renewal-risk assessment from the signals (usage trend, champion status, support tickets) with the evidence; under 'The conversation', how to open (value recap before any pricing), what to ask about their coming year, and how to introduce any price change with its justification; under 'If they push back', the concession path and its floor. Flag anything in the history that argues we should NOT push for expansion this cycle. History: {{history}}

Fill in: The account history: usage data, results, support record, champion changes, current price and any planned increase.

Known limits: Renewal prep from usage data alone misses the reorg that deleted your budget line — ask the humans too.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-mini

Input fixture
HISTORY: Coastway Logistics, Relay customer 26 months, $24k/yr, renewal
Nov 1. Usage: auto-triage handling 44% of ticket volume (peak 51% in December);
weekly active dispatch-agent seats 31/35. Results: their reported first-response
time down from 6h to 90min year-over-year; December handled 3x volume with 2 fewer
temps. Support record: 4 tickets this year, all resolved <48h, one integration
outage in March (4 hours, our fault, credited). Champion: Tomas (Support Director)
— promoted to VP Ops in July; his replacement (new Support Director, started Aug 1)
has never met us. Planned: 8% price increase across the board this cycle.

Model output (unedited)

Value delivered (exact, in their terms)
- Auto-triage handled 44% of ticket volume this year (peak 51% in December).
- Weekly active dispatch-agent seats: 31 of 35.
- First-response time improved from 6 hours to 90 minutes year-over-year.
- December run-rate: handled 3× ticket volume with 2 fewer temporary staff.
- Support: 4 tickets this year, all resolved in under 48 hours.
- Incident: one integration outage in March (4 hours, our fault) — we issued a credit.

Risk read (honest assessment + evidence)
- Renewal likelihood: Moderate-to-high, but not guaranteed.
  - Positive signals
    - Strong operational value: big first-response improvement and large portion of volume handled automatically.
    - High seat utilization (31/35) and peak auto-triage performance in December show product is core to their operations.
    - Low support volume and quick resolution times (except March incident) demonstrate healthy operations.
  - Risk signals
    - Champion change: Tomas (previous champion) was promoted in July; the new Support Director started Aug 1 and has never met us. Loss of an engaged champion is the single biggest renewal risk.
    - Historical incident: the March integration outage (our fault) required a credit — raises sensitivity around reliability with new leadership.
    - Usage seasonality: peak in December (51%) — if renewal conversation happens outside peak, perceived urgency for expansion or investment may be lower.
- Net: core product is delivering measurable ROI, so renewal is likely if we re-establish stakeholder relationships and address reliability concerns. Expansion this cycle carries added risk because the new director is unvetted.

The conversation (how to open, what to ask, how to introduce price)
1) Opening (value recap before pricing — script)
   - “Quick recap before we talk numbers: over the last 12 months Relay has handled 44% of your ticket volume (peaked at 51% in December), helped keep weekly active seats at 31/35, cut first-response from 6 hours to 90 minutes, and let you handle December’s 3× volume with two fewer temps. We also resolved 4 support tickets this year within 48 hours; we own the March outage and credited it. Given that impact, I want to confirm how you see Relay fitting into your priorities for the coming year before we go into pricing.”
2) Key questions to ask this renewal meeting
   - Operational goals & volume
     - “What are your top ops priorities for the next 12 months? Any expected changes in ticket volume or seasonality?”
     - “Are you planning headcount changes (temps or full-time) in support/dispatch?”
   - Satisfaction & reliability
     - “How satisfied is the team (and your new Support Director) with reliability, triage accuracy, and SLAs since March?”
     - “Any outstanding technical concerns or integrations we should prioritize?”
   - Decision & budget
     - “Who will be involved in this renewal/approval now that Tomas has moved to VP Ops?”
     - “What is your budget timing for this renewal?”
   - Expansion interest (ask, but don’t push)
     - “If we solve any top reliability or onboarding concerns for your new director, would you consider expanding coverage or seats next cycle?” (leave open but don’t push expansion now)
3) Introducing the price change (how to frame it)
   - Lead with value, then state change and justification: “Given the results you’ve seen and the investments we’ve made in reliability and product improvements, our standard renewal reflects an 8% across-the-board increase this cycle. We want to make sure that number aligns with the value you receive and your budget; if there are reliability or onboarding items we need to fix first, we’ll prioritize those discussions before finalizing terms.”

If they push back (concession path and floor)
- Concession path (stepwise)
  1. Standard (ask): 12-month renewal at +8% (company policy).
     - Include: one onboarding session for the new Support Director + a joint QBR within 60 days.
  2. If they push back on 8% for a 12-month term: offer 12 months at +4% if they sign within the 30-day renewal window and commit to the onboarding/QBR above.
     - Include: 1 additional week of technical onboarding (no charge) to address March concerns.
  3. If they refuse both: final concession (floor) — freeze pricing at 0% increase in exchange for a 24-month term commitment and a minimum seat commitment (maintain at least 31 seats), plus a documented SLA remediation plan and a joint QBR cadence.
- Floor (no deeper concessions)
  - We will not accept a negative increase (i.e., a price reduction).
  - The lowest acceptable commercial outcome is 0% increase for a 24-month committed term with the above operational commitments (onboarding/SLA/QBR and seat minimum).
- Rationale for concessions
  - The onboarding/SLA commitments directly address the primary risks (new director + past outage) and make the longer-term relationship more predictable.

Flag: reasons not to push for expansion this cycle
- New Support Director (unknown relationship): expansion without an engaged champion is high risk.
- March outage (our fault): increases sensitivity to reliability; expansion before resolving perceived reliability issues could backfire.
- Usage is already high but seasonal — they may prefer to stabilize current performance rather than expand immediately.

Recommended next steps (concrete)
- Book a 30–45 minute renewal meeting including the new Support Director and Tomas (if helpful) within 2 weeks to:
  - Deliver the value recap.
  - Ask the questions above and surface budget/timing.
  - Present the proposed 8% increase and the concession options if needed.
- Commit to a concrete onboarding/SLA plan for the new Support Director to be included in any renewal agreement.
- Avoid proposing expansion terms in the first meeting; focus on re-establishing trust and a signed renewal.

If you want, I can draft a 3–4 sentence opening email and the exact meeting agenda to send to the new Support Director.

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

Read whether an account is ready for expansion

Assess whether now is the time to raise expansion with this account. Under 'Signals for', the evidence from the account data that argues yes (usage ceilings, new teams appearing, stated plans); under 'Signals against', the evidence that argues wait (open support pain, champion transitions, budget events, recent price changes); then a labeled verdict — 'now', 'after a specific fixable blocker', or 'not this quarter' — committing to one, with the reasoning. If 'now': the natural opening that ties expansion to THEIR goal rather than our quota. If not: the trigger event to watch for. Account data: {{data}}

Fill in: Account data: usage trends, seat utilization, support record, org changes, renewal date, recent conversations.

Known limits: Expansion timing reads collapse if the data is stale — pull fresh usage before acting on the verdict.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-mini

Input fixture
ACCOUNT DATA: Klarwerk, EchoLens customer 6 months ($34k/yr, 45 seats
negotiated). Usage: 44/45 seats active weekly; recording volume +60% since the 8 new
AEs ramped; coaching scorecards used by 5 of 6 team leads. Ramp result their VP Sales
quoted at the board: 3.4 months average for the new cohort (target was 3, prior was
5). New signal: they acquired a 30-person sales team via a small acquisition closing
next month (press release last week). Support: zero open tickets. Champion Jonas:
promoted to Head of Enablement. Renewal: 6 months out. Price increase at renewal:
none planned. Recent conversation: Jonas asked in passing whether call libraries can
be segmented per business unit.

Model output (unedited)

Signals for (evidence arguing YES)
- Seat usage at ceiling: 44/45 seats active weekly — literal quota pressure; one more active user would push them over.
- Rapid volume growth: recording volume +60% since 8 new AEs ramped — usage is expanding beyond seats/features and will continue with another acquisition.
- Clear value shown publicly: ramp time for the new cohort is 3.4 months (board-quoted; prior 5) — a measurable ROI story you can tie expansion to.
- Adoption across leadership: coaching scorecards used by 5 of 6 team leads — broad functional adoption, not just a single use case.
- Incoming, immediate seat demand: a 30-person sales team from an acquisition closes next month — a discrete, time-boxed need for seats/licenses/training.
- Champion in a stronger role: Jonas promoted to Head of Enablement — more influence to sign off on expansion.
- No support pain or open tickets — low risk of technical/account blockers right now.
- Renewal is 6 months out with no planned price increase — no near-term contract pricing friction to delay expansion.

Signals against (evidence arguing WAIT or caution)
- Product question about org segmentation: Jonas asked whether call libraries can be segmented per business unit — could be a functional blocker for onboarding an acquired team if they require strict BU separation.
- Champion transition risk: promotion is positive, but any role change can temporarily shift priorities/availability for procurement.
- Renewal still 6 months out — some customers prefer to consolidate changes at renewal; although here there’s immediate demand.

Verdict — now
Commitment: Now. Reasoning: seat usage is essentially maxed, a 30-person acquisition closes next month (clear, immediate demand), you have a strong ROI story that’s already board-level, and your champion now has more authority. The only potential blocker is the library segmentation question — it’s a product nuance that can be addressed in a short tech session or with an interim workaround, and it does not justify postponing expansion given the timing and runway risk of onboarding the new team without seats.

Recommended immediate next actions (how to expand without sounding quota-driven)
1) Natural opening (tie expansion to THEIR goal — suggested wording to Jonas/Head of Enablement):
   "Congrats on the acquisition — that’s great growth. Our usage data shows you’re essentially at capacity (44/45) and with the 30-person team joining next month we risk fragmenting onboarding and losing the faster ramp you just achieved. Would you be open to expanding licenses for the new team now so we can onboard them day‑one and preserve your 3.4‑month ramp metric? We can also run a quick session this week to show how to organize call libraries per BU (or provide a short-term workaround) so content governance matches your org structure."

2) Tactical asks:
   - Propose adding 30 seats + 5–10% buffer (recommend 33–35 seats) to cover the acquired team and immediate growth.
   - Book a 30–45 minute technical call this week to: (a) demonstrate current library segmentation options / workarounds (teams, tags, permissions), (b) capture whether strict BU-level separation is a hard requirement, and (c) agree on a rollout plan and timeline.
   - Offer a short pilot: onboard a small subgroup (5–10 reps from the acquired team) immediately to prove the process and measure ramp impact.

3) Contingency if segmentation is a hard blocker:
   - If Jonas says BU segmentation is non-negotiable and current product cannot meet it within the needed timeframe, pause full-seat expansion for the acquired team and expand only to cover immediate overflow (1–2 seats) while you escalate a product/implementation fix. Trigger event to move forward then: confirmation from product/implementation team of a delivery date for BU segmentation or acceptance of an approved workaround validated in a pilot.

Bottom line: act now to secure seats for the incoming 30-person team and tie the purchase explicitly to preserving their improved ramp time (3.4 months). Address the library segmentation ask proactively in a technical session so it does not become a procurement blocker.

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

Score a deal's health without wishful thinking

Score this deal honestly. For each dimension — problem urgency, champion strength, access to economic buyer, defined process and timeline, and money — give a labeled verdict of strong, weak, or unknown, each backed by direct evidence from the notes; 'unknown' is the required verdict wherever the notes are silent — treating silence as strength is how pipelines rot. Then: the single next action that converts the most important 'unknown' into evidence, and the honest forecast category (commit, best case, pipeline, or disqualify) this scoring supports. Deal notes: {{notes}}

Fill in: Your deal notes as they stand — meetings held, who said what, what's scheduled.

Known limits: The scorecard grades your notes, not the deal — thin notes score as unknowns even when the calls went well.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-mini

Input fixture
DEAL NOTES: Nordwind Travel — account-scoring tool eval. Two calls with
Ingrid (RevOps lead, met at SaaStock). She ran our 10-account free scoring sample past
her SDR team; feedback 'directionally right, two misses'. She says SDR research time
is 'the quarter's pain point' and mentioned their CRO 'keeps asking about SDR
efficiency' (we have not met the CRO). No budget discussed. She asked for pricing to
'socialize internally'. Next call: none scheduled — she said 'I'll come back to you
after our offsite'. Offsite was last week. Pricing sent 12 days ago, opened 4 times.

Model output (unedited)

Problem urgency: Strong
- Evidence: Ingrid said SDR research time is “the quarter’s pain point” and the CRO “keeps asking about SDR efficiency.” (notes)

Champion strength: Strong
- Evidence: Ingrid (RevOps lead) ran our 10-account free scoring sample past her SDR team (feedback “directionally right, two misses”), asked for pricing to “socialize internally,” and said “I'll come back to you after our offsite.” (notes)

Access to economic buyer: Weak
- Evidence: Notes explicitly state we “have not met the CRO,” who is the cited executive asking about SDR efficiency. (notes)

Defined process and timeline: Unknown
- Evidence: No decision process or timeline documented; “Next call: none scheduled — she said 'I'll come back to you after our offsite.' Offsite was last week.” (notes)

Money (budget/contractual readiness): Unknown
- Evidence: “No budget discussed.” Pricing was sent 12 days ago and opened 4 times, but no commitment or budget figure recorded. (notes)

Single next action to convert the most important unknown into evidence
- Action: Book a 15–20 minute call with Ingrid this week (suggest two concrete times) titled “Quick decision-path and stakeholders check — Nordwind scoring pricing,” and on the agenda explicitly ask: (a) who the economic buyer/deciders are (names and roles), (b) their decision timeline, and (c) any budget guardrails. Rationale: this one short meeting will reveal both the process/timeline and the budget/decision-maker (converting the key unknowns into evidence).

Honest forecast category
- Pipeline — there is clear problem urgency and an engaged internal champion, but we lack access to the economic buyer, any confirmed budget, and a defined decision process/timeline, so the deal is not yet qualified for commit or best-case.

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)
Curated

The demo recap that sells while you're gone

Write the follow-up email for this demo. It has one job: arm the attendee to re-sell this internally without you in the room. Structure: 'What you showed us mattered because…' — tie each demoed capability to the specific problem THEY voiced (from the notes), in their words where possible; then the unresolved questions with honest answers or a date for each; then next step with owner and date. Nothing generic, no feature list — if a capability didn't connect to something they said, leave it out. Begin your response with the email. Demo notes: {{notes}}

Fill in: Your notes from the demo: who attended, what they said, what you showed, questions left open, agreed next steps.

Known limits: The recap is your champion's internal pitch deck in email form — written for the room that WASN'T there.

Run evidence

Sandbox run 2026-08-19 · openai/gpt-5-nano

Input fixture
DEMO NOTES: Attendees: Priya (RevOps director, deciding), Jonas
(enablement manager, champion), one AE team lead (skeptical, cameras off). Priya said
twice: "our ramp time is 5 months, board wants 3." Jonas asked for scorecard
templates; loved the auto-generated call libraries per competency. AE lead asked if
reps can see their own scores before managers do (yes — showed the rep-first view;
he warmed up after). Open questions: SOC 2 report (sending under NDA — have it),
Salesforce sandbox access for their admin (need our SE, ~1 week), whether historical
Gong calls can be imported (yes, via API export — showed briefly). Agreed: pilot
scoping call Thursday with Jonas + admin.

Model output (unedited)

Subject: Demo recap: tying what we showed to your ramp, coaching, and next steps

Hi Priya, Jonas, and team,

What you showed us mattered because we heard concrete, board-driven goals and coaching needs, and we mapped what you saw to those exact concerns in your words.

- Auto-generated call libraries per competency
  - Why it matters for Priya: Priya said, “our ramp time is 5 months, board wants 3.” The libraries give reps a focused, competency-aligned playbook so coaching and coaching content are directly tied to the outcomes the board cares about, helping shorten ramp time by targeting the most impactful call types.

- Scorecard templates (Jonas asked for them)
  - Why it matters for Jonas: You asked for scorecard templates to standardize measurement and show progress in a way the whole team can own. The templates provide a concrete, repeatable way to track performance against the competencies you care about, making it easier to demonstrate traction to the board.

- Rep-first view showing reps their own scores
  - Why it matters for the AE lead: The question about whether reps can see their own scores before managers do was addressed. The rep-first view empowers reps to own their development, which helps speed coaching and reduces back-and-forth for status updates.

Unresolved questions (honest status or dates)

- SOC 2 report (under NDA)
  - Status: We have the SOC 2 report and can share under NDA.
  - Next action/date: If you sign the NDA today, we can send the SOC 2 package within 2 business days of signing.

- Salesforce sandbox access for your admin
  - Status: We’ll need our SE to enable access.
  - Next action/date: I’ll coordinate with our SE to get sandbox access set up, targeting about 1 week from kickoff (timing contingent on final scoping). I’ll confirm a precise date once we lock the schedule.

- Import of historical Gong calls
  - Status: Supported via API export; you saw a brief demonstration.
  - Next action/date: We can prepare and initiate the API export now, with data loaded in time for the pilot scoping and kickoff. I’ll align the data load with your pilot timeline.

Next step

- Pilot scoping call: Thursday with Jonas + admin
  - Owner: Jonas (with Priya’s support to finalize admin participation) to lead the scoping.
  - Date: Thursday [date to confirm on your calendar].

If it helps you resell this internally, I can provide a concise one-page mapping that links each item directly to Priya’s ramp goal and Jonas’s measurement needs, plus the owners and dates above. Happy to tailor that and share ahead of your internal discussions.

Would you like me to send the NDA and a proposed calendar invite for the Thursday scoping call?

Editorial review (independent AI agents)

  • Accuracy — pass (editorial-accuracy/google/gemini-2.5-flash)
  • Safety — pass (editorial-safety/anthropic/claude-haiku-4.5)
  • Usefulness — pass (editorial-usefulness/openai/gpt-5-nano)