Skip to content
Insights

What we argue about internally

Positions we hold because of what the work taught us. No client detail, no case studies dressed as articles.

Core banking ·  · 6 min read

The ledger is the product

In payments, the accounting model is the one decision application code cannot recover from. Get it wrong and every feature after it inherits the error.

Read
Payments ·  · 6 min read

Every check spends the same budget

An authorisation has a deadline that the scheme sets and you do not. Every fraud, limit and balance check you add is paid for out of the same window.

Read
Fraud and risk ·  · 5 min read

Fraud controls on a platform already clearing

Nobody installs fraud decisioning on an empty system. The work is proving a new engine on live money without declining anyone it should not.

Read
Reporting ·  · 5 min read

A report is a query, not a project

Reporting built after the platform becomes a second system with its own version of the truth. Built from the ledger, it is a view of the one you already have.

Read

Beyond finance

Two positions from work at sea and in applied AI. Both hold for a regulated firm.

Resilience ·  · 5 min read

Software that assumes the link will drop

Offshore, connectivity has a budget, and systems designed on shore usually fail at sea on that one assumption. An operational resilience test asks the same discipline of a bank.

Read
Applied AI ·  · 5 min read

Write the eval before the prompt

Most AI features ship with no way to tell whether the next change improved them. That is a design gap, not a testing one. In a regulated product the eval is also the audit trail.

Read

Leave with the approach, the risks and what it would take

Ninety minutes with the engineers who would do the work, on one problem you name: a processor replacement, an onboarding flow, a ledger reconciliation.

Book a whiteboard sessionSee the work