How to Use a Prospect's Tech Stack to Sharpen Your Discovery Call

Knowing what software a prospect uses before your discovery call is one of the highest-leverage advantages an SDR can have — it lets you skip generic qualification questions and go straight to the pain that actually matters. Most reps spend the first 10 minutes of a discovery call asking things they could have answered in 5 minutes of research. That wastes the prospect's time and signals you haven't done the work. When you walk in knowing their stack, you walk in knowing their workflow, their likely frustrations, and which competitor you're up against.

Why does a prospect's tech stack matter in discovery?

A company's software stack is a map of how they work. Each tool reflects a decision someone made about a specific problem — and every tool in that stack is either solving that problem well or creating new ones. When you know the map before the call, you can ask questions that land at the intersection of their current process and your product's value. That's where real discovery happens.

Most discovery frameworks — MEDDIC, SPIN, Challenger — assume you're starting from scratch. In practice, you rarely are. A prospect using a legacy CRM alongside three point solutions is telling you something specific: they've outgrown a monolithic system and are patching gaps manually. A prospect running your direct competitor is telling you something different: they have budget, they've validated the problem category, and they've already made a buying decision once. Your job in each case is completely different, and the tech stack is what tells you which situation you're in.

According to Gartner's research on the B2B buying journey, buyers spend only 17% of their total purchase process talking to potential suppliers — and that time is split across multiple vendors. You don't get unlimited chances to run a thorough discovery. Every question you ask has to count. Stack intel compresses the early qualification phase so you can spend your limited time on the questions that actually move a deal.

"The reps who consistently book second meetings are the ones who reference something specific about how we work in the first call. It tells us they're not just running a script."

— VP of Sales, 80-person SaaS company (Stealery customer)

How do you find a prospect's tech stack before the call?

The most reliable free source is job postings. Companies name specific tools in job requirements constantly — a posting for a "Marketing Operations Manager" that requires "HubSpot, Segment, and Looker" tells you three confirmed tools in their stack. This data is public, constantly refreshed, and covers companies that don't appear in any enrichment database.

Job postings

Search the company on LinkedIn Jobs, Indeed, or Greenhouse. Filter for roles in operations, engineering, marketing, and finance — these departments name tools the most explicitly. A single job posting often surfaces 4–6 confirmed tools. The advantage over enrichment tools is recency: a job posted last week reflects the stack they're actively using today, not 18 months ago.

G2 and Capterra reviews

If employees at the target company have left reviews on G2 or Capterra, those reviews frequently mention the other tools they integrated with or migrated from. Search the company name on G2 directly — many profiles show which products that company's employees have reviewed.

LinkedIn employee profiles

Sales ops, RevOps, and IT staff list tools in their experience sections and skills. A RevOps manager at the company who has "Salesforce, Outreach, Gong, and Clari" in their profile is telling you the full sales tech stack. This takes 3 minutes and yields high-confidence data.

Technographic tools

For scale, technographic databases remove the manual work. Tools like Stealery let you search by a specific competitor's name and pull a list of companies confirmed to be using it — filtered by company size, location, and hiring signals. If you're working a list of 200 accounts, doing this manually for each one isn't realistic. Running a competitor filter and getting a pre-qualified list in 30 seconds is.

What discovery questions does the tech stack unlock?

The goal is not to ask a prospect what tools they use — you already know. The goal is to ask questions that assume you know, and use that knowledge to get to friction faster. This is the shift from generic discovery to technographic discovery.

Integration and workflow questions

Start here. "I saw you're running [tool] — how does that connect to the rest of your process for [workflow]?" This question does three things: it signals you did your homework, it opens a workflow conversation rather than a product conversation, and it surfaces integration gaps immediately. Integration is where pain lives in mature stacks.

• "How does [tool A] hand off to [tool B] in your current setup?"
• "Is the data from [tool] making it into your CRM cleanly, or is there still manual work in that step?"
• "Which part of that workflow still feels like it shouldn't be as manual as it is?"

Adoption and satisfaction questions

Knowing they have a tool doesn't tell you if they're happy with it. These questions surface latent dissatisfaction without telegraphing your pitch.

• "How long have you been on [tool]? What made you choose it at the time?"
• "If you were scoping that decision again today, would you make the same call?"
• "What's the one thing [tool] still doesn't do well for your team?"

Outcome questions anchored to their stack

Once you understand the workflow and the friction, anchor outcome questions to the specific tools they named. This keeps the conversation grounded and avoids abstract benefit claims.

• "Given the way [tool] is set up for you now, what would 'better' actually look like — not in theory, but for your team's day-to-day?"
• "If [specific integration gap] got fixed, what does that unblock for you?"

Salesloft's analysis of top-performing discovery calls found that the highest-converting reps ask fewer total questions but ask more specific ones — questions that reference the prospect's actual situation rather than hypothetical pain. Technographic prep is the single fastest way to shift from generic to specific without guessing.

How do you use competitor tools to sharpen your positioning?

When a prospect's stack includes a direct competitor, your discovery call structure changes entirely. You're not validating whether the problem exists — they already paid someone to solve it. You're finding out whether that solution is actually working.

Skip the problem-education phase

Reps who don't check the stack often spend 15 minutes establishing why a category of problem matters — to a prospect who already has a tool in that category. That's not discovery; it's a waste of mutual time. When you know they're using a competitor, open with: "You're already on [competitor] — this call is really about whether what you're getting from them is actually what you need. What's working well, and where are you still hitting walls?" That's a peer-to-peer conversation, not a sales pitch.

Use the competitor as a calibration anchor

Every competitor has known strengths and known gaps. If you know them, you can ask questions that lead the prospect to articulate those gaps in their own words — which is far more powerful than you claiming those gaps exist.

• "[Competitor] tends to be strong on [X] — is that the part of the workflow you care most about, or is there another area that matters more to you right now?"
• "A lot of teams we talk to who came from [competitor] found that [known gap] was the friction point. Has that come up for you at all?"

Understand the switching threshold before pitching

A prospect using a competitor isn't automatically a prospect who wants to switch. Before you pitch differentiation, establish switching cost awareness. "If you decided to make a change, what would the migration look like from your side — data, training, internal buy-in?" The answer tells you whether the pain is real enough to justify switching or whether this is a conversation for 6 months from now.

What mistakes do reps make when using tech stack intel in discovery?

Technographic data is a precision instrument, but it gets used as a blunt one more often than not. These are the patterns that waste the intel.

Leading with the tool name instead of a question

"I see you're using Salesforce" is not a discovery question — it's a statement that gets a "yep" and moves nowhere. The tool name should appear in the setup of a question, not as the question itself. "I saw you're running Salesforce — how are your reps actually using it for [specific workflow]?" opens a conversation. "You're using Salesforce, right?" closes one.

Assuming the tool means the problem

A company that has a tool doesn't necessarily have the pain your product solves. A CRM doesn't mean they have a pipeline visibility problem. A marketing automation platform doesn't mean they have a lead quality problem. The stack tells you the workflow; the discovery call tells you whether the workflow is broken. Don't skip that step.

Using old technographic data

A company that was using a competitor 12 months ago may have churned off it since. Stale data is worse than no data — it makes you look uninformed when you reference a tool they've already migrated away from. Prioritise sources with high recency: job postings from the last 30 days, recent G2 reviews, active LinkedIn profiles. Treat any technographic data older than 6 months with scepticism.

Showing all your cards at once

Listing every tool you found in the first 30 seconds reads as unsettling, not impressive. Reference one or two specific tools as a signal that you prepared. Let the rest inform your questions invisibly. The goal is to ask better questions — not to recite their stack back to them.

The teams who do this well treat the tech stack as a call preparation tool, not a conversation topic. It shapes every question they ask without ever becoming the subject of the call itself. That's the level of technographic discovery that consistently converts — and it's the habit worth building before your next discovery block.