> 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 Customer Responses ![Mind Reasoner](/_fern-img/466e07efd0202b28f29ec8dda3be88918c85104c2652efceb8ff717127f861ca.webp) > **Stop Reacting. Start Predicting.** > > **The shift:** Create a customer mind. Ask it any question. Know how they'll respond before the meeting. > > **Result:** Win significantly more deals with accurate customer prediction. --- ## What You Can Predict #### Objections **Know before they say it:** * Which objections they'll raise * Why they'll raise them * What will overcome them * Which responses will work Test your responses beforehand. #### Pain Points **Uncover hidden pain:** * What they care about (vs. what they say) * Which questions will unlock them * Real priorities vs. stated ones * What creates urgency for them Ask the right questions. #### Messaging **Test what resonates:** * Does your pitch land with them? * Which benefits matter to them? * What proof do they need? * How to frame your solution Know what works before presenting. #### Decision Criteria **Understand their process:** * Price vs. value: what matters more? * Speed vs. caution in decisions * Risk tolerance level * Who else influences them Navigate their buying process. --- ## How to Predict #### 1. Create Customer Mind Upload 1 conversation transcript ```bash > "Create a mind for Lisa Martinez, VP Sales at Acme, using /Documents/calls/acme-vp-sales.vtt" ``` **Training:** 5-15 minutes #### 2. Ask Any Question **Predict objections:** ```bash > "I'm presenting $200K pricing tomorrow. What objections will you raise? Why?" ``` **Uncover pain:** ```bash > "What are your biggest pain points right now? > What would make you take action?" ``` **Test messaging:** ```bash > "If I position our solution this way: [your pitch], how will you respond? Will it resonate?" ``` #### 3. Prepare and Win Get predictions. Refine your approach. Enter meeting prepared. **You'll know:** * What they'll say * What they need to hear * What will close them --- ## Real Examples #### Predict Objections ### Before the Meeting **You ask customer mind:** ```bash > "I'm presenting $400K pricing. What objections will you raise?" ``` **Customer mind predicts:** ``` I'll raise 3 objections: 1. ROI Timeline: "How fast will we see return?" Real concern: Got burned by 18-month implementation before What I need: Conservative 12-month payback with proof 2. Budget: "This is 2x what we budgeted" Real concern: Political capital after last failed purchase What I need: Competitor cost comparison + references 3. Risk: "What if it doesn't work?" Real concern: My job is on the line What I need: Pilot program with success metrics ``` ### Test Your Response **You ask:** ```bash > "If I respond to your ROI concern with conservative 12-month payback and 3 customer references who saw return in 10 months, will that address it?" ``` **Customer mind confirms:** ``` YES. That addresses my concern. Why it works: - Conservative timeline matches my risk profile - Proof from customers (not promises) builds credibility - 10-month actual results give me buffer With this proof, I'm convinced on ROI. ``` ### In the Actual Meeting **What happens:** * Customer: "This is 2x our budget and how fast will we see return?" * You: *\[prepared response with conservative ROI + references]* * Customer: "This is exactly what I need. Connect me with those references." **Result:** Deal won. Because you predicted and prepared. #### Uncover Pain ### Before Discovery Call **You ask prospect mind:** ```bash > "I have a discovery call with you tomorrow. What are your biggest pain points?" ``` **Prospect mind reveals:** ``` PAIN POINTS (that I won't volunteer easily): 1. Team Retention Crisis What's happening: Best rep just quit Why I care: Terrified of losing more top performers What I'll say initially: "We're doing okay" Question that unlocks me: "How is your setup affecting team morale?" 2. Rep Productivity What's happening: Team spends 60% time on admin Why I care: $2.4M annually wasted on non-selling What I'll say initially: "Some inefficiency" Question that unlocks me: "How many hours per week on admin?" 3. Forecast Accuracy What's happening: Don't trust pipeline numbers Why I care: Lost credibility with CEO due to missed forecasts What I'll say initially: "We manage" Question that unlocks me: "What happens when forecasts are wrong?" ``` ### Test Your Questions **You ask:** ```bash > "If I ask: 'How is your current setup affecting team morale and retention?', will you open up?" ``` **Prospect mind confirms:** ``` YES. I'll open up. What I'll say: "Actually... my best rep just quit last month. She was frustrated spending 60% time on admin instead of selling. I'm worried we'll lose more. That's really why I'm looking." Why this question works: - Hits my hidden concern directly - Shows you understand the real problem - Creates trust—I'll be honest with you ``` ### In Actual Discovery Call **What happens:** * You: "How is your current setup affecting team morale and retention?" * Prospect: *\[opens up about retention crisis, exactly as predicted]* * You: *\[addresses the real pain point]* **Result:** Uncovered \$100K opportunity competitors missed. #### Test Messaging ### Before Demo **You ask customer mind:** ```bash > "I'm demoing tomorrow. If I lead with ROI and efficiency gains, will that resonate? Or should I lead with something else?" ``` **Customer mind reveals:** ``` DON'T lead with ROI. Why it won't work with me: - I've heard ROI promises before—burned by vendor who overpromised - I'm skeptical of efficiency gain claims - This won't differentiate you from competitors What WILL resonate with me: - Lead with risk mitigation (my #1 concern) - Show me how you reduce my implementation risk - Provide proof of smooth rollouts (not just ROI numbers) - Then talk about conservative efficiency gains If you lead with risk mitigation + proof, you have my attention. If you lead with ROI, I mentally check out. ``` ### Refine Your Approach **You test:** ```bash > "What if I lead with: 'Here's how we ensure smooth implementation with zero downtime' and show 3 customer references with technical rollout stories. Then discuss conservative efficiency gains. How will you respond?" ``` **Customer mind confirms:** ``` PERFECT. This will work. Why: - Risk mitigation speaks to my top concern - Technical rollout proof = credibility - Conservative gains show you're not overpromising - Customer references give me confidence Lead with this. You'll have my full attention. ``` ### In Actual Demo **What happens:** * You: *\[leads with risk mitigation + rollout proof]* * Customer: "This is exactly what I need to see. Those references—can I talk to them?" **Result:** Demo resonated. Deal moved forward. --- ## Common Scenarios #### Pricing Objections **Predict:** * Is "too expensive" real or negotiation tactic? * Do they care about price or value? * What ROI timeline convinces them? * Which proof points overcome price concerns? **Test responses** before the call. Know what works. **Outcome:** Win significantly more deals with pricing objection preparation #### Feature Gaps **Predict:** * Do they actually care about missing features? * Is it a checklist item or real need? * What alternative approach will they accept? * Which features truly matter to them? **Know which gaps matter** to THIS buyer. Focus there. **Outcome:** Win deals despite feature gaps when you know what they actually need #### Risk Concerns **Predict:** * What past failures make them cautious? * What proof reduces their risk perception? * Which guarantees matter to them? * How do they evaluate vendor reliability? **Address their specific risk concerns** with the right proof. **Outcome:** Win risk-averse buyers by knowing exactly what reassures them #### Timeline Objections **Predict:** * Is "need to think about it" real or brush-off? * What's the actual timeline concern? * What would create urgency for them? * Who else needs to approve? **Know if it's real** or just a stall. Respond accordingly. **Outcome:** Faster deal cycles when you understand their real timeline --- ## Quick Start #### 1. Create Customer Mind Upload 1 transcript from any past conversation: * Sales calls * Discovery meetings * Email exchanges * Demo feedback **Training:** 5-15 minutes per customer #### 2. Predict Before Every Meeting Ask the customer mind: * What objections will you raise? * What do you care about most? * How will you respond to this approach? Get answers. Prepare accordingly. #### 3. Track and Improve After meetings: * Did they respond as predicted? * What surprised you? * Update customer mind with new info **Result:** Predictions get better over time --- ## Implementation #### MCP (No Code) **Use Mind Reasoner through Claude Code** No coding. Just natural conversation in Claude. **You:** ```bash > Create a customer mind for David Kim, CTO at FinanceApp, using /Documents/calls/financeapp-cto.vtt ``` **Mind Reasoner:** ``` ✓ Training customer mind... (~10 min) ``` **You:** ```bash > I'm presenting $300K pricing tomorrow. What objections will David raise? Why will he raise them? ``` **Mind Reasoner:** ``` Based on David's decision-making patterns: Objections he'll raise: 1. Integration Complexity - his team is slammed 2. Security Compliance - reports to board on this 3. Vendor Lock-in - got burned before What he needs to say yes: - Technical architecture review - Security/compliance documentation - API flexibility demonstration - Reference from similar fintech company ``` **You:** ```bash > If I address integration concerns by offering a 2-week technical pilot with his team, will that work? ``` **Mind Reasoner:** ``` YES. This will work with David. Why: Shows you understand his constraint (team capacity) Lets him validate before full commitment Reduces his risk He'll say: "A pilot makes sense. Let's scope it." ``` [MCP Tools Reference →](/mcp-tools) #### Direct API **Build prediction into your workflow** ```javascript const API_BASE = 'https://api.reasoner.com/api/mindsim'; // Create customer mind and train // (See API Quick Start for full workflow) // Predict objections before meeting const objectionPrediction = await fetch(`${API_BASE}/simulate`, { method: 'POST', headers: { 'Authorization': `Bearer ${API_KEY}`, 'Content-Type': 'application/json' }, body: JSON.stringify({ mindId: customerMindId, scenario: { message: "I'm presenting $300K pricing. What objections will you raise? Why?" } }) }).then(r => r.json()); // Test response approach const responseTest = await fetch(`${API_BASE}/simulate`, { method: 'POST', headers: { 'Authorization': `Bearer ${API_KEY}`, 'Content-Type': 'application/json' }, body: JSON.stringify({ mindId: customerMindId, scenario: { message: `If I respond to your objection this way: [approach], will it work?` } }) }).then(r => r.json()); console.log('Prediction:', objectionPrediction.message); console.log('Response test:', responseTest.message); ``` [API Documentation →](/api-quick-start) --- ## Next Steps #### [Win Complex Deals](/workflow-sales-win-complex-deals) Navigate enterprise deals and competitive situations #### [MCP Quick Start](/mcp-quickstart) Set up in 5 minutes #### [API Quick Start](/api-quick-start) Build into your CRM > **Info** > > Questions? Email [support@reasoner.com](mailto:support@reasoner.com)