It Was Never About the Website

Key Takeaways

• Achieve Safety Ltd’s website rebuild was framed by its own agency as a whole-business modernisation project, replacing manual processes with automation “across the business,” not a front-end refresh.
• Nationwide Fleet Services’ project for Royal Mail wasn’t a website at all. It was two companies’ internal systems, and their drivers’ phones, being connected directly so a manual reporting process could disappear.
• Neither case study reports a percentage improvement or a measured time saving, both describe the change qualitatively, through what the manual process used to require and what replaced it, worth naming as a genuine evidence gap against the more heavily quantified case studies elsewhere on this site.
• Both projects were commissioned to fix an operational bottleneck, bookings that had to be manually managed, breakdowns that had to be manually relayed, and a website or app happened to be the mechanism, not the point.

Two case studies published on this site describe projects that look, on the surface, like a website build and an app build. Read past the deliverable, and both were commissioned to solve a problem that had nothing to do with marketing. Achieve Safety Ltd needed to stop running its bookings by hand. Nationwide Fleet Services needed its drivers to stop relaying breakdowns through a slower manual process. In both cases, the brief that reached the agency was operational before it was ever digital.

A training provider that outgrew its own paperwork

Achieve Safety Ltd, a health and safety training provider, was running its business on outdated, manual digital systems that were holding back how it took bookings and managed courses. Contrado Digital’s response wasn’t a redesign in the usual sense. The agency rebuilt the company’s website with integrated ecommerce and course-booking functionality, but its own account of the work is explicit that the rebuild replaced manual processes with automation across the business, not just the website. “Contrado Digital have helped us to modernise our whole business by utilising industry leading technologies and driving efficiencies throughout our business with digital methods and automation. I would be 100% willing to recommend Contrado Digital to others,” said Peter Bradley, Achieve Safety Ltd’s Lead Consultant. The word choice in that quote is worth sitting with: Bradley credits the agency with modernising “our whole business,” not the website specifically.

A fleet operator building a bridge between two companies’ systems

Nationwide Fleet Services’ project started from an even more clearly operational brief: Royal Mail drivers needed a way to report vehicle breakdowns and recovery requests directly from their phones, rather than through the slower manual process already in place. Renowned, the agency, began not with design work but with workshops, first with Nationwide’s own fleet software developers to understand the existing breakdown and recovery process, then with Royal Mail’s internal development team to design how requests would flow into Nationwide’s systems and back out to Royal Mail as daily assistance summaries. Multiple APIs were built to connect the two organisations’ systems to each other, and native iPhone and Android apps let drivers report issues from the road rather than by phone call or paperwork. The apps went through a soft launch with testing before the full rollout. “We cannot thank Inaam and his team, for the ingenious technology they developed for our company. Even after they carried out detailed testing, on the soft launch of the apps we did not experience any issues and our client Royal Mail are so thankful for the new apps we made as the drivers are very happy with the new solution,” said Nick Dement, Nationwide Fleet Service’s Managing Director.

What the two projects actually have in common

Neither case study was framed, in its own telling, as a marketing engagement. Achieve Safety Ltd’s problem was that a manual booking and course-management system was “holding back” the business; the fix that mattered was automation, and a rebuilt website was the surface that automation needed to live on. Nationwide Fleet Services’ problem was that breakdown reporting between two companies, and their drivers, ran on a slower manual channel; the fix was a set of APIs connecting Nationwide’s and Royal Mail’s systems directly, and native apps were simply the interface drivers needed to reach that connection from the road. In both projects, the visible deliverable, a rebuilt ecommerce site, a pair of mobile apps, is the part that would show up in a portfolio. The actual commissioned problem, in both cases, was a manual process that had become a bottleneck for the business running it.

It’s also worth being precise about what these two case studies don’t claim. Neither reports a percentage improvement, a time saving, or a booking-volume figure the way several other case studies published on this site do. Achieve Safety Ltd’s result is described entirely through Peter Bradley’s account of what changed, not a measured before-and-after. Nationwide Fleet Services’ result is described through the absence of problems during a soft launch and Royal Mail’s stated satisfaction, not a quantified reduction in reporting time or recovery delays. That’s a real evidence gap, not a criticism of either project. A whole-business automation shift and a two-company systems integration are both harder to reduce to a single conversion metric than a paid search campaign is, and neither case study pretends otherwise.

Why this matters for how a business briefs a “website” project

The practical lesson from reading these two together is about how a business defines the project in the first place. Achieve Safety Ltd could have briefed its agency for a website refresh and got one; instead it briefed for whole-business automation and got a rebuild that happened to be a website because the booking and course-management functions needed a public-facing home. Nationwide Fleet Services could have briefed for a driver-facing app; instead it briefed for a connection between two companies’ systems, and the app was simply the endpoint drivers needed to reach it. Neither agency started with a page layout. Both started by mapping the manual process the business actually wanted to remove, and only then worked out what digital surface that removal needed. A business treating a manual, paper-based or phone-based bottleneck as purely an operational fix, something to solve internally rather than something to brief a digital agency for, risks missing the version of the fix both of these case studies actually describe: the automation and the interface are usually the same project, not two separate ones.