We rebuild the software your business runs on.

The tool from 2004 your whole company still depends on: we take it over, keep it running, and make it better every week. The work that is pure routine goes to AI agents we build and test ourselves.

Where to start.

Three ways in, one per practice.

Software modernization

Built years ago, extended by nobody, too risky to touch. That is where we start.

How an engagement runs

The engagement

RebuildWe rebuild what you run today, fix what is broken, and tailor it to how you work.
IterateBug fixes and small features: requested one week, shipped the next.
ProveNothing switches off until the replacement has proven itself on your real data.
OwnWhat we build is yours, including the IP.

AI agents

Routine work, carried by an agent we build: one workflow, a permission map decided first, every action logged.

How we build them

Permission map

Specimen

ReadThe order inbox and the ERP exports.
WriteStaging tables only.
SpendNothing.
SendInternal summaries, named recipients.

Enforced outside the model.

We know how agents break. It shows in what we build.

AI agent audits

Before an AI agent goes live, we attack it: hostile documents, poisoned tool outputs, attempts to exceed its authority.

The method, the engagements, the sample report

Gate review · Findings

Fictional sample

AF-01Prompt injectionbroke
AF-04Spend-limit / policy-engine bypassbroke
nonePayment execution was outside the agent’s reachheld

From the sample gate-review report, a fictional engagement.

How we work.

  • Scope and price are agreed before we start.
  • You see progress every week, not a report at the end.
  • You talk to the engineers doing the work.

More about the firm

Let’s talk.

The people on the call are the engineers who would do the work.