The system nobody dares touch.

Built by people long gone, and holding everything together. Every company has one. We take it over: first a fixed-price pilot on the one workflow that hurts most, then week by week from there.

The pilot

One workflowYou pick it.
Fixed priceAgreed before we start.
Two weeksThe typical pilot, start to finish.
In productionA working replacement, run alongside the old system.

How an engagement runs.

1. The pilot

You pick the workflow. We agree on a fixed price, and typically two weeks later a working replacement of that workflow is in production, not a slide deck. Your old system keeps running the whole time; nothing is switched off until the replacement has proven itself alongside it, on your real data.

2. Week by week

We maintain and extend what we built. Bug fixes and small features: requested one week, shipped the next. As with the pilot, the price is fixed and agreed before the work starts. And when something new should be built rather than bought, we build it.

AI agents are part of this work now. Where one can carry the routine, we build it into the system: the overnight jobs, the recurring checks, the small fixes.

Building agents, as its own practice

3. The long run

Software should outlive the team that built it. We build to that standard, and we keep what we ship worth improving.

What you receive.

  • The repository, with its full history.
  • A runbook, so the system can be run by people who did not build it.
  • The test suite.
  • A staging environment that matches production.
  • The IP, assigned to you.

Start with the workflow that hurts most.

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