Case studies

The decision first. The software second.

Each of these engagements began by classifying a workflow rather than scoping a build. Client names are withheld where confidentiality applies; we discuss specifics under NDA.

Engagement pattern

Classify first. Build second.

NDA

Workflow under review

Operational process · not a feature list

Decision

Rent
Commodity
Extend
Platform fit
Own
Advantage

Then software

Delivery

Scoped only after the lane is clear

Second

Projects delivered: 150+
Years operating: 14+
References: On request

Selected work

Four engagements, described honestly

Structured the way we would want to read them: what was decided, what was built, what changed.

Legal operations

Own

Matter intake and conflicts, moved out of email

Decision: Intake was the firm's differentiator and its bottleneck. The practice management system could record matters but not shape how they were accepted.
Work: A custom intake and conflicts workflow integrated with the existing system of record, with rules owned by the firm's risk team.

Days → hours

Intake cycle time

Removed

Manual re-entry

The result

Intake moved from days to hours, with the acceptance rules owned by the firm rather than the vendor.

Manufacturing

Extend

Quality exceptions surfaced where operations actually work

Decision: The ERP was correct and staying. What was missing was an operational surface for exception handling on the floor.
Work: An extension layer over ERP and MES data with a purpose-built exception workflow, on tablets, in the plant.

Measurably faster

Exception resolution

Retired

Shadow spreadsheets

The result

Exceptions are resolved on the floor instead of in a spreadsheet, with the ERP left untouched.

Service management

Extend

ServiceNow extended past its configuration ceiling

Decision: Eighty percent of the process fitted the platform. The remaining twenty percent was being forced into configuration that would not survive upgrades.
Work: Scoped applications and a custom service layer for the non-standard path, keeping the platform upgrade-clean.

Contained

Upgrade risk

Full

Process fit

The result

Full process fit without the upgrade risk that heavy configuration was accumulating.

Logistics

Own

One operational picture across carriers and systems

Decision: No vendor modelled this network. The integration and decision layer was the strategic asset, not any single application.
Work: An owned orchestration layer over carrier APIs, WMS and finance, with exception-first operator tooling.

Single source

Status visibility

Proactive

Exception handling

The result

One status source across carriers, and exception handling that runs ahead of customer escalations.

14+

Years delivering enterprise software

150+

Projects across platforms and custom builds

Deep platform practices: Salesforce and ServiceNow

Not the launch. Whether the system was still worth owning three years later.

What we ask you to judge us on

Next step

Want the detailed version?

We walk through architecture, commercials and outcomes for the engagement closest to your situation.

Request a walkthrough Start the assessment