Work

Selected work.

Our engagements are confidential, and we do not publish client names or figures. These are two we can describe. Both ran inside a national third-party benefits administrator, a regulated operation where every decision is subject to audit.

Enterprise IT · service desk and operations

Service requests handled without a queue, and an IT estate the team can see.

A benefits administrator running a large, regulated IT estate: virtualization, backup, and endpoint platforms across the organization, with a service desk fielding a steady volume of requests and no single view of what was healthy and what was not.

What we delivered

An intake assistant inside the existing service-desk platform that takes requests in plain language, classifies them, and raises correctly formed tickets, and consolidated monitoring across the server, virtualization, and backup estate so operations staff see issues before users report them.

What changed

Routine requests are handled at intake instead of in a queue. Operations staff work from one view of the estate. The service desk runs inside the platform the client already owns, with no new tool to learn.

Applied AI · claims review

Claims reviewed with the evidence attached, and a person's name on every decision.

The same administrator processes high volumes of claims against dense plan documents. Reviewers spent most of their time finding the relevant passage before they could decide, and the decision record did not show which evidence had been considered.

What we delivered

A claims-review system in which every recommendation cites the exact passage of the plan document it rests on. Reviewers click the citation, see the highlighted source, and approve or correct the decision. Every approval is recorded with the reviewer's name and the evidence they saw.

What changed

Reviewers decide from evidence rather than searching for it. Every material decision carries a name and its source. The record stands up to internal review and external audit, and corrections feed back into the system.

In every engagement

What the client keeps.

Working software

A first version in daily use within 30 days, inside the client's environment.

Documentation and training

Written guides and hands-on training, so the client's team runs it.

Ownership

Code, data, and documentation belong to the client. Nothing is held back.

A record

Every material decision carries its evidence and the name of the person who approved it.

Start here

Let's talk about what changes in your operation.

A 30-minute conversation with the firm's leadership. We'll tell you where the return is, and where it isn't.

Discuss an engagement See how we work