The Essential Guide: Three Questions to Ask Any Software Salesperson

Every good demo looks the same: a clean dashboard, a confident presenter, a feature list that answers every problem you mentioned. The right questions to ask software vendor reps cut through that in minutes, because a demo is built to show you the best case — it is not built to show you what happens on a bad day, six months after you've signed.

Questions to ask software vendor reps: why the pitch isn't the point

A sales conversation is designed to build confidence quickly. That's not dishonest — it's the job. But confidence built on a polished demo tells you almost nothing about contract terms, data ownership, or what support looks like once the sale is closed. The questions below are deliberately about the parts of the relationship a demo never covers.

Ask them early, ask them plainly, and watch how the answer is delivered as much as what it says. A straight answer, even an imperfect one, tells you more than a smooth deflection.

None of the three questions below are complicated, and none require any technical knowledge to ask. What they require is asking them before you're emotionally committed to the sale — which, in practice, means earlier than feels natural.

Question one: what actually happens if I want to leave?

This is the single most revealing question you can ask, and one of the most useful software salesperson questions in any evaluation. Ask about contract length, notice period, and whether your own data comes with you in a usable format if you switch. Vendor lock-in is rarely announced upfront — it's usually discovered the day you try to leave and realise your data is trapped in a proprietary export nobody can read.

A vendor confident in their product will answer this without flinching, because they're not relying on the contract to keep you. One who gets vague, or pivots straight back to features, is telling you something important.

Question two: where does my data actually live?

Ask which country your data is stored in, whether it's backed up, and who besides the vendor can access it. This matters for ordinary software contract terms reasons and for UK data protection law reasons — you remain responsible for your customers' data even when a third party is processing it on your behalf.

Good vendors answer this readily, usually pointing to a specific data centre region and a documented backup policy. If the answer is "don't worry about it," worry about it.

Question three: who do I actually call when it breaks?

Ask what support looks like at 8pm on a Friday, not during the sales process when everyone is responsive. Is there a named UK team, or a ticket queue that disappears into a time zone you've never heard of? This single question predicts more about your day-to-day experience than every feature on the demo screen.

Comparing how vendors answer these three questions

The pattern is consistent across most software categories, not just ours — how a vendor handles these three questions predicts the relationship better than any feature comparison.

Question	Good sign	Warning sign
What if I want to leave?	Clear notice period, data export included	Vague answer, redirected to features
Where does my data live?	Named region, documented backups	"Don't worry about it"
Who do I call when it breaks?	Named team, real hours stated	"Our support is excellent" with no detail

Prepare evidence, access questions and an exit scenario

A few minutes of homework changes the whole conversation. Look the company up on the Companies House register — how long has it actually been trading, and does the registered address match what's on their website? Search for existing customers, not just testimonials chosen by the vendor. Check whether the NCSC's supply chain security guidance flags anything relevant if the software will touch sensitive business data.

None of this takes long, and it means you walk into the sales conversation already knowing which of the three questions to press hardest on.

Why these answers change the whole procurement decision

These questions apply whether you're evaluating a business platform, a till system, a self-service kiosk, an AI assistant, or a new website build. The specifics change; the underlying test — will this vendor still look good to deal with a year from now — does not.

It's also worth asking whether the vendor sells one narrow product or a genuinely connected set of tools. A business running separate systems for its till, its payments and its customer messaging has three separate versions of these three questions to answer, not one — which is its own argument for consolidating where it genuinely makes sense to.

What switching software actually costs

Cost isn't only the new subscription. Factor in staff retraining, data migration, and the overlap period where you're paying for both systems. A vendor who can talk you through this honestly, rather than glossing over it, is one worth taking seriously.

Where payments are involved — a till, a booking system that takes deposits, or a card payment setup of any kind — the same FCA guidance on payment service providers and PCI Security Standards Council rules apply regardless of which vendor you choose — they're not a reason to pick one over another, but worth knowing before you sign anything that touches card data.

Ask specifically whether migration support is included in the price or billed separately. A vendor who quotes a low headline fee but charges heavily for the actual switch-over is answering question one — what happens if I want to leave, or in this case arrive — less honestly than the pitch suggested.

The reassuring answers that are not evidence

Most bad software decisions trace back to skipping one of the three questions to ask software vendor reps, not to picking the "wrong" product outright.

• Judging the product entirely on the demo, which is built to show the best case, not a normal Tuesday.
• Not asking about contract length until after you've mentally committed to the purchase.
• Assuming "cloud-based" automatically means your data is portable if you leave.
• Skipping a quick company check because the salesperson was likeable.
• Signing before getting the answers to these three questions in writing.

Signs a vendor is dodging the real questions

Not every vendor will refuse outright — most of these questions to ask software vendor reps get a partial, practised non-answer instead. Watch for these patterns.

• Every question about contracts gets redirected back to a feature or a discount.
• "Nobody's ever asked that before" is offered as if it settles the matter.
• The person on the call can't say who handles support once the deal closes.
• Reference customers turn out to be hand-picked case studies rather than businesses you can actually contact.
• Data location and export format are described as "not something to worry about."

Protecting your business data during evaluation

Be careful what you hand over during a trial or demo — don't upload live customer data or card information until contract terms are actually agreed. The NCSC's small organisations guide is a useful checklist for account and access security during any evaluation period, trial or otherwise.

Questions to ask software vendor reps, by business type

Sole traders and small teams

Focus hardest on question one — contract length and exit terms — since a long tie-in matters more when you don't have a procurement team to manage it. Review your own position as a self-employed buyer before signing anything multi-year, and don't be talked into a longer term than the business genuinely needs just because it comes with a discount.

Multi-site or growing businesses

Ask specifically how the platform handles multiple locations or teams — a tool built for one site often breaks down, not gracefully, once a second site is added. Get a straight answer on per-location pricing too, since some vendors quote an attractive single-site rate and only reveal the real multi-site cost once you're already committed.

Regulated or data-sensitive sectors

Push harder on question two. Where the software touches health, financial or otherwise sensitive records, get the data-location and access answer in writing, not just verbally on the call. A vendor operating in a regulated sector should be used to this level of scrutiny and shouldn't treat it as an unusual request.

Planning your vendor evaluation

Turning questions to ask software vendor reps into a repeatable process takes a short, deliberate sequence rather than winging it call to call.

1. Write the three questions down before the call, so you don't forget them mid-pitch.
2. Do a quick Companies House and customer-review check beforehand.
3. Ask for written confirmation of contract length, data location and support hours.
4. Compare at least two vendors using the same three questions, not just the one you liked first.

Under the general consumer protection rights that apply to UK sales, a vague verbal promise is far harder to rely on than something confirmed in writing — ask for it in writing every time.

Ask for proof, not just promises

Any vendor worth signing with should be able to point you to real customers, not just a marketing page. Read a few of our own published case studies and you'll see exactly the kind of detail this article is asking you to demand elsewhere — named businesses, specific outcomes, nothing dressed up. If a vendor can't offer the equivalent, ask why.

If you'd rather put these three questions to us directly, get in touch with our UK team — we'd rather answer them before you sign than after.

What a usable answer looks like in writing

Reread your notes from the call a day later, away from the sales pressure. If any of the three answers still feels vague or contradictory, that's worth a follow-up call before you sign anything. The Citizens Advice guidance on resolving a purchase gone wrong is a useful reference for what recourse actually looks like if a vendor's promises don't hold up later.

Ask for the exit route in writing before you are impressed by the demo

A supplier can give a confident answer about data, support or cancellation and still leave the practical details vague. Ask for the answer in the proposal or agreement: what information can be exported, in what format, what happens to incoming enquiries during a handover, and who remains responsible until the change is complete. A good answer describes a process, not a reassurance.

Use a real scenario: it is Friday afternoon, a member of staff cannot access a customer record, and the person who sold the system is unavailable. Who can they contact, what information will support need, and what does the business do while it waits? The NCSC guidance for small organisations is a sensible independent reference for the questions around access and recovery.

Before signing, write your three answers beside the business problem you want solved. If a supplier cannot explain ownership, exit and support in plain language, pause. Our own consultation process should be judged by the same standard.

Key takeaways

• The three questions to ask software vendor reps are: what happens if I leave, where does my data live, and who do I call when it breaks?
• A vendor's tone answering these three questions predicts the relationship better than any demo.
• A few minutes of company research before the call changes the whole conversation.
• There's no single "best" vendor — only the one that answers these questions to ask software vendor reps honestly for your business.
• Get contract length, data location and support hours confirmed in writing.

Frequently asked questions about questions to ask software vendor reps

Should I ask these questions on the first call?

Yes — asking early saves time on both sides and shows the vendor you're a serious buyer, not a browser. There's no polite way to save questions to ask software vendor reps for later; the earlier they're on the table, the less time you waste on a vendor that isn't right.

What if the salesperson can't answer technical questions like data location?

That's fine, as long as they can get you a written answer promptly from someone who can. A flat refusal to find out — rather than an honest "let me check" — is the real warning sign in any of the questions to ask software vendor reps.

Is a longer contract always a bad sign?

Not necessarily — some genuinely need it to price fairly, particularly where hardware is involved. What matters is that the length and exit terms are disclosed clearly upfront, not buried in a document you're only sent after agreeing verbally.

How many vendors should I actually compare?

At least two or three, using the same three questions each time, so you're comparing answers rather than just first impressions — that consistency is what actually makes the comparison fair.