Start looking for almost anything you need to buy and the information arrives from every side. Vendor websites, pricing pages, brochures, sales calls, demos, follow-up emails, review sites and advice from people you know. Within a week you have heard a lot and can prove very little.
The problem is not only the amount. Each vendor describes its product in its own words, in its own order, with its own names for the same things. One calls it a plan, another calls it a tier, a third calls it an edition. One lists a feature as included, another lists it under a heading you have never seen. Nothing lines up, so you cannot put two vendors next to each other and see the difference.
Most of what you hear is spoken
A lot of the important detail never reaches paper. It comes up on a call or in a demo. A salesperson says yes, that works. Someone on your team asks about a feature and hears, we can do that. A price is mentioned as a rough figure. Then the call ends.
Spoken promises cost you in three ways.
- People forget. A week and four calls later, nobody is sure which vendor said what. Notes from a demo are short and written in a hurry.
- People hear different things. Two people on the same call can leave with two different answers. One heard "yes", the other heard "yes, on the top plan".
- The detail arrives after you sign. This is the expensive one. You start using the product and find that the feature you were shown is an add-on, or works only up to a limit, or is still being built. The person who said yes may have meant "yes, with conditions", and the conditions were never said out loud.
Once you have paid, you have little leverage. You are left scrambling to work out what you actually bought, and there is nothing in writing to point to.
A demo shows, it does not commit
Demos are useful. You see the product move, and you get a feel for how it works. But a demo is run by the vendor, on their data, along a path they chose. It shows you what they want you to see.
When a feature comes up in a demo, three different things can be true. It may be fully there today, on the plan you would buy. It may be there in part, or only on a higher plan. Or it may be planned for later. A demo rarely makes the difference clear, and a quick "yes, we have that" covers all three.
So treat a demo as a way to see the product, not as the answer to your questions. The answers belong in writing.
The fix: the same questions, answered in writing
The way out of the noise is simple. Decide what you need, write it as a list of questions, and send the same list to every vendor. Ask them to answer each question in writing.
For each question, ask for more than yes or no. A useful written answer has four parts.
- A clear status. Yes, partly, planned or no. "Partly" and "planned" are honest answers, and they are much better than a vague yes.
- How much. If there is a limit, what is it? How many users, records, locations or hours?
- Which plan. Is it included on the plan you would buy, or only on a higher one, or as an add-on?
- Their own note. A short line in the vendor's words about how it works or what is missing. This is where a good vendor explains, and where a weak answer shows.
Then ask for one more thing: the price for your size. Give every vendor the same number of users and the same needs, and ask what they would charge for the plan that covers your list. A price for a team of your size is worth more than any figure on a pricing page.
When every vendor answers the same questions in the same form, the information stops being a pile. It becomes a table. Each row is one of your questions. Each column is one vendor. Now you can compare like with like, apples to apples.
How to read an apples-to-apples table
A table full of answers can still be read badly. Work through it in this order.
Start with your must-haves. Look only at the questions you marked as essential. Any vendor that answers "no" to one of them is out, however good the rest looks. Any vendor that answers "planned" to a must-have is a risk. Ask when, and ask them to say it in writing. If the date is vague, treat it as a no for now.
This step usually shortens the list a lot, and it is the step most people skip when they are comparing from memory.
Then look at the partial answers. "Partly" needs a closer look. Read the vendor's note. Is the missing part something you would never use, or is it the part you care about most? Does "partly" mean a limit you would reach in six months? If the note is unclear, ask a follow-up question and get the reply in writing too.
Two vendors can both answer "partly" and mean very different things. The note is where you find out which.
Then compare the price for what you need. Only now look at price, and look at the price for the plan that covers your must-haves, at your size. Not the cheapest headline price on the website. A low price on a plan that leaves out what you need is not a saving. You will either upgrade or work around the gap.
Value for money is what you get against what you pay. A vendor that answers yes to all your must-haves at a fair price is often better value than a cheaper one with three partial answers. The table lets you see that, because both answers and prices sit in the same place.
Keep the written answers after you buy
Once you choose, do not throw the table away. Save the answers from the vendor you picked, with the date. They are a record of what you were told when you made the decision.
If something turns out to be an add-on after all, or a limit is lower than you were told, you have the vendor's own words to point to. That makes the conversation shorter and fairer for both sides. It also helps at renewal, when you can check whether the planned features ever arrived.
NeutralPick does this for free: you write the checklist, every vendor answers the same questions in writing with their price, and you see the answers side by side, with no vendor paying to be shown or ranked.
There will always be a lot of information when you buy something. You cannot stop it arriving. But you can decide which part of it counts, and the part that counts is what each vendor was willing to put in writing.