Home / Free Tools / Vendor Questions
Field guide · Free · Vendor-neutral

The vendor
conversation guide

26 questions to ask a human risk vendor before you sign anything. Built to show you how a vendor thinks, with notes on what a strong answer sounds like.

26 questions 11 topics By Jason Hoenich Updated Nov 2026

Most vendor calls run on the vendor's script. You get the demo, the logo slide, the AI slide, and a click-rate chart that trends down and to the right. Forty-five minutes later you know what the product does and almost nothing about how the company thinks.

These questions flip the script. They show you a vendor's judgment: where they think the space is going, what they refuse to build, where they keep a human in the loop, and which parts of their product they'd rather you didn't look at too closely.

How to use it. Pick the sections that matter to your program. Nobody needs all eleven in one sitting. Two or three topics, asked well, tell you more than a 200-row RFP spreadsheet.

Works for renewals, new evaluations, analyst-style briefings, and the intro call you agreed to at a conference. Print it and the page turns into a checklist with room for notes.

01 / Direction

Where they're headed

  1. Where do you think this space is going in the next two years, and where does your product fit?
  2. What are you building toward that isn't on your website yet?
  3. What are you choosing not to build, and why?
What to listen forA real point of view and real tradeoffs. A vendor that can't name something they've said no to probably hasn't had to make a hard call yet.
02 / Microsoft Teams

Teams, both sides of it

  1. How are you thinking about Teams as an attack surface and as a place to run the program?
  2. What does a good Teams experience look like to you, for employees and for the people running it?
What to listen forTwo separate answers. Teams as a phishing and impersonation channel is one problem. Teams as the place your program reaches people is another. Good vendors have thought about both.
03 / AI agents as the target

When the agent gets phished

  1. As employees start working with AI assistants and agents, how do you think about the risk that creates?
  2. What do you think the training and testing side of that looks like?
  3. Is that something you're building toward, and what's your sense of how customers are thinking about it?
What to listen forSomething past "don't paste secrets into ChatGPT." Shadow AI, agents acting on an employee's behalf, and prompt injection hiding in everyday content are where this is heading.
04 / AI agents as the tooling

Who's driving the program

  1. How are you thinking about agents helping run the program, such as building and analyzing campaigns?
  2. Where do you think a human should stay in the loop?
  3. How are you thinking about connecting with the AI tools customers already use?
What to listen forNamed approval points. "The AI handles it" without a checkpoint you control is a signal to dig further.
05 / Tabletop and exercises

Rehearsal, not a gotcha

  1. How are you thinking about tabletop and exercise support?
  2. Where do you see the line between simulating an attack on people and helping a team rehearse its response?
  3. Where do you think AI helps in running an exercise, and where doesn't it?
What to listen forAn understanding that exercises are about how a team makes decisions under pressure. The goal is a better response plan, not a list of who fumbled.
06 / Deepfake and synthetic media

Whose voice is that

  1. How are you thinking about realistic voice and video in training, and where do you draw the line?
  2. How do you think about consent for the people being imitated?
What to listen forA written policy. Ask who signs off before an executive's voice gets cloned, where that likeness is stored, and when it gets deleted.
07 / Adaptive attacks

How far it's allowed to go

  1. How are you thinking about attacks that adapt to the person across steps and channels?
  2. How much autonomy do you think is right, and who decides?
What to listen forLimits the customer sets. Your team decides how far a simulation goes. The model doesn't.
The answers will tell you more about a two-year relationship than any feature matrix.
08 / Where measurement is going

Life after click rates

  1. Beyond clicks, what do you think a good signal of human risk looks like in a few years?
  2. What data would you want to use, and what would you decline to collect?
What to listen forBehavioral outcomes like reporting rates, time to report, and real incident data. Be wary of completion and click rates repackaged as a risk score.
10 / Their own AI

Turn the lens around

  1. How are you thinking about the risk your own AI features add to a customer?
  2. Which parts of your AI would you want us to scrutinize first?
What to listen forA vendor willing to point at its own weak spots. Follow up on what data trains or grounds their models and whether your data ever leaves your tenant.
11 / Working together

The first gig

  1. What would a good first engagement look like from your side?
  2. Who are the customers you'd want us to talk to?
What to listen forA scoped first step with a measurable outcome, and references that look like you in size and industry. Their biggest logo is rarely the most useful call.
Before the call

Know your own gaps before they pitch you theirs

Vendor answers only mean something against your own baseline. If you don't know where your program stands on strategy, engagement, assessment and training, every pitch sounds like the fix you need. The free SEAT maturity assessment takes about 15 minutes, needs no account, and tells you which gaps you're trying to close.