Prompt Details
Model
Chat - (gpt-5.6)
Token size
399
Example input
[Solution Deployed]: Enterprise AI Workflow Automation & Robotic Orchestration Platform
[Target Enterprise Profile]: Global Logistics & Supply Chain Enterprise ($2B+ Annual Turnover)
[Deal Outcome Scenario]: Loss to Legacy Incumbent in Late-Stage Procurement Due to Perceived Switching Risk
[Deal Financial Scope]: $340,000 ARR Multi-Year Implementation Contract
Example output
EXECUTIVE B2B WIN-LOSS POST-MORTEM & REVENUE DIAGNOSTIC
1. Post-Mortem Root-Cause & Buyer Friction Diagnostic:
- Technical Friction: Enterprise IT flagged concerns regarding legacy database connectors, fearing an unbudgeted 6-month migration effort.
- Commercial Friction: Procurement demanded a 35% discount to match grandfathered renewal terms offered by the incumbent.
- Political Friction: The VP of Infrastructure was reluctant to disrupt established vendor ties, overriding the Head of Automation's championing efforts.
- Stated vs. Real Objections: Stated objection was "budget prioritization," whereas the actual barrier was perceived migration operational risk and job security anxieties.
2. Competitive Displacement & Product Gap Breakdown:
- Incumbent Tactics: Incumbent offered free year-one connector maintenance and leveraged long-standing executive relationships with the CIO.
- Product Gaps: Lack of an automated schema-translation wizard in the POC raised fears of manual data mapping errors.
- Messaging Failures: Value propositions heavily highlighted cutting-edge AI features instead of proven operational business continuity.
3. Executive Stakeholder Post-Mortem Debrief Agenda:
- Champion Debrief Agenda (45-Minute Structure):
- 00–10 Min: Neutral context setting and appreciation for evaluation partnership.
- 10–25 Min: Unvarnished review of the technical evaluation and steering committee voting dynamics.
- 25–35 Min: Analysis of procurement's commercial assessment and incumbent counter-proposals.
- 35–45 Min: Mutual next steps and future re-evaluation trigger points.
- 4 Diagnostic Discovery Questions:
1. "When the final decision was escalated to the CIO, what was the single biggest perceived risk that tipped the balance toward the incumbent?"
2. "If commercial terms had been identical, would your engineering architecture team have chosen our platform on pure technical capability?"
3. "What specific migration guarantees or rollback assurances would your Infosec team have required to approve the switch?"
4. "What scheduled contract milestones or performance reviews exist with the incumbent over the next 12 months?"
4. Account Re-Engagement Strategy & Product Feedback Loop:
- 90-Day Re-Engagement Roadmap:
- Day 30: Send quarterly product updates highlighting legacy migration tooling improvements.
- Day 60: Share an enterprise case study demonstrating successful migration from the same incumbent in a peer logistics firm.
- Day 90: Schedule an informal executive catch-up with the champion prior to their mid-year budget reallocation.
- Product Feedback Loop:
- Engineering: Prioritize zero-downtime automated legacy ETL migration modules in the next sprint.
- Product Marketing: Build a dedicated "Incumbent Displacement & Migration Risk Mitigation" executive whitepaper.
By purchasing this prompt, you agree to our terms of service
GPT-5.6
Conduct executive post-mortem deal diagnostics and win-loss analyses. Identifies root-cause buyer friction, exposes competitive displacement tactics, scripts champion debrief interviews, and structures 90-day pipeline re-engagement roadmaps.
...more
Added 1 week ago
