Case Studies Overview
See how Digital Royalty builds custom software, integrations, and business systems that run in production.
Featured Projects
November 2026
Updating an Out-of-Date WordPress Site Without Breaking It
This page is an illustrative composite. It draws on update and domain work we have done on real WordPress sites, with every client detail removed, so it shows how the work runs and carries no outcome figures. The Challenge The site worked, so it had been left alone. WordPress itself was a major version behind and the plugins screen had...
0
Discussions
2026
Delivered
0
Tags
October 2026
Evolution Engineers: a lead platform built around one business
Who they are Evolution Engineers is a technology-led lead generation business that builds, tests and continuously improves systems for generating high-quality customer opportunities at scale. It operates across more than 20 markets, combining paid media, proprietary technology, automation and commercial data to connect businesses with prospective customers. Evolution Engineers was founded by James Lee. We’ve worked with the business on...
0
Discussions
2026
Delivered
0
Tags
All Case Studies
Legmark: rebuilding a live platform without taking it offline
Who they are Legmark is a marketing agency for law firms. Its product benchmarks around 5,700 UK law firm websites, shows each firm where it stands against the rest, and tells it what to fix first. We built that product. We’ve been Legmark’s development partner since late 2021, and in 2026 we built its second generation. The first platform We...
Spreadsheet to Internal Platform Migration
The Problem A mid-size operations firm was running its entire business across a stack of interlinked Google Sheets. Job intake lived in one workbook, scheduling in another, time logging in a third, invoicing in a fourth, and a master dashboard pulled selected ranges from all of them via fragile cross-sheet references. The spreadsheets had grown organically over several years, and...
Recruitment Automation Workflow Replacement
The Problem A specialist recruitment firm placing technical staff into mid-market businesses was handling candidates almost entirely by hand. CVs arrived by email and were saved into folders by consultant. Initial screening notes lived in a shared spreadsheet that consultants updated when they remembered. Calls were logged sporadically, and follow-up reminders depended on each consultant’s personal calendar discipline. The visible...
Recruitment Agency Pipeline Platform
The Problem A UK recruitment agency placing across several specialisms was running its pipeline across a generic ATS, two LinkedIn instances, a shared spreadsheet that nobody admitted to owning, and individual consultants’ personal Excel files. The ATS held candidate records. The spreadsheet held the actual state of each role: who was being put forward, where each candidate was in interview,...
Multi-Location Finance Reporting Dashboard
The Problem A multi-site services group operating several branches across the South of England had no consolidated view of its own finances. Each branch ran its own copy of the same accounting software with its own chart of accounts, its own customised categories, and its own way of recording the same transaction. Group finance lived in Excel: every month, the...
Legacy Access Database Replacement
The Problem A long-established UK manufacturing business had been running its core operational records on a Microsoft Access database for many years. The database held customer records, order history, production scheduling, and dispatch logs going back a long way, spread across a sprawl of tables, with macros and VBA built up over time by people who had since left the...
Law Firm Client Document Portal
The Problem A UK legal practice was sharing client documents the way most small firms do: email attachments, the occasional Dropbox link, and the occasional encrypted ZIP when the matter felt sensitive enough to warrant the extra step. The model was familiar to everyone but no longer defensible. Clients had started asking, at the start of new instructions, what the...
Internal SOP Platform for Distributed Team
The Problem A distributed services business with staff across the UK and Europe had accumulated standard operating procedures the way most growing businesses do: by accident. Documents lived in several Google Drive accounts (depending on which director had originally written them), a Notion workspace that had been adopted with enthusiasm and then drifted, a couple of long internal wiki pages,...
Healthcare Workflow Automation
The Problem A UK clinical operations team supporting a multi-clinician practice was buried in administrative work that sat around the patient-care system rather than inside it. The clinical system itself handled records, appointments, and notes correctly. What it did not handle was the workflow surrounding it. Referrals came in by fax, post, encrypted email, and the occasional portal. Each one...
Finance Back-Office Modernisation
The Problem The finance team of a UK professional services firm (a small team supporting a mid-sized business) was running across four separate platforms. Invoicing happened in the accounting system. Expenses were captured by staff in a different mobile expense app. Reconciliation against the bank was done in the accounting system again, but with a separate plugin. And reporting to...
About Our Case Studies
What We Build Looks Like This
Most development agencies describe their work in abstract terms: capabilities, methodologies, tech stacks. We would rather show what got built, the problem it was built for, and what it lets the business do now.
Where a case study names the client, as with Legmark and Evolution Engineers, it describes that client’s build. The unnamed ones are illustrative: they show the kinds of systems we build and how they work, with client details anonymised and in some cases combined into a composite. We describe what was built and what it makes possible, and we do not put outcome figures on work a client has not measured and published.
Most of them start the same way. A business outgrows what off-the-shelf tools can do, and we build a system around how it already works. A support retainer lets that system keep changing month by month after launch.
Each study goes into the detail: the integrations involved, the architectural decisions, the constraints we worked within and the trade-offs we made. You will find custom portals, AI automation, monitoring, API integrations and legacy modernisation work here. If you are comparing development partners, read the one closest to your own problem and judge for yourself whether we understand it.
Ready to Be Our Next Success Story?
Let us discuss how we can help transform your business with technology solutions that deliver real, measurable results.