Field note
The questions to ask before buying an AI tool
Most AI tool regret traces back to one skipped step: nobody tested it on real work before the invoice arrived.
Before buying any AI tool, ask what specific problem it solves that a process fix could not, what happens to your data if you cancel, whether it fits the systems you already use, and whether you can trial it on real work, not a demo. Skip any of these four and a subscription becomes shelfware.
Name the problem
Not the tool, the task it fixes
Check the data terms
Training use, exports, cancellation
Test on real work
Not a vendor demo
Assign an owner
Someone who reports back on a set date
Is this actually a technology problem, or a process one wearing an AI label?
Before evaluating any specific tool, name the problem in one sentence without mentioning software. If the honest sentence is "nobody owns following up on stalled invoices" or "our onboarding steps live in three people's heads", that is a process gap, not a shortage of AI. A tool will make an undefined process faster at being undefined. Only buy once you can say exactly which repeatable task the tool needs to shorten or take off someone's plate.
What happens to your data, and to what the tool produces?
Ask three specific things before signing: does the vendor train its models on your inputs by default, can you turn that off, and what do you get back if you cancel next year. A vendor with a plain answer to all three has usually built the answer into their terms already. One that answers with marketing language about "enterprise-grade security" and nothing concrete about your specific data is telling you the answer is not written down yet.
Does it fit the tools your team already has open, or does it become one more tab nobody visits?
An AI tool that requires people to leave their email, their CRM, or their project board to go use it loses the adoption race to whatever is already open on their screen. That is a measured pattern, not a guess: Microsoft's 2024 Work Trend Index found that at small and mid-sized companies specifically, 80 percent of AI users are bringing their own unsanctioned tools to work rather than the one the business chose, usually because the sanctioned option did not fit where the work actually happens. Ask a vendor to show the integration with the specific system your team lives in, not a generic list of supported apps.
Can you test it against a real piece of your own work, and who owns that test?
Insist on running the tool against an actual client email, an actual spreadsheet, an actual support ticket, not a sales demo built on the vendor's cleanest example. A vendor that resists a short trial on real work is a signal worth taking seriously. Name one person inside the business who owns the trial and put a date on their calendar to report back on whether it earned a place on the invoice. A trial with no owner and no date quietly becomes a subscription nobody remembers agreeing to.
At small and mid-sized companies specifically, the share of AI users bringing their own unsanctioned tools to work is higher than average, which is usually a sign the sanctioned tool does not fit how people actually work.
The takeaway
Before you sign anything, write down in one sentence the problem this tool needs to solve, get a straight answer on what happens to your data if you cancel, and name the one person who will test it on real work and report back by a set date. If any of the three is missing, you are not ready to buy yet.
