A demo takes twenty minutes. The decision to keep paying takes a year. Somewhere between the two, most teams stop asking questions and start entering card details, usually because the trial is about to expire and someone is tired of comparing tabs.
That is the moment this checklist is built for. Nothing below requires a technical background. It requires thirty minutes, a real example of your own work, and a willingness to be slightly annoying with a sales representative.
Start with the job, not the tool
Before you compare anything, write one sentence: We will use this to ______ for ______ people, ______ times a month. If you cannot fill in the blanks, you are evaluating a feeling rather than a tool.
Then note what you do today instead. Ten minutes of manual work per report sounds trivial until you multiply it by six colleagues and fifty weeks. That number is your budget, and it is the bar any subscription has to clear.
Finally, choose two or three deal-breakers in advance. Examples: no single sign-on, no bulk export, or inputs used for model training by default. Write them down before the demo, because almost everything looks acceptable during a demo.
Privacy: follow the data, not the landing page
Marketing pages describe intentions. Contracts describe obligations. Read the privacy policy and, if you are buying for a company, the data processing agreement. The useful questions are specific:
- Are our inputs used to train or improve models, and can that be switched off in writing?
- How long is data retained, and can we request deletion on demand?
- Which third parties process data on the vendor's behalf?
- Where is the data stored, and does that matter for your industry or region?
- Can administrators control who inside your company sees what?
Be extra careful with client records, employee information, health details, legal matters, or anything covered by a confidentiality agreement. If a tool touches those categories, speak with your legal or compliance advisor before pasting anything into a box. A general checklist is not a substitute for that conversation.
Accuracy: test it the way you would test a new hire
Vendor benchmarks show what a tool can do on curated problems. Your work is not a curated problem. Bring five real examples from last month, ones where you already know the correct answer, and run them yourself on the plan you would actually buy. Free tiers often have tighter limits or different capabilities, so testing free and buying paid can mislead you.
- One easy case, to confirm the basics work.
- One messy case: odd formatting, abbreviations, mixed languages, a long attachment.
- One ambiguous request that a competent colleague would ask you to clarify.
- One case where the correct answer is "there is not enough information here."
Pay attention to how wrong answers look. A tool that says it is unsure is more useful than one that produces confident nonsense with a tidy layout. If the output goes to customers, patients, or regulators, build a human review step into the workflow instead of trusting the first draft.
Pricing, limits, and the exit door
The price you will actually pay
Ask what happens when you hit the limit: does the tool stop, or does it keep working and bill you? Check whether the feature you need sits on the plan you are trialling. Add the costs that never appear on the pricing page — setup, migration, internal training, and the time someone spends administering seats.
Getting your work back out
Can you export everything you create, in bulk, in a format you can use, without emailing support? Test it with one project before you commit. If the only answer is screenshots and copy-paste, that is a decision, not an inconvenience.
Then read the exit terms: monthly versus annual billing, refund policy, notice period for cancellation, and whether pricing is locked for the term. Prefer monthly for the first period unless the annual discount is large enough to justify the risk.
Support and security: the questions nobody enjoys
How do you reach a human when something breaks at five o'clock on a Friday? Is support included or sold as an add-on? Is there a public status page? What response time is promised, and in writing?
On security, ask about single sign-on, two-factor authentication, role-based permissions, audit logs, and what happens to your data when you leave. If a vendor displays a compliance badge, request the report behind it rather than trusting the logo. Ask for two reference customers of roughly your size, and ask them one question: what broke, and how did the vendor handle it? Happy customers describe features. Honest ones describe incidents.
The 12 questions, in one place
- What specific task will this replace or improve, and how will we measure that?
- Will our inputs be used to train models, and can we turn that off in writing?
- How long is our data retained, and how do we delete it?
- Where is our data stored, and which third parties touch it?
- Which admin controls and permissions exist for our team?
- Can we test with our own real examples before paying?
- What does the tool do when it is unsure, and who reviews the output?
- What exactly triggers extra charges, and what happens at the limit?
- What is the total cost including setup, training, and add-ons?
- Can we export everything we create, in bulk, in a usable format?
- What is the cancellation and refund process, and what notice does it require?
- Who supports us, how quickly, and does our plan include it?
Run a two-week trial and decide on a date
Give one person ownership. Pick a single workflow. Run the same ten tasks you would handle in a normal week, and score the results on three things: time saved, corrections needed, and whether you would trust the output without checking twice.
Set the decision date before the trial ends, and put the cancellation deadline in a shared calendar. If the tool does not clear the bar you wrote down at the start, cancel it and move on. A subscription nobody remembers signing up for is the most expensive kind.
One final test, and it is the honest one: would you pay for this out of your own pocket for the next six months? If the answer is a shrug, you already have your answer.
Photo: ckstockphoto / Pixabay
