Almost every case study you’ll ever read was written in the first 6 to 12 months after go live. Ours included.

There’s a reason for it. That’s when the change is loudest and easiest to count. Admin hours are down, the errors have stopped, everyone still remembers what the old way felt like, and the numbers go onto a page cleanly. Efficiency is usually the clearest thing to measure, so efficiency is what gets measured.

It’s also the smallest version of the story. What that efficiency turns into can take a lot more than 12 months to surface, because the gains compound quietly and then the business takes a step change off the back of them. It’s often not dug into or understood, because there’s a tendency to rush on to the next case study or the next customer.

So we went back and asked. Five years on, what actually happened?

The first pass

We wrote KAB Solutions up not long after go live. Demolition, excavation, bins and hire, several work types running at once, schedule changes constantly. The numbers we published then were the usual ones: 69% less time on job allocation, 88% less on job progress tracking, 75% off quality checking. Four systems down to one.

Good numbers. Entirely ordinary case study.

The line in that piece that turned out to matter wasn’t a number. It was Kurt Beckett, Director at KAB, on what the change had bought him:

‘I feel now like I have a solid base to build on, to grow more, because of Emvisage.’

That’s a forecast. This is what happened to it.

Five years on, the business is five times the size

Over those five years KAB grew five times over. Kurt is direct about the part Emvisage played: it helped him do it.

Underneath growth like that is something far less exciting to write about. The process holds.

A process that holds is one where the work doesn’t depend on anybody remembering it. It sits in one place, the form won’t let an item through, the status is there without a phone call, and the next step happens whether or not someone chases it. None of that is interesting until the volume doubles, and then it’s the whole game. Work that runs on memory, email and a mix of software tools degrades as it scales, and it degrades quietly at first. More jobs means more edges, more handovers, more detail half-known by one person who’s on leave next week. A process that holds takes the extra volume and behaves the same way at the other end.

‘Now everything’s there in the one location, and it’s spread across everyone, everyone knows what’s going to happen.’

That’s the difference between coping with growth and being set up for it. And it’s the part a customer feels first, because a stretched process never fails internally. It fails as a missed window, a report that doesn’t arrive, a job closed out without the evidence, an invoice nobody can substantiate.

The plainest test of whether a process holds is whether it can be handed over. Key person dependency is what quietly caps a lot of operators. The operation runs on somebody’s judgement and memory, so it can only grow as far as that person’s week goes, and it carries a continuity risk every client can see. KAB passed that test.

‘Emvisage allowed me to pass the day-to-day running of the business on to someone else. I now have an operations manager who runs all the day-to-day, so I trust him entirely to fill it all out, answer the phone calls and run the day-to-day, which allows me to focus on upcoming works and the future direction of the business.’

‘I used to finish up the day at 7, 7:30, 8 o’clock at night. Most days now I’m well and truly finished by the 4 or 5 o’clock mark. And I just, all around, can trust that it’s going to be done.’

The real constraint is often what your customers think you can handle

Ask an operator why they haven’t taken on more work and you’ll hear about crews, plant, cash and risk. What you’re less likely to hear is that a lot of the decision isn’t theirs. A principal contractor or an asset owner handing out work is transferring risk, and before they transfer more of it they want to know whether your process holds. Whether you’re dependable when the program compresses. Whether you can ramp up without things slipping through. If the answer is uncertain, nobody tells you no. You get kept as overflow.

That judgement gets made on unglamorous evidence. Reports arriving on time and complete. Jobs closed out with the photos attached. Compliance records produced on request rather than reconstructed. Invoices that survive a query without a week of email archaeology. This isn’t about capability in the field, and most contractors who lose out on this are excellent in the field. It’s about whether the workflow behind the crews holds up under volume.

That’s what sits underneath the 5x. Growth on that scale isn’t won by having spare hours in the week. It’s won by being the contractor a client is comfortable handing more to, and then being set up to take it.

Year one shows you the gain, not what it unlocks

When the fit is right end to end, the gain isn’t a percentage off one step. It’s that the whole run, from job request to close out to invoice, happens as one process. No re-keying, no chasing, no double handling between systems. In complex, high consequence work that’s worth far more than it looks, because it opens up real capacity, and that capacity goes into the things that never got a look in. The process improvement nobody could get to. The contract that needed a better answer on reporting and compliance evidence. The work type the business couldn’t service before. Every one of those makes the following year easier than the one before it.

That’s the compounding, and it runs both ways. A system that nearly fits compounds too. The steps it doesn’t cover get done somewhere else, and somewhere else becomes a spreadsheet, then a tracker, then a person whose job is holding the gap together. None of that looks serious in year one. By year five it’s a second operation running alongside the first, quietly absorbing the capacity that should have gone into growth.

In year one, the difference between a system that fits and one that nearly does is decent. By year five it’s a chasm.

Which is why we’d rather be judged on year five. It’s a harder test and it’s the only one that answers the question you’re actually asking, which isn’t whether this saves time. It’s whether it changes what the business can do.

Grow without growing the back office. Book a quick demo