Roles and context: how to steer the model
Sales reps treat LLM chats like generic search engines, submitting passive queries. Consequently, the model defaults to a fawning, overly agreeable digital assistant that avoids sharp critique, flatters the seller, and provides zero commercial stress-testing.
Deploy Adversarial Role Prompting to detect fatal vulnerabilities in your sales proposals before facing real prospects:
1. The Cynical Buyer Persona: Position the model as an exhausted enterprise CFO who has endured 20 vendor pitches this quarter and seeks any excuse to disqualify. Review your email: 'Where does this smell like unsubstantiated vendor marketing?'.
2. The Competitor Product Lead: Instruct the model to embody your primary market rival: 'Here is our core positioning deck. Identify the 3 weakest architectural points you will exploit against us in competitive bids'.
3. The Procurement Sparring Partner: Instruct the model to simulate hardball contract negotiations: 'Act as a procurement officer demanding a 25% unearned discount. Challenge every concession. Begin the dialogue'.
- BAD
- 'Review my sales training proposal.' Output: 'Your proposal is comprehensive, engaging, and will surely bring great value to participants' (fawning, commercially useless flattery).
- GOOD
- 'Act as a pragmatic VP of Sales managing 50 enterprise quota carriers in telecom. You despise theoretical workshops that leave reps with binders of shelfware. Review this curriculum: [SYLLABUS]. Flag 3 modules you consider a waste of rep selling hours and demand hard simulation replacements.' Output: ruthless, high-value commercial critique that saves the deal.
Act as: Cynical Chief Information Security Officer (CISO) at a Tier-1 commercial bank. Your core priorities: DORA compliance, data sovereignty, minimizing third-party vendor attack surface. You reject 95% of software pitches due to compliance gaps. Here is the outreach email I intend to send to an executive in your seat: [PASTE EMAIL DRAFT OR PROPOSAL EXCERPT] Task: 1. Isolate 3 phrases that immediately trigger security compliance alarms or read like vendor hand-waving. 2. State 2 technical questions regarding data retention and cryptographic key custody that would stump the rep on call. 3. Rewrite the email to front-load the exact compliance credentials needed to survive initial triage.
Variations & alternative scenarios
Procurement Officer Persona: Stress-test payment terms, termination for convenience, and volume tiers.
End-User Persona: Verify whether the proposed workflow automation reduces or adds administrative friction for front-line reps.
Practical exercise
Take your current sales deck or proposal template. Execute the Adversarial CISO prompt to identify hidden commercial risks before your next enterprise review.