Draft targeted discovery questions, objection responses, and outreach language tailored to prospect context, industry, and role — supporting SPIN, Challenger, and MEDDPICC. Trigger on: discovery questions, what should I ask, sales discovery, objection handling, prospect research, outreach planning, how to open the call.
Accelerate deal velocity by generating discovery questions and outreach messaging that demonstrate deep prospect understanding, uncover critical buying criteria, and build credibility before calls. When Harmony conversation data is available, grounds personalization in real patterns from successful sales conversations.
Gather prospect context: Provide company name, prospect title/role, industry, company stage (early stage/mid-market/enterprise), and their current solution (if applicable)
Input previous interactions (if available): Share any prior email exchanges, call notes, or Harmony conversation data to personalize questions around what the prospect has already shared
Define sales objective: Specify whether you're seeking pain discovery, budget uncovering, timeline identification, competitive differentiation, or decision-process mapping
Select methodology: Choose from SPIN (Situation/Problem/Implication/Need), Challenger (teach/tailor/take control), MEDDPICC (budget/decision/timeline), or balanced approach
Specify role targeting: Confirm prospect's function (Finance, Engineering, Operations, Sales, Marketing, Executive) to tailor question depth and language
Set context on deal stage: Indicate if this is cold outreach, early exploration, active evaluation, or reactivation scenario
Request outreach variants: Ask for email subject lines, opening hooks, value propositions, and follow-up sequences for different response scenarios
## Discovery Questions
### Priority Questions
- [Question designed to uncover specific pain or criteria]
- [Question that probes decision process]
- [Question that uncovers budget or resource constraints]
### Follow-Up Probes
- [Secondary question to dig deeper]
- [Question that reveals competitive landscape thinking]
### Industry/Role-Specific Questions
**[Role title] context:**
- [Tailored question specific to their function and priorities]
## Objection Responses
### "We're happy with our current solution"
**Acknowledgment & Bridge**: [Response that validates their statement, then pivots to a specific gap or capability]
**Redirect with Proof Points**: [Short example of specific improvement or use case they might not have considered]
### "We don't have budget for this"
**Reframe**: [Response that emphasizes ROI or cost savings without discounting]
## Outreach Sequence
### Cold Outreach
**Subject Line Options**
- [Specific, non-generic subject that shows research]
- [Alternative that emphasizes specific value or pain point]
**Opening Hook** (1-2 sentences)
[Demonstrates specific knowledge of their company/situation]
**Value Proposition** (clear and specific)
[Benefit stated in terms of their business outcome, not feature]
**Call to Action** (specific and low-friction)
[Single, clear next step; usually 15-min exploratory call]
---
### Follow-Up After No Response (3-5 days)
[Brief, value-add message with new angle or insight]
### Follow-Up After Initial Interest
[Questions and next steps that build momentum]
### Handling Objections in Sequence
[Specific messaging for most common "noes"]
## Context-Aware Personalization Notes
- If Harmony data provided: Reference specific quotes or situations the prospect mentioned in prior calls
- Adjust question sophistication based on company stage and role seniority
- Surface competitive alternatives the prospect might be evaluating
- Align questions with current economic/industry shifts relevant to their sector
Prospect Context
Previous Interactions (from warm intro email)
VP Operations context (financial services):
Acknowledgment & Bridge: "I hear you—and honestly, spreadsheets and Tableau have gotten your team pretty far, especially through rapid growth. I'm curious though: as you add 12 more ops people, are you planning to multiply your reporting infrastructure effort by 1.5x? That's what we typically see with the scaling ops teams face. Most teams we work with realized their setup worked great until 15-20 people—then it broke. Have you thought through how you'll scale reporting without it becoming a bottleneck?"
Redirect with Proof Points: "A few of your peers at companies like Ramp and Mercury faced the exact same situation—they had reporting they felt was working. What changed for them was that board and finance started asking real-time questions that required data they didn't have in spreadsheets. Does that resonate at all?"
Reframe: "Totally understood—and honestly, I wouldn't recommend squeezing it in if there's other priorities. What I usually see though is that the 50+ hours per month your ops team spends on manual reporting and ad-hoc data requests costs you roughly $[calculated based on team size and fully-loaded cost]—which usually exceeds platform cost significantly. Would it make sense to run a quick analysis on what your current reporting setup costs you?"
Bridge with Specificity: "Tableau's great for what it does—and I'm not suggesting you rip and replace. Most teams we work with actually keep Tableau. What they add is a real-time operational layer that Tableau wasn't designed for. For example, for payment processing visibility, you want immediate alerts and dashboards that update every minute, not on-demand analysis. Does that distinction matter for your use case, or is batch reporting really what you need?"
Subject Line Options
Opening Hook (1-2 sentences) "Hi Sarah, I saw your recent post about building scalable ops infrastructure at TechFlow—and it resonated because I've been talking to a lot of VP Operations at scaling fintech companies facing the exact same transition: how do you keep real-time visibility into payment processing and ops metrics as you go from 8 to 20-person teams?"
Value Proposition (clear and specific) "What we're seeing is that spreadsheet and Tableau setups work great until about 15 people—then the manual reporting effort becomes a major bottleneck. Most ops teams end up spending 40-60+ hours a month on reporting instead of strategy. We work with companies like Ramp and Mercury to flip that: real-time operational dashboards that require zero manual updates, plus automated alerts for payment and ops anomalies."
Call to Action (specific and low-friction) "Curious whether this resonates for your scaling situation. Totally happy to just brainstorm your ops reporting challenge—no pitch, 15 minutes, that's it. Does next Tuesday or Wednesday work for a quick call?"
Subject: "One specific thing I was wondering about re: your Series B"
"Hey Sarah, I realized I should have asked a more specific question in my first note. With the Series B raise and your ops team doubling, I imagine investor board reports are getting asked more frequently. Are board reporting requests creating a new kind of pressure on your finance and ops reporting? If yes, this might be worth 15 minutes of conversation. If not, no worries at all."
Subject: "Quick ops reporting audit for TechFlow?"
"Great to hear from you. Before our call, I'd love to understand your current setup better. Quick context-setting: Can you walk me through what a typical week of reporting requests looks like for your team? And—totally candid—what's the most frustrating part of your current Tableau/spreadsheet setup today?"
If "we're not ready yet": "Totally fair. I'd suggest revisiting this conversation once you hit 15 people on the ops team—that's usually the inflection point. I'm happy to check back in Q3. In the meantime, if you hit a point where reporting becomes painful, feel free to reach out."
If "our tech stack is locked down": "Got it. Most of the time this isn't a Tableau vs. us conversation—it's about adding a real-time layer your current stack doesn't have. A lot of teams integrate us alongside Tableau. But worth understanding: are you locked down on a vendor, or locked down on budget?"
If no mutual connection or prior interaction, lead with extreme specificity about their industry/company stage rather than generic value prop. Example: "I work with Series B fintech companies where ops teams are stuck between spreadsheets and expensive data warehouses—I've noticed TechFlow recently hired 3 ops analysts, which usually signals you're hitting the scaling pain point."
If prospect previously said "not now," avoid re-pitching. Instead: "I remember we chatted 6 months ago and the timing wasn't right. Since then, we've worked with companies very similar to yours (Ramp, Mercury) and solved a specific problem I think you're probably hitting now—real-time ops visibility as you scaled ops team. Worth 15 minutes to see if this still doesn't fit?" Reference the specific context from dead deal to show you did your homework.
Generate different question sets for different roles:
Use outreach sequence to route each stakeholder to the right conversation angle.
If prospect currently uses competitor (e.g., Tableau, Looker), don't attack the tool. Instead ask: "What can your current solution not do that you wish it could?" This uncovers gaps your platform fills without positioning as direct replacement. Example objection response: "Looker is great for analysis. We're built for real-time operations—different use case entirely. Most teams use both."
Invest heavily in research (LinkedIn, recent news, funding announcements, job postings). Lead with a very specific observation about their company or industry trend. Example: "I noticed TechFlow posted for 2 ops analyst roles last month—that usually indicates you're moving from founder-led ops to scaling ops infrastructure. Is that accurate?"