Skip to content

Use cases

Use cases by department and industry.

Apps, automation, reporting and migrations our people have delivered. Filter by the problem you have, see the numbers, then read how it was done.

The work at a glance

By department

Use cases per department. Select a bar to filter.

Industry and department

How many use cases sit at each crossing. Select a cell to filter.

IT and platformFinanceHR and peopleOperationsSales and serviceRisk and legalManagement
Finance and insurance
Professional services
Public sector
Energy
Life sciences
Manufacturing
Transport
Technology
Education
Real estate
Cross-industry

61 use cases

Results in numbers

Figures from the delivered projects.

How should you read these use cases?

Why are client names left out?

Most of this work runs inside regulated or internal systems, so we describe each client by sector and size instead of by name. We name a client only when they approve it in writing.

What does each use case cover?

Each use case is a project our people delivered: the problem the client had, what we built, and the result. Together they cover governance, business apps, automation, reporting, migrations and Copilot.

Where do the numbers come from?

From the projects themselves: build effort, time saved, volumes handled and people supported, recorded by the people who did the work. Where a case has no number, it describes the outcome in words.

Can you do the same in our tenant?

Usually yes, with changes for your licences, data and rules. We start with a short scoping call and look at what you already have, so the scope for a similar build starts from facts rather than guesses.

Have a similar problem?

Tell us about it. When the work is done we write up the result together, anonymised unless you approve naming.