Most software buying starts with a demo. A salesperson shows the parts of the product that look good, and the call follows their script. At the end, you have seen a lot of features and still don't know if the product does the few things you need.
A short checklist, written before you talk to any vendor, fixes this. It doesn't need to be long or perfect. It needs to say, in plain words, what the product must do for you. Then every vendor answers the same questions, and you decide what the demo is about. Here is how to write one in about 15 minutes.
Why write it before the first call
Once you have seen a demo, your list starts to change. You add features you didn't know existed, and you lose sight of the problem you started with. A list written first is an honest record of what you need. It also makes vendors easier to compare, because they all answer your questions instead of telling their own story.
The steps
- List the jobs the product must do. Use your own words, not the words on vendor websites. Write down the work, not the feature. "Send an invoice the same day the job is finished" is a job. "Smart invoicing" is a sales phrase. Aim for five to ten jobs. If you get stuck, think about what goes wrong today and what takes too long.
- Turn each job into a yes/no question. A good question has an answer you can check. A vague question gets a vague answer, and every vendor will say yes. Compare these:
- Weak: "Is it easy to use?"
- Strong: "Can a new staff member create and send an invoice without training?"
- Weak: "Does it handle payments?"
- Strong: "Can a customer pay an invoice by card from a link in the email?"
- Sort each question into must have, nice to have or optional. Must have means you would not buy a product without it. Nice to have means it saves real time or trouble. Optional means it would be pleasant but changes little. Keep the must-haves few, usually three to six. If everything is a must-have, nothing is, and no vendor will pass.
- Add the questions people forget. These rarely come up in a demo, and they often matter most a year later:
- Can we export all our data, in a standard format, if we leave?
- Who owns the data we put in, and what happens to it after we cancel?
- What is the full yearly price for a business of our size, including add-ons?
- How long is the contract, and can we cancel early?
- What are your support hours, and how do we reach a person?
- Does it connect to the tools we already use, without a paid add-on?
- Set a budget range. Write down the lowest and highest yearly amount you would pay. A range is more useful than a single number. It lets you remove vendors that are clearly out of reach before anyone books a call, and it stops a long demo from slowly raising your limit.
- Cut anything you wouldn't drop a vendor over. Read each must-have and ask: if a vendor said no to this, would we stop talking to them? If the honest answer is no, move it down to nice to have. Then read the whole list once more and delete anything nobody would miss. A short list gets clear answers. A long one gets skimmed.
- Share it with the people who will use it. The person who buys the tool is often not the person who uses it every day. Send the list to them and ask one question: what is missing? They will spot the job you forgot, and they are more likely to use a tool they helped choose.
An example: an invoicing tool for a small business
Here is a short checklist for a small business with a few staff that wants to stop sending invoices from a spreadsheet. It took about ten minutes to write.
Must have
- Can a new staff member create and send an invoice without training?
- Can a customer pay by card or bank transfer from a link in the invoice?
- Does it send a reminder automatically when an invoice is overdue?
- Can we export all our invoices and customer records at any time, in a standard file format?
Nice to have
- Does it connect to the accounting software we already use, so nobody types an invoice twice?
- Can we see which invoices are unpaid, and for how long, on one screen?
Optional
- Can we send invoices in a second language or currency?
Budget: a yearly range for three users, agreed before any calls. Plus the forgotten questions above: data ownership, contract length, support hours and the full price at our size.
Notice what is not on the list. There is nothing about dashboards, artificial intelligence or a long list of templates. Those may be pleasant, but this business would not drop a vendor over them.
What to do with the answers
Send the same list to every vendor you are considering and ask for written answers. When the answers come back, look at the must-haves first. A vendor that says no to one of them is out. A vendor that says "partly" needs one follow-up question: what exactly is missing?
Then book demos only with the vendors that answered well. In each demo, ask them to show you what they claimed in writing, using a small sample of your own data. The demo now follows your list, not their script.
Watch for vague answers. "It integrates with everything" or "setup is simple" usually means the honest answer is "only partly". Ask the question again in a narrower form, and ask for the answer in writing.
You can write this list on paper or in a document. If you would rather not, NeutralPick can draft it with you and store it for free, then send every vendor the same questions.