Nobody phones a software company to say thank you for a quiet month. The login worked, the reports ran, Tuesday’s update changed nothing anyone noticed and the month-end run finished before lunch. That’s the best month business software can have, and it gets no credit at all.
New features get the attention
Software companies love launches. Marketing wants something to announce, sales wants something new to demo, and product teams would rather build than fix. So the release notes fill up with features, and the work that makes software dependable slides down the list.
You encourage it as a customer. You compare vendors on feature lists because features are easy to see in a demo. Nobody demos a system that stayed up on the last working day of the quarter.
Reliability is what you’re paying for
Think about what it costs when business software lets you down. A payroll run that fails on the 25th. An invoicing system that’s down the morning a big client wants a statement. A report that shows different numbers after an update, with no explanation, so the team loses a day working out whether the software or the data is wrong.
None of those moments involve a missing feature, and every one of them costs more than a new feature would have been worth. For software that runs a core part of your business, dependability is the product. Everything else is a bonus.
Every outage changes how people work
The cost doesn’t end when the system comes back. Once software has let them down a couple of times, people start protecting themselves. They export everything to a spreadsheet before month end, in case. They check the numbers by hand. They keep the old process running on the side. Each habit makes sense on its own, and together they undo most of what you signed up for.
Predictable beats exciting
Good software changes in ways you can plan for. Updates arrive on a known rhythm, with notes that say in plain language what’s different and who it affects. Changes to how something is calculated are announced before they happen, with a reason. Nothing moves in the week your team is busiest.
When a vendor gets this right, your team stops bracing for updates. They trust that what worked yesterday works today, and they spend their attention on their own work instead of the software.
Boring takes a lot of work
Software that never surprises you is hard to build. It needs testing that covers the unglamorous cases, monitoring that spots problems before customers do and a team disciplined enough to hold a release back when it isn’t ready, and to tell you a feature is late instead of shipping it half done. It needs people who care as much about the bug that affects twelve customers as the feature that impresses a hundred prospects.
You won’t see any of that in a demo. You’ll feel it at month end.
How to check before you sign up
Ask vendors how often they release updates and how they tell customers about them. Ask what happened the last time something broke, how long it took to fix and what they changed afterwards. A vendor that answers openly has thought about it. One that claims it never happens hasn’t been straight with you.
Ask to see their release notes for the last few months. You’re looking for clear, dull, regular entries. A long list of exciting launches and hardly any fixes tells you where the effort goes.
And ask an existing customer the simplest question of all. When did the software last let you down?
Built for the day that counts
At Commspace, the day that counts is month end, when practices need their numbers right and on time. That’s the day we build for. See how at www.commspace.co.za.
