Ten questions to ask before you buy mission-critical publishing software

Choosing the system your publication runs on is not a features-and-price decision, even though features and price are what almost every comparison ends up measuring. Those two things are easy to put in a spreadsheet and poor at predicting whether the choice works out three years later.

This is the shorter, opinionated version. If you want the long form — criteria, demo questions, and what "good" looks like for a community publisher — read our guide on how to choose newspaper advertising software. We are obviously not a neutral party here, so weigh it accordingly; every point below is one you can put to any vendor, us included.

1. Treat it as mission-critical, because it is

Do not assume all software in a category does roughly the same thing. It does not.

• Evaluate it with the people who will actually live in it every day, not just the person signing.
• Do not get lost in small missing features. If a vendor is receptive to change, a small gap may be in the next release. A structural gap will never close.
• Be careful of scoring only on features and price — most of what determines success is in the rest of this list.

2. Ask for the upgrade history

Ask how often the product has genuinely improved, and get specifics.

Products quietly reach end of life when the vendor's attention moves to something newer. The new thing looks shiny; the mission-critical thing you actually bought stops keeping up with an industry that does not stop changing.

Watch the definition of "upgrade" too. Some vendors count bug fixes as upgrades and bill separately for anything that adds capability. Ask which of the last few releases added function, and which were repairs.

3. Look at what it is built on

Ask what language the product is written in and which databases it supports, then spend ten minutes searching the answers.

Periodically every vendor has to rewrite to keep up with platform and database changes. Tools that make an application fast to build are often not intended for software that will be sold and maintained for decades. The foundation determines whether the vendor can keep developing, or eventually has to start over and take you with them.

4. Take the user experience seriously

Your staff will spend most of their working day in this software.

Browser-only products can be easier for a vendor to deliver as a cloud service and more frustrating to work in. Clicking back and forth is a poor substitute for putting two invoices side by side. Check specifically whether multiple advertiser and order screens can be open at once — it sounds small and it is not.

5. Push hard on reporting

Reporting is a large part of why you are buying accounting and operational software at all.

• Invoices and statements are reports, and they go to your customers.
• Management decisions run on sales data and expected revenue.
• Every department needs to get at what is in the database without asking someone else.

You should be able to find when an advertiser dropped off, or list everyone expiring next month, in about two minutes. Also check that the product restricts not only which reports a user can open but which data appears on them. A rep needs their own advertisers and their own order history — not the whole book.

6. Understand what you are buying: ownership or access

The industry moved from buying software outright to renting it by subscription. Both models have real advantages.

Ask whether the vendor supports both, and — more usefully — whether you can move between them later. Wanting to subscribe for six months to see how the software performs before committing is a reasonable request.

Check the contract term as well. A three-to-five-year commitment is a long time to be wrong. Shorter terms limit the damage; longer terms may lock a price. It is fair to ask for a short commitment with a longer price guarantee.

On the pricing model itself, the question that matters operationally is whether you are charged for every name on the staff list. If you are, you will end up rationing access to the system that runs your business, and the people who need occasional visibility will not have it.

7. Evaluate the people, not just the product

The product is only as good as the training, the development team, and the service team behind it.

Ask where development sits. Communication between support, sales, training, and development is hard enough when everyone is in one building. Across languages and time zones it gets harder, and you feel it every time you report a defect.

Ask how training is delivered. Personalised sessions in small increments, remotely, tend to beat multi-day marathons. Producing the paper does not stop for a rollout, and frequent contact with a trainer while your team is actually using the system is worth more than a firehose in week one.

Ask what happens when someone picks up the phone. If a user cannot get help with a phone call — if the only route is a ticket and a callback days later — they will stop asking, and they will use a fraction of what you bought. Ask whether cloud support extends to the printer and browser problems that stop someone working, or stops at the edge of the application.

8. Cloud or on-premise — and can you change your mind?

Most software has moved to a hosted model where it runs on the vendor's servers.

The advantage is real: less of your IT budget goes to backups, upgrade installs, and server maintenance. The trade is that hosting is a permanent operating cost, usually tied to a subscription, and you are exposed to the vendor's pricing decisions and to how their servers perform under load.

The question worth asking is not "which is better" but "can I move between them later without changing products?"

9. Price is not cost

Think about how long you have run your current process. Unless you are brand new, it is probably a decade or more.

So compare vendors on total cost across the realistic life of the system, not the monthly figure. Then add the parts that never appear on the quote:

• Expected annual increases — ask for the history of the last few years.
• New modules the vendor has announced: included in your upgrade path, or billed separately?
• Whether phone support, new-employee training, and upgrades are in the service contract.
• The staff time to train and migrate, which for mission-critical software is substantial.

Choosing the cheapest option and discovering in month four that the vendor cannot meet your needs means doing the whole migration again, with a team that now has opinions about migrations.

10. Check references, then check more

You are effectively partnering with this vendor, so interview them the way you would a hire.

Ask for references, then ask for a few more — ideally including recent customers. Then ask those references:

• How long does a call back take? Can you call at all, or is it ticket-only?
• Have you requested a change? Did any of it ship?
• How did training and rollout go — did the vendor have your back?
• How often do upgrades arrive, and is training on new features charged?
• You reported a defect. What happened?
• What do you like, and what would you change?

Then take the criticisms to the vendor and watch the response. You might even check back with the reference a few days later to see whether the vendor reached out about it.

No product and no vendor is perfect; what one customer calls essential another calls clutter. What actually separates vendors is how they handle the gap — whether support is real, and whether anything changes in the software as a result.