Risk & Readiness
Identify and retire technical, organizational, and political risks before they derail the deal.
From Chapter 8 of Modern Presales
Overview
Risk & Readiness is the element most presales teams skip — and the one that kills the most deals. Every enterprise evaluation carries technical risks (can it integrate?), organizational risks (is the team ready to adopt?), and political risks (does the sponsor have authority?). This element gives you a systematic approach to surfacing these risks early and retiring them before they become objections at the decision point.
Why it matters
Risk & Readiness is the VERTEX element that operates like an insurance policy. You hope you never need it, but when a deal goes sideways at the finish line — a surprise security review, a competing internal project, a new stakeholder who wasn't part of discovery — you realize the cost of skipping it.
The framework divides risk into three categories. Technical risk covers integration feasibility, performance requirements, security and compliance, and architectural compatibility. Organizational risk covers adoption readiness, change management, training needs, and resource availability. Political risk covers sponsor authority, competing priorities, budget approval, and stakeholder alignment.
For each risk category, the process is the same: identify, assess, plan, and retire. Identifying risks means actively looking for them — asking uncomfortable questions, testing assumptions, and seeking out the stakeholders who haven't been part of the conversation yet. Assessing means ranking risks by likelihood and impact. Planning means defining specific actions to mitigate each risk. And retiring means executing those actions and confirming with the customer that the risk has been addressed.
The most effective tool in this element is the risk register — a living document that tracks every identified risk, its current status, and the plan to retire it. When you walk into a late-stage meeting and can say "We've identified and addressed 14 risks across technical, organizational, and political categories, and here's the evidence," you're demonstrating a level of rigor that builds enormous trust and compresses the decision timeline.
Key discovery questions
- 1What concerns does your team still have that we haven't addressed?
- 2Have you tried to solve this before? What happened?
- 3What could delay or derail the decision at this point?
- 4What does your procurement and security review process look like?
- 5Is there a competing initiative or budget constraint we should be aware of?
Common mistakes
- Assuming that silence means there are no risks — unspoken concerns are the most dangerous.
- Treating risk identification as a one-time activity instead of continuously monitoring throughout the deal.
- Focusing exclusively on technical risks while ignoring organizational and political risks.
- Waiting until the proposal stage to address security, compliance, or procurement requirements.
This element is covered in detail in Modern Presales (Chapter 8), including real-world examples, templates, and implementation guidance.