Industries

Domain knowledge is the difference between six weeks and six days.

Requirements gathering is mostly translation. When we already know what a settlement window is, or why a clinician won't tolerate a second login, we skip the education and get to the design. These are the sectors where we've already made the expensive mistakes.

Banking & fintech

Where a rounding error is a regulatory event.

Core ledgers, payments, KYC and regulatory reporting. We've rebuilt a settlement engine while it was still processing live volume, which is the kind of thing you only agree to once you've done the dual-running maths.

Event-sourced ledgers with full replay and audit
UPI, NEFT, RTGS, SWIFT and card scheme integrations
KYC/AML workflows with case management
RBI and regulatory reporting pipelines

Read the Northbank case study

Typical constraints we design around

Zero tolerance on money movementReconciliation must prove itself, not assert itself

Immovable regulatory datesScope flexes; the date rarely does

Data residencyStorage and processing inside jurisdiction

Legacy that cannot pauseMigration happens alongside live operation

Healthcare & life sciences

The interface competes with the patient in front of them.

Patient platforms, diagnostics workflows and clinical data handling. The hard part is almost never the integration — it's persuading a clinician that a new screen won't cost them ninety seconds per consultation.

HL7 v2, FHIR and DICOM integration
Consent and access control built into the data layer
HIPAA-aligned and DPDP-compliant handling
Clinical workflow design with real time-and-motion testing

Read the Verdana Health case study

Typical constraints we design around

Clinician time is the scarce resourceEvery extra click is measured and defended

Consent is granular and revocableModelled properly, not bolted on

Records outlive systemsExport formats agreed before build

Downtime has clinical consequencesDegraded mode designed, not improvised

Retail & commerce

Inventory truth is harder than it sounds.

Omnichannel inventory, pricing engines and storefronts at scale. Most retail problems we're called into turn out to be one problem wearing different clothes: nobody agrees what "in stock" means.

Single inventory view across stores, warehouses and marketplaces
Rules-based pricing and promotion engines
Headless commerce and high-traffic storefronts
Peak-event load testing against real traffic shapes

A recent result

Halden Retail repriced 190 stores overnight in a batch that regularly overran into trading hours. We replaced it with a rules engine that repriced in 40 seconds and could be run mid-day.

40 sFull reprice

190Stores

0Trading overruns

Logistics & mobility

Optimal routes that drivers will actually follow.

Route optimisation, fleet telemetry and warehouse orchestration. A route that's 4% shorter but ignores where drivers can safely stop gets quietly abandoned in week two, and then you've paid for nothing.

Live re-routing with driver-acceptance modelling
Telematics ingestion at fleet scale
Warehouse and yard orchestration
Offline-first mobile for patchy coverage

A recent result

Kestrel Logistics re-routes 2,400 vehicles live. Empty-run kilometres fell 22% in the first quarter, and driver acceptance of suggested routes sat above 90% because the model was trained on what they'd historically accepted.

22%Empty-run cut

2,400Vehicles

91%Route acceptance

Manufacturing

Shop-floor systems survive by being simple.

MES integration, predictive maintenance and production visibility. Anything that needs a supervisor to read a manual at shift change will not be used, and the plant will go back to the whiteboard within a fortnight.

MES and SCADA integration with existing PLCs
Predictive maintenance on real sensor history
OEE dashboards readable from ten feet away
Multi-plant ERP rollouts, plant by plant

See Atlas ERP

Typical constraints we design around

Equipment older than the networkProtocol bridging rather than replacement

Shift handover is the real interfaceDesigned for gloves, glare and noise

Downtime costs are per minuteRollout sequenced around planned stops

Energy & utilities

Grid data is enormous, late and occasionally wrong.

Grid analytics, metering platforms and asset performance. Half the engineering is handling the meters that report twice, the ones that report nothing for six hours, and the ones that report from a decade in the future.

Smart-meter ingestion at millions of reads per day
Fault prediction with explicit false-positive budgets
Asset performance and outage management
Late and duplicate data handled as normal, not exceptional

A recent result

Talvera Energy predicts faults across 1.1M smart meters. The model gives around 40 minutes of early warning on average — chosen deliberately over a sharper model that generated more false call-outs than crews could absorb.

1.1MMeters

40 minEarly warning

3.1%False positives

Education

Term dates are the hardest deadline in software.

Learning platforms, assessment engines and institution systems. There is no negotiating with the start of an academic year, so we sequence releases backwards from it and cut scope rather than dates.

Learning platforms built for low-bandwidth access
Assessment and proctoring with integrity controls
Admissions, records and fee systems
Accessibility as a procurement requirement, met properly

Typical constraints we design around

Enrolment-day traffic spikesLoad tested at 20× normal, every year

Devices are old and sharedBudget Android over throttled 3G is the test bench

Minors' dataStricter retention and consent by default

Public sector

Everyone is a user, including the people you didn't plan for.

Citizen services, records digitisation and accessibility compliance. Public systems can't select their audience, which means the edge cases aren't edge cases — they're several million people.

WCAG 2.2 AA verified by assistive-technology users
Multilingual interfaces including right-to-left scripts
Records digitisation with OCR and verification workflows
Open, documented data formats and no lock-in

Typical constraints we design around

Procurement shapes architectureExit and portability specified up front

Assisted digital is mandatoryPhone and counter routes designed alongside

Public scrutinyDecisions documented so they can be defended

Not on this list?

Then we'll say so. If we don't have the domain depth for your sector we'll tell you in the first call rather than learning on your budget — and we'll usually know someone who does.

Describe your problem See the work