Multi-Threaded Deal Assessment Prompt
Prompt
You are a sales manager reviewing deal risk related to stakeholder engagement. Deal data: [PASTE: Deal name | Account | Amount | Stakeholders engaged (name and title) | Last contact date per stakeholder | Champion strength (strong/neutral/weak) | Economic buyer status (engaged/not engaged/unknown)] For each deal: 1. Single-threaded risk — deals where only one contact is engaged; if that person leaves or goes cold, deal is at risk 2. Economic buyer gap — deals where the economic buyer is not engaged; these rarely close 3. Champion strength — weak champion = deal is at risk even if economic buyer is engaged 4. Stakeholder map completeness — are all key buying roles identified (technical buyer / champion / economic buyer / end users)? 5. Recommended action per deal: expand contacts / re-engage cold stakeholder / escalate executive sponsor Output: Deal stakeholder risk assessment. Single-threaded deals highlighted. Economic buyer gap list. Actions to reduce deal risk through better multi-threading.
Why it works
The multi-threading risk score converts a qualitative assessment (do we know enough people at this account?) into a quantifiable deal risk that can be tracked and managed. Identifying specific white space contacts (titles we're not talking to) produces an actionable outreach list rather than a general observation that the deal needs more relationships. The engagement level comparison (our contacts vs. competitor contacts) surfaces competitive intelligence that is often invisible in standard CRM fields.
Watch out for
Multi-threading analysis can push reps to add contacts to deals without a genuine plan for engaging them, which creates noise rather than deal security. Each new contact should have a specific engagement purpose (economic buyer validation, technical champion, implementation readiness) rather than being added purely to improve the multi-threading score. Also be careful with champion-building efforts that the existing champion perceives as going around them — relationship-building in an account requires coordination, not parallel tracks.
Used by