About Lambda Twelve

We start by understanding the process, not the software. Most failed systems we are asked to rescue failed because somebody wrote down what the business was supposed to do rather than what it actually does.

We deliver in pieces that work, rather than in one large release at the end. A module that is live and used is worth more than three that are nearly finished.

We write things down. Handover documentation is produced during the build, while the reasons behind a decision are still fresh, not reconstructed afterwards.

We are a remote team, so there is no office to visit and no reception to get past. In practice that means the person who replies to you is the person doing the work, not somebody relaying it.

The infrastructure is a different matter, because it is physical. We rent the metal and the racks; everything above them — the hypervisors, the storage design, the network — is ours to run.

Hypervisor cluster

Helsinki · Falkenstein · Nuremberg

Backups

Helsinki · Falkenstein · Amsterdam · Piraeus

Every one of them is inside the EU. What we run on says exactly whose racks they are.

We will tell you when a project does not need us, when an off-the-shelf product would be cheaper than a custom build, and when a supplier is charging you for something you do not need.

This occasionally costs us work. It has also been the reason for a good deal of the work we have.