Taking over a live product without switching it off.
A company asked us to take over the software its customers pay for, from the outside team that built it. Nine weeks later it was fully theirs.
Case study · Build
- 9 weeksFrom the first look to full ownership.
- 1.7bn recordsSearched by paying customers the whole time.
- 876 checksRan during the first release. None failed.
The situation
Our client sells a data product. Their customers log in to search and compare about 1.7 billion records. An outside contractor had built it and ran it day to day.
The client wanted to own it themselves: the code, the servers, the passwords, all of it. They asked us to make that happen while customers kept using the product.
There are two ways to get this wrong. The first is to believe everything you are told. Then every hidden fault becomes yours on day one. The second is to start changing things before you understand them. Then you break the product yourself.
What we did
We looked before we touched.
We took a locked copy of all the code and read it. We changed nothing. We found 32 faults, two of them serious. One would have crashed the product the next time anyone updated it.
We checked everything we were told.
The contractor handed over a document with 55 points. We marked each one as verified, reported or open. A point stayed “reported” until we had seen it for ourselves. Six turned out to be wrong. Some of the databases had no backups.
We moved one thing at a time.
First the code moved to the client’s own account. Then the system that publishes updates. Only after both were proved did we publish an update. Each step could be undone.
We proved we could go back.
Two days after the move, one change hid some data from signed-in customers. We put the previous version back and the data returned. Then we fixed the cause properly.
The result
The first full update under the client’s ownership took 56 minutes. 876 automatic checks ran while it went live. None failed.
The client now holds the code, the keys and the backups. Every change is checked automatically before it reaches a customer.
What we learned
Look before you touch.
A week of reading saved the product from a crash.
Treat every claim as unproved until you have seen it.
A handover document says how a system was meant to work. The live system says how it does.
A green light is not proof.
A server can report that it is healthy while customers see an empty screen. Check what the customer sees.