Skip to the content

Stop typing the same thing into four systems

The systems you already pay for, talking to each other reliably, so a thing entered once appears everywhere it belongs within seconds.

Typically costs
£30k–£65k
Live in
616 weeks
Price yours properlyThree minutes, and it asks for nothing

Joining systems up

2 parts

01Where this usually starts

A new customer gets typed into your sales system, your accounts package, your scheduling tool and a spreadsheet. They differ within a fortnight. Somebody spends a day a week keeping them in step, and the errors that get through are the ones that reach your customers.

02What changes

What you end up holding.

  • 01Entered once, correct everywhere, within seconds
  • 02A day a week given back to whoever is currently retyping
  • 03Disagreements between systems surfaced and settled rather than discovered by a customer
  • 04A clear answer to which system wins when two of them differ
  • 05Something that keeps working when a supplier changes their end, because it is watched

A day a week handed back, and the cheapest first move if you are not ready to replace anything yet.

03The pieces

What a system like this is usually made of.

You will not want all of it on day one, and you should not pay for all of it on day one. The estimator lets you choose, and shows what each one adds.

Talking to your other systems

Entered once, correct everywhere, within seconds.

Bringing your history across

Checked against the old system and shown to you before you commit to the move.

The sort of detail that matters

  • Anything that fails is held and visible, never silently dropped

04How it would run

6 to 16 weeks, in five phases you approve one at a time.

  1. 01

    Getting to the truth

    A written account of how your work really runs today, what the current way is costing you, and what your new system has to do about it.

  2. 02

    Shaping it

    Every screen and every decision your system will make, in front of you and signed off, with your live date fixed at the end of it.

  3. 03

    Building it

    Your system takes shape week by week in your own account, with something you can click on and try at the end of every fortnight.

  4. 04

    Proving it

    Your own people put it through real work with real records, and everything they find is fixed before anybody depends on it.

  5. 05

    Going live

    Your team moves across trained, with their history intact, on the date fixed months earlier.

What happens in each of them

05Asked most often

The questions that come up.

One of our systems has no way in at all.

Common, and rarely the end of it. Scheduled file exchange, an agreed extract from the supplier, or reading its own screens the way a person would. It costs more than a proper connection, and you get that figure before you commit to anything.

What happens when something goes wrong overnight?

You hear it from the system rather than from a customer. Anything that could not be processed is held, visible, and can be put through again once the cause is fixed. Nothing is dropped silently.

Is this cheaper than replacing the systems?

Usually by a long way, and you will be told when it is. Joining up what you have is often the right first move and buys you a year to decide about the rest.

06The rest of it

Most projects are two or three of these at once.

Put a date on it.

Half an hour with whoever would build it gets you the shape of the work, a figure you can take to your board, and the week it could start. No deck, no discovery fee, no follow-up sequence.