The Space Between Your Apps Is Eating Your Week

It is 9:12 on a Tuesday and someone in your operations team is doing something they would never put on a CV. They are copying a list of order references out of one system, pasting it into another, then going back to the first system because the paste went wrong somewhere around row 40.

Nobody asked them to do this. There is no process document. It is simply the shape the work has taken, it will take 25 minutes, and it will happen again tomorrow.

The cost that never reaches a budget line

Most UK teams can tell you what they spend on software. Very few can tell you what they spend moving work between it.

That is the handoff tax: the cumulative cost of every moment where a piece of work leaves one platform and has to be re-entered, re-explained, re-approved or re-checked somewhere else. Copy-paste. Re-keying. Chasing a sign-off in a direct message because the workflow tool only nudges people who remember to open the workflow tool. Screenshotting a dashboard into a slide because the leadership team live in a different app entirely. Waiting for the only licence-holder on the team to come back from lunch so a record can be approved.

Each instance feels like nothing. Together they are the reason your people describe themselves as flat out while the important work sits still.

Doing the rough maths

Take a 30-person team on a standard 37.5-hour week. Suppose each person hits eight handoffs a day — not unreasonable for anyone working across a CRM, a finance package, a project tool and a chat app. At three minutes each, that is 24 minutes a day, about two hours a week.

That is roughly 5 per cent of contracted time, which sounds survivable until you price it. At a loaded cost of £35 an hour, 30 people losing two hours a week is over £100,000 a year. Now assume six minutes per handoff, because approvals involve waiting and waiting is not free, and you are closer to a day a week per person.

The figures are illustrative and any finance director will say so. The point is not the precision. The point is that the same organisation will spend three months building a case for a £40k licence and never once quantify the six-figure sum of manual ferrying happening quietly underneath it.

Integration debt is now a culture problem

We tend to file this under technical plumbing — an API that was never built, a connector nobody bought. But integration debt is what grows around the gap when the plumbing is missing, and that growth is human.

It looks like folklore. Ask a new starter how invoices get from the project tool into Sage and the answer is a name, not a process. It looks like personal automation accounts on someone's own card, quietly gluing two systems together in a way that no one has documented and IT has never seen. It looks like the person who is the single point of failure for an entire revenue process, and the annual leave request that makes the whole team nervous.

That is why the phrase 'just integrate it' so often stalls. The technical work is the easy half. The hard half is that a dozen people have built small, sensible, undocumented coping mechanisms, and each one has to be unpicked before anything can be joined up properly. The workarounds are the culture. Until you can see them, you cannot change them.

There is a second cultural cost, which is harder to put on a slide: nobody feels responsible for the gap. The platform owner owns the platform. The process owner owns the process. The space between them belongs to whoever is standing nearest at the time.

A one-week audit that costs nothing

You do not need a consultant, a maturity model or a new tool to find your worst bottlenecks. You need a week, a stopwatch and the willingness to be mildly embarrassed.

1. Pick one process end to end. Not the whole department. Quote-to-cash, client onboarding, or the monthly board pack. One thread.

2. Map the handoffs, not the tools. Draw the process, then mark every point where a human moves data or chases a decision. You are looking for the crossings, not the systems.

3. Time five of them honestly. Sit next to someone and watch. Do not ask how long it takes — people round down, because they think the answer reflects on them.

4. Multiply. Volume per week, times minutes, times loaded hourly cost. You now have a number with a currency symbol in front of it, which is the only kind of number that survives a steering group.

5. Rank by fragility as well as cost. The question is not only what it costs, but what breaks when the person who does it is off sick. Some of the cheapest handoffs are the most dangerous.

6. List what you could delete. Not automate. Delete. An approval nobody has refused in two years is a handoff with a salary.

Delete first, integrate second

The tempting conclusion is that you need better tooling. Occasionally that is right. More often the audit reveals three steps that exist because of a decision made in 2019 by someone who has since left, and a fourth that exists only because two systems disagree about what a client is called.

Fixing the definition of a client is free. Deleting a redundant sign-off is free. Fixing the copy-paste loop usually requires a proper integration, which costs money and takes time — and is far easier to justify once you can show the annual cost of not doing it.

The Friday version

If a week is out of reach, book 20 minutes on a Friday and ask everyone in the team for the three things they copy and paste most often. Tally it. You will have your shortlist before the kettle boils, and you will probably find that half the room names the same three things.

That is your starting point — before the renewal, before the next demo, before anyone suggests another platform to sit in the middle of the others.