Before You Sign That SaaS Contract, Ask These Seven Questions

Every procurement process has a moment where the balance of power quietly shifts. It happens somewhere between the second demo and the proposal review, when the vendor's polish starts doing the thinking for your evaluation team. The deck is beautiful. The references are 'available upon request.' The ROI slide has a chart with an arrow pointing up and to the right.

Seasoned buyers know this moment well — and they know that the questions a vendor answers reluctantly are the ones that matter most. Below are seven of them, along with how to read the response.

1. 'Which customers with our profile can I call directly?'

A strong answer names two or three companies similar to yours in size and industry, offers a reference contact, and doesn't flinch. A dodge sounds like 'our client base is highly confidential' or produces a logo slide of Fortune 500 household names when you run a 400-person distribution company in Ohio. Logos without context are marketing, not evidence. If no comparable customer will talk to you, assume you would be their first.

2. 'Show me exactly how you calculated that ROI figure.'

Every modern vendor deck includes projected savings or revenue lift. The question is what sits underneath it. A good answer walks through the assumptions line by line — headcount reduction percentages, adoption rates, time horizons — and invites you to adjust them. A dodge recites the number louder. Beware any projection that assumes 100% user adoption in month one; no software in history has achieved it.

3. 'What does this cost in year three, including support, integrations, and price increases?'

The sticker price is the entry fee, not the bill. Strong vendors disclose their standard annual uplift (often 5–8%), implementation fees, premium support tiers, and the cost of the API calls or seats you will inevitably need. Dodges include 'pricing is customized to each client' without a range, or deferring everything to 'the implementation scoping phase.' Custom pricing with no anchor is a signal that the number depends more on your perceived budget than on their costs.

4. 'Who exactly will be on my account after the signature?'

The team that sold you and the team that serves you are usually different people. A good answer introduces your actual delivery lead by name, describes their caseload, and explains escalation paths. A dodge keeps rotating the executive sponsor through the conversation and promises a 'dedicated success manager' without specifying experience or capacity. Ask to meet your post-sale team before you sign. Hesitation here predicts a support experience of portal tickets and form emails.

5. 'What happens to my data if we part ways?'

Contract terms around data portability, deletion timelines, and export formats reveal how a vendor expects the relationship to end — which tells you how they view it overall. Strong answers include a defined export process in standard formats, a contractual deletion window, and no hostage-style fees for retrieving your own information. Vague answers ('we'll work with you on an exit plan') mean the exit plan will be negotiated when you have zero leverage.

6. 'Where does your product roadmap come from, and what got cut last quarter?'

This question tests honesty twice. First, on process: good vendors can describe how customer input shapes priorities. Second, on candor: every roadmap involves trade-offs, and a vendor who cannot name a single thing they deprioritized is either hiding something or not actually building anything. The answer also tells you whether a feature your team needs is six months out or six years.

7. 'What would you tell us not to use your product for?'

The best question in the list. A confident vendor will name the use cases where competitors or spreadsheets are the better fit, because they know their product's boundaries. A dodge — 'we're really flexible, it works for everything' — should end the conversation. Tools that claim to do everything tend to do nothing particularly well, and vendors who cannot admit a limitation will not flag problems during implementation either.

A Shorter List, A Better Contract

None of these questions is adversarial, and strong vendors welcome them — the best ones will answer several before you ask. The point is not to interrogate your potential partner into submission. It is to find out, before the signature rather than after, whether you are buying a solution or a subscription to someone else's optimism.

Decisive buyers ask early, document the answers, and make the vendor's own words part of the contract's appendices. The vendors worth having will not mind at all.