Questions to Ask a Software Vendor
For anyone evaluating a software product before signing: an operations lead, an IT manager, or a business owner replacing a system that no longer fits. These questions cover what the product actually does today, what the contract really costs over three years, and how hard it would be to leave.
The questions
Open any question for the note
Which of the features you've shown me are live today, and which are on the roadmap?
Why ask it
Demos routinely blend shipped functionality with prototypes and planned work, and roadmap items slip or get cancelled. Ask for the distinction in writing, and treat anything not yet released as absent when you compare vendors.
Can you show me the workflow that matters most to us, using our data?
Why ask it
Scripted demos avoid the awkward paths, so watching your own messy process run through the product is where the gaps appear. A refusal to attempt it usually means the fit is worse than the pitch implied.
What do customers like us typically struggle with in this product?
Why ask it
Every product has a known weak area, and a vendor who names theirs and explains the workaround is more trustworthy than one who claims none. Sales engineers are often franker on this than account executives.
Who is a customer at our size and in our industry that I can call?
Why ask it
References from much larger organisations tell you nothing about the support and onboarding you would receive. Ask for one who has been live for at least a year, since the honeymoon period hides most problems.
What is the total cost for three years, including everything that isn't in the licence fee?
Why ask it
Implementation, training, premium support, integrations, sandbox environments and per-transaction fees regularly add more than the subscription. Ask for a single three year figure and make them itemise it.
How does the price change as we add users, records or volume?
Why ask it
Pricing tiers create sudden jumps, and per-seat models get expensive at exactly the point where you can no longer work without the tool. Ask what the cost looks like at double your current size.
What are the renewal terms, and how much has your list price risen in the past three years?
Why ask it
Automatic renewal with an uncapped uplift is common and is where the real cost accumulates. Negotiating a cap now is far easier than arguing about it at renewal.
What does implementation involve, and how much of it is our work?
Why ask it
Vendors quote their own hours and leave out your staff's time for data cleanup, configuration decisions and testing, which is often the larger share. Ask how long a customer like you took from signature to genuinely live.
Who does the implementation, you or a third party partner?
Why ask it
Reseller and partner-led implementations vary widely in quality, and the vendor may take no responsibility if it goes badly. Find out who you would escalate to when it does.
How does this integrate with the systems we already run?
Why ask it
Ask whether the integration is native, built on an API, or dependent on a middleware tool you would also have to buy. Established integrations that are used by many customers behave very differently from ones a vendor offers to build for you.
Can we get our data out in a usable form, on demand?
Why ask it
Export that produces a partial CSV without relationships or attachments is not a real exit route. Ask whether full export is self-service, whether it costs anything, and how long you keep access after cancelling.
What happens to our data if we leave or if you go out of business?
Why ask it
Retention periods, deletion guarantees and any source code escrow arrangement should be explicit in the contract. This also prompts a useful conversation about how long the company has been funded for.
What uptime do you commit to, and what happens when you miss it?
Why ask it
A published availability figure without a remedy is marketing rather than a commitment, and service credits are usually small. Ask for the actual uptime over the past twelve months and where it is publicly reported.
How do you handle security, and can I see your most recent audit or report?
Why ask it
Ask for the current SOC 2 report, penetration test summary or equivalent rather than a page of badges. Also ask where data is physically stored, which matters for privacy obligations.
Have you had a breach or serious outage, and how did you communicate it?
Why ask it
Incidents happen to everyone, and how a vendor notified customers is the part you can evaluate. Evasion here is a reasonable ground to walk away.
What support is included, what does it upgrade to, and what are the real response times?
Why ask it
Base support is often email only during one time zone's business hours, with anything faster sold separately. Ask what the median first response time was last quarter, not the target.
How do updates reach us, and can we defer them?
Why ask it
Forced updates can break your integrations and your training material with little notice. Ask how much warning you get and whether there is a sandbox to test in first.
What administration will this need from us once it's running?
Why ask it
Many products quietly require a part-time internal owner for permissions, configuration and reporting, and that cost never appears in the quote. Ask what the customer reference you were given does about this.
Which contract terms are you able to change?
Why ask it
Liability caps, notice periods, price protection and data terms are frequently negotiable while the standard order form implies they are not. Asking directly tells you how much room exists before you spend legal time.
Can we run a paid pilot with a real team before committing?
Why ask it
A short pilot with actual users surfaces problems no evaluation matrix will, and willingness to offer one signals confidence in the product. If the answer is no, ask what the exit terms are in the first ninety days instead.
Evaluating a Software Vendor
Practical guidance for the conversation itself
Prepare Before the Demo
Write Down the Three Things It Must Do
A short list of must-haves stops a polished demo from redefining your requirements for you. Everything else is a preference, and preferences should not drive a three year commitment.
Bring Real Data and a Real Task
Ask the vendor to walk through the specific process that is painful today, using a sample of your own records. This is the fastest way to find the workaround you would live with daily.
Include the People Who Will Use It
Software chosen only by managers gets quietly abandoned by the team expected to use it. Put two eventual users in the demo and let them ask their own questions.
Compare Total Three Year Cost, Not Monthly Price
Build one table per vendor covering licence, implementation, training, integrations, support tier and internal staff time. Differences in monthly price often reverse entirely at the three year line.
Sequences That Work
Testing the Fit
- 1Which features are live today versus on the roadmap?
- 2Can you run our workflow with our data?
- 3What do customers like us struggle with?
- 4Who at our size can I call?
Testing the Commercials
- 1What is the three year total, itemised?
- 2How does the price change as we grow?
- 3What are the renewal terms and price uplift history?
- 4Which contract terms can you change?
Testing the Exit
- 1Can we export everything, on demand, without a fee?
- 2What happens to our data after cancellation?
- 3What notice do we have to give, and when?
Common Pitfalls
Buying the Roadmap
Committing on the basis of features due next quarter leaves you paying for something that may never ship. Score vendors only on what you could use next week.
Letting the Evaluation Run Out of Time
End-of-quarter discounts are designed to compress your diligence, and the discount is usually still available afterwards. If a price expires in forty eight hours, that is information about the vendor.
Ignoring the Cost of Leaving
Data that cannot be exported cleanly turns every renewal into a foregone conclusion. Establish the exit route before you migrate anything in.
Skipping the Reference Call
Fifteen minutes with an existing customer regularly changes a decision, particularly on support quality and implementation reality. Ask them what they wish they had known.
Forgetting Who Will Administer It
A product with no internal owner drifts into misconfiguration and stale permissions within a year. Name the person before you sign.