Angulith

Practice

Software

Software gives ideas form — ledgers, consoles, and APIs written so a staff team can inherit them.

For operators who have outgrown a vendor template or a first-generation internal tool, and need software they will still own in five years.

We design and ship the software that sits under the operation: clearing and posting, operational consoles, partner APIs, the unglamorous internals that cannot be bought as a template. The brief is rarely “an app.” It is a constraint set — a regulator, an incumbent vendor, a data model that already exists, a team that has to live in the repository after we leave.

We start with the system of record and the people who already keep the process alive in spreadsheets. We write the boundaries down. We choose durable defaults on purpose: explicit contracts, predictable deploy paths, tests around the money and the identity, not around the framework of the season.

Delivery is a thin vertical slice that is real in production, then the next slice, with the inheriting engineers in the reviews from the first month. If a decision will be expensive to reverse, it is written, dated, and owned.

This practice almost always sits next to Cloud. Software that cannot be promoted the same way from a laptop to live is not finished, however polished the interface looks in staging.

What you leave with

  1. 01

    A codebase a staff engineer can extend without a guided tour

  2. 02

    Interfaces and data contracts written down, not implied in Slack

  3. 03

    A delivery cadence you can predict past the first release

  4. 04

    The original operators reviewing exceptions, not rebuilding the month

  5. 05

    A written architecture the next engagement can argue with

Related engagements