Questions to Ask During Vendor Selection
Questions to ask prospective vendors, written for whoever runs the comparison: a buyer, an operations lead or an owner choosing between two or three firms for the same piece of work. The first eight suit a first call with each one, and the rest follow the order a vendor selection usually takes, through delivery, price, risk, proof and the contract. Put the same questions to every vendor on the shortlist, so the answers can be scored side by side.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
First call
Can you show us two projects like ours, including one that went badly?
Why ask it
Every vendor has a polished case study ready. Asking for the difficult one tests candour, and how they describe a project that went wrong tells you how they will describe yours if it does.
Will your own staff do this work, or will any of it go to subcontractors?
Why ask it
Subcontracting is not a problem in itself, but it changes who you can hold to a deadline and whose insurance covers a mistake. Find out which parts go outside the firm, and whether you would be told before a subcontractor is swapped.
Who is our day-to-day contact, and what happens when they are away?
Why ask it
Ask for the named cover, not the concept of cover. An account that rests on one person goes quiet the week that person is on holiday, which tends to be the week you need a decision.
What is your timeline from signed contract to live, and what has to happen on our side?
Why ask it
The second half is the half that slips. Get the list of what they need from you, with a date and an owner on your side for each item, because a vendor's timeline quietly assumes your people are free.
What does the quoted price include, and what will be billed separately?
Why ask it
Ask specifically about setup, data migration, training, integrations, support tiers and out-of-hours work. The gap between the quote and the first year's invoices lives in exactly these lines.
How much of your business is work like this, and how long have you been doing it?
Why ask it
A firm that does this every week has templates, trained staff and a few scars. If it is a new line for them, you are paying for their learning, which can still be a fair deal at a lower price and with tighter checkpoints.
What would make you turn down this project?
Why ask it
A vendor with real criteria will name something: a timeline that cannot work, a scope outside their competence. One who would take any work at all is telling you how they will handle a bad fit.
What do you need to know about us before you can give a firm proposal?
Why ask it
A prospective vendor who quotes without asking anything is pricing a guess, and the guess gets corrected after you sign. The questions that come back also show how closely they read the brief.
Delivery
Will the people we met in the pitch still be on the account after we sign?
Why ask it
Senior people often win the work and pass it to a team you have never met. Meet the delivery lead before you decide, and have the names written into the proposal.
How many clients does the team assigned to us support?
Why ask it
The pitch gets a team's full attention; the contract gets whatever is left after their other accounts. Put the question about the named people and not the firm's average, and find out what share of their week yours would take.
How long have the people on our team been with you, and what happens to our account when one of them leaves?
Why ask it
Tenure is a fair guide to how often you would be explaining your business again to a new face. On the leaving half, listen for shared notes on your setup, a second person who already knows the account, and warning before the handover instead of after it.
How much capacity do you have right now, and when could you realistically start?
Why ask it
A start that depends on another client's project finishing is a start that can move. If they would need to hire to take you on, find out who does the work until the hire arrives.
What happens in the first thirty days after we sign?
Why ask it
Anyone who has done this before can describe the kickoff, the first deliverable and the first review without stopping to think. A hazy first month usually means the plan will be written once the contract is safe.
Where do projects like this usually stall on the client side?
Why ask it
The best answer is specific, sign-off delays, missing data, an unavailable subject expert, and it doubles as a warning list for you. Vendors who say projects never stall have not run many.
How would this fit with the systems and routines we already use, and who does the connecting work?
Why ask it
Fit is where a vendor who looks right on paper turns difficult in practice. Name the two or three things it has to work with, such as your accounts package, your booking system or your warehouse routine, and have the proposal say whose staff do the joining up and whose budget it comes from.
How do you define done for each stage, and who on our side signs it off?
Why ask it
Arguments over whether something was delivered begin where acceptance was never written down. Agree the test for each stage before work starts, and name one person on your side with the authority to say yes.
How will we know the work is on track between milestones?
Why ask it
Settle the rhythm now: a weekly note, a shared tracker, a monthly review with numbers in it. Request a real status report from another account with the names removed, since its format shows whether bad news gets reported or buried.
How quickly do you commit to responding and to fixing a problem, and what do we get when you miss that?
Why ask it
A service level with no consequence is a statement of intent. Ask what was actually paid or credited to a client in the last year, which separates a real remedy from a clause.
If something goes wrong, who do we escalate to, and how senior are they?
Why ask it
Get a name and a phone number above your account manager before you ever need them. An escalation route that ends at the person who caused the problem is no route at all.
What does support look like after go-live, and is it the same team?
Why ask it
Handover from implementation to support is where knowledge about your setup gets lost. Ask what is documented at handover and who you will be speaking to a year from now.
What training and documentation do we get, and who owns it afterwards?
Why ask it
Training that exists only as a session your staff attended once disappears with the first resignation. Written material you can keep and update is worth negotiating for explicitly.
Price
Is this a fixed price, a rate for time, or a mix, and which parts are estimates?
Why ask it
Two quotes with the same total can carry very different risk. Under a fixed price the vendor absorbs an overrun and under time and materials you do, so label every line with its kind before you compare totals.
Which assumptions is this quote built on?
Why ask it
Volumes, working hours, the state of your records, how fast you approve things: every quote leans on a few of these. Have them listed in the proposal, because each one is a future conversation about extra cost.
How do you price a change request, and who has to approve it?
Why ask it
A day rate with no approval step is how a fixed budget doubles. Ask to see the change control process rather than being told one exists.
How will the price change in the second and third year?
Why ask it
The first-year figure is the one built to win the comparison. Get the increase mechanism in writing, whether that is a fixed percentage, an index or simply the vendor's discretion, and find out if there is a ceiling.
What are your payment terms, and can any payment wait until a milestone we can check?
Why ask it
Money paid up front is leverage handed over. Tying part of each invoice to a deliverable you can test keeps both sides interested in the same date.
What do we pay if we end up needing less than we committed to?
Why ask it
Minimum volumes and committed spend are easy to agree in an optimistic month. Work out the bill if your demand fell by a third, then see whether the commitment can be reviewed part-way through the term.
If we need far more than we planned, how quickly can you scale up, and at what rate?
Why ask it
Growth is when a buyer has least room to shop around, so the rate for extra volume is better fixed now than quoted later. Speed counts as well: more capacity might take them days, or a hiring round.
When a client ends up paying more than the quote in the first year, what is the extra usually for?
Why ask it
This invites the vendor to name the overruns they see most, and many will name one or two. Add those lines to every vendor's column in your comparison sheet, not only theirs.
When does this quote expire, and what changes if we decide after that date?
Why ask it
Some deadlines are real, such as a team that will be assigned elsewhere. A discount that vanishes on Friday is more often a sales tactic, and asking what specifically changes after the date tells you which kind you are looking at.
Is there room to move on price, and what would you want in exchange?
Why ask it
Vendors will often trade price for something that costs you little: a longer term, faster payment, a case study, a flexible start date. Decide which of those you would give before the conversation starts.
Risk
Where is our data stored, who can access it, and which other companies handle it?
Why ask it
Ask for locations, subprocessors and the deletion timeline in writing, and treat vague reassurance as a reason to slow the process down. Privacy rules differ by country and by sector, so pass the answer to whoever handles data protection for you and ask how it applies where you operate.
What certifications, licences and insurance do you hold, and can we see the certificates?
Why ask it
The documents matter more than the logos on the website, because certifications lapse. Check the expiry date and the scope, since a certification can cover one product line and not yours.
Have you had a security incident or a serious service failure, and how did you tell your clients?
Why ask it
A long-lived vendor with no incidents at all is rare, so the telling part is the second half. How fast clients heard, from whom, and what changed afterwards is roughly how you would be treated.
How do you vet the staff and subcontractors who would have access to our systems or premises?
Why ask it
You are extending your own access controls to people you will never interview. Three things matter: what is checked, how access is removed when someone leaves, and whether subcontractors are held to the same standard. What screening is allowed varies by country, so ask how it works in theirs.
What is your plan if one of your own key suppliers or systems fails?
Why ask it
Their dependencies become yours the day you sign. A concrete answer names the dependency and the fallback, while a general statement about resilience has probably never been tested.
Who owns the company, and how is the business funded?
Why ask it
Fair to ask of any supplier you will depend on. A recent acquisition or heavy outside investment can bring price rises, product changes and staff departures during your contract, so ask what the owners expect over your term.
What can you show us about your financial health?
Why ask it
A vendor that fails mid-contract leaves you with half a project and nobody to call. Audited accounts, a credit report or a bank reference are all reasonable requests for a contract that matters, and a private company may share them under a confidentiality agreement.
How much of your revenue comes from your largest client?
Why ask it
If one account pays most of the bills, that client's demands come first and its departure could shrink the team serving you. A rough share is enough, since you are looking for dependence and not exact figures.
Do you work with any of our competitors, and how do you keep our information separate?
Why ask it
Working across an industry is how a vendor gets good at it, so the answer need not be no. What you want described is the separation: different teams, restricted files, and what their people may carry from one account to the next.
Is there any dispute, claim or investigation involving your company that could affect this work?
Why ask it
Ask it plainly and keep a record of the reply. If something they chose not to mention comes to light later, the silence will tell you more than the dispute itself would have.
Proof
Can we speak to three clients, including one who has left you?
Why ask it
Curated references say what you would expect. The former client is the informative call, and a vendor who cannot produce one is either very new or filtering hard.
Which clients have left in the past year, and why?
Why ask it
Some churn is normal and being able to describe it honestly is a good sign. Answers that blame every departure on the client's own failings describe a pattern rather than a coincidence.
Who is your longest-standing client, and what has kept them with you?
Why ask it
Long relationships show whether a vendor is still good once the sales effort ends. Listen for whether the reason given is the work itself or simply that switching would be painful.
What do your clients most often complain about?
Why ask it
Every supplier has a known weakness, whether that is slow reporting, documentation or a thin support desk. Naming it is a sign they hear feedback; denying it means you will find out yourself.
What have you changed in the way you work because a client pushed back?
Why ask it
This checks whether a complaint travels any further than the account manager. Press for the detail: what the client said, what was altered, and whether every other account got the change too.
Who do you most often lose bids to, and why?
Why ask it
Vendors know exactly who beats them and on what, be it price, speed or range. An honest answer hands you another name for the shortlist and a clear view of where this one is weakest.
Would we be one of your larger clients, one of your smaller ones, or about typical?
Why ask it
Small accounts at a big vendor can wait behind the large ones, and a large account at a small vendor can swamp it. Check the answer with a reference of similar size, who knows how it feels from that seat.
Can we see the work itself, through a site visit, a sample or a live account, before we decide?
Why ask it
Slides show the best version of everything. An hour watching the real service run, or handling an actual sample, answers questions nobody would think to raise in a meeting room.
Would you agree to a paid pilot or a trial period before the full contract?
Why ask it
A small paid piece of real work tests what a proposal cannot: how they communicate, how they take a surprise, whether their dates hold. Fix in advance what a pass looks like and what you owe if you stop there.
Contract
Can we see your standard contract now, before we choose?
Why ask it
Terms that arrive after the decision arrive after your leverage has gone. Reading each prospective vendor's paper during selection also lets the contract count in the scoring, where a harsh one should cost points.
What are the contract term, notice period and renewal terms?
Why ask it
A one-year term that renews automatically unless you give ninety days notice can become a second year you never chose. Put the notice deadline in a calendar the day you sign.
Which clauses do clients usually push back on, and where have you given ground before?
Why ask it
Most standard terms are an opening position, and the vendor knows which ones move. Hearing what others negotiated stops you accepting a clause as fixed when it rarely is.
Will you write what you have told us in these meetings into the contract?
Why ask it
Many contracts say that only the written document counts, which can leave a promise made aloud during the sale with nothing behind it. Keep a running list of those promises and ask for it as a schedule; hesitation over a particular item marks the promise least likely to be kept.
Who will own what you create for us, and what do you keep the right to reuse?
Why ask it
Designs, code, reports and templates made on your budget do not automatically belong to you. It depends on the contract and on the law where you are, so settle it before work starts and have a lawyer read that clause.
If your mistake costs us money, what are you liable for, and where is the cap?
Why ask it
A cap set at a few months of fees may sit far below what a failure would cost you. How these clauses work depends on the law governing the contract, so have a lawyer set the cap beside your realistic worst case.
What counts as grounds for us to end the contract early, and what would it cost us to walk away?
Why ask it
Look for two ways out: one for when they fail to perform, and one for when your needs simply change. The second usually carries a fee, and learning the figure now beats discovering it in the middle of a dispute.
If we disagree about an invoice or a deliverable, what happens before it becomes a legal dispute?
Why ask it
Most disagreements are small and ought to be settled by two named people within days. Find out whether you may hold back a disputed amount while paying the rest, which varies by contract and by country.
How would we get our data out if we terminated?
Why ask it
Ask what format, how long it takes, and what it costs. An export that arrives as a locked report rather than usable records is how a supplier stays after you have decided to leave.
If we replace you, what handover do you commit to, and for how long?
Why ask it
The end of a contract is when cooperation is least in a vendor's interest. A handover period, a list of what gets passed on and a rate for the extra work are far easier to agree while they are still trying to win you.
Running a vendor comparison
Practical guidance for the conversation itself
Which questions belong to which stage
First call with a prospective vendor
The eight First call questions fit one short conversation and are enough to cut a long list down to three or four names. Send them ahead where you can: a vendor who turns up with answers has shown you how they prepare.
Proposal and presentation
Delivery and Price belong here, once every vendor has the same written brief. Ask for the answers inside the proposal and not only aloud, so that the document you score is the one that later sits behind the contract.
Checks on the shortlist
Risk and Proof are for the two or three vendors still standing. Certificates, accounts and reference calls take real effort on both sides, and spending that effort on a long list uses up the goodwill you will want later.
Before anyone signs
No Contract question should be left for signature day. Request each vendor's paper during selection and give whoever reviews your contracts time to read it, since what can be enforced depends on where you and the vendor are based.
Set criteria before you talk to anyone
Separate must-haves from preferences
Write the non-negotiables down first, in one page. Doing this after the demos means the criteria get shaped by whichever vendor presented most confidently.
Weight the criteria and score in isolation
Decide how much each criterion counts before the first meeting, then score each vendor as you finish with them and not in one sitting at the end. Scores settled all at once tend to lean towards whoever was seen last.
Ask every vendor the same questions
The same questions in the same order turn a set of impressions into a comparison, because a gap in one vendor's answer shows up against the other two. It also exposes who has not prepared.
Include the people who will use it
The team that will live with the service notices things a buyer does not. Give them a session without the vendor present to say what they think.
Cost beyond the quoted price
- Implementation, configuration and data migration
- Training for the first cohort and for later joiners
- Integration work on your side, including your own staff time
- Support tier, out-of-hours cover and named contacts
- Charges that grow with headcount, volume or usage
- Annual uplift clauses and how they are capped
- Exit costs: data extraction, parallel running, replacement
Doing reference calls properly
Ask for a comparable client
Similar size, similar problem. A glowing reference from an organisation ten times your size tells you about their enterprise team, not the team you will get.
Ask what surprised them
More productive than asking whether they are satisfied. The answer is usually about timelines, an unexpected cost, or how much of the work fell to them.
Ask whether they would buy again today
It forces a verdict where general praise does not. Hesitation before a yes is worth following up on.
Listen for the lukewarm reference
A reference willing to take the call but reluctant to say much is giving you an answer. Ask directly what they would do differently.
Reasons to slow down
- A discount that expires at the end of the week
- A proposal with no named team, dates or deliverables
- Every question answered yes, including the ones that should trade off against each other
- Reluctance to name subcontractors or where data is held
- No former client they are willing to let you speak to
- Answers that change between the demo and the written proposal
- Contract terms sent only at signature, with legal review discouraged
Piloting before you commit
Define what a pass looks like first
Two or three measurable outcomes, agreed in writing with the vendor. A pilot without criteria tends to be decided on how pleasant the vendor was to deal with.
Keep the scope small and real
One workflow, one team, real data if you safely can. Sandbox pilots with clean sample data hide exactly the problems a pilot exists to find.
Agree what happens if it fails
Who owns any configuration work, whether fees are refunded, and how the data is returned or deleted. Settling this at the start makes stopping a normal outcome rather than a dispute.