Selected work

The kind of work we do

Detailed client case studies are being written as current engagements reach measurable outcomes. Until then, the examples below are illustrative — representative of the engagements we take on and the shape of outcome we work toward, drawn from common situations rather than specific named clients.

A note on these examples

Each example is clearly marked as illustrative. The companies are anonymised and the figures are representative targets, not measured results from a specific client. We would rather show you an honest illustration than a fabricated success story — and real, client-approved case studies will take their place here as they are ready.

Illustrative Idea to Software

Replacing paper job sheets for a field-service company

A 120-person field-service company ran its daily work on paper job sheets that were rekeyed by hand each evening. We replaced that with a mobile-first workflow platform, cutting the rekeying entirely and getting invoices out days sooner.

Field services

Illustrative Modernization

Making an ageing .NET system safe to change again

An eight-year-old .NET application still ran a professional-services firm, but a one-line change took three weeks and only two people dared touch it. We modernised it incrementally — deployment and tests first — until change was cheap again, with no rewrite and no feature freeze.

Professional services

Illustrative AI Adoption

An AI document-extraction pilot that had to earn its place

A finance operations team drowning in supplier invoices wanted "AI". We ran a three-week sprint that defined the accuracy bar first, built a working extraction prototype on real documents, and evaluated it honestly against that bar — with a human in the loop and a clear fallback.

Financial operations

What you would receive

The artefacts every project produces

Illustrations aside, these are real and concrete — the same deliverables you would get on your own engagement.

  • Architecture decision record

    Why a decision was made, what was rejected, and what would cause us to revisit it — so a future team can disagree with us knowingly.

  • Modernization scorecard

    A scored assessment across architecture, quality, delivery and operational risk, with a prioritized roadmap rather than a list of complaints.

  • System context and deployment diagrams

    What talks to what, where it runs, and where the risk sits — legible to an executive and precise enough for an engineer.

  • Security and quality statement

    The standards we hold ourselves to on every engagement: review, testing, dependency management, secrets, backups and incident response.

Tell us what you are trying to build or fix.

A 30-minute call is enough to tell you whether we can help, what it would take, and what the sensible first step is. No obligation, no pitch deck.