Skip to content
TresVerse

Insights

Thinking, published when it is finished.

Positions we hold about building software for institutions. Written up as they are finished, and not before.

  • Software Engineering

    The fourth year is the review that counts

    Every system is defensible on launch day. The useful question is what it costs to change once the people who built it have moved on.

  • Artificial Intelligence

    Retrieval before prediction

    Most institutions asking for a model are describing a search problem. Making the record legible is cheaper, safer, and usually the whole answer.

  • Automation

    The steps between the systems

    The manual work in an organisation rarely sits inside a product. It sits in the gaps where one system’s output becomes another’s input by hand.

  • ERP

    One number, one meaning

    An ERP earns its cost the moment finance and operations stop reconciling two versions of the same figure. Everything else it does is secondary.

  • Digital Transformation

    Replacing a system that still works

    Nothing can be switched off on a Friday. Modernisation is a sequence of reversible steps, or it is an outage with a project plan attached.