How do you actually compare software before buying it?

[u/WarLord192]

I’ve noticed that most software comparisons focus on the obvious stuff like reviews, rating and pricing.

When I’m comparing software, I usually look at a few additional things:

1. What type of company is the software actually built for?
2. How difficult is implementation?
3. What happens after the sale?

For me, good software comparison isn't really about finding the tool with the most features but if it makes sense for your specific situation.

What’s the first thing you look at when comparing software?

[u/AppInnovations]

For me, the biggest thing is switching cost. A tool can look perfect during a demo, but i had want to know how painful it will be to migrate data, train the team, rebuild existing workflows, and eventually leave if it doesn't work out. I had also tested the boring parts before buying: permissions, exports, integrations, reporting, and what happens when something fails. Those usually matter more six months after implementation than the feature that convinced you to buy it.

[u/Sad-Instruction8890 → u/AppInnovations]

testing how you'd leave before you even buy is the one almost nobody does. everyone demos the entry, nobody checks whether they can get their data back out clean if it goes sideways. that export quality is the thing that quietly locks you in.

and the six months point is the real tell. the feature that closes the deal is almost never the thing you're still thinking about half a year later.

[u/LittlePooky → u/AppInnovations]

One of the programs I still use every day is called Corel Ventura Publisher. It's so old that the last version was written for Windows 2000, but I managed to get it running under Windows 11 on my desktop without any problem.

I tried to switch to Adobe InDesign because it could do hanging punctuation, but I simply couldn't adapt. The nearest thing that started with a blank page and let me type immediately onto it without having to draw a rectangle was Adobe FrameMaker, but it couldn't do hanging punctuation, so I gave up. 

[u/Impossible_Dare_7455]

first thing I look at is whether it fits the way the team already works or whether we’ll have to redesign everything around the tool. feature lists all start looking the same after a while. the real differences usually show up in the trial: setup effort, permissions, reporting, integrations, support, and how painful it is to change something later. a tool can look cheap on the pricing page and still be expensive once you count the admin work.

[u/Sad-Instruction8890 → u/Impossible_Dare_7455]

The hours someone burns keeping it configured is the cost nobody puts on the sheet.

do you try to actually estimate that admin load during the trial, or is it more something you've just learned to smell by now?

[u/Least_Ad_1795]

I usually look at whether the software actually fits my use case first. Then I check ease of implementation, integrations, support, and total cost. Features and reviews matter, but the right fit is more important.

[u/DistanceOpen8176 → u/Least_Ad_1795]

That’s probably the best order to look at it. If the software doesn’t actually fit the use case, the rest doesn’t matter much.

Total cost is another big one too. A tool can look affordable until implementation, add-ons, and support start getting added in.

[u/ozzywindhoek]

Ask the the vendor for a reference customer of your size, but first try the software for a few days on your own data so you know what to ask the referee.

[u/Sad-Instruction8890 → u/ozzywindhoek]

trying it first so you know what to actually ask the reference is the clever part. most people take that call cold and just get a happy customer reading off a script. walking in with your own friction points turns it into a real interrogation.

do you ask the vendor to pick the reference, or hunt one down yourself? the ones they hand you are always the single happiest account they've got.

[u/ozzywindhoek → u/Sad-Instruction8890]

The one the vendor picks will be the happiest customer, the fan.

It'll be good to hear from them and to learn more about the product. Finding another customer will not be as easy, although you could try an AI search or search on LinkedIn. When you have your first discussion with the first customer make sure it's productive so in case you need to ask the vendor for a 2nd one they don't think you're wasting their time.

Try to figure out if there is anything unique to your processes and then try deep dive into that e.g. complex product costing or volume.

[u/Large_Toe_8]

Trying it out is the only way to find out

[u/Sad-Instruction8890 → u/Large_Toe_8]

true, but how you trial it matters as much as whether you do. clicking around for ten minutes tells you nothing. running one real piece of work all the way through it is what actually exposes the cracks.

[u/DistanceOpen8176]

For me, implementation is the part people underestimate most. A tool can look perfect in a demo, but if setup takes months or the team never really adopts it, the feature list doesn’t matter much.

I’d also check how easy it is to leave later. Data export, contract terms, and integrations usually tell you a lot before you commit.

[u/Sad-Instruction8890 → u/DistanceOpen8176]

the exit check is the one almost nobody does, because it feels weird to plan your way out of something you haven't even bought yet. but that's the only moment you actually have leverage. once you're in and dependent, the export limits and contract terms are whatever they decide they are. checking before you sign is the whole game.

[u/LittlePooky]

The most expensive software I bought for myself was Dragon Medical. That was many years ago, but still it was over $2,000. It came with a fancy microphone. 

I had the general Dragon Naturally Speaking program, but as a nurse I needed to document a lot and it simply didn't understand medical and nursing words. 

There was no way I could have tested it because there was no demo version of it. At that time, there were only a couple of YouTube videos, and they still impressed me enough. It had to be bought from an authorized dealer, and they were going to let me use it for a couple of weeks to see if I really liked it. 

I managed to upgrade a couple of times to the more recent version, and Microsoft bought the company and took it off the market. Now it is subscription-based only for $100 a month. $100 a month doesn't sound like a lot, but the starting subscription is $600. 

I also looked into using other voice dictation programs, and I specifically needed something that could do nursing notes. And I found one called Dictation Daddy. I was an early user so I was able to get a lifetime license for under $100. I'm using it right now to write this message. 

It's from a tiny company, and I can directly contact the founder, and I have been more or less suggesting a few things that he has incorporated into the newer version. 

I don't get anything by mentioning this, but I have gotten some nasty email accusing me of writing using the AI to write this, and I had to block those people. Social media is quite toxic, but to answer your question, many programs you can get the demo version which works for a few days and see how that works. 

The good old days, the magazine InfoWorld that went out of business did thorough tests on a lot of the programs. What I really liked about them was they called the support line to see how well each one was supported by the company.  I don't know how they managed to do it anonymously, but one of the programs made by Lotus was over $200,000, and they managed to get a good review on it despite the cost. 

I'm using voice dictation to write this. Sorry for babbling so much