> This page is for version v8.3.0 (default). > For other versions, use one of these documentation indexes: > - v8.3.0 (default): https://docs.workflows.com/v-8-3-0/llms.txt > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.workflows.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.workflows.com/_mcp/server. # Predict Team Responses ![Mind Reasoner](/_fern-img/466e07efd0202b28f29ec8dda3be88918c85104c2652efceb8ff717127f861ca.webp) > **Stop Rolling Out. Start Validating.** > > **The shift:** Create team minds. Test any change. Know how they'll respond before implementation. > > **Result:** Drive adoption of revenue-critical changes. Avoid resistance and attrition. Optimize revenue engine. --- ## What You Can Predict #### Comp Plan Changes **Know before rolling out:** * Will this motivate or demotivate? * Which reps will game the system? * What unintended consequences? * Which behaviors will it drive? Test comp plans with team minds. #### Territory Changes **Predict responses:** * Who will resist reassignments? * Which reps will threaten to quit? * How to minimize attrition? * What concerns need addressing? Navigate territory changes successfully. #### Quota Adjustments **Understand impact:** * Will team view quotas as achievable? * What pushback will you get? * Which reps will sandbag? * How to position for buy-in? Set quotas that drive performance. #### Process Changes **Identify friction:** * Will team actually adopt this? * What causes abandonment? * Which incentives drive adoption? * Where will resistance emerge? Design processes team will follow. --- ## How to Predict ### 1. Create Team Minds Upload transcripts from team members: one-on-one meetings, team calls, performance reviews, and feedback sessions. **Training:** 5-15 minutes per team segment ### 2. Test Any Change **Validate comp plans:** ```bash > "SCENARIO: Your VP of Sales is announcing a new comp structure effective Q1 2026. Current plan: $75K base, 8% commission on all deals. New plan: $80K base, 12% commission on deals above quota, 4% on deals below quota. You're currently at 92% of your $800K annual quota. QUESTION: How will you respond to this comp change? Will this motivate you to push harder vs. make you feel penalized? What concerns do you have?" ``` **Test territory changes:** ```bash > "SCENARIO: RevOps is restructuring territories next month. You're losing your top account ($250K ARR, 3-year relationship) but gaining 3 mid-market accounts ($60K, $75K, $85K ARR - all net new with no existing relationships). Your quota stays at $800K annually. QUESTION: How will you respond to this territory change? Will you accept this vs. threaten to quit? What would make this acceptable to you?" ``` **Check process adoption:** ```bash > "SCENARIO: Leadership is mandating MEDDICC qualification for all opportunities over $50K starting next quarter. You'll need to document Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion in Salesforce before moving deals to demo stage. This adds 15-20 minutes per opportunity. QUESTION: Will you actually use MEDDICC consistently vs. find workarounds? What friction points will cause you to abandon this process?" ``` ### 3. Implement with Confidence Get predictions, address concerns, and roll out successfully knowing how team will respond, what objections to address, and what drives adoption. --- ## Implementation #### MCP (No Code) **Use Mind Reasoner through Claude Code** **You:** ```bash > Create minds for our sales team segments: /Documents/meetings/top-performer-sarah.vtt /Documents/meetings/mid-tier-mike.vtt /Documents/meetings/new-rep-jessica.vtt ``` **Mind Reasoner:** ``` ✓ Training 3 team minds... (~10 min each) ``` **You:** ```bash > SCENARIO: Your CRO is rolling out a new comp plan for Q1 2026. Current plan: $75K base + 8% commission on all deals. New plan: $80K base + 12% commission above quota, 4% below quota, spiffs removed. You're at 92% of $800K annual quota. QUESTION: How will you respond to this comp change? Will this motivate you vs. make you start looking elsewhere? ``` **Mind Reasoner:** ``` Top Performer: LOVES IT. Accelerators reward high performance. Mid-Tier Rep: MIXED. Worried about hitting 100% consistently. New Rep: CONCERNED. Still ramping, unlikely to hit 100%. Risk: Mid-tier morale and new rep attrition. ``` [MCP Tools Reference →](/mcp-tools) #### Direct API **Build team prediction into your workflow** ```javascript const API_BASE = 'https://api.reasoner.com/api/mindsim'; // Create minds for team segments const teamSegments = [ { name: 'Sarah - Top Performer', mindId: 'mind_top' }, { name: 'Mike - Mid-Tier Rep', mindId: 'mind_mid' }, { name: 'Jessica - New Rep', mindId: 'mind_new' } ]; // Test comp plan across segments const compPlanTest = await Promise.all( teamSegments.map(async ({ name, mindId }) => { const response = await fetch(`${API_BASE}/simulate`, { method: 'POST', headers: { 'Authorization': `Bearer ${API_KEY}`, 'Content-Type': 'application/json' }, body: JSON.stringify({ mindId, scenario: { message: "SCENARIO: Your CRO is rolling out a new comp plan for Q1 2026. Current plan: $75K base + 8% commission on all deals (variable ~$50K at quota). New plan: $80K base + 12% commission above quota, 4% below quota, all monthly spiffs removed. You're currently at 92% of your $800K annual quota.\n\nQUESTION: How will you respond to this comp change? Will this motivate you to perform better vs. make you start looking elsewhere? What specific concerns do you have?" } }) }).then(r => r.json()); return { segment: name, response: response.message }; }) ); console.log('Team segment responses:', compPlanTest); ``` [API Documentation →](/api-quick-start) --- ## Next Steps #### [Drive Revenue Growth](/workflow-revenue-ops-drive-growth) Navigate pricing, tools, and strategic revenue initiatives #### [MCP Quick Start](/mcp-quickstart) Set up in 5 minutes #### [API Quick Start](/api-quick-start) Build into your RevOps workflow > **Info** > > Questions? Email [support@reasoner.com](mailto:support@reasoner.com)