Every few weeks a new supplier gets in touch. There is an app for rotas, an app for bookings, an app for reviews, an app for invoices, an app for chasing invoices. Each demo is slick, each monthly fee looks small, and each one promises to save you hours. Some of them genuinely would, on their own.
The trouble is that nobody buys software on its own. It lands on top of everything you already have, and that is where the hours quietly go.
The pattern: one problem, one app
It usually starts sensibly. Bookings are messy, so you buy a booking tool. Then customer follow-ups slip, so you add an email tool. Then quotes take too long, so there is a quoting app, and a separate one for job sheets, and a spreadsheet to tie the numbers together at the end of the month.
Each purchase fixes the symptom in front of it. None of them fixes the cause, which is usually that the business has no single place where the work, the customers and the money come together. Give it a couple of years and you have ten logins, ten copies of your customer list that never quite agree, and a member of staff whose real job is copying things from one screen to another. More software, and more admin than before you started.
A sticky plaster stops you looking at the wound. It does not stop you getting cut in the same place again.
Signs you are buying sticky plasters
- The same details get typed in more than once. A new customer goes into the booking tool, the invoicing tool and the mailing list, by hand.
- Nobody trusts a single number. Ask how many active customers you have and you get three answers, depending on which system someone checks.
- Reports are built in a spreadsheet. Every month someone exports from several places and stitches it together.
- Only one person knows how it all connects. If they are off sick, things stop or go wrong.
- You are paying for tools nobody opens. Subscriptions renew for apps that were bought for a problem that has since moved on.
- The next purchase is already being discussed. A new pain point appears and the first instinct is to look for another app, rather than asking why the current setup let it happen.
None of this means the individual tools are bad. It means nobody has stepped back and designed how they should work together, or whether they need to exist at all.
What a long-term fix looks like
Understand how the business really runs first
Before anything is built or bought, someone should sit with the people doing the work and map it: where enquiries arrive, who touches them, what gets handed over, where things wait and where they fall through. The way a business actually runs is rarely the way the org chart or the last software demo assumed. Good software is shaped around that reality, not the other way round.
One joined-up foundation, not another silo
The aim is a single core system that holds your customers, your work and your money in one place, with everything else either built into it or properly connected to it. That might mean keeping a couple of specialist tools you like and wiring them in, and retiring the rest. What matters is that information is entered once and flows to wherever it is needed. If you are deciding where to start, our piece on whether you need a website, an app or a CRM first walks through the order.
You own your data, and on bespoke work the custom layer
Your customer records, history and documents are yours. You should be able to export them in a usable format whenever you like, without asking permission or paying a release fee. On bespoke work, the custom layer built for your business should be yours too. That is what stops a supplier relationship turning into a hostage situation. We cover the website side of this in do you actually own your website?
Someone who stays to support and improve it
Launch day is the start, not the finish. Businesses change, people change and new needs turn up. A long-term fix comes with someone who answers when something breaks, keeps it secure and up to date, and improves it as you learn what you actually need. Software that is handed over and left alone slowly turns into the next problem.
Questions to ask any software supplier
Whoever is pitching you, these questions cut through the demo quickly. A good supplier will answer them plainly, and will not mind you asking for the answers in writing.
- Who owns the data and the code? You should own your data outright. On bespoke work, find out exactly what you own and what stays theirs.
- Can I export everything? Not just a summary. All of your records, in a format another system could read.
- What happens if you disappear? If the company closes, is bought or drops the product, how do you get your data out and keep running?
- Do you run your own software in production? Have they built and kept live products of their own, with real users, or is yours the first?
- Who supports it after launch? A named person or team, response times, and what it costs.
- Do you train AI on my data? You should get a clear yes or no, and know where your data is stored and who can see it.
If the answers are vague, that tells you something on its own.
Why a supplier that runs its own products is a safer bet
Building software for a client and then walking away is one skill. Running software every day, with real people relying on it, is another. Suppliers who run their own live products deal with the things that only show up after launch: the update that breaks something, the customer who needs their data exported, the security patch on a Sunday, the feature nobody asked for that turns out to be essential. That experience carries straight into the work they do for you.
It is also why we work the way we do. Alongside client work, we build and run our own products: Jeanus, our CRM, Stamp for loyalty cards in Apple and Google Wallet, avibe for free ticketing and bookings, and Strandline on iOS. They are not a sales pitch. They are where we learn, every day, what it takes to keep software useful long after the launch.
Common questions
Why does adding more software sometimes make things worse?
Each new app solves one problem in isolation. It brings its own login, its own copy of your customers and its own way of doing things, so information gets typed in twice, drifts out of step and has to be reconciled by hand. Past a certain point the joining up becomes a job in itself.
Should we replace all our software at once?
Rarely. The sensible route is to map how the business actually runs, decide what the core system should be, and move across in stages. Some good tools will stay and simply be connected properly; others can be retired once their job is covered.
What should we ask a software supplier before signing?
Ask who owns the data and the code, whether you can export everything, what happens if the supplier disappears, whether they run their own software in production, who supports it after launch and whether they train AI on your data. Get the answers in writing.
Is bespoke software always better than an off-the-shelf app?
No. If a well-made product fits how you work, use it. Bespoke work earns its place when your process is specific enough that generic tools need constant workarounds, or when the real problem is that your systems do not talk to each other.
If your business has collected more apps than it can keep track of, we are happy to take a look. Book a free 30 minute look at your systems and we will tell you plainly what to keep, what to connect and what to drop. If you would rather start by seeing something, ask for a free concept.
