How it works

Seven steps, no surprises. Follow Linda's firm through them.

You should know what you are buying, what it costs and when you can stop. Here is how a Better Systems Co. project runs, told through one wholesaler from the first phone call.

In short: a free 20-minute call, then a paid audit that is credited against the build and free if it finds no savings worth more than its fee, then a fixed quote in writing. We build using your real orders or documents, run the automation side by side with your team until it has proved itself, then go live with your team approving and anything doubtful held for a person. Your existing systems stay in place throughout.

  1. A 20-minute call, free

    Linda rings on a Tuesday. She runs a food wholesaler with 40 staff and thinks the order desk is costing her more than it should. She tells us how an order gets from a customer's email into Sage 50, roughly how many arrive a day, and that Sandra does nearly all of it. We tell her it sounds worth counting, and give her a rough price range for fixing it. Had it not been worth it, we would have said so.

  2. A paid assessment, one to two weeks

    For £500 to £1,250 we spend half a day in Linda's office. We sit beside Sandra while she works, list the systems she logs into, count a week of orders, time them, and write down the checks she does from memory. We test how Sage 50 can take an order in. Linda gets a short report with the cost of the typing in pounds, on her own figures, and a second page saying which of her customers have gone quiet and who pays late. The fee comes off the build. Had we found no savings worth more than the fee, she would not have paid it.

  3. A fixed quote, in writing

    Linda gets one price and one document. It says what will be built, what will not, how we will all know it works, what she pays and when, who owns it, and how her customers' details are handled. Nothing is built until she has signed it.

  4. We build it on her real orders

    Sandra sends us a hundred real orders, covered by a written data agreement. We build against those, awkward ones included. Ordinary software follows the rules for prices, stock and cut-off times. AI is used only to read the messy emails and PDFs, and everything it reads is checked against Linda's own product list and rules.

  5. It runs alongside Sandra

    For a few weeks Sandra carries on typing orders exactly as before. The automation reads the same orders beside her and we compare the two each day. Nothing touches the live Sage data until the results match what was agreed and Linda says go.

  6. Sandra switches from typing to approving

    Now each order is waiting for her, already read and checked, beside the customer's original. She approves it with a click. Anything the software was unsure about waits for her with a note saying why. Every action is recorded. We count the same things we counted in the assessment, so Linda can see the difference in her own numbers.

  7. We stay, if she wants us to

    Linda takes a support plan, from £150 a month. We watch the automation, fix it when a customer changes their order layout, and make the small changes Sandra asks for. The hours and response times are written down.

Linda and Sandra are made up. The seven steps are exactly how every project runs.

What we will not do

  • Tell you to replace a system that works, in order to sell a bigger project.
  • Quote you a savings percentage before we have counted your work. You get the figure in pounds, after the assessment.
  • Connect to any system without its owner's written approval of how we do it.
  • Let software make a decision about money or stock that cannot be undone, without a person saying yes.
  • Sell unlimited development for a small monthly fee.

Questions people ask

How long does a first project take?

One job, such as emailed orders into one system, typically takes three to six weeks from the signed agreement to going live, including the weeks it runs alongside your team. Several connected jobs across more than one system take longer and are done in stages.

How much of our time does it need?

Expect half a day with the people who do the work during the audit, an hour or two a week during the build for questions and testing, and a short daily check while it runs alongside your team. We plan around your busy periods.

What if our systems change mid-project?

Any change is agreed in writing first. Small ones are usually absorbed. Larger ones are quoted before any extra work starts, so the price never moves without your agreement.

Do you use AI, and is our data used to train it?

We use AI to read emails and documents that are laid out differently every time, under contracts that do not allow your data to be used for training. Anything involving money or your rules is handled by ordinary software. A written data agreement names every company that handles your data and where it is kept.

Who owns what we pay for?

You own what was built for you under the written agreement. Better Systems Co. keeps general-purpose parts and know-how. The terms are in the contract for your solicitor to review.

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.