Blog

How to compare vendors after a sales demo

20 November 2026 · 6 min read

Which vendor actually does what we need, and did they say so in writing?

You have sat through three sales demos in two weeks. Each one went well. Each vendor showed a clean screen, a smooth workflow and a confident presenter. Now your team meets to decide, and the talk sounds like this: "I liked the second one." "The first one felt easier." "Didn't the third one say they could do that?"

That is the problem with demos. They are rehearsed, and each vendor chooses what to show. One spends twenty minutes on reports. Another skips reports and shows its phone app. So after three demos you are comparing impressions, not facts. This article shows a simple way to turn those impressions into answers you can compare.

Write down what you need before the demos

Do this first, ideally before the first demo is booked. If you wait until after, the demos will shape your list. You will add things you saw and liked, and forget things nobody showed you.

Keep the list short and concrete. Write each need as something the tool must do, not as a vague quality. "Sends an invoice reminder automatically after 14 days" is useful. "Easy to use" is not.

Then sort the list into two groups:

Be strict with the must-haves. If everything is a must-have, nothing is.

Send every vendor the same questions

Turn your list into questions and send the same list to every vendor. Use the same words for each one. If you ask one vendor "Can it sync with our accounting software?" and another "Does it have a two-way sync with our accounting software, including credit notes?", you will get answers that cannot be compared.

Sending the list before the demo also helps. A good vendor will build the demo around your questions instead of its usual script. If a vendor ignores your list and gives the standard demo anyway, that tells you something too.

Ask for written answers

A spoken "yes, we can do that" in a demo is easy to give and easy to forget. Ask each vendor to answer every question in writing, using one of four answers:

Ask for a short note with each answer: one or two sentences on how it works, or what is missing. The note is where the real information is. A "yes" with a note that says "using our add-on" is a different answer from a plain "yes".

Treat "planned" with care. Plans change, and dates slip. Unless the vendor will put a date in the contract, count "planned" as "no" for anything you need on day one.

Mark what you saw and what was only claimed

Right after each demo, go through your list while it is fresh. For each item, mark one of these:

This takes ten minutes and it changes the conversation later. When someone says "the third one could do that", you can check whether anyone actually saw it. Anything that is a must-have and only "claimed" should go back to the vendor as a follow-up: ask them to show it, or to confirm it in writing.

Compare the must-haves first

Now put the written answers side by side, one column per vendor, one row per question. Start with the must-haves only.

Any vendor that answers "no" to a must-have is out. Do not let a strong demo or a friendly salesperson talk you out of this. You wrote the must-haves before the demos for exactly this reason.

Only after this step should you look at the nice-to-haves. Use them to choose between the vendors that are left, not to rescue one that missed a must-have.

Ask "partly" answers what exactly is missing

"Partly" is the most common answer and the hardest to judge. It can mean "it does 90% of this" or "you could build it yourself with a lot of effort". For every "partly" on a must-have, send a short follow-up:

Then decide whether the gap is one you can live with. Write the decision down, so you do not argue about it again next week.

Check the price for your size and the right plan

The price in the demo is often the starting price. That plan may not include everything you need. Ask each vendor two direct questions:

  1. Which plan meets all of our must-haves?
  2. What will that plan cost per year for our number of users, including setup, training and any add-ons?

Ask also what happens to the price when you add more people, and what the price will be when the first contract ends. A low first-year price can hide a large increase in year two.

Compare these totals, not the prices on the website. A cheaper tool that needs its top plan to meet your must-haves may cost more than a dearer tool on its basic plan.

Involve the people who will use it

The people who choose a tool are often not the people who use it every day. A manager may love the reports, while the team that enters the data finds every screen slow.

Bring one or two daily users into the final demos, or ask for a trial they can use with real tasks. Ask them to try the three or four things they will do most often. Their notes belong in the comparison next to the vendors' answers.

Putting it together

When you finish, you should have one table. Every vendor has answered the same questions in writing. You can see which answers you saw working and which were only claimed. Vendors that missed a must-have are gone. Each "partly" has a note on what is missing. Each price is for your size and the plan you would actually buy.

That table is much easier to decide from than three people's memories of three different demos. It is also easier to defend later, when someone asks why you chose the tool you did.

NeutralPick lets you write the checklist once, send it to every vendor and see the written answers side by side, for free.

Write your questions once, send every vendor the same list, and compare the answers side by side.

Build a checklist