All work

Supply chain operator — under NDA

An agentic supply chain management system, built from scratch.

Sector
Supply chain
Engagement
Duration — to confirm
Scope
Platform build, from zero
Stack
Java · JavaScript · Postgres · AWS · Terraform

01The problem

Supply chain decisions were being made in inboxes, spreadsheets and the heads of a small number of people who had been there long enough to know what "normal" looked like.

That works until volume rises or one of those people leaves. The failure mode is not dramatic — nothing crashes. Decisions just get slower, less consistent, and harder to explain after the fact.

Narrative drafted from the brief — replace with the engagement detail

02What discovery found

  1. The bottleneck was the routine decisions, not the exceptional ones.

  2. Nothing recorded why a call had been made, only what it was.

  3. The proposed dashboard would have described the problem without changing it.

03What we built

An agentic system that handles the routine decisions and escalates the ones that genuinely need a person, with the reasoning recorded either way.

  • Decision engine

    Java services taking the routine calls against the rules the business already ran on, with the reasoning written to Postgres beside the decision.

  • Escalation path

    Anything outside the rules goes to a person, in a JavaScript front end that carries the context with it rather than making it be re-gathered.

  • Infrastructure and integrations

    Provisioned on AWS with Terraform, and wired into the systems already in use so nothing had to be re-keyed to make it work.

  • Handover

    Their team was in the pull requests during the build, not briefed at the end of it.

04 — What changed

Qualitative — add figures when you have them

  • Decisions stopped living in inboxes

    Routine calls are made by the system and recorded with their reasoning. The ones that need judgement get escalated rather than missed.

  • The knowledge is no longer in one head

    What "normal" looks like is written down and enforced, so the operation survives the person who used to know.

  • Their team runs it

    Handed over during the build rather than after it. We are not a dependency.

Got something shaped like this? Let's talk.

Discovery is free — you get a written proposal either way