How to choose the right software for your business

When your business feels messy, it is very tempting to go looking for a new tool. A better project management system, a smarter CRM or a platform that promises to bring everything together beautifully, preferably by lunchtime.

I understand the appeal. At times I have been guilty of the shiny new tool acquisition. The free trial, the tempting deal, the possibility that this might finally be the thing that makes everything easier. Ideally without creating another login we’ve forgotten three weeks later.

Sometimes, new software really does help. But it’s worth looking at what’s become difficult before deciding what to buy.

Perhaps information lives in too many places, follow-ups depend on memory or nobody is entirely sure which document to use. The process might still be in someone’s head, where it has been accumulating space for quite some time.

A new system can give all of that somewhere to go. Working out how it should fit together still needs a bit of thought.

1. Work out what you need to make easier

“I need a CRM” might actually mean “I keep losing track of follow-ups after good conversations”. I’ve worked with some great clients who have run a very successful CRM just using Google sheets, but with the right information held and designed to keep it up to date really easily.

“I need to sort Google Drive” might mean “We don’t have an agreed way of organising our files”. Operating in OneDrive, GoogleDrive and Client-Shared Drives, we know how challenging it can be to store and locate documents. Everyone has a different approach and without a plan, it becomes chaos, fast.

Those are useful starting points because they describe something you can improve and then check.

This is an approach I bring across from learning and development: establish what needs to change, then work backwards. Before choosing a platform, describe what someone should be able to do, find or complete more easily.

As a VA I receive lots of invites from software providers and app builders promising me great software for my clients. Sometimes it lives up to the pitch, sometimes it doesn’t get a viewing. But whenever I’m reviewing a tool, it has to meet my requirements and the way I need to work, not the other way around.

For example: “After a client conversation, I want to record the next step, give it a date and see it alongside my other commitments.” That gives you something specific to test when the software demonstration begins.

2. Be honest about how you actually work

One of the easiest mistakes to make is choosing software for an imaginary version of yourself.

The version who updates every field, reviews every dashboard and maintains the system every Friday afternoon with a herbal tea and a clear mind.

Lovely idea. Likely not real life.

Think about the circumstances in which you’ll use it. You might be adding a note on your phone between appointments, sharing information with someone who dislikes new systems or picking up a task after several days away from it.

Does it need to be mobile? work offline? shared with colleagues? shared with your VA?

How many subscriptions and users do you really want?

A useful setup needs to accommodate those moments. If entering one follow-up requires twelve fields and a small administrative ceremony, there’s a fair chance it won’t happen.

Ask anyone else who needs to use the system what would make it workable for them too. They may spot something you would otherwise discover after paying for the year.

Plot spoiler, I get to do this a lot.

Whether it’s a client’s internal app, an external knowledge bank or website that I’m helping a client build or just systems that we need to use together, I’ve put a lot of systems through their paces over the years. Sometimes it’s actually the billable work I’m doing for the client, sometimes it’s just part of building our relationship together. Either way, get your team, better half, or just an overly excitable VA who loves her tech involved, and really test out if it’s going to bring the return you want and need.

3. Check what you already have

Before taking on another subscription, look at the tools you’re already paying for. Now this is such an obvious one, but we all get caught up in the new shiny tools that’s got great marketing and can do ‘the thing’ without realising you’ve got the solution already in your IT arsenal. It just snuck in when you weren’t looking, or you didn’t know it did that, or even worse, you forgot.

There will also be times when an existing tool has reached its limit. Perhaps permissions are too restrictive, reporting takes too much manual work or important information keeps getting separated. I’ve had well-documented experiences with CRMs….and website tools over the years!

Businesses change. People change. What is possible has changed. It’s when you get to the point and too many limitations push you to upgrade, or start the search for your new technical bestie that you become focused on finding a replacement.

Write down that limitation. It helps distinguish a genuine requirement from a feature that looks appealing in a demonstration.

And include the practical costs in your comparison: setting it up, moving information, learning how to use it and maintaining it afterwards. The monthly subscription is only part of the commitment. Are there additional future costs that haven’t quite advertised themselves yet?

4. Test it with a real piece of work

Tutorials tend to involve tidy examples. Your business probably has a few more complications. This is where you really get to try and break the system. Ideally not literally, but it’s been known.

This is the fun bit, when you get to play. To really test out if the grass really is greener, and what it says on the marketing actually delivers.

During a trial, take one ordinary task through the whole process. Add an enquiry, record the next action, attach the relevant information and find it again later. If someone else will use the system, include them in the test.

Notice where you hesitate, repeat yourself or need to keep information somewhere else.

Can you tell what needs doing next? Is it easy to update? Can you find the detail without remembering exactly what you called it?

Use sample information where appropriate, particularly while you’re still checking whether the service is suitable for client data.

A small, realistic trial will tell you more than an afternoon spent making the dashboard look lovely and applying the branding. Although I appreciate the temptation.

And the bits it can’t do. Are they on the road map? Does the system even have a road map? Because just because the functionality you need is not there today, if it’s being released next month, quarter, or even next year, that’s significant. So ask. I do and not just because I’m nosy, but because it gives me a really good feel for how they work with users and the general set up of the brain behind the system.

5. Think about what happens when it’s unavailable

This is less exciting than exploring the features, but it deserves a place in the decision.

If you couldn’t open the system tomorrow, what would stop? Could you contact the people expecting something from you, find the information needed for urgent work or use an agreed alternative?

At Jessanol, we run both Google and Microsoft set ups. Financially desirable? No. Practical? Absolutely. Having another way to work is a deliberate choice. It also enables us to fully support all of our clients, regardless of which way they’ve set up their technical environment.

That doesn’t mean everything automatically transfers between them, or that two subscriptions amount to a backup plan. The useful part is understanding what each option allows us to do and what information we would need available.

When assessing software, check how you can export your information and whether the exported files are actually usable. Consider who controls the account and how an authorised person would regain access if the usual account holder were unavailable.

You don’t need to duplicate every system. You do need to understand where you’re relying on one.

6. Keep the setup small enough to maintain

New software makes it very easy to create every possible category, status, tag, folder and automation.

It feels organised at first. Then real work arrives, and maintaining the system becomes another job.

Begin with the information and actions you genuinely need. You can add detail when there’s a clear reason for it.

Borrow ideas from other people’s setups, but allow for the differences in your work. Their projects, clients and enthusiasm for colour-coded dashboards may be quite different from yours.

Agree a few everyday habits too: where new actions go, who updates progress and when you review anything outstanding. Software becomes useful through those ordinary actions, repeated often enough that you can trust what it tells you.

Here at Jessanol HQ we undertake performance reviews on both humans and systems alike. Every Friday afternoon, as part of a weekly round-up, we run through what could we do better and what do we do well. Left unchecked, I could disappear down all sorts of rabbit holes exploring functionality and fiddling with setups. Keeping things manageable takes a little restraint.

We recently chose to scale back our CRMgiving up a huge amount of functionality in the process. The previous system came at a not insignificant cost. But it wasn’t working. It felt awkward and whilst offering lots of – ‘it does everything vibes’, for us it wasn’t deep enough. In anything. So we bought a new CRM. A small but perfectly formed one. The bits it doesn’t do, we use other software for. Specialist software that really knows it’s stuff. It also makes me feel less reliant on one platform. And that’s a good thing.

A simple way to compare your options

Before committing, make a short note of:

  • The problem you need to solve.
  • The essential tasks the software must support.
  • Who will use it and in what circumstances.
  • The full cost, including setup and ongoing upkeep.
  • How you will retrieve your information or work around an interruption.
  • What a successful trial would look like.

Keep that beside you while comparing options. It’s surprisingly easy to forget why you started looking once someone shows you a clever feature.

Choose one part of your business that feels harder than it should. Finish this sentence:

“I need a reliable way to __________, so that __________.”

For example: “I need a reliable way to record client follow-ups, so that I can see what I’ve promised and when it needs doing.”

Then check whether your existing tools could support that with a little adjustment. If they can’t, you have a much clearer brief for finding something that will.

Need help making your systems easier to work with?

If your business information is spread across emails, spreadsheets and half-used applications, Jessanol can help work through what needs to happen and put a practical structure around it.

That might involve organising what you already have, setting up a clearer way to track work or documenting the steps so someone else can follow them.

You don’t need to arrive with the process neatly mapped out. Showing me what happens now, and where it gets frustrating, is a useful place to start.

Get in touch if you’d like help making it easier to work with. I do enjoy a useful bit of software. Especially when it earns its keep.

Enjoyed the articles? Get fresh insights delivered monthly.

Practical tips, tools and ideas for SMEs — delivered straight to your inbox, once a month. No overwhelm, no jargon, just useful.

Check out our newsletter archive here.

By subscribing you agree to receive monthly emails from Jessanol. No spam, ever. You can unsubscribe at any time. Your data is handled in accordance with our Privacy Policy.

Scroll to Top