Neul Labs client delivery
Work Neul Labs carried out for a client, with a measured result. Published only with the client’s approval, anonymised unless they choose otherwise, and always with a definition of what was measured.
This page →Case studies
Measured results, honestly defined
Client outcomes from Neul Labs engagements. Each one names the metric, defines exactly what was measured and says what the figure does not show. Every account is anonymised and approved by the client.
Client delivery Payroll preparation
48 hours → 40 minutes
Elapsed turnaround per payroll cycle
Payroll preparation: from 48 hours to 40 minutes
How automated input collection and validation cut payroll preparation turnaround from 48 hours to 40 minutes for a UK employer with 250–1,000 staff.
A UK employer with 250–1,000 staff
Read the case study → Client delivery Production tracking and stage handoffs
20 days → 1 week
Elapsed turnaround for the production workflow in scope
Animation handoffs: from 20 days to one week
Connecting production tracking and tools cut workflow turnaround from 20 days to one week for an independent animation studio with under 50 staff.
An independent animation studio with under 50 staff
Read the case study →Reading the evidence
Three kinds of evidence, kept apart
A buyer deserves to know which claims rest on client results, which on prior experience and which on public code. We label each one and never let one stand in for another.
Founder professional experience
Systems the founder built or led in previous roles. That experience informs how we work, but it is not Neul Labs client work and we do not present it as such.
About the studio →Neul Labs public engineering
Open-source projects, benchmarks and methods anyone can inspect. They show how we build. They are not customer case studies or warranties that a component fits your system.
Project catalogue →Why the definitions matter
"Faster" can mean several different things. Elapsed turnaround is the calendar time from inputs arriving to output being ready, including all the waiting in between. Active labour is the time people actually spend working. Review effort, error rates and total cost are different again. A process can halve its turnaround without saving an hour of labour, or save labour without finishing any sooner.
Both results published here measure elapsed turnaround, compared before and after the change. Neither is a claim about labour saved, cost or quality, and neither is a promise about what another organisation would see. The engineering evidence method sets out what each class of claim needs before we publish it.
We publish a result only when three things are true: the client has approved the account, the metric is defined precisely enough that someone else could repeat the measurement, and the before and after figures were taken the same way. Results that do not meet that bar stay out of our marketing, however good they look.
Both engagements were workflow automation in the plain sense: connecting systems, validating inputs early and making handoffs explicit. If that sounds like your process, the workflow automation page explains how we would approach it.
Have a workflow that takes too long?
Tell us how often it runs, which systems it touches and where the time goes.
Describe your workflow