How to choose between custom and ready-made management software

It depends on how standard your way of working is and how much it sets you apart from your competitors. If you work the way most businesses in your sector do, a well-chosen off-the-shelf tool is usually enough and gets you started right away. If your process is the reason clients choose you, or no tool on the market can follow it without awkward workarounds, custom software starts to make sense. Quite often, though, the right answer sits in between, because you can keep what works and build only the piece that’s missing.

The starting point is data scattered across too many places

Plenty of small and mid-sized businesses don’t have a real management system. They have a collection of tools that grew over time, such as a calendar, a few Excel sheets, WhatsApp groups and the invoicing software, plus maybe a CRM that nobody uses fully. A CRM, if the term is new to you, is the software that keeps your contacts and the history of every client.

Each tool does its job on its own, but together they don’t talk to each other. The same information gets typed in two or three times, and someone updates it in one place but not the other. Finding out how the month is going means cross-checking everything by hand. When someone goes on holiday or changes jobs, part of what the business knows leaves with them.

That cost never shows up on an invoice, but it is made of hours spent copying, searching and fixing, plus mistakes that reach your clients.

The three options in plain words

Off-the-shelf software (SaaS)

SaaS stands for software as a service, meaning a product you use in the browser or in an app for a subscription, almost always per user per month. The upsides are obvious. You can start within days, the vendor takes care of updates and security, and plenty of other customers have already put the tool through its paces.

The flip side is that you have to adapt to the tool. The features are what they are, customisation only goes so far, and you pay for things you don’t use. The bill also grows every time someone joins the team, and your data lives on the vendor’s servers, on the vendor’s terms.

Custom management software

It’s software built around the way you work. It has only the features you need and screens designed for the people who use them every day. With a properly written contract, the code and the data also belong to you.

It takes more effort up front, because someone has to understand how you work, set priorities, build and test. And the work doesn’t end at delivery. Custom software needs maintenance, which means security updates, small changes, a server to run on and backups.

The middle ground

The middle ground is often the most sensible route when something already works. You can keep a solid ready-made tool for the standard part, such as accounting, and build only what’s missing. Or you can connect the tools you already have, so data flows from one to the next without anyone retyping it. Sometimes, rather than a new system, you need the existing pieces to stop working in isolation.

How to tell which route fits you

There’s no single answer for everyone, but seven criteria clear things up quickly.

• If your process is standard, an up-to-date off-the-shelf product almost always wins. Invoicing, bookkeeping and payroll work much the same way for everyone and follow rules that change over time.
• If the way you work is what sets you apart, squeezing it into a generic tool flattens it. That goes for quotes, production or the way you look after clients.
• The number of users weighs heavily on cost. With a handful of users the subscription is light, while with a growing team the licence grows with every hire. Software you own has server and maintenance costs, but no licence per person.
• The tools it needs to connect to, such as your website, online shop, payments, invoicing and WhatsApp, should be listed up front. Check whether the ready-made tool already has the connections you need, or whether you’d end up building them anyway.
• If you want the data to stay truly yours, ask yourself whether you can export everything in a usable format. Also ask what happens if the vendor raises prices, changes its plans or shuts the product down. When switching costs so much that it’s no longer a real option, that’s what people call lock-in.
• To compare costs fairly you have to look at a few years, not at month one. On one side are licences that keep rising, extra tools bolted on to plug gaps and hours lost to workarounds, and on the other the initial investment, maintenance and hosting.
• For security and backups, a SaaS means relying on the vendor’s practices. Check where the data is stored, who can access it and whether there’s a written agreement on how personal data is processed. With custom software the same responsibilities need to be assigned in writing from day one, and either way, under GDPR, your clients’ data remains your responsibility.

Warning signs that it’s time for a change

You usually notice it in very concrete situations.

• You enter the same information in more than one place.
• Getting a picture of the month means cross-checking spreadsheets by hand.
• Some information exists only in one person’s head, or on their phone.
• Your team has invented workarounds, such as side spreadsheets, WhatsApp notes and paper reminders.
• You pay for subscriptions you barely use, and the one feature you actually need is missing.
• Mistakes reach your clients, for example a double booking, a forgotten quote or a payment that never got recorded.

If two or three of these sound familiar, it’s worth stepping back to look at how you really work before signing up for yet another subscription.

What to ask before you commission custom software

Custom software only gives you freedom if the rules are clear from the start. Before signing, ask the developer these questions.

• Who owns the code when the project ends, and who owns the data?
• Where does the software run, who pays for the server, and whose name are the accounts and domains in?
• What does maintenance include, how quickly will they respond, and how are new requests handled?
• Is there enough documentation for another developer to pick it up?
• How are backups made, and how often does someone check they can actually be restored?
• If the relationship ends, what do you get, meaning the code, the access credentials and the data in a format you can use elsewhere?
• Does the project start with everything, or with a first version that covers the essential steps?

Custom software is truly yours only when the code, the data and the accounts are in your name, in writing.

On that last question, starting with a smaller first version and growing it is almost always safer than designing everything in one go. It’s the same reasoning behind starting a new app from an MVP.

A real example with PlanB

PlanB grew out of exactly the problem described above. Bookings, clients, staff, services, invoices and payments often end up scattered across a paper diary, Excel sheets, WhatsApp and different software. That leaves more time spent managing the business and less spent growing it.

The answer was to bring everything into one web platform, with a shared calendar, client records, staff management, online booking, invoicing, automatic notifications and reports. Each team member sees what they need, and whoever runs the business always has the whole picture. You’ll find the details in the PlanB case study.

How I can help

If you’re not sure which way to go, we can start from how you work today, meaning the tools you use, where time gets lost and what gets typed in twice. From there I’ll tell you which route makes sense, even when the answer is to keep the software you have and connect it better. If custom is the right call, I design and build it myself, and I stay your single point of contact after launch too. Get in touch and tell me how your work is organised.