Systems and integration

Too many logins? How to get your business systems in one place without replacing them

By · Published

You can get your business systems in one place without replacing them by building a single screen, behind a single login, on top of the software you already run. It collects what each system knows, tells you when something needs attention and lets you approve actions that are carried out in the right system. The existing systems stay exactly as they are.

Phil runs the office at a door and window retailer. Before he has taken his coat off he has logged into six things. The supplier’s ordering site. A second supplier site for delivery dates. The sales system. The accounts. The fitters’ diary. The deposits spreadsheet on the shared drive.

At ten o’clock a customer rings to ask where her door is. The order is in one system, the delivery date in another and the fitter’s booking in a third. Phil says he will ring her back.

On Thursday the supplier moves a delivery date. It changes on their site. Nobody at Phil’s firm is looking at their site on Thursday. The fitter finds out on the customer’s drive.

Phil is made up. The six logins are not.

Key facts

  • The average small or medium UK firm runs 52 digital tools behind 27 logins, and nine in ten spend significant time re-entering information by hand (Sage, September 2026).
  • The same survey found an average of 2.9 hours a week spent moving information between systems that do not connect, which Sage puts at about £5,700 a year per business.
  • Compatibility with existing systems is the third most important thing UK small and medium firms look for when choosing technology, after ease of use and cost (Department for Business and Trade, July 2025).
  • Systems can be brought together on one screen without replacing any of them.
  • Better Systems Co. only connects to a system by a route its owner has approved in writing.

Why do established firms end up with so many systems?

Because each one was a sensible purchase at the time. The accounts package came first. Then a sales system, because the accounts package could not hold quotes. Then a diary for the fitters. Then the supplier launched an ordering site and everyone had to use it. Nobody chose to have six. They arrived one at a time over fifteen years.

Each one does its own job well enough. What none of them does is talk to the others. So the people do the talking. Phil carries a delivery date from one screen to another in his head, and that works until the day he is off.

Sage’s survey of 1,500 UK small and medium firms found that the average one now runs 52 digital tools behind 27 logins (Sage, September 2026). Phil’s six is modest.

What does it cost when systems do not talk to each other?

It costs time you can count and mistakes you cannot see coming.

The time. Say Phil spends 40 minutes a day logging in, looking things up and ringing people back with answers. Over five days a week and 48 working weeks, that is 160 hours a year. At £20 an hour all in, it is £3,200 of his time. Those are example figures for one person. Sage puts the average across UK small and medium firms at 2.9 hours a week, or about £5,700 a year per business.

The mistakes. A system that does not talk cannot warn anyone. The delivery date that moved on Thursday was visible the whole time, to anyone who logged into the right site and looked. Nobody did, because nobody knew to. A fitter’s wasted morning and an annoyed customer cost more than the 40 minutes ever did.

The owner’s view. Ask the owner of Phil’s firm how many doors are waiting on the supplier, and how much is owed in balances, and the honest answer is “I will ask Phil”. The figures exist. They are in four places.

Do we have to replace them all with one big system?

No, and for most firms it is the wrong move. An all-in-one system, usually sold as an ERP, promises one login by replacing everything you have. That means moving every record, retraining every person and a long project. It also cannot replace a system that belongs to your supplier.

The other way is to leave every system where it is and join them up.

Replace with one big system Join up what you have
What happens to your current systems Switched off Stay exactly as they are
What your team has to learn Everything again One new screen
Systems owned by suppliers or customers Still separate Can be included, with their approval
Time before you see a benefit After the whole project After the first system is connected
If it does not work out Hard to go back Switch it off and carry on as before

Our guide on whether to replace or integrate business software sets out the few cases where replacing is right. When the systems themselves still do their jobs, joining up is cheaper and far less disruptive. Compatibility with existing systems is the third most important thing UK small and medium firms look for in new technology, after ease of use and cost (Department for Business and Trade, July 2025).

What does “everything in one place” actually mean?

Five things, and a firm can start with the first two.

  1. One login. Your team signs in once. The systems underneath keep their own logins, which the connection uses on your behalf.
  2. One screen. Each order, job or customer appears once, with what every system knows about it. For Phil, one line for each door. Ordered, confirmed, delivery date, fitter booked, balance owing.
  3. You are told. When a date moves, a payment is late or stock runs low, the right person gets a message. Nobody has to remember to look.
  4. The figures, together. How many doors are waiting, what is owed, what is running late. Always up to date, with no one building a report.
  5. Actions ready for your yes. A rebooked fitter, a reorder or a chasing email is drafted and waits for a person to approve it. On approval it is carried out in the system it belongs to.

Nothing here decides anything about money on its own. A person approves, as with everything we build.

Can systems we do not own be included?

Often, with the owner’s approval. This matters, because for many firms the most awkward login is not theirs. It is a supplier’s ordering site or a big customer’s portal.

This part is real, and it is not Phil’s story. The engineering practice behind Better Systems Co. built an ordering website for a door retailer and connected it to its supplier’s ordering system. That system had no API, which is the usual way for one program to talk to another, and the supplier’s side turned out to be several separate systems with separate logins. The connection was made by a method the supplier had permitted. The supplier did not commission or endorse the work. The write-up is in the case study.

The rule is the same every time. We only connect to a system by a route its owner has approved in writing. We never scrape a site or get round a login. Where a supported route exists we use it, and our guide to integrating a legacy system that has no API explains the options when one does not. If an owner says no, that system stays separate, and you know before you spend anything.

Where should we start?

  1. Write down everything you log into. Systems, supplier sites, shared spreadsheets. Most owners find the list is longer than they thought.
  2. Write down the questions you ask every day. “Where is this order?” “Who owes us money?” “What is late?” These decide what goes on the screen.
  3. Pick the two systems that answer the most questions. Join those first.
  4. Add the alerts that would have saved you last month. The date that moved. The payment that never came.
  5. Then add the next system.

A paid Automation Opportunity Audit does the first two steps with you and puts a figure in pounds on the time being lost.

What does Phil’s morning look like afterwards?

He signs in once. Every door is on one screen. Two have a flag beside them. The supplier moved one delivery date overnight, and one balance is a week late.

A new date for the fitter is already drafted. Phil reads it and approves it, and the fitter’s diary changes. A reminder to the late payer is waiting for his yes as well.

At ten o’clock a customer rings to ask where her door is. He tells her, while she is still on the phone.

The six systems are all still there, doing what they always did. A firm that works this way answers its customers on the first call. The one that does not is still ringing them back.

What we would do

We would start by listing what your team logs into and what they have to look up, then put a figure on it in the audit. If it is worth doing, Better Systems Co. builds one screen on top of the systems you already run, one connection at a time, each agreed with the system’s owner. Nothing is rebuilt. See one screen for all your systems and connecting existing systems.

Sources

Questions people ask

Do we have to replace our systems to get everything in one place?

No. The systems stay as they are. A single screen is built on top of them that reads what each one knows and shows it together. Your team keeps the software it knows and loses the logging in and looking up.

Will we really have just one login?

For day-to-day work, yes. Your team signs in once. The systems underneath keep their own logins, which the connection uses securely on your behalf, and anyone can still open a system directly when they need to.

Can a supplier's or customer's system be included?

Often, with their written approval. We never connect to a system without its owner agreeing to the method, and we use a supported route wherever one exists. If an owner says no, that system stays separate and we tell you before you commit.

What does it cost?

Better Systems Co. prices this at £3,000 to £15,000 or more, depending mainly on how many systems are involved and how each can be reached. A paid audit of £500 to £1,250 comes first and is credited against the build. If the audit finds no savings worth more than its fee, you do not pay for it.

Related guides

Find out what the typing is costing you

A 20-minute call. You tell us about your Sandra, your Dave or your Phil, and how the job gets done today. We tell you honestly whether automating it would pay, and what it would cost.