Case studies / Work in context
Better systems show up in the everyday.
These fictional engagements show the kind of practical decisions, trade-offs and measurable results we value. Each outcome is contextual to its own operating baseline.
01 / Freight finance · Compliance
Harbor Ledger
A clearer review process for a freight-finance operator handling dense, time-sensitive evidence.
Outcome · compared with the previous workflow
time spent preparing review packs
The challenge
Reviewers assembled evidence from separate systems, checked recurring documents by hand and copied decisions into a pack for each account. The operator could not replace its core finance system during the engagement, and review decisions needed a traceable human sign-off.
The approach
We observed review sessions, mapped evidence sources and tested a compact queue-and-checklist model with reviewers. Rather than automate judgement, the team chose to automate evidence collection and highlight missing or changed material for a person to resolve.
What shipped
A responsive review workspace, evidence checklist, change and exception cues, audit-ready summary export, integration adapters and a measured rollout with the operations team.
The fictional case-study team measured review-pack preparation time against the operator’s own pre-release sample. The 42% reduction reflects that defined task, not all compliance work.
02 / Regional care · Patient access
Northvale Care Network
A referral and scheduling journey built for care coordinators working across a regional network.
Outcome · successful referral completion
higher completion after launch
The challenge
Regional coordinators received referrals through multiple channels. Incomplete information and unclear ownership meant that patients could wait while teams chased missing details. Existing scheduling tools differed across sites and had to remain in use.
The approach
We mapped the referral journey with coordinators and tested the content and status language with staff. The team chose a shared intake and tracking layer that could coexist with site scheduling, with a simple route for a coordinator to ask for clarification.
What shipped
A responsive referral portal, structured submission and completeness checks, a coordinator triage view, status updates, scheduling handoff and a small rollout across representative sites before wider adoption.
Successful completion was measured as referrals reaching the network’s agreed completion state, compared with the period before launch. No patient-level outcome claim is implied.
03 / Specialist distribution · Operations
Fieldmark Supply
An operations platform that helps a specialist building-material distributor catch exceptions while the day can still be changed.
Outcome · same-day exception resolution
of exceptions resolved the day they appear
The challenge
Order, warehouse and supplier updates lived in separate tools. Teams spotted shortages late, often after a delivery window had passed. The distributor had limited time for training and could not pause its dispatch operation for a large platform change.
The approach
We shadowed dispatch and customer service staff, then ranked exceptions by urgency and controllability. A staged release focused first on a shared queue and clear ownership. The team preserved familiar source systems and avoided adding alerts that could not be acted on.
What shipped
An operational exception board, source-system connectors, ownership and status tracking, a small set of actionable notifications and an onboarding playbook for shift teams.
The same-day figure is the share of tracked exceptions resolved before the end of their logged business day, measured after rollout against the earlier 54% baseline.
Is your operation telling a similar story?
Start with the part of the work that feels harder than it should.
Discuss your project ↗