Quick answer
A vendor evaluation questionnaire is a short written list of questions you send before a paid trial or an annual commitment, covering data handling, billing mechanics, real usage limits, support, and exit terms. Send it in writing rather than asking on a call: written answers are quotable, the people who actually hold the answer can be included, and a vague reply is itself useful evidence. The point is to stop discovering the important terms after you have already signed.
Why writing beats a demo
A demo is run by the person who is best at running demos. The person who knows how long your documents are retained, what happens when you exceed a usage cap, or how much notice a cancellation needs is rarely in the room. A written list also makes two candidates comparable instead of two memorable sales conversations, and leaves a record you can point at if a term later turns out to be different from what you were told.
Section 1: data handling and security
- Is our content used to train your models, on which plan tiers, and can that be turned off per workspace?
- Where is our data stored and processed, and which regions can we choose?
- How long is data retained after we delete it, and what do backups retain?
- Do you support SSO and per-workspace role permissions, and on which tier do they start?
- Do you hold a current independent security certification, and can you share the report under NDA?
- Which subprocessors receive our data, and how are we told when that list changes?
If you are working through these questions for your own team, our guides on whether AI tools are safe for business data and writing a company AI usage policy cover the internal decisions that run alongside them.
Section 2: billing and contract mechanics
- What exactly is the unit we are billed on — seats, credits, tasks, minutes of audio, or tokens?
- What happens when we exceed the included amount: overage billing, throttling, or a hard stop?
- Which price are we protected against for the contract term, and how much notice do you give before a price change?
- Is the annual price paid up front, and what is the refund or credit position if we stop using it?
- What is the cancellation process and notice period, and does a downgrade take effect immediately or at renewal?
- Are there separate charges for API access, exports, or overage seats that sit outside the headline plan?
Pricing pages and credit rules change, so treat any figure a vendor quotes you as dated — check it against their official page, or against our dated pricing research and Pricing Watch log, before you commit to an annual plan.
Section 3: product limits at your real volume
- What are the hard limits on the tier we are considering — storage, history, export size, integrations, concurrency?
- Which features on the pricing page are gated behind a higher tier or a quote-only enterprise plan?
- How does the product behave at ten times our current volume — is there a documented rate limit, and what does hitting it do?
- What is the export format, and does leaving the platform require vendor involvement?
- Which integrations are officially supported rather than community-maintained?
The same questions apply to the tools we track individually — each review lists plan structure and links the vendor's official pages, so you can compare answers against published terms.
Section 4: support, reliability, and exit
- What support channels and response targets are included on our tier, and what is the escalation path?
- Do you publish a status page and a history of incidents, and what is your stated uptime commitment?
- If we cancel, how do we retrieve our data, and for how long is it recoverable?
- Are you offering any migration assistance, or is switching entirely on us?
Reading the answers: what a non-answer means
- A paragraph instead of a yes or no. Treat it as a no until you get one. Training-data answers in particular are frequently softened this way.
- "Contact us for enterprise pricing." Not a red flag on its own, but it means the tier you are reading about may not include what you need. Ask which specific limits change.
- Answers that only restate the marketing page. Ask once more, naming the exact page and the exact sentence you need clarified.
- Silence on a security question. Do not fill the gap yourself. If your workflow touches client or regulated data, an unanswered question is a reason to defer, not to proceed carefully.
Turning answers into a decision
Score the answers the way you score the product. Our free evaluation scorecard has a column for terms and privacy alongside workflow fit and cost, which is where questionnaire answers belong.
When a questionnaire is overkill
Skip it for a free tier on a personal project. It earns its place when client material, company data, multiple seats, or an annual prepayment are involved. For a single low-cost subscription you would cancel if it disappoints, read the privacy page instead and get on with the trial.
Frequently asked questions
Should I send the same questionnaire to every vendor?
Yes, and in the same order. Identical questions are what make two candidates comparable, and vendors answer a standard list faster than a bespoke one. Add role-specific extras at the end rather than rewriting the whole list.
What if the vendor refuses to answer in writing?
Ask for the answer in writing once more, and treat continued refusal as information about how the relationship will work after you buy. A vendor that will not put retention or cancellation terms in an email will not be easier to deal with at renewal.
Can I just read the public terms instead?
Read them, and use the questionnaire for what the public pages leave ambiguous for your specific case — your region, your tier, your data type. Public terms are the baseline; the questionnaire clarifies the parts that apply to you.