How to Evaluate Software Before You Buy: A Vendor Question Checklist

I buy software almost as often as I build it, and I have made every mistake in the book: signed a year-long contract after a polished preview, imported my data into a tool that refused to give it back, picked a vendor whose support team logged off exactly when my own day started. Each mistake was avoidable. This post is the checklist I now run on every purchase — accounting tools, scheduling software, AI services, whatever. The whole process takes about an hour, and it has saved me far more than that in wasted money, lost data, and evenings spent fighting over a contract I should never have signed.

Start with the exit, not the entrance

The first thing to check in any software is not what it can do. It is whether you can leave. Ask: can I export all my data in a standard format — CSV, Excel, JSON, or a clean database file? Can I do it myself, or do I need to file a request? Do exports include attachments, history, and settings, or just the bare records? What does the vendor charge to help me leave, and how long does it take? A tool that holds your data hostage has you locked in, whether or not the contract says so. Test the export on day one, while you have nothing invested, so you know what leaving will look like later. The export test also reveals how the vendor thinks about you: a vendor who makes export a one-click feature is telling you they expect you to stay because you want to, not because you are trapped.

Test with your own real data

A software tool can look excellent in a guided tour and fall apart on your actual work. The numbers you will type in, the file formats you receive, the odd edge cases in your business — these are what matter. So test with your own real data, not with the sample files the vendor provided. Load your real spreadsheets, your real customer list, your real product catalogue. If the tool cannot handle the shape of your data, no amount of polish will save it. Most vendors offer a live trial precisely so you can do this; use it. If a vendor refuses to let you work with your own data before you pay, that is a serious reason to walk away.

Verify the support model and timezone

Support is where many software purchases quietly die. Ask who answers when you write: a human, a bot, or a shared inbox that nobody owns? What are the hours, and in which timezone? If your business runs in a different timezone than the vendor, a tool whose support closes at the start of your workday will leave you stranded at the exact moment you need it. Ask for the median response time, not the advertised target, and ask whether your plan includes a named person or an account manager. One client's overnight batch jobs failed, and the vendor's support only started at midday their time. Also check whether support is included in the plan you are buying or is an extra — some vendors gate live support behind a more expensive tier, and the difference matters on the day you actually need help.

Check the contract and exit terms

Read the contract as if a lawyer wrote it to catch you, because someone did. Look for automatic renewal periods that commit you to another year unless you cancel inside a narrow window. Look for minimum terms, early-termination fees, and clauses that let the vendor raise prices with little notice. Ask what happens if you outgrow the plan or need to shrink it: is there a penalty, a proration, or a credit? Ask who owns the data you put in the system — you, or the vendor — and what happens to that data if the vendor is acquired or shuts down. These questions are not aggressive; they are the normal cost of doing business, and a confident vendor will answer them in writing. If the vendor is reluctant to share the full contract before you pay, that is a red flag in itself; you should be able to read the entire agreement before any money moves.

Security and privacy

Every tool now sits in the middle of your business, so security is not an IT problem, it is a buying criterion. Ask where your data is stored, in which regions, and whether you can choose. Ask how data is encrypted in transit and at rest, who has access, and how the vendor proves it. Ask about certifications and audits, and ask the vendor to name the person accountable for security. On privacy, the key question is simple: what data does the tool collect about your customers and staff, and what is it used for? If the answer involves advertising or selling data, that tool does not belong in your business. Read the privacy policy yourself, because the marketing page will not tell you.

How it handles real workloads

Ask the vendor how the software behaves under the load you actually produce. Will it handle your busiest day, not your average day? What happens when a thousand customers check out at once, or a hundred people file expenses on the same Friday afternoon? Ask for a written performance statement, and ask what the documented limits are for the plan you are buying. Then test it yourself with a realistic workload — the busiest hour of last month, replayed in the trial. A tool that slows down at exactly the moment your customers need it will cost you more than its subscription price. Do not accept "it will be fine" as an answer. Ask for the numbers, then verify them.

The vendor question checklist

| Area | Questions to ask | |---|---| | Data export | Can I export everything myself, in open formats, at any time? | | Real data | Can I load my own data into a live trial and test my busiest workflow? | | Support | Who answers, what hours, in which timezone, and how fast? | | Contract | What are the renewal, cancellation, and price-change terms? | | Data ownership | Who owns my data, and what happens to it if the vendor shuts down? | | Security | Where is my data stored, how is it protected, and who can see it? | | Workload | What happens under my busiest day, and what are the hard limits? | | Privacy | What data is collected about my customers and staff, and why? |

Red flags and green flags

Red flags: a vendor who cannot put a pricing or contract answer in writing, who charges for exporting your own data, whose support has no humans, or who changes the subject when you ask about leaving. Green flags: a vendor who gives you a guided tour, then offers a live trial, then lets you test with your own data, then answers the exit questions first. The good ones are not afraid of the questions on this list. The weak ones will show themselves quickly when you ask them.

A note from someone who builds software

I write this from both sides. I founded Synthixx Technologies, and we build software ourselves, so I know how much work goes into export, support, and honest contracts. That is exactly why I ask vendors the same questions I answer in our own work. And when I need a quick utility, I use free tools like the ones at tools.synthixx.com — but the buying rules above apply to every single tool, free or paid, including ones I build. If a free tool cannot export your work, do not build your life inside it.

Frequently asked questions

How long should an evaluation take? A focused afternoon is usually enough if the vendor gives you a live trial and answers questions in writing. If the vendor drags the process across weeks, treat that as a signal.

Is it okay to ask about data export before I sign? It should be the first thing you ask. A vendor who hesitates on export is telling you how hard leaving will be.

What if the free trial does not allow my real data? Ask for an exception. If the vendor refuses, evaluate on sample data that looks like your real work, and get the export test done on whatever you can.

Do I really need to read the whole privacy policy? At minimum, read the sections on data collection, sharing, and retention. Those three sections tell you more about the product than the features page.

How do I handle a vendor who will not answer in writing? Politely note that you need the answer documented for your records. A vendor who refuses to document the deal will not honour it later. One vendor promised one thing on a call and a different thing in the contract; we only caught it because we asked for it in writing.